Bug 1659042 - Bootdisk does not validate media leading to Medium cannot be blank error during bootdisk provision method [NEEDINFO]
Summary: Bootdisk does not validate media leading to Medium cannot be blank error duri...
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Bootdisk Plugin   
(Show other bugs)
Version: 6.4
Hardware: Unspecified
OS: Unspecified
high vote
Target Milestone: 6.5.0
Assignee: Lukas Zapletal
QA Contact: Jan Hutař
Keywords: Regression, Triaged
: 1663524 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2018-12-13 12:47 UTC by Lukas Zapletal
Modified: 2019-04-17 14:29 UTC (History)
11 users (show)

Fixed In Version: foreman-,tfm-rubygem-foreman_bootdisk-
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
lzap: needinfo? (mmccune)

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 14797 None None None 2019-01-21 09:07 UTC
Foreman Issue Tracker 25680 None None None 2018-12-13 13:19 UTC
Red Hat Knowledge Base (Solution) 2832391 None None [Satellite 6] Registering new host fails with error "Validation failed: Location can't be blank." 2019-03-04 15:11 UTC
Red Hat Knowledge Base (Solution) 3774291 None None None 2019-03-04 15:23 UTC

Description Lukas Zapletal 2018-12-13 12:47:51 UTC
I was trying to create a host using newly added bootdisk provisioning method from UI. I associated all required fields and simply selected the "Boot disk based" provisioning method. All other fields on "operating system" tab were appeared same as for "network based".

Under "Media selection" -> "Synced contents" was selected and Kickstart media was auto populated. The moment I submitted the create host form, UI raised error on Media under "operating system" tab: 

Media can't be blank

Symptoms the same as in https://bugzilla.redhat.com/show_bug.cgi?id=1513327

Regression, 6.3 was fixed in BZ 1513327 but upstream was not yet properly fixed.

This is a bootdisk blocker for 6.4

Comment 4 Lukas Zapletal 2019-01-07 14:02:20 UTC
*** Bug 1663524 has been marked as a duplicate of this bug. ***

Comment 6 Lukas Zapletal 2019-01-11 14:35:40 UTC
The PRs are just about to be merged. As a workaround apply this:


and this for bootdisk:


That will do it.

Comment 9 Bryan Kearney 2019-01-21 09:02:15 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25680 has been resolved.

Comment 15 Jan Hutař 2019-02-25 21:31:11 UTC
Some generic info about Boot disk based provisioning method I got from lzap (thanks!):

- this was provided by community (thanks!)
- this currently works only on VmWare compute resource
- you do not need to download boot disk yourself, this happens automatically when host is created in Satellite (boot disk gets uploaded to VmWare and attached as bootable CD to the VM)
- initial discussion was here: https://community.theforeman.org/t/rfc-uefi-http-booting/8723/12

Note You need to log in before you can comment on or make changes to this bug.