RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 980558 - After upgrading RHEV-H, the host system fails to boot
Summary: After upgrading RHEV-H, the host system fails to boot
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-02 17:24 UTC by Anitha Udgiri
Modified: 2018-12-03 19:15 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-19 16:12:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 144813 0 None None None Never

Description Anitha Udgiri 2013-07-02 17:24:59 UTC 
Description of problem:
 When trying to upgrade the host from RHEV Hypervisor - 6.3 - 20121212.0.el6_3 to RHEV Hypervisor - 6.4 - 20130528.0.el6_4, the hypervisor gets stuck during the start of system services.

Here is the screen shot content of the errors:
##########################

Welcome to Red Hat Enterprise Virtualization Hypervisor

Starting udev: [ OK ] 

Setting hostname localhost.localdomain: [ OK ]

Setting up Logical Volume Management: 4 logical volume(s) in volume group "HostVG" now active

44 logical volume(s) in volume group "565fac5d-393b-4bcc-8208-0290fac7d22a" now active [ OK ]

cp: '/var/lib/vdsm/' and '/var/lib/stateless/writable/var/lib/vdsm' are the same file 

Mounting local filesystems: [ OK ]

chown: invalid user: 'root:root'

Enabling /etc/fstab swaps [ OK ]

telinit: Did not receive a reply. Possible causes include the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. 

init: rcS post-stop process (2070) terminated with status 1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Version-Release number of selected component (if applicable):
The user is using RHEV-M 3.2 and has used the GUI to upgrade the hypervisor


How reproducible:
Not sure

Additional Information:
~~~~~~~~~~~~~~~~~~~~~~~
THe user is unable to login to the hypervisor even in rescue mode to check on the contents of logs.
Comment 1 Longjun Song 2013-07-22 10:25:49 UTC 
Step 1. Install the RHEV Hypervisor-6.3-20121212.0.el6_3 integritedly.

Step 2. Upgrade the host to RHEV Hypervisor-6.4-20130528.0.el6_4 from RHEVM 3.2(sf18)

Result: There is no this issue when the installation is integreted.

BUT After deleting the data of root in file '/etc/passwd' manaully and reboot, the problem will occur. This operation is done by myself but I don't know how to reproduce it by program. Please attach the detail steps, log files and /etc/passwd for analysis.
Comment 2 Lei Wang 2013-08-02 06:18:40 UTC 
Hello Anitha, 

As mentioned in comment1, QE are not sure the correct way to reproduce this bug, though seems via removing root related data in /etc/passwd could trigger this issue. 

Would you please provide more detailed steps and logs, /etc/passwd etc for reproducing and analyzing this issue? Is it 100% reproducible or just happen under specific situation?

Thanks!
Comment 3 Anitha Udgiri 2013-08-02 16:18:10 UTC 
Hello Lei Wang,
     Unfortunately, we don't have additional information to proceed further here. Customer reinstalled to get back into production.
Acording to them, they did not do anything else other than upgrade the host via RHEV-M.
We also could not get any sosreport info from the host as they were unable to access the system even in rescue mode.
Under these circumstances, it may be a good idea to close this BZ.
Comment 6 Mike Burns 2013-09-19 16:12:36 UTC 
Closing since we don't have enough to debug the issue and can't reproduce.  Please re-open if more information surfaces.
Comment 9 Mark Huth 2013-12-11 05:42:37 UTC 
Actually I forget to mention that this customer was also upgrading their hypervisor too, which certainly matches the error scenario in comment #0.
Note You need to log in before you can comment on or make changes to this bug.