Creation of an NSX-T backed workload domain in VMware Cloud Foundation fails with the error message UNABLE_TO_UPDATE_TRANSPORT_NODE
Article ID: 316983
Updated On:
Products
VMware Cloud Foundation
Issue/Introduction
Symptoms:
- Creation of an NSX-T backed workload domain in VMware Cloud Foundation fails with the error message UNABLE_TO_UPDATE_TRANSPORT_NODE
- One or more NSX-T backed workload domains have been created successfully in the past
- Manual changes have been made to the NSX-T transport zones and/or logical switches
- You see messages similar to the following in the /var/log/vmware/vcf/domainmanager/domainmanager.log file on the SDDC Manager VM:
2019-05-07 16:06:19.661 [vcf_dm,80f0bef3076de0ea,8070154c76a72765] [-thread-14] INFO [ c.v.e.s.o.core.ProcessingTaskSubscriber] Invoking method of task UpdateHostTransportZoneAction (Update host transport zone), e3d86130-70de-11e9-8eb8-e7a8a394304e..
2019-05-07 16:06:20.172 [vcf_dm,80f0bef3076de0ea,8070154c76a72765] [-thread-14] ERROR [ c.v.v.c.f.p.n.a.UpdateHostTransportZoneAction] UNABLE_TO_UPDATE_TRANSPORT_NODE
com.vmware.vapi.std.errors.InvalidRequest: InvalidRequest (com.vmware.vapi.std.errors.invalid_request) => {
messages = [],
data = struct => {error_message=The uplink teaming policy name/s [[TOR 1, TOR 2]] is/are not specified in the TranportNode's attached uplink profile [BaseHostSwitchProfile/0a26d126-7116-11e5-9d70-feff819cdc9f]., httpStatus=BAD_REQUEST, error_code=8516, module_name=NsxSwitching service}
}
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
2019-05-07 16:06:20.172 [vcf_dm,80f0bef3076de0ea,8070154c76a72765] [-thread-14] ERROR [ c.v.v.c.f.p.n.a.UpdateHostTransportZoneAction] UNABLE_TO_UPDATE_TRANSPORT_NODE
com.vmware.vapi.std.errors.InvalidRequest: InvalidRequest (com.vmware.vapi.std.errors.invalid_request) => {
messages = [],
data = struct => {error_message=The uplink teaming policy name/s [[TOR 1, TOR 2]] is/are not specified in the TranportNode's attached uplink profile [BaseHostSwitchProfile/0a26d126-7116-11e5-9d70-feff819cdc9f]., httpStatus=BAD_REQUEST, error_code=8516, module_name=NsxSwitching service}
}
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
Environment
VMware Cloud Foundation 3.5.x
VMware Cloud Foundation 3.7.x
VMware Cloud Foundation 3.7.x
Resolution
This is a known issue affecting VMware Cloud Foundation. There is currently no resolution.
Workaround:
Workaround:
- Download 68172_vcf-domain-manager.zip .
- Use a file transfer utility to copy 68172_vcf-domain-manager.zip to the /tmp folder on the SDDC Manager VM (as the vcf user).
- SSH to the SDDC Manager as the vcf user and then issue the su - command to switch to the root user.
- Issue the following commands to install the vcf-domain-manager-3.5.1-13760427 patch:
unzip -c /tmp/ /tmp/68172_vcf-domain-manager.zip
rpm -Uhv /tmp/vcf-domain-manager-3.5.1-13760427.noarch.rpm
Note: You will see output similar to the following:
Archive: /tmp/68172_vcf-domain-manager.zip
inflating: /tmp/vcf-domain-manager-3.5.1-13760427.noarch.rpm
Preparing... ################################# [100%]
Updating / installing...
1:vcf-domain-manager-3.5.1-13760427################################# [ 50%]
+ test 2 -eq 1
+ systemctl daemon-reload
+ systemctl restart domainmanager.service
Cleaning up / removing...
2:vcf-domain-manager-3.5.0-11215621################################# [100%]
rpm -Uhv /tmp/vcf-domain-manager-3.5.1-13760427.noarch.rpm
Note: You will see output similar to the following:
Archive: /tmp/68172_vcf-domain-manager.zip
inflating: /tmp/vcf-domain-manager-3.5.1-13760427.noarch.rpm
Preparing... ################################# [100%]
Updating / installing...
1:vcf-domain-manager-3.5.1-13760427################################# [ 50%]
+ test 2 -eq 1
+ systemctl daemon-reload
+ systemctl restart domainmanager.service
Cleaning up / removing...
2:vcf-domain-manager-3.5.0-11215621################################# [100%]
- Issue the following command to validate that the version of the domainmanager component is upgraded to 3.5.1-13760427:
curl http://localhost/domainmanager/about
Note: You should see output similar to the following:
{
"id": "1f0a90ad-bf26-4358-a3bf-d217f7e8ffdc",
"name": "DOMAIN_MANAGER",
"version": "3.5.1-RELEASE-13760427",
"status": "ACTIVE",
"serviceUrl": "http://127.0.0.1:7200/domainmanager",
"description": "Domain Manager"
Note: You should see output similar to the following:
{
"id": "1f0a90ad-bf26-4358-a3bf-d217f7e8ffdc",
"name": "DOMAIN_MANAGER",
"version": "3.5.1-RELEASE-13760427",
"status": "ACTIVE",
"serviceUrl": "http://127.0.0.1:7200/domainmanager",
"description": "Domain Manager"
- Issue the following command to make a copy of the /opt/vmware/vcf/lcm/lcm-app/conf/VersionAlias.yml file:
cp -fp /opt/vmware/vcf/lcm/lcm-app/conf/VersionAlias.yml /opt/vmware/vcf/lcm/lcm-app/conf/VersionAlias.yml.$(date +%Y%m%d)
- Open the /opt/vmware/vcf/lcm/lcm-app/conf/VersionAlias.yml file with a text editor and add the following to the end of the file.
DOMAIN_MANAGER:
- base: 3.5.1-RELEASE-12050813
alias:
- 3.5.1-RELEASE-13760427
- base: 3.5.1-RELEASE-12050813
alias:
- 3.5.1-RELEASE-13760427
- Save and close the file.
- Restart the lcm service by issuing the systemctl restart lcm command.
Additional Information
Impact/Risks:
A snapshot of the SDDC Manager VM should be taken prior to implementing the steps noted in the workaround. The snapshot can be removed once the workaround has been validated.
A snapshot of the SDDC Manager VM should be taken prior to implementing the steps noted in the workaround. The snapshot can be removed once the workaround has been validated.
Feedback
Yes
No
Powered by
