Closed dulek closed 1 year ago
@dulek: This pull request references Jira Issue OCPBUGS-11993, which is invalid:
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.
/jira refresh
@dulek: 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
.
@dulek: This pull request references Jira Issue OCPBUGS-11993, which is invalid:
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.
@dulek: This pull request references Jira Issue OCPBUGS-11993, which is invalid:
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.
/jira refresh
@dulek: This pull request references Jira Issue OCPBUGS-11993, which is invalid:
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.
/jira refresh
@dulek: This pull request references Jira Issue OCPBUGS-11993, which is valid. The bug has been moved to the POST state.
No GitHub users were found matching the public email listed for the QA contact in Jira (itbrown@redhat.com), skipping review request.
/cherry-pick release-4.11
@dulek: once the present PR merges, I will cherry-pick it on top of release-4.11 in a new PR and assign it to you.
/retest
/retest
/retest
/retest
/label backport-risk-assessed
/retest
/retest
Seems like we have some troubles with Octavia at the Kuryr cloud, overriding. /override ci/prow/e2e-openstack-kuryr
/cc @MaysaMacedo
@dulek: Overrode contexts on behalf of dulek: ci/prow/e2e-openstack-kuryr
@dulek: 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-openstack-kuryr | d3e6b649968e572ad0bc8637a702df36fec02a1e | link | true | /test e2e-openstack-kuryr |
Full PR test history. Your PR dashboard.
/lgtm /label cherry-pick-approved
@MaysaMacedo: Can not set label cherry-pick-approved: Must be member in one of these teams: []
/cc @rlobillo can you check this pr and try applying the cherry-pick-approved label if you see fit?
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dulek, MaysaMacedo
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/label cherry-pick-approved
As stated at the clone in 4.13 https://issues.redhat.com/browse/OCPBUGS-11994, QE verification is not needed for this.
@dulek: Jira Issue OCPBUGS-11993: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-11993 has been moved to the MODIFIED state.
@dulek: new pull request created: #725
[ART PR BUILD NOTIFIER]
This PR has been included in build kuryr-controller-container-v4.12.0-202305022015.p0.g3e5ab43.assembly.stream for distgit kuryr-controller. All builds following this will include this PR.
[ART PR BUILD NOTIFIER]
This PR has been included in build kuryr-cni-container-v4.12.0-202305022015.p0.g3e5ab43.assembly.stream for distgit kuryr-cni. All builds following this will include this PR.
[ART PR BUILD NOTIFIER]
This PR has been included in build kuryr-controller-container-v4.12.0-202305030754.p0.g3e5ab43.assembly.stream for distgit kuryr-controller. All builds following this will include this PR.
[ART PR BUILD NOTIFIER]
This PR has been included in build kuryr-cni-container-v4.12.0-202305030754.p0.g3e5ab43.assembly.stream for distgit kuryr-cni. All builds following this will include this PR.
There's argument number mismatch on release_vif() call while reverting port association. This commit fixes that.