Description of problem: A data section with additional user defined rule, added to forklift-validation-config, by this example [1], is removed by pod reconciling. [1] https://github.com/pemcg/forklift-validation/tree/update_readme#user-defined-additional-rules Version-Release number of selected component (if applicable): MTV-2.2 How reproducible: Tried twice on the same PSI based cluster Expected results: User defined rule data should not be removed.
With the change, the configmap should be reconciled if it already exists. If the configmap content is breaking the validation service, deleting the configmap will force the operator to create a new empty configmap, resetting the validation service. Please verify with mtv-operator-bundle-container-2.2.0-100 / ii:138977, or later.
Verified on MTV-2.2.0-100. A data section with additional user defined rule, added to forklift-validation-config, by this example [1], and it is not removed by pod reconciling. [1] https://github.com/pemcg/forklift-validation/tree/update_readme#user-defined-additional-rules It was tested for VMware to a target namespace openshit-mtv as well as a new created namespace. This it the validation "information" message displayed in UI, for a VM with 2 disks: "Multiple disks detected: Example user-supplied extra validation rule - multiple disks have been detected on this VM". "MultiDisks" Screenshot attached.
Please see build 2.2.0-102 for latest revision of the fix for this issue.
Tested on MTV-2.2.0-104. A data section with additional user defined rule, added to forklift-validation-config, by example [1]. [1] https://github.com/pemcg/forklift-validation/tree/update_readme#user-defined-additional-rules It was tested for VMware to a target namespace other than openshift-mtv. This is the validation "information" message displayed in UI, for a VM with 2 disks: "Multiple disks detected: Example user-supplied extra validation rule - multiple disks have been detected on this VM". Continue to track the config map for the coming hours, to ensure reconcile doesn't reset the configMap to it's initial content.
Moving bug to verified as after couple of hours data still remains in the validation configMap.
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 (MTV 2.2.0 Images), 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-2021:5066