Skip to content

[release-4.19] OCPBUGS-56888: Add flags in console static plugin for all the components of this epic #15106

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
Merged
openshift-merge-bot merged 1 commit into from
Jun 9, 2025
Merged

[release-4.19] OCPBUGS-56888: Add flags in console static plugin for all the components of this epic #15106

openshift-merge-bot merged 1 commit into from
Jun 9, 2025

Conversation

@lokanandaprabhu
Copy link
Contributor

@lokanandaprabhu lokanandaprabhu commented May 30, 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 30, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 30, 2025

@lokanandaprabhu: This pull request references Jira Issue OCPBUGS-56888, 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 Jira Issue OCPBUGS-56888 to depend on a bug targeting a version in 4.20.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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.

Details

In response to this:

Manual cherry-pick of #14992 and https://github.com/openshift/console/pull/15101/files

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 added component/pipelines Related to pipelines-plugin approved Indicates a PR has been approved by an approver from all required OWNERS files. labels May 30, 2025
@lokanandaprabhu
Copy link
Contributor Author

lokanandaprabhu commented May 30, 2025

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 30, 2025

@lokanandaprabhu: This pull request references Jira Issue OCPBUGS-56888, which is invalid:

  • expected dependent Jira Issue OCPBUGS-56889 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST 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.

Details

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.

@lokanandaprabhu
Copy link
Contributor Author

lokanandaprabhu commented Jun 3, 2025

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jun 3, 2025

@lokanandaprabhu: An error was encountered updating to the POST state for bug OCPBUGS-56888 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message. No response returned: Post "https://issues.redhat.com/rest/api/2/issue/17020076/transitions": POST https://issues.redhat.com/rest/api/2/issue/17020076/transitions giving up after 5 attempt(s)

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

Details

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.

@lokanandaprabhu
Copy link
Contributor Author

lokanandaprabhu commented Jun 3, 2025

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

openshift-ci-robot commented Jun 3, 2025

@lokanandaprabhu: This pull request references Jira Issue OCPBUGS-56888, 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-56889 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-56889 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
  • bug has dependents
Details

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.

@lokanandaprabhu
Copy link
Contributor Author

lokanandaprabhu commented Jun 3, 2025

/cc @vikram-raj

@openshift-ci openshift-ci bot requested a review from vikram-raj June 3, 2025 06:17
vikram-raj
vikram-raj reviewed Jun 3, 2025
View reviewed changes
Copy link
Member

@vikram-raj vikram-raj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 3, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lokanandaprabhu, vikram-raj

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

@vikram-raj
Copy link
Member

vikram-raj commented Jun 3, 2025

/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 Jun 3, 2025
@sanketpathak
Copy link
Contributor

sanketpathak commented Jun 5, 2025

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

openshift-ci-robot commented Jun 5, 2025

/retest-required

Remaining retests: 0 against base HEAD 2c71b4d and 2 for PR HEAD 91d69c3 in total

1 similar comment
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jun 6, 2025

/retest-required

Remaining retests: 0 against base HEAD 2c71b4d and 2 for PR HEAD 91d69c3 in total

@lokanandaprabhu
Copy link
Contributor Author

lokanandaprabhu commented Jun 9, 2025

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 9, 2025

@lokanandaprabhu: 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-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 68d2876 into openshift:release-4.19 Jun 9, 2025
7 checks passed
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jun 9, 2025

@lokanandaprabhu: Jira Issue OCPBUGS-56888: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-56888 has been moved to the MODIFIED state.

Details

In response to this:

Manual cherry-pick of #14992 and https://github.com/openshift/console/pull/15101/files

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-bot
Copy link
Contributor

openshift-bot commented Jun 9, 2025

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-console
This PR has been included in build openshift-enterprise-console-container-v4.19.0-202506091116.p0.g68d2876.assembly.stream.el9.
All builds following this will include this PR.

@lokanandaprabhu
Copy link
Contributor Author

lokanandaprabhu commented Jun 9, 2025

/cherrypick release-4.18

@openshift-cherrypick-robot
Copy link

openshift-cherrypick-robot commented Jun 9, 2025

@lokanandaprabhu: new pull request created: #15160

Details

In response to this:

/cherrypick release-4.18

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-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jun 9, 2025
Merged
@openshift-merge-robot
Copy link
Contributor

openshift-merge-robot commented Jun 10, 2025

Fix included in accepted release 4.19.0-0.nightly-2025-06-09-210043

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

Reviewers

@christoph-jerolimov christoph-jerolimov Awaiting requested review from christoph-jerolimov

@Lucifergene Lucifergene Awaiting requested review from Lucifergene

1 more reviewer

@vikram-raj vikram-raj vikram-raj left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

@gouyang gouyang

@vikram-raj vikram-raj

@jrichter1 jrichter1

@ebenahar ebenahar

@yanpzhan yanpzhan

@sanketpathak sanketpathak

@juzhao juzhao

@lihongyan1 lihongyan1

@XiyunZhao XiyunZhao

@Tai-RedHat Tai-RedHat

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. component/pipelines Related to pipelines-plugin 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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.