Project

General

Profile

Actions

Tracker #26990

closed

Tracker for VMware issues

Added by Oleh Fedorenko almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Compute resources
Target version:
-
% Done:

0%

Difficulty:
Triaged:
No
Team Backlog:
Fixed in Releases:
Found in Releases:
In Kanboard:

Related issues 10 (1 open9 closed)

Related to Hammer CLI - Feature #26421: Implement multiple SCSIControllers for VMware backed hostClosedOleh FedorenkoActions
Related to Hammer CLI - Bug #25584: Unclear error when not specifying the 'path' under --compute-attributes sectionClosedOleh FedorenkoActions
Related to Hammer CLI - Bug #25093: Provisioning VMs with Foreman API Not Working for Multiple SCSI Controllers and VolumesClosedOleh FedorenkoActions
Related to Hammer CLI - Refactor #23973: Change Compute Resource help for create to look like host creatNewActions
Related to Hammer CLI - Bug #23473: Update hammer to correctly provision vmware VMs.ClosedActions
Related to Hammer CLI - Bug #22171: create a host from hammer CLI to VMWare with error "Ressource host not found by id" when all the options are presentClosedalexender flemingActions
Related to Hammer CLI - Bug #19702: Hammer host create, with vmware compute resource, cant use VMware network names, needs the network ID insteadClosedyifat makiasActions
Related to Hammer CLI - Feature #18885: Add hammer-cli help output telling user how to use VMWare storage pod / datastore clustersClosedActions
Related to Hammer CLI - Bug #12502: hammer host create using oVirt should use text IDs, not UUIDsDuplicateActions
Related to Hammer CLI - Bug #4309: hammer host start no longer powers on VMware hostClosedActions
Actions

Also available in: Atom PDF