Project

General

Profile

Bug #24748

no way to list cluster IDs inside compute resource

Added by Chris Roberts 24 days ago. Updated 16 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Difficulty:
easy
Triaged:
No
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Cloned from BZ:

Description of problem:
A VMware type compute resource can have multiple clusters defined within it (defined by VMware). Full use of the `hammer` command for provisioning requires we specify a cluster ID to deploy to. There is no way to currently list the clusters within a compute resource.

Version-Release number of selected component (if applicable):
tfm-rubygem-hammer_cli-0.11.0.1-1.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. Configure a VMware type compute resource within Satellite 6.3
2. Issue `hammer compute resource info --id 1`
3. See no information about clusters within the given compute resource

Actual results:
No information on clusters, no additional commands to list information on clusters in `hammer compute-resource --help`

Expected results:
Either a listing of all clusters or an additional command sequence to get that list.

Additional info:


Related issues

Related to Hammer CLI - Tracker #16829: Tracker for compute resource related issuesNew2016-10-07

Associated revisions

Revision 908d42da (diff)
Added by Chris Roberts 16 days ago

Fixes #24748 - Add Cluster option to Hammer CR.

History

#1 Updated by Chris Roberts 24 days ago

  • Category deleted (Hammer)
  • Project changed from Katello to Hammer CLI
  • Fixed in Releases hammer-cli-foreman-0.14.0 added

#2 Updated by The Foreman Bot 24 days ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/hammer-cli-foreman/pull/383 added

#3 Updated by Andrew Kofink 22 days ago

  • Fixed in Releases deleted (hammer-cli-foreman-0.14.0)

#4 Updated by Tomáš Strachota 16 days ago

  • Related to Tracker #16829: Tracker for compute resource related issues added

#5 Updated by Chris Roberts 16 days ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF