-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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_command: VirtualMediaInsert does not work with Supermicro #4839
redfish_command: VirtualMediaInsert does not work with Supermicro #4839
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution! Could you please add a changelog fragment? Thanks.
The test
The test
The test
The test
The test
The test
The test
The test
|
f044816
to
0739826
Compare
@felixfontein I've just added the changelog could you please have a look. |
This looks good. Out of curiosity, does removing |
changelogs/fragments/4839-fix-VirtualMediaInsert-Supermicro.yml
Outdated
Show resolved
Hide resolved
changelogs/fragments/4839-fix-VirtualMediaInsert-Supermicro.yml
Outdated
Show resolved
Hide resolved
166e557
to
9ad4915
Compare
changelogs/fragments/4839-fix-VirtualMediaInsert-Supermicro.yml
Outdated
Show resolved
Hide resolved
changelogs/fragments/4839-fix-VirtualMediaInsert-Supermicro.yml
Outdated
Show resolved
Hide resolved
9ad4915
to
f4a4150
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. @mraineri is everything still fine for you?
One thing that came out in the group's review is that it's not really typical for a user to specify "inserted" or "write_protected" in these types of requests; while the standard allows for it, the real simple case is the user provides the image URI and the service does everything else needed. So, one of the questions that came up is if @FRUCHTiii really needs to provide "inserted" or "write_protected" in their playbook and if there's the possibility it can just be simplified on that end. But, if it's really needed, the changes look good. We'll just need to be cognizant of the possibility that Supermicro may add support for those parameters in the future. |
I don't know if I understand you correctly @mraineri But the code will insert it every time. My playbooks looks like this:
|
Ah, I see now. I was under the impression "inserted" and "write_protected" are only provided if specified in the playbook. Clearly that isn't the case here. Thanks for showing me this. Looks good on my end now! |
SUMMARY
ISSUE TYPE
COMPONENT NAME
redfish_command
ADDITIONAL INFORMATION
Supermicro does not support WriteProtected and Inserted to use by virtual media.
This fixes the issue und adds Supermicro as "image_only" like HP iLO4
Also Supermicro doesn't clear the ImageName after unmounting the ISO so we deleted this check and now just use inserted: false
before
after