+++ This bug is an upstream to downstream clone. The original bug is: +++ +++ bug 1643733 +++ ====================================================================== Description of problem: ----------------------- After upgrading from RHV 4.1.11, the new virt options are not available in virt profile ( /var/lib/glusterd/groups/virt ) Version-Release number of selected component (if applicable): -------------------------------------------------------------- RHVH 4.1.11 RHVH 4.2.7 How reproducible: ------------------ 6/6 Steps to Reproduce: ------------------- 1. Install RHVH 4.1.11 2. Check for the contents of virt profile 3. Update to the latest RHVH 4.2.7 4. Check for the contents of virt profile Actual results: --------------- New virt profile still points to the old content Expected results: ------------------ New virt profile should have the new content Additional info: (Originally by Satheesaran Sundaramoorthi)
QE can reproduce this issue. Test version: # imgbase layout rhvh-4.1-0.20180425.0 +- rhvh-4.1-0.20180425.0+1 rhvh-4.2.7.3-0.20181026.0 +- rhvh-4.2.7.3-0.20181026.0+1 Test steps: 1. Install redhat-virtualization-host-4.1-20180426.0 2. Check for the contents of virt profile /var/lib/glusterd/groups/virt 3. Upgrade rhvh to 4.2.7 rhvh-4.2.7.3-0.20181026.0 4. Check for the contents of virt profile /var/lib/glusterd/groups/virt 5. Clean install rhvh-4.2.7.3-0.20181026.0 6. Check for the contents of virt profile /var/lib/glusterd/groups/virt Test results: 1. After step 4, the contents of virt profile is same as step 2: # cat /var/lib/glusterd/groups/virt performance.quick-read=off performance.read-ahead=off performance.io-cache=off performance.low-prio-threads=32 network.remote-dio=enable cluster.eager-lock=enable cluster.quorum-type=auto cluster.server-quorum-type=server cluster.data-self-heal-algorithm=full cluster.locking-scheme=granular cluster.shd-max-threads=8 cluster.shd-wait-qlength=10000 features.shard=on user.cifs=off 2. After step 6, the contents of virt profile is not same as step 4: # cat /var/lib/glusterd/groups/virt performance.quick-read=off performance.read-ahead=off performance.io-cache=off performance.low-prio-threads=32 network.remote-dio=enable cluster.eager-lock=enable cluster.quorum-type=auto cluster.server-quorum-type=server cluster.data-self-heal-algorithm=full cluster.locking-scheme=granular cluster.shd-max-threads=8 cluster.shd-wait-qlength=10000 features.shard=on user.cifs=off cluster.choose-local=off client.event-threads=4 server.event-threads=4 performance.client-io-threads=on (Originally by Huijuan Zhao)
This bug is fixed in redhat-virtualization-host-4.2-20181128.0 Test version: # imgbase layout rhvh-4.1-0.20180425.0 +- rhvh-4.1-0.20180425.0+1 rhvh-4.2.8.0-0.20181127.0 +- rhvh-4.2.8.0-0.20181127.0+1 Test steps: Same as comment 1 Test results: 1. After step4, the contents of virt profile is different as step 2 2. After step6, the contents of virt profile is same as step 4 So new virt profile has the new content. So this bug is fixed in rhvh-4.2.8.0-0.20181127.0, will verify this bug once the status move to ON_QA.
4.3 is handled in https://bugzilla.redhat.com/show_bug.cgi?id=1643733
According to comment 3, move to VERIFIED.
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/RHBA-2019:0116