USHIFT-3001: Add initial RF ipv6 tests - #3658
Conversation
|
@pacevedom: This pull request references USHIFT-3001 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.17.0" version, but no target version was set. DetailsIn response to this:
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-ci-robot
added
the
jira/valid-reference
openshift-ci
Bot
added
the
approved
|
/retest-required |
|
/hold |
openshift-ci
Bot
added
the
do-not-merge/hold
|
/hold cancel |
openshift-ci
Bot
removed
the
do-not-merge/hold
|
/test metal-periodic-test-arm |
| ... Expects RF runner host has opened port 5353 for libvirt zone. | ||
|
|
||
| ${result}= Run Process | ||
| ... avahi-resolve-host-name ${HOSTNAME} |
There was a problem hiding this comment.
I see it returned hello-microshift.cluster.local 2001:db8:ca7:ff::1522. Do think it's possible to have a race condition with another test that would also expose hello-microshift.cluster.local?
Should we check if the IP we got is indeed IPv6?
There was a problem hiding this comment.
Good points, did both.
Use hello-microshift.ipv6.cluster.local to avoid collisions with other tests running at the same time.
|
/lgtm |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pacevedom, pmtk The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required |
|
/test metal-periodic-test-arm |
|
Periodic tests failing because of the crel upgrade issue described here: https://redhat-internal.slack.com/archives/C0310LGMQQY/p1721797490189859 |
|
/override ci/prow/metal-periodic-test |
|
@pacevedom: Overrode contexts on behalf of pacevedom: ci/prow/metal-periodic-test, ci/prow/metal-periodic-test-arm DetailsIn response to this:
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. |
|
@pacevedom: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
3 participants
Which issue(s) this PR addresses:
Closes #