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

RHEL 9: Filesystem customizations for edge-raw-image #255

Merged
merged 3 commits into from
Dec 13, 2023

Conversation

say-paul
Copy link
Member

This PR enables File system customization for edge-raw-image.

@say-paul say-paul marked this pull request as draft November 13, 2023 12:52
@say-paul
Copy link
Member Author

say-paul commented Nov 13, 2023

having the following error:

Nov 13 18:03:33 saypaul-thinkpadx1carbongen9.pnq.csb osbuild-worker[1450]: time="2023-11-13T18:03:33+05:30" level=info msg="    Failed to open file \"/sys/fs/selinux/checkreqprot\": Read-only file system" jobId=3230a5f5-ee82-416e-9be3-11e7089cc948
Nov 13 18:03:33 saypaul-thinkpadx1carbongen9.pnq.csb osbuild-worker[1450]: time="2023-11-13T18:03:33+05:30" level=info msg="    LVM2: using vg name '25287c67-6499-43cd-a25f-a80f90f36cb0'" jobId=3230a5f5-ee82-416e-9be3-11e7089cc948
Nov 13 18:03:33 saypaul-thinkpadx1carbongen9.pnq.csb osbuild-worker[1450]: time="2023-11-13T18:03:33+05:30" level=info msg="      Physical volume \"/dev/mapper/osbuild-luks-46d73afa-d0b3-4c68-860c-ca1c52f87211\" successfully created." jobId=3230a5f5-ee82-416e-9be3-11e7089cc948
Nov 13 18:03:33 saypaul-thinkpadx1carbongen9.pnq.csb osbuild-worker[1450]: time="2023-11-13T18:03:33+05:30" level=info msg="      Creating devices file /etc/lvm/devices/system.devices" jobId=3230a5f5-ee82-416e-9be3-11e7089cc948
Nov 13 18:03:33 saypaul-thinkpadx1carbongen9.pnq.csb osbuild-worker[1450]: time="2023-11-13T18:03:33+05:30" level=info msg="      Volume group \"25287c67-6499-43cd-a25f-a80f90f36cb0\" successfully created" jobId=3230a5f5-ee82-416e-9be3-11e7089cc948
Nov 13 18:03:33 saypaul-thinkpadx1carbongen9.pnq.csb osbuild-worker[1450]: time="2023-11-13T18:03:33+05:30" level=info msg="      WARNING: Logical volume 25287c67-6499-43cd-a25f-a80f90f36cb0/rootlv not zeroed." jobId=3230a5f5-ee82-416e-9be3-11e7089cc948
Nov 13 18:03:33 saypaul-thinkpadx1carbongen9.pnq.csb osbuild-worker[1450]: time="2023-11-13T18:03:33+05:30" level=info msg="      Logical volume \"rootlv\" created." jobId=3230a5f5-ee82-416e-9be3-11e7089cc948
Nov 13 18:03:33 saypaul-thinkpadx1carbongen9.pnq.csb osbuild-worker[1450]: time="2023-11-13T18:03:33+05:30" level=info msg="      Volume group \"25287c67-6499-43cd-a25f-a80f90f36cb0\" has insufficient free space (252 extents): 256 required." jobId=3230a5f5-ee82-416e-9be3-11e7089cc948
Nov 13 18:03:33 saypaul-thinkpadx1carbongen9.pnq.csb osbuild-worker[1450]: time="2023-11-13T18:03:33+05:30" level=info msg="    Traceback (most recent call last):" jobId=3230a5f5-ee82-416e-9be3-11e7089cc948
Nov 13 18:03:33 saypaul-thinkpadx1carbongen9.pnq.csb osbuild-worker[1450]: time="2023-11-13T18:03:33+05:30" level=info msg="      File \"/run/osbuild/bin/org.osbuild.lvm2.create\", line 110, in <module>" jobId=3230a5f5-ee82-416e-9be3-11e7089cc948
Nov 13 18:03:33 saypaul-thinkpadx1carbongen9.pnq.csb osbuild-worker[1450]: time="2023-11-13T18:03:33+05:30" level=info msg="        ret = main(args[\"devices\"], args[\"options\"])" jobId=3230a5f5-ee82-416e-9be3-11e7089cc948
Nov 13 18:03:33 saypaul-thinkpadx1carbongen9.pnq.csb osbuild-worker[1450]: time="2023-11-13T18:03:33+05:30" level=info msg="      File \"/run/osbuild/bin/org.osbuild.lvm2.create\", line 105, in main" jobId=3230a5f5-ee82-416e-9be3-11e7089cc948
Nov 13 18:03:33 saypaul-thinkpadx1carbongen9.pnq.csb osbuild-worker[1450]: time="2023-11-13T18:03:33+05:30" level=info msg="        subprocess.run(cmd, encoding='utf8', check=True)" jobId=3230a5f5-ee82-416e-9be3-11e7089cc948
Nov 13 18:03:33 saypaul-thinkpadx1carbongen9.pnq.csb osbuild-worker[1450]: time="2023-11-13T18:03:33+05:30" level=info msg="      File \"/usr/lib64/python3.9/subprocess.py\", line 528, in run" jobId=3230a5f5-ee82-416e-9be3-11e7089cc948
Nov 13 18:03:33 saypaul-thinkpadx1carbongen9.pnq.csb osbuild-worker[1450]: time="2023-11-13T18:03:33+05:30" level=info msg="        raise CalledProcessError(retcode, process.args," jobId=3230a5f5-ee82-416e-9be3-11e7089cc948
Nov 13 18:03:33 saypaul-thinkpadx1carbongen9.pnq.csb osbuild-worker[1450]: time="2023-11-13T18:03:33+05:30" level=info msg="    subprocess.CalledProcessError: Command '['lvcreate', '-an', '--size', '1073741824B', '-n', 'foo_barlv', '25287c67-6499-43cd-a25f-a80f90f36cb0']' returned non-zero exit status 5." jobId=3230a5f5-ee82-416e-9be3-11e7089cc948

with blueprint:

name = "rhel93-fs-image"
description = "rhel93-fs-image"
version = "0.0.0"
packages = []
modules = []
groups = []
distro = "rhel-93"

[customizations]

[[customizations.filesystem]]
mountpoint = "/foo"
size = 256
[customizations.ignition]
[customizations.ignition.firstboot]
url = "http://192.168.122.1:8001/config.ign"

@say-paul say-paul force-pushed the filesystem_customization branch 2 times, most recently from 00b7f2c to 34a8fa8 Compare November 27, 2023 10:37
@say-paul
Copy link
Member Author

blueprint for customization:

~/composed_images $ cat ~/blueprints/rhel93-multiple-v2-fs-image.toml 
name = "rhel93-multiple-v2-fs-image"
description = "rhel93-fs-multiple-v2-image"
distro = "rhel-93"

[[customizations.filesystem]]
mountpoint = "/foo/bar"
size=2147483648

[[customizations.filesystem]]
mountpoint = "/foo"
size=8589934592


[[customizations.filesystem]]
mountpoint = "/var/myfiles"
size= "1 GiB"

[customizations.ignition.firstboot]
url = "http://192.168.122.1:8001/config.ign"

~/composed_images $ composer-cli blueprints show rhel93-multiple-v2-fs-image 
name = "rhel93-multiple-v2-fs-image"
description = "rhel93-fs-multiple-v2-image"
version = "0.0.0"
packages = []
modules = []
groups = []
distro = "rhel-93"

[customizations]

[[customizations.filesystem]]
mountpoint = "/foo/bar"
size = 2147483648

[[customizations.filesystem]]
mountpoint = "/foo"
size = 8589934592

[[customizations.filesystem]]
mountpoint = "/var/myfiles"
size = 1073741824
[customizations.ignition]
[customizations.ignition.firstboot]
url = "http://192.168.122.1:8001/config.ign"


@say-paul
Copy link
Member Author

composed image
image

@achilleas-k
Copy link
Member

achilleas-k commented Nov 29, 2023

I found the issue. It's a tricky detail with the way the partition table is described internally. Volume group partitions are sizeable containers, they need to have a size defined. But it seems we don't do this in our static partition tables, so the volume group's partition starts off as 0 bytes and is then grown to fill the space of the required total image size. This worked fine so far, but once the logical volume sizes add up to more than the image size, we run out of space.

The proper solution here is to have logic which resizes the volume group partition to fit the logical volumes it contains and also have it calculate the size of those LVs when needed. It would basically be the same logic we have for the partition table as a whole: the vg has a "desired size", if the sum of lv sizes inside it is bigger than that desired size we grow it, if it's not then it's set to that size.

I'll get a fix (and some tests) done asap.

@say-paul say-paul force-pushed the filesystem_customization branch from 34a8fa8 to dc3549c Compare November 30, 2023 11:10
@say-paul
Copy link
Member Author

say-paul commented Nov 30, 2023

Interesting details, can we pre-calculate the space required and create the VG accordingly, and then grow rootlv to fit the remaining space in image.disk_space.

@say-paul
Copy link
Member Author

@achilleas-k @thozza So the the PR will be waiting for another PR, any feedback on policy and how its applied?

@achilleas-k
Copy link
Member

Interesting details, can we pre-calculate the space required and create the VG accordingly, and then grow rootlv to fit the remaining space in image.disk_space.

yeah that's the plan. I'm working on that today.

@achilleas-k
Copy link
Member

Fix for the filesystem size calculation is here #293

@say-paul say-paul force-pushed the filesystem_customization branch from dc3549c to a12698b Compare December 1, 2023 09:55
@say-paul say-paul marked this pull request as ready for review December 1, 2023 09:56
@say-paul say-paul force-pushed the filesystem_customization branch from a12698b to 2733adf Compare December 1, 2023 11:40
internal/pathpolicy/path_policy.go Outdated Show resolved Hide resolved
@achilleas-k achilleas-k changed the title Filesystem customization RHEL 9: Filesystem customizations for edge-raw-image Dec 1, 2023
@say-paul say-paul force-pushed the filesystem_customization branch from 2733adf to d6a28df Compare December 4, 2023 07:32
@say-paul say-paul requested a review from achilleas-k December 4, 2023 07:44
@say-paul say-paul force-pushed the filesystem_customization branch from 1814442 to e325e46 Compare December 4, 2023 07:53
internal/pathpolicy/path_policy.go Outdated Show resolved Hide resolved
@say-paul say-paul force-pushed the filesystem_customization branch from e325e46 to 53a6d61 Compare December 4, 2023 11:35
@say-paul say-paul requested a review from achilleas-k December 4, 2023 12:44
Copy link
Member

@thozza thozza left a comment

Choose a reason for hiding this comment

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

Thanks for your work. I added a few comments inline.

On a general note, I'm not a big fan of merging the policies in the way you implemented it. I admit that this is probably a bit of a personal preference, but I feel like the merging makes the code more complex. In addition, the destination of the merge function is modified in-place and can override parts of the source policy (which is not needed AFAICT and it is also not explicitly documented and not covered by the unit test).

My preference would be to not touch the default path policy and how it is checked. Then in the checkOptions() function, you could simply do something like this after the default policy check:

...
err := blueprint.CheckMountpointsPolicy(mountpoints, pathpolicy.MountpointPolicies)
if err != nil {
	return warnings, err
}

if t.rpmOstree {
	err := blueprint.CheckMountpointsPolicy(mountpoints, pathpolicy.OstreeMountpointPolicies)
	if err != nil {
		return warnings, err
	}
}
...

This way, the ostree mountpoint policy would be really just an add-on to the default polisy and very few new code and logic would need to be added.

test/configs/filesystem-customizations.json Outdated Show resolved Hide resolved
internal/pathpolicy/policies.go Outdated Show resolved Hide resolved
@achilleas-k
Copy link
Member

Thanks for your work. I added a few comments inline.

On a general note, I'm not a big fan of merging the policies in the way you implemented it. I admit that this is probably a bit of a personal preference, but I feel like the merging makes the code more complex. In addition, the destination of the merge function is modified in-place and can override parts of the source policy (which is not needed AFAICT and it is also not explicitly documented and not covered by the unit test).

My preference would be to not touch the default path policy and how it is checked. Then in the checkOptions() function, you could simply do something like this after the default policy check:

...
err := blueprint.CheckMountpointsPolicy(mountpoints, pathpolicy.MountpointPolicies)
if err != nil {
	return warnings, err
}

if t.rpmOstree {
	err := blueprint.CheckMountpointsPolicy(mountpoints, pathpolicy.OstreeMountpointPolicies)
	if err != nil {
		return warnings, err
	}
}
...

This way, the ostree mountpoint policy would be really just an add-on to the default polisy and very few new code and logic would need to be added.

I agree with all of this. Much simpler and avoids any implicit behaviour when merging. Let's do it this way.

@say-paul say-paul force-pushed the filesystem_customization branch from 53a6d61 to aa43332 Compare December 5, 2023 12:24
test/config-map.json Outdated Show resolved Hide resolved
@say-paul say-paul force-pushed the filesystem_customization branch from e96fb7f to 8e5c411 Compare December 6, 2023 06:46
@say-paul
Copy link
Member Author

say-paul commented Dec 6, 2023

If your team does not feel comfortable with enabling the FS customizations for that image type, then please at least manually boot-test the image.

I am up for enabling it for edge-ami too , but I would defer to the teams decision on this which I will update shortly.

@say-paul say-paul force-pushed the filesystem_customization branch from 8e5c411 to 921e4f8 Compare December 6, 2023 06:54
@say-paul
Copy link
Member Author

say-paul commented Dec 6, 2023

If your team does not feel comfortable with enabling the FS customizations for that image type, then please at least manually boot-test the image.

I am up for enabling it for edge-ami too , but I would defer to the teams decision on this which I will update shortly.

Looking into the broader epic that I am working,we need support for :
simplified-installer, edge-raw-image, edge-ami, edge-vsphere, so it makes sense to enable it for all .

@say-paul say-paul force-pushed the filesystem_customization branch 5 times, most recently from f2cf7c4 to a6c7031 Compare December 13, 2023 14:56
Ostree specific filesystem policy to prevent users form
accidentally  creating custom filesystems that can ovewrite the
systems filesystem.

Signed-off-by: Sayan Paul <[email protected]>
Filesystem customizations is enabled for edge-raw-image,
edge-ami,edge-vsphere,simplified-installer
relevent testing config is added to run in CI

Signed-off-by: Sayan Paul <[email protected]>
rhel only supports uefi, thus enforcing it.

Signed-off-by: Sayan Paul <[email protected]>
@say-paul say-paul force-pushed the filesystem_customization branch from a6c7031 to da406f8 Compare December 13, 2023 17:07
@say-paul
Copy link
Member Author

rebased and commit message updated

@say-paul say-paul requested a review from thozza December 13, 2023 17:09
Copy link
Member

@achilleas-k achilleas-k left a comment

Choose a reason for hiding this comment

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

LGTM. A couple of comments for follow-up stuff.

test/scripts/boot-image Show resolved Hide resolved
test/config-map.json Show resolved Hide resolved
@achilleas-k
Copy link
Member

Created new issues from my comments for follow-up.

@achilleas-k achilleas-k added this pull request to the merge queue Dec 13, 2023
Merged via the queue into osbuild:main with commit 15e9d28 Dec 13, 2023
8 checks passed
thozza added a commit to thozza/osbuild-images that referenced this pull request Dec 19, 2023
Extend the ostree filesystem customizations test case according to
osbuild#255 (comment)

Signed-off-by: Tomáš Hozza <[email protected]>
thozza added a commit to thozza/osbuild-images that referenced this pull request Dec 19, 2023
Extend the ostree filesystem customizations test case according to
osbuild#255 (comment)

Signed-off-by: Tomáš Hozza <[email protected]>
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.

4 participants