-
Notifications
You must be signed in to change notification settings - Fork 222
USHIFT-6141: SR-IOV RF smoke test #5796
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
@vanhalenar: This pull request references USHIFT-6141 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.21.0" version, but no target version was set. In 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. |
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: vanhalenar The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test ? |
|
@vanhalenar: The following commands are available to trigger required jobs: The following commands are available to trigger optional jobs: Use In 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. |
|
/test e2e-aws-tests-bootc |
|
/test e2e-aws-tests-bootc |
|
@vanhalenar: This pull request references USHIFT-6141 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.21.0" version, but no target version was set. In 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. |
|
/test e2e-aws-tests-bootc |
|
/test e2e-aws-tests-bootc |
|
/test e2e-aws-tests-bootc |
|
@vanhalenar: This pull request references USHIFT-6141 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.21.0" version, but no target version was set. In 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. |
|
/test e2e-aws-tests-bootc |
|
@vanhalenar: The following test failed, say
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. |
test/suites/optional/sriov.robot
Outdated
| Create VFs And Verify | ||
| [Documentation] Deploys sriovnetworknodepolicy and verifies the VF configuration | ||
| VAR ${testcmd}= oc get sriovnetworknodestate -o yaml -n sriov-network-operator -o json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| VAR ${testcmd}= oc get sriovnetworknodestate -o yaml -n sriov-network-operator -o json | |
| VAR ${testcmd}= oc get sriovnetworknodestate -n sriov-network-operator -o json |
because you already have -o json this change won't affect the behaviour
test/suites/optional/sriov.robot
Outdated
| VAR ${testcmd}= oc get sriovnetworknodestate -o yaml -n sriov-network-operator -o json | ||
| Run With Kubeconfig ${testcmd} | ||
| VAR ${cmd}= | ||
| ... oc get sriovnetworknodestate -o yaml -n sriov-network-operator -o json | jq -r '.items[].status.interfaces[0].pciAddress' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| ... oc get sriovnetworknodestate -o yaml -n sriov-network-operator -o json | jq -r '.items[].status.interfaces[0].pciAddress' | |
| ... oc get sriovnetworknodestate -n sriov-network-operator -o json | jq -r '.items[].status.interfaces[0].pciAddress' |
| prepare_kickstart host1 kickstart-bootc.ks.template rhel96-bootc-source-optionals | ||
| # Two nics - one for macvlan, another for ipvlan (they cannot enslave the same interface) | ||
| launch_vm --boot_blueprint rhel96-bootc --network "${VM_MULTUS_NETWORK},${VM_MULTUS_NETWORK}" | ||
| launch_vm --boot_blueprint rhel96-bootc --network "sriov,${VM_MULTUS_NETWORK},${VM_MULTUS_NETWORK}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's use a variable for sriov network name?
This test is deploying a NetworkNodePolicy and checking if the VFs are configured correctly.