-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
False
-
None
-
-
CNV I/U Operators Sprint 280
-
None
Description of problem:
When the WASP agent is enabled, by configuring: .spec.higherWorkloadDensity.memoryOvercommitPercentage greater than 100 in HyperConverged CR The hyperconverged-controller is stuck at upgradeMode=true and the upgrade process never fully finishes. The HCO's Progressing condition is stuck at HCOUpgrading indefinately with: HCO is now upgrading to version 4.99.0-0.1764114957 (for example) and further upgrade is being blocked.
Version-Release number of selected component (if applicable):
4.99 (probably also in 4.21)
How reproducible:
100%
Steps to Reproduce:
1. configure .spec.higherWorkloadDensity.memoryOvercommitPercentage > 100 at the HCO CR's spec. 2. wait for the wasp-agent daemonset to be deployed. 3. upgrade CNV to a newer version
Actual results:
upgrade is stuck, the new CSV is not being installed because OperatorCondition's Upgradable is false.
Expected results:
Upgrade should finish succeessfully
Additional info:
This is due to the fact that the function that compares the required and found for the wasp-agent DaemonSet returns false, because the required is missing some fields, that are getting populated by default.