Loading...

Type: Bug
Resolution: Unresolved
Priority: Major
Fix Version/s: None
Affects Version/s: quay-v3.8.8, quay-v3.9.0, quay-v3.10.0
Component/s: quay-operator
Labels:
- triaged

Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Workaround Description:
Hide

This issue is being reprioritized as Major since it has not been addressed within a few days or weeks of creation. We are using the OpenShift Bug Process critieria, https://source.redhat.com/groups/public/openshift/openshift_wiki/openshift_bugzilla_process#bug-priority:

BLOCKER: These are interrupt worthy bugs. Usually these would be CRITICAL or IMPORTANT severity bugs. Teams should immediately stop other items and address BLOCKER priority bugs. It should be worked until it is either resolved or the priority reduced. Leads and managers SHOULD always know the up-to-date status of these bugs.

CRITICAL: These are not necessarily immediately interrupt worthy, but likely cannot wait more than a few days for attention. Usually these would be CRITICAL or IMPORTANT severity bugs.

MAJOR: These should generally be scheduled for the current or next sprint and take precedence over feature work. These should not necessarily immediately interrupt ongoing work. Owners should be reporting daily on these in their standups.

NORMAL: These bugs should be evaluated, prioritized, and scheduled alongside all other work (ie. features) each sprint.

MINOR: These bugs should be periodically re-evaluated and may be scheduled along with other work. Bugs with a sustained low priority should be given strong consideration for closure.
Show
This issue is being reprioritized as Major since it has not been addressed within a few days or weeks of creation. We are using the OpenShift Bug Process critieria, https://source.redhat.com/groups/public/openshift/openshift_wiki/openshift_bugzilla_process#bug-priority: BLOCKER: These are interrupt worthy bugs. Usually these would be CRITICAL or IMPORTANT severity bugs. Teams should immediately stop other items and address BLOCKER priority bugs. It should be worked until it is either resolved or the priority reduced. Leads and managers SHOULD always know the up-to-date status of these bugs. CRITICAL: These are not necessarily immediately interrupt worthy, but likely cannot wait more than a few days for attention. Usually these would be CRITICAL or IMPORTANT severity bugs. MAJOR: These should generally be scheduled for the current or next sprint and take precedence over feature work. These should not necessarily immediately interrupt ongoing work. Owners should be reporting daily on these in their standups. NORMAL: These bugs should be evaluated, prioritized, and scheduled alongside all other work (ie. features) each sprint. MINOR: These bugs should be periodically re-evaluated and may be scheduled along with other work. Bugs with a sustained low priority should be given strong consideration for closure.
Intelligence Requested:
Market:

SFDC Cases Links:
SFDC Cases Open:
SFDC Cases Counter:

PX Impact Score:

Description:

This is an issue found in Quay 3.9.0 Operator, now after use quay config editor to make some config changes successfully, found can't update Quay config by updating the config bundle secret managed by QuayRegistry CR, pls review this issue, see the Quay Operator logs Quay390_operator_pod.logs

Quay: quay-operator-bundle-container-v3.9.0-105

Note: This issue can also be reproduced in Quay 3.8.8

Steps:

Deploy Quay 3.9.0 Operator, choose to use all managed components
Open Quay config editor to make some config changes, like adding new superuser, etc.
After Quay Operator reconcile the change successfully, update the config bundle secret managed by QuayRegistry CR, like add new line "FEATURE_UI_V2: true", etc
Save the Change
Waiting for Quay Operator to reconcile the change

Expected Results:

Quay Operator reconcile the change successfully.

Actual Results:

Quay Operator can't reconcile the change, and report following error message in Quay Operator logs.

"1.685431185274928e+09 DEBUG events Warning {"object": {"kind":"QuayRegistry","namespace":"quay-enterprise-847","name":"quayregistry","uid":"a4fe4625-02ed-4d0a-9e5f-e662f37e181e","apiVersion":"quay.redhat.com/v1","resourceVersion":"209440"}, "reason": "ComponentCreationFailed", "message": "could not inflate kubernetes objects: error converting JSON to YAML: yaml: control characters are not allowed"}"