Skip to content

NO-ISSUE: Rebase 4.14.0 + csi-snapshot-webhook alignment#3283

Merged
openshift-merge-bot[bot] merged 10 commits intoopenshift:release-4.14from
pmtk:rebase-4.14.0-0.nightly-2024-04-24-075532_amd64-2024-04-24_arm64-2024-04-24
Apr 26, 2024
Merged

NO-ISSUE: Rebase 4.14.0 + csi-snapshot-webhook alignment#3283
openshift-merge-bot[bot] merged 10 commits intoopenshift:release-4.14from
pmtk:rebase-4.14.0-0.nightly-2024-04-24-075532_amd64-2024-04-24_arm64-2024-04-24

Conversation

@pmtk
Copy link
Member

@pmtk pmtk commented Apr 25, 2024

No description provided.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 25, 2024
@openshift-ci openshift-ci bot requested review from dhellmann and jerpeter1 April 25, 2024 09:32
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 25, 2024
@pmtk pmtk force-pushed the rebase-4.14.0-0.nightly-2024-04-24-075532_amd64-2024-04-24_arm64-2024-04-24 branch from faed10a to 7e3ff1b Compare April 25, 2024 14:51
@pmtk pmtk changed the title WIP Rebase 4.14.0 0.nightly 2024 04 24 075532 amd64 2024 04 24 arm64 2024 04 24 NO-ISSUE: Rebase 4.14.0 + csi-snapshot-webhook alignment Apr 25, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 25, 2024
@openshift-ci-robot
Copy link

@pmtk: This pull request explicitly references no jira issue.

Details

In response to 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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 25, 2024
@pmtk
Copy link
Member Author

pmtk commented Apr 25, 2024

/retest

+ sudo subscription-manager register --org=XXXXXXXX --activationkey=XXXXXXXXXXXXXXXXXXXXX
Candlepin is in Suspend mode, please check /status resource to get more details (HTTP error code 503: Service Unavailable)

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 25, 2024

@pmtk: 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/test-infra repository. I understand the commands that are listed here.

@copejon
Copy link
Contributor

copejon commented Apr 25, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 25, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 25, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, pmtk

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

@ggiguash
Copy link
Contributor

/label backport-risk-assessed
/label jira/valid-bug

@openshift-ci openshift-ci bot added 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. labels Apr 26, 2024
@dhensel-rh
Copy link
Contributor

/label cherrypick-approved

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 26, 2024

@dhensel-rh: The label(s) /label cherrypick-approved cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, approved, backport-risk-assessed, bugzilla/invalid-bug, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label cherrypick-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/test-infra repository.

@dhensel-rh
Copy link
Contributor

/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 Apr 26, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit a7786b0 into openshift:release-4.14 Apr 26, 2024
@pmtk pmtk deleted the rebase-4.14.0-0.nightly-2024-04-24-075532_amd64-2024-04-24_arm64-2024-04-24 branch May 17, 2024 05:23
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