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
ERROR! couldn't resolve module/action 'nsxt_fabric_compute_manager'. This often indicates a misspelling, missing collection, or incorrect module path
#481
Open
kkrishnasamy01 opened this issue
Nov 7, 2023
· 3 comments
"ERROR! couldn't resolve module/action 'nsxt_fabric_compute_manager'. This often indicates a misspelling, missing collection, or incorrect module path"
Reproduction steps
hosts: localhost
name: Register vCenter as a compute manager in NSX-T
gather_facts: false
vars_files: ../answerfile.yml
Describe the bug
Unable to add compute manager.
"ERROR! couldn't resolve module/action 'nsxt_fabric_compute_manager'. This often indicates a misspelling, missing collection, or incorrect module path"
Reproduction steps
hosts: localhost
name: Register vCenter as a compute manager in NSX-T
gather_facts: false
vars_files: ../answerfile.yml
tasks:
nsxt_fabric_compute_managers:
hostname: "{{ nsxt_hostname }}"
username: "{{ nsxt_admin_user }}"
password: "{{ nsxt_password }}"
validate_certs: "{{ nsxt_validate_certs }}"
display_name: "vCenter"
server: "{{ vcenter_hostname }}"
origin_type: "vCenter"
credential:
credential_type: "UsernamePasswordLoginCredential"
username: "{{ vcenter_username }}"
password: "{{ vcenter_password }}"
state: "present"
Expected behavior
hosts: localhost
name: Register vCenter as a compute manager in NSX-T
gather_facts: false
vars_files: ../answerfile.yml
tasks:
nsxt_fabric_compute_managers:
hostname: "{{ nsxt_hostname }}"
username: "{{ nsxt_admin_user }}"
password: "{{ nsxt_password }}"
validate_certs: "{{ nsxt_validate_certs }}"
display_name: "vCenter"
server: "{{ vcenter_hostname }}"
origin_type: "vCenter"
credential:
credential_type: "UsernamePasswordLoginCredential"
username: "{{ vcenter_username }}"
password: "{{ vcenter_password }}"
state: "present"
Additional context
No response
The text was updated successfully, but these errors were encountered: