-
Notifications
You must be signed in to change notification settings - Fork 112
ci: Add an additional NIC for test purposes #762
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
Conversation
2968a18 to
878207d
Compare
94a3e52 to
bf0c783
Compare
bf0c783 to
b477173
Compare
.github/workflows/tft.yml
Outdated
| api_key: ${{ secrets.TF_API_KEY_RH }} | ||
| update_pull_request_status: false | ||
| tmt_hardware: '{ "memory": ">= ${{ needs.prepare_vars.outputs.memory }} MB" }' | ||
| tmt_hardware: '{ "memory": ">= ${{ needs.prepare_vars.outputs.memory }} MB", "network": [{"type": "eth"},{"type": "eth"}] }' |
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.
what is the NIC name or how can we tell from the config ?
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.
When I tested it interfaces were eth0 and eth1.
tmt docs list 5 parameters for network: type, device-name, device, vendor-name, vendor, driver. Maybe it may help to provide some of these to make setup more specific.
b477173 to
980fb58
Compare
| api_key: ${{ secrets.TF_API_KEY_RH }} | ||
| update_pull_request_status: false | ||
| tmt_hardware: '{ "memory": ">= ${{ needs.prepare_vars.outputs.memory }} MB" }' | ||
| tmt_hardware: '{ "memory": ">= ${{ needs.prepare_vars.outputs.memory }} MB", "network": [{"type": "eth", "device-name": "eth0"}, {"type": "eth", "device-name": "eth1"}] }' |
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.
@liangwen12year does this work?
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.
We've tested it with Wen in TF and it seems to be working. Will see how TF action likes this syntax.
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.
I pair-programmed with @spetrosi on a testing farm machine using the following command, and it works as expected.
ip a
nmcli c
nmcli d
ethtool -P eth0
cat /sys/class/net/eth0/address
ethtool -P eth1
cat /sys/class/net/eth1/address
| api_key: ${{ secrets.TF_API_KEY_RH }} | ||
| update_pull_request_status: false | ||
| tmt_hardware: '{ "memory": ">= ${{ needs.prepare_vars.outputs.memory }} MB" }' | ||
| tmt_hardware: '{ "memory": ">= ${{ needs.prepare_vars.outputs.memory }} MB", "network": [{"type": "eth", "device-name": "eth0"}, {"type": "eth", "device-name": "eth1"}] }' |
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.
The commit message is a bit confusing, it is not adding two NICs , you only added 1 additional NIC, eth0 is still the default device for bridging the ssh connection between the control node and the managed host. Can you change the commit message to ci: Configure two NICs for testing purposes ?
Signed-off-by: Sergei Petrosian <spetrosi@redhat.com>
980fb58 to
0b6a266
Compare
No description provided.