Bug 1322078 - Specifying provision and primary flags should not be mandatory
Summary: Specifying provision and primary flags should not be mandatory
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Sachin Ghai
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-29 18:22 UTC by Eric Helms
Modified: 2019-09-26 17:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:07:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 13927 0 None None None 2016-04-22 16:39:42 UTC

Description Eric Helms 2016-03-29 18:22:58 UTC
If I don't specify which interface is primary/provision, the first one is marked such. Most of users create host with just one interface.

Comment 1 Eric Helms 2016-03-29 18:23:00 UTC
Created from redmine issue http://projects.theforeman.org/issues/13927

Comment 2 Eric Helms 2016-03-29 18:23:03 UTC
Upstream bug assigned to mhulan

Comment 8 Sachin Ghai 2016-05-12 13:36:13 UTC
Verified with sat62 GA snap10

I can create host without specifying provision and primary flags.

 ~]# hammer -u admin -p changeme --output=csv host create --medium-id="9" --root-pass='foobarbaz' --organization-id="1" --location-id="2" --architecture-id="1" --operatingsystem-id="2" --name="ham-host2" --environment-id="1" --compute-resource-id="1" --domain-id="1" --puppet-proxy-id="1" --partition-table-id="61" --hostgroup-id 1 --compute-attributes="cpus=1, memory=2147483648," --volume="capacity=10G,format_type=qcow" --mac 52:54:00:23:24:05
Message,Id,Name
Host created,7,ham-host2.idmqe.lab.eng.bos.redhat.com

Comment 9 Bryan Kearney 2016-07-27 11:07:31 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


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