Ops Manager version Upgrade via Concourse pipeline failed with error "govc: The provided network mapping between OVF networks and the system network is not supported by any host."

Products

• Operations Manager
• Concourse for VMware Tanzu

Issue/Introduction

The customer is upgrading the Ops Manager version and they are having an issue with rebuilding the opsman VM. They are getting the following error from the Concourse pipeline output.

+ om vm-lifecycle upgrade-opsman --config config/config/templates/opsman.yml --image-file 'image/[ops-manager,###+LTS-T]ops-manager-vsphere-###+LTS-T.ova' --state-file state/opsman-state.yml --installation installation/installation.zip --env-file env/env.yml --vars-file config/config/defaults/opsman.yml --vars-file vars/###/###/tile-config/opsman.yml --vars-file vars/###/###/###/tile-config/opsman.yml --vars-file vars/###/###/###/tile-config/opsman.yml
15:44:20 
15:44:20 Executing: "/rootfs/usr/bin/om --env env/env.yml --skip-ssl-validation curl --path /api/v0/info"
15:44:20 This could take a few moments...
15:45:50 /rootfs/usr/bin/om[stderr]: 2024/07/31 19:45:50 failed to make api request: failed submitting request: could not make api request to unlock endpoint: Put "https://opsman.example.net/api/v0/unlock": dial tcp ###.###.###.##:443: i/o timeout
15:45:50 creating the new opsman vm
15:45:50 Using vSphere...
15:45:50 
15:45:50 Executing: "govc import.ova -options=/tmp/options.json### image/[ops-manager,###+LTS-T]ops-manager-vsphere-###+LTS-T.ova"
15:45:50 This could take a few moments...
15:45:51 govc[stderr]: govc: The provided network mapping between OVF networks and the system network is not supported by any host.
15:45:51 2024/07/31 19:45:51 could not create the vm: unexpected error: govc error: govc error: exit status 1

Cause

The issue was due to customer incorrect config.

Resolution

The fact that the wrong resource pool was being passed made govc point to EXSi hosts that were not attached to the VDS.

/Datacenter/host/<cluster name>/Resources/<resource pool>

 

There are some useful troubleshooting steps: 

• Check if resource pool is existing in vSphere
• Check if the targeted host and network combo are correct in vSphere:

Below is the example of Network mapping in env:

"NetworkMapping":
   {
        "Name":"Network 1",
        "Network":"<Distributed_switch-name>/<Distributed_port_group-name>"
    }

Login to vSphere Client --> Search the Distributed_switch name --> Navigate to the Hosts Tab --> Check the Cluster column

• Use fly intercept command pop you right into the build's containers, which can be useful for debugging: 

$ fly -t example intercept -j some-pipeline/some-job -b some-build -s some-step

Below is an example:

root@d68e98f1-146a-4f4f-5ac8-a36b17d4f585:/tmp/build/7c5e83d7# env | grep -i resource
OM_VAR_terraform_om_resource_pool=/wh-####/host/wh-###aaa/Resources/###-prod
GOVC_RESOURCE_POOL=/wh-####/host/wh-###bbbb/Resources/###-prod

root@d68e98f1-146a-4f4f-5ac8-a36b17d4f585:/tmp/build/7c5e83d7# export OM_VAR_terraform_om_resource_pool=/wh-####/host/wh-###bbb/Resources/###-prod

root@d68e98f1-146a-4f4f-5ac8-a36b17d4f585:/tmp/build/7c5e83d7# om vm-lifecycle upgrade-opsman --config config/config/templates/opsman.yml --image-file 'image/[ops-manager,###+LTS-T]ops-manager-vsphere-###+LTS-T.ova' --state-file state/opsman-state.yml --installation installation/installation.zip --env-file env/env.yml --vars-file config/config/defaults/opsman.yml --vars-file vars/###/###/tile-config/opsman.yml --vars-file vars/###/###/###/tile-config/opsman.yml --vars-file vars/###/###/###/tile-config/opsman.yml