dell / ansible-powerscale

PowerScale (Isilon) Ansible modules
GNU General Public License v3.0
25 stars 21 forks source link

[BUG]: user and group module does not support specifying user_id/group_id at creation #48

Closed sigbjornaib closed 1 year ago

sigbjornaib commented 1 year ago

Describe the bug When creating a user or group where both the user_name and user_id for a new user, or group_name and group_id for a new group, an error is thrown:

"parameters are mutually exclusive: user_name|user_id"

Specifying a uidnumber or gidnumber when creating users and groups using the Isilon CLI is supported and works.

isi auth groups add group1000 --gid 1000 --zone myzone --provider local

To Reproduce Steps to reproduce the behavior:

  1. Write a task using dellemc.powerscale.user or dellemc.powerscale.group
  2. Enter a group_name/user_name in the task
  3. Enther a group_id/user_id in the same task. ... n. Step n See error
      - name: Create/Modify Local Groups
        dellemc.powerscale.group:
          onefs_host: "{{ onefs_hostname }}"
          port_no: "{{ onefs_port }}"
          verify_ssl: "{{ onefs_verify_ssl }}"
          api_user: "{{ api_user }}"
          api_password: "{{ api_password }}"
          group_name: "group{{ item.gidnumber }}"
          group_id: "{{ item.gidnumber }}"
          access_zone: "{{ item.access_zone }}"
          provider_type: "local"
          state: "{{ item.state | default('present') }}"
        loop: "{{ isilon_groups }}"

Expected behavior We need to create local users for legacy systems with specific uidnumbers/gidnumbers. We have automated almost all the Isilon/Powerscale setup using Ansible. Not being able to create users and groups is a setback for a fully automated Isilon/Powerscale setup.

Screenshots If applicable, add screenshots to help explain your problem.

Logs If applicable, submit logs or stack traces from the affected services

System Information (please complete the following information):

anupamaloke commented 1 year ago

@sigbjornaib, thank you for reporting this issue. This has been added to the v1.9.0 milestone.

anupamaloke commented 1 year ago

Fixed by #51