Bug 881891
Summary: | Unclear description of next steps after upgrade procure from RHEVM 3.0 to 3.1 environment with hosts which have same UUID | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | vvyazmin <vvyazmin> |
Component: | ovirt-engine-setup | Assignee: | Barak <bazulay> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavel Stehlik <pstehlik> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.1.0 | CC: | bazulay, cnegus, dyasny, hateya, iheim, mgoldboi, Rhev-m-bugs, sgrinber, ykaul |
Target Milestone: | --- | ||
Target Release: | 3.1.2 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | integration infra | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-12-24 09:25:05 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
vvyazmin@redhat.com
2012-11-29 18:23:04 UTC
Probably best to refer to a KB changed to Infra (In reply to comment #0) [ DONE ] > > RHEV Manager upgrade completed successfully! > > * NOTICE: > > The following hosts must be reinstalled. If reason is BIOS > duplicate UUID execute the following command on each host before > reinstallation: > # uuidgen > /etc/vdsm/vdsm.id > If you are running rhev-h or ovirt-node, restart vdsm-reg service: > # service vdsm-reg restart > > - Host cougar08(cougar08.scl.lab.tlv.redhat.com), reason: duplicate BIOS > UUID > - Host cougar05(cougar05.scl.lab.tlv.redhat.com), reason: duplicate BIOS > UUID > . What is not clear with the above explanation ? > * Upgrade log available at > /var/log/ovirt-engine/ovirt-engine-upgrade_2012_11_28_14_45_56.log > * DB Backup available at > /var/lib/ovirt-engine/backups/ovirt-engine_db_backup_2012_11_28_14_46_02.sql > > > > > In description, my next steps, should mention: > Before Activate Those hosts: > 1. Upgrade those hosts to latest (stable) OS version > 2. Upgrade / Reinstall VDSM version The above section has no relevance the only steps required in those rare occasions is to run the exact commands listed in the message above (In reply to comment #4) > > (In reply to comment #0) > [ DONE ] > > > > RHEV Manager upgrade completed successfully! > > > > * NOTICE: > > > > The following hosts must be reinstalled. If reason is BIOS > > duplicate UUID execute the following command on each host before > > reinstallation: > > # uuidgen > /etc/vdsm/vdsm.id > > If you are running rhev-h or ovirt-node, restart vdsm-reg service: > > # service vdsm-reg restart > > > > - Host cougar08(cougar08.scl.lab.tlv.redhat.com), reason: duplicate BIOS > > UUID > > - Host cougar05(cougar05.scl.lab.tlv.redhat.com), reason: duplicate BIOS > > UUID > > . > > What is not clear with the above explanation ? > > > > > * Upgrade log available at > > /var/log/ovirt-engine/ovirt-engine-upgrade_2012_11_28_14_45_56.log > > * DB Backup available at > > /var/lib/ovirt-engine/backups/ovirt-engine_db_backup_2012_11_28_14_46_02.sql > > > > > > > > > > In description, my next steps, should mention: > > Before Activate Those hosts: > > 1. Upgrade those hosts to latest (stable) OS version > > 2. Upgrade / Reinstall VDSM version > > The above section has no relevance the only steps required in those rare > occasions is to run the exact commands listed in the message above I expect that, in the end installation, end user will know that, he need manually upgrade his VDSM on all relevant hosts, and upgrade OS on his hosts. Without this you can't use your hosts in 3.1 environment. (In reply to comment #6) > I expect that, in the end installation, end user will know that, he need > manually upgrade his VDSM on all relevant hosts, and upgrade OS on his > hosts. Without this you can't use your hosts in 3.1 environment. It's a bit more complicated then that: For RHEL host, upgrade is automatically triggered by the re-install link. For RHEV-H he cant just upgrade the VDSM he must upgrade the host. Barak let's leave it as is and move the solution to kbase 269333 Let's not forget that now the upgrade script and documentation refers to this kbase: https://access.redhat.com/knowledge/articles/269333 Chris, could you please take care of that. When done please let me know and I'll close this bug. Please contact Barak if something is unclear. I added this information to the article (https://access.redhat.com/knowledge/node/269333). Please let me know if I need to change anything in the wording. |