| 2016-05-17 16:52:47 |
James Page |
bug |
|
|
added bug |
| 2016-05-17 16:53:13 |
James Page |
description |
The change to lsb-base that landed into -updates on the 12th of May:
lsb (4.1+Debian11ubuntu6.1) trusty; urgency=medium
* Add 01-upstart-lsb from the upstart package and make
executing rc.d scripts no-op if there is an upstart
job for that script. (LP: #1273462)
-- Zhang Hua <joshua.zhang@canonical.com> Thu, 06 Aug 2015 11:11:16 -0500
changed the behaviour of init.d scripts to pass through to the associated upstart configuration for process management, where packages ship both an upstart configuration and an init.d configuration.
This has a rather nasty side effect on 'service --status-all', which calls the 'status' method on all installed init.d scripts - this gets translated into:
status <service-name>
for upstart scripts, which correctly identifies the process as not running, but always returns a 0 return code. As a result, --status-all incorrectly identifies upstart processes as actually running.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lsb-base 4.1+Debian11ubuntu6.1
ProcVersionSignature: User Name 3.13.0-86.130-generic 3.13.11-ckt39
Uname: Linux 3.13.0-86-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Tue May 17 16:47:30 2016
Dependencies:
Ec2AMI: ami-0000015b
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small.osci
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
PackageArchitecture: all
SourcePackage: lsb
UpgradeStatus: No upgrade log present (probably fresh install) |
The change to lsb-base that landed into -updates on the 12th of May:
lsb (4.1+Debian11ubuntu6.1) trusty; urgency=medium
* Add 01-upstart-lsb from the upstart package and make
executing rc.d scripts no-op if there is an upstart
job for that script. (LP: #1273462)
-- Zhang Hua <joshua.zhang@canonical.com> Thu, 06 Aug 2015 11:11:16 -0500
changed the behaviour of init.d scripts to pass through to the associated upstart configuration for process management, where packages ship both an upstart configuration and an init.d configuration.
This has a rather nasty side effect on 'service --status-all', which calls the 'status' method on all installed init.d scripts - this gets translated into:
status <service-name>
for upstart scripts, which correctly identifies the process as not running, but always returns a 0 return code. As a result, --status-all incorrectly identifies upstart processes as running even when they are not.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lsb-base 4.1+Debian11ubuntu6.1
ProcVersionSignature: User Name 3.13.0-86.130-generic 3.13.11-ckt39
Uname: Linux 3.13.0-86-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Tue May 17 16:47:30 2016
Dependencies:
Ec2AMI: ami-0000015b
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small.osci
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
PackageArchitecture: all
SourcePackage: lsb
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2016-05-17 16:53:30 |
James Page |
tags |
amd64 apport-bug ec2-images trusty |
amd64 apport-bug ec2-images regression-update trusty |
|
| 2016-05-17 16:54:35 |
Launchpad Janitor |
lsb (Ubuntu): status |
New |
Confirmed |
|
| 2016-05-17 16:54:38 |
Ryan Beisner |
bug |
|
|
added subscriber Ryan Beisner |
| 2016-05-18 00:09:15 |
Steve Langasek |
lsb (Ubuntu): importance |
Undecided |
High |
|
| 2016-05-18 00:09:15 |
Steve Langasek |
lsb (Ubuntu): status |
Confirmed |
Triaged |
|
| 2016-05-18 00:09:15 |
Steve Langasek |
lsb (Ubuntu): assignee |
|
Steve Langasek (vorlon) |
|
| 2016-05-18 00:09:50 |
Steve Langasek |
lsb (Ubuntu): status |
Triaged |
In Progress |
|
| 2016-05-18 00:09:58 |
Steve Langasek |
nominated for series |
|
Ubuntu Trusty |
|
| 2016-05-18 00:09:58 |
Steve Langasek |
bug task added |
|
lsb (Ubuntu Trusty) |
|
| 2016-05-18 00:37:59 |
Steve Langasek |
lsb (Ubuntu Trusty): importance |
Undecided |
High |
|
| 2016-05-18 00:37:59 |
Steve Langasek |
lsb (Ubuntu Trusty): status |
New |
In Progress |
|
| 2016-05-18 00:37:59 |
Steve Langasek |
lsb (Ubuntu Trusty): assignee |
|
Steve Langasek (vorlon) |
|
| 2016-05-18 00:38:24 |
Steve Langasek |
lsb (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2016-05-18 01:02:16 |
Steve Langasek |
description |
The change to lsb-base that landed into -updates on the 12th of May:
lsb (4.1+Debian11ubuntu6.1) trusty; urgency=medium
* Add 01-upstart-lsb from the upstart package and make
executing rc.d scripts no-op if there is an upstart
job for that script. (LP: #1273462)
-- Zhang Hua <joshua.zhang@canonical.com> Thu, 06 Aug 2015 11:11:16 -0500
changed the behaviour of init.d scripts to pass through to the associated upstart configuration for process management, where packages ship both an upstart configuration and an init.d configuration.
This has a rather nasty side effect on 'service --status-all', which calls the 'status' method on all installed init.d scripts - this gets translated into:
status <service-name>
for upstart scripts, which correctly identifies the process as not running, but always returns a 0 return code. As a result, --status-all incorrectly identifies upstart processes as running even when they are not.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lsb-base 4.1+Debian11ubuntu6.1
ProcVersionSignature: User Name 3.13.0-86.130-generic 3.13.11-ckt39
Uname: Linux 3.13.0-86-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Tue May 17 16:47:30 2016
Dependencies:
Ec2AMI: ami-0000015b
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small.osci
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
PackageArchitecture: all
SourcePackage: lsb
UpgradeStatus: No upgrade log present (probably fresh install) |
[SRU Justification]
SRU regression. The change to lsb-base that landed into -updates on the 12th of May:
lsb (4.1+Debian11ubuntu6.1) trusty; urgency=medium
* Add 01-upstart-lsb from the upstart package and make
executing rc.d scripts no-op if there is an upstart
job for that script. (LP: #1273462)
-- Zhang Hua <joshua.zhang@canonical.com> Thu, 06 Aug 2015 11:11:16 -0500
changed the behaviour of init.d scripts to pass through to the associated upstart configuration for process management, where packages ship both an upstart configuration and an init.d configuration.
This has a rather nasty side effect on 'service --status-all', which calls the 'status' method on all installed init.d scripts - this gets translated into:
status <service-name>
for upstart scripts, which correctly identifies the process as not running, but always returns a 0 return code. As a result, --status-all incorrectly identifies upstart processes as running even when they are not.
[Regression potential]
Minimal. This SRU updates the behavior of the lsb init script upstart diversion to implement LSB-compliant return values for the 'status' subcommand. It is possible this behavior change will differ from the original behavior of some init scripts, but that behavior was undefined.
[Test case]
1. On an installed trusty system, run this command to get a list of affected upstart jobs:
for job in $(initctl list | awk '/stop\/waiting/ { print $1 }'); do if [ -x "/etc/init.d/$job" ]; then echo $job; done
2. Check the status of this service in the output of service --status-all:
service --status-all 2>&1 | grep procps
3. Confirm that the service is shown as running, despite us knowing above that it is not:
[ + ] procps
4. Install the lsb-base package from trusty-proposed.
5. Check the status of this service again in the output of service --status-all:
service --status-all 2>&1 | grep procps
6. Confirm that the service is no longer shown as running:
[ - ] procps |
|
| 2016-05-18 09:37:46 |
Martin Pitt |
lsb (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2016-05-18 09:37:48 |
Martin Pitt |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-05-18 09:37:53 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2016-05-18 09:37:59 |
Martin Pitt |
tags |
amd64 apport-bug ec2-images regression-update trusty |
amd64 apport-bug ec2-images regression-update trusty verification-needed |
|
| 2016-05-19 07:13:25 |
Launchpad Janitor |
lsb (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2016-08-18 19:30:09 |
Ubuntu Foundations Team Bug Bot |
tags |
amd64 apport-bug ec2-images regression-update trusty verification-needed |
amd64 apport-bug ec2-images regression-update removal-candidate trusty verification-needed |
|
| 2016-09-09 01:17:42 |
Mathew Hodson |
tags |
amd64 apport-bug ec2-images regression-update removal-candidate trusty verification-needed |
amd64 apport-bug ec2-images regression-update trusty verification-done |
|
| 2016-09-09 01:37:32 |
Mathew Hodson |
description |
[SRU Justification]
SRU regression. The change to lsb-base that landed into -updates on the 12th of May:
lsb (4.1+Debian11ubuntu6.1) trusty; urgency=medium
* Add 01-upstart-lsb from the upstart package and make
executing rc.d scripts no-op if there is an upstart
job for that script. (LP: #1273462)
-- Zhang Hua <joshua.zhang@canonical.com> Thu, 06 Aug 2015 11:11:16 -0500
changed the behaviour of init.d scripts to pass through to the associated upstart configuration for process management, where packages ship both an upstart configuration and an init.d configuration.
This has a rather nasty side effect on 'service --status-all', which calls the 'status' method on all installed init.d scripts - this gets translated into:
status <service-name>
for upstart scripts, which correctly identifies the process as not running, but always returns a 0 return code. As a result, --status-all incorrectly identifies upstart processes as running even when they are not.
[Regression potential]
Minimal. This SRU updates the behavior of the lsb init script upstart diversion to implement LSB-compliant return values for the 'status' subcommand. It is possible this behavior change will differ from the original behavior of some init scripts, but that behavior was undefined.
[Test case]
1. On an installed trusty system, run this command to get a list of affected upstart jobs:
for job in $(initctl list | awk '/stop\/waiting/ { print $1 }'); do if [ -x "/etc/init.d/$job" ]; then echo $job; done
2. Check the status of this service in the output of service --status-all:
service --status-all 2>&1 | grep procps
3. Confirm that the service is shown as running, despite us knowing above that it is not:
[ + ] procps
4. Install the lsb-base package from trusty-proposed.
5. Check the status of this service again in the output of service --status-all:
service --status-all 2>&1 | grep procps
6. Confirm that the service is no longer shown as running:
[ - ] procps |
[Impact]
This is a regression caused by the change to lsb-base that landed in -updates on the 12th of May:
lsb (4.1+Debian11ubuntu6.1) trusty; urgency=medium
* Add 01-upstart-lsb from the upstart package and make
executing rc.d scripts no-op if there is an upstart
job for that script. (LP: #1273462)
-- Zhang Hua <joshua.zhang@canonical.com> Thu, 06 Aug 2015 11:11:16 -0500
This changed the behaviour of init.d scripts to pass through to the associated upstart configuration for process management, where packages ship both an upstart configuration and an init.d configuration.
This has a rather nasty side effect on 'service --status-all', which calls the 'status' method on all installed init.d scripts - this gets translated into:
status <service-name>
for upstart scripts, which correctly identifies the process as not running, but always returns a 0 return code. As a result, --status-all incorrectly identifies upstart processes as running even when they are not.
[Test Case]
1. On an installed trusty system, run this command to get a list of affected upstart jobs:
for job in $(initctl --system list | awk '/stop\/waiting/ {print $1}'); do if [ -x "/etc/init.d/$job" ]; then echo $job; fi; done
2. Check the status of this service in the output of service --status-all:
service --status-all 2>&1 | grep procps
3. Confirm that the service is shown as running, despite us knowing above that it is not:
[ + ] procps
4. Install the lsb-base package from trusty-proposed.
5. Check the status of this service again in the output of service --status-all:
service --status-all 2>&1 | grep procps
6. Confirm that the service is no longer shown as running:
[ - ] procps
[Regression Potential]
Minimal. This SRU updates the behavior of the lsb init script upstart diversion to implement LSB-compliant return values for the 'status' subcommand. It is possible this behavior change will differ from the original behavior of some init scripts, but that behavior was undefined. |
|
| 2016-09-13 06:38:34 |
Launchpad Janitor |
lsb (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2016-09-13 06:38:42 |
Martin Pitt |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
