Skip to content

Conversation

vyzigold
Copy link
Contributor

Turns out IPSets use the node's hostname as defined in the nodeset CR, not the node's name. These 2 might be the same, but they might differ and in case they differ, the controller doesn't find them and it uses the ansible inventory secret to get the IPs instead.

Unfortunatelly the hostname from the nodeset isn't always copied into the ansible inventory secret. It either gets copied into the canonical_hostname variable as is or a DNS domain is appended to it, so I introduced a bit of code to pick the correct parts of the canonical_hostname.

This worked for both cases described above when I tested it, there is also still the fallback to using the ansibleHost from the inventory secret.

Copy link
Contributor

openshift-ci bot commented Dec 19, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vyzigold

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Turns out IPSets use the node's hostname as defined in the
nodeset CR, not the node's name. These 2 might be the same, but
they might differ and in case they differ, the controller
doesn't find them and it uses the ansible inventory secret to get
the IPs instead.

Unfortunatelly the hostname from the nodeset isn't always
copied into the ansible inventory secret. It either gets
copied into the canonical_hostname variable as is or
a DNS domain is appended to it, so I introduced a bit
of code to pick the correct parts of the canonical_hostname.

This worked for both cases described above when I tested it,
there is also still the fallback to using the ansibleHost
from the inventory secret.
@vyzigold
Copy link
Contributor Author

/retest

5 similar comments
@vyzigold
Copy link
Contributor Author

/retest

@vyzigold
Copy link
Contributor Author

/retest

@vyzigold
Copy link
Contributor Author

/retest

@vyzigold
Copy link
Contributor Author

/retest

@vyzigold
Copy link
Contributor Author

vyzigold commented Jan 6, 2025

/retest

@jlarriba
Copy link
Collaborator

jlarriba commented Jan 7, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Jan 7, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 23ac41a into openstack-k8s-operators:main Jan 7, 2025
6 checks passed
@vyzigold
Copy link
Contributor Author

/cherry-pick 18.0-fr1

@openshift-cherrypick-robot

@vyzigold: new pull request created: #590

In response to this:

/cherry-pick 18.0-fr1

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants