[release-4.10] Bug 2057674: Custom imagepullsecret reference information not found when creating pod using console in openshift
This is an automated cherry-pick of #11058
/assign jhadvig
@openshift-cherrypick-robot: Bugzilla bug 2042710 has been cloned as Bugzilla bug 2057674. Retitling PR to link against new bug. /retitle [release-4.10] Bug 2057674: Custom imagepullsecret reference information not found when creating pod using console in openshift
In response to this:
[release-4.10] Bug 2042710: Custom imagepullsecret reference information not found when creating pod using console in openshift
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 Bugzilla bug 2057674, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.
6 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target release (4.10.0) matches configured target release for branch (4.10.0)
- bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
- dependent bug Bugzilla bug 2042710 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
- dependent Bugzilla bug 2042710 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
- bug has dependents
Requesting review from QA contact: /cc @yapei
In response to this:
[release-4.10] Bug 2057674: Custom imagepullsecret reference information not found when creating pod using console in openshift
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
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
Rotten issues close after 30d 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-bot: Closed this PR.
In response to this:
Rotten issues close after 30d 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/test-infra repository.
@openshift-cherrypick-robot: This pull request references Bugzilla bug 2057674. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state. Warning: Failed to comment on Bugzilla bug with reason for changed state.
In response to this:
[release-4.10] Bug 2057674: Custom imagepullsecret reference information not found when creating pod using console in openshift
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 Bugzilla bug 2057674, which is invalid:
- expected the bug to target the "4.10.z" release, but it targets "4.10.0" instead
- expected dependent Bugzilla bug 2042710 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
[release-4.10] Bug 2057674: Custom imagepullsecret reference information not found when creating pod using console in openshift
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.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please ask for approval from jhadvig by writing /assign @jhadvig in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
- /go/src/github.com/openshift/console/frontend/gui_test_screenshots/cypress/scree (1280x720)
nshots/crud/resource-crud.spec.ts/Kubernetes resource CRUD operations -- Persist
entVolume -- edits the resource instance (failed).png
- /go/src/github.com/openshift/console/frontend/gui_test_screenshots/cypress/scree (1280x720)
nshots/crud/resource-crud.spec.ts/Kubernetes resource CRUD operations -- Persist
entVolume -- edits the resource instance (failed) (attempt 2).png
/retest
@openshift-cherrypick-robot: 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/e2e-gcp-console | eeca4dc4c5870aa00fcf52e0e9dbabfe50c750fc | link | true | /test e2e-gcp-console |
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.
Rotten issues close after 30d 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-bot: Closed this PR.
In response to this:
Rotten issues close after 30d 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/test-infra repository.
@openshift-cherrypick-robot: An error was encountered removing this pull request from the external tracker bugs for bug 2057674 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details.
Full error message.
response code 400 not 200
Please contact an administrator to resolve this issue, then request a bug refresh with /bugzilla refresh.
In response to this:
[release-4.10] Bug 2057674: Custom imagepullsecret reference information not found when creating pod using console in openshift
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.