Distribution and version:
CentOS Linux release 7.9.2009 (Core)
Other relevant data:
After upgrading from 2.0.3 to 2.1.4 the deployment does not work anymore.
At the end of the installation of Ubuntu the installer crashes.
Red Screen shows: Failed to run preseeded command
So I chrooted into the VM to see what’s going on there.
I downloaded the finish script and executed it line by line.
Running the following command is responsible for the problem: /opt/puppetlabs/bin/puppet resource service puppet enable=true
unable to read /etc/init.d/puppet
Error: /Service[puppet]/enable: change from 'false' to 'true' failed:
Execution of '/usr/bin/update-rc.d puppet defaults' returned 1: update-rc.d: error: unable to read /etc/init.d/puppet
Running in chroot, ignoring request
service {'puppet':
enable => 'false',
provider => 'debian',
}
I guess this comes from ‘puppet_setup.erb’
But there is no variable to set this. <% if os_family == 'Suse' || (os_name == 'Debian' && os_major > 8) || (os_name == 'Ubuntu' && os_major >= 15) -%> <%= bin_path %>/puppet resource service puppet enable=true
The only thing I can think of is that it doesn’t work well in the chroot. Sounds like a bug in Puppet. Have you tried their support? You can also try Puppet 6 since Puppet 5 goes EOL in a few days.
I tried Ubuntu 20.04 and puppet-agent 6.10.1-1focal but the problem stays the same.
The problem occurred after upgrading Foreman from 2.0.3 to 2.1.4.
I guess the provisioning templates in use will never be changed after an upgrade?
Is the slack channel the best way to get information from the puppet people?
The real problem is somewhere else.
The last wget command fails every time because the image can not be ejected.
2020-11-30T15:53:17 [W|app|f15bbd95] Failed to set Build on x.y…net: [“Failed to detach ISO image from CDROM drive of instance x.y…net: GenericVmConfigFault: Connection control op
eration failed for disk ‘ide0:0’.”]
