I'm trying to run Foreman on Amazon AWS and finding it challenging since
AWS has so many different domains and hostnames for a VM.
After a certain amount of assault and battery, I got the semi-official
hostname of the VM to be "foreman.my.domain" and map it in Amazon's VPC
DNS. I was able to set up the smart proxy, spin up a new host under Foreman
control and import some Puppet classes.
I went away and came back and things were now broken. It may be that
someone fiddled with DNS and changed the DNS hostname to
"theforeman.my.domain". I changed it back when facter told me that the fqdn
was wrong.
At this point, the "Provisioning Setup" page is angry with me. It claims
"Missing registered host foreman.ec2.internal, please ensure it is checking
in"
This is NOT one of the FQDNs I want to be running under and I don't know
where it's coming from or how it managed to replace the
previously-functioning "foreman.my.domain" FQDN. It's not in the facter
collection for this machine, it's not in puppet's config file and it's not
in any of the /etc/foreman files.
I would be very grateful if someone could tell me how to get it out of the
Foreman Provisioning Setup and "New Host" processes as well.
Resolved with help from Foreman IRC: /etc/hosts had dropped the foreman
hostname entries from its localhost definition line (probably DHCP
provisioner did it).
ยทยทยท
On Thursday, 24 September 2015 18:36:46 UTC-4, Tim Holloway wrote:
>
> I'm trying to run Foreman on Amazon AWS and finding it challenging since
> AWS has so many different domains and hostnames for a VM.
>
> After a certain amount of assault and battery, I got the semi-official
> hostname of the VM to be "foreman.my.domain" and map it in Amazon's VPC
> DNS. I was able to set up the smart proxy, spin up a new host under Foreman
> control and import some Puppet classes.
>
> I went away and came back and things were now broken. It may be that
> someone fiddled with DNS and changed the DNS hostname to
> "theforeman.my.domain". I changed it back when facter told me that the fqdn
> was wrong.
>
> At this point, the "Provisioning Setup" page is angry with me. It claims
> "Missing registered host foreman.ec2.internal, please ensure it is checking
> in"
>
> This is NOT one of the FQDNs I want to be running under and I don't know
> where it's coming from or how it managed to replace the
> previously-functioning "foreman.my.domain" FQDN. It's not in the facter
> collection for this machine, it's not in puppet's config file and it's not
> in any of the /etc/foreman files.
>
> I would be very grateful if someone could tell me how to get it out of the
> Foreman Provisioning Setup and "New Host" processes as well.
>
