+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1431188 +++ ====================================================================== Description of problem: Version-Release number of selected component (if applicable): RHEVM 4.0.6.3-0.1.el7 RHEL-H 7.3 on 3.6 How reproducible: - Add the repositories in the hypervisor for 4.0 upgrade - Click Upgrade button in the Engine - Hosts will be unavailable, lost network and had to redeploy (Originally by dougsland)
Douglas, could you please provide both engine and VDSM logs? (Originally by Martin Perina)
Adrian, Douglas, could you attach sosreport from the host *prior* to the redeployment? This bug should be dedicated to the first failed upgrade. comment 5 analyses another problem with the redeployed host. (Originally by danken)
This probably shares an underlying reason with bug 1431228: ActivateVdsCommand takes unbearably long time to finish. (Originally by danken)
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [FOUND CLONE FLAGS: ['rhevm-4.1.z', 'rhevm-4.2-ga'], ] For more info please contact: rhv-devops (Originally by rhev-integ)
Hi Douglas, - Add the repositories in the hypervisor for 4.0 upgrade - Click Upgrade button in the Engine If i understand it correctly, the rhv-3.6 you used is the old node rhv-h and not ngn rhv-h 3.6, correct? As the ngn rhv-h 3.6 don't invoke the 'Upgrade' button in the engine, only old node rhv-h. The new ngn 3.6 rhv-h is updated when adding new repos to the host, then rebooting it from the new OS and host is up in the engine(without the upgrade button). Dan, BTW, i'm not even sure how this can be tested on 4.1.2(as the original report is for engine 4.0.6 and this is targeted for 4.1.2). Problem is that you can't add rhv-h 3.6 or rhv-4.0 to engine 4.1.2, even it's for clusters 3.6 and 4.0. not sure how this report should be tested. Another thing, this bug targeted to 4.1.2, but still on modified.
This bug should better be added manually to the engine 4.1.2 erratum (I've ask Dusan to do so). It is about performance so it does not really matter which rhv-h-ngn you are adding; try rhv-h-ngn-4.1.2.
Hi Michael, (In reply to Michael Burman from comment #15) > Hi Douglas, > > > - Add the repositories in the hypervisor for 4.0 upgrade > - Click Upgrade button in the Engine > > If i understand it correctly, the rhv-3.6 you used is the old node rhv-h and > not ngn rhv-h 3.6, correct? Adrian's (adumitru) environment was RHEL-H 3.6 not RHEV-H. > > As the ngn rhv-h 3.6 don't invoke the 'Upgrade' button in the engine, only > old node rhv-h. > The new ngn 3.6 rhv-h is updated when adding new repos to the host, then > rebooting it from the new OS and host is up in the engine(without the > upgrade button). > > Dan, > > BTW, i'm not even sure how this can be tested on 4.1.2(as the original > report is for engine 4.0.6 and this is targeted for 4.1.2). > > Problem is that you can't add rhv-h 3.6 or rhv-4.0 to engine 4.1.2, even > it's for clusters 3.6 and 4.0. not sure how this report should be tested. > > Another thing, this bug targeted to 4.1.2, but still on modified.
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [NO RELEVANT PATCHES FOUND] For more info please contact: rhv-devops
All relevant patches are reported on BZ#1431228, which this patch is depends on transitively.
Verified on - 4.1.2.1-0.1.el7
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://access.redhat.com/errata/RHEA-2017:1281