fix(nmcli): remove bond from ip_conn_type

[joey-grant]

SUMMARY

Removes bond connection types from the ip_conn_type list. Currently, with bond connections being included in the ip_conn_type list, the resulting nmcli commands include references to ipv4 and ipv6 settings. These options are not available to bond connection types as stated by the error output in issue #8558.

Fixes #8558

ISSUE TYPE

Bugfix Pull Request

COMPONENT NAME

nmcli

ADDITIONAL INFORMATION

# before change

TASK [Setup bond interface for - internal] ***********************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error: invalid or not allowed setting 'ipv4': 'ipv4' not among [connection, bond, 802-3-ethernet (ethernet), ethtool, bridge-port, link, match].\n", "name": "bond-internal", "rc": 2}


# after change

TASK [Setup bond interface for - internal] ***********************************************************************************
ok: [localhost]

[ansibullbot]

cc @alcamie101
click here for bot help

[felixfontein]

Thanks for your contribution!

[felixfontein]

Suggested change

	- "nmcli - corrects underlying command formation by no longer including ``ipv4.*`` and ``ipv6.*`` settings when working with ``bond`` connection types (https://github.com/ansible-collections/community.general/issues/8558)."
	- "nmcli - corrects underlying command formation by no longer including ``ipv4.*`` and ``ipv6.*`` settings when working with ``bond`` connection types (https://github.com/ansible-collections/community.general/issues/8558, https://github.com/ansible-collections/community.general/pull/8729)."

[felixfontein]

It seems like this was different in the past, since at least some ipv4/ipv6 settings were intentionally passed on for bond interfaces in the past. (https://github.com/ansible-collections/community.general/pull/1113/files#diff-0beb963c40c22c48521d124bde17191aa121555e97ddf206ea1cd82f5d68941cL882)

[joey-grant]

It seems like this was different in the past, since at least some ipv4/ipv6 settings were intentionally passed on for bond interfaces in the past. (https://github.com/ansible-collections/community.general/pull/1113/files#diff-0beb963c40c22c48521d124bde17191aa121555e97ddf206ea1cd82f5d68941cL882)

Thanks for the feedback. I have marked this as a draft. This is looking/feeling more like a workflow problem instead of requiring the solution I proposed. Following a process such as the one described here results in ipv4.* and ipv6.* options being available to a bond type.

[rabin-io]

So regarding issue #8558, you think it can be resolved by refactoring the steps in the playbook?
(end result should be bonding 2 interface > and the bond should be attached to bridge with IP's)