Bug 2279151

Summary:	Boot disk based Provisioning fails to generate ISO image for instance clietn.example.com: ERF42-8093 [Foreman::Exception]: ISO build failed
Product:	Red Hat Satellite	Reporter:	Satyajit Das <sadas>
Component:	Bootdisk Plugin	Assignee:	Evgeni Golov <egolov>
Status:	CLOSED MIGRATED	QA Contact:	Gaurav Talreja <gtalreja>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.16.0	CC:	ahumbe, gtalreja, lstejska, rlavi, sganar, shwsingh
Target Milestone:	Unspecified	Keywords:	AutomationBlocker, MigratedToJIRA, Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 17:36:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Satyajit Das 2024-05-05 12:49:16 UTC

Description of problem:

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


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

satellite-common-6.16.0-0.3.stream.el9sat.noarch
Red Hat Enterprise Linux release 9.3 

How reproducible:

100%(Satellite running on RHEL-9)


Steps to Reproduce:
1. In the Satellite Web UI select Hosts --> Create Host. (Fill in all the required details)
2. Next, in the Operating System tab, under Provisioning Method  Select Boot Disk Based and click submit

Actual results:

Unable to save
Failed to generate ISO image for instance client.example.com: ERF42-8093 [Foreman::Exception]: ISO build failed

Expected results:

Able to provision host using Auto-attach Bootdisk 


Additional info:

==> /var/log/foreman/production.log <==

2024-05-05T08:06:48 [I|for|2e9a69b1] Retrieved http://satellite.example.com/pulp/content/Default_Organization/Library/content/dist/rhel9/9.3/x86_64/baseos/kickstart//images/pxeboot/initrd.img from local cache (use foreman-rake tmp:cache:clear to empty)
2024-05-05T08:06:48 [W|app|2e9a69b1] Failed to generate ISO image for instance dora-rydolph.vms.sat.rdu2.redhat.com: ERF42-8093 [Foreman::Exception]: ISO build failed
2024-05-05T08:06:48 [I|app|2e9a69b1] Backtrace for 'Failed to generate ISO image for instance client.example.com: ERF42-8093 [Foreman::Exception]: ISO build failed' error (Foreman::Exception): ERF42-8093 [Foreman::Exception]: ISO build failed
 2e9a69b1 | /usr/share/gems/gems/foreman_bootdisk-21.2.3/app/services/foreman_bootdisk/iso_generator.rb:160:in `generate'
 2e9a69b1 | /usr/share/gems/gems/foreman_bootdisk-21.2.3/app/services/foreman_bootdisk/iso_generator.rb:30:in `generate_full_host'
 2e9a69b1 | /usr/share/gems/gems/foreman_bootdisk-21.2.3/app/models/concerns/foreman_bootdisk/orchestration/compute.rb:47:in `bootdisk_generate_iso_image'
 2e9a69b1 | /usr/share/gems/gems/foreman_bootdisk-21.2.3/app/models/concerns/foreman_bootdisk/orchestration/compute.rb:71:in `setGenerateIsoImage'
 2e9a69b1 | /usr/share/foreman/app/models/concerns/orchestration.rb:227:in `execute'
 2e9a69b1 | /usr/share/foreman/app/models/concerns/orchestration.rb:152:in `block in process'
 2e9a69b1 | /usr/share/foreman/app/models/concerns/orchestration.rb:144:in `each'
 2e9a69b1 | /usr/share/foreman/app/models/concerns/orchestration.rb:144:in `process'
 2e9a69b1 | /usr/share/foreman/app/models/concerns/orchestration.rb:44:in `around_save_orchestration'
 2e9a69b1 | /usr/share/gems/gems/activesupport-6.1.7.7/lib/active_support/callbacks.rb:126:in `block in run_callbacks'
 2e9a69b1 | /usr/share/gems/gems/activesupport-6.1.7.7/lib/active_support/callbacks.rb:137:in `run_callbacks'
 2e9a69b1 | /usr/share/gems/gems/activesupport-6.1.7.7/lib/active_support/callbacks.rb:824:in `_run_save_callbacks'
 2e9a69b1 | /usr/share/gems/gems/activerecord-6.1.7.7/lib/active_record/callbacks.rb:457:in `create_or_update'
 2e9a69b1 | /usr/share/gems/gems/activerecord-6.1.7.7/lib/active_record/timestamp.rb:126:in `create_or_update'
 2e9a69b1 | /usr/share/gems/gems/activerecord-6.1.7.7/lib/active_record/persistence.rb:474:in `save'
 2e9a69b1 | /usr/share/gems/gems/activerecord-6.1.7.7/lib/active_record/validations.rb:47:in `save'
 2e9a69b1 | /usr/share/gems/gems/activerecord-6.1.7.7/lib/active_record/transactions.rb:298:in `block in save'
 2e9a69b1 | /usr/share/gems/gems/activerecord-6.1.7.7/lib/active_record/transactions.rb:354:in `block in with_transaction_returning_status'
 2e9a69b1 | /usr/share/gems/gems/activerecord-6.1.7.7/lib/active_record/connection_adapters/abstract/database_statements.rb:320:in `block in transaction'
 2e9a69b1 | /usr/share/gems/gems/activerecord-6.1.7.7/lib/active_record/connection_adapters/abstract/transaction.rb:319:in `block in within_new_transaction'
 2e9a69b1 | /usr/share/gems/gems/activesupport-6.1.7.7/lib/active_support/concurrency/load_interlock_aware_monitor.rb:26:in `block (2 levels) in synchronize'
 2e9a69b1 | /usr/share/gems/gems/activesupport-6.1.7.7/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt'
===============================================================================

Comment 1 sganar 2024-05-07 07:13:44 UTC

Note: This is not only related to VMware but overall bootdisk across the satellite. Baremetal Bootdisk is also impacted due to this.

Comment 3 Eric Helms 2024-06-06 17:36:51 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.