Cannot parse ipv6 address

[sourcecodemage]

This could be a documentation issue, as I can only find examples with IPv4 addresses.

When I run my playbook the reset and wait steps work fine, but the import config job failes.

PB

• name: Reset iDRAC dellemc_idrac_reset: idrac_ip: "{{ idrac_address }}" idrac_user: "{{ idrac_username }}" idrac_password: "{{ idrac_password }}"

• name: Waiting for iDRAC to respond wait_for: host: "{{ idrac_address }}" port: 443 delay: 60 connect_timeout: 300

• name: Import Server Configuration Profile from a local path idrac_server_config_profile: idrac_ip: "{{ idrac_address }}" idrac_user: "{{ idrac_username }}" idrac_password: "{{ idrac_password }}" idrac_port: "443" command: "import" share_name: "{{ playbook_dir }}/../conf" scp_file: "server_raid_config_clone.xml" scp_components: "RAID" job_wait: True when: "server_details.json.response.hostName| regex_search('cdnec|cdnmid|atsec|atsmid')"

  Error msg: "scp_status": {"Data": {"Message": "Failed to execute redfish request: Failed to parse: :443"

It concatenates the port at the end of the ip address. eg idrac_address: "::1" then the error is : "scp_status": {"Data": {"Message": "Failed to execute redfish request: Failed to parse: ::1:443"

Server Info Dell 740XD BIOS Version 1.4.5 iDRAC Firmware Version 3.21.21.21

Is there a special way that I should be formatting ipv6 addresses for the idrac_server_config_profile module? I tried putting square brackets around the address and that made it worse.

[anupamaloke]

@jagooch, we are looking into this issue. Also, will it be possible for you to raise a support ticket with Dell support too?

[sourcecodemage]

certainly. I noted that the ImportSystemConfigurationLocalFilenameREDFISH.py script in imports local xml configuration file fine. I haven't look at the source to what that script does differently. It doesn't use OMSDK, which may be the difference.

[rajeevarakkal]

@jagooch Care still facing this issue?

[anupamaloke]

Closing this issue due to inactivity for long. Please create a new issue if you run into this error.