Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1605076 - [downstream clone - 4.2.5] Config values inconsistency between RHV versions
[downstream clone - 4.2.5] Config values inconsistency between RHV versions
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
unspecified
Unspecified Unspecified
high Severity high
: ovirt-4.2.5
: ---
Assigned To: Eli Mesika
Lucie Leistnerova
: ZStream
Depends On: 1599321
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-20 02:38 EDT by RHV Bugzilla Automation and Verification Bot
Modified: 2018-07-31 13:50 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Release Note
Doc Text:
There were inconsistencies in the following internal configuration options: * HotPlugCpuSupported * HotUnplugCpuSupported * HotPlugMemorySupported * HotUnplugMemorySupported * IsMigrationSupported * IsMemorySnapshotSupported * IsSuspendSupported * ClusterRequiredRngSourcesDefault If you are having issues with these features, upgrade to Red Hat Virtualization 4.2.5+ to resolve the problem.
Story Points: ---
Clone Of: 1599321
Environment:
Last Closed: 2018-07-31 13:49:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 92968 master MERGED db: fixing config values 2018-07-20 02:39 EDT
oVirt gerrit 92969 ovirt-engine-4.2 MERGED db: fixing config values 2018-07-20 02:39 EDT
Red Hat Product Errata RHBA-2018:2318 None None None 2018-07-31 13:50 EDT

  None (edit)
Description RHV Bugzilla Automation and Verification Bot 2018-07-20 02:38:32 EDT
+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1599321 +++
======================================================================

Description of problem:

There's an inconsistency of HotUnplugMemorySupported value in 4.1 clusters between RHV versions:

1. Clean RHV 4.1 installation

      option_name        |         option_value          | version 
-------------------------+------------------------------+---------
HotUnplugMemorySupported | {"x86":"false","ppc":"false"} | 3.6
HotUnplugMemorySupported | {"x86":"false","ppc":"false"} | 4.0
HotUnplugMemorySupported | {"x86":"false","ppc":"false"} | 4.1


2. RHV 4.2 upgraded from RHV 4.1

      option_name        |                option_value                 | version 
-------------------------+---------------------------------------------+---------
HotUnplugMemorySupported | {"x86":"false","ppc":"false"}               | 3.6
HotUnplugMemorySupported | {"x86":"false","ppc":"false"}               | 4.0
HotUnplugMemorySupported | {"x86":"false","ppc":"false"}               | 4.1
HotUnplugMemorySupported | {"x86":"true","ppc":"true","s390x":"false"} | 4.2



3. Clean RHV 4.2 installation

      option_name        |                option_value                 | version 
-------------------------+---------------------------------------------+---------
HotUnplugMemorySupported | {"x86":"false","ppc":"false"}               | 3.6
HotUnplugMemorySupported | {"x86":"false","ppc":"false"}               | 4.0
HotUnplugMemorySupported | {"x86":"true","ppc":"false"}                | 4.1
HotUnplugMemorySupported | {"x86":"true","ppc":"true","s390x":"false"} | 4.2

(Originally by Martin Perina)
Comment 1 RHV Bugzilla Automation and Verification Bot 2018-07-20 02:38:39 EDT
Michale, so what's the correct value for HotUnplugMemorySupported for 4.1 clusters?

(Originally by Martin Perina)
Comment 3 RHV Bugzilla Automation and Verification Bot 2018-07-20 02:38:45 EDT
Supported in 4.1 for x86_64
Not supported for ppc64le until 4.2

It was probably broken quite early in 4.1 already without people noticing

(Originally by michal.skrivanek)
Comment 4 RHV Bugzilla Automation and Verification Bot 2018-07-20 02:38:49 EDT
Workaround for existing 4.1/4.2 customers:

1. Login to RHV manager host as root

2. Execute following commands:

   . /etc/ovirt-engine/engine.conf.d/10-setup-database.conf

   PGPASSWORD="$ENGINE_DB_PASSWORD" psql -h "${ENGINE_DB_HOST}" \
       -d "${ENGINE_DB_DATABASE}" -U "${ENGINE_DB_USER}" \
       -c "update vdc_options set option_value='{\"x86\":\"true\",\"ppc\":\"false\"}' where option_name = 'HotUnplugMemorySupported' and version='4.1';"

3. Restart ovirt-engine service

   systemctl restart ovirt-engine

(Originally by Martin Perina)
Comment 5 RHV Bugzilla Automation and Verification Bot 2018-07-20 02:38:53 EDT
This is not specific to the HotUnplugMemorySupported values , in the attached document there are 24 values that are not correct when you compare 4.1 to 4.2 upgrade VS 4.2 clean install

(Originally by Eli Mesika)
Comment 6 RHV Bugzilla Automation and Verification Bot 2018-07-20 02:38:57 EDT
Created attachment 1457836 [details]
config diff between 4.1 to 4.2 upgrade and clean install

(Originally by Eli Mesika)
Comment 7 RHV Bugzilla Automation and Verification Bot 2018-07-20 02:39:01 EDT
Marking as a blocker, this affects RHV 4.2 customers upgrading from 4.1 badly (new 4.2 installations are not affected)

(Originally by Martin Perina)
Comment 8 RHV Bugzilla Automation and Verification Bot 2018-07-20 02:39:05 EDT
The reason for most of those changes between upgrade an clean install is [1] which did a change in config in an upgrade script instead of modifying 0000_config.sql directly , since 0000_config.sql is running in each upgrade, the changes made by [1] to 4.0 are overridden whilw installing 4.1


[1] https://gerrit.ovirt.org/#/c/49299/8/packaging/dbscripts/upgrade/04_00_0080_rename_architecture_family.sql

(Originally by Eli Mesika)
Comment 9 RHV Bugzilla Automation and Verification Bot 2018-07-20 02:39:10 EDT
(In reply to Martin Perina from comment #0)

Please note that the original bug on the HotUnplugMemorySupported value for 4.1 will not be fixed since it is probably supported but was not tested for 4.1 

Customers willing to use this feature will have to enable it manually for 4.1 on their DBs on their own risk

(Originally by Eli Mesika)
Comment 10 RHV Bugzilla Automation and Verification Bot 2018-07-20 02:39:14 EDT
Workaround mentioned in Comment 3 is not valid, HotUnplugMemorySupported should be disabled in RHV 4.1 as it was not fully tested by QE (sorry for the confusion). And what's more important, there are much more inconsistencies on other values:

HotPlugCpuSupported
HotUnplugCpuSupported
HotPlugMemorySupported
HotUnplugMemorySupported
IsMigrationSupported
IsMemorySnapshotSupported
IsSuspendSupported
ClusterRequiredRngSourcesDefault

So if RHV 4.1/4.2 customers, who upgraded from RHV 4.0, have issues around above features, they need to upgrade to RHV 4.2.5+.

(Originally by Martin Perina)
Comment 12 Lucie Leistnerova 2018-07-26 04:39:30 EDT
Upgrade 4.1.11 -> 4.2.5 and clean 4.2.5 has no main differences in vdc_options values
and HotUnplugMemorySupported is {"x86":"false","ppc":"false"} for version < 4.2

verified in ovirt-engine-4.2.5.2-0.1.el7ev.noarch
Comment 14 errata-xmlrpc 2018-07-31 13:49:18 EDT
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-2018:2318

Note You need to log in before you can comment on or make changes to this bug.