-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
False
-
None
-
False
-
-
-
-
Rejected
Description of problem:
From 4.15 the update of of the AMQ operator from v7.11.6 to v7.11.7 fails with the error: error validating existing CRs against new CRD''s schema for "activemqartemisaddresses.broker.amq.io": error validating broker.amq.io/v2alpha1, Kind=ActiveMQArtemisAddress "amq-test/ex-aaoaddress": updated validation is too restrictive: [].spec.queueName: Required value If the ActiveMQArtemisAddress does not have the field "queueName". The CR is created using the version v1beta1 that does not have restrictions for the "queueName", but the validation goes against the v2alpha1 that as that field as required.
Version-Release number of selected component (if applicable):
reproduced in 4.15.16
How reproducible:
always
Steps to Reproduce:
1. Install 4.15 cluster 2. Install amq-broker-operator.v7.11.6-opr-2 operator 3. Create an activemqartemis with default values. 4. Create an activemqartemisaddresses without the field `.spec.queueName` 5. Update to amq-broker-operator.v7.11.7-opr-1 operator
Actual results:
The update of the operator stuck and is necessary to reinstall it.
Expected results:
The operator should be updated without additional manual actions.
Additional info:
This issue does not happen in OpenShift 4.14
- clones
-
ENTMQBR-9210 Operator update failing for "updated validation is too restrictive"
- Closed
- links to
-
RHBA-2024:139747 AMQ Broker 7.11.7.OPR.2.GA Container Images release
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...