Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1663524 - Creating a host w/ Boot disk provisioning method fails at medium selection - medium can't be blank
Summary: Creating a host w/ Boot disk provisioning method fails at medium selection - ...
Keywords:
Status: CLOSED DUPLICATE of bug 1659042
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Bootdisk Plugin
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Roman Plevka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-04 17:23 UTC by Pablo Hess
Modified: 2019-08-12 19:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-07 14:02:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pablo Hess 2019-01-04 17:23:00 UTC
Description of problem:
This is extremely similar to BZ #1513327 but I'm seeing it on 6.4.0. Problem description is the exact same but I'm adding possibly relevant information:

I was trying to create a host on a VMware hypervisor using bootdisk provisioning method from webUI. I associated all required fields and simply selected the "Boot disk based" provisioning method. All other fields on "operating system" tab appeared the same as for "network based".

Under "Media selection", "Synced contents" was selected and Kickstart media was auto populated with RHEL Server 7.6 x86_64 Kickstart. The moment I submitted the create host form, the webUI raised an error on Media under "operating system" tab: 

Media can't be blank

And at the same time it switched the radio button from "Synced contents" to "All Media". I clicked "Synced contents" back, and RHEL Server 7.6 x86_64 Kickstart was automatically selected again on the drop-down. But once I clicked Submit, it failed again with the same "Media can't be blank" message.

Note that this is using a Host Group that's pointing specifically to this RHEL 7.6 Kickstart repo.


Version-Release number of selected component (if applicable):
Satellite 6.4.0.
tfm-rubygem-foreman_bootdisk-12.0.0-1.el7sat.noarch

How reproducible:
Every time.

Steps to Reproduce:
1. Create a Host Group pointing to a VMware compute resource and with RHEL 7.6 Kickstart.
2. Browse to Hosts > Create Host, select the described Host Group.
3. Click the Operating System tab, select Provisioning Method: Boot disk based, click Submit.

Actual results:
The webUI does not submit the command, stating "Medium can't be blank" instead.

Expected results:
The webUI should submit the command, and the VM should be provisioned with the Boot disk method.

Additional info:
The attachments from BZ #1513327 reflect exactly what I'm seeing. https://bugzilla.redhat.com/attachment.cgi?id=1352438 and https://bugzilla.redhat.com/attachment.cgi?id=1352441

Comment 4 Lukas Zapletal 2019-01-07 14:02:20 UTC
The bug sneaked into 6.4.0 it was not properly fixed upstream. Working on it.

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


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