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

Add storage checks #468

Merged
merged 21 commits into from Jan 16, 2018
Merged

Add storage checks #468

merged 21 commits into from Jan 16, 2018

Conversation

joseivanlopez
Copy link
Contributor

@yast yast deleted a comment from coveralls Dec 18, 2017
@yast yast deleted a comment from coveralls Dec 18, 2017
@yast yast deleted a comment from coveralls Dec 18, 2017
@yast yast deleted a comment from coveralls Dec 19, 2017
@yast yast deleted a comment from coveralls Dec 19, 2017
@yast yast deleted a comment from coveralls Dec 19, 2017
@joseivanlopez joseivanlopez force-pushed the setup_checker branch 5 times, most recently from 17a5632 to 1d4d9d7 Compare January 10, 2018 15:57
@yast yast deleted a comment from coveralls Jan 10, 2018
@yast yast deleted a comment from coveralls Jan 10, 2018
@yast yast deleted a comment from coveralls Jan 10, 2018
@yast yast deleted a comment from coveralls Jan 10, 2018
@yast yast deleted a comment from coveralls Jan 10, 2018
@yast yast deleted a comment from coveralls Jan 10, 2018
@yast yast deleted a comment from coveralls Jan 10, 2018
@yast yast deleted a comment from coveralls Jan 10, 2018
@yast yast deleted a comment from coveralls Jan 10, 2018
@yast yast deleted a comment from coveralls Jan 10, 2018
@joseivanlopez joseivanlopez force-pushed the setup_checker branch 3 times, most recently from 7defe9b to 170624a Compare January 12, 2018 17:25
@yast yast deleted a comment from coveralls Jan 12, 2018
@yast yast deleted a comment from coveralls Jan 12, 2018
@yast yast deleted a comment from coveralls Jan 12, 2018
@coveralls
Copy link

Coverage Status

Coverage increased (+0.05%) to 96.28% when pulling f149102 on joseivanlopez:setup_checker into 1831961 on yast:master.

@yast yast deleted a comment from coveralls Jan 15, 2018
@yast yast deleted a comment from coveralls Jan 15, 2018
@@ -16,7 +16,7 @@
#

Name: yast2-storage-ng
Version: 4.0.68
Version: 4.0.70
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are you jumping two numbers here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Arfff

@@ -6,6 +14,7 @@ Mon Jan 15 12:51:01 UTC 2018 - ancor@suse.com
alignment types, in addition to the optimal one.
- Added a (temporary) workaround to a possible bug in libstorage-ng
regarding alignment.
- 4.0.69
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was not intended to introduce a version bump, no need to "correct" that


- Added sanity checks for partitioning setup.
- Partitioner: setup issues are shown to the user before continue.
Mandatory product volumes are required according to control file.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I miss the storage-ng fate entry and also mentioning the several bug reports we have about the missing checks.

@@ -69,7 +69,6 @@
it "requires it to be between 1 and 8MiB, despite the alignment" do
expect(grub_part.min).to eq 1.MiB
expect(grub_part.max).to eq 8.MiB
expect(grub_part.align).to eq :keep_size
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's remove also the "despite the alignment" part from the textual description

@@ -79,7 +78,6 @@
it "requires it to be between 256KiB and 8MiB, despite the alignment" do
expect(grub_part.min).to eq 256.KiB
expect(grub_part.max).to eq 8.MiB
expect(grub_part.align).to eq :keep_size
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here for "despite the alignment"

@@ -138,7 +136,6 @@
it "requires it to be between 1MiB and 8MiB, despite the alignment" do
expect(prep_part.min).to eq 1.MiB
expect(prep_part.max).to eq 8.MiB
expect(prep_part.align).to eq :keep_size
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here for "despite the alignment"

@@ -148,7 +145,6 @@
it "requires it to be between 256KiB and 8MiB, despite the alignment" do
expect(prep_part.min).to eq 256.KiB
expect(prep_part.max).to eq 8.MiB
expect(prep_part.align).to eq :keep_size
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here for "despite the alignment"

# BIOS RAIDs. Class MdContainer is also derived from Md, but objects of this
# class are not be considered neither Software nor BIOS RAIDs.
# To properly exclude MdContainer as :raid device, here only Software RAIDs
# are considered to be raid type.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NP: Wouldn't be too much to ask to have this explanation right on top of the types << :raid if software_defined? line instead of the heading of the method?

@@ -105,7 +105,7 @@ def self.to_string_attrs
def volume_match_values
{
mount_point: mount_point,
size: DiskSize.zero,
size: nil,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why don't we want to check the size of the Md devices? Doesn't Md#size return a sensible value just like e.g. Partition#size?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is a Planned::Md and it has not #size.

# Session15694/SHARE_Bootloader_Ihno_PittsPPT_0.09.pdf
#
# @return [Array<Filesystems::Type>]
def self.zipl_filesystems
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be mentioned that the first one is the preferred one (i.e. used by the guided setup)

error_message = _("Current boot disk cannot be used for booting")
error_message = _(
"Looks like the system is going to be installed on a FBA " \
"or LDL device. Booting from such device is not supported"
Copy link
Contributor

@ancorgs ancorgs Jan 15, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing period at the end?

@@ -60,7 +60,7 @@ def device_attributes_list
device_udev_by_path.join(Yast::HTML.Newline),
device_udev_by_id.join(Yast::HTML.Newline),
# TRANSLATORS: acronym for Filesystem Identifier
format(_("FS ID: %s"), "TODO")
format(_("Partition ID: %s"), "TODO")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please update the comment for the translators

@coveralls
Copy link

Coverage Status

Coverage increased (+0.05%) to 96.28% when pulling 6f23a5e on joseivanlopez:setup_checker into 1831961 on yast:master.

@ancorgs
Copy link
Contributor

ancorgs commented Jan 16, 2018

LGTM, let's go for it!

@joseivanlopez joseivanlopez merged commit 52089a7 into yast:master Jan 16, 2018
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

3 participants