I'll copy Michal's answer from another thread:
"Indeed it won’t work for el8 guests. Unfortunately an el7
libguestfs(so any virt- tool) can’t work with el8 filesystems. And
ovirt still uses el7 hosts
That’s going to be a limitation until 4.4

Thanks,
michal"

If you wish to seal el8 guest, you might seal it manually and create a
template from it.
Liran.

On Fri, May 17, 2019 at 7:46 AM Vinícius Ferrão
<fer...@versatushpc.com.br> wrote:
>
> Hello,
>
> I’m trying to seal a RHEL8 template but the operation is failing.
>
> Here’s the relevant information from engine.log:
>
> 2019-05-17 01:30:31,153-03 INFO  
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHostJobsVDSCommand] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-58) 
> [91e1acd6-efc5-411b-8c76-970def4ebbbe] FINISH, GetHostJobsVDSCommand, return: 
> {b80c0bbd-25b8-4007-9b91-376cb0a18e30=HostJobInfo:{id='b80c0bbd-25b8-4007-9b91-376cb0a18e30',
>  type='virt', description='seal_vm', status='failed', progress='null', 
> error='VDSError:{code='GeneralException', message='General Exception: 
> ('Command [\'/usr/bin/virt-sysprep\', \'-a\', 
> u\'/rhev/data-center/mnt/192.168.10.6:_mnt_pool0_ovirt_vm/d19456e4-0051-456e-b33c-57348a78c2e0/images/1ecdfbfc-1c22-452f-9a53-2159701549c8/f9de3eae-f475-451b-b587-f6a1405036e8\']
>  failed with rc=1 out=\'[   0.0] Examining the guest ...\\nvirt-sysprep: 
> warning: mount_options: mount exited with status 32: mount: \\nwrong fs type, 
> bad option, bad superblock on /dev/mapper/rhel_rhel8-root,\\n       missing 
> codepage or helper program, or other error\\n\\n       In some cases useful 
> info is found in syslog - try\\n       dmesg | tail or so. 
> (ignored)\\nvirt-sysprep: warning: mount_options: mount: /boot: mount point 
> is not a \\ndirectory (ignored)\\nvirt-sysprep: warning: mount_options: 
> mount: /boot/efi: mount point is not \\na directory (ignored)\\n[  17.9] 
> Performing "abrt-data" ...\\n\' err="virt-sysprep: error: libguestfs error: 
> glob_expand: glob_expand_stub: you \\nmust call \'mount\' first to mount the 
> root filesystem\\n\\nIf reporting bugs, run virt-sysprep with debugging 
> enabled and include the \\ncomplete output:\\n\\n  virt-sysprep -v -x 
> [...]\\n"',)'}'}}, log id: 1bbb34bf
>
> I’m not shure what’s wrong or missing. The VM image is using UEFI with Secure 
> Boot, so standard UEFI partition is in place.
>
> Ive found something on bugzilla but does not seem to be related:
> https://bugzilla.redhat.com/show_bug.cgi?id=1671895
>
> Thanks,
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WILFBK6SOTKJP25PAS4JODNNOUFW7HUQ/
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WPFWL3U3OORLXYH37EEYQES6RK6L463V/

Reply via email to