Skip to content

[release-4.19] OCPBUGS-55798: Sync OpenStack CA Bundles from legacy location #856

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

Open
wants to merge 2 commits into
base: release-4.19
Choose a base branch
from

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #850

/assign stephenfin

stephenfin added 2 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 <[email protected]>
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 <[email protected]>
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-55777 has been cloned as Jira Issue OCPBUGS-55798. Will retitle bug to link to clone.
/retitle [release-4.19] OCPBUGS-55798: Sync OpenStack CA Bundles from legacy location

In response to this:

This is an automated cherry-pick of #850

/assign stephenfin

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 changed the title [release-4.19] OCPBUGS-55777: Sync OpenStack CA Bundles from legacy location [release-4.19] OCPBUGS-55798: Sync OpenStack CA Bundles from legacy location May 6, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 6, 2025
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-55798, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-55777 to target a version in 4.20.0, but it targets "4.20" 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.

In response to this:

This is an automated cherry-pick of #850

/assign stephenfin

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

codecov bot commented May 6, 2025

Codecov Report

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

Project coverage is 47.04%. Comparing base (9c3346a) to head (852f4f6).
Report is 2 commits behind head on release-4.19.

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

Impacted file tree graph

@@               Coverage Diff                @@
##           release-4.19     #856      +/-   ##
================================================
- Coverage         47.05%   47.04%   -0.02%     
================================================
  Files                97       97              
  Lines             11880    11889       +9     
================================================
+ Hits               5590     5593       +3     
- Misses             5676     5680       +4     
- Partials            614      616       +2     
Files with missing lines Coverage Δ
...g/operator/secretannotator/openstack/reconciler.go 53.67% <50.00%> (-1.45%) ⬇️
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@stephenfin
Copy link
Contributor

/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 May 14, 2025
@openshift-ci-robot
Copy link
Contributor

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

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 New, 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 ON_QA, 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

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.

@stephenfin
Copy link
Contributor

The ci/prow/security job is failing due to quota issues (again).

@jstuever
Copy link
Contributor

/override ci/prow/security
There is an existing bug for this.

@jstuever
Copy link
Contributor

/lgtm
/approve
/label backport-risk-assessed

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

openshift-ci bot commented May 14, 2025

@jstuever: Overrode contexts on behalf of jstuever: ci/prow/security

In response to this:

/override ci/prow/security
There is an existing bug for this.

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.

Copy link
Contributor

openshift-ci bot commented May 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jstuever, openshift-cherrypick-robot

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

Copy link
Contributor

openshift-ci bot commented May 14, 2025

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

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

/label cherry-pick-approved

Copy link
Contributor

openshift-ci bot commented May 15, 2025

@stephenfin: Can not set label cherry-pick-approved: Must be member in one of these teams: []

In response to this:

/label cherry-pick-approved

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.

@stephenfin
Copy link
Contributor

/cc @lwan-wanglin @jianping-shu @huangmingxia

Looks like I need one of you folks to stick the cherry-pick-approved label on this?

@openshift-ci openshift-ci bot requested a review from huangmingxia May 15, 2025 15:16
@stephenfin
Copy link
Contributor

Proposed openshift/release#64985 so assignment happens automatically going forward.

@jianping-shu
Copy link

@stephenfin Pls. see my comments on OCPBUGS-55777, it encountered RBAC issue in verification.

@rlobillo
Copy link

/label cherry-pick-approved

Copy link
Contributor

openshift-ci bot commented May 16, 2025

@rlobillo: Can not set label cherry-pick-approved: Must be member in one of these teams: []

In response to this:

/label cherry-pick-approved

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.

@stephenfin
Copy link
Contributor

@stephenfin Pls. see my comments on OCPBUGS-55777, it encountered RBAC issue in verification.

Thank you. I'll take a look.

@stephenfin
Copy link
Contributor

The ci/prow/security job is failing due to quota issues (again).

@stephenfin Pls. see my comments on OCPBUGS-55777, it encountered RBAC issue in verification.

Thank you. I'll take a look.

I have proposed a fix at #860. Assuming all is good, will include that PR in this backport.

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. 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