Project

General

Profile

Tracker #26990

Tracker for VMware issues

Added by Oleh Fedorenko over 3 years ago. Updated over 2 years ago.

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

0%

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

Related issues

Related to Hammer CLI - Feature #26421: Implement multiple SCSIControllers for VMware backed hostClosed
Related to Hammer CLI - Bug #25584: Unclear error when not specifying the 'path' under --compute-attributes sectionClosed
Related to Hammer CLI - Bug #25093: Provisioning VMs with Foreman API Not Working for Multiple SCSI Controllers and VolumesClosed
Related to Hammer CLI - Refactor #23973: Change Compute Resource help for create to look like host creatNew
Related to Hammer CLI - Bug #23473: Update hammer to correctly provision vmware VMs.Closed
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 presentClosed
Related to Hammer CLI - Bug #19702: Hammer host create, with vmware compute resource, cant use VMware network names, needs the network ID insteadClosed
Related to Hammer CLI - Feature #18885: Add hammer-cli help output telling user how to use VMWare storage pod / datastore clustersClosed
Related to Hammer CLI - Bug #12502: hammer host create using oVirt should use text IDs, not UUIDsDuplicate
Related to Hammer CLI - Bug #4309: hammer host start no longer powers on VMware hostClosed

History

#1 Updated by Oleh Fedorenko over 3 years ago

  • Related to Feature #26421: Implement multiple SCSIControllers for VMware backed host added

#2 Updated by Oleh Fedorenko over 3 years ago

  • Related to Bug #25584: Unclear error when not specifying the 'path' under --compute-attributes section added

#3 Updated by Oleh Fedorenko over 3 years ago

  • Related to Bug #25093: Provisioning VMs with Foreman API Not Working for Multiple SCSI Controllers and Volumes added

#4 Updated by Oleh Fedorenko over 3 years ago

  • Related to Refactor #23973: Change Compute Resource help for create to look like host creat added

#5 Updated by Oleh Fedorenko over 3 years ago

  • Related to Bug #23473: Update hammer to correctly provision vmware VMs. added

#6 Updated by Oleh Fedorenko over 3 years ago

  • Related to Bug #22171: create a host from hammer CLI to VMWare with error "Ressource host not found by id" when all the options are present added

#7 Updated by Oleh Fedorenko over 3 years ago

  • Related to Bug #19702: Hammer host create, with vmware compute resource, cant use VMware network names, needs the network ID instead added

#8 Updated by Oleh Fedorenko over 3 years ago

  • Related to Feature #18885: Add hammer-cli help output telling user how to use VMWare storage pod / datastore clusters added

#9 Updated by Oleh Fedorenko over 3 years ago

  • Related to Bug #12502: hammer host create using oVirt should use text IDs, not UUIDs added

#10 Updated by Oleh Fedorenko over 3 years ago

  • Related to Bug #4309: hammer host start no longer powers on VMware host added

#11 Updated by Shira Maximov over 2 years ago

  • Status changed from New to Closed

We have decided to close the tracker issue, and use a category instead

Also available in: Atom PDF