| 2024-02-26 14:11:30 |
Heinrich Schuchardt |
bug |
|
|
added bug |
| 2024-02-27 08:38:20 |
Calvin Mwadime Makokha |
ubuntu-advantage-tools (Ubuntu): status |
New |
Incomplete |
|
| 2024-02-27 09:00:22 |
Heinrich Schuchardt |
attachment added |
|
ua_logs.tar.gz https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2055046/+attachment/5749681/+files/ua_logs.tar.gz |
|
| 2024-02-27 09:01:51 |
Heinrich Schuchardt |
ubuntu-advantage-tools (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2024-02-27 15:42:11 |
Robie Basak |
tags |
|
regression-proposed |
|
| 2024-02-28 04:20:11 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto Murata |
| 2024-02-28 15:39:17 |
Patrik Lundquist |
tags |
regression-proposed |
noble regression-proposed |
|
| 2024-02-29 21:43:29 |
Ubuntu Archive Robot |
bug |
|
|
added subscriber Paride Legovini |
| 2024-03-04 14:40:36 |
Grant Orndorff |
description |
Logrotate does not start due to misconfigured Ubuntu Pro:
$ sudo systemctl status logrotate | cat
× logrotate.service - Rotate log files
Loaded: loaded (/usr/lib/systemd/system/logrotate.service; static)
Active: failed (Result: exit-code) since Mon 2024-02-26 15:10:44 CET; 9s ago
TriggeredBy: ● logrotate.timer
Docs: man:logrotate(8)
man:logrotate.conf(5)
Process: 85798 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=1/FAILURE)
Main PID: 85798 (code=exited, status=1/FAILURE)
CPU: 69ms
Feb 26 15:10:44 workstation5 systemd[1]: Starting logrotate.service - Rotate log files...
Feb 26 15:10:44 workstation5 logrotate[85798]: error: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage-license-check.log
Feb 26 15:10:44 workstation5 logrotate[85798]: error: found error in file ubuntu-pro-client, skipping
Feb 26 15:10:44 workstation5 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
Feb 26 15:10:44 workstation5 systemd[1]: logrotate.service: Failed with result 'exit-code'.
Feb 26 15:10:44 workstation5 systemd[1]: Failed to start logrotate.service - Rotate log files. |
[ Impact ]
After an upgrade from ubuntu-advantage-tools 30.1 to ubuntu-pro-client 31.1, an old logrotate conffile named ubuntu-advantage-tools is left behind. The old file configures the same files as the new conffile: ubuntu-pro-client.
The result is that when logrotate runs (on a daily timer) it has an error becuase two configurations for the same log files exist. This results in a "degrated" system status.
The fix is to use the `rm_conffile` maintscript to remove the old ubuntu-advantage-tools logrotate conffile on upgrade.
[ Test Plan ]
We added a test to the ubuntu-pro-client integration test suite that covers this scenario. It upgrades to the new ubuntu-pro-client and then runs logrotate and checks that there are no errors. Because this is covered by the integration test suite, this bug will be verified as part of the verification process for LP: #2048921.
[ Where problems could occur ]
Touching conffiles is always risky. It could result in the removal of a needed config option or in an unnecessary debconf prompt on upgrade. I tested that user modifications were preserved on upgrade, but there is always the possibility that something could go wrong.
[ Original Description ]
Logrotate does not start due to misconfigured Ubuntu Pro:
$ sudo systemctl status logrotate | cat
× logrotate.service - Rotate log files
Loaded: loaded (/usr/lib/systemd/system/logrotate.service; static)
Active: failed (Result: exit-code) since Mon 2024-02-26 15:10:44 CET; 9s ago
TriggeredBy: ● logrotate.timer
Docs: man:logrotate(8)
man:logrotate.conf(5)
Process: 85798 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=1/FAILURE)
Main PID: 85798 (code=exited, status=1/FAILURE)
CPU: 69ms
Feb 26 15:10:44 workstation5 systemd[1]: Starting logrotate.service - Rotate log files...
Feb 26 15:10:44 workstation5 logrotate[85798]: error: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage-license-check.log
Feb 26 15:10:44 workstation5 logrotate[85798]: error: found error in file ubuntu-pro-client, skipping
Feb 26 15:10:44 workstation5 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
Feb 26 15:10:44 workstation5 systemd[1]: logrotate.service: Failed with result 'exit-code'.
Feb 26 15:10:44 workstation5 systemd[1]: Failed to start logrotate.service - Rotate log files. |
|
| 2024-03-04 14:43:12 |
Grant Orndorff |
description |
[ Impact ]
After an upgrade from ubuntu-advantage-tools 30.1 to ubuntu-pro-client 31.1, an old logrotate conffile named ubuntu-advantage-tools is left behind. The old file configures the same files as the new conffile: ubuntu-pro-client.
The result is that when logrotate runs (on a daily timer) it has an error becuase two configurations for the same log files exist. This results in a "degrated" system status.
The fix is to use the `rm_conffile` maintscript to remove the old ubuntu-advantage-tools logrotate conffile on upgrade.
[ Test Plan ]
We added a test to the ubuntu-pro-client integration test suite that covers this scenario. It upgrades to the new ubuntu-pro-client and then runs logrotate and checks that there are no errors. Because this is covered by the integration test suite, this bug will be verified as part of the verification process for LP: #2048921.
[ Where problems could occur ]
Touching conffiles is always risky. It could result in the removal of a needed config option or in an unnecessary debconf prompt on upgrade. I tested that user modifications were preserved on upgrade, but there is always the possibility that something could go wrong.
[ Original Description ]
Logrotate does not start due to misconfigured Ubuntu Pro:
$ sudo systemctl status logrotate | cat
× logrotate.service - Rotate log files
Loaded: loaded (/usr/lib/systemd/system/logrotate.service; static)
Active: failed (Result: exit-code) since Mon 2024-02-26 15:10:44 CET; 9s ago
TriggeredBy: ● logrotate.timer
Docs: man:logrotate(8)
man:logrotate.conf(5)
Process: 85798 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=1/FAILURE)
Main PID: 85798 (code=exited, status=1/FAILURE)
CPU: 69ms
Feb 26 15:10:44 workstation5 systemd[1]: Starting logrotate.service - Rotate log files...
Feb 26 15:10:44 workstation5 logrotate[85798]: error: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage-license-check.log
Feb 26 15:10:44 workstation5 logrotate[85798]: error: found error in file ubuntu-pro-client, skipping
Feb 26 15:10:44 workstation5 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
Feb 26 15:10:44 workstation5 systemd[1]: logrotate.service: Failed with result 'exit-code'.
Feb 26 15:10:44 workstation5 systemd[1]: Failed to start logrotate.service - Rotate log files. |
[ Impact ]
After an upgrade from ubuntu-advantage-tools 30.1 to ubuntu-pro-client 31.1, an old logrotate conffile named ubuntu-advantage-tools is left behind. The old file configures the same files as the new conffile: ubuntu-pro-client.
The result is that when logrotate runs (on a daily timer) it has an error because two configurations for the same log files exist. This results in a "degraded" system status.
The fix is to use the `rm_conffile` maintscript to remove the old ubuntu-advantage-tools logrotate conffile on upgrade.
[ Test Plan ]
We added a test to the ubuntu-pro-client integration test suite that covers this scenario. It upgrades to the new ubuntu-pro-client and then runs logrotate and checks that there are no errors. Because this is covered by the integration test suite, this bug will be verified as part of the verification process for LP: #2048921.
[ Where problems could occur ]
Touching conffiles is always risky. It could result in the removal of a needed config option or in an unnecessary debconf prompt on upgrade. I tested that user modifications were preserved on upgrade, but there is always the possibility that something could go wrong.
[ Original Description ]
Logrotate does not start due to misconfigured Ubuntu Pro:
$ sudo systemctl status logrotate | cat
× logrotate.service - Rotate log files
Loaded: loaded (/usr/lib/systemd/system/logrotate.service; static)
Active: failed (Result: exit-code) since Mon 2024-02-26 15:10:44 CET; 9s ago
TriggeredBy: ● logrotate.timer
Docs: man:logrotate(8)
man:logrotate.conf(5)
Process: 85798 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=1/FAILURE)
Main PID: 85798 (code=exited, status=1/FAILURE)
CPU: 69ms
Feb 26 15:10:44 workstation5 systemd[1]: Starting logrotate.service - Rotate log files...
Feb 26 15:10:44 workstation5 logrotate[85798]: error: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage-license-check.log
Feb 26 15:10:44 workstation5 logrotate[85798]: error: found error in file ubuntu-pro-client, skipping
Feb 26 15:10:44 workstation5 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
Feb 26 15:10:44 workstation5 systemd[1]: logrotate.service: Failed with result 'exit-code'.
Feb 26 15:10:44 workstation5 systemd[1]: Failed to start logrotate.service - Rotate log files. |
|
| 2024-03-04 16:04:18 |
Robie Basak |
ubuntu-advantage-tools (Ubuntu Mantic): status |
New |
Fix Committed |
|
| 2024-03-04 16:04:19 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2024-03-04 16:04:20 |
Robie Basak |
bug |
|
|
added subscriber SRU Verification |
| 2024-03-04 16:04:24 |
Robie Basak |
tags |
noble regression-proposed |
noble regression-proposed verification-needed verification-needed-mantic |
|
| 2024-03-04 16:04:51 |
Robie Basak |
ubuntu-advantage-tools (Ubuntu Jammy): status |
New |
Fix Committed |
|
| 2024-03-04 16:04:53 |
Robie Basak |
tags |
noble regression-proposed verification-needed verification-needed-mantic |
noble regression-proposed verification-needed verification-needed-jammy verification-needed-mantic |
|
| 2024-03-04 16:05:25 |
Robie Basak |
ubuntu-advantage-tools (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2024-03-04 16:05:27 |
Robie Basak |
tags |
noble regression-proposed verification-needed verification-needed-jammy verification-needed-mantic |
noble regression-proposed verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic |
|
| 2024-03-04 16:06:00 |
Robie Basak |
ubuntu-advantage-tools (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2024-03-04 16:06:03 |
Robie Basak |
tags |
noble regression-proposed verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic |
noble regression-proposed verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-mantic |
|
| 2024-03-04 16:06:33 |
Robie Basak |
ubuntu-advantage-tools (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2024-03-04 16:06:36 |
Robie Basak |
tags |
noble regression-proposed verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-mantic |
noble regression-proposed verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-mantic verification-needed-xenial |
|
| 2024-03-06 20:07:35 |
Grant Orndorff |
description |
[ Impact ]
After an upgrade from ubuntu-advantage-tools 30.1 to ubuntu-pro-client 31.1, an old logrotate conffile named ubuntu-advantage-tools is left behind. The old file configures the same files as the new conffile: ubuntu-pro-client.
The result is that when logrotate runs (on a daily timer) it has an error because two configurations for the same log files exist. This results in a "degraded" system status.
The fix is to use the `rm_conffile` maintscript to remove the old ubuntu-advantage-tools logrotate conffile on upgrade.
[ Test Plan ]
We added a test to the ubuntu-pro-client integration test suite that covers this scenario. It upgrades to the new ubuntu-pro-client and then runs logrotate and checks that there are no errors. Because this is covered by the integration test suite, this bug will be verified as part of the verification process for LP: #2048921.
[ Where problems could occur ]
Touching conffiles is always risky. It could result in the removal of a needed config option or in an unnecessary debconf prompt on upgrade. I tested that user modifications were preserved on upgrade, but there is always the possibility that something could go wrong.
[ Original Description ]
Logrotate does not start due to misconfigured Ubuntu Pro:
$ sudo systemctl status logrotate | cat
× logrotate.service - Rotate log files
Loaded: loaded (/usr/lib/systemd/system/logrotate.service; static)
Active: failed (Result: exit-code) since Mon 2024-02-26 15:10:44 CET; 9s ago
TriggeredBy: ● logrotate.timer
Docs: man:logrotate(8)
man:logrotate.conf(5)
Process: 85798 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=1/FAILURE)
Main PID: 85798 (code=exited, status=1/FAILURE)
CPU: 69ms
Feb 26 15:10:44 workstation5 systemd[1]: Starting logrotate.service - Rotate log files...
Feb 26 15:10:44 workstation5 logrotate[85798]: error: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage-license-check.log
Feb 26 15:10:44 workstation5 logrotate[85798]: error: found error in file ubuntu-pro-client, skipping
Feb 26 15:10:44 workstation5 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
Feb 26 15:10:44 workstation5 systemd[1]: logrotate.service: Failed with result 'exit-code'.
Feb 26 15:10:44 workstation5 systemd[1]: Failed to start logrotate.service - Rotate log files. |
[ Impact ]
After an upgrade from ubuntu-advantage-tools 30.1 to ubuntu-pro-client 31.1, an old logrotate conffile named ubuntu-advantage-tools is left behind. The old file configures the same files as the new conffile: ubuntu-pro-client.
The result is that when logrotate runs (on a daily timer) it has an error because two configurations for the same log files exist. This results in a "degraded" system status.
The fix is to use the `mv_conffile` maintscript to remove the old ubuntu-advantage-tools logrotate conffile on upgrade.
[ Test Plan ]
We added a test to the ubuntu-pro-client integration test suite that covers this scenario. It upgrades to the new ubuntu-pro-client and then runs logrotate and checks that there are no errors. Because this is covered by the integration test suite, this bug will be verified as part of the verification process for LP: #2048921.
[ Where problems could occur ]
Touching conffiles is always risky. It could result in the removal of a needed config option or in an unnecessary debconf prompt on upgrade. I tested that user modifications were preserved on upgrade, but there is always the possibility that something could go wrong.
[ Original Description ]
Logrotate does not start due to misconfigured Ubuntu Pro:
$ sudo systemctl status logrotate | cat
× logrotate.service - Rotate log files
Loaded: loaded (/usr/lib/systemd/system/logrotate.service; static)
Active: failed (Result: exit-code) since Mon 2024-02-26 15:10:44 CET; 9s ago
TriggeredBy: ● logrotate.timer
Docs: man:logrotate(8)
man:logrotate.conf(5)
Process: 85798 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=1/FAILURE)
Main PID: 85798 (code=exited, status=1/FAILURE)
CPU: 69ms
Feb 26 15:10:44 workstation5 systemd[1]: Starting logrotate.service - Rotate log files...
Feb 26 15:10:44 workstation5 logrotate[85798]: error: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage-license-check.log
Feb 26 15:10:44 workstation5 logrotate[85798]: error: found error in file ubuntu-pro-client, skipping
Feb 26 15:10:44 workstation5 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
Feb 26 15:10:44 workstation5 systemd[1]: logrotate.service: Failed with result 'exit-code'.
Feb 26 15:10:44 workstation5 systemd[1]: Failed to start logrotate.service - Rotate log files. |
|
| 2024-03-09 01:59:32 |
Grant Orndorff |
tags |
noble regression-proposed verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-mantic verification-needed-xenial |
noble regression-proposed verification-done verification-done-bionic verification-done-focal verification-done-jammy verification-done-mantic verification-done-xenial |
|
| 2024-03-12 16:19:43 |
Launchpad Janitor |
ubuntu-advantage-tools (Ubuntu Mantic): status |
Fix Committed |
Fix Released |
|
| 2024-03-12 16:20:08 |
Andreas Hasenack |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2024-03-12 16:20:24 |
Launchpad Janitor |
ubuntu-advantage-tools (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2024-03-12 16:20:43 |
Launchpad Janitor |
ubuntu-advantage-tools (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2024-03-12 16:21:06 |
Launchpad Janitor |
ubuntu-advantage-tools (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2024-03-12 16:21:42 |
Launchpad Janitor |
ubuntu-advantage-tools (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2024-03-28 07:58:10 |
Launchpad Janitor |
ubuntu-advantage-tools (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2024-04-22 10:51:37 |
Stefan Jakl |
bug |
|
|
added subscriber Stefan Jakl |
