[ovirt-users] Re: ovrt node ng 4.4 different fs layout and error if changed

2020-05-22 Thread jan.kleefeld.1996
Same here. I let the installer automatically set the partition
configuration. I changed nothing. Same error as you have.

On ovirt-node-ng-installer-4.4.0-2020052110.el8

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CWZ4DGWFZE6ILI47ERUCZEFZ5YLR5ABJ/


[ovirt-users] Re: ovrt node ng 4.4 different fs layout and error if changed

2020-04-29 Thread Sandro Bonazzola
Il giorno dom 19 apr 2020 alle ore 12:03 Gianluca Cecchi <
gianluca.cec...@gmail.com> ha scritto:

> Hello,
> In CentOS 7 default filesystem in anaconda was xfs, but in ovirt node ng
> 4.3.9 (based on CentOS 7) the default layout was set to ext4.
> In CentOS 8 again the default is xfs and I see that ovirt node ng 4.4
> beta4 (based on CentOS 8.1) has now xfs for all filesystems, excluded /boot
> that is set to ext4.
> In general I have a preference for ext4.
> I notice that while in 4.3.9 I could somehow customize partition layout,
> even if not recommended, in 4.4 I always get error if I don't accept
> automatic partitioning.
> What I sometimes do:
> - select disk and custom layout
> - click done and the storage page appears
> - I click the button to create automatically and I get the automatic
> partitioning layout
> - and here I can change fs type and update settings button and/or change
> size of some filesystems (eg for /var/log if using Gluster)
>
> Even if I only set all filesystems automatically generated by installer to
> ext4, without changing any size, in the final stage of installation I get
> this error and installation aborts:
> "
> There was an error running the kickstart script at line 5.  This is a
> fatal error and installation will be aborted.  The details of this error
> are:
>
> 2020-04-19 10:37:50,451 [INFO] (MainThread) Trying to create a manageable
> base from '/'
> 2020-04-19 10:37:50,811 [ERROR] (MainThread) LVM Thin Provisioning
> partitioning scheme is required.
> For autoinstall via Kickstart with LVM Thin Provisioning check options:
> --thinpool and --grow. Please consult documentation for details
>
> Traceback (most recent call last):
>   File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main
> "__main__", mod_spec)
>   File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code
> exec(code, run_globals)
>   File "/usr/lib/python3.6/site-packages/imgbased/__main__.py", line 53,
> in 
> CliApplication()
>   File "/usr/lib/python3.6/site-packages/imgbased/__init__.py", line 82,
> in CliApplication
> app.hooks.emit("post-arg-parse", args)
>   File "/usr/lib/python3.6/site-packages/imgbased/hooks.py", line 120, in
> emit
> cb(self.context, *args)
>   File "/usr/lib/python3.6/site-packages/imgbased/plugins/core.py", line
> 171, in post_argparse
> layout.initialize(args.source, args.init_nvr)
>   File "/usr/lib/python3.6/site-packages/imgbased/plugins/core.py", line
> 215, in initialize
> self.app.imgbase.init_layout_from(source, init_nvr)
>   File "/usr/lib/python3.6/site-packages/imgbased/imgbase.py", line 293,
> in init_layout_from
> self.init_tags_on(existing_lv)
>   File "/usr/lib/python3.6/site-packages/imgbased/imgbase.py", line 271,
> in init_tags_on
> pool = lv.thinpool()
>   File "/usr/lib/python3.6/site-packages/imgbased/lvm.py", line 305, in
> thinpool
> raise MissingLvmThinPool()
> imgbased.lvm.MissingLvmThinPool
> "
>
> If I change nothing and choose automatic partitioning the installation
> completes.
> Tried different times with same results.
>
> Is it expected? In this case instead of specifying "recommended" it should
> be written sort of "mandatory"...
>

Adding +Nir Levy  and +Chen Shao  for
awareness.



>
> Gianluca
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/F5PD5LSQB5WNZCF2J7TDG3OKQL74WSXW/
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com
*
*
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.
*
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BJ4O4QPRVCXP5LHHBXOCTMAM2KLGSTLK/