Skip to content

Conversation

@stephenfin
Copy link
Contributor

This is a manual backport of #850 that also includes #860. It replaces #856.

stephenfin added 5 commits May 6, 2025 21:56
Where fmt.Errorf is called with a single string parameter, it is faster
and arguably more correct to call errors.New instead.

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
There's some rework needed around CCM and the docs to get users to start
using the new location of the CA cert. That is not going to happen in
4.19, so for now we opt to simply sync from the old place to the new
place and leave the existing docs in place. In a future release, we can
fully remove the old place (with a release note) and remove this syncer.

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Reflect their respective namespaces.

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

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
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>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 30, 2025
@openshift-ci-robot
Copy link
Contributor

@stephenfin: This pull request references Jira Issue OCPBUGS-55798, which is invalid:

  • expected dependent Jira Issue OCPBUGS-55777 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

Details

In response to this:

This is a manual backport of #850 that also includes #860. It replaces #856.

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-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label May 30, 2025
@openshift-ci openshift-ci bot requested review from 2uasimojo and jstuever May 30, 2025 11:07
@codecov
Copy link

codecov bot commented May 30, 2025

Codecov Report

Attention: Patch coverage is 50.00000% with 7 lines in your changes missing coverage. Please review.

Project coverage is 47.14%. Comparing base (9c3346a) to head (d5af20b).
Report is 13 commits behind head on release-4.19.

Files with missing lines Patch % Lines
...g/operator/secretannotator/openstack/reconciler.go 50.00% 5 Missing and 2 partials ⚠️
Additional details and impacted files

Impacted file tree graph

@@               Coverage Diff                @@
##           release-4.19     #866      +/-   ##
================================================
+ Coverage         47.05%   47.14%   +0.08%     
================================================
  Files                97       97              
  Lines             11880    12011     +131     
================================================
+ Hits               5590     5662      +72     
- Misses             5676     5727      +51     
- Partials            614      622       +8     
Files with missing lines Coverage Δ
...g/operator/secretannotator/openstack/reconciler.go 53.62% <50.00%> (-1.50%) ⬇️

... and 2 files with indirect coverage changes

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

@jstuever jstuever self-assigned this Jun 5, 2025
@jianping-shu
Copy link

pre-merge-tested with OCP-82011.
The regression test for aws mint cluster passed too.

Copy link
Contributor

@jstuever jstuever left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve
/label backport-risk-assessed

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. lgtm Indicates that a PR is ready to be merged. labels Jun 6, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 6, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jstuever, 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 6, 2025
@jstuever
Copy link
Contributor

jstuever commented Jun 6, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 6, 2025
@openshift-ci-robot
Copy link
Contributor

@jstuever: This pull request references Jira Issue OCPBUGS-55798, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-55777 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-55777 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
  • bug has dependents

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

Details

In response to this:

/jira refresh

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-ci openshift-ci bot requested a review from jianping-shu June 6, 2025 18:27
@jianping-shu
Copy link

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 9, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 9, 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 675dad5 into openshift:release-4.19 Jun 9, 2025
13 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the cherry-pick-850-to-release-4.19 branch June 9, 2025 04:24
@openshift-ci-robot
Copy link
Contributor

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

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

Details

In response to this:

This is a manual backport of #850 that also includes #860. It replaces #856.

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.19.0-202506090516.p0.g675dad5.assembly.stream.el9.
All builds following this will include this PR.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.

5 participants