Skip to content

Conversation

@stephenfin
Copy link
Contributor

As noted by QE, we missed this in #850. Add it now.

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels May 21, 2025
@openshift-ci-robot
Copy link
Contributor

@stephenfin: This pull request references Jira Issue OCPBUGS-55777, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.0) matches configured target version for branch (4.20.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jianping-shu

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

As noted by QE, we missed this in #850. Add it now.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Copy link
Member

@mandre mandre left a comment

Choose a reason for hiding this comment

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

/lgtm

This new role allows to read the cloud-provider-config configmap in the openshift-config namespace.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 21, 2025
@jstuever
Copy link
Contributor

/test e2e-openstack

@jstuever
Copy link
Contributor

jstuever commented May 21, 2025

/assign @jianping-shu
for pre-merge testing

@jianping-shu
Copy link

@stephenfin The pre-merge testing failed, still the same.
(1) CCO has the following logs, looks like CCO was listing the configmap instead of get?
I0522 05:00:57.039480 1 reflector.go:349] Listing and watching *v1.ConfigMap from sigs.k8s.io/controller-runtime/pkg/cache/internal/informers.go:108
W0522 05:00:57.044098 1 reflector.go:569] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers.go:108: failed to list *v1.ConfigMap: configmaps is forbidden: User "system:serviceaccount:openshift-cloud-credential-operator:cloud-credential-operator" cannot list resource "configmaps" in API group "" at the cluster scope
E0522 05:00:57.044142 1 reflector.go:166] "Unhandled Error" err="sigs.k8s.io/controller-runtime/pkg/cache/internal/informers.go:108: Failed to watch *v1.ConfigMap: failed to list *v1.ConfigMap: configmaps is forbidden: User "system:serviceaccount:openshift-cloud-credential-operator:cloud-credential-operator" cannot list resource "configmaps" in API group "" at the cluster scope" logger="UnhandledError"

(2)And the output of the following command is exactly the same to the one in previous test.
oc get clusterroles.rbac.authorization.k8s.io cloud-credential-operator-role -o yaml

(3)Add ca-bundle.pem in configmap openshift-config/cloud-provider-config, the root credential secret kept no change.

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label May 26, 2025
@jianping-shu
Copy link

Tested again but still the same error.
The rbac output for below command was still not changed.
oc get clusterroles.rbac.authorization.k8s.io cloud-credential-operator-role -o yaml

Reflect their respective namespaces.

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
…config CM

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
@stephenfin stephenfin force-pushed the OCPBUGS-55777 branch 2 times, most recently from 2fbc82b to bcaa77e Compare May 28, 2025 14:33
Unlike the other clients, this one does not use caching (which requires
the operator have cluster-wide access to config maps). This is the same
thing done for AWS.

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
@codecov
Copy link

codecov bot commented May 29, 2025

Codecov Report

Attention: Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.

Project coverage is 47.14%. Comparing base (6a880b4) to head (a87b3b4).
Report is 6 commits behind head on master.

Files with missing lines Patch % Lines
...g/operator/secretannotator/openstack/reconciler.go 66.66% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #860      +/-   ##
==========================================
+ Coverage   46.97%   47.14%   +0.16%     
==========================================
  Files          97       97              
  Lines       11907    12011     +104     
==========================================
+ Hits         5593     5662      +69     
- Misses       5696     5727      +31     
- Partials      618      622       +4     
Files with missing lines Coverage Δ
...g/operator/secretannotator/openstack/reconciler.go 53.62% <66.66%> (-0.06%) ⬇️

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jianping-shu
Copy link

Tested w/ OCP-82011
In summary:
(1)When ca-bundle.pem is added/modified in configmap cloud-provider-config -n openshift-config, it will be synced to the root credential secret(kube-system/openstack-credentials) then the component credential secrets. But it won't be synced immediately, instead it will be synced in next cco reconcile.
(2)When ca-bundle.pem is removed, the cacert part in the root credential secret and the component credential secrets won't removed after next cco reconcile.
Pls. check if the above behaviors are ok

@stephenfin
Copy link
Contributor Author

Pls. check if the above behaviors are ok

That sounds correct, yes 👍

@jstuever
Copy link
Contributor

jstuever commented Jun 4, 2025

/retest

@jstuever
Copy link
Contributor

jstuever commented Jun 4, 2025

/test e2e-openshift

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 4, 2025

@jstuever: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test coverage
/test e2e-aws-ovn
/test e2e-azure-manual-oidc
/test e2e-hypershift
/test e2e-upgrade
/test images
/test security
/test unit
/test verify
/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-aws-manual-oidc
/test e2e-aws-qe
/test e2e-azure
/test e2e-azure-upgrade
/test e2e-gcp
/test e2e-gcp-manual-oidc
/test e2e-openstack
/test e2e-openstack-parallel
/test okd-scos-e2e-aws-ovn
/test okd-scos-images

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-cloud-credential-operator-master-coverage
pull-ci-openshift-cloud-credential-operator-master-e2e-aws-ovn
pull-ci-openshift-cloud-credential-operator-master-e2e-aws-qe
pull-ci-openshift-cloud-credential-operator-master-e2e-hypershift
pull-ci-openshift-cloud-credential-operator-master-e2e-upgrade
pull-ci-openshift-cloud-credential-operator-master-images
pull-ci-openshift-cloud-credential-operator-master-okd-scos-e2e-aws-ovn
pull-ci-openshift-cloud-credential-operator-master-security
pull-ci-openshift-cloud-credential-operator-master-unit
pull-ci-openshift-cloud-credential-operator-master-verify
pull-ci-openshift-cloud-credential-operator-master-verify-deps
Details

In response to this:

/test e2e-openshift

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@jstuever
Copy link
Contributor

jstuever commented Jun 4, 2025

/test e2e-openstack

@jstuever
Copy link
Contributor

jstuever commented Jun 4, 2025

/hold
for e2e-hypershift and e2e-openstack

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 4, 2025
@jstuever
Copy link
Contributor

jstuever commented Jun 4, 2025

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 4, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jstuever, mandre, stephenfin

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

The pull request process is described here

Details 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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 4, 2025
@stephenfin
Copy link
Contributor Author

/test e2e-openstack

Just a slow node causing : [bz-openshift-apiserver] clusteroperator/openshift-apiserver should not change condition/Available to fail, but it would be good to have a clean run.

@jianping-shu
Copy link

/retest

@stephenfin
Copy link
Contributor Author

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 5, 2025
@stephenfin
Copy link
Contributor Author

stephenfin commented Jun 5, 2025

CI is green. No further need for the hold. Thanks for the reviews/help, @jstuever @jianping-shu

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD f95f61d and 2 for PR HEAD a87b3b4 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 5, 2025

@stephenfin: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 92e68ab into openshift:master Jun 5, 2025
13 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the OCPBUGS-55777 branch June 5, 2025 20:26
@openshift-ci-robot
Copy link
Contributor

@stephenfin: Jira Issue OCPBUGS-55777: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-55777 has been moved to the MODIFIED state.

Details

In response to this:

As noted by QE, we missed this in #850. Add it now.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-cloud-credential-operator
This PR has been included in build ose-cloud-credential-operator-container-v4.20.0-202506052341.p0.g92e68ab.assembly.stream.el9.
All builds following this will include this PR.

ming1013 pushed a commit to ming1013/cloud-credential-operator that referenced this pull request Dec 15, 2025
OCPBUGS-55777: Add missing Role, RoleBinding
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants