-
Bug
-
Resolution: Done
-
Blocker
-
quay-v3.4.0
-
False
-
False
-
Undefined
-
Description:
This is an issue found when use new "quay configure editor" deployed by new TNG Operator, after input valid AWS S3 storage configurations, click "validation configurations changes", and get validation passed. next click button "Reconfigure Quay", found new quay-config-secret was created, but new Quay APP POD still mount and use old quay-config-secret, also found when reloading config editor, still see the old configurations.
Note:
Here Quay should maintain only one quay-configure-secret, so new Quay APP POD can get to know and mount updated quay-configure-secret.
lizhang@lzha-mac Quay3.3_operator_testing % oc get secret | grep quaydemo-quay-config-secret quaydemo-quay-config-secret-27d8gfk956 Opaque 6 109m quaydemo-quay-config-secret-2972h9dmg2 Opaque 9 89m quaydemo-quay-config-secret-2f75d4fh95 Opaque 6 109m quaydemo-quay-config-secret-2f7cdt488k Opaque 6 100m quaydemo-quay-config-secret-2t6k85mbtk Opaque 6 101m quaydemo-quay-config-secret-4ttmmtbc4c Opaque 6 109m quaydemo-quay-config-secret-5g755hkbhm Opaque 6 107m quaydemo-quay-config-secret-66cd826m77 Opaque 6 93m quaydemo-quay-config-secret-6b2thh8ct9 Opaque 6 109m quaydemo-quay-config-secret-6c8g8gdd46 Opaque 6 108m quaydemo-quay-config-secret-6d9ck27fff Opaque 6 109m quaydemo-quay-config-secret-6tt7g9hdd2 Opaque 15 38m quaydemo-quay-config-secret-79d5b255d6 Opaque 9 101m quaydemo-quay-config-secret-7btbk44824 Opaque 9 102m quaydemo-quay-config-secret-85tc4cg42d Opaque 6 108m quaydemo-quay-config-secret-8kbchtdf77 Opaque 6 109m quaydemo-quay-config-secret-9m7tfkc49d Opaque 6 108m quaydemo-quay-config-secret-bkbgkbm6mf Opaque 9 101m quaydemo-quay-config-secret-bkk7dk2tdh Opaque 3 8h quaydemo-quay-config-secret-c4h7kgk5ck Opaque 6 109m quaydemo-quay-config-secret-c72gdb48b8 Opaque 15 27m quaydemo-quay-config-secret-c9992mt2f4 Opaque 15 57m quaydemo-quay-config-secret-cbd728h8cf Opaque 12 86m quaydemo-quay-config-secret-cc79fkc4t2 Opaque 9 101m quaydemo-quay-config-secret-ccbghc2fd6 Opaque 6 108m quaydemo-quay-config-secret-dmcdk7c2k2 Opaque 6 109m quaydemo-quay-config-secret-f8tg7b2679 Opaque 12 86m quaydemo-quay-config-secret-fmt4ktg5kt Opaque 12 86m quaydemo-quay-config-secret-g8f28t6947 Opaque 12 86m quaydemo-quay-config-secret-g9g249d8c8 Opaque 6 100m quaydemo-quay-config-secret-h5ft9f8tfh Opaque 6 109m quaydemo-quay-config-secret-h6b45kb78k Opaque 6 109m quaydemo-quay-config-secret-h9fc2dkkk2 Opaque 6 100m quaydemo-quay-config-secret-hgk7gf488m Opaque 6 109m quaydemo-quay-config-secret-k6dg72fd25 Opaque 6 109m quaydemo-quay-config-secret-kd7c5d7f6h Opaque 6 109m quaydemo-quay-config-secret-kmkgkbgb27 Opaque 3 8h quaydemo-quay-config-secret-m9g5mmgctm Opaque 6 108m quaydemo-quay-config-secret-mf929fhmf7 Opaque 6 109m quaydemo-quay-config-secret-mg6tcm5gh7 Opaque 6 108m quaydemo-quay-config-secret-mm7cct6ggb Opaque 6 109m quaydemo-quay-config-secret-mt4d9fh4td Opaque 6 109m quaydemo-quay-config-secret-t5b85779c4 Opaque 12 86m quaydemo-quay-config-secret-t6cdg65m82 Opaque 6 109m quaydemo-quay-config-secret-t74746c7t2 Opaque 12 86m quaydemo-quay-config-secret-td925d7hb6 Opaque 6 109m quaydemo-quay-config-secret-tdck6hgt2d Opaque 9 101m quaydemo-quay-config-secret-tg7c8g68m6 Opaque 9 102m
Quay App POD:
oc get pod quaydemo-quay-app-6cd455ccf4-fnq4q -o json | jq '.spec.volumes' [ { "name": "configvolume", "secret": { "defaultMode": 420, "secretName": "quaydemo-quay-config-secret-c72gdb48b8" } }, { "configMap": { "defaultMode": 420, "name": "quaydemo-cluster-service-ca" }, "name": "extra-ca-certs" }, { "name": "default-token-7pzrn", "secret": { "defaultMode": 420, "secretName": "default-token-7pzrn" } } ]
Quay Catalogsoure Image:
quay.io/quay/quay-operator-catalog:v3.4.0-osbs
Quay image: quay.io/quay/quay:v3.4.0-osbs
OCP Version: 4.5.0
Quay CR:
apiVersion: quay.redhat.com/v1 kind: QuayRegistry metadata: name: quaydemo
Steps:
- Login OCP Console
- Create new OCP Namespace and deploy Quay TNG Operator
- Create Quay CR with "create -n quay0340 -f quay.yaml"
- Open Quay config editor
- Input valid AWS S3 configurations at Registry Storage
- Click "Validate configuration changes"
- Click button "Reconfigure Quay"
Expected Results:
Will trigger Quay re-deployment, and update quay-configure-secret, new Quay APP POD will use and mount latest quay-configure-secret
Actual Results:
New quay-configure-secret was created, but new Quay APP POD still use and mount old quay-configure-secret
