Bug 705236 - "rm: cannot remove `/var/run/subsys/rhsm': Is a directory" message during system boot for RHEL5.7
Summary: "rm: cannot remove `/var/run/subsys/rhsm': Is a directory" message during sys...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: subscription-manager
Version: 5.7
Hardware: ppc64
OS: All
unspecified
medium
Target Milestone: rc
: ---
Assignee: Chris Duryee
QA Contact:
URL:
Whiteboard:
: 705730 711826 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-17 05:30 UTC by IBM Bug Proxy
Modified: 2011-07-21 12:30 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-21 08:45:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
initscript patch (414 bytes, text/plain)
2011-05-17 05:30 UTC, IBM Bug Proxy
no flags Details
Corrected patch (458 bytes, text/plain)
2011-05-18 07:50 UTC, IBM Bug Proxy
no flags Details


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 71998 0 None None None Never
Red Hat Product Errata RHEA-2011:1078 0 normal SHIPPED_LIVE new package: subscription-manager 2011-07-21 08:45:07 UTC

Description IBM Bug Proxy 2011-05-17 05:30:27 UTC
== Comment: #0 - SUBRATA MODAK <Subrata Modak <subrata.ibm.com>> - 2011.05.10 05:51:37 ==
---Problem Description---
This message is consistently produced during every system boot of RHEL5.7-Alpha:
                  "rm: cannot remove `/var/run/subsys/rhsm': Is a directory"

The sequence is:
"
...
Remounting root filesystem in read-write mode:  [  OK  ]
Mounting local filesystems:  [  OK  ]
Enabling local filesystem quotas:  [  OK  ]
rm: cannot remove `/var/run/subsys/rhsm': Is a directory
Enabling /etc/fstab swaps:  [  OK  ]
...
"

Regards--
Subrata
 
 
---uname output---
Linux 2.6.18-259.el5 #1 SMP Fri Apr 29 01:11:49 EDT 2011 ppc64 ppc64 ppc64 GNU/Linux
 
Machine Type = 8231-E2C-10708FP 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
Mentioned Above
 
---Installation and Packaging Component Data--- 
Install disk info: N/A
 
Install method: NIM
 
Install ISO Information: RHEL5.7-Server-20110430.2-ppc-DVD.iso
 
Userspace tool common name: File System Quota 
 
The userspace tool has the following bit modes: N/A 

Userspace rpm: N/A 

Userspace tool obtained from project website:  na 
 

== Comment: #2 - ARUNA H. BALAKRISHNAIAH <arunabal.com> - 2011.05.16 11:54:50 ==

initscript patch

Hi Subrata,

Please test with the patch and share the results.

rpm -qf /etc/rc.d/rc.sysinit
initscripts-8.45.35-2.el5

Thanks,
Aruna.

== Comment: #3 - ARUNA H. BALAKRISHNAIAH <arunabal.com> - 2011.05.17 01:24:45 ==
Hi Subrata, 

I rebooted the machine with the patch , i couldnt find the error messages.

Remounting root filesystem in read-write mode:  [  OK  ]
Mounting local filesystems:  [  OK  ]
Enabling local filesystem quotas:  [  OK  ]
Enabling /etc/fstab swaps:  [  OK  ]

Thanks,
Aruna.

Comment 1 IBM Bug Proxy 2011-05-17 05:30:32 UTC
Created attachment 499271 [details]
initscript patch

Comment 2 IBM Bug Proxy 2011-05-17 09:10:25 UTC
------- Comment From Subrata Modak subrata.ibm.com 2011-05-17 05:01 EDT-------
Hi Aruna,

This solves the issue. Thanks for the Patch.

RH,

The proposed patch solves the problem. Can you please include this patch inside RHEL5.7 ?

Comment 3 Chris Lumens 2011-05-17 12:50:42 UTC
This has nothing to do with anaconda.  The fact that there's even a patch to an initscript is a pretty good indicator of that.

Comment 4 IBM Bug Proxy 2011-05-17 14:00:25 UTC
------- Comment From Subrata Modak subrata.ibm.com 2011-05-17 09:57 EDT-------
Correct,

So, can you please let us know whether this patch is being looked to be included soon in RHEl5.7 ?

Regards--
Subrata

Comment 5 Bill Nottingham 2011-05-17 18:18:31 UTC
That patch is very very wrong.

You want to add a special case for rhsm like the other special cases, not blindly remove everything.

Although /var/run/subsys/rhsm is a pretty bizarre directory. What's it putting there, and what's the lifecycle for that data?

Comment 6 RHEL Program Management 2011-05-17 18:19:08 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 7 IBM Bug Proxy 2011-05-18 05:40:26 UTC
------- Comment From Subrata Modak subrata.ibm.com 2011-05-18 01:39 EDT-------
(In reply to comment #10)
> That patch is very very wrong.
>
> You want to add a special case for rhsm like the other special cases, not
> blindly remove everything.
>
> Although /var/run/subsys/rhsm is a pretty bizarre directory. What's it putting
> there, and what's the lifecycle for that data?

We would request you to kindly provide a solution. Since this directory is containing nothing and the intention of the script is to remove the directory (which will never occur with 'rm -f'), we found this to be the optimum solution. Let us know how would you like to solve this ?

Regards--
Subrata

>
> This request was evaluated by Red Hat Product Management for inclusion in a Red
> Hat Enterprise Linux maintenance release.  Product Management has requested
> further review of this request by Red Hat Engineering, for potential
> inclusion in a Red Hat Enterprise Linux Update release for currently deployed
> products.  This request is not yet committed for inclusion in an Update
> release.

Comment 8 IBM Bug Proxy 2011-05-18 07:50:32 UTC
Created attachment 499535 [details]
Corrected patch


------- Comment on attachment From arunabal.com 2011-05-18 03:42 EDT-------


Have included a special case to check for rhsm, since it couldnt be included directly , because afile = /var/run/*, it could match only 1 directory below it, so its checked for subsys and there its checked for rhsm.

Thanks,
Aruna,

Comment 9 Bill Nottingham 2011-05-18 16:33:22 UTC
*** Bug 705730 has been marked as a duplicate of this bug. ***

Comment 10 IBM Bug Proxy 2011-05-24 18:20:39 UTC
------- Comment From shubgoya.com 2011-05-24 14:19 EDT-------
I checked on couple of system X platforms and the message mentioned in bug description was appearing consistently during system boot of RHEL5.7Alpha. So this issue is reproducible in x systems too.

Comment 13 Bill Nottingham 2011-06-01 19:41:59 UTC
This patch still looks very wrong. WTF is rhsm doing with that directory?

Comment 14 Bill Nottingham 2011-06-01 19:44:03 UTC
To be more explicit:

- /var/run/subsys isn't a defined directory used by anything else
- why is rhsm using that?
- what is it putting there?

I shouldn't have ACKed this; it's not entirely clear that this is an initscripts bug.

Comment 15 IBM Bug Proxy 2011-06-02 05:40:32 UTC
------- Comment From arunabal.com 2011-06-02 01:30 EDT-------
Can you please suggest the patch ?

Comment 16 Bill Nottingham 2011-06-02 15:37:32 UTC
This shouldn't be fixed in intiscripts at all. Harald, can we revert this patch?

This is a bug in subscription manager:

/usr/share/rhsm/subscription_manager/certlib.py:

class ActionLock(Lock):

    PATH = '/var/run/subsys/rhsm/cert.pid'

That should almost certainly be /var/run/rhsm/cert.pid - /var/run/rhsm is the directory that the package installs, for example.

Comment 17 Chris Duryee 2011-06-03 14:06:20 UTC
Fixed on RHEL5.7 branch in 4c2b38d6e4c560b33fa6cfc5e626eae42fad4658, version 0.95.5.21

Comment 18 Chris Duryee 2011-06-03 14:07:12 UTC
Fixed on master branch in 025de56c3f0192280560084c88660cad9b2ef788, version 0.96.2

Comment 19 J.C. Molet 2011-06-03 18:24:31 UTC
tested on subscription-manager-firstboot-0.95.5.20-1.git.5.4445aa4.el5

in cirtlib.py, the path has been changed to:
PATH = '/var/run/rhsm/cert.pid'

as suggested.

upon rebooting the machine, no error messages were found.  Fixes should appear in 0.95.5.21 release.  Marking VERIFIED.

Comment 20 Petr Lautrbach 2011-06-07 22:23:04 UTC
Since this is fixed in subscription-manager I've reverted patch in initscripts

Comment 21 IBM Bug Proxy 2011-06-08 06:30:40 UTC
------- Comment From Subrata Modak subrata.ibm.com 2011-06-08 02:25 EDT-------
Thanks. Will test on SNAP1 and post results soon.

Regards--
Subrata

Comment 22 Phil Knirsch 2011-06-08 16:28:34 UTC
*** Bug 711826 has been marked as a duplicate of this bug. ***

Comment 23 IBM Bug Proxy 2011-06-09 11:30:37 UTC
------- Comment From Subrata Modak subrata.ibm.com 2011-06-09 07:25 EDT-------
Hello RH,

This is fixed in SS*2 release of RHEL5.7. Thanks very much.

Regards--
Subrata

Comment 24 Harald Hoyer 2011-06-16 16:02:59 UTC
(In reply to comment #16)
> This shouldn't be fixed in intiscripts at all. Harald, can we revert this
> patch?
> 
> This is a bug in subscription manager:
> 
> /usr/share/rhsm/subscription_manager/certlib.py:
> 
> class ActionLock(Lock):
> 
>     PATH = '/var/run/subsys/rhsm/cert.pid'
> 
> That should almost certainly be /var/run/rhsm/cert.pid - /var/run/rhsm is the
> directory that the package installs, for example.

ah, tomatoes on my eyes... didn't see "subsys", my brain also thought of "/var/run/rhsm"

Comment 25 errata-xmlrpc 2011-07-21 08:45:56 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-1078.html

Comment 26 errata-xmlrpc 2011-07-21 12:30:35 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-1078.html


Note You need to log in before you can comment on or make changes to this bug.