openshift
[release-4.15] OCPBUGS-33283: Adjust NAD name to "network-xxx-xxx" when creating
This is an automated cherry-pick of #13568
/assign gouyang
@openshift-cherrypick-robot: Jira Issue OCPBUGS-22749 has been cloned as Jira Issue OCPBUGS-33283. Will retitle bug to link to clone. /retitle [release-4.15] OCPBUGS-33283: Adjust NAD name to "network-xxx-xxx" when creating
In response to this:
This is an automated cherry-pick of #13568
/assign gouyang
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: This pull request references Jira Issue OCPBUGS-33283, 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"
- expected dependent Jira Issue OCPBUGS-22749 to target a version in 4.16.0, but it targets "4.15.0" 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 #13568
/assign gouyang
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.
@jhadvig: This pull request references Jira Issue OCPBUGS-33283, 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"
- expected dependent Jira Issue OCPBUGS-22749 to target a version in 4.16.0, but it targets "4.15.0" 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 openshift-eng/jira-lifecycle-plugin repository.
@gouyang: This pull request references Jira Issue OCPBUGS-33283, which is invalid:
- expected dependent Jira Issue OCPBUGS-22749 to target a version in 4.16.0, but it targets "4.15.0" 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 openshift-eng/jira-lifecycle-plugin repository.
@gouyang: This pull request references Jira Issue OCPBUGS-33283, which is invalid:
- expected dependent Jira Issue OCPBUGS-22749 to target a version in 4.16.0, but it targets "4.15.0" 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 openshift-eng/jira-lifecycle-plugin repository.
@gouyang: This pull request references Jira Issue OCPBUGS-33283, 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.15.z) matches configured target version for branch (4.15.z)
- 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-22749 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-22749 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
- bug has dependents
Requesting review from QA contact: /cc @yapei
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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jhadvig, openshift-cherrypick-robot, pcbailey
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~frontend/packages/network-attachment-definition-plugin/OWNERS~~ [jhadvig,pcbailey]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
/retest-required
Remaining retests: 0 against base HEAD 157ae85fbb44c518def931e2db590645b49e33be and 2 for PR HEAD 731658a66967127458835ec959208030cb3c0dd3 in total
/retest-required
Remaining retests: 0 against base HEAD 789c888ec459b7b19f36b69ceaaaf3d55288702f and 1 for PR HEAD 731658a66967127458835ec959208030cb3c0dd3 in total
/retest-required
Remaining retests: 0 against base HEAD 9ba26321b269e64f43a284c8071c5994f4d0ba3e and 0 for PR HEAD 731658a66967127458835ec959208030cb3c0dd3 in total
/hold
Revision 731658a66967127458835ec959208030cb3c0dd3 was retested 3 times: holding
@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 | 731658a66967127458835ec959208030cb3c0dd3 | 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-sigs/prow repository. I understand the commands that are listed here.
PR needs rebase.
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.
@metalice it seems the PR cannot pass the e2e-gcp-console test before the conflict was found, could you take a look at this again because there is a request to backport this to 4.15.