openshift
[release-4.14] OCPBUGS-33752: Deploy dual stack with IPv6 on top of bond/vlan fails
This is an automated cherry-pick of #6245
/assign gamli75
@openshift-cherrypick-robot: Jira Issue OCPBUGS-32972 has been cloned as Jira Issue OCPBUGS-33753. Will retitle bug to link to clone. /retitle [release-4.14] OCPBUGS-33753: Deploy dual stack with IPv6 on top of bond/vlan fails
In response to this:
This is an automated cherry-pick of #6245
/assign gamli75
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-33753, 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-32972 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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 #6245
/assign gamli75
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.
/retitle [release-4.14] OCPBUGS-33752: Deploy dual stack with IPv6 on top of bond/vlan fails
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-33752, which is invalid:
- expected the bug to target either version "4.14." or "openshift-4.14.", but it targets "4.15.z" instead
- expected dependent Jira Issue OCPBUGS-31631 to target a version in 4.15.0, 4.15.z, but it targets "4.16.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 #6245
/assign gamli75
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.
@gamli75: This pull request references Jira Issue OCPBUGS-33752, which is invalid:
- expected the bug to target either version "4.14." or "openshift-4.14.", but it targets "4.15.z" instead
- expected dependent Jira Issue OCPBUGS-31631 to target a version in 4.15.0, 4.15.z, but it targets "4.16.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.
@gamli75: This pull request references Jira Issue OCPBUGS-33752, which is invalid:
- expected dependent Jira Issue OCPBUGS-31631 to target a version in 4.15.0, 4.15.z, but it targets "4.16.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.
@openshift-cherrypick-robot: 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-sigs/prow repository. I understand the commands that are listed here.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: gamli75, openshift-cherrypick-robot
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [gamli75]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/label backport-risk-assesed @gamli75 it looks like you linked this 4.14 PR to the 4.15 bug, closed the 4.14 bug, and retargeted the 4.15 bug to 4.14.z after the 4.15 bug had merged. So the bot is not going to be happy. You'll want to put things back how the cherry-pick bot had it.
@zaneb: The label(s) /label backport-risk-assesed cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?
In response to this:
/label backport-risk-assesed @gamli75 it looks like you linked this 4.14 PR to the 4.15 bug, closed the 4.14 bug, and retargeted the 4.15 bug to 4.14.z after the 4.15 bug had merged. So the bot is not going to be happy. You'll want to put things back how the cherry-pick bot had it.
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.
@gamli75: This pull request references Jira Issue OCPBUGS-33752, which is invalid:
- expected dependent Jira Issue OCPBUGS-31631 to target a version in 4.15.0, 4.15.z, but it targets "4.16.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.
@gamli75: This pull request references Jira Issue OCPBUGS-33752, which is invalid:
- expected dependent Jira Issue OCPBUGS-31631 to target a version in 4.15.0, 4.15.z, but it targets "4.16.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.
@gamli75: This pull request references Jira Issue OCPBUGS-33752, which is invalid:
- expected dependent Jira Issue OCPBUGS-31631 to target a version in 4.15.0, 4.15.z, but it targets "4.16.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.
@gamli75: This pull request references Jira Issue OCPBUGS-33752, which is valid.
7 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.14.z) matches configured target version for branch (4.14.z)
- bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
- release note type set to "Release Note Not Required"
- dependent bug Jira Issue OCPBUGS-31631 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
- dependent Jira Issue OCPBUGS-31631 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
- bug has dependents
No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.
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.
@openshift-cherrypick-robot: Jira Issue OCPBUGS-33752: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-33752 has been moved to the MODIFIED state.
In response to this:
This is an automated cherry-pick of #6245
/assign gamli75
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.
[ART PR BUILD NOTIFIER]
This PR has been included in build ose-agent-installer-api-server-container-v4.14.0-202405210637.p0.g5861f06.assembly.stream.el8 for distgit ose-agent-installer-api-server. All builds following this will include this PR.
