ipa host names are not properly generated with custom network names
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
In Progress
|
Undecided
|
Unassigned |
Bug Description
When a network has all `name`, `name_lower` and `service_
```yaml
---
# network_data.yaml
- dns_domain: my-external.
name: External
name_lower: overclouda_external
service_
subnets:
overclouda
---
# overcloud_
- name: Controller
count: 1
defaults:
network_config:
default_
- overclouda_external
networks:
- network: ctlplane
vif: true
- network: overclouda_external
- network: overclouda_
- network: overclouda_
- network: overclouda_storage
- network: overclouda_tenant
profile: controller
hostname_format: controller-%index%
```
Then the hosts being generated in freeipa are like:
`controller-
instead of the hostname that is used for freeipa services like `<email address hidden>`:
`controller-
But actually the correct behaviour would have been to be:
`controller-
So I found the underlying issue being this commit [1]. This contradicts how other services define the principal using `fqdn_$NETWORK`, e.g. [2]. I believe we should use the latter in all the other places as well, e.g. [3] which causes the mismatch in ipa of this issue.
[1]: https:/ /review. opendev. org/c/openstack /tripleo- heat-templates/ +/815598 /opendev. org/openstack/ tripleo- heat-templates/ src/commit/ a6576e1c5980b4d dcf292599037eb0 89975aa76f/ deployment/ nova/nova- modular- libvirt- container- puppet. yaml#L781 /opendev. org/openstack/ tripleo- heat-templates/ src/commit/ a6576e1c5980b4d dcf292599037eb0 89975aa76f/ deployment/ ipa/ipaservices -baremetal- ansible. yaml#L107
[2]: https:/
[3]: https:/