-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: CRD creation fails #1609
Comments
@maiti0706: 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 container.storage.modules@dell.com. |
@maiti0706 Any chance this setup was running CSM for Authorization v1 before and some of the resources including CRDs are stale from v1? |
No, this is new setup/cluster |
@mgandharva is triaging this issue |
@maiti0706 @ashleyvjoy , I went through the issue. I tried the same steps as given in the issue, I didn't get any error. It worked absolutely fine. I'm attaching the screenshots here: Then I tried to regenrate error, as you can see in logs, I believe the crds version, in the setup is incorrect, please try this command to check the versin of the crd, It should be v1.
Please update crds version, It should work then |
@francis-nijay can we close this issue since it's open for 2 weeks and haven't heard back any updates? |
Bug Description
CSM Authorization 2.0 for PowerFlex
Openshift: 4.17
Install type: CSM Operator
CR fails with the given manifest file (as mentioned in documentation) https://github.com/dell/csm-operator/blob/main/samples/authorization/csm_authorization_proxy_server_v200.yaml . All pods are running expect proxy server (logs attached)
[root@spv-csm-jhl01 auth20]# oc get pods
NAME READY STATUS RESTARTS AGE
authorization-controller-5f94dd5899-wlfs2 0/1 CrashLoopBackOff 5 (98s ago) 18m
proxy-server-7f9fb95c98-m2jdm 2/3 CrashLoopBackOff 8 (2m14s ago) 18m
redis-csm-0 1/1 Running 0 18m
redis-csm-1 1/1 Running 0 18m
redis-csm-2 1/1 Running 0 18m
redis-csm-3 1/1 Running 0 18m
redis-csm-4 1/1 Running 0 18m
rediscommander-8fd8b5795-vnqvf 1/1 Running 0 18m
role-service-797b9ccf7d-mxq78 1/1 Running 0 18m
sentinel-0 1/1 Running 0 18m
sentinel-1 1/1 Running 0 18m
sentinel-2 1/1 Running 0 18m
sentinel-3 1/1 Running 0 18m
sentinel-4 1/1 Running 0 18m
storage-service-5d78c89c46-7m4xj 1/1 Running 1 (18m ago) 18m
tenant-service-55bbc5869b-cgtgq 1/1 Running 2 (18m ago) 18m
[root@spv-csm-jhl01 auth20]# oc logs proxy-server-7f9fb95c98-m2jdm
Defaulted container "proxy-server" out of: proxy-server, opa, kube-mgmt
time="2024-11-25T14:08:23Z" level=info msg="configuration has been set" LOG_LEVEL=debug
time="2024-11-25T14:08:23Z" level=info msg="configuration has been set" LOG_LEVEL=debug
time="2024-11-25T14:08:23Z" level=info msg="main: started application version "develop""
time="2024-11-25T14:08:23Z" level=info msg="sentinel-0.sentinel.authorization.svc.cluster.local:5000\n"
time="2024-11-25T14:08:23Z" level=info msg=" sentinel-1.sentinel.authorization.svc.cluster.local:5000\n"
time="2024-11-25T14:08:23Z" level=info msg=" sentinel-2.sentinel.authorization.svc.cluster.local:5000\n"
time="2024-11-25T14:08:23Z" level=info msg=" sentinel-3.sentinel.authorization.svc.cluster.local:5000\n"
time="2024-11-25T14:08:23Z" level=info msg=" sentinel-4.sentinel.authorization.svc.cluster.local:5000\n"
redis: 2024/11/25 14:08:23 sentinel.go:379: sentinel: discovered new sentinel="c7e215abf4ebc81f1557864669abe1c6d3cbbcca" for master="mymaster"
redis: 2024/11/25 14:08:23 sentinel.go:379: sentinel: discovered new sentinel="3d0508f9d6ac7c02292b1545bf2794bd3bacebca" for master="mymaster"
redis: 2024/11/25 14:08:23 sentinel.go:379: sentinel: discovered new sentinel="49e545b62f069139a50ba3059b324ac8e4b86e35" for master="mymaster"
redis: 2024/11/25 14:08:23 sentinel.go:379: sentinel: discovered new sentinel="e49cdcabfe32e7ef9e196391492882768ba1245f" for master="mymaster"
redis: 2024/11/25 14:08:23 sentinel.go:332: sentinel: new master="mymaster" addr="redis-csm-0.redis-csm.authorization.svc.cluster.local:6379"
time="2024-11-25T14:08:23Z" level=info msg="main: initializing debugging support"
time="2024-11-25T14:08:23Z" level=debug msg="main: debug listening" debug host=":9090"
time="2024-11-25T14:08:23Z" level=info msg="main: stopped application"
time="2024-11-25T14:08:23Z" level=error msg="main: error: getting powerflex systems: listing storage: no matches for kind "Storage" in version "csm-authorization.storage.dell.com/v1""
[root@spv-csm-jhl01 auth20]#
Logs
logs-auth-proxy.txt
Screenshots
Additional Environment Information
No response
Steps to Reproduce
CSM Operator installation (openshift 4.17) ;
oc apply -f csm_athorization_proxy_server_v200.yaml
Expected Behavior
proxy pod should be running
CSM Driver(s)
1.7.0
Installation Type
Operator
Container Storage Modules Enabled
No response
Container Orchestrator
Openshift 4.17
Operating System
RH 9.1
The text was updated successfully, but these errors were encountered: