You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 11, 2020. It is now read-only.
Thanks for submitting an issue to pcf-pipelines.
Please note that this repository will be officially deprecated soon.
To help us triage the issue, please fill out the following form as much as you can:
Issue
upgrade-ops-manager/vsphere/pipeline.yml
If the using "vcenter_cluster" param and not the "vcenter_resource_pool" the resource pool is still mapped to the deploy-opsman-vm task.
This throws an error "govc: no such VM" as the govc command on line 68 of deply-opsman-vm/task.sh will be missing an arguement;
old_opsman_path="$(govc find "${GOVC_RESOURCE_POOL}" -type m -guest.ipAddress "${OPSMAN_IP}" -runtime.powerState poweredOn)"
Context
This throws an error "govc: no such VM" as the govc command on line 68 of deply-opsman-vm/task.sh will be missing an arguement;
old_opsman_path="$(govc find "${GOVC_RESOURCE_POOL}" -type m -guest.ipAddress "${OPSMAN_IP}" -runtime.powerState poweredOn)"
Expected result
if the resource pool param is empty, use the cluster param instead for deply-opsman-vm/task.sh
Current result
during tsk deply-opsman-vm receive the following error when "Shutting down OLD OpsMgr VM..."
govc: no such VM
Steps to Reproduce
leave the param "vcenter_resource_pool:" blank when running upgrade-ops-manager/vsphere/pipeline.yml
Possible Fix
Use the vcenter_cluster param if vcenter_resource_pool is blank
Logs and Screenshots
unable to send through screenshots due to corp policies.
Importing OVA of new OpsMgr VM...
Running govc import.ova -options=opsman_settings.json /tmp/build/39dbd1bf/pivnet-opsmgr/pcf-vsphere-2.3-build.194.ova
[12-11-18 06:02:44] Uploading pivotal-ops-manager-disk1.vmdk... OK
Setting CPUs on new OpsMgr VM... /{{DC_NAME}}/ControlPlane/OpsManager-2.3.5-20181112060121
Shutting down OLD OpsMgr VM... {{ip_address}}
govc: no such VM
The text was updated successfully, but these errors were encountered:
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
Thanks for submitting an issue to pcf-pipelines.
Please note that this repository will be officially deprecated soon.
To help us triage the issue, please fill out the following form as much as you can:
Issue
upgrade-ops-manager/vsphere/pipeline.yml
If the using "vcenter_cluster" param and not the "vcenter_resource_pool" the resource pool is still mapped to the deploy-opsman-vm task.
This throws an error "govc: no such VM" as the govc command on line 68 of deply-opsman-vm/task.sh will be missing an arguement;
old_opsman_path="$(govc find "${GOVC_RESOURCE_POOL}" -type m -guest.ipAddress "${OPSMAN_IP}" -runtime.powerState poweredOn)"
Context
This throws an error "govc: no such VM" as the govc command on line 68 of deply-opsman-vm/task.sh will be missing an arguement;
old_opsman_path="$(govc find "${GOVC_RESOURCE_POOL}" -type m -guest.ipAddress "${OPSMAN_IP}" -runtime.powerState poweredOn)"
Expected result
if the resource pool param is empty, use the cluster param instead for deply-opsman-vm/task.sh
Current result
during tsk deply-opsman-vm receive the following error when "Shutting down OLD OpsMgr VM..."
govc: no such VM
Steps to Reproduce
leave the param "vcenter_resource_pool:" blank when running upgrade-ops-manager/vsphere/pipeline.yml
Possible Fix
Use the vcenter_cluster param if vcenter_resource_pool is blank
Logs and Screenshots
unable to send through screenshots due to corp policies.
Importing OVA of new OpsMgr VM...
Running govc import.ova -options=opsman_settings.json /tmp/build/39dbd1bf/pivnet-opsmgr/pcf-vsphere-2.3-build.194.ova
[12-11-18 06:02:44] Uploading pivotal-ops-manager-disk1.vmdk... OK
Setting CPUs on new OpsMgr VM... /{{DC_NAME}}/ControlPlane/OpsManager-2.3.5-20181112060121
Shutting down OLD OpsMgr VM... {{ip_address}}
govc: no such VM
The text was updated successfully, but these errors were encountered: