Skip to content
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

Remove unused 'DeploymentReady' condition from Cinder status #300

Merged

Conversation

abays
Copy link
Contributor

@abays abays commented Nov 20, 2023

The DeploymentReadyCondition condition in the Cinder controller is initialized but then never used. It doesn't interfere with the overall "ready" state calculation because of the way the Cinder CRD's IsReady() function is written. But if it isn't used, we should just drop it.

@abays
Copy link
Contributor Author

abays commented Nov 20, 2023

@abays: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/cinder-operator-build-deploy-tempest e5c45a7 link false /test cinder-operator-build-deploy-tempest

Full PR test history. Your PR dashboard.

/test cinder-operator-build-deploy-tempest

Doesn't immediately seem related to this change:

Error from server (NotFound): deployments.apps "openstack-operator-controller-manager" not found
+ n=12
+ sleep 10
+ '[' 12 -ge 30 ']'
+ oc get deployment openstack-operator-controller-manager
NAME                                    READY   UP-TO-DATE   AVAILABLE   AGE
openstack-operator-controller-manager   0/1     1            0           5s
+ break
++ oc get subscription openstack-operator -o 'jsonpath={.status.installedCSV}'
+ INSTALLED_CSV=openstack-operator.v0.0.1
+ oc get csv openstack-operator.v0.0.1 -o 'jsonpath={.spec.install.spec.deployments[*].name}'
+ timeout 240 xargs -I '{}' -d ' ' sh -c 'oc wait --for=condition=Available deployment {} --timeout=-1s'
{"component":"entrypoint","error":"wrapped process failed: exit status 124","file":"k8s.io/test-infra/prow/entrypoint/run.go:84","func":"k8s.io/test-infra/prow/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2023-11-20T18:43:55Z"}
error: failed to execute wrapped command: exit status 124

Copy link
Contributor

@fmount fmount left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unless there are other plans to reuse this variable, the change makes sense
/lgtm

Copy link
Contributor

openshift-ci bot commented Nov 21, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abays, fmount

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 689b50f into openstack-k8s-operators:main Nov 21, 2023
1 check passed
ASBishop pushed a commit to ASBishop/cinder-operator that referenced this pull request Mar 11, 2024
…rators/renovate/openstack-k8s-operators

Update openstack-k8s-operators
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants