Bug 1321054 - vdsm-tool configure --force on rhel-7.2 mess up /boot
Summary: vdsm-tool configure --force on rhel-7.2 mess up /boot
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: vdsm
Classification: oVirt
Component: General
Version: 4.17.23
Hardware: x86_64
OS: Linux
unspecified
unspecified vote
Target Milestone: ---
: ---
Assignee: Yaniv Bronhaim
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-24 14:41 UTC by Ido Rosenzwig
Modified: 2016-06-02 11:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-11 12:11:54 UTC
oVirt Team: Infra
irosenzw: needinfo-
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)
boot description (46.58 KB, image/png)
2016-03-24 14:41 UTC, Ido Rosenzwig 		no flags Details
logs (469.68 KB, application/x-gzip)
2016-03-29 14:22 UTC, Ido Rosenzwig 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Ido Rosenzwig 2016-03-24 14:41:29 UTC 
Created attachment 1140001 [details]
boot description

Description of problem:
when installing HE on rhel-7.2:
after running vdsm-tool configure --force and then reboot,
the machine boot into maintenance mode. 


Steps to Reproduce:
1.install rhel 7.2
2.subscribe and add the channel "rhel-7-server-rhev-mgmt-agent-rpms"
3.install ovirt-hosted-engine-setup
4.yum update
(it is recommended to create a snapshot at this point)
5.vdsm-tool configure --force 
6.reboot
Comment 1 Dan Kenigsberg 2016-03-27 09:03:03 UTC 
In the attached image one can see the signs of a corrupted filesystem. I doubt that this has much to do with vdsm-tool configure (and certainly nothing with network), but it's bad enough to merit more researching.

Please attach all possibly-relevant logs from the corrupted guess (prior to its reboot).
Comment 2 Ido Rosenzwig 2016-03-29 14:22:56 UTC 
Created attachment 1141283 [details]
logs
Comment 3 Yaniv Bronhaim 2016-03-30 07:37:46 UTC 
I see in syslog that configure fails again and again with "Mar 29 09:46:02 he-host2 sasldblistusers2: _sasldb_getkeyhandle has failed" - so it can't check that the sasl user is set correctly. If you can reproduce it - check why "sasldblistusers2" fails to run. maybe "/etc/libvirt/passwd.db" is not accessible?
Comment 4 Yaniv Bronhaim 2016-04-03 13:24:29 UTC 
I suspect it relates to the image you use. I can't reproduce it and I need more info
Note You need to log in before you can comment on or make changes to this bug.