Till!
Till!
> And be a aware that FQDN hostnames are not recommended or well supported, the hostname really should be the first component of the fqdn. For the record, this worked...
@ader1990 it contains two variants: ```json { "uuid": "ABC", "meta": { "group": "customer", "label": "docker", "role": "worker", "origin": "foo" }, "admin_pass": "ABC", "hostname": "node-001-docker", "name": "node-001.docker", "launch_index": 0, "availability_zone": "nova",...
> It's openstack metadata that is doing the translation. Yes, of course. What I meant to add is, I couldn't find anything _obvious_ how to set the `hostname` value myself.
The metadata service also responds with the _broken_ hostname.
Is there anything I should add to ignition to force my hostname? I think so far I only write to `/etc/hostname` but I suspect something in OpenStack derives the value...
The output is: ``` curl http://169.254.169.254/latest/meta-data/hostname && echo node-001-docker ``` This is also rather interesting: - https://github.com/openstack/python-openstackclient/blob/2eea916b35fd6f01947dce168c50c314ed9072db/openstackclient/compute/v2/server.py#L1447-L1457 - https://docs.openstack.org/openstacksdk/latest/user/resources/compute/v2/server.html It seems like it'll use `name` when no `hostname` is provided....
@gabriel-samfira thanks for looking into it. I made a PR to Gophercloud to set the hostname going forward. And I'll see what else I can do in terms of user-data/ignition....
@gabriel-samfira Yes, using config drive and ignition.
@tormath1 firefox
@sxd Is there anything else you need?