openshift
[release-4.14] OCPBUGS-20173: Console should not panic when no response is retrieved for plugin assets
This is an automated cherry-pick of #13166
/assign danielmellado
@openshift-cherrypick-robot: Jira Issue OCPBUGS-19367 has been cloned as Jira Issue OCPBUGS-20173. Will retitle bug to link to clone. /retitle [release-4.14] OCPBUGS-20173: Console should not panic when no response is retrieved for plugin assets
In response to this:
This is an automated cherry-pick of #13166
/assign danielmellado
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-cherrypick-robot: This pull request references Jira Issue OCPBUGS-20173, which is valid. The bug has been moved to the POST state.
6 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.14.0) matches configured target version for branch (4.14.0)
- bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
- dependent bug Jira Issue OCPBUGS-19367 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
- dependent Jira Issue OCPBUGS-19367 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
- bug has dependents
Requesting review from QA contact: /cc @yapei
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
This is an automated cherry-pick of #13166
/assign danielmellado
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-cherrypick-robot: This pull request references Jira Issue OCPBUGS-20173, which is valid.
6 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.14.0) matches configured target version for branch (4.14.0)
- bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
- dependent bug Jira Issue OCPBUGS-19367 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
- dependent Jira Issue OCPBUGS-19367 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
- bug has dependents
Requesting review from QA contact: /cc @yapei
In response to this:
This is an automated cherry-pick of #13166
/assign danielmellado
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.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d 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
@danielmellado: Can not set label cherry-pick-approved: Must be member in one of these teams: []
In response to this:
/label cherry-pick-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.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@danielmellado: GitHub didn't allow me to assign the following users: simonpasquier.
Note that only openshift members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
In response to this:
/assign @simonpasquier
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.
@danielmellado: GitHub didn't allow me to assign the following users: simonpasquier.
Note that only openshift members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
In response to this:
/assign simonpasquier
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.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d 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
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jhadvig, openshift-cherrypick-robot, simonpasquier
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~pkg/OWNERS~~ [jhadvig]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
tested PR with cluster-bot, launch 4.14,openshift/console#13217 metal,ipv6
the monitoring-plugin component worked well, no panic logs found.
/label cherry-pick-approved
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-20173, 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"
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.
In response to this:
This is an automated cherry-pick of #13166
/assign danielmellado
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.
@Tai-RedHat: This pull request references Jira Issue OCPBUGS-20173, 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"
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.
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.
@Tai-RedHat: This pull request references Jira Issue OCPBUGS-20173, 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"
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.
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.
@Tai-RedHat: This pull request references Jira Issue OCPBUGS-20173, which is valid.
7 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.14.z) matches configured target version for branch (4.14.z)
- bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
- release note type set to "Release Note Not Required"
- dependent bug Jira Issue OCPBUGS-19367 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
- dependent Jira Issue OCPBUGS-19367 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0, 4.15.z
- bug has dependents
Requesting review from QA contact: /cc @Tai-RedHat
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.
@openshift-cherrypick-robot: 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.
@openshift-cherrypick-robot: Jira Issue OCPBUGS-20173: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-20173 has been moved to the MODIFIED state.
In response to this:
This is an automated cherry-pick of #13166
/assign danielmellado
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.
[ART PR BUILD NOTIFIER]
This PR has been included in build openshift-enterprise-console-container-v4.14.0-202404280610.p0.gf6808b8.assembly.stream.el8 for distgit openshift-enterprise-console. All builds following this will include this PR.
Fix included in accepted release 4.14.0-0.nightly-2024-04-28-111527
