Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-4.7] Bug 1932383: Connect default NIC to cluster network #2427

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #2384

/assign pliurh

Connect default NIC to cluster network, if it is not triggered automantically.
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Bugzilla bug 1922997 has been cloned as Bugzilla bug 1932383. Retitling PR to link against new bug.
/retitle [release-4.7] Bug 1932383: Connect default NIC to cluster network

In response to this:

[release-4.7] Bug 1922997: Connect default NIC to cluster network

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-robot openshift-ci-robot changed the title [release-4.7] Bug 1922997: Connect default NIC to cluster network [release-4.7] Bug 1932383: Connect default NIC to cluster network Feb 24, 2021
@openshift-ci-robot openshift-ci-robot added the bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. label Feb 24, 2021
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Bugzilla bug 1932383, which is invalid:

  • expected dependent Bugzilla bug 1922997 to be in one of the following states: MODIFIED, VERIFIED, but it is ON_QA 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.7] Bug 1932383: Connect default NIC to cluster network

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-robot openshift-ci-robot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Feb 24, 2021
@kikisdeliveryservice kikisdeliveryservice added the 4.7 Work deferred for 4.7 label Feb 25, 2021
@pliurh
Copy link
Contributor

pliurh commented Mar 2, 2021

/retest

@pliurh
Copy link
Contributor

pliurh commented Mar 2, 2021

/bugzilla refresh

@openshift-ci-robot
Copy link
Contributor

@pliurh: This pull request references Bugzilla bug 1932383, 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.7.z) matches configured target release for branch (4.7.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1922997 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1922997 targets the "4.8.0" release, which is one of the valid target releases: 4.8.0
  • bug has dependents

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.

@openshift-ci-robot openshift-ci-robot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Mar 2, 2021
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 5, 2021
@pliurh
Copy link
Contributor

pliurh commented Mar 8, 2021

/retest

7 similar comments
@pliurh
Copy link
Contributor

pliurh commented Mar 8, 2021

/retest

@pliurh
Copy link
Contributor

pliurh commented Mar 9, 2021

/retest

@pliurh
Copy link
Contributor

pliurh commented Mar 12, 2021

/retest

@pliurh
Copy link
Contributor

pliurh commented Mar 15, 2021

/retest

@pliurh
Copy link
Contributor

pliurh commented Mar 16, 2021

/retest

@pliurh
Copy link
Contributor

pliurh commented Mar 17, 2021

/retest

@pliurh
Copy link
Contributor

pliurh commented Apr 8, 2021

/retest

@pliurh
Copy link
Contributor

pliurh commented Apr 9, 2021

/retest

1 similar comment
@pliurh
Copy link
Contributor

pliurh commented Apr 12, 2021

/retest

@kikisdeliveryservice
Copy link
Contributor

jobs are red and not reqd for merging

/skip

@kikisdeliveryservice
Copy link
Contributor

/assign @rbbratta

@pliurh
Copy link
Contributor

pliurh commented Apr 23, 2021

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 23, 2021
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, pliurh, sinnykumari

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@bparees bparees added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Apr 28, 2021
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

4 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 30, 2021

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws-single-node 4cf03fb link /test e2e-aws-single-node
ci/prow/okd-e2e-gcp-op 4cf03fb link /test okd-e2e-gcp-op
ci/prow/okd-e2e-upgrade 4cf03fb link /test okd-e2e-upgrade

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-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit b20ecdc into openshift:release-4.7 May 1, 2021
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

Bugzilla bug 1932383 has been moved to the MODIFIED state.

In response to this:

[release-4.7] Bug 1932383: Connect default NIC to cluster network

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4.7 Work deferred for 4.7 approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants