Start a Conversation

Solved!

Go to Solution

1 Rookie

 • 

2 Posts

1464

September 15th, 2022 14:00

PowerScale Ansible Module v1.6 dellemc.powerscale.smb returns ******** for character "a"?

Hello, Looking for help resolving this problem.

I’m trying to gather SMB share details from the shares as suggested in SMB module documentation: ansible-powerscale/Product Guide.md at 1.6.0 · dell/ansible-powerscale (github.com)

This is how I use the module in my code:

name: Get SMB share permissions from the cluster
dellemc.powerscale.smb:
onefs_host: "{ {onefs_host}}"
verify_ssl: "{ {verify_ssl}}"
api_user: "{ {api_user}}"
api_password: "{ {api_password}}"
access_zone: "{ {item.zone}}"
share_name: "{ {item.share}}"
state: present
register: getpermissions_result
with_items: "{ {share_list}}"

The output returned, however, is very unexpected.  It shows status "changed" instead of the expected "ok", and the output also contains some "a" characters replaced with eight asterisk* characters in its place.  Is this a known issue with 1.6.0 PowerScale module?  Any help as to resolve it / troubleshoot it?

Expected behavior example...

ok: [DBISILONSIMULATOR] => (item={'share': 'CreatedFromAnsible', 'zone': 'testzone'}) => { "ansible_loop_var": "item", "changed": false, "invocation": { "module_args": { "access_based_enumeration": null, "access_based_enumeration_root_only": null, "access_zone": "testzone", "api_password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",...... "create_permissions": "default acl",

Unexpected behavior example...

changed: [fbkppexfer] => (item={'share': 'PKITA_24891470_ADT', 'zone': 'PPEXFER-Ring0'}) => { "ansible_loop_var": "item", "changed": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",.... ", "create_permissions": "def********ult ********cl",

 

1 Rookie

 • 

2 Posts

September 19th, 2022 12:00

Update:  possible that customer used default credentials with a password of "a".  Although, it should not reflect status: changed in any way, this is designed to protect a password if it is inadvertently typed into the ansible parameters.  

Potential workaround:  asking customer to change the password to something less common than "a" and retest

Bug fix:  how to go about requesting that?  Git Hub?

1 Rookie

 • 

79 Posts

September 20th, 2022 03:00

Hi @JshMyr ,

Yes, the issue can be raised here for tracking https://github.com/dell/ansible-powerscale/issues

Thanks,

Jennifer

1 Message

September 21st, 2022 23:00

Update:  although this is a bug, if the customer has set their dashboard password to "a" then it will fail. The only way we have found to work around this is to send over a dropdown of just one password option, so that they can type in their own password without having it stored in plain text anywhere. I can't find any other way to do this (it's not relevant with Ansible).

No Events found!

Top