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
when the playbook for infra setup is played - add compute manager - and nsxt_fabric_compute_managers.py is run trust in not enabled, as such you will need to login via the gui and edit the compute manager manually.
If trust is not enabled when you try to configure a vsphere cluster with a transport node profile you get the below error
'error_message': 'NSX cannot be enabled on vLCM enabled cluster as trust is not enabled on Compute Manager. Please enable trust on Compute Manager [5c7d1a85-cb3e-4c68-a8ed-a0b8177f05da] to enable NSX on vLCM clusters.'})]."}
Reproduction steps
deploy an NSX-Manager
configure a compute manager
create transport zones, tep ip pools, uplink profiles, an a transport node profile
try to play the transport node collections playbook
error is returned
Expected behavior
I would expect the vsphere cluster to be nsx prepared
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Hello,
when the playbook for infra setup is played - add compute manager - and nsxt_fabric_compute_managers.py is run trust in not enabled, as such you will need to login via the gui and edit the compute manager manually.
If trust is not enabled when you try to configure a vsphere cluster with a transport node profile you get the below error
'error_message': 'NSX cannot be enabled on vLCM enabled cluster as trust is not enabled on Compute Manager. Please enable trust on Compute Manager [5c7d1a85-cb3e-4c68-a8ed-a0b8177f05da] to enable NSX on vLCM clusters.'})]."}
Reproduction steps
deploy an NSX-Manager
configure a compute manager
create transport zones, tep ip pools, uplink profiles, an a transport node profile
try to play the transport node collections playbook
error is returned
Expected behavior
I would expect the vsphere cluster to be nsx prepared
Additional context
No response
The text was updated successfully, but these errors were encountered: