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

[release-4.14] NO-JIRA: denylist: add dhcp-propagation and podman.rootless-systemd #1550

Merged
merged 1 commit into from
Jul 16, 2024

Conversation

marmijo
Copy link
Contributor

@marmijo marmijo commented Jul 15, 2024

In 4.14, these tests are using the F38 container. The F38 content was moved to the archive on the mirrors but the metalinks still reference the non-archive URLs causing these tests to fail.

Let's denylist them for now until https://pagure.io/releng/issue/12204 is resolved.

…temd

In 4.14, these tests are using the F38 container. The F38 content was
moved to the archive on the mirrors but the metalinks still reference
the non-archive URLs causing these tests to fail.

Let's denylist them for now until https://pagure.io/releng/issue/12204
is resolved.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 15, 2024
@openshift-ci-robot
Copy link

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

In response to this:

In 4.14, these tests are using the F38 container. The F38 content was moved to the archive on the mirrors but the metalinks still reference the non-archive URLs causing these tests to fail.

Let's denylist them for now until https://pagure.io/releng/issue/12204 is resolved.

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 review from jlebon and jschintag July 15, 2024 18:10
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 15, 2024
@marmijo
Copy link
Contributor Author

marmijo commented Jul 15, 2024

This situation could be prevented in the future with: #1546

@jlebon
Copy link
Member

jlebon commented Jul 15, 2024

Thanks!

/lgtm
/label backport-risk-assessed
/label cherry-pick-approved

@openshift-ci openshift-ci bot added 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. labels Jul 15, 2024
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 15, 2024
Copy link
Contributor

openshift-ci bot commented Jul 15, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@marmijo
Copy link
Contributor Author

marmijo commented Jul 15, 2024

/retest

@jlebon
Copy link
Member

jlebon commented Jul 15, 2024

/label jira/valid-bug

Copy link
Contributor

openshift-ci bot commented Jul 15, 2024

@jlebon: Can not set label jira/valid-bug: Must be member in one of these teams: [openshift-patch-managers openshift-staff-engineers openshift-release-oversight]

In response to this:

/label jira/valid-bug

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.

@sdodson sdodson added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jul 15, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 8d05da6 and 2 for PR HEAD 65d0b71 in total

@marmijo
Copy link
Contributor Author

marmijo commented Jul 16, 2024

/retest-required

@jlebon
Copy link
Member

jlebon commented Jul 16, 2024

Opened #1551 to track the timeouts. For now, let's unbreak the pipelines.

/override ci/prow/rhcos-92-build-test-metal
/override ci/prow/rhcos-92-build-test-qemu

Copy link
Contributor

openshift-ci bot commented Jul 16, 2024

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

In response to this:

Opened #1551 to track the timeouts. For now, let's unbreak the pipelines.

/override ci/prow/rhcos-92-build-test-metal
/override ci/prow/rhcos-92-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-sigs/prow repository.

@jlebon
Copy link
Member

jlebon commented Jul 16, 2024

/override ci/prow/rhcos-92-build-test-metal
/override ci/prow/rhcos-92-build-test-qemu

Copy link
Contributor

openshift-ci bot commented Jul 16, 2024

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

In response to this:

/override ci/prow/rhcos-92-build-test-metal
/override ci/prow/rhcos-92-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-sigs/prow repository.

@openshift-merge-bot openshift-merge-bot bot merged commit a48d004 into openshift:release-4.14 Jul 16, 2024
5 checks passed
Copy link
Contributor

openshift-ci bot commented Jul 16, 2024

@marmijo: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/rhcos-92-build-test-metal 65d0b71 link unknown /test rhcos-92-build-test-metal

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.

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.

4 participants