Skip to content
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

F27 devel fix leaving storage spoke with no disk #1212

Conversation

rvykydal
Copy link
Contributor

No description provided.

…#1496327)

Leaving the storage spoke with all disk unselected is currently there as a way
to get back out of the spoke. In this special case the storage is not reset (to
snapshot) when leaving the spoke, so it doesn't make sense to try to re-execute
the storage on not updated (reset) device tree as we do. It would lead to
invalid results (not enough space on the unselected disks which are actually
used for execute/partitioning).

Could resetting the storage/devicetree also in this special case help? It would
not work because no selected disk in GUI just results in setting storage's
exclusive_disks to empty list (with ignored_disks being kept empty list) which
actually does not hide any disks in storage reset (leading to the invalid result
described above).

So let's just leave the spoke while ensuring it is in incomplete state (by
setting the checker error to "No disks selected").
This would make debugging hangs and races (esp. of automated installs) easier.
My only concern is that it can make some races more or less accessible. But it is
not necessarily a bad thing - let's shake it a bit to see what happens.
@rvykydal rvykydal added the f27 label Oct 11, 2017
Copy link
Contributor

@poncovka poncovka left a 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.

@rvykydal rvykydal merged commit 8e80e8a into rhinstaller:f27-devel Oct 12, 2017
@rvykydal rvykydal deleted the f27-devel-fix-leaving-storage-spoke-with-no-disk branch October 12, 2017 09:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 participants