nim_alt_disk_migration role can't find "internal" directory

[AIXperts]

Describe the bug
When using the nim_alt_disk_migration role from the 1.9.2 collection, it starts running through the tasks but fails on finding the nim_select_target_disk.py file which has been put in plugins/modules/internal/.

To Reproduce
Steps to reproduce the behavior:

1. Download and un-pack 1.9.2 collection
2. Unpack in base reposiroty
3. Use the role in a playbook:

• name: Perform 7.2 to 7.3 migration
  include_role:
  name: nim_alt_disk_migration
  apply:
  delegate_to: "{{ nimserver }}"
  vars:
  target_disk:
  disk_name: hdisk1
  lpp_source: 7300-02-00-2345_lpp_source
  spot: spot_7300-02-00
  register: nimadm_results

• name: "Debug: nimadm_results"
  debug: var=nimadm_results

4. Error is:

TASK [Perform 7.2 to 7.3 migration] ********************************************
task path: /runner/project/ansible/playbooks/aix_upgrade-73TL2SP0.yml:51

ERROR! couldn't resolve module/action 'ibm.power_aix.internal.nim_select_target_disk'. This often indicates a misspelling, missing collection, or incorrect module path.

Expected behavior
Expected task to run successfully on target host and for playbook to complete

Screenshots

TASK [Perform 7.2 to 7.3 migration] ********************************************
task path: /runner/project/ansible/playbooks/aix_upgrade-73TL2SP0.yml:51

ERROR! couldn't resolve module/action 'ibm.power_aix.internal.nim_select_target_disk'. This often indicates a misspelling, missing collection, or incorrect module path.

Environment (please complete the following information):

• OS: Linux RHEL 8.6
• Python Version: 3.9.7
• OpenSSH Version: OpenSSH_8.0p1, OpenSSL 1.1.1k FIPS 25 Mar 2021
• Ansible Version: AWX 24.6.1
• AIX Collection Version: 1.9.2

Additional context
Add any other context about the problem here.

[schamola]

Hi @AIXperts !
Thanks for reporting the issue, we are looking into it.
Will update here soon.

[schamola]

Hi @AIXperts
We were not able to recreate this issue on our environment.
It seems to be an environment specific issue, can you please give more details about your directory structure and environment ?

Moreover, can you please confirm if the other modules are running fine, or are they also throwing this error ??