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 1233612 - hammer info doesn't return all values for location
Summary: hammer info doesn't return all values for location
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.1.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-19 09:40 UTC by Oleksandr Shtaier
Modified: 2021-07-22 07:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:51:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 15502 0 None None None 2016-10-10 14:00:04 UTC

Description Oleksandr Shtaier 2015-06-19 09:40:58 UTC 
Description of problem:
We can create new 'Location' object with, for example, description:
hammer -u admin -p changeme location create --name Test01 --description Test01
But there are no way to get information about location description through hammer:
hammer -u admin -p changeme location info --name Test01
---------------------------------------
Id:                 228
Name:               Test01
Users:              

Smart proxies:      

Subnets:            

Compute resources:  

Installation media: 

Templates:          
    Boot disk iPXE - generic host (Bootdisk)
    ...
Domains:            

Environments:       

Hostgroups:         

Parameters:         

Created at:         2015/06/19 09:11:04
Updated at:         2015/06/19 09:11:04
------------------------------------------

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

How reproducible:
Always

Steps to Reproduce:
1. Create new location through CLI
2. Read information about just created entity

Actual results:
There are no information about location description in 'hammer location info' output


Expected results:
Necessary information can be received through CLI

Additional info:
Comment 1 RHEL Program Management 2015-06-19 10:04:22 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 3 Bryan Kearney 2016-07-08 20:35:59 UTC 
Per 6.3 planning, moving out non acked bugs to the backlog
Comment 5 Adam Ruzicka 2016-10-10 13:50:04 UTC 
Created redmine issue http://projects.theforeman.org/issues/16849 from this bug
Comment 6 Adam Ruzicka 2016-10-10 14:00:05 UTC 
Moving to POST since the bug was already closed in upstream.
Comment 7 Peter Ondrejka 2016-12-13 09:13:27 UTC 
Verified in Sat 6.3 snap 8, location description is now correctly displayed in the output of hammer location info
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
Note You need to log in before you can comment on or make changes to this bug.