Skip to content

OCPBUGS-36520: Update Dockerfile path for console operator release 4.17 #67416

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 2 commits into from
Closed

OCPBUGS-36520: Update Dockerfile path for console operator release 4.17 #67416

wants to merge 2 commits into from

Conversation

@Leo6Leo
Copy link
Contributor

@Leo6Leo Leo6Leo commented Jul 23, 2025

Description

Update Dockerfile path for console operator release 4.17. This PR links to openshift/console-operator#1023

@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 Jul 23, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 23, 2025

@Leo6Leo: This pull request references Jira Issue OCPBUGS-36520, which is invalid:

  • expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.17.z" 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:

Description

Update Dockerfile path for console operator release 4.17. This PR links to openshift/console-operator#1023

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.

@Leo6Leo
Copy link
Contributor Author

Leo6Leo commented Jul 23, 2025

/cc @ashwindasr

@openshift-ci openshift-ci bot requested a review from ashwindasr July 23, 2025 20:08
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 23, 2025

[REHEARSALNOTIFIER]
@Leo6Leo: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-console-operator-release-4.17-e2e-aws-console openshift/console-operator presubmit Ci-operator config changed
pull-ci-openshift-console-operator-release-4.17-e2e-aws-operator openshift/console-operator presubmit Ci-operator config changed
pull-ci-openshift-console-operator-release-4.17-e2e-aws-ovn-single-node openshift/console-operator presubmit Ci-operator config changed
pull-ci-openshift-console-operator-release-4.17-e2e-azure-ovn-upgrade openshift/console-operator presubmit Ci-operator config changed
pull-ci-openshift-console-operator-release-4.17-e2e-gcp-ovn openshift/console-operator presubmit Ci-operator config changed
pull-ci-openshift-console-operator-release-4.17-images openshift/console-operator presubmit Ci-operator config changed
pull-ci-openshift-console-operator-release-4.17-okd-scos-images openshift/console-operator presubmit Ci-operator config changed
pull-ci-openshift-console-operator-release-4.17-unit openshift/console-operator presubmit Ci-operator config changed
pull-ci-openshift-console-operator-release-4.17-verify openshift/console-operator presubmit Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-ci openshift-ci bot requested review from TheRealJon and jhadvig July 23, 2025 20:09
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 23, 2025

[REHEARSALNOTIFIER]
@Leo6Leo: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-console-operator-release-4.17-okd-scos-images openshift/console-operator presubmit Ci-operator config changed
pull-ci-openshift-console-operator-release-4.17-e2e-aws-console openshift/console-operator presubmit Ci-operator config changed
pull-ci-openshift-console-operator-release-4.17-e2e-aws-operator openshift/console-operator presubmit Ci-operator config changed
pull-ci-openshift-console-operator-release-4.17-e2e-aws-ovn-single-node openshift/console-operator presubmit Ci-operator config changed
pull-ci-openshift-console-operator-release-4.17-e2e-azure-ovn-upgrade openshift/console-operator presubmit Ci-operator config changed
pull-ci-openshift-console-operator-release-4.17-e2e-gcp-ovn openshift/console-operator presubmit Ci-operator config changed
pull-ci-openshift-console-operator-release-4.17-images openshift/console-operator presubmit Ci-operator config changed
pull-ci-openshift-console-operator-release-4.17-unit openshift/console-operator presubmit Ci-operator config changed
pull-ci-openshift-console-operator-release-4.17-verify openshift/console-operator presubmit Ci-operator config changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 23, 2025

@Leo6Leo: 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.

@ashwindasr
Copy link
Contributor

ashwindasr commented Jul 23, 2025

/lgtm

/hold

Feel free to unhold when ready

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 23, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 23, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 23, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ashwindasr, Leo6Leo
Once this PR has been reviewed and has the lgtm label, please assign spadgett for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@Leo6Leo Leo6Leo mentioned this pull request Jul 31, 2025
Open
@openshift-bot
Copy link
Contributor

openshift-bot commented Aug 23, 2025

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 23, 2025
@Leo6Leo
Copy link
Contributor Author

Leo6Leo commented Aug 23, 2025

/lifecycle frozen

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 23, 2025

@Leo6Leo: The lifecycle/frozen label cannot be applied to Pull Requests.

In response to this:

/lifecycle frozen

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.

@Leo6Leo
Copy link
Contributor Author

Leo6Leo commented Aug 25, 2025

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 25, 2025
@openshift-bot
Copy link
Contributor

openshift-bot commented Sep 24, 2025

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 24, 2025
@openshift-bot
Copy link
Contributor

openshift-bot commented Oct 9, 2025

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 9, 2025
@openshift-bot
Copy link
Contributor

openshift-bot commented Oct 24, 2025

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Oct 24, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 2025

@openshift-bot: Closed this PR.

In response to this:

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 24, 2025

@Leo6Leo: This pull request references Jira Issue OCPBUGS-36520. The bug has been updated to no longer refer to the pull request using the external bug tracker.

In response to this:

Description

Update Dockerfile path for console operator release 4.17. This PR links to openshift/console-operator#1023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ashwindasr ashwindasr Awaiting requested review from ashwindasr

@jhadvig jhadvig Awaiting requested review from jhadvig

@TheRealJon TheRealJon Awaiting requested review from TheRealJon

Assignees

@ashwindasr ashwindasr

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/invalid-bug Indicates that a referenced Jira bug is invalid 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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@Leo6Leo @openshift-ci-robot @ashwindasr @openshift-bot