Bug 1213437

Summary:	Unable to get subnet ipam type
Product:	Red Hat Satellite	Reporter:	Alex <alexshtayer>
Component:	Hammer	Assignee:	Katello Bug Bin <katello-bugs>
Status:	CLOSED ERRATA	QA Contact:	Corey Welton <cwelton>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	alexshtayer, bbuckingham, bkearney, cwelton, erezende, oshtaier
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
URL:	http://projects.theforeman.org/issues/11074
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 11:00:30 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:

Description Alex 2015-04-20 14:44:41 UTC

Description of problem:
I am trying to get information about subnet ipam type, but cannot find a way to do that. It is not a problem to set that information, but not to get.

Version-Release number of selected component (if applicable):
Satellite 6.1.0 Beta


How reproducible:
Always

Steps to Reproduce:
1. To set:
hammer subnet create --name "a0" --network "127.0.0.1" --mask "255.0.0.0" --ipam "Internal DB"
2. To get:
hammer subnet info --name "a0"
3. There are no information about "IPAM" in the output

Actual results:
Id:            8
Name:          a0
Network:       127.0.0.1
Mask:          255.0.0.0
Priority:      
DNS:           
Primary DNS:   
Secondary DNS: 
TFTP:          
DHCP:          
VLAN ID:       
Gateway:       
From:          
To:            
Domains:


Expected results:
Id:            8
Name:          a0
Network:       127.0.0.1
Mask:          255.0.0.0
Priority:      
DNS:           
Primary DNS:   
Secondary DNS: 
IPAM: 
TFTP:          
DHCP:          
VLAN ID:       
Gateway:       
From:          
To:            
Domains:


Additional info:

Comment 1 Alex 2015-04-20 14:47:07 UTC

More like this:

Expected results:
Id:            8
Name:          a0
Network:       127.0.0.1
Mask:          255.0.0.0
Priority:      
DNS:           
Primary DNS:   
Secondary DNS: 
IPAM: Internal DB
TFTP:           
DHCP:          
VLAN ID:       
Gateway:       
From:          
To:            
Domains:

Comment 3 Bryan Kearney 2015-07-09 17:28:47 UTC

Created redmine issue http://projects.theforeman.org/issues/11074 from this bug

Comment 4 Bryan Kearney 2015-10-14 12:01:51 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/11074 has been closed
-------------
Alon Goldboim
Applied in changeset commit:hammer-cli-foreman|ee7d698957fae81da3e212d8db9ba1f85d9d4eda.

Comment 5 Tazim Kolhar 2015-10-28 12:41:01 UTC

*** This bug is verified in upstream.  This fix should eventually land in future downstream builds ***
Version Tested:

# rpm -qa | grep foreman
foreman-proxy-1.11.0-0.develop.201510201341git00875b3.el7.noarch
foreman-selinux-1.11.0-0.develop.201510071426git6234447.el7.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-3.el7.noarch
tfm-rubygem-foreman_docker-1.4.1-2.fm1_10.el7.noarch
foreman-libvirt-1.11.0-0.develop.201510201422git6eb234a.el7.noarch
foreman-compute-1.11.0-0.develop.201510201422git6eb234a.el7.noarch
foreman-release-scl-1-1.el7.x86_64
foreman-gce-1.11.0-0.develop.201510201422git6eb234a.el7.noarch
foreman-debug-1.11.0-0.develop.201510201422git6eb234a.el7.noarch
tfm-rubygem-foreman_gutterball-0.0.1-3.el7.noarch
hp-sl2x170zg6-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch
tfm-rubygem-foreman_discovery-4.1.1-1.fm1_11.el7.noarch
foreman-vmware-1.11.0-0.develop.201510201422git6eb234a.el7.noarch
tfm-rubygem-foreman_hooks-0.3.9-1.el7.noarch
tfm-rubygem-foreman-tasks-0.7.6-1.fm1_10.el7.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.8-1.el7.noarch
tfm-rubygem-foreman_bootdisk-6.0.0-2.fm1_10.el7.noarch
hp-sl2x170zg6-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch
hp-sl2x170zg6-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-ovirt-1.11.0-0.develop.201510201422git6eb234a.el7.noarch
foreman-1.11.0-0.develop.201510201422git6eb234a.el7.noarch
tfm-rubygem-hammer_cli_foreman_docker-0.0.3-4.el7.noarch
foreman-release-1.11.0-0.develop.201510201422git6eb234a.el7.noarch
foreman-postgresql-1.11.0-0.develop.201510201422git6eb234a.el7.noarch
tfm-rubygem-hammer_cli_foreman-0.4.0-1.201510201150gitab068d9.el7.noarch

steps:
# hammer subnet create --name "a0" --network "127.0.0.1" --mask "255.0.0.0" --ipam "Internal DB"
[Foreman] Password for admin: 
Subnet created

# hammer subnet info --name "a0"
[Foreman] Password for admin: 
Id:            1
Name:          a0
Network:       127.0.0.1
Mask:          255.0.0.0
Priority:      
DNS:           
Primary DNS:   
Secondary DNS: 
TFTP:          
DHCP:          
IPAM:          Internal DB
VLAN ID:       
Gateway:       
From:          
To:            
Domains:

Comment 8 Oleksandr Shtaier 2016-04-19 08:58:21 UTC

Verified on latest 6.2 SNAP 8.2

hammer -u user -p pass subnet create --name "a0" --network "127.0.0.1" --mask "255.0.0.0" --ipam "Internal DB"
Subnet created

hammer -u user -p pass subnet info --name "a0"
Id:            63
Name:          a0
Network:       127.0.0.1
Mask:          255.0.0.0
Priority:      
DNS:           
Primary DNS:   
Secondary DNS: 
TFTP:          
DHCP:          
IPAM:          Internal DB
VLAN ID:       
Gateway:       
From:          
To:            
Domains:

Comment 10 Bryan Kearney 2016-07-27 11:00:30 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/RHBA-2016:1501