console
console copied to clipboard
[release-4.10] Bug 2072792: Fetch common templates in a different namespace
Common templates are fetched only in the openshift namespace. if commonTemplateNamespace
is different from 'openshift', add additional templates in the store and get the used template from there
@upalatucci: This pull request references Bugzilla bug 2072792, which is invalid:
- expected Bugzilla bug 2072792 to depend on a bug targeting a release in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found
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 2072792: Fetch common templates in a different namespace
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.
/bugzilla refresh
@upalatucci: This pull request references Bugzilla bug 2072792, 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.z) matches configured target release for branch (4.10.z)
- bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
- dependent bug Bugzilla bug 2102302 is in the state CLOSED (ERRATA), which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
- dependent Bugzilla bug 2102302 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0, 4.11.z
- bug has dependents
Requesting review from QA contact: /cc @gouyang
In response to this:
/bugzilla 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
/label cherry-pick-approved
/label backport-risk-assessed
@gouyang: Can not set label backport-risk-assessed: Must be member in one of these teams: []
In response to this:
/label backport-risk-assessed
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
/lgtm
/retest
/retest
/retest
/retest
/retest
/retest
/label backport-risk-assessed
/retest
it looks the customize wizard is crashed in the test. /retest
it looks the customize wizard is crashed in the test. /retest
Yes! I don't know why. In my cluster, it does not crash
/retest
@upalatucci: 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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: pcbailey, upalatucci
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~frontend/packages/kubevirt-plugin/OWNERS~~ [pcbailey]
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment
@upalatucci: All pull requests linked via external trackers have merged:
Bugzilla bug 2072792 has been moved to the MODIFIED state.
In response to this:
[release-4.10] Bug 2072792: Fetch common templates in a different namespace
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.