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 1427319 - Fail to create a host under vmware compute resource when the cluster name contains parenthesis ()
Summary: Fail to create a host under vmware compute resource when the cluster name con...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.2.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-27 21:59 UTC by Christian Marineau
Modified: 2021-06-10 11:59 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 17883 0 Normal Closed Problem with resource pool vCenter 5.5 2021-01-28 10:42:14 UTC
Red Hat Knowledge Base (Solution) 2986661 0 None None None 2017-03-30 03:38:06 UTC

Description Christian Marineau 2017-02-27 21:59:08 UTC 
Description of problem:
When creating a new host on a VMware Compute Resource, if the Cluster Name contains parenthesis ( ), it throws an error about the resource pool


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


How reproducible:
100%


Steps to Reproduce:
1. In VMware, create a cluster with parenthesis, eg: Cluster (Test)
2. In Satellite, click on Host > New host
3. Fill all the required fields. For the field "Deploy on", make sure to specify the Compute Resource where you have created "Cluster (Test)"
4. In the Virtual Machine tab, select the Cluster "Cluster (Test)"
5. Click Submit


Actual results:
- The first step will fail:
   x failed - Set up compute instance test-01.domain.com
  
- Then this error will appear
    Unable to save
    Failed to create a compute VMware instance test-01.domain.com: failed to create vm: undefined method `resourcePool' for #<RbVmomi::VIM::Folder:0x0000000908ce70>


Expected results:
No error


Additional info:
The errors indicate an issue about the resource pool, but it seems to be a side effect that is misleading.
Comment 1 Marek Hulan 2017-02-28 07:14:11 UTC 
Thanks for the report

Similar errors were reported but we never resolved it (for reference only)
* http://projects.theforeman.org/issues/2696
* http://projects.theforeman.org/issues/10912

Are you 100% sure about the cause? If you rename the cluster (or use another one without parenthesis) does it work? In such case, the upstream tracker would be http://projects.theforeman.org/issues/17883
Comment 2 Christian Marineau 2017-02-28 14:11:41 UTC 
(In reply to Marek Hulan from comment #1)
> Thanks for the report
> 
> Similar errors were reported but we never resolved it (for reference only)
> * http://projects.theforeman.org/issues/2696
> * http://projects.theforeman.org/issues/10912
> 
> Are you 100% sure about the cause? If you rename the cluster (or use another
> one without parenthesis) does it work? In such case, the upstream tracker
> would be http://projects.theforeman.org/issues/17883

Hi,

This behaviour has been tested and reported by a customer and reproduced in our lab. The issue happens when we add parenthesis to the Cluster name and disappear when we remove them.

Thanks
Comment 8 Satellite Program 2017-05-11 14:04:09 UTC 
Upstream bug assigned to mhulan
Comment 9 Satellite Program 2017-05-11 14:04:13 UTC 
Upstream bug assigned to mhulan
Comment 10 Satellite Program 2017-05-14 10:04:12 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17883 has been resolved.
Comment 12 Bryan Kearney 2017-05-15 18:30:19 UTC 
Added this to 6.2.11. Thanks Marek
Comment 19 Bryan Kearney 2018-02-21 16:45:42 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0336
Comment 20 Satellite Program 2018-02-21 16:54:37 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> > 
> > For information on the advisory, and where to find the updated files, follow the link below.
> > 
> > If the solution does not work for you, open a new bug report.
> > 
> > https://access.redhat.com/errata/RHSA-2018:0336
Note You need to log in before you can comment on or make changes to this bug.