+++ This bug was initially created as a clone of Bug #2247081 +++

Created attachment 1996209
strace_log

Description of problem:

 - Provisioning virtual machines in the VMware platform vSphere 8.0 via satellite version 6.13.4 using the Bootdisk Method (BIOS and UEFI) failed to create the host with the error.

Version-Release number of selected component (if applicable):
 
 6.13.4

How reproducible:

 100% (Customer's env)

Steps to Reproduce:
1. Provision a host using the Satellite server.
2. While the host is provisioning, it fails with the error.

Actual results:

  ==========================
  [W|app|eb9fe95d] Failed to attach ISO image to CDROM drive of instance client.example.com: InvalidPowerState: The attempted operation cannot be performed in the current state (Powered on).
  [I|app|eb9fe95d] Backtrace for 'Failed to attach ISO image to CDROM drive of instance client.example.com: InvalidPowerState: The attempted operation cannot be performed in the current state (Powered on).' error (RbVmomi::Fault): InvalidPowerState: The attempted operation cannot be performed in the current state (Powered on).
   eb9fe95d | /usr/share/gems/gems/rbvmomi2-3.6.0/lib/rbvmomi/vim/Task.rb:15:in `wait_for_completion'
   eb9fe95d | /usr/share/gems/gems/fog-vsphere-3.6.2/lib/fog/vsphere/requests/compute/vm_reconfig_hardware.rb:10:in `vm_reconfig_hardware'
   eb9fe95d | /usr/share/gems/gems/fog-vsphere-3.6.2/lib/fog/vsphere/requests/compute/vm_reconfig_cdrom.rb:32:in `vm_reconfig_cdrom'
   eb9fe95d | /usr/share/gems/gems/foreman_bootdisk-21.0.3/app/models/concerns/foreman_bootdisk/compute_resources/vmware.rb:43:in `iso_attach'
   eb9fe95d | /usr/share/gems/gems/foreman_bootdisk-21.0.3/app/models/concerns/foreman_bootdisk/orchestration/compute.rb:63:in `bootdisk_attach_iso'
   eb9fe95d | /usr/share/gems/gems/foreman_bootdisk-21.0.3/app/models/concerns/foreman_bootdisk/orchestration/compute.rb:89:in `setAttachIsoImage'
  ==========================

Expected results:

 The host should be provisioned without any error.

Additional info:

 Check the attached file for the complete log.

--- Additional comment from  on 2023-10-31T07:58:20Z 

CC Gaurav from QE and Leos + Toledo from Dev team

This is perhaps the very first vSphere 8 issue reported for Sat 6

At some point, It was actually mentioned that CU had tested with vSphere 7 and found the same issue but what CU did is, Used vSpehere 8 only and while creating the VM, he just lowered the H/W version of the VM ( assuming that is = vSphere 7 compatibility ).

--- Additional comment from  on 2023-10-31T08:01:54Z 

// For Public Visibility // 


Description of problem:

 - Provisioning virtual machines in the VMware platform vSphere 8.0 via satellite version 6.13.4 using the Bootdisk Method (BIOS and UEFI) failed to create the host with the error.

Version-Release number of selected component (if applicable):
 
Satellite 6.13.4 + VMware vSphere 8 ( compute resource )

How reproducible:

 100% ( for the affected end-users )

Steps to Reproduce:

1. Provision a VM using the Satellite server with the Bootdisk Auto-Attach method on a VMware vSphere 8 compute resource. 
2. Check if the deployment is getting completed.

Actual results:

  ==========================
  [W|app|eb9fe95d] Failed to attach ISO image to CDROM drive of instance client.example.com: InvalidPowerState: The attempted operation cannot be performed in the current state (Powered on).
  [I|app|eb9fe95d] Backtrace for 'Failed to attach ISO image to CDROM drive of instance client.example.com: InvalidPowerState: The attempted operation cannot be performed in the current state (Powered on).' error (RbVmomi::Fault): InvalidPowerState: The attempted operation cannot be performed in the current state (Powered on).
   eb9fe95d | /usr/share/gems/gems/rbvmomi2-3.6.0/lib/rbvmomi/vim/Task.rb:15:in `wait_for_completion'
   eb9fe95d | /usr/share/gems/gems/fog-vsphere-3.6.2/lib/fog/vsphere/requests/compute/vm_reconfig_hardware.rb:10:in `vm_reconfig_hardware'
   eb9fe95d | /usr/share/gems/gems/fog-vsphere-3.6.2/lib/fog/vsphere/requests/compute/vm_reconfig_cdrom.rb:32:in `vm_reconfig_cdrom'
   eb9fe95d | /usr/share/gems/gems/foreman_bootdisk-21.0.3/app/models/concerns/foreman_bootdisk/compute_resources/vmware.rb:43:in `iso_attach'
   eb9fe95d | /usr/share/gems/gems/foreman_bootdisk-21.0.3/app/models/concerns/foreman_bootdisk/orchestration/compute.rb:63:in `bootdisk_attach_iso'
   eb9fe95d | /usr/share/gems/gems/foreman_bootdisk-21.0.3/app/models/concerns/foreman_bootdisk/orchestration/compute.rb:89:in `setAttachIsoImage'
  ==========================

Expected results:

 The host should be provisioned without any error and the error should happen neither during ATTACH nor DETACH of the CDROM drive

--- Additional comment from  on 2023-10-31T16:10:00Z 

VMware 8 U2 issue with InvalidPowerState · Issue #287 · fog/fog-vsphere
https://github.com/fog/fog-vsphere/issues/287

--- Additional comment from  on 2023-10-31T23:53:57Z 

cu in 03653561 also appeared to be affected and the below are the version:

 ~~~
 satellite-6.13.5　
 VMware Vcenter 8.0.2
 ~~~

--- Additional comment from  on 2023-11-01T00:22:26Z 

Hello,

Just to keep on track, Satellite 6.13 supports vCenter version 6.x and 7.x. At this moment, we have no support for vCenter 8.x, which is the main idea of bugzilla [1].

Here is the doc.

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/provisioning_hosts/index#Creating_a_VMware_User_vmware-provisioning

Best
Waldirio

[1]. https://bugzilla.redhat.com/show_bug.cgi?id=2247345

--- Additional comment from  on 2023-11-06T13:40:04Z 



*** This bug has been marked as a duplicate of bug 2247345 ***

--- Additional comment from  on 2023-12-04T17:31:59Z 

Fixed in this build:

https://github.com/theforeman/foreman_bootdisk/commit/9642ed90f3548cdba01c07858f01379ca5a71a99

--- Additional comment from  on 2023-12-05T12:09:47Z 

I hope that the QE team will test the fix on both vCenter 7 as well as 8u2, once the BZ moves to ON_QA stage

--- Additional comment from  on 2023-12-19T18:27:00Z 

Verified.

Tested on Satellite 6.15.0 Snap 3.0
rubygem-foreman_bootdisk-21.2.1-1.el8sat.noarch

Steps followed: 
1. Configure the satellite for provisioning and create the VMware CR
2. Provision a host on VMware using the bootdisk method

Observation: 
1. Tested on vCenter 7 as well as 8
2. The host provisioned without any issues.

One thing to note is after the host is successfully provisioned, the build status still shows `Pending Installation` on VMware 8 but the host is successfully registered and has content access through repos from AK, it just displays the wrong status(this is the only case when provisioning via Bootdisk but Network, Image-based shows correct build status as Installed)

`Everything works fine on VMware 7`

I am going to open a new BZ to track this issue, not going to block verification of this BZ as the main issue of this BZ is resolved.

QE Tracker for https://issues.redhat.com/browse/SAT-22363
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2257415