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
# /root/.ansible/collections/ansible_collections
Collection Version
----------------- -------
community.windows 2.3.0
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
- name: Copy the current user's PSRepositories to all non-service account profiles and Default profilecommunity.windows.win_psrepository_copy:
Executed when there is a Profile in the ProfileList that is in a semi-corrupted state that has no ProfileImagePath defined:
EXPECTED RESULTS
Either all the time, or configurable through a module parameter, ignore keys that have no ProfileImagePath defined.
Alternatively, or in conjunction, allow the include/exclude filtering to occur BEFORE enumerating all of the defined profiles - as currently the Get-ProfileDirectory function used in the module performs the filtering AFTER attempting to enumerate all paths.
ACTUAL RESULTS
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: at <ScriptBlock>, <No file>: line 194
fatal: [server]: FAILED! => {"changed": false, "msg": "Unhandled exception while executing module: Property \"ProfileImagePath\" cannot be found."}
SUMMARY
win_psrepository_copy fails when the ProfileList registry key contains a subkey for a profile that is invalid with no ProfileImagePath defined.
Example of a profile registry key:
ISSUE TYPE
COMPONENT NAME
win_psrepository_copy module
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
Executed when there is a Profile in the ProfileList that is in a semi-corrupted state that has no ProfileImagePath defined:
EXPECTED RESULTS
Either all the time, or configurable through a module parameter, ignore keys that have no ProfileImagePath defined.
Alternatively, or in conjunction, allow the include/exclude filtering to occur BEFORE enumerating all of the defined profiles - as currently the Get-ProfileDirectory function used in the module performs the filtering AFTER attempting to enumerate all paths.
ACTUAL RESULTS
Exception details:
The text was updated successfully, but these errors were encountered: