[ovirt-users] Re: [ANN] oVirt 4.4.3 Fifth Release Candidate is now available for testing

2020-10-19 Thread Edward Berger
with those packages installed I was able to run the single node
hyperconverged wizard,
but it fails during deploy "Hosted Engine Deployment" with
[ INFO ] TASK [ovirt.ovirt.engine_setup : Update setup packages]
[ INFO ] skipping: [localhost]
[ INFO ] TASK [ovirt.ovirt.engine_setup : Update all packages]
[ ERROR ] fatal: [localhost -> testvirt.bil.psc.edu]: FAILED! =>
{"changed": false, "failures": [], "msg": "Depsolve Error occured: \n
Problem: cannot install the best update candidate for package
ovirt-engine-metrics-1.4.1.1-1.el8.noarch\n - nothing provides
rhel-system-roles >= 1.0-19 needed by
ovirt-engine-metrics-1.4.2-1.el8.noarch", "rc": 1, "results": []}
[ INFO ] TASK [ovirt.ovirt.engine_setup : Clean temporary files]
[ INFO ] changed: [localhost -> testvirt.bil.psc.edu]

I can 'virsh console HostedEngineLocal' and yum update there says
[root@testvirt ~]# yum update
Last metadata expiration check: 0:03:58 ago on Mon 19 Oct 2020 12:52:54 PM
EDT.
Error:
 Problem: cannot install the best update candidate for package
ovirt-engine-metrics-1.4.1.1-1.el8.noarch
  - nothing provides rhel-system-roles >= 1.0-19 needed by
ovirt-engine-metrics-1.4.2-1.el8.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to
use not only best candidate packages)





On Mon, Oct 19, 2020 at 12:25 PM Edward Berger  wrote:

> I'm installing 4.4.3-pre on CentOS8.2 and it seems the glusterfs-server
> and gluster-ansible-roles RPMs aren't installed,
> with the ovirt-cockpit which pulls other dependencies.
>
> This caused the cockpit hyperconverged installer to fail. It mentions the
> roles rpm but not the glusterfs
> with the role installed, failure comes up when it tries to setup the
> firewall for non-existing glusterfs-server.
>
> It is similarly missing on 4.4.2-release.
> (the quick installation instructions are missing this or its a bug)
>
>
> On Mon, Oct 19, 2020 at 4:31 AM Lev Veyde  wrote:
>
>> oVirt 4.4.3 Fifth Release Candidate is now available for testing
>>
>> The oVirt Project is pleased to announce the availability of oVirt 4.4.3
>> Fifth Release Candidate for testing, as of October 16th, 2020.
>>
>> This update is the third in a series of stabilization updates to the 4.4
>> series.
>> How to prevent hosts entering emergency mode after upgrade from oVirt
>> 4.4.1
>>
>> Note: Upgrading from 4.4.2 GA should not require re-doing these steps, if
>> already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only
>> required to be done once.
>>
>> Due to Bug 1837864  -
>> Host enter emergency mode after upgrading to latest build
>>
>> If you have your root file system on a multipath device on your hosts you
>> should be aware that after upgrading from 4.4.1 to 4.4.3 you may get your
>> host entering emergency mode.
>>
>> In order to prevent this be sure to upgrade oVirt Engine first, then on
>> your hosts:
>>
>>1.
>>
>>Remove the current lvm filter while still on 4.4.1, or in emergency
>>mode (if rebooted).
>>2.
>>
>>Reboot.
>>3.
>>
>>Upgrade to 4.4.3 (redeploy in case of already being on 4.4.3).
>>4.
>>
>>Run vdsm-tool config-lvm-filter to confirm there is a new filter in
>>place.
>>5.
>>
>>Only if not using oVirt Node:
>>- run "dracut --force --add multipath” to rebuild initramfs with the
>>correct filter configuration
>>6.
>>
>>Reboot.
>>
>> Documentation
>>
>>-
>>
>>If you want to try oVirt as quickly as possible, follow the
>>instructions on the Download  page.
>>-
>>
>>For complete installation, administration, and usage instructions,
>>see the oVirt Documentation .
>>-
>>
>>For upgrading from a previous version, see the oVirt Upgrade Guide
>>.
>>-
>>
>>For a general overview of oVirt, see About oVirt
>>.
>>
>> Important notes before you try it
>>
>> Please note this is a pre-release build.
>>
>> The oVirt Project makes no guarantees as to its suitability or usefulness.
>>
>> This pre-release must not be used in production.
>> Installation instructions
>>
>> For installation instructions and additional information please refer to:
>>
>> https://ovirt.org/documentation/
>>
>> This release is available now on x86_64 architecture for:
>>
>> * Red Hat Enterprise Linux 8.2 or newer
>>
>> * CentOS Linux (or similar) 8.2 or newer
>>
>> This release supports Hypervisor Hosts on x86_64 and ppc64le
>> architectures for:
>>
>> * Red Hat Enterprise Linux 8.2 or newer
>>
>> * CentOS Linux (or similar) 8.2 or newer
>>
>> * oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)
>>
>> See the release notes [1] for installation instructions and a list of new
>> features and bugs fixed.
>>
>> Notes:
>>
>> - oVirt Appliance is already available for CentOS Linux 8
>>
>> - 

[ovirt-users] Re: [ANN] oVirt 4.4.3 Fifth Release Candidate is now available for testing

2020-10-19 Thread Edward Berger
 I'm installing 4.4.3-pre on CentOS8.2 and it seems the glusterfs-server
and gluster-ansible-roles RPMs aren't installed,
with the ovirt-cockpit which pulls other dependencies.

This caused the cockpit hyperconverged installer to fail. It mentions the
roles rpm but not the glusterfs
with the role installed, failure comes up when it tries to setup the
firewall for non-existing glusterfs-server.

It is similarly missing on 4.4.2-release.
(the quick installation instructions are missing this or its a bug)


On Mon, Oct 19, 2020 at 4:31 AM Lev Veyde  wrote:

> oVirt 4.4.3 Fifth Release Candidate is now available for testing
>
> The oVirt Project is pleased to announce the availability of oVirt 4.4.3
> Fifth Release Candidate for testing, as of October 16th, 2020.
>
> This update is the third in a series of stabilization updates to the 4.4
> series.
> How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1
>
> Note: Upgrading from 4.4.2 GA should not require re-doing these steps, if
> already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only
> required to be done once.
>
> Due to Bug 1837864  -
> Host enter emergency mode after upgrading to latest build
>
> If you have your root file system on a multipath device on your hosts you
> should be aware that after upgrading from 4.4.1 to 4.4.3 you may get your
> host entering emergency mode.
>
> In order to prevent this be sure to upgrade oVirt Engine first, then on
> your hosts:
>
>1.
>
>Remove the current lvm filter while still on 4.4.1, or in emergency
>mode (if rebooted).
>2.
>
>Reboot.
>3.
>
>Upgrade to 4.4.3 (redeploy in case of already being on 4.4.3).
>4.
>
>Run vdsm-tool config-lvm-filter to confirm there is a new filter in
>place.
>5.
>
>Only if not using oVirt Node:
>- run "dracut --force --add multipath” to rebuild initramfs with the
>correct filter configuration
>6.
>
>Reboot.
>
> Documentation
>
>-
>
>If you want to try oVirt as quickly as possible, follow the
>instructions on the Download  page.
>-
>
>For complete installation, administration, and usage instructions, see
>the oVirt Documentation .
>-
>
>For upgrading from a previous version, see the oVirt Upgrade Guide
>.
>-
>
>For a general overview of oVirt, see About oVirt
>.
>
> Important notes before you try it
>
> Please note this is a pre-release build.
>
> The oVirt Project makes no guarantees as to its suitability or usefulness.
>
> This pre-release must not be used in production.
> Installation instructions
>
> For installation instructions and additional information please refer to:
>
> https://ovirt.org/documentation/
>
> This release is available now on x86_64 architecture for:
>
> * Red Hat Enterprise Linux 8.2 or newer
>
> * CentOS Linux (or similar) 8.2 or newer
>
> This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
> for:
>
> * Red Hat Enterprise Linux 8.2 or newer
>
> * CentOS Linux (or similar) 8.2 or newer
>
> * oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)
>
> See the release notes [1] for installation instructions and a list of new
> features and bugs fixed.
>
> Notes:
>
> - oVirt Appliance is already available for CentOS Linux 8
>
> - oVirt Node NG is already available for CentOS Linux 8
>
> Additional Resources:
>
> * Read more about the oVirt 4.4.3 release highlights:
> http://www.ovirt.org/release/4.4.3/
>
> * Get more oVirt project updates on Twitter: https://twitter.com/ovirt
>
> * Check out the latest project news on the oVirt blog:
> http://www.ovirt.org/blog/
>
>
> [1] http://www.ovirt.org/release/4.4.3/
>
> [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/
>
> --
>
> Lev Veyde
>
> Senior Software Engineer, RHCE | RHCVA | MCITP
>
> Red Hat Israel
>
> 
>
> l...@redhat.com | lve...@redhat.com
> 
> TRIED. TESTED. TRUSTED. 
> ___
> 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/3CRWW4EMTGHRVGGJM6EY4DUEEM6QJKBI/
>
___
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: 

[ovirt-users] Re: VM has snapshot with disk in illegal status

2020-10-19 Thread Massimo Mad
Hi,
It's very strange because in the engine UI i have only one disk in illegal
status.
But i have a problem with another VM that have all the disk OK the storage
migration begins, takes the snap shot then fails and the snapshot is
deleted.
the size of the vm with the disk in illega is 200Gb the id of the disk is
a0f9a434-7837-4ec6-8017-c9698ed5cd01
Regards
Massimo


Il giorno lun 19 ott 2020 alle ore 15:47 Shani Leviim 
ha scritto:

> Hi Massimo,
> As shown on the output, you currently have 2 illeagal images:
>
>image:55893adf-1e56-4346-8070-4b3e660dd44d
>
>  - ea57d10b-13d5-4696-bedc-13a92b88f32d
>status: ILLEGAL, voltype: LEAF, format: COW, legality:
> *ILLEGAL*, type: SPARSE, capacity: 107374182400, truesize: 1744830464
>
>
>image:825765ba-b132-4b36-8cb9-8ecd2c7b597a
>
>  - 5c534181-fbd6-4912-afdc-4ac812e0e9fe
>status: ILLEGAL, voltype: LEAF, format: COW, legality:
> *ILLEGAL*, type: SPARSE, capacity: 85899345920, truesize: 1879048192
>
> Can you try removing them from the engine UI?
>
>
> *Regards,*
>
> *Shani Leviim*
>
>
> On Mon, Oct 19, 2020 at 4:36 PM Massimo Mad  wrote:
>
>> Hi Shani
>> I run the command on the host owner of the SPM it's correct ?
>> This is the output:
>> [root@ovirthpr01 ~]# vdsm-tool dump-volume-chains
>> eb483eb3-a9ce-4867-9ce8-96a0ca171042
>>
>> Images volume chains (base volume first)
>>
>>image:ff44dc13-de50-4891-84ce-9fb3e3fe1c88
>>
>>  - c45ee9cd-17e3-4cec-b7fb-74af27e792a8
>>status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
>> type: PREALLOCATED, capacity: 134217728, truesize: 134217728
>>
>>
>>image:a0f9a434-7837-4ec6-8017-c9698ed5cd01
>>
>>  - 64ac336f-25d8-43d0-aeb8-7fb77bf6ef97
>>status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
>> type: PREALLOCATED, capacity: 214748364800, truesize: 214748364800
>>
>>
>>image:4da04f46-2fea-436f-9648-772c24a849c3
>>
>>  - 77ddb7b8-b10f-4d7e-82df-36e077a9eb25
>>status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
>> type: PREALLOCATED, capacity: 134217728, truesize: 134217728
>>
>>
>>image:55893adf-1e56-4346-8070-4b3e660dd44d
>>
>>  - ea57d10b-13d5-4696-bedc-13a92b88f32d
>>status: ILLEGAL, voltype: LEAF, format: COW, legality:
>> ILLEGAL, type: SPARSE, capacity: 107374182400, truesize: 1744830464
>>
>>
>>image:825765ba-b132-4b36-8cb9-8ecd2c7b597a
>>
>>  - 5c534181-fbd6-4912-afdc-4ac812e0e9fe
>>status: ILLEGAL, voltype: LEAF, format: COW, legality:
>> ILLEGAL, type: SPARSE, capacity: 85899345920, truesize: 1879048192
>>
>>
>>image:0264f52e-fa59-4523-81e4-47564193665e
>>
>>  - dfb3d366-f2d3-49ee-8ca3-3b44e24a0111
>>status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
>> type: PREALLOCATED, capacity: 536870912000, truesize: 536870912000
>> And after what is the next step?
>> Regards
>> Massimo
>>
>>
>> Il giorno lun 19 ott 2020 alle ore 13:51 Shani Leviim 
>> ha scritto:
>>
>>> Hi Massimo,
>>> In order to locate the illegal image, you can run this command on the
>>> host:
>>> vdsm-tool dump-volume-chains 
>>>
>>> It's also recommended to verify that the engine and vdsm are synced
>>> about that image, once you've find it, by running this command on the
>>> engine:
>>> SELECT *
>>>  FROM images_storage_domain_view images_storage_domain_view
>>>  WHERE image_group_id = ;
>>>
>>> Than, you can try removing it from the engine.
>>> (and if it doesn't work - you can delete it from the DB)
>>>
>>>
>>> *Regards,*
>>>
>>> *Shani Leviim*
>>>
>>>
>>> On Mon, Oct 19, 2020 at 11:15 AM Massimo Mad 
>>> wrote:
>>>
 Hi,
 I try to delete a snapshot that i have created in the past, now in the
 events i have the following error:
 Failed to delete snapshot
 And the VM now has the exclamation point with the following message:
 VM has snapshot with disk in illegal status
 How i can fix this problem ?
 Regards
 Massimo
 ___
 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/VZJ62WAKAVWWORPPEIKMAT4KXOB6AU2D/

>>>
___
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/KLR3FPLMEYYAVVF7ZQ4KU2W7HHZIOGCN/


[ovirt-users] Re: 20+ Fresh Installs Failing in 20+ days [newbie & frustrated]

2020-10-19 Thread info
I used Cockpit web interface to do the install and I crashed again. I think it 
did not do the final part of the install. There are no other files such as 
"engine-side logs"

It keep disconnecting from the Cockpit

This is my problem for the last few weeks, it will not complete the install and 
I have no idea why.

Yours Sincerely,
 
Henni 


-Original Message-
From: Yedidyah Bar David  
Sent: Monday, 19 October 2020 14:58
To: i...@worldhostess.com
Cc: Edward Berger ; users 
Subject: [ovirt-users] Re: 20+ Fresh Installs Failing in 20+ days [newbie & 
frustrated]

Hi,

On Fri, Oct 16, 2020 at 4:44 PM  wrote:
>
> Another zip file from fresh Centos & Ovirt install
>
> The following directories and files are included 1. openvswitch 2. 
> ovirt-hosted-engine-ha 3. ovirt-hosted-engine-setup 4. ovirt-imageio 
> 5. vdsm 6. firewalld
>
> https://drive.google.com/file/d/1QXj2eiNYseJvTVwmlDp8qwIWg64t45Sc/view
> ?usp=sharing

Thanks.

It's still the same problem ("Check engine VM health" failed) and the zip still 
does not include engine-side logs (either from the engine vm itself or from 
subdirs of /var/log/ovirt-hosted-engine-setup). Please check/share these.

Also, the files' timestamps are not kept, so 'ls -ltr' does not show them in 
the correct order. Is there a problem with simply using 'tar' as I suggested?

Thanks and best regards,
--
Didi
___
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/OSV5JYVZTMAJJ7L4O4XHAIBWDL5VKZNP/
___
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/BVYSMGD7KXPODVRCM7YDVLFJFMLABPXH/


[ovirt-users] Re: VM has snapshot with disk in illegal status

2020-10-19 Thread Shani Leviim
Hi Massimo,
As shown on the output, you currently have 2 illeagal images:

   image:55893adf-1e56-4346-8070-4b3e660dd44d

 - ea57d10b-13d5-4696-bedc-13a92b88f32d
   status: ILLEGAL, voltype: LEAF, format: COW, legality:
*ILLEGAL*, type: SPARSE, capacity: 107374182400, truesize: 1744830464


   image:825765ba-b132-4b36-8cb9-8ecd2c7b597a

 - 5c534181-fbd6-4912-afdc-4ac812e0e9fe
   status: ILLEGAL, voltype: LEAF, format: COW, legality:
*ILLEGAL*, type: SPARSE, capacity: 85899345920, truesize: 1879048192

Can you try removing them from the engine UI?


*Regards,*

*Shani Leviim*


On Mon, Oct 19, 2020 at 4:36 PM Massimo Mad  wrote:

> Hi Shani
> I run the command on the host owner of the SPM it's correct ?
> This is the output:
> [root@ovirthpr01 ~]# vdsm-tool dump-volume-chains
> eb483eb3-a9ce-4867-9ce8-96a0ca171042
>
> Images volume chains (base volume first)
>
>image:ff44dc13-de50-4891-84ce-9fb3e3fe1c88
>
>  - c45ee9cd-17e3-4cec-b7fb-74af27e792a8
>status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
> type: PREALLOCATED, capacity: 134217728, truesize: 134217728
>
>
>image:a0f9a434-7837-4ec6-8017-c9698ed5cd01
>
>  - 64ac336f-25d8-43d0-aeb8-7fb77bf6ef97
>status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
> type: PREALLOCATED, capacity: 214748364800, truesize: 214748364800
>
>
>image:4da04f46-2fea-436f-9648-772c24a849c3
>
>  - 77ddb7b8-b10f-4d7e-82df-36e077a9eb25
>status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
> type: PREALLOCATED, capacity: 134217728, truesize: 134217728
>
>
>image:55893adf-1e56-4346-8070-4b3e660dd44d
>
>  - ea57d10b-13d5-4696-bedc-13a92b88f32d
>status: ILLEGAL, voltype: LEAF, format: COW, legality:
> ILLEGAL, type: SPARSE, capacity: 107374182400, truesize: 1744830464
>
>
>image:825765ba-b132-4b36-8cb9-8ecd2c7b597a
>
>  - 5c534181-fbd6-4912-afdc-4ac812e0e9fe
>status: ILLEGAL, voltype: LEAF, format: COW, legality:
> ILLEGAL, type: SPARSE, capacity: 85899345920, truesize: 1879048192
>
>
>image:0264f52e-fa59-4523-81e4-47564193665e
>
>  - dfb3d366-f2d3-49ee-8ca3-3b44e24a0111
>status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
> type: PREALLOCATED, capacity: 536870912000, truesize: 536870912000
> And after what is the next step?
> Regards
> Massimo
>
>
> Il giorno lun 19 ott 2020 alle ore 13:51 Shani Leviim 
> ha scritto:
>
>> Hi Massimo,
>> In order to locate the illegal image, you can run this command on the
>> host:
>> vdsm-tool dump-volume-chains 
>>
>> It's also recommended to verify that the engine and vdsm are synced about
>> that image, once you've find it, by running this command on the engine:
>> SELECT *
>>  FROM images_storage_domain_view images_storage_domain_view
>>  WHERE image_group_id = ;
>>
>> Than, you can try removing it from the engine.
>> (and if it doesn't work - you can delete it from the DB)
>>
>>
>> *Regards,*
>>
>> *Shani Leviim*
>>
>>
>> On Mon, Oct 19, 2020 at 11:15 AM Massimo Mad  wrote:
>>
>>> Hi,
>>> I try to delete a snapshot that i have created in the past, now in the
>>> events i have the following error:
>>> Failed to delete snapshot
>>> And the VM now has the exclamation point with the following message:
>>> VM has snapshot with disk in illegal status
>>> How i can fix this problem ?
>>> Regards
>>> Massimo
>>> ___
>>> 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/VZJ62WAKAVWWORPPEIKMAT4KXOB6AU2D/
>>>
>>
___
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/4XTOI6EZIX2MT5NQ6LGDM5CDOPXZJEGX/


[ovirt-users] Re: VM has snapshot with disk in illegal status

2020-10-19 Thread Massimo Mad
Hi Shani
I run the command on the host owner of the SPM it's correct ?
This is the output:
[root@ovirthpr01 ~]# vdsm-tool dump-volume-chains
eb483eb3-a9ce-4867-9ce8-96a0ca171042

Images volume chains (base volume first)

   image:ff44dc13-de50-4891-84ce-9fb3e3fe1c88

 - c45ee9cd-17e3-4cec-b7fb-74af27e792a8
   status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
type: PREALLOCATED, capacity: 134217728, truesize: 134217728


   image:a0f9a434-7837-4ec6-8017-c9698ed5cd01

 - 64ac336f-25d8-43d0-aeb8-7fb77bf6ef97
   status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
type: PREALLOCATED, capacity: 214748364800, truesize: 214748364800


   image:4da04f46-2fea-436f-9648-772c24a849c3

 - 77ddb7b8-b10f-4d7e-82df-36e077a9eb25
   status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
type: PREALLOCATED, capacity: 134217728, truesize: 134217728


   image:55893adf-1e56-4346-8070-4b3e660dd44d

 - ea57d10b-13d5-4696-bedc-13a92b88f32d
   status: ILLEGAL, voltype: LEAF, format: COW, legality:
ILLEGAL, type: SPARSE, capacity: 107374182400, truesize: 1744830464


   image:825765ba-b132-4b36-8cb9-8ecd2c7b597a

 - 5c534181-fbd6-4912-afdc-4ac812e0e9fe
   status: ILLEGAL, voltype: LEAF, format: COW, legality:
ILLEGAL, type: SPARSE, capacity: 85899345920, truesize: 1879048192


   image:0264f52e-fa59-4523-81e4-47564193665e

 - dfb3d366-f2d3-49ee-8ca3-3b44e24a0111
   status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
type: PREALLOCATED, capacity: 536870912000, truesize: 536870912000
And after what is the next step?
Regards
Massimo


Il giorno lun 19 ott 2020 alle ore 13:51 Shani Leviim 
ha scritto:

> Hi Massimo,
> In order to locate the illegal image, you can run this command on the host:
> vdsm-tool dump-volume-chains 
>
> It's also recommended to verify that the engine and vdsm are synced about
> that image, once you've find it, by running this command on the engine:
> SELECT *
>  FROM images_storage_domain_view images_storage_domain_view
>  WHERE image_group_id = ;
>
> Than, you can try removing it from the engine.
> (and if it doesn't work - you can delete it from the DB)
>
>
> *Regards,*
>
> *Shani Leviim*
>
>
> On Mon, Oct 19, 2020 at 11:15 AM Massimo Mad  wrote:
>
>> Hi,
>> I try to delete a snapshot that i have created in the past, now in the
>> events i have the following error:
>> Failed to delete snapshot
>> And the VM now has the exclamation point with the following message:
>> VM has snapshot with disk in illegal status
>> How i can fix this problem ?
>> Regards
>> Massimo
>> ___
>> 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/VZJ62WAKAVWWORPPEIKMAT4KXOB6AU2D/
>>
>
___
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/2CYLBMY7IF3YSZFMUU44DL26GZ3ORFH4/


[ovirt-users] Re: VM has snapshot with disk in illegal status

2020-10-19 Thread Shani Leviim
Hi Massimo,
In order to locate the illegal image, you can run this command on the host:
vdsm-tool dump-volume-chains 

It's also recommended to verify that the engine and vdsm are synced about
that image, once you've find it, by running this command on the engine:
SELECT *
 FROM images_storage_domain_view images_storage_domain_view
 WHERE image_group_id = ;

Than, you can try removing it from the engine.
(and if it doesn't work - you can delete it from the DB)


*Regards,*

*Shani Leviim*


On Mon, Oct 19, 2020 at 11:15 AM Massimo Mad  wrote:

> Hi,
> I try to delete a snapshot that i have created in the past, now in the
> events i have the following error:
> Failed to delete snapshot
> And the VM now has the exclamation point with the following message:
> VM has snapshot with disk in illegal status
> How i can fix this problem ?
> Regards
> Massimo
> ___
> 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/VZJ62WAKAVWWORPPEIKMAT4KXOB6AU2D/
>
___
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/MQXKZIN27RJDXIVARH4EBAC3VYKTYSP5/


[ovirt-users] oVirt Survey Autumn 2020 results

2020-10-19 Thread Sandro Bonazzola
Thanks to the 79 participants to oVirt Survey Autumn 2020!
The survey is now closed and results are publicly available at
https://docs.google.com/forms/d/1eMYaCoysPkYt2iHZW2RRO1HmSqsD0phrwSTVYFlqLy4/viewanalytics
We'll analyze collected data in order to improve oVirt thanks to your
feedback.

Thanks,
-- 

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/AKU27TVYXZNIPONFIWSULXISY5T7KRGO/


[ovirt-users] [ANN] oVirt 4.4.3 Fifth Release Candidate is now available for testing

2020-10-19 Thread Lev Veyde
oVirt 4.4.3 Fifth Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.3
Fifth Release Candidate for testing, as of October 16th, 2020.

This update is the third in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA should not require re-doing these steps, if
already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only
required to be done once.

Due to Bug 1837864  -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.3 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

   1.

   Remove the current lvm filter while still on 4.4.1, or in emergency mode
   (if rebooted).
   2.

   Reboot.
   3.

   Upgrade to 4.4.3 (redeploy in case of already being on 4.4.3).
   4.

   Run vdsm-tool config-lvm-filter to confirm there is a new filter in
   place.
   5.

   Only if not using oVirt Node:
   - run "dracut --force --add multipath” to rebuild initramfs with the
   correct filter configuration
   6.

   Reboot.

Documentation

   -

   If you want to try oVirt as quickly as possible, follow the instructions
   on the Download  page.
   -

   For complete installation, administration, and usage instructions, see
   the oVirt Documentation .
   -

   For upgrading from a previous version, see the oVirt Upgrade Guide
   .
   -

   For a general overview of oVirt, see About oVirt
   .

Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.3 release highlights:
http://www.ovirt.org/release/4.4.3/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/


[1] http://www.ovirt.org/release/4.4.3/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel



l...@redhat.com | lve...@redhat.com

TRIED. TESTED. TRUSTED. 
___
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/3CRWW4EMTGHRVGGJM6EY4DUEEM6QJKBI/


[ovirt-users] VM has snapshot with disk in illegal status

2020-10-19 Thread Massimo Mad
Hi,
I try to delete a snapshot that i have created in the past, now in the
events i have the following error:
Failed to delete snapshot
And the VM now has the exclamation point with the following message:
VM has snapshot with disk in illegal status
How i can fix this problem ?
Regards
Massimo
___
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/VZJ62WAKAVWWORPPEIKMAT4KXOB6AU2D/


[ovirt-users] Re: 20+ Fresh Installs Failing in 20+ days [newbie & frustrated]

2020-10-19 Thread Yedidyah Bar David
Hi,

On Fri, Oct 16, 2020 at 4:44 PM  wrote:
>
> Another zip file from fresh Centos & Ovirt install
>
> The following directories and files are included
> 1. openvswitch
> 2. ovirt-hosted-engine-ha
> 3. ovirt-hosted-engine-setup
> 4. ovirt-imageio
> 5. vdsm
> 6. firewalld
>
> https://drive.google.com/file/d/1QXj2eiNYseJvTVwmlDp8qwIWg64t45Sc/view?usp=sharing

Thanks.

It's still the same problem ("Check engine VM health" failed) and the zip
still does not include engine-side logs (either from the engine vm itself
or from subdirs of /var/log/ovirt-hosted-engine-setup). Please check/share
these.

Also, the files' timestamps are not kept, so 'ls -ltr' does not show them
in the correct order. Is there a problem with simply using 'tar' as I suggested?

Thanks and best regards,
-- 
Didi
___
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/OSV5JYVZTMAJJ7L4O4XHAIBWDL5VKZNP/


[ovirt-users] Re: New host: no network interfaces visible

2020-10-19 Thread Ales Musil
On Thu, Oct 15, 2020 at 2:39 PM Richard Chan 
wrote:

> What could cause no Network Interfaces visible in installing a new host?
>
> I have added a new host to oVirt 4.3.10, the initial SSH installs all the
> packages (all with failed=0 in host-deploy/*log). The installation is shown
> as failed without any meaningful message.
>
> However the Network Interfaces page is blank, what could cause this?
>
> Host in CentOS 7.8 tried with/without biosdevname.
>
>
> --
> Richard Chan
>
> ___
> 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/UWXJCPL6CNNQN37RY4DUGVGDBOTDK23B/
>


Hello Richard,

can you please share relevant logs from the host deploy?
It should be located on the engine machine
/var/log/ovirt-engine/host-deploy/.

Thanks.

Regards,
Ales Musil

-- 

Ales Musil

Software Engineer - RHV Network

Red Hat EMEA 

amu...@redhat.comIM: amusil

___
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/T76JE7ITJ7IS47BORPF2O3QCDDNTVGY7/