Project

General

Profile

Bug #4358

Unable to create unmanaged host

Added by Lukas Zapletal over 5 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
High
Category:
Foreman commands (obsolete)
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

When managed is set to false, hammer cli should not require all the parameters, except name:

hammer> host create --name test --managed false

Could not create the host:
  Error: Options --environment-id, --architecture-id, --domain-id, --puppet-proxy-id, --operatingsystem-id, --partition-table-id are required

I need to fix this to move on with other task, will add dependency.


Related issues

Related to Foreman - Feature #3506: Tool to register existing hosts back to ForemanNew2013-10-25

Associated revisions

Revision e92e5532 (diff)
Added by Lukas Zapletal over 5 years ago

fixes #4358 - unmanaged host can be now created empty

Revision ccb50b79
Added by Tomas Strachota over 5 years ago

Merge pull request #86 from lzap/unmanaged-host-4358

fixes #4358 - unmanaged host can be now created empty

History

#1 Updated by Lukas Zapletal over 5 years ago

  • Status changed from Assigned to Ready For Testing

#2 Updated by Lukas Zapletal over 5 years ago

  • Related to Feature #3506: Tool to register existing hosts back to Foreman added

#3 Updated by Anonymous over 5 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Applied in changeset foreman:hammer-cli-foreman|commit:e92e5532698041eeef753eb6dc8b2f07ec2c034c.

Also available in: Atom PDF