| 2017-08-09 16:44:06 |
Ramon Grullon |
bug |
|
|
added bug |
| 2017-08-09 17:03:04 |
Eric Desrochers |
tags |
|
sts sts-sru-needed |
|
| 2017-08-09 17:03:13 |
Eric Desrochers |
nominated for series |
|
Ubuntu Artful |
|
| 2017-08-09 17:03:13 |
Eric Desrochers |
bug task added |
|
logrotate (Ubuntu Artful) |
|
| 2017-08-09 17:03:13 |
Eric Desrochers |
nominated for series |
|
Ubuntu Trusty |
|
| 2017-08-09 17:03:13 |
Eric Desrochers |
bug task added |
|
logrotate (Ubuntu Trusty) |
|
| 2017-08-09 17:03:13 |
Eric Desrochers |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-08-09 17:03:13 |
Eric Desrochers |
bug task added |
|
logrotate (Ubuntu Xenial) |
|
| 2017-08-09 17:03:13 |
Eric Desrochers |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-08-09 17:03:13 |
Eric Desrochers |
bug task added |
|
logrotate (Ubuntu Zesty) |
|
| 2017-08-09 17:07:40 |
Eric Desrochers |
bug watch added |
|
https://github.com/logrotate/logrotate/issues/45 |
|
| 2017-08-09 17:07:51 |
Eric Desrochers |
logrotate (Ubuntu Artful): status |
New |
In Progress |
|
| 2017-08-09 17:07:53 |
Eric Desrochers |
logrotate (Ubuntu Artful): importance |
Undecided |
Medium |
|
| 2017-08-09 17:07:56 |
Eric Desrochers |
logrotate (Ubuntu Artful): assignee |
|
Eric Desrochers (slashd) |
|
| 2017-08-09 17:22:45 |
Eric Desrochers |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 |
|
| 2017-08-09 17:22:45 |
Eric Desrochers |
bug task added |
|
logrotate (Debian) |
|
| 2017-08-09 17:26:36 |
Eric Desrochers |
description |
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file
- Re-run "/etc/cron.daily/logrotate" and you will get something like this "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate
logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand.
System will eventually run out of disk space and crash. |
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand.
System will eventually run out of disk space on /var/log for instance.
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file
- Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate
[Regression Potential]
* Risk of potential regression is low, and couldn' be worst than the actual situation where logrotate doesn't recover from a corrupt statefile.
The current patch does recover (after verification)
[Other Info]
* Upstream commit:
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a
* Upstream bug:
https://github.com/logrotate/logrotate/issues/45
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 |
|
| 2017-08-09 17:26:50 |
Eric Desrochers |
bug |
|
|
added subscriber Eric Desrochers |
| 2017-08-09 17:34:45 |
Eric Desrochers |
description |
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand.
System will eventually run out of disk space on /var/log for instance.
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file
- Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate
[Regression Potential]
* Risk of potential regression is low, and couldn' be worst than the actual situation where logrotate doesn't recover from a corrupt statefile.
The current patch does recover (after verification)
[Other Info]
* Upstream commit:
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a
* Upstream bug:
https://github.com/logrotate/logrotate/issues/45
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 |
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand.
System will eventually run out of disk space on /var/log for instance.
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file
- Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate
Unless you remove the statefile and start again or fix the corruption by hand.
[Regression Potential]
* Risk of potential regression is low, and couldn' be worst than the actual situation where logrotate doesn't recover from a corrupt statefile.
The current patch does recover (after verification)
[Other Info]
* Upstream commit:
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a
* Upstream bug:
https://github.com/logrotate/logrotate/issues/45
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 |
|
| 2017-08-09 18:17:26 |
Eric Desrochers |
attachment added |
|
lp1709670-logrotate-artful.debdiff https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+attachment/4929643/+files/lp1709670-logrotate-artful.debdiff |
|
| 2017-08-09 18:18:36 |
Eric Desrochers |
tags |
sts sts-sru-needed |
patch sts sts-sru-needed |
|
| 2017-08-09 18:18:45 |
Eric Desrochers |
bug |
|
|
added subscriber Ubuntu Security Sponsors Team |
| 2017-08-09 18:18:47 |
Eric Desrochers |
removed subscriber Ubuntu Security Sponsors Team |
|
|
|
| 2017-08-09 18:18:53 |
Eric Desrochers |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2017-08-09 18:20:09 |
Eric Desrochers |
logrotate (Ubuntu Trusty): status |
New |
Confirmed |
|
| 2017-08-09 18:20:13 |
Eric Desrochers |
logrotate (Ubuntu Zesty): status |
New |
Confirmed |
|
| 2017-08-09 18:20:15 |
Eric Desrochers |
logrotate (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2017-08-09 18:29:43 |
Eric Desrochers |
attachment added |
|
lp1709670-logrotate-zesty.debdiff https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+attachment/4929665/+files/lp1709670-logrotate-zesty.debdiff |
|
| 2017-08-09 18:30:12 |
Eric Desrochers |
logrotate (Ubuntu Zesty): assignee |
|
Eric Desrochers (slashd) |
|
| 2017-08-09 18:30:14 |
Eric Desrochers |
logrotate (Ubuntu Xenial): assignee |
|
Eric Desrochers (slashd) |
|
| 2017-08-09 18:30:16 |
Eric Desrochers |
logrotate (Ubuntu Trusty): assignee |
|
Eric Desrochers (slashd) |
|
| 2017-08-09 18:36:16 |
Eric Desrochers |
description |
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand.
System will eventually run out of disk space on /var/log for instance.
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file
- Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate
Unless you remove the statefile and start again or fix the corruption by hand.
[Regression Potential]
* Risk of potential regression is low, and couldn' be worst than the actual situation where logrotate doesn't recover from a corrupt statefile.
The current patch does recover (after verification)
[Other Info]
* Upstream commit:
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a
* Upstream bug:
https://github.com/logrotate/logrotate/issues/45
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 |
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand.
System will eventually run out of disk space on /var/log for instance.
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file
- Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate
Unless you remove the statefile and start again or fix the corruption by hand.
[Regression Potential]
* Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile.
* The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al.
[Other Info]
* Upstream commit:
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a
* Upstream bug:
https://github.com/logrotate/logrotate/issues/45
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 |
|
| 2017-08-09 19:03:01 |
Nish Aravamudan |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2017-08-09 19:45:44 |
Eric Desrochers |
description |
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand.
System will eventually run out of disk space on /var/log for instance.
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file
- Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate
Unless you remove the statefile and start again or fix the corruption by hand.
[Regression Potential]
* Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile.
* The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al.
[Other Info]
* Upstream commit:
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a
* Upstream bug:
https://github.com/logrotate/logrotate/issues/45
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 |
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand.
System will eventually run out of disk space on /var/log for instance.
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file
- Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate
Unless you remove the statefile and start again or fix the corruption by hand.
[Regression Potential]
* Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile.
* The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al.
* Additionally, I will run the /path_to_source/test/test script as a dogfooding that does a bunch of tests.
[Other Info]
* Upstream commit:
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a
* Upstream bug:
https://github.com/logrotate/logrotate/issues/45
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 |
|
| 2017-08-09 19:49:29 |
Eric Desrochers |
description |
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand.
System will eventually run out of disk space on /var/log for instance.
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file
- Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate
Unless you remove the statefile and start again or fix the corruption by hand.
[Regression Potential]
* Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile.
* The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al.
* Additionally, I will run the /path_to_source/test/test script as a dogfooding that does a bunch of tests.
[Other Info]
* Upstream commit:
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a
* Upstream bug:
https://github.com/logrotate/logrotate/issues/45
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 |
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand.
System will eventually run out of disk space on /var/log for instance.
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file
- Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate
Unless you remove the statefile and start again or fix the corruption by hand.
[Regression Potential]
* Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile.
* The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al.
* Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests.
[Other Info]
* Upstream commit:
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a
* Upstream bug:
https://github.com/logrotate/logrotate/issues/45
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 |
|
| 2017-08-09 19:49:40 |
Eric Desrochers |
tags |
patch sts sts-sru-needed |
sts sts-sru-needed |
|
| 2017-08-09 19:49:53 |
Eric Desrochers |
bug |
|
|
added subscriber SRU Verification |
| 2017-08-09 19:59:20 |
Eric Desrochers |
attachment removed |
lp1709670-logrotate-zesty.debdiff https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+attachment/4929665/+files/lp1709670-logrotate-zesty.debdiff |
|
|
| 2017-08-09 20:30:19 |
Eric Desrochers |
logrotate (Ubuntu Zesty): status |
Confirmed |
In Progress |
|
| 2017-08-09 20:30:24 |
Eric Desrochers |
logrotate (Ubuntu Trusty): status |
Confirmed |
In Progress |
|
| 2017-08-09 20:30:26 |
Eric Desrochers |
logrotate (Ubuntu Xenial): status |
Confirmed |
In Progress |
|
| 2017-08-09 21:31:25 |
Eric Desrochers |
logrotate (Ubuntu Artful): status |
In Progress |
Fix Committed |
|
| 2017-08-10 02:20:31 |
Eric Desrochers |
description |
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand.
System will eventually run out of disk space on /var/log for instance.
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file
- Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate
Unless you remove the statefile and start again or fix the corruption by hand.
[Regression Potential]
* Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile.
* The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al.
* Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests.
[Other Info]
* Upstream commit:
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a
* Upstream bug:
https://github.com/logrotate/logrotate/issues/45
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 |
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand.
Impact scenarios :
- System could eventually run out of disk space on a separate partition if mounted in "/var" or specifically "/var/log" or even worst if "/var/log" is on the same partition as "/" it could create even more damage if by any chance the partition is running out of free space.
- System keep updating the same files over and over, creating large size logfiles.
- ...
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file
- Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate
Unless you remove the statefile and start again or fix the corruption by hand.
[Regression Potential]
* Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile.
* The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al.
* Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests.
[Other Info]
* Upstream commit:
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a
* Upstream bug:
https://github.com/logrotate/logrotate/issues/45
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 |
|
| 2017-08-10 02:20:51 |
Eric Desrochers |
description |
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand.
Impact scenarios :
- System could eventually run out of disk space on a separate partition if mounted in "/var" or specifically "/var/log" or even worst if "/var/log" is on the same partition as "/" it could create even more damage if by any chance the partition is running out of free space.
- System keep updating the same files over and over, creating large size logfiles.
- ...
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file
- Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate
Unless you remove the statefile and start again or fix the corruption by hand.
[Regression Potential]
* Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile.
* The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al.
* Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests.
[Other Info]
* Upstream commit:
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a
* Upstream bug:
https://github.com/logrotate/logrotate/issues/45
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 |
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand.
Impact scenarios :
- System could eventually run out of disk space on a separate partition if mounted in "/var" or specifically "/var/log" or even worst if "/var/log" is on the same partition as "/" it could create even more damage if by any chance the partition is running out of free space.
- System keep updating the same files over and over, creating large size logfiles.
- ...
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file
- Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate
Unless you remove the statefile and start again or fix the corruption by hand.
[Regression Potential]
* Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile.
* The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al.
* Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests.
[Other Info]
* Upstream commit:
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a
* Upstream bug:
https://github.com/logrotate/logrotate/issues/45
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 |
|
| 2017-08-10 02:21:12 |
Eric Desrochers |
description |
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand.
Impact scenarios :
- System could eventually run out of disk space on a separate partition if mounted in "/var" or specifically "/var/log" or even worst if "/var/log" is on the same partition as "/" it could create even more damage if by any chance the partition is running out of free space.
- System keep updating the same files over and over, creating large size logfiles.
- ...
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file
- Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate
Unless you remove the statefile and start again or fix the corruption by hand.
[Regression Potential]
* Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile.
* The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al.
* Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests.
[Other Info]
* Upstream commit:
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a
* Upstream bug:
https://github.com/logrotate/logrotate/issues/45
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 |
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand.
Impact scenarios :
- System could eventually run out of disk space on a separate partition if mounted in "/var" or specifically "/var/log" or even worst if "/var/log" is on the same partition as "/" it could create even more damage if by any chance the partition is running out of free space.
- System keep updating the same files over and over, creating large size logfiles.
- ...
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file
- Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate
Unless you remove the statefile and start again or fix the corruption by hand.
* Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests.
[Regression Potential]
* Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile.
* The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al.
* Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests.
[Other Info]
* Upstream commit:
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a
* Upstream bug:
https://github.com/logrotate/logrotate/issues/45
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 |
|
| 2017-08-10 02:40:43 |
Launchpad Janitor |
logrotate (Ubuntu Artful): status |
Fix Committed |
Fix Released |
|
| 2017-08-10 12:58:10 |
Eric Desrochers |
attachment added |
|
lp1709670-logrotate-trusty.debdiff https://bugs.launchpad.net/ubuntu/trusty/+source/logrotate/+bug/1709670/+attachment/4929987/+files/lp1709670-logrotate-trusty.debdiff |
|
| 2017-08-10 12:59:04 |
Eric Desrochers |
attachment added |
|
lp1709670-logrotate-zesty.debdiff https://bugs.launchpad.net/ubuntu/trusty/+source/logrotate/+bug/1709670/+attachment/4929988/+files/lp1709670-logrotate-zesty.debdiff |
|
| 2017-08-10 12:59:43 |
Eric Desrochers |
attachment added |
|
lp1709670-logrotate-xenial.debdiff https://bugs.launchpad.net/ubuntu/trusty/+source/logrotate/+bug/1709670/+attachment/4929989/+files/lp1709670-logrotate-xenial.debdiff |
|
| 2017-08-10 13:00:00 |
Eric Desrochers |
logrotate (Ubuntu Trusty): importance |
Undecided |
Medium |
|
| 2017-08-10 13:00:02 |
Eric Desrochers |
logrotate (Ubuntu Xenial): importance |
Undecided |
Critical |
|
| 2017-08-10 13:00:03 |
Eric Desrochers |
logrotate (Ubuntu Xenial): importance |
Critical |
Medium |
|
| 2017-08-10 13:00:05 |
Eric Desrochers |
logrotate (Ubuntu Zesty): importance |
Undecided |
Medium |
|
| 2017-08-10 13:01:49 |
Eric Desrochers |
tags |
sts sts-sru-needed |
sts sts-sponsor-done sts-sru-needed |
|
| 2017-08-10 15:12:48 |
Łukasz Zemczak |
logrotate (Ubuntu Zesty): status |
In Progress |
Fix Committed |
|
| 2017-08-10 15:12:49 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-08-10 15:12:53 |
Łukasz Zemczak |
tags |
sts sts-sponsor-done sts-sru-needed |
sts sts-sponsor-done sts-sru-needed verification-needed verification-needed-zesty |
|
| 2017-08-10 15:15:04 |
Łukasz Zemczak |
logrotate (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2017-08-10 15:15:09 |
Łukasz Zemczak |
tags |
sts sts-sponsor-done sts-sru-needed verification-needed verification-needed-zesty |
sts sts-sponsor-done sts-sru-needed verification-needed verification-needed-xenial verification-needed-zesty |
|
| 2017-08-10 15:17:05 |
Łukasz Zemczak |
logrotate (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2017-08-10 15:17:10 |
Łukasz Zemczak |
tags |
sts sts-sponsor-done sts-sru-needed verification-needed verification-needed-xenial verification-needed-zesty |
sts sts-sponsor-done sts-sru-needed verification-needed verification-needed-trusty verification-needed-xenial verification-needed-zesty |
|
| 2017-08-11 10:26:34 |
Bug Watch Updater |
logrotate (Debian): status |
Unknown |
New |
|
| 2017-08-15 20:46:31 |
Eric Desrochers |
tags |
sts sts-sponsor-done sts-sru-needed verification-needed verification-needed-trusty verification-needed-xenial verification-needed-zesty |
sts sts-sponsor-done sts-sru-needed verification-done-xenial verification-needed verification-needed-trusty verification-needed-zesty |
|
| 2017-08-16 21:37:56 |
Eric Desrochers |
tags |
sts sts-sponsor-done sts-sru-needed verification-done-xenial verification-needed verification-needed-trusty verification-needed-zesty |
sts sts-sponsor-done sts-sru-needed verification-done-trusty verification-done-xenial verification-needed verification-needed-zesty |
|
| 2017-08-17 21:20:18 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-08-17 21:21:10 |
Launchpad Janitor |
logrotate (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-08-17 21:30:23 |
Launchpad Janitor |
logrotate (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2017-08-21 14:31:40 |
Eric Desrochers |
tags |
sts sts-sponsor-done sts-sru-needed verification-done-trusty verification-done-xenial verification-needed verification-needed-zesty |
sts sts-sponsor-done sts-sru-needed verification-done-trusty verification-done-xenial verification-done-zesty |
|
| 2017-08-21 19:12:09 |
Eric Desrochers |
tags |
sts sts-sponsor-done sts-sru-needed verification-done-trusty verification-done-xenial verification-done-zesty |
sts sts-sponsor-done sts-sru-needed verification-done-trusty verification-done-xenial verification-needed-zesty |
|
| 2017-08-21 19:12:34 |
Eric Desrochers |
tags |
sts sts-sponsor-done sts-sru-needed verification-done-trusty verification-done-xenial verification-needed-zesty |
sts sts-sponsor-done sts-sru-needed verification-done-trusty verification-done-xenial verification-done-zesty |
|
| 2017-08-23 01:39:34 |
Launchpad Janitor |
logrotate (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
| 2018-08-20 13:14:12 |
Edward Hope-Morley |
tags |
sts sts-sponsor-done sts-sru-needed verification-done-trusty verification-done-xenial verification-done-zesty |
sts sts-sponsor-done sts-sru-done verification-done-trusty verification-done-xenial verification-done-zesty |
|
| 2018-08-23 04:25:59 |
Bug Watch Updater |
logrotate (Debian): status |
New |
Fix Released |
|
