-
Notifications
You must be signed in to change notification settings - Fork 92
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
HE: Filter IP addresses based on 'ipv6_deployment' #560
base: master
Are you sure you want to change the base?
Conversation
At the beginning of HE deployment we set the 'ipv6_deployment' fact based on host's address. This var should be the source of truth for whether to use an IPv4 or IPv6 address for the HE VM. Until now we were simply picking up the first address that was reported by 'virsh' and using this throughout the rest of the process. This PR adds filtering of the reported addresses based on the value of 'ipv6_deployment'. Additionally we're picking the first address to make other usages of 'local_vm_ip' nicer. Signed-off-by: Marcin Sobczyk <[email protected]>
/ost he-basic-suite-master el9stream |
var: local_vm_ip_candidates | ||
- name: Select first IPv6 address | ||
ansible.builtin.set_fact: | ||
local_vm_ip: "{{ local_vm_ip_candidates.stdout_lines | ansible.netcommon.ipv6 | first }}" |
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.
ansible.netcommon, is this a new collection?
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.
ah, no, we already depend on it. Thouhg it looks unused until now
/ost he-basic-suite-master el8stream |
it seems it's broken on el8stream too now |
it seems to me that due to the now-functional ipv4 dhcp entry the vm boots with default route on ipv4, which breaks the assumption and route manipulation of he setup |
Same problem happens for IPv4-only deployment. Somehow the bootstrap VM enables and gets IPv6 now |
At the beginning of HE deployment we set the 'ipv6_deployment' fact
based on host's address. This var should be the source of truth for
whether to use an IPv4 or IPv6 address for the HE VM.
Until now we were simply picking up the first address that was reported
by 'virsh' and using this throughout the rest of the process.
This PR adds filtering of the reported addresses based on the value of
'ipv6_deployment'. Additionally we're picking the first address to make
other usages of 'local_vm_ip' nicer.
Signed-off-by: Marcin Sobczyk [email protected]