Provisioning Setup Error on fresh 1.11/Ubuntu 14.04 install

Using a new installation of Ubuntu Server 14.04, I followed the Foreman
quickstart guide and installed Foreman using the official installer.
Everything works fine, except when I go to Infrastructure -> Provisioning
setup, I see the following

[x] Missing registered host foreman.ABCdefghi.local, please ensure it is
checking in
[v] Found registered smart proxy foreman.ABCdefghi.local
[x] No network interfaces listed in $interfaces fact

I'm not exactly sure what that means or how to fix it? The host it
mentions shows up under the Hosts -> All Hosts list, although it is
displayed with a lower case FQDN whereas the domain is mixed-case. I
thought that might be related, though it doesn't appear to be a problem
with regard to finding the smart proxy. I've already done a puppet run on
the host and deployed ntp via the 1.11 manual, also tried rebooting, but
neither had any affect.

Any idea what's going on?

I think this is a known bug in the foreman_setup (Provisioning Setup)
plugin that I've not yet fixed. For now I think you'll want to either
change the hostname (probably easiest to reinstall!) or configure
provisioning manually by adding subnets, domains, OSes and associating them.

··· On 07/06/16 21:17, Alexander Ray wrote: > Using a new installation of Ubuntu Server 14.04, I followed the Foreman > quickstart guide and installed Foreman using the official installer. > Everything works fine, except when I go to Infrastructure -> > Provisioning setup, I see the following > > [x] Missing registered host foreman.ABCdefghi.local, please ensure it is > checking in > [v] Found registered smart proxy foreman.ABCdefghi.local > [x] No network interfaces listed in $interfaces fact > > I'm not exactly sure what that means or how to fix it? The host it > mentions shows up under the Hosts -> All Hosts list, although it is > displayed with a lower case FQDN whereas the domain is mixed-case. I > thought that might be related, though it doesn't appear to be a problem > with regard to finding the smart proxy.


Dominic Cleal
dominic@cleal.org