Bug 1429594
| Summary: | [downstream clone - 4.0.7] RHVH 4.0.7 cannot be up again in the side of RHEVM 4.0 after upgrade | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | rhev-hypervisor-ng | Assignee: | Yuval Turgeman <yturgema> |
| Status: | CLOSED ERRATA | QA Contact: | jianwu <jiawu> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.0.7 | CC: | bugs, cshao, dfediuck, dguo, gklein, jiawu, leiwang, lsurette, mgoldboi, rbalakri, rbarry, Rhev-m-bugs, srevivo, weiwang, yaniwang, ycui, ykaul, ylavi, yzhao |
| Target Milestone: | ovirt-4.0.7 | Keywords: | Regression, TestBlocker, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
vdsm is not configured after an upgrade of RHVH
Consequence:
RHVH is not brought up
Fix:
Running vdsm-tool configure --force on boot sets up the different vdsm modules
Result:
vdsm is configured and RHVH is up
|
Story Points: | --- |
| Clone Of: | 1429288 | Environment: | |
| Last Closed: | 2017-03-16 15:40:34 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1429288 | ||
| Bug Blocks: | |||
|
Description
rhev-integ
2017-03-06 16:31:44 UTC
Created attachment 1260243 [details]
related picture about this issue
(Originally by Jian Wu)
Created attachment 1260244 [details]
another picture about vdsmd.service
(Originally by Jian Wu)
This bug blocks upgrade test in RHEVM side, and the same issue happens via "yum update" way ,so I could not check status in rhevm side and related test. (Originally by Jian Wu) Can you please provide journalctl output? (Originally by Ryan Barry) Created attachment 1260262 [details]
journalctl output
(Originally by Jian Wu)
(In reply to Ryan Barry from comment #4) > Can you please provide journalctl output? Hi, I have upload attachment 1260262 [details] for journalcl output, please check it Thanks (Originally by Jian Wu) Thanks jianwu.
I'm not sure this is unexpected behavior, though it's not nice.
We've carefully avoided adding a 'vdsm-tool configure --force' as part of NGN booting (which vintage RHV-H had).
The version of RHV-H used for upgrading was particularly old, but I'm not sure how vdsm handles this behind the scenes.
The version of lvmlocal.conf from the old version did not have the necessary configuration. In fact, it appears to have matched the installed version exactly:
# mount
/dev/mapper/rhvh_dhcp--10--229-rhvh--4.0--0.20160919.0+1 on /tmp/a type xfs (rw,relatime,seclabel,attr2,inode64,logbsize=256k,sunit=512,swidth=512,noquota)
# diff -u /tmp/a/etc/lvm/lvmlocal.conf /tmp/a/usr/share/factory/etc/lvm/lvmlocal.conf
In this case, we took the lvmlocal.conf from the new image, but this is also not what vdsm expects. Differences between /etc/lvm/lvmlocal.conf before and after "vdsm-tool configure --force" are significant.
I don't see anything in the relevant topic branch which looks like vdsm should keep/handle this on upgrades either. I'm not very familiar with how vdsm handles upgrades, though.
A quick glance at the specfile show:
if ! %{_bindir}/vdsm-tool is-configured >/dev/null 2>&1; then
%{_bindir}/vdsm-tool configure --force >/dev/null 2>&1
fi
I'd like to match this if possible.
Yuvalt:
Can you please add a method in plugins/osupdater which matches this?
(Originally by Ryan Barry)
Hi, I have test this bug on redhat-virtualization-host-4.0-20170307.1.x86_64 Test version: Before upgrade: rhvh-4.0-0.20160919.1 After upgrade: redhat-virtualization-host-4.0-20170307.1.x86_64(new build) imgbased-0.8.16-0.1.el7ev.noarch kernel-3.10.0-514.10.2.el7.x86_64 Test results: Vdsmd.service works well and New RHVH could be up in rhevm side SO I think this bug is fixed in this build. Verify this bug according #c10 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2017-0549.html |