Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1381881

Summary: Taxonomies are not returned for Canned Roles
Product: Red Hat Satellite Reporter: Oleksandr Shtaier <oshtaier>
Component: HammerAssignee: Marek Hulan <mhulan>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: mhulan
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:51:07 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1373844    

Description Oleksandr Shtaier 2016-10-05 09:21:48 UTC
Description of problem:
When I create new Canned Role with taxonomies:
hammer -v -u admin -p changeme --output=csv role create --organizations="coC4sT" --locations="lVZNUA2tLR" --name="Cc417k"
Message,Id,Name
User role [Cc417k] created,21,Cc417k

and try to read it back, necessary information is not returned:
hammer --output=json -v -u admin -p changeme role info --id="21"
{
  "Id": 21,
  "Name": "Cc417k",
  "Builtin": "No"
}


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

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
Taxonomies are not returned for just created Role

Expected results:
I can get expected information for Canned Role

Additional info:

Comment 2 Marek Hulan 2016-10-05 10:14:18 UTC
Created redmine issue http://projects.theforeman.org/issues/16799 from this bug

Comment 4 Bryan Kearney 2016-10-05 12:20:10 UTC
Upstream bug assigned to mhulan

Comment 5 Bryan Kearney 2016-10-05 12:20:13 UTC
Upstream bug assigned to mhulan

Comment 6 Bryan Kearney 2016-10-05 14:19:22 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16799 has been resolved.

Comment 7 Peter Ondrejka 2017-08-31 09:30:54 UTC
Verified in Sat 6.3 snap 13:

~]# hammer -v -u admin -p changeme --output=csv role create --organizations="kok" --locations="Default Location" --name="Cc417k"


~]# hammer --output=json -v -u admin -p changeme role info --id=26
{
  "Id": 26,
  "Name": "Cc417k",
  "Builtin": 0,
  "Description": null,
  "Locations": [
    {
      "id": 2,
      "name": "Default Location",
      "title": "Default Location",
      "description": null
    }
  ],
  "Organizations": [
    {
      "id": 3,
      "name": "kok",
      "title": "kok",
      "description": ""
    }
  ]
}

Comment 8 Satellite Program 2018-02-21 16:51:07 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