Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

redfish_storage_volume not idempotent #245

Closed
akamac opened this issue Mar 3, 2021 · 2 comments · Fixed by #391
Closed

redfish_storage_volume not idempotent #245

akamac opened this issue Mar 3, 2021 · 2 comments · Fixed by #391
Labels
area/idrac idrac modules type/feature A feature. This label is applied to a feature issues.
Milestone

Comments

@akamac
Copy link

akamac commented Mar 3, 2021

Hi there,

I have a task:

- redfish_storage_volume:
    <<: *auth_redfish
    state: present
    volume_type: Mirrored
    name: root
    controller_id: RAID.Integrated.1-1
    volume_id: Disk.Virtual.0:RAID.Integrated.1-1
    drives:
      - Disk.Bay.0:Enclosure.Internal.0-1:RAID.Integrated.1-1
      - Disk.Bay.1:Enclosure.Internal.0-1:RAID.Integrated.1-1
    capacity_bytes: "{{ disks.capacity | human_to_bytes }}"
    optimum_io_size_bytes: 65536

When I run it for the first time, it works just fine.
Second time it fails with:

fatal: [<redacted>]: FAILED! => changed=false
  error_info:
    error:
      '@Message.ExtendedInfo':
      - Message: Unable to complete the operation because either the Fully Qualified Device Descriptor (FQDD) entered did not match any virtual drive (VD), the physical drives available, or the operation is not supported on the physical drive (s).
        MessageArgs: []
        MessageArgs@odata.count: 0
        MessageId: IDRAC.2.2.STOR009
        RelatedProperties: []
        RelatedProperties@odata.count: 0
        Resolution: 'Make sure of the following and retry the operation: 1) A physical drive or virtual drive with the FQDD entered exists. 2) The physical drive (s) supports the operation being tried. For more information about supported physical drives, see the iDRAC User''s Guide available on the support site.'
        Severity: Warning
      code: Base.1.7.GeneralError
      message: A general error has occurred. See ExtendedInfo for more information
  msg: 'HTTP Error 400: Bad Request'

Anything I'm doing wrong?

@anupamaloke anupamaloke moved this from To do to In progress in OpenManage Ansible Collection Feb 3, 2022
@anupamaloke anupamaloke added this to the v5.1.0 milestone Feb 3, 2022
@anupamaloke anupamaloke added the type/feature A feature. This label is applied to a feature issues. label Mar 9, 2022
@anupamaloke anupamaloke modified the milestones: v5.1.0, v5.3.0 Mar 9, 2022
@anupamaloke anupamaloke added area/idrac idrac modules and removed idempotency labels Mar 9, 2022
@sachin-apa sachin-apa linked a pull request Mar 28, 2022 that will close this issue
@sachin-apa
Copy link
Collaborator

This was added to list of release by mistake, reopening the issue

@sachin-apa sachin-apa reopened this Mar 29, 2022
@jagadeeshnv jagadeeshnv moved this from In progress to Done in OpenManage Ansible Collection Apr 26, 2022
@anupamaloke
Copy link
Contributor

Closed #402

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/idrac idrac modules type/feature A feature. This label is applied to a feature issues.
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

4 participants