Bug 619387

Summary:	service pand is not lsb compatible
Product:	Red Hat Enterprise Linux 6	Reporter:	Lubos Kocman <lkocman>
Component:	bluez	Assignee:	Bastien Nocera <bnocera>
Status:	CLOSED WONTFIX	QA Contact:	Ken Benoit <kbenoit>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.0	CC:	benl
Target Milestone:	rc	Keywords:	RHELNAK
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-06 11:53:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	633349

Description Lubos Kocman 2010-07-29 12:53:22 UTC

Description of problem:

service pand does not behave as expected according to LSB compatibility

see http://intranet.corp.redhat.com/ic/intranet/InitscriptsSpec.html for more information.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
 

1. touch /var/lock/subsys/pand
2. /etc/init.d/pand stop
Shutting down pand:                                        [FAILED]
3. /etc/init.d/pand status


Actual results: 0
Expected results: 3

Additional info:

$PANDARGS is not set

Comment 1 Lubos Kocman 2010-07-29 12:55:14 UTC

bluez-compat-4.66-1.el6.x86_64
bluez-4.66-1.el6.x86_64
bluez-libs-4.66-1.el6.x86_64

Comment 3 RHEL Program Management 2010-07-29 13:27:41 UTC

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 4 RHEL Program Management 2011-01-07 16:06:24 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 5 RHEL Program Management 2012-09-21 16:03:38 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 6 RHEL Program Management 2013-10-14 01:17:57 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 7 Jan Kurik 2017-12-06 11:53:59 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/