Skip to content

Add new vendor Dell#79

Open
simcod wants to merge 45 commits intomasterfrom
dell-v2
Open

Add new vendor Dell#79
simcod wants to merge 45 commits intomasterfrom
dell-v2

Conversation

@simcod
Copy link
Contributor

@simcod simcod commented Sep 19, 2025

Description

Add new vendor Dell

@izvyk
Copy link

izvyk commented Oct 13, 2025

There's still one problem I don't have a good solution for. After you set the boot order you have to reboot to apply changes. If you change your mind before the reboot it fails to set the values because of the pending request.

The first idea is to only apply the last change right before the reboot, which means in case of a failure it fails long time after it was set. And deferring the operation seems also quite complicated, no other function in the project requires this. So not a suitable good approach.

Another option is to create a job explicitly instead of issuing the boot order change request. And then delete the job in the job queue by its id (if you change your mind). That's better, but also not ideal.

Any thoughts on this? Do we have such a use case?

@simcod
Copy link
Contributor Author

simcod commented Oct 14, 2025

There's still one problem I don't have a good solution for. After you set the boot order you have to reboot to apply changes. If you change your mind before the reboot it fails to set the values because of the pending request.

The first idea is to only apply the last change right before the reboot, which means in case of a failure it fails long time after it was set. And deferring the operation seems also quite complicated, no other function in the project requires this. So not a suitable good approach.

Another option is to create a job explicitly instead of issuing the boot order change request. And then delete the job in the job queue by its id (if you change your mind). That's better, but also not ideal.

Any thoughts on this? Do we have such a use case?

How about triggering a reboot after the boot order was changed successfully?

@izvyk
Copy link

izvyk commented Oct 14, 2025

How about triggering a reboot after the boot order was changed successfully?

If reboot is no problem, I'll implement that now. Thank you!

@majst01
Copy link
Contributor

majst01 commented Oct 14, 2025

There's still one problem I don't have a good solution for. After you set the boot order you have to reboot to apply changes. If you change your mind before the reboot it fails to set the values because of the pending request.
The first idea is to only apply the last change right before the reboot, which means in case of a failure it fails long time after it was set. And deferring the operation seems also quite complicated, no other function in the project requires this. So not a suitable good approach.
Another option is to create a job explicitly instead of issuing the boot order change request. And then delete the job in the job queue by its id (if you change your mind). That's better, but also not ideal.
Any thoughts on this? Do we have such a use case?

How about triggering a reboot after the boot order was changed successfully?

This would lead to a massive delay during the installation process, not a good idea

@izvyk izvyk self-assigned this Oct 16, 2025
@Gerrit91 Gerrit91 moved this to In Progress in Development Jan 26, 2026
@majst01 majst01 marked this pull request as ready for review February 4, 2026 07:56
@majst01 majst01 requested a review from a team as a code owner February 4, 2026 07:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

4 participants