-
Notifications
You must be signed in to change notification settings - Fork 163
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
[BUG]: unable to set IscsiDev1ConXVlanID #682
Labels
Comments
sistarers
added
needs-triage
Issue requires triage.
type/bug
Something isn't working
labels
Jun 14, 2024
error(s) below, I initiated the playbook with the following command. If the eventvlan variable in the playbook is set using -- eventvlan: anyInteger an the -e eventvlan=anyInteger is not passed then the playbook executes successfully.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description
See #648 for additional details. The same ansible controller, version, dellemc.ome collection etc is now unable to set the IscsiDev1ConXVlanID value.
ansible [core 2.14.14]
config file = /etc/ansible/ansible.cfg
configured module search path = ['/home/ncraf/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3.9/site-packages/ansible
ansible collection location = /home/ncraf/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/local/bin/ansible
python version = 3.9.18 (main, Jan 24 2024, 00:00:00) [GCC 11.4.1 20231218 (Red Hat 11.4.1-3)] (/usr/bin/python3)
jinja version = 3.1.2
libyaml = True
Component or Module Name
dellemc.openmanage.idrac_bios:
Ansible Version
Ansible 2.14.14
Python Version
Python 3.9.18
iDRAC/OME/OME-M version
iDRAC: 7.00.00.171, BIOS: 2.9.4
iDRAC: 7.10.30.05, BIOS: 2.1.5
Operating System
N/A but O/S will eventually be esxi 8.x or 7.x: this setting is required in order for the blade to find it's boot disk via iSCSI so the O/S can be installed
Playbook Used
will upload in subsequent post
Logs
[UP - Set BIOS to default settings using specific A/V pairs MX760s] *****************************
Wednesday 12 June 2024 19:51:26 +0000 (0:00:00.063) 0:00:03.695 ********
Wednesday 12 June 2024 19:51:26 +0000 (0:00:00.063) 0:00:03.694 ********
fatal: [cmc_2Y5MW04_blade1-9W5MW04 -> localhost]: FAILED! => {"changed": false, "msg": "HTTP Error 400 on PATCH request to 'https://10.200.4.166/redfish/v1/Systems/System.Embedded.1/Bios/Settings', extended message: 'Unable to set the object properties because an incorrect object value is entered.'"}
TASK [UP - Set BIOS to default settings using specific A/V pairs MX740s] *****************************
Wednesday 12 June 2024 19:51:29 +0000 (0:00:03.884) 0:00:07.579 ********
Wednesday 12 June 2024 19:51:29 +0000 (0:00:03.884) 0:00:07.578 ********
fatal: [cmc_CP40PZ3_blade2-D2NK243 -> localhost]: FAILED! => {"changed": false, "msg": "HTTP Error 400 on PATCH request to 'https://10.200.4.209/redfish/v1/Systems/System.Embedded.1/Bios/Settings', extended message: 'Unable to set the object properties because an incorrect object value is entered.'"}
Steps to Reproduce
run playbook on different platforms of mx740c and mx760c blades
Expected Behavior
vlan integer value is set per the playbook either by variable or by hard coded value in playbook
Actual Behavior
error above occurs
Screenshots
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: