Skip to content

Bug 1823557: backport fixes to support upstream->downstream merges#589

Closed
dcbw wants to merge 2 commits intoopenshift:release-4.4from
dcbw:44-support-upstream
Closed

Bug 1823557: backport fixes to support upstream->downstream merges#589
dcbw wants to merge 2 commits intoopenshift:release-4.4from
dcbw:44-support-upstream

Conversation

@dcbw
Copy link
Contributor

@dcbw dcbw commented Apr 13, 2020

Backports of #466, #467, and #572 . These are needed to make nbctl daemon mode work while at the same time being able to check local OVS database to figure out if SCTP is supported by OVN.

@trozet @knobunc @fepan @openshift/networking

@openshift-ci-robot
Copy link
Contributor

@dcbw: 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.

Details

In response to this:

Backport fixes to support upstream->downstream merges

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.

@dcbw
Copy link
Contributor Author

dcbw commented Apr 13, 2020

/test e2e-aws-ovn

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dcbw

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

The pull request process is described here

Details 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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 13, 2020
@openshift-ci-robot
Copy link
Contributor

@dcbw: 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.

Details

In response to this:

Backport fixes to support upstream->downstream merges

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.

@dcbw
Copy link
Contributor Author

dcbw commented Apr 13, 2020

/retest

@dcbw dcbw changed the title Backport fixes to support upstream->downstream merges Bug 1811811: backport fixes to support upstream->downstream merges Apr 13, 2020
@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 Apr 13, 2020
@openshift-ci-robot
Copy link
Contributor

@dcbw: This pull request references Bugzilla bug 1811811, which is invalid:

  • expected the bug to target the "4.4.0" release, but it targets "4.5.0" instead
  • expected Bugzilla bug 1811811 to depend on a bug targeting a release in 4.5.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), 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.

Details

In response to this:

Bug 1811811: backport fixes to support upstream->downstream merges

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.

@dcbw dcbw changed the title Bug 1811811: backport fixes to support upstream->downstream merges Bug 1823557: backport fixes to support upstream->downstream merges Apr 13, 2020
@openshift-ci-robot
Copy link
Contributor

@dcbw: This pull request references Bugzilla bug 1823557, which is invalid:

  • expected dependent Bugzilla bug 1718372 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
  • expected dependent Bugzilla bug 1811815 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
  • expected dependent Bugzilla bug 1718372 to target a release in 4.5.0, but it targets "---" 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.

Details

In response to this:

Bug 1823557: backport fixes to support upstream->downstream merges

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.

@dcbw
Copy link
Contributor Author

dcbw commented Apr 13, 2020

/bugzilla refresh

@openshift-ci-robot
Copy link
Contributor

@dcbw: This pull request references Bugzilla bug 1823557, which is invalid:

  • expected dependent Bugzilla bug 1718372 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
  • expected dependent Bugzilla bug 1811815 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
  • expected dependent Bugzilla bug 1718372 to target a release in 4.5.0, but it targets "---" 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.

Details

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.

@dcbw
Copy link
Contributor Author

dcbw commented Apr 13, 2020

/bugzilla refresh

@openshift-ci-robot
Copy link
Contributor

@dcbw: This pull request references Bugzilla bug 1823557, which is invalid:

  • expected dependent Bugzilla bug 1811815 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), 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.

Details

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.

@trozet
Copy link
Contributor

trozet commented Apr 13, 2020

@dcbw I already have a bz and pr approved for 4.4 ssl fix

alexanderConstantinescu and others added 2 commits April 14, 2020 09:00
Completes the switch from ovn2.11 to ovn2.12 by removing support for the
now obsolete ovn2.11

SDN-643
https://issues.redhat.com/browse/SDN-643

Signed-off-by: Phil Cameron <pcameron@redhat.com>
(cherry picked from commit f479a53)
@dcbw dcbw force-pushed the 44-support-upstream branch from fe4b958 to 170f892 Compare April 14, 2020 14:04
@dcbw
Copy link
Contributor Author

dcbw commented Apr 14, 2020

@trozet and I see that merged; which is great. So this is now just the other cleanups.

@squeed
Copy link
Contributor

squeed commented Jun 24, 2020

@dcbw do we still need this?

@openshift-ci-robot
Copy link
Contributor

@dcbw: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-gcp 170f892 link /test e2e-gcp
ci/prow/e2e-gcp-upgrade 170f892 link /test e2e-gcp-upgrade
ci/prow/images 170f892 link /test images
ci/prow/verify 170f892 link /test verify
ci/prow/unit 170f892 link /test unit
ci/prow/e2e-gcp-ovn 170f892 link /test e2e-gcp-ovn
ci/prow/e2e-upgrade 170f892 link /test e2e-upgrade

Full PR test history. Your PR dashboard.

Details

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.

@squeed
Copy link
Contributor

squeed commented Oct 14, 2020

Closing this for now; @dcbw reopen if you like.

@squeed squeed closed this Oct 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants