Deployment / upgrade of 5.2 on a LXC container

[igarny]

Hello guys

There are error messages and a statement of Failure in relation to the apparmor config.
It had been operational before the upgrade from 5.1.4.

I am going to investigate further on these reports.

root@twamptst1:~# ./install.sh --repo nightly-minor testpoint

#
# Starting perfSONAR installation 2025-02-03T16:59:48
#


#
# Installing prerequisites
#

Reading package lists...
Building dependency tree...
Reading state information...
curl is already the newest version (7.81.0-1ubuntu1.20).
                                                        software-properties-common is already the newest version (0.99.22.9).
                                                                                                                             0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
                                                                                                                                                                                           8 not fully installed or removed.
                                After this operation, 0 B of additional disk space will be used.
                                                                                                Setting up owamp-server (5.1.4-1) ...

Configuration file '/etc/apparmor.d/usr.sbin.owampd'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** usr.sbin.owampd (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/apparmor.d/usr.sbin.owampd ...
Created symlink /etc/systemd/system/multi-user.target.wants/owamp-server.service в†’ /lib/systemd/system/owamp-server.service.
Job for owamp-server.service failed because a fatal signal was delivered to the control process.
See "systemctl status owamp-server.service" and "journalctl -xeu owamp-server.service" for details.
invoke-rc.d: initscript owamp-server, action "start" failed.
в—Џ owamp-server.service - OWAMP server
     Loaded: loaded (/lib/systemd/system/owamp-server.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: signal) since Mon 2025-02-03 17:00:00 UTC; 8ms ago
    Process: 1120 ExecStart=/usr/sbin/owampd -c /etc/owamp-server -R /var/run (code=killed, signal=SEGV)
        CPU: 1ms
dpkg: error processing package owamp-server (--configure):
 installed owamp-server package post-installation script subprocess returned error exit status 1
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                          dpkg: dependency problems prevent configuration of pscheduler-tool-powstream:
 pscheduler-tool-powstream depends on owamp-server; however:
  Package owamp-server is not configured yet.

dpkg: error processing package pscheduler-tool-powstream (--configure):
 dependency problems - leaving unconfigured
Setting up twamp-server (5.1.4-1) ...

Configuration file '/etc/apparmor.d/usr.sbin.twampd'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** usr.sbin.twampd (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/apparmor.d/usr.sbin.twampd ...
Created symlink /etc/systemd/system/multi-user.target.wants/twamp-server.service в†’ /lib/systemd/system/twamp-server.service.
Job for twamp-server.service failed because a fatal signal was delivered to the control process.
See "systemctl status twamp-server.service" and "journalctl -xeu twamp-server.service" for details.
invoke-rc.d: initscript twamp-server, action "start" failed.
в—Џ twamp-server.service - TWAMP server
     Loaded: loaded (/lib/systemd/system/twamp-server.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: signal) since Mon 2025-02-03 17:01:21 UTC; 9ms ago
    Process: 1320 ExecStart=/usr/sbin/twampd -c /etc/twamp-server -R /var/run (code=killed, signal=SEGV)
        CPU: 2ms
dpkg: error processing package twamp-server (--configure):
 installed twamp-server package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of pscheduler-tool-twping:
 pscheduler-tool-twping depends on twamp-server; however:
  Package twamp-server is not configured yet.

dpkg: error processing package pscheduler-tool-twping (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pscheduler-bundle-full:
 pscheduler-bundle-full depends on pscheduler-tool-powstream; however:
  Package pscheduler-tool-powstream is not configured yet.
 pscheduler-bundle-full depends on pscheduler-tool-twping; however:
  Package pscheduler-tool-twping is not configured yet.

dpkg: error processing package pscheduler-bundle-full (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of perfsonar-tools:
 perfsonar-tools depends on owamp-server (>= 3.No apport report written because MaxReports is reached already
                                                                                                             No apport report written because MaxReports is reached already
                                                                                                                                                                           No apport report written because MaxReports is reached already
                                             No apport report written because MaxReports is reached already
                                                                                                           No apport report written because MaxReports is reached already
                                                                                                                                                                         5.0); however:
  Package owamp-server is not configured yet.
 perfsonar-tools depends on twamp-server; however:
  Package twamp-server is not configured yet.

dpkg: error processing package perfsonar-tools (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pscheduler-tool-owping:
 pscheduler-tool-owping depends on owamp-server; however:
  Package owamp-server is not configured yet.

dpkg: error processing package pscheduler-tool-owping (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of perfsonar-testpoint:
 perfsonar-testpoint depends on perfsonar-tools; however:
  Package perfsonar-tools is not configured yet.
 perfsonar-testpoint depends on pscheduler-bundle-full | pscheduler-bundle-full-nos3; however:
  Package pscheduler-bundle-full is not configured yet.
  Package pscheduler-bundle-full-nos3 is not installed.

dpkg: error processing package perfsonar-testpoint (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 owamp-server
 pscheduler-tool-powstream
 twamp-server
 pscheduler-tool-twping
 pscheduler-bundle-full
 perfsonar-tools
 pscheduler-tool-owping
 perfsonar-testpoint
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)


INSTALLATION FAILED

Output logged to /root/install-perfsonar-2025-02-03T16:59:48

[igarny]

Same thing happens for a clean pS Testpoint 5.2 install
I have tried 2 deployments with and wihtout prior apparmor configuration