Bug 1328188 - "Error: organization found more than once" when creating a hostgroup
Summary: "Error: organization found more than once" when creating a hostgroup
Keywords:
Status: CLOSED DUPLICATE of bug 1309107
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.1.8
Hardware: Unspecified
OS: Unspecified
unspecified
low vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-18 15:58 UTC by Andrew Kofink
Modified: 2017-08-11 14:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-11 14:16:58 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Andrew Kofink 2016-04-18 15:58:42 UTC
Description of problem: The `hammer hostgroup <create|update>` subcommands take organizations or organization_ids, and the command is successful if only one organization is provided; however, when providing a comma-separated list, the following error is displayed:

Could not create the hostgroup:
  Error: organization found more than once


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

How reproducible:
Always in 6.1.8 and 1.12.0-develop.

Steps to Reproduce:
1. Create an additional organization:
hammer organization create --name "org3"
2. Find the org's ID:
hammer organization list
3. Try to create a host group with 2 or more organizations:
hammer hostgroup create --content-view 'cv1' --organizations "Default Organization","org3" --name 'hg3'

Actual results:
Could not create the hostgroup:
  Error: organization found more than once

Expected results:
Hostgroup created

Additional info:
Related (PR submitted): https://bugzilla.redhat.com/show_bug.cgi?id=1309107

Comment 1 Bryan Kearney 2016-07-26 18:59:15 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 3 Bryan Kearney 2017-08-11 14:16:58 UTC
This appears to be a dupe of 1309107. I am closing it as such. If this is still an issue, please feel free to re-open.

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


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