-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
1.7.0, 1.8.0
-
None
-
False
-
-
False
-
-
Known Issue
-
Done
-
-
Description of problem:
As tried out in https://issues.redhat.com/browse/RHIDP-8910?focusedId=28102414&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28102414 , changes done to the default configuration of a running Operator won't persist when the operator is upgraded.
Prerequisites (if any, like setup, operators/versions):
Context: Testing direct upgrade from 1.5 to 1.7 (RHIDP-8910)
Steps to Reproduce
See the scenario depicted in https://docs.google.com/document/d/10RjljQsjD0mgZwA0L9694j5HbvZlO9phZMHGdPzeMMU/edit?tab=t.0#bookmark=id.ip5060evux85
Actual results:
Operator succesfully upgraded, but changes to the default configuration are lost.
Expected results:
In some cases, we recommend users to ultimately edit the Operator default configuration in order to workaround/fix some issues, so such edits should persist when the Operator is upgraded.
That said, not sure if this can be fixed on OLM-based operators.
Reproducibility (Always/Intermittent/Only Once):
Always