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 1229901 - Unable to deploy host to RHEL OSP compute node
Summary: Unable to deploy host to RHEL OSP compute node
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.0.8
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: Tom Caspy
QA Contact: Jan Hutař
URL: http://projects.theforeman.org/issues...
Whiteboard:
: 1228723 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-09 21:30 UTC by Brett Thurber
Modified: 2017-02-23 19:56 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 16:02:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 6455 0 None None None 2016-04-22 14:57:14 UTC

Description Brett Thurber 2015-06-09 21:30:54 UTC
Description of problem:
Added RHEL OSP provider as a compute resource that is configured with a public and tenant network.  When attempting to deploy a host receive an error that a network must first be selected however there is no option within the deployment template to choose a network. 

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

How reproducible:
Every time

Steps to Reproduce:
1. Add a RHEL OSP compute resource
2. Create a new host and select RHEL OSP as the resource to deploy on
3. Click deploy and receive the following error:
Failed to create a compute RHELOSP6 (RHEL OpenStack Platform) instance test.refarch.bos.redhat.com: Multiple possible networks found, use a Network ID to be more specific. 

Actual results:
Unable to provision host.

Expected results:
Able to select the appropriate network and provision host onto a RHEL OSP compute resource.

Additional info:
http://pastebin.test.redhat.com/287149

Comment 1 RHEL Program Management 2015-06-09 21:52:52 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 4 Ohad Levy 2015-06-14 10:23:21 UTC
linked to upstream bug http://projects.theforeman.org/issues/6455

Comment 5 Bryan Kearney 2015-06-15 14:39:47 UTC
Upstream bug assigned to tcaspy

Comment 6 Tom Caspy 2015-06-15 14:52:02 UTC
this was fixed in 6.1

Comment 7 Tom Caspy 2015-06-15 14:53:18 UTC
also, ticket seems to be duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1228723

Comment 8 Bryan Kearney 2015-06-16 14:04:51 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/6455 has been closed

Comment 9 Bryan Kearney 2015-06-16 21:33:23 UTC
*** Bug 1228723 has been marked as a duplicate of this bug. ***

Comment 13 Bryan Kearney 2015-08-12 16:02:47 UTC
This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015.


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