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

Do not update filesystem info for resize in the installer mode #173

Conversation

vojtechtrefny
Copy link
Member

Blivet runs update_size_info automatically in Anaconda so we don't
need to do it again. Also our update_size_info call will always
fail for LVs because they are no longer active when blivet-gui is
running (because anaconda runs teardown_all during populate).

Resolves: rhbz#1826370

Blivet runs update_size_info automatically in Anaconda so we don't
need to do it again. Also our update_size_info call will always
fail for LVs because they are no longer active when blivet-gui is
running (because anaconda runs teardown_all during populate).

Resolves: rhbz#1826370
@AdamWill
Copy link
Contributor

I'm testing this now, but investigating independently I had come to pretty much exactly the same conclusion, and the change is more or less exactly what I was gonna propose too, so LGTM :)

@packit-as-a-service
Copy link

Congratulations! One of the builds has completed. 🍾

You can install the built RPMs by following these steps:

  • sudo yum install -y dnf-plugins-core on RHEL 8
  • sudo dnf install -y dnf-plugins-core on Fedora
  • dnf copr enable packit/storaged-project-blivet-gui-173
  • And now you can install the packages.

Please note that the RPMs should be used only in a testing environment.

@vojtechtrefny
Copy link
Member Author

Jenkins, test this please.

@AdamWill
Copy link
Contributor

Fix confirmed in testing. I'm just wondering if it might be a bit safer to do something like this:

if not self.installer_mode or not blivet_device.min_size:

just in case there's some case we've not thought of where we really do need to update the size info at this point in the installer...but it's only an idea.

@AdamWill
Copy link
Contributor

eh, seems like most filesystems have default min sizes, so that's probably not going to do much.

@vojtechtrefny
Copy link
Member Author

Fix confirmed in testing. I'm just wondering if it might be a bit safer to do something like this:

if not self.installer_mode or not blivet_device.min_size:

just in case there's some case we've not thought of where we really do need to update the size info at this point in the installer...but it's only an idea.

Blivet does the size info update in FS class constructor so we really shouldn't need to run it again. Anaconda (Custom partitioning) also doesn't do that. Worst case scenario: we'll mark the device as not resizable which is what's happening right now. Not ideal but not worse :-)

@vojtechtrefny vojtechtrefny merged commit 781538d into storaged-project:master Apr 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants