[BUG]: Authorization Proxy deployment is in permanent fail state when deployed by CSM-Operator #1143
Assignees
Labels
area/csm-operator
needs-triage
Issue requires triage.
type/bug
Something isn't working. This is the default label associated with a bug issue.
Milestone
Comments
jooseppi-luna
added
needs-triage
8 tasks
|
@jooseppi-luna: Thank you for submitting this issue! The issue is currently awaiting triage. Please make sure you have given us as much context as possible. If the maintainers determine this is a relevant issue, they will remove the needs-triage label and respond appropriately. We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at [email protected]. |
|
Fixed in v1.9.2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description
The CSM object associated with the authorization proxy server is stuck in a permanent failed state.
Logs
auth-proxy-fail-operator-logs.log
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce
Install auth proxy with csm-operator v1.4.1
Expected Behavior
Once the auth proxy deployment has succeeded, the auth proxy csm object should go into success state.
CSM Driver(s)
Not driver-specific
Installation Type
CSM-Operator v1.4.1
Container Storage Modules Enabled
Authorization v1.9.1
Container Orchestrator
Kubernetes v1.27.2
Operating System
RHEL 8.9
The text was updated successfully, but these errors were encountered: