Description of problem:
During the installation of RHV-H from ISO, when selecting to customize the partition table, 'LVM' is the default. If you continue with LVM, the installation will fail in post-install of the node. LVM Thin Provisioning is required. At a minimum, LVM thin provisioning should be the default. Ideally non-thin should not be an option if it will cause installation failure.
Version-Release number of selected component (if applicable):
RHV-H 4 GA
Steps to Reproduce:
1. Boot to RHV-H ISO
2. Select to install RHV-H
3. Select Language and click continue
4. Select Installation Destination, click 'I will configure partitioning', and click Done
New mount points will use the following partitioning scheme: LVM
When clicking 'create automatically' and then proceeding with this install, the install will fail at post config due to LVM.
'LVM Thin Provisioning' should be the default partitioning scheme so it does not cause an install to fail when automatically generating the partition table
A good point.
We need to see if we can override the default partitioning scheme by using our own install class.
Regardless of this bug, we are working on enhancing the error messages to give more meaningful feedback to users, if they choose the wrong layout.
Like the other bug (enhanced feedback), this does not appear to be possible with an installclass.
This is directly set in pyanaconda.constants, and it doesn't seem to be possible with a product.img
There's always the option of maintaining some kind of forked anaconda to hold updates.img layered on top of stock, but this is an option I'd rather not pursue.
Is this possible with defaultFS? It doesn't look like it.
If not, I'll open some an RFE
We will not be able to fix this in anaconda for 4.1, but we are looking at a long term solution for this issue.
For 4.1 we will improve the post-installation error message to provide a more meaningful error message.
*** Bug 1380646 has been marked as a duplicate of this bug. ***
(In reply to Ryan Barry from comment #2)
> Like the other bug (enhanced feedback), this does not appear to be possible
> with an installclass.
> This is directly set in pyanaconda.constants, and it doesn't seem to be
> possible with a product.img
> There's always the option of maintaining some kind of forked anaconda to
> hold updates.img layered on top of stock, but this is an option I'd rather
> not pursue.
> Samantha -
> Is this possible with defaultFS? It doesn't look like it.
> If not, I'll open some an RFE
A possible way around this, could be to create an anaconda addon (with a relevant gui spoke) that validates the requirements for the installation before the actual installation takes place. We could ship it in product.img
It will not be selected as a default, but some improvements were done in bug 1412151 to add storage checks in anaconda. Does it cover this one ?
(In reply to Yuval Turgeman from comment #6)
> It will not be selected as a default, but some improvements were done in bug
> 1412151 to add storage checks in anaconda. Does it cover this one ?
Moving the question to Ryan
This definitely looks like it should cover it.
Yuval, can you check?
Sorry, by check, I mean with the latest ISO.
Nevermind -- we'll need to wait for bz#1412151 to ship before this can be verified.
Looks like it bz#1412151 was shipped, i'll check this.
How does this look, Yuval?
Looks good in 7.4 iso, it defaults to lvmthin, and NIST partitioning. Only issue is that the default fs is ext4 for some reason (guessing it's the default in blivet). Looking further at the default rhv.py installclass from anaconda, it uses defaultFSType, while in rhel.py it sets defaultFS = xfs, should we post a patch ?
For my part, I'm not sure that we should switch to xfs mid-release, especially since discard is very valuable with LVM thinpools.
However, I don't have a strong opinion about it, and fstrim.timer probably works nearly as well.
1. Install RHVH-4.2-20171207.1-RHVH-x86_64-dvd1.iso
2. Choose "I will configure partitioning" to enter the MANUAL PARTITIONING page.
3. Check the default partitioning scheme.
4. Check custom partitioning constraints.
1. The default partitioning scheme on the MANUAL PARTITIONING page is "LVM Thin Provisioning"
2. When choosing other partitioning schemes, such as LVM, and clicking "Click here to create them automatically", then an error would be popped up at the bottom of the window saying you have to choose LVM Thin Provisioning.
3. There are also separated error indications for the following configurations:
1) /boot lower than 1GiB
2) no /var
3) /var lower than 10GiB
According to the results, the custom partitioning scheme defaults to "LVM Thin Provisioning", and there are also some important storage constraint checks, so the bug is fixed, change the status to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.