Description of problem (please be detailed as possible and provide log snippests): As part of our regression runs, we noticed a failure in several of our tests, related to the creation and deletion of PVPool-backed backingstores. i.e. - tests/manage/mcg/test_bucket_creation.py::TestBucketCreation::test_bucket_creation[1-CLI-PVPOOL] In order to check the backingstore's health, we check its modeCode, and verify that it says OPTIMAL. In version 4.9.0-237.ci, the modeCode was still present (the tests passed in run 1636980743), meaning the change seems to have occurred in either 238 or 239. Version of all relevant components (if applicable): 4.9.0-239.ci Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? No Is there any workaround available to the best of your knowledge? Yes - check the backingstore's health in a different way Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 2 Can this issue reproducible? Unknown at the moment Can this issue reproduce from the UI? Unknown at the moment If this is a regression, please provide more details to justify this: This is a regression, since the modeCode was present in previous ODF versions. Steps to Reproduce: 1. Create a PVPool backingstore 2. Check the backingstore's YAML, and look for the status.mode.modeCode field Actual results: status.mode is an empty dictionary Expected results: status.mode.modeCode is present Additional info:
Hey, Please attach a must-gather in order to investigate the YAMLs and logs of NooBaa. Thank you.
Thank you very much, Petr. Removing needinfo as the must-gather was supplied
Moving to 4.10, will backport to 4.9.z if needed