Open b4ldr opened 9 months ago
@b4ldr Thanks for reporting this issue. Can you try with IPv4 address instead of fqdn and let us know if the issue reproducible. Also, Please let us know how did you configure the fqdn for the idrac.
@sachin-apa if i use the IP address, i get a 401 username and password error. however testing with python and the same password works well
In [26]: s = Session()
In [27]: s.auth = ('dns0ps', password)
In [28]: s.headers.update({"Accept": "application/json"})
In [29]: s.verify = False
In [30]: r = s.get('https://199.43.132.142/redfish/v1/Managers')
/Users/john.bond/Library/Python/3.9/lib/python/site-packages/urllib3/connectionpool.py:1099: InsecureRequestWarning: Unverified HTTPS request is being made to host '199.43.132.142'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#tls-warnings
warnings.warn(
In [31]: r.ok
Out[31]: True
In [32]: r.json()
Out[32]:
{'@odata.context': '/redfish/v1/$metadata#ManagerCollection.ManagerCollection',
'@odata.id': '/redfish/v1/Managers',
'@odata.type': '#ManagerCollection.ManagerCollection',
'Description': 'BMC',
'Members': [{'@odata.id': '/redfish/v1/Managers/iDRAC.Embedded.1'}],
'Members@odata.count': 1,
'Name': 'Manager'}
ansible output
fatal: [ae01.xz-stp.l.dns.icann.org -> localhost]: FAILED! => {
"changed": false,
"error_info": {
"error": {
"@Message.ExtendedInfo": [
{
"Message": "Unable to complete the operation because an invalid username and/or password is entered, and therefore authentication failed.",
"MessageArgs": [],
"MessageArgs@odata.count": 0,
"MessageId": "IDRAC.2.9.SYS415",
"RelatedProperties": [],
"RelatedProperties@odata.count": 0,
"Resolution": "Enter valid user name and password and retry the operation.",
"Severity": "Warning"
}
],
"code": "Base.1.12.GeneralError",
"message": "A general error has occurred. See ExtendedInfo for more information"
}
},
"invocation": {
"module_args": {
"ca_path": null,
"force": true,
"idrac_ip": "199.43.132.142",
"idrac_password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
"idrac_port": 443,
"idrac_user": "root",
"resource_id": null,
"timeout": 30,
"validate_certs": false,
"virtual_media": [
{
"domain": null,
"image": "https://download.dns.icann.org/dban-2.2.8_i586.iso",
"index": null,
"insert": true,
"media_type": null,
"password": null,
"username": null
}
]
}
},
"msg": "HTTP Error 401: Unauthorized"
}
thanks john
@b4ldr i tried to reproduce this in our lab, but i'm not able to reproduce this. I see http error is coming from the iDRAC not from ansible/module/url lib.. We might need a session to debug this further.
Request you to please go to Dell Support, enter your Servicetag and then raise a technical support request. You must have an existing and valid warranty on your server before you can raise a SR.
@anupamaloke
I had the same behaviour while configuring a batch of new R760xa servers with the task below:
- name: Configure iDRAC Rac name
dellemc.openmanage.idrac_attributes:
idrac_ip: "{{ ipmi_host }}"
idrac_user: "{{ ipmi_user }}"
idrac_password: "{{ ipmi_password }}"
ca_path: "{{ idrac_ca_path | default(omit) }}"
validate_certs: "{{ idrac_validate_certs | default(omit) }}"
idrac_attributes:
NIC.1.DNSRacName: "{{ inventory_hostname }}-ipmi"
NIC.1.DNSDomainName: "{{ idrac_dns_domain_name }}"
delegate_to: localhost
My inventory defines ipmi_host: "{{ inventory_hostname }}-ipmi"
but the hostname of the iDRAC is still the default one (idrac-SERVICE_TAG
). A wokaround is to use idrac_ip: "{{ lookup('community.general.dig', ipmi_host) }}"
instead.
Is it related to idrac_ip
being a different hostname than the one configured in the iDRAC?
This task used to work last year when I configured another batch of nodes (XE8545).
@b4ldr,
Could you please let us know if this issue is resolved?
Bug Description
When using
dellemc.openmanage.idrac_virtual_media
i get the following errorComponent or Module Name
idrac_virtual_media
Ansible Version
2.16.2
Python Version
3.12
iDRAC/OME/OME-M version
iDRAC: 7.00.60.00
Operating System
Mac sonoma 14.1.1
Playbook Used
Logs
Steps to Reproduce
Run the cookbook
Expected Behavior
Would expect the remote iso to be mounted
Actual Behavior
Get a 400 error with the following message
Screenshots
No response
Additional Information
No response