Created attachment 1763038 [details] Incorrect infra configuration. Description of problem: Incorrect information related to infra configuration provided to CDI CR through the HCO spec is being accepted. Version-Release number of selected component (if applicable):4.8 How reproducible:100% Steps to Reproduce: 1.Add attached yaml contents in the HCO CR spec 2.Observe the HCO CR status in the UI as well as CLI Actual results: Changes to HCO CR are propagated to CDI CR which is accepted which leads to HCO CR keeping itself in Progressing state and never completes. Expected results: Changes made to the Infra under HCO CR spec should be refused by CDI CR as they are incorrect. Additional info:In the attached example the wrong part of the configuration is the "Equal" operand which doesn't exists. HCO CR refuse to update incorrect changes which is fixed in the BZ(https://bugzilla.redhat.com/show_bug.cgi?id=1893646).
Can we get an update on the status please? This is blocking automation.
Inbar, we moved it to next Sprint, but in case it's AutomationBlocker we'll do it this sprint. I'll update once there is a PR.
This is going to take a little more time to get right. Therefore I am pushing out to 4.9. The workaround is to simply pass correct data.
@adam litke can we maybe target it to a 4.8.Z stream?
@Inbar, The fix is going to be too complex and risky to be a z-stream candidate. Plus, since this bug isn't too severe and has a simple workaround it would be hard for me to justify the risk.
This depends on some refactoring of the CDI operator which did not land in time for 4.9. Therefore we need to push this out to 4.10.
Hi, Arnon, Do we have any update for this bug?
Removing keyword 'automation blocker', since it's not an automation blocker. Satyajit, was this issue found using automation? if so, please add a keyword 'automation'
Yan, no update. As Adam commented, it depends on some refactoring of the CDI operator. Michael, I guess it will wait for 4.11?
Hello Natalie, It is blocking me to write automation as it is not honoring the dry run. Thanks, Satyajit.
Arnon, has the refactoring that you are waiting on been completed? please provide the update on this bug
Yan, refactoring was not done yet. afair @mhenriks was supposed to work on it. Removing it from 4.11.
Arnon, please advise when will be a good time to complete this. If it is blocked by something, please ensure that the required work is documented in a Jira issue and linked to this bugzilla.
Adam, as Michael mentioned in the Jira, the issue is that the CDI CR needs to be validated at creation time. In order to do that, cdi-operator must implement a validating webhook for CDI resources. It is not a minor change but a significant refactoring work. It can be targeted to 4.15 if prioritized. wdyt?