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

MCO-392: Re-enable ostree-container-inject-openshift-cvo-labels knob #1457

Merged
merged 1 commit into from Mar 18, 2024

Conversation

jlebon
Copy link
Member

@jlebon jlebon commented Mar 7, 2024

This was previously enabled (#1048, #1374) and then disabled again (#1084, #1393).

The last time we tried it, the issue was that there were some references remaining in openshift/kubernetes and openshift/release. Those have been cleaned up now:

openshift/release#49156
openshift/kubernetes#1805

So... third time's the charm!

This was previously enabled (openshift#1048, openshift#1374) and then disabled again (openshift#1084, openshift#1393).

The last time we tried it, the issue was that there were some references
remaining in openshift/kubernetes and openshift/release. Those have been
cleaned up now:

openshift/release#49156
openshift/kubernetes#1805

So... third time's the charm!
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 7, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 7, 2024

@jlebon: This pull request references MCO-392 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target either version "4.16." or "openshift-4.16.", but it targets "4.15.0" instead.

In response to this:

This was previously enabled (#1048, #1374) and then disabled again (#1084, #1393).

The last time we tried it, the issue was that there were some references remaining in openshift/kubernetes and openshift/release. Those have been cleaned up now:

openshift/release#49156
openshift/kubernetes#1805

So... third time's the charm!

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.

@jlebon
Copy link
Member Author

jlebon commented Mar 7, 2024

/hold

This needs to be coordinated with DTK, ART, and TRT. But let's make sure it's reviewed and ready to go once we're ready.

@openshift-ci openshift-ci bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 7, 2024
@jlebon
Copy link
Member Author

jlebon commented Mar 7, 2024

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 7, 2024

@jlebon: This pull request references MCO-392 which is a valid jira issue.

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.

@jlebon
Copy link
Member Author

jlebon commented Mar 7, 2024

/retest

@jmarrero
Copy link
Member

jmarrero commented Mar 12, 2024

/approve

@jmarrero
Copy link
Member

/lgtm

Copy link
Contributor

openshift-ci bot commented Mar 12, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jlebon, jmarrero

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-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 12, 2024
@jlebon
Copy link
Member Author

jlebon commented Mar 18, 2024

We're ready to do this!

/hold cancel

@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 Mar 18, 2024
@jlebon
Copy link
Member Author

jlebon commented Mar 18, 2024

Wasn't sure if this was acknowledge-critical-fixes-only-worthy, but openshift/driver-toolkit#142 merged and we can't do just one.

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Mar 18, 2024
@jlebon
Copy link
Member Author

jlebon commented Mar 18, 2024

I'm going to force-merge this one. It's time-sensitive now that openshift/driver-toolkit#142 has merged. CI did pass previously here (but anyway the change here is not really tested by CI beyond the superficial level of cosa being able to add the labels to the oscontainer, which is trivial).

/override ci/prow/rhcos-9-build-test-metal
/override ci/prow/rhcos-9-build-test-qemu
/override ci/prow/scos-9-build-test-metal
/override ci/prow/scos-9-build-test-qemu

Copy link
Contributor

openshift-ci bot commented Mar 18, 2024

@jlebon: Overrode contexts on behalf of jlebon: ci/prow/rhcos-9-build-test-metal, ci/prow/rhcos-9-build-test-qemu, ci/prow/scos-9-build-test-metal, ci/prow/scos-9-build-test-qemu

In response to this:

I'm going to force-merge this one. It's time-sensitive now that openshift/driver-toolkit#142 has merged. CI did pass previously here (but anyway the change here is not really tested by CI beyond the superficial level of cosa being able to add the labels to the oscontainer, which is trivial).

/override ci/prow/rhcos-9-build-test-metal
/override ci/prow/rhcos-9-build-test-qemu
/override ci/prow/scos-9-build-test-metal
/override ci/prow/scos-9-build-test-qemu

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.

@jlebon
Copy link
Member Author

jlebon commented Mar 18, 2024

/override ci/prow/images

Copy link
Contributor

openshift-ci bot commented Mar 18, 2024

@jlebon: Overrode contexts on behalf of jlebon: ci/prow/images

In response to this:

/override ci/prow/images

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 722cc11 into openshift:master Mar 18, 2024
7 checks passed
Copy link
Contributor

openshift-ci bot commented Mar 18, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. 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.

None yet

3 participants