console
console copied to clipboard
[release-4.11] OCPBUGS-2515:Change annotation to be used for fake helm repositories
This is an automated cherry-pick of #12141
/assign Kartikey-star
@openshift-cherrypick-robot: Jira Issue OCPBUGS-2344 has been cloned as Jira Issue OCPBUGS-2515. Retitling PR to link against new bug. /retitle [release-4.11] OCPBUGS-2515:Change annotation to be used for fake helm repositories
In response to this:
This is an automated cherry-pick of #12141
/assign Kartikey-star
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: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh
.
In response to this:
[release-4.11] OCPBUGS-2515:Change annotation to be used for fake helm repositories
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-2515, which is invalid:
- expected dependent Jira Issue OCPBUGS-2344 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is ON_QA 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:
This is an automated cherry-pick of #12141
/assign Kartikey-star
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.
/jira refresh
@Kartikey-star: This pull request references Jira Issue OCPBUGS-2515, which is invalid:
- expected dependent Jira Issue OCPBUGS-2344 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is ON_QA 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.
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 kubernetes/test-infra repository.
/retest
/retest
/assign @jhadvig
Jakub, this change is to get an error string returned from the helm backend when it can not access one or more helm chart repos. @debsmita1 is working on frontend code that will show this annotation and we will backport this as well.
@jerolimov the frontend code will be also backported ?
@jhadvig Yes (it's not part of master yet, it's WIP, but we will backport it as well)
/jira-refresh
/jira refresh
@Kartikey-star: This pull request references Jira Issue OCPBUGS-2515, 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.11.z) matches configured target version for branch (4.11.z)
- bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
- dependent bug Jira Issue OCPBUGS-2344 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
- dependent Jira Issue OCPBUGS-2344 targets the "4.12.0" version, which is one of the valid target versions: 4.12.0
- bug has dependents
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 kubernetes/test-infra repository.
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jerolimov, jhadvig, Kartikey-star, openshift-cherrypick-robot
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~pkg/helm/OWNERS~~ [Kartikey-star,jhadvig]
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment
This PR has been tested with private build (launch 4.11.0-0.nightly-2022-10-24-182851,openshift/console#12182) Verification Step:
- Login OCP as administrator
- Go to developer perspective -> Helm page
- Create a fake help repository (Click "Install a Helm Chart from the developer catalog" -> Click the link of "try to configure their own custom Helm Chart repository." on Helm Charts page -> provide name: testhelm and URL: http://github.test.com as an example)
- Go back to Helm Chart page again
- Check the API response on the Network of the Browser
- Re-login OCP as a normal user, do steps 2-5 again Result:
- A request could be caught by the Network of Browser, and the annotations of "console-waring: The following repositories seem to be invalid or unreachable:" would be found on the Response
/label qe-approved
/label cherry-pick-approved
/retest
/retest
/retest
@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: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-2515 has been moved to the MODIFIED state.
In response to this:
This is an automated cherry-pick of #12141
/assign Kartikey-star
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.