Project

General

Profile

Actions

Bug #25993

closed

Changing disk of VMWare hosts does not actually alter the VM

Added by Sebastian Bublitz about 5 years ago. Updated about 5 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Compute resources - VMware
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Description of problem:

When altering a VMWare host's disk size via Foreman, the VM does not actually get altered and the disk stayes the same.
Foreman UI also displays the old size afterwards.
There are not error rendered neither in the UI nor in production.log
Changing the values for CPU and RAM works just fine. kakq95 on IRC also encountered this problem.

Expected outcome:
The VM disk should actually be altered or an error message rendered if there is in fact a problem.

Additional info:

# rpm -qa | egrep 'fog|foreman' | grep -v $(hostname -s)
tfm-rubygem-fog-openstack-0.1.25-2.el7.noarch
tfm-rubygem-fog-xml-0.1.2-6.el7.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.13-1.fm1_20.el7.noarch
foreman-postgresql-1.20.1-1.el7.noarch
foreman-installer-katello-3.9.1-1.el7.noarch
foreman-cli-1.20.1-1.el7.noarch
tfm-rubygem-fog-google-0.1.0-4.el7.noarch
foreman-installer-1.20.1-1.el7.noarch
tfm-rubygem-foreman_bootdisk-14.0.0-1.fm1_20.el7.noarch
tfm-rubygem-fog-vsphere-2.3.0-2.el7.noarch
foreman-selinux-1.20.1-1.el7.noarch
foreman-vmware-1.20.1-1.el7.noarch
foreman-debug-1.20.1-1.el7.noarch
tfm-rubygem-fog-digitalocean-0.3.0-3.el7.noarch
tfm-rubygem-fog-1.42.1-2.el7.noarch
tfm-rubygem-foreman-tasks-0.14.3-1.fm1_20.el7.noarch
rubygem-foreman_maintain-0.3.0-1.el7.noarch
tfm-rubygem-foreman_hooks-0.3.15-1.fm1_20.el7.noarch
foreman-release-scl-7-2.el7.noarch
tfm-rubygem-foreman-tasks-core-0.2.5-2.fm1_20.el7.noarch
tfm-rubygem-fog-aws-1.3.0-3.el7.noarch
tfm-rubygem-fog-ovirt-1.1.2-2.el7.noarch
foreman-1.20.1-1.el7.noarch
tfm-rubygem-foreman_discovery-14.0.0-1.fm1_20.el7.noarch
tfm-rubygem-fog-json-1.0.2-6.el7.noarch
tfm-rubygem-fog-xenserver-0.2.3-3.el7.noarch
tfm-rubygem-hammer_cli_foreman_docker-0.0.4-4.el7.noarch
tfm-rubygem-foreman_docker-4.1.0-2.fm1_20.el7.noarch
tfm-rubygem-foreman_remote_execution-1.6.7-1.fm1_20.el7.noarch
tfm-rubygem-fog-core-1.45.0-3.el7.noarch
tfm-rubygem-fog-rackspace-0.1.4-3.el7.noarch
tfm-rubygem-hammer_cli_foreman-0.15.1-1.el7.noarch
foreman-compute-1.20.1-1.el7.noarch
foreman-proxy-1.20.1-1.el7.noarch
tfm-rubygem-foreman_scc_manager-1.4.0-3.fm1_20.el7.noarch
tfm-rubygem-foreman_remote_execution_core-1.1.4-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-7.el7.noarch
tfm-rubygem-foreman_templates-6.0.3-2.fm1_20.el7.noarch
foreman-release-1.20.1-1.el7.noarch
tfm-rubygem-foreman_snapshot_management-1.5.0-3.fm1_20.el7.noarch

Actions #1

Updated by Sebastian Bublitz about 5 years ago

  • Status changed from New to Duplicate

I seam to be unable to figure out how to directly set the "duplicate of" value,so I put it here:
Duplicate of https://projects.theforeman.org/issues/25629

Actions

Also available in: Atom PDF