Skip to content

Conversation

@spetrosi
Copy link
Collaborator

@spetrosi spetrosi commented Feb 6, 2025

No description provided.

@spetrosi spetrosi self-assigned this Feb 6, 2025
@spetrosi spetrosi changed the title tft add 2 nics ci: Add two NICs for test purposes Feb 6, 2025
@spetrosi spetrosi force-pushed the tft-add-2-nics branch 2 times, most recently from 94a3e52 to bf0c783 Compare February 6, 2025 12:47
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"}] }'
Copy link
Contributor

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 ?

Copy link
Collaborator Author

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.

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"}] }'
Copy link
Contributor

Choose a reason for hiding this comment

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

@liangwen12year does this work?

Copy link
Collaborator Author

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.

Copy link
Contributor

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"}] }'
Copy link
Contributor

@liangwen12year liangwen12year Feb 7, 2025

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>
@spetrosi spetrosi changed the title ci: Add two NICs for test purposes ci: Add an additional NIC for test purposes Feb 7, 2025
@spetrosi spetrosi merged commit 3dc49b9 into main Feb 7, 2025
22 checks passed
@spetrosi spetrosi deleted the tft-add-2-nics branch February 7, 2025 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants