Bug 2048348 - Service CA Operator does not reconcile for spec.loglevel changes in ServiceCA CRD
Summary: Service CA Operator does not reconcile for spec.loglevel changes in ServiceCA...
Status: CLOSED DUPLICATE of bug 2048349
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: service-ca
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Stefan Schimanski
QA Contact: Yash Tripathi
Depends On:
TreeView+ depends on / blocked
Reported: 2022-01-31 03:52 UTC by Michael Washer
Modified: 2022-01-31 03:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-01-31 03:58:02 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Michael Washer 2022-01-31 03:52:27 UTC
The logLevel value registered for the Service CA CRD are not reconciled immediately and require manual intervention by deleting the ServiceCA Controller instance Deployment for the application’s loglevel to change.

The options are described here:

Version-Release number of selected component (if applicable):
OpenShift 4.x
OpenShift Service CA Operator

How reproducible:
Every time

Steps to Reproduce:
1. Change the `servicecas.spec.logLevel` options to Debug, Trace or TraceAll
2. Check the ServiceCA Controller Pods - This is still verbosity level 2

Actual results:
Loglevel is not increased

Expected results:
LogLevel is increased (without requiring deletion of the whole Deployment)

Additional info:
To force a redeployment of the ServiceCA Controller, we can delete the whole deployment and the verbosity will increase.
Delete the ServiceCA Controller Deployment `oc delete deploy -n openshift-service-ca --all`

We can see in the links below:
`needsDeploy` doesn't take into account changes to the ServiceCA CRD:

ServiceCAOperator then avoids (re)deploying the ServiceCA Controller when `needsDeploy || caModified` is not true:

Comment 1 Michael Washer 2022-01-31 03:58:02 UTC
closing as this appears to have been created twice. See BZ 2048349

*** This bug has been marked as a duplicate of bug 2048349 ***

Note You need to log in before you can comment on or make changes to this bug.