Skip to content

[release-4.10] Bug 2048836: Use ip command to check for ipv6 addresses - #2938

Merged
openshift-merge-robot merged 1 commit into
openshift:release-4.10from
openshift-cherrypick-robot:cherry-pick-2934-to-release-4.10
Feb 1, 2022
Merged

[release-4.10] Bug 2048836: Use ip command to check for ipv6 addresses#2938
openshift-merge-robot merged 1 commit into
openshift:release-4.10from
openshift-cherrypick-robot:cherry-pick-2934-to-release-4.10

Conversation

@openshift-cherrypick-robot

Copy link
Copy Markdown

This is an automated cherry-pick of #2934

/assign aravindhp

For some reason the nmcli call to determine the number of ipv6
addresses on an interface is sometimes returning a blank line as
part of the output. This causes a single address to look like 2
because we're just checking the line count and makes us incorrectly
set "ipv6.may-fail no" on the interface. This causes the connection
to fail and prevents ovs-configuration from completing.

Here's some example output from an affected system:

[root@master-0-0 core]# nmcli -m multiline --get-values ip6.address conn show 84a523ff-ee8a-4a29-94ca-47590eb0cb76
IP6.ADDRESS[1]:fe80::5054:ff:fe6e:6923/64

[root@master-0-0 core]#

Additionally, we have seen another case where the link-local address
from both the baremetal and provisioning networks shows up in the
output of this command. That will also fail because we're just
looking for line count > 1.

This change modifies the check to use the ip command on the interface
directly, so we should only get the addresses on the interface itself
and we can use jq to filter out the ones we're not interested in.
Although the bug specifically related to ipv6 addresses, in theory
a similar issue could exist for ipv4 so that check is also converted.
@openshift-ci

openshift-ci Bot commented Jan 31, 2022

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: Bugzilla bug 2047445 has been cloned as Bugzilla bug 2048836. Retitling PR to link against new bug.
/retitle [release-4.10] Bug 2048836: Use ip command to check for ipv6 addresses

Details

In response to this:

[release-4.10] Bug 2047445: Use ip command to check for ipv6 addresses

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 openshift-ci Bot changed the title [release-4.10] Bug 2047445: Use ip command to check for ipv6 addresses [release-4.10] Bug 2048836: Use ip command to check for ipv6 addresses Jan 31, 2022
@openshift-ci openshift-ci Bot added bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent 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. labels Jan 31, 2022
@openshift-ci

openshift-ci Bot commented Jan 31, 2022

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2048836, 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.10.0) matches configured target release for branch (4.10.0)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2047445 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Bugzilla bug 2047445 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
  • bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

Details

In response to this:

[release-4.10] Bug 2048836: Use ip command to check for ipv6 addresses

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.

@kikisdeliveryservice

Copy link
Copy Markdown
Contributor

/approve

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 1, 2022
@trozet

trozet commented Feb 1, 2022

Copy link
Copy Markdown
Contributor

/test e2e-metal-ipi-ovn-dualstack

@trozet

trozet commented Feb 1, 2022

Copy link
Copy Markdown
Contributor

/test e2e-ovn-step-registry

@trozet

trozet commented Feb 1, 2022

Copy link
Copy Markdown
Contributor

patch worked correctly on ci/prow/e2e-ovn-step-registry. dualstack didn't get far enough

/test ci/prow/e2e-ovn-step-registry
/test ci/prow/e2e-metal-ipi-ovn-dualstack

@openshift-ci

openshift-ci Bot commented Feb 1, 2022

Copy link
Copy Markdown
Contributor

@trozet: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test cluster-bootimages
  • /test e2e-agnostic-upgrade
  • /test e2e-aws
  • /test e2e-gcp-op
  • /test images
  • /test okd-images
  • /test unit
  • /test verify

The following commands are available to trigger optional jobs:

  • /test bootstrap-unit
  • /test e2e-aws-disruptive
  • /test e2e-aws-proxy
  • /test e2e-aws-serial
  • /test e2e-aws-single-node
  • /test e2e-aws-upgrade
  • /test e2e-aws-upgrade-single-node
  • /test e2e-aws-workers-rhel7
  • /test e2e-aws-workers-rhel8
  • /test e2e-azure
  • /test e2e-azure-upgrade
  • /test e2e-gcp-op-single-node
  • /test e2e-gcp-single-node
  • /test e2e-gcp-upgrade
  • /test e2e-metal-assisted
  • /test e2e-metal-ipi
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-ovn-ipv6
  • /test e2e-openstack
  • /test e2e-openstack-parallel
  • /test e2e-ovirt
  • /test e2e-ovirt-upgrade
  • /test e2e-ovn-step-registry
  • /test e2e-vsphere
  • /test e2e-vsphere-upgrade
  • /test e2e-vsphere-upi
  • /test okd-e2e-aws
  • /test okd-e2e-gcp-op
  • /test okd-e2e-upgrade
  • /test okd-e2e-vsphere

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-machine-config-operator-release-4.10-bootstrap-unit
  • pull-ci-openshift-machine-config-operator-release-4.10-e2e-agnostic-upgrade
  • pull-ci-openshift-machine-config-operator-release-4.10-e2e-aws
  • pull-ci-openshift-machine-config-operator-release-4.10-e2e-aws-disruptive
  • pull-ci-openshift-machine-config-operator-release-4.10-e2e-aws-serial
  • pull-ci-openshift-machine-config-operator-release-4.10-e2e-aws-single-node
  • pull-ci-openshift-machine-config-operator-release-4.10-e2e-aws-upgrade-single-node
  • pull-ci-openshift-machine-config-operator-release-4.10-e2e-aws-workers-rhel7
  • pull-ci-openshift-machine-config-operator-release-4.10-e2e-aws-workers-rhel8
  • pull-ci-openshift-machine-config-operator-release-4.10-e2e-gcp-op
  • pull-ci-openshift-machine-config-operator-release-4.10-e2e-gcp-op-single-node
  • pull-ci-openshift-machine-config-operator-release-4.10-e2e-metal-ipi
  • pull-ci-openshift-machine-config-operator-release-4.10-e2e-ovn-step-registry
  • pull-ci-openshift-machine-config-operator-release-4.10-e2e-vsphere-upgrade
  • pull-ci-openshift-machine-config-operator-release-4.10-images
  • pull-ci-openshift-machine-config-operator-release-4.10-okd-e2e-aws
  • pull-ci-openshift-machine-config-operator-release-4.10-okd-e2e-gcp-op
  • pull-ci-openshift-machine-config-operator-release-4.10-okd-e2e-upgrade
  • pull-ci-openshift-machine-config-operator-release-4.10-okd-images
  • pull-ci-openshift-machine-config-operator-release-4.10-unit
  • pull-ci-openshift-machine-config-operator-release-4.10-verify
Details

In response to this:

patch worked correctly on ci/prow/e2e-ovn-step-registry. dualstack didn't get far enough

/test ci/prow/e2e-ovn-step-registry
/test ci/prow/e2e-metal-ipi-ovn-dualstack

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

trozet commented Feb 1, 2022

Copy link
Copy Markdown
Contributor

/test e2e-ovn-step-registry
/test e2e-metal-ipi-ovn-dualstack

@openshift-ci

openshift-ci Bot commented Feb 1, 2022

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: The following tests 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-aws-workers-rhel7 5e16f58 link false /test e2e-aws-workers-rhel7
ci/prow/okd-e2e-gcp-op 5e16f58 link false /test okd-e2e-gcp-op
ci/prow/e2e-vsphere-upgrade 5e16f58 link false /test e2e-vsphere-upgrade
ci/prow/e2e-gcp-op-single-node 5e16f58 link false /test e2e-gcp-op-single-node
ci/prow/e2e-metal-ipi 5e16f58 link false /test e2e-metal-ipi
ci/prow/e2e-aws-workers-rhel8 5e16f58 link false /test e2e-aws-workers-rhel8
ci/prow/okd-e2e-upgrade 5e16f58 link false /test okd-e2e-upgrade
ci/prow/e2e-aws-upgrade-single-node 5e16f58 link false /test e2e-aws-upgrade-single-node
ci/prow/e2e-aws-disruptive 5e16f58 link false /test e2e-aws-disruptive
ci/prow/e2e-aws-single-node 5e16f58 link false /test e2e-aws-single-node

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.

@trozet

trozet commented Feb 1, 2022

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Feb 1, 2022
@vvoronkov

Copy link
Copy Markdown

/label cherry-pick-approved

@openshift-ci openshift-ci Bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Feb 1, 2022

@knobunc knobunc left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@knobunc knobunc added the staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). label Feb 1, 2022
@openshift-ci

openshift-ci Bot commented Feb 1, 2022

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kikisdeliveryservice, knobunc, openshift-cherrypick-robot, trozet

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:
  • OWNERS [kikisdeliveryservice]

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

@openshift-merge-robot
openshift-merge-robot merged commit 14a1ca2 into openshift:release-4.10 Feb 1, 2022
@openshift-ci

openshift-ci Bot commented Feb 1, 2022

Copy link
Copy Markdown
Contributor

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

Bugzilla bug 2048836 has been moved to the MODIFIED state.

Details

In response to this:

[release-4.10] Bug 2048836: Use ip command to check for ipv6 addresses

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

approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent 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. staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead).

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants