Bug 1328188

Summary: "Error: organization found more than once" when creating a hostgroup
Product: Red Hat Satellite Reporter: Andrew Kofink <akofink>
Component: HammerAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.1.8CC: bkearney, mmccune
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-11 14:16:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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 ***