Problem:
Provisioning of VMware machines is stuck after upgrading from 2.0.3 to 2.1.4.
At the end of the install process (Ubuntu 18.04/20.04) pressed wants to eject the disk.
Expected outcome:
Works as in version 2.0.3
Foreman and Proxy versions:
Foreman 2.1.4
Foreman and Proxy plugin versions:
foreman-vmware.noarch 2.1.4-1.el7
Distribution and version:
CentOS Linux release 7.9.2009 (Core)
Other relevant data:
/var/log/foreman-proxy/
Failed to detach ISO image from CDROM drive of instance x.y.net: GenericVmConfigFault: Connection control operation failed for disk ‘ide0:0’.
Even if the Foreman user has the role ‘administrator’ it does not work.
I comment out ‘compute_resource.iso_detach(uuid)’ in line 59 of /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_bootdisk-17.0.2/app/models/concerns/foreman_bootdisk/orchestration/compute.rb
I did a new build but the problem still occurs
Is this the correct file at all?
Do I have to restart something?
Only if I force it:
The guest operating system has locked the CD-ROM door and is probably using the CD-ROM, which can prevent the guest from recognizing media changes. If possible, eject the CD-ROM from inside the guest before disconnecting. Disconnect anyway and override the lock?
This is not a Ubuntu/Debian preseed problem.
I tried to install CentOS. Which has worked fine the whole time.
But after the upgrade and I have the same problem.
Last message:
“Informing Foreman that we are built”
and vSphere Center shows:
The guest operating system has locked the CD-ROM door and is probably using the CD-ROM, which can prevent the guest from recognizing media changes. If possible, eject the CD-ROM from inside the guest before disconnecting. Disconnect anyway and override the lock?
Yes, the finish template is the correct place.
An hour ago I added a plain /usr/bin/eject
before the 3 sed commands and this works for me
I already deployed a couple of machines