[ovirt-users] Cannot put host in maintenance mode

2020-01-27 Thread Vinícius Ferrão 
Hello,

I’m with an issue on one of my oVirt installs and I wasn’t able to solve it. 
When trying to put a node in maintenance it complains about image transfers:

Error while executing action: Cannot switch Host ovirt2 to Maintenance mode. 
Image transfer is in progress for the following (3) disks: 

8f4c712e-66bb-4bfc-9afb-78407b8b726c,
eb0ef249-284d-4d77-b1f1-ee8b70718f3d,
73245a4c-8f56-4508-a5c5-2d7697f87654 

Please wait for the operations to complete and try again.

I wasn’t able to find this image transfers. There’s nothing on the engine 
showing any transfer.

How can I debug this?

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

[ovirt-users] Details about bios and custom emulated machine values

2020-01-27 Thread Gianluca Cecchi 
Hello,
in oVirt 4.3.7 in "Edit VM" -> System -> Advanced parameters
I can choose

Bios Type:
Default
Q35 Chipset with Legacy BIOS
Q35 Chipset with UEFI BIOS
Q35 Chipset with SecureBoot

and
Custom Emulated Machine:
Use cluster default (pc-i440fx-rhel7.6.0)
...
q35
pc-q35-rhel7.3.0
pc-q35-rhel7.4.0
pc-q35-rhel7.5.0
pc-q35-rhel7.6.0

and I can apparently mix all possible values.
Any deeper information about implications?
What is the "Default" value for Bios Type?

Did anything change in 4.3.8 (eg official support for q35)?

I search also through official docs for RHV 4.3 (virtual mgmt guide,
appendix A), but for example I don't find any reference to the "Bios Type"
parameter and a vague reference to the "Custom Emulated Machine". Is there
any more detailed link?

Thanks,
Gianluca
___
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/RBXYGBA6MBUYURYYMDC75LU7LOJJBOPB/

[ovirt-users] Windows Server Migration from Proxmox

2020-01-27 Thread Robert Webb 
I have several Windows systems I am trying to migrate from Proxmox. In each VM 
under Proxmox, I have removed all guest utilities and completed a clean 
shutdown.

I have successfully imported the disk image into oVirt and attached to a new VM 
with the same specs. 

When I power on, though, they all give me a "kmode exception not handled".

Has anyone else run into this and successfully migrated a WIndows VM? These are 
primarily Server 2019 systems..
___
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/EYSC2DTNOTO6VFTHONO45OUAX2T65NIF/

[ovirt-users] Re: [ANN] oVirt 4.3.8 is now generally available

2020-01-27 Thread Robert Webb 
That fixed it.

Thanks..


From: Sandro Bonazzola 
Sent: Monday, January 27, 2020 10:22 AM
To: Robert Webb
Cc: users
Subject: Re: [ovirt-users] [ANN] oVirt 4.3.8 is now generally available



Il giorno lun 27 gen 2020 alle ore 15:59 Robert Webb 
mailto:rw...@ropeguru.com>> ha scritto:
Have the repositories been updated yet?

Running oVIrt Node 4.3.7 with hosted engine in a cluster.

Was able to successfully update the engine, bit when following the online 
upgrade instructions, running "Installation --> Check" on the host does not 
come back with any updates. Manually running an update check with 'yum update" 
yields the same result.


Link used for updating instructions: 
https://www.ovirt.org/documentation/upgrade-guide/chap-Updates_between_Minor_Releases.html

mirrors are still syncing, maybe you just hit a mirror which wasn't updated yet.
Can you "yum clean metadata" and retry?






From: Sandro Bonazzola mailto:sbona...@redhat.com>>
Sent: Monday, January 27, 2020 7:50 AM
To: users
Subject: [ovirt-users] [ANN] oVirt 4.3.8  is now generally available

The oVirt Project is pleased to announce the general availability of oVirt 
4.3.8 as of January 27th, 2020.



This update is the eighth in a series of stabilization updates to the 4.3 
series.



This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)



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

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)

* oVirt Node 4.3 (available for x86_64 only)



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



Notes:

- oVirt Appliance is already available

- oVirt Node is already available[2]


oVirt Node and Appliance have been updated including:

- oVirt 4.3.8: http://www.ovirt.org/release/4.3.8/

  *   Including fixes for CVE-2019-19336 oVirt Engine Cross Site Scripting 
Vulnerability

- Latest CentOS 7.7 updates including:

  *   CEBA-2019:3970 CentOS 7 ca-certificates BugFix 
Update

  *   CEBA-2019:3971 CentOS 7 curl BugFix 
Update

  *   CEBA-2019:3985 CentOS 7 iproute BugFix 
Update

  *   CESA-2019:3979 Important CentOS 7 kernel Security 
Update

  *   CEBA-2019:4106 CentOS 7 kernel BugFix 
Update

  *   CEBA-2019:3983 CentOS 7 util-linux BugFix 
Update

  *   CEBA-2019:3972 CentOS 7 sssd BugFix 
Update

  *   CEBA-2019:3969 CentOS 7 samba BugFix 
Update

  *   CEBA-2019:3975 CentOS 7 libvirt BugFix 
Update

  *   CEEA-2019:4161 CentOS 7 microcode_ctl Enhancement 
Update

  *   CESA-2019:4190 Important CentOS 7 nss Security 
Update

  *   CESA-2019:4190 Important CentOS 7 nss-softokn Security 
Update

  *   CESA-2019:4190 Important CentOS 7 nss-util Security 
Update

  *   CEBA-2019:3977 CentOS 7 numactl BugFix 
Update

  *   CEBA-2019:3982 CentOS 7 selinux-policy BugFix 
Update

  *   CEBA-2019:3973 CentOS 7 sos BugFix 
Update

  *   CESA-2019:3976 Low CentOS 7 tcpdump Security 
Update

- latest CentOS Virt and Storage SIG updates:

  *   Ansible 2.9.4: 
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst#v2-9-4

  *   Glusterfs 6.7: https://docs.gluster.org/en/latest/release-notes/6.7/



Given the amount of security fixes provided by this release, upgrade is 
recommended as soon as practical.


Additional Resources:

* Read more about the oVirt 4.3.8 release

[ovirt-users] Update 4.4

2020-01-27 Thread Dirk Streubel 
Hello,

i use for testing Version 4.4 and i wanted to make a update.

This is the result:

LANG=C engine-setup

...

[ INFO  ] Checking for product updates...
[ ERROR ] Yum
[u'ovirt-engine-backend-4.4.0-0.0.master.20200122090542.git5f0a359.el7.noarch
requires java-client-kubevirt >= 0.1.0']
[ INFO  ] Yum Performing yum transaction rollback
[ ERROR ] Failed to execute stage 'Environment customization':
[u'ovirt-engine-backend-4.4.0-0.0.master.20200122090542.git5f0a359.el7.noarch
requires java-client-kubevirt >= 0.1.0']
[ INFO  ] Stage: Clean up
  Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20200127193352-x6p04t.log
[ INFO  ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20200127193405-setup.conf'
[ ERROR ] Failed to execute stage 'Clean up': must be unicode, not str
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed

So, i found this:

https://repo1.maven.org/maven2/org/ovirt/java-client-kubevirt/java-client-kubevirt/0.2.0/

So, do i have to install a.jar to make the engine update or what is the
best way to do the update?

Dirk


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

[ovirt-users] Re: command line vm start/stop

2020-01-27 Thread Staniforth, Paul 
Hello,
you could use ansible or for a common cli to (libvirt, KubeVirt, 
oVirt, OpenStack, VMware vSphere, GCP and AWS) you could try kcli 
https://github.com/karmab/kcli/blob/master/doc/index.md ( although I haven't 
tried it yet).


Regards,
   Paul S.

From: uran...@gmail.com 
Sent: 27 January 2020 13:35
To: users@ovirt.org 
Subject: [ovirt-users] command line vm start/stop

Caution External Mail: Do not click any links or open any attachments unless 
you trust the sender and know that the content is safe.

Hello Experts.

In version  3.5.2.1-1.el6, we used an "ovirt-shell -E action..." command to 
start/stop virtual machines from command line. In version 4.3.7.2-1.el7 
ovirt-shell is deprecated. Please advise how to start/stop them from command 
line. vdsm-client provides only destroy/shutdown/reset/cont, nothing about 
startvm or poweron.

Regards.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: 
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fsite%2Fprivacy-policy%2Fdata=02%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7Cb7300c7a7e994339292508d7a33722f4%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C1%7C637157329524130327sdata=f1VuO2uEH%2BZlpPxNTKMO2Y5uIFbnCtu2bN7QBx8Gkvk%3Dreserved=0
oVirt Code of Conduct: 
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fcommunity%2Fabout%2Fcommunity-guidelines%2Fdata=02%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7Cb7300c7a7e994339292508d7a33722f4%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C1%7C637157329524130327sdata=czyRpS4jkA8GMsLAKVJwb56PeKwyUKeTsp9fMa7Vyjg%3Dreserved=0
List Archives: 
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovirt.org%2Farchives%2Flist%2Fusers%40ovirt.org%2Fmessage%2FQRNBIPH42NYX7VY7YBXO235R2HKQOCRH%2Fdata=02%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7Cb7300c7a7e994339292508d7a33722f4%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C1%7C637157329524130327sdata=Z5DrMzBYdX8s5NOG0X2lDRBWHjfgOrEiPGWjaKur5YU%3Dreserved=0
To view the terms under which this email is distributed, please go to:-
http://leedsbeckett.ac.uk/disclaimer/email/
___
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/VIMWBEQFBU6CKFG63IU4PFW4NNHML7QC/

[ovirt-users] Re: Unsynced entries do not self-heal during upgrade from oVirt 4.2 -> 4.3

2020-01-27 Thread Strahil Nikolov 
On January 27, 2020 4:17:26 PM GMT+02:00, "Goorkate, B.J." 
 wrote:
>Hi all,
>
>I'm in the process of upgrading oVirt-nodes from 4.2 to 4.3. 
>
>After upgrading the first of 3 oVirt/gluster nodes, there are between
>600-1200 unsynced entries for a week now on 1 upgraded node and one
>not-yet-upgraded node. The third node (also not-yet-upgraded) says it's
>OK (no unsynced entries).
>
>The cluster doesn't seem to be very busy, but somehow self-heal doesn't
>complete.
>
>Is this because of different gluster versions across the nodes and will
>it resolve as soon as I upgraded all nodes? Since it's our production
>cluster, I don't want to take any risk...
>
>Does anybody recognise this problem? Of course I can provide more
>information if necessary.
>
>Any hints on troubleshooting the unsynced entries are more than
>welcome!
>
>Thanks in advance!
>
>Regards,
>
>Bertjan
>
>--
>
>De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is
>uitsluitend bestemd voor de geadresseerde. Indien u dit bericht
>onterecht
>ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender
>direct
>te informeren door het bericht te retourneren. Het Universitair Medisch
>Centrum Utrecht is een publiekrechtelijke rechtspersoon in de zin van
>de W.H.W.
>(Wet Hoger Onderwijs en Wetenschappelijk Onderzoek) en staat
>geregistreerd bij
>de Kamer van Koophandel voor Midden-Nederland onder nr. 30244197.
>
>Denk s.v.p aan het milieu voor u deze e-mail afdrukt.
>
>--
>
>This message may contain confidential information and is intended
>exclusively
>for the addressee. If you receive this message unintentionally, please
>do not
>use the contents but notify the sender immediately by return e-mail.
>University
>Medical Center Utrecht is a legal person by public law and is
>registered at
>the Chamber of Commerce for Midden-Nederland under no. 30244197.
>
>Please consider the environment before printing this e-mail.
>___
>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/OSF5DPTRS4WS3GG6JA6GOEQP6CGPOC5Y/

I don't  wabt to scare you, but I don't think it's related to the different 
versions.

Have yiu tried the following:
1. Run 'gluster volume heal  full'
2. Run a stat to force an update from client side (wait for the full heal to 
finish).
find /rhev/data-center/mnt/glusterSD  -iname '*' -exec stat {} \;

Best Regards,
Strahil Nikolov
___
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/JXLFXUMIPCJ7LSTAES4S2IWXS73XMHRD/

[ovirt-users] Re: [ANN] oVirt 4.3.8 is now generally available

2020-01-27 Thread Robert Webb 
Have the repositories been updated yet?

Running oVIrt Node 4.3.7 with hosted engine in a cluster.

Was able to successfully update the engine, bit when following the online 
upgrade instructions, running "Installation --> Check" on the host does not 
come back with any updates. Manually running an update check with 'yum update" 
yields the same result.


Link used for updating instructions: 
https://www.ovirt.org/documentation/upgrade-guide/chap-Updates_between_Minor_Releases.html


From: Sandro Bonazzola 
Sent: Monday, January 27, 2020 7:50 AM
To: users
Subject: [ovirt-users] [ANN] oVirt 4.3.8  is now generally available

The oVirt Project is pleased to announce the general availability of oVirt 
4.3.8 as of January 27th, 2020.



This update is the eighth in a series of stabilization updates to the 4.3 
series.



This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)



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

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)

* oVirt Node 4.3 (available for x86_64 only)



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



Notes:

- oVirt Appliance is already available

- oVirt Node is already available[2]


oVirt Node and Appliance have been updated including:

- oVirt 4.3.8: http://www.ovirt.org/release/4.3.8/

  *   Including fixes for CVE-2019-19336 oVirt Engine Cross Site Scripting 
Vulnerability

- Latest CentOS 7.7 updates including:

  *   CEBA-2019:3970 CentOS 7 ca-certificates BugFix 
Update

  *   CEBA-2019:3971 CentOS 7 curl BugFix 
Update

  *   CEBA-2019:3985 CentOS 7 iproute BugFix 
Update

  *   CESA-2019:3979 Important CentOS 7 kernel Security 
Update

  *   CEBA-2019:4106 CentOS 7 kernel BugFix 
Update

  *   CEBA-2019:3983 CentOS 7 util-linux BugFix 
Update

  *   CEBA-2019:3972 CentOS 7 sssd BugFix 
Update

  *   CEBA-2019:3969 CentOS 7 samba BugFix 
Update

  *   CEBA-2019:3975 CentOS 7 libvirt BugFix 
Update

  *   CEEA-2019:4161 CentOS 7 microcode_ctl Enhancement 
Update

  *   CESA-2019:4190 Important CentOS 7 nss Security 
Update

  *   CESA-2019:4190 Important CentOS 7 nss-softokn Security 
Update

  *   CESA-2019:4190 Important CentOS 7 nss-util Security 
Update

  *   CEBA-2019:3977 CentOS 7 numactl BugFix 
Update

  *   CEBA-2019:3982 CentOS 7 selinux-policy BugFix 
Update

  *   CEBA-2019:3973 CentOS 7 sos BugFix 
Update

  *   CESA-2019:3976 Low CentOS 7 tcpdump Security 
Update

- latest CentOS Virt and Storage SIG updates:

  *   Ansible 2.9.4: 
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst#v2-9-4

  *   Glusterfs 6.7: https://docs.gluster.org/en/latest/release-notes/6.7/



Given the amount of security fixes provided by this release, upgrade is 
recommended as soon as practical.


Additional Resources:

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

* 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.3.8/

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





--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA

sbona...@redhat.com

[ovirt-users] Re: [ANN] oVirt 4.3.8 is now generally available

2020-01-27 Thread Sandro Bonazzola 
Il giorno lun 27 gen 2020 alle ore 15:59 Robert Webb 
ha scritto:

> Have the repositories been updated yet?
>
> Running oVIrt Node 4.3.7 with hosted engine in a cluster.
>
> Was able to successfully update the engine, bit when following the online
> upgrade instructions, running "Installation --> Check" on the host does not
> come back with any updates. Manually running an update check with 'yum
> update" yields the same result.
>
>
> Link used for updating instructions:
> https://www.ovirt.org/documentation/upgrade-guide/chap-Updates_between_Minor_Releases.html


mirrors are still syncing, maybe you just hit a mirror which wasn't updated
yet.
Can you "yum clean metadata" and retry?




>
>
> 
> From: Sandro Bonazzola 
> Sent: Monday, January 27, 2020 7:50 AM
> To: users
> Subject: [ovirt-users] [ANN] oVirt 4.3.8  is now generally available
>
> The oVirt Project is pleased to announce the general availability of oVirt
> 4.3.8 as of January 27th, 2020.
>
>
>
> This update is the eighth in a series of stabilization updates to the 4.3
> series.
>
>
>
> This release is available now on x86_64 architecture for:
>
> * Red Hat Enterprise Linux 7.7 or later (but < 8)
>
> * CentOS Linux (or similar) 7.7 or later (but < 8)
>
>
>
> This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
> for:
>
> * Red Hat Enterprise Linux 7.7 or later (but < 8)
>
> * CentOS Linux (or similar) 7.7 or later (but < 8)
>
> * oVirt Node 4.3 (available for x86_64 only)
>
>
>
> See the release notes [1] for installation / upgrade instructions and a
> list of new features and bugs fixed.
>
>
>
> Notes:
>
> - oVirt Appliance is already available
>
> - oVirt Node is already available[2]
>
>
> oVirt Node and Appliance have been updated including:
>
> - oVirt 4.3.8: http://www.ovirt.org/release/4.3.8/
>
>   *   Including fixes for CVE-2019-19336 oVirt Engine Cross Site Scripting
> Vulnerability<
> https://www.symantec.com/security-center/vulnerabilities/writeup/111466>
>
> - Latest CentOS 7.7 updates including:
>
>   *   CEBA-2019:3970 CentOS 7 ca-certificates BugFix Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035571.html
> >
>
>   *   CEBA-2019:3971 CentOS 7 curl BugFix Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035558.html
> >
>
>   *   CEBA-2019:3985 CentOS 7 iproute BugFix Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035568.html
> >
>
>   *   CESA-2019:3979 Important CentOS 7 kernel Security Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035574.html
> >
>
>   *   CEBA-2019:4106 CentOS 7 kernel BugFix Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035575.html
> >
>
>   *   CEBA-2019:3983 CentOS 7 util-linux BugFix Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035567.html
> >
>
>   *   CEBA-2019:3972 CentOS 7 sssd BugFix Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035565.html
> >
>
>   *   CEBA-2019:3969 CentOS 7 samba BugFix Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035561.html
> >
>
>   *   CEBA-2019:3975 CentOS 7 libvirt BugFix Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035562.html
> >
>
>   *   CEEA-2019:4161 CentOS 7 microcode_ctl Enhancement Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035586.html
> >
>
>   *   CESA-2019:4190 Important CentOS 7 nss Security Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035590.html
> >
>
>   *   CESA-2019:4190 Important CentOS 7 nss-softokn Security Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035589.html
> >
>
>   *   CESA-2019:4190 Important CentOS 7 nss-util Security Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035587.html
> >
>
>   *   CEBA-2019:3977 CentOS 7 numactl BugFix Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035573.html
> >
>
>   *   CEBA-2019:3982 CentOS 7 selinux-policy BugFix Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035559.html
> >
>
>   *   CEBA-2019:3973 CentOS 7 sos BugFix Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035572.html
> >
>
>   *   CESA-2019:3976 Low CentOS 7 tcpdump Security Update<
> https://lists.centos.org/pipermail/centos-announce/2019-December/035570.html
> >
>
> - latest CentOS Virt and Storage SIG updates:
>
>   *   Ansible 2.9.4:
> https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst#v2-9-4
>
>   *   Glusterfs 6.7: https://docs.gluster.org/en/latest/release-notes/6.7/
>
>
>
> Given the amount of security fixes provided by this release, upgrade is
> recommended as soon as practical.
>
>
> Additional Resources:
>
> * Read more about the oVirt 4.3.8 release highlights:
>

[ovirt-users] Re: command line vm start/stop

2020-01-27 Thread Jayme 
Hello,

I believe the best way would be to use ansible with the ovirt ansible
modules i.e.
https://docs.ansible.com/ansible/latest/modules/ovirt_vm_module.html#ovirt-vm-module
--
you can do it with a simple task like:

- name: Stop vm
  ovirt_vm:
state: stopped
name: myvm

you could also use "virsh" on the command line to stop VMs but I'd
stick with using ansible personally.


On Mon, Jan 27, 2020 at 10:41 AM  wrote:

> Hello Experts.
>
> In version  3.5.2.1-1.el6, we used an "ovirt-shell -E action..." command
> to start/stop virtual machines from command line. In version 4.3.7.2-1.el7
> ovirt-shell is deprecated. Please advise how to start/stop them from
> command line. vdsm-client provides only destroy/shutdown/reset/cont,
> nothing about startvm or poweron.
>
> Regards.
> ___
> 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/QRNBIPH42NYX7VY7YBXO235R2HKQOCRH/
>
___
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/72ODAYQUBD26HOOGOYN7Q6DTPKV2V2JW/

[ovirt-users] Unsynced entries do not self-heal during upgrade from oVirt 4.2 -> 4.3

2020-01-27 Thread Goorkate, B.J. 
Hi all,

I'm in the process of upgrading oVirt-nodes from 4.2 to 4.3. 

After upgrading the first of 3 oVirt/gluster nodes, there are between 600-1200 
unsynced entries for a week now on 1 upgraded node and one not-yet-upgraded 
node. The third node (also not-yet-upgraded) says it's OK (no unsynced entries).

The cluster doesn't seem to be very busy, but somehow self-heal doesn't 
complete.

Is this because of different gluster versions across the nodes and will it 
resolve as soon as I upgraded all nodes? Since it's our production cluster, I 
don't want to take any risk...

Does anybody recognise this problem? Of course I can provide more information 
if necessary.

Any hints on troubleshooting the unsynced entries are more than welcome!

Thanks in advance!

Regards,

Bertjan

--

De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is
uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht
ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender direct
te informeren door het bericht te retourneren. Het Universitair Medisch
Centrum Utrecht is een publiekrechtelijke rechtspersoon in de zin van de W.H.W.
(Wet Hoger Onderwijs en Wetenschappelijk Onderzoek) en staat geregistreerd bij
de Kamer van Koophandel voor Midden-Nederland onder nr. 30244197.

Denk s.v.p aan het milieu voor u deze e-mail afdrukt.

--

This message may contain confidential information and is intended exclusively
for the addressee. If you receive this message unintentionally, please do not
use the contents but notify the sender immediately by return e-mail. University
Medical Center Utrecht is a legal person by public law and is registered at
the Chamber of Commerce for Midden-Nederland under no. 30244197.

Please consider the environment before printing this e-mail.
___
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/OSF5DPTRS4WS3GG6JA6GOEQP6CGPOC5Y/

[ovirt-users] command line vm start/stop

2020-01-27 Thread uran987 
Hello Experts.

In version  3.5.2.1-1.el6, we used an "ovirt-shell -E action..." command to 
start/stop virtual machines from command line. In version 4.3.7.2-1.el7 
ovirt-shell is deprecated. Please advise how to start/stop them from command 
line. vdsm-client provides only destroy/shutdown/reset/cont, nothing about 
startvm or poweron.

Regards.
___
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/QRNBIPH42NYX7VY7YBXO235R2HKQOCRH/

[ovirt-users] [ANN] oVirt 4.3.8 is now generally available

2020-01-27 Thread Sandro Bonazzola 
The oVirt Project is pleased to announce the general availability of oVirt
4.3.8 as of January 27th, 2020.



This update is the eighth in a series of stabilization updates to the 4.3
series.



This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)



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

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)

* oVirt Node 4.3 (available for x86_64 only)



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



Notes:

- oVirt Appliance is already available

- oVirt Node is already available[2]

oVirt Node and Appliance have been updated including:

- oVirt 4.3.8: http://www.ovirt.org/release/4.3.8/

   -

   Including fixes for CVE-2019-19336 oVirt Engine Cross Site Scripting
   Vulnerability
   

- Latest CentOS 7.7 updates including:

   -

   CEBA-2019:3970 CentOS 7 ca-certificates BugFix Update
   


   -

   CEBA-2019:3971 CentOS 7 curl BugFix Update
   


   -

   CEBA-2019:3985 CentOS 7 iproute BugFix Update
   

   -

   CESA-2019:3979 Important CentOS 7 kernel Security Update
   

   -

   CEBA-2019:4106 CentOS 7 kernel BugFix Update
   

   -

   CEBA-2019:3983 CentOS 7 util-linux BugFix Update
   


   -

   CEBA-2019:3972 CentOS 7 sssd BugFix Update
   


   -

   CEBA-2019:3969 CentOS 7 samba BugFix Update
   

   -

   CEBA-2019:3975 CentOS 7 libvirt BugFix Update
   


   -

   CEEA-2019:4161 CentOS 7 microcode_ctl Enhancement Update
   


   -

   CESA-2019:4190 Important CentOS 7 nss Security Update
   

   -

   CESA-2019:4190 Important CentOS 7 nss-softokn Security Update
   


   -

   CESA-2019:4190 Important CentOS 7 nss-util Security Update
   


   -

   CEBA-2019:3977 CentOS 7 numactl BugFix Update
   

   -

   CEBA-2019:3982 CentOS 7 selinux-policy BugFix Update
   

   -

   CEBA-2019:3973 CentOS 7 sos BugFix Update
   


   -

   CESA-2019:3976 Low CentOS 7 tcpdump Security Update
   



- latest CentOS Virt and Storage SIG updates:

   -

   Ansible 2.9.4:
   
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst#v2-9-4

   -

   Glusterfs 6.7: https://docs.gluster.org/en/latest/release-notes/6.7/



Given the amount of security fixes provided by this release, upgrade is
recommended as soon as practical.

Additional Resources:

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

* 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.3.8/

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





-- 

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

[ovirt-users] Re: feature policy='require' name='md-clear'

2020-01-27 Thread Strahil Nikolov 
 You need some extra steps:1. Set alias:
alias virsh='virsh -c 
qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf'2. Get the xml 
of the HostedEngine and save it to a file. Edit it and try either with removed 
or with feature policy='optional'3. Check if you have the following 
network:[root@ovirt1 ~]# virsh net-dumpxml vdsm-ovirtmgmt

  vdsm-ovirtmgmt
  1185a91b-533a-4bee-8a66-3208846605fa
  
  


If not , you can define it in a file and use virsh to import it.
4. use virsh to define and start the HostedEnginevirsh define 
HostedEngine.xmlvirsh start HostedEngine
5. Wait for the VM to power up and access over ssh. Do general healthcheck.
6. Leave the Engine working for several hours, so it can update the relevant 
data on the shared storage.
7. Power off the VM and start it via vdsm
Best Regards,Strahil Nikolov

В неделя, 26 януари 2020 г., 9:59:18 Гринуич-5, thomas.c.albre...@lmco.com 
 написа:  
 
 Tried this... had to make a new user, but "allow" isn't part of the grammar.  
Tried optional, but when I did a "hosted-engine --vm-start", the configuration 
for the engine reverted back to the original configuration and failed.

I don't think virsh is the proper way to make changes to the ovirt VMs.  I 
tried using vdsm-client instead, but couldn't figure out the syntax.  Any other 
ideas?
___
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/F6FR6T73OX4XT43E2VFPSJHEJCZGRVY5/
  ___
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/HOP4ZCJO6MHDOWAI5X6AH46GWOZE44NQ/