[ovirt-users] Re: vGPU on ovirt 4.3

2021-01-27 Thread Gianluca Cecchi
On Wed, Jan 27, 2021 at 9:14 AM  wrote:

> I would also be interested to know that :)
>

Ok, I think I found at least for Nvidia. You can follow what described for
RHV:
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/setting_up_an_nvidia_gpu_for_a_virtual_machine_in_red_hat_virtualization/proc_nvidia_gpu_passthrough_nvidia_gpu_passthrough

In the same manual there are also instructions for vGPU.

There is also the guide for 4.3:
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/setting_up_an_nvidia_gpu_for_a_virtual_machine_in_red_hat_virtualization/proc_nvidia_gpu_passthrough_nvidia_gpu_passthrough

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


[ovirt-users] Re: OVN and change of mgmt network

2021-01-26 Thread Gianluca Cecchi
On Tue, Jan 26, 2021 at 7:54 PM Kevin Doyle 
wrote:

> Hi Gianluca did you ever resolve this ? I add a new host using the same IP
> as the old host but get errors that ovs already has an entry (the old one)
>
> Thanks
> Kevin
>
>
yes, with the suggested command I was able to delete the previously defined
chassis of the removed/readded host
But probably it was oVirt 4.3 time. Are you using 4.4 or 4.3? In 4.4 the
removal of host from web admin gui should imply an ansible playbook how
removes ovn config for that host
And probably you can cross check logs to understand why it was left over...

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


[ovirt-users] Re: vGPU on ovirt 4.3

2021-01-26 Thread Gianluca Cecchi
On Tue, Jan 26, 2021 at 5:30 PM Michal Skrivanek <
michal.skriva...@redhat.com> wrote:

>
>
>
> why a hook? we have a “native” ovirt support for both GPU and vGPU since
> cca 4.1.
> There was a hook initially, but that’s no longer needed…since 4.2 iirc
> I think we also tested some Intel’s GTV-g card...
>
>
My suggestion  for the hook was only for GPU passthrough, not being P4000
supported for vGPU.
Good to know that GPU passthrough is supported/integrated. Do you have a
description of the workflow for doing it without a hook? Edit VM? Add
device?
Thanks,
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/5BRV2YNZU2U3DR4JXNT2YXH4L5QELXPN/


[ovirt-users] Re: vGPU on ovirt 4.3

2021-01-26 Thread Gianluca Cecchi
On Tue, Jan 26, 2021 at 10:26 AM  wrote:

> Thanks all for the feedback.
>
> When we bought the servers, they put some Nvidia Quadro P4000's in, but I
> can't seem to find anything that says they support vGPU.
>
> I wasn't aware of the license server requirement for Nvidia, but the
> pricing isn't too bad, so I can probably get that pushed through. Anyone
> aware of which AMD cards are supported by oVirt? I have only found a list
> of Nvidia cards.
>
> Thanks,
>
> Kim
>
>

Hello,
updated list of supported GPUs for vGPU functionality should be this one:
https://docs.nvidia.com/grid/gpus-supported-by-vgpu.html

and P4000 seems not to be present

So you could use the other supported method, with passthrough Gpu,
following what described here for qemu command line:
https://docs.nvidia.com/grid/latest/grid-vgpu-user-guide/index.html#using-gpu-pass-through-red-hat-el-qemu-cli

and driving oVirt to do so with vdsm hook qemucmdline

[root@ov200 ~]# dnf info vdsm-hook-qemucmdline.noarch
Last metadata expiration check: 2:48:59 ago on Tue 26 Jan 2021 09:58:06 AM
CET.
Available Packages
Name : vdsm-hook-qemucmdline
Version  : 4.40.40
Release  : 1.el8
Architecture : noarch
Size : 15 k
Source   : vdsm-4.40.40-1.el8.src.rpm
Repository   : ovirt-4.4
Summary  : QEMU cmdline hook for VDSM
URL  : http://www.ovirt.org/develop/developer-guide/vdsm/vdsm/
License  : GPLv2+
Description  : Provides support for injecting QEMU cmdline via VDSM hook.
 : It exploits libvirt's qemu:commandline facility available in
the
 : qemu xml namespace.

[root@ov200 ~]#

I donna if the doc here is up to date, not tested lately:
https://www.ovirt.org/develop/developer-guide/vdsm/hook/qemucmdline.html

I think the persist command in case of node is not necessary with NG any
more
Developers could confirm and eventually point to the correct page for the
hook guide?

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


[ovirt-users] Re: Grafana oVirt 4.4.4 Node install - Grafana Monitoring Portal not available

2021-01-25 Thread Gianluca Cecchi
On Mon, Jan 25, 2021 at 5:15 PM  wrote:

> Having installed oVirt 4.4.4 HCI 3 node cluster, the Grafana 'Monitoring
> Portal' was not visible on the Default page.
> It appears that Grafana is installed but not configured.
> I have checked a 4.4.3 environment and it is installed and running, so is
> this a bug with 4.4.4.7-1.el8?
> Any help would be appreciated.
>
>
there were these messages rom Lucie and Didi

https://lists.ovirt.org/archives/list/users@ovirt.org/message/SI4VIKPPRBWV234ZPXJ77O6PJX5J7GMN/

https://lists.ovirt.org/archives/list/users@ovirt.org/thread/73FS7GQJSFARZFD5SIL5YUKDS4N5KQ2C/#4GBNGXKR2HSDN6MLVCJAB62U3UZR2SHL

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


[ovirt-users] Re: Managed Block Storage and more

2021-01-19 Thread Gianluca Cecchi
On Tue, Jan 19, 2021 at 12:20 PM Benny Zlotnik  wrote:

> >Thanks for pointing out the requirement for Master domain. In theory,
> will I be able to satisfy the requirement with another iSCSI or >maybe Ceph
> iSCSI as master domain?
> It should work as ovirt sees it as a regular domain, cephFS will
> probably work too
>

Ceph iSCSI gateway should be supported since 4.1, so I think I can use it
for configuring the master domain and still leveraging the same overall
storage environment provided by Ceph, correct?

https://bugzilla.redhat.com/show_bug.cgi?id=1527061

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/3ASTNEGXSV7I4NIOG5RVZKDWIPQCEPMU/


[ovirt-users] Re: Managed Block Storage and more

2021-01-19 Thread Gianluca Cecchi
On Tue, Jan 19, 2021 at 9:01 AM Konstantin Shalygin  wrote:

> Shantur, I recommend to look to OpenStack or some OpenNebula/Proxmox if
> you wan’t use Ceph Storage.
> Current storage team support in oVirt just can break something and do not
> work with this anymore, take a look what I talking about: in [1], [2], [3]
>
>
> k
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1899453
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1899453
> [3] https://bugzilla.redhat.com/show_bug.cgi?id=1899453
>
>
>
>
perhaps a copy paste error about the bugzilla entries? They are the same
number...
___
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/3XYMG4QUM3TTTL45XGXUWA6DOWIWDQ64/


[ovirt-users] Re: Managed Block Storage and more

2021-01-19 Thread Gianluca Cecchi
On Tue, Jan 19, 2021 at 8:43 AM Benny Zlotnik  wrote:

> Ceph support is available via Managed Block Storage (tech preview), it
> cannot be used instead of gluster for hyperconverged setups.
>
>
Just for clarification: when you say Managed Block Storage you mean
cinderlib integration, correct?
Is still this one below the correct reference page for 4.4?
https://www.ovirt.org/develop/release-management/features/storage/cinderlib-integration.html

So are the manual steps still needed (and also repo config that seems
against pike)?
Or do you have an updated link for configuring cinderlib in 4.4?

Moreover, it is not possible to use a pure Managed Block Storage setup
> at all, there has to be at least one regular storage domain in a
> datacenter
>
>
Is this true only for Self Hosted Engine Environment or also if I have an
external engine?

Thanks,
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/SHSQO6WLMTVDNTVFACLOEFOFOD3GRYLW/


[ovirt-users] Re: Spliting login pages

2021-01-07 Thread Gianluca Cecchi
On Thu, Jan 7, 2021 at 3:18 PM  wrote:

> I believe it's a necessity. All portal are the same page. It's risky.
> Maybe we can use a WAF to solve the issue.
>
>
Risky for what?
You have to profile your users, depending on what you want them to be able
to do.
You can go to the landing page of many sensitive and critical
websites...you don't achieve security through obfuscation. Or at least it
has never been so in Linux / Open Source world
___
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/YRTNGLBQ727ZOFOSLHFU64GSKGSYK4OW/


[ovirt-users] Re: Can NFV (Network Functions Virtualization) work on oVirt?

2021-01-04 Thread Gianluca Cecchi
On Mon, Jan 4, 2021 at 10:04 AM fukumoto.shi...@fujitsu.com <
fukumoto.shi...@fujitsu.com> wrote:

> Hello everyone,
>
> I've checked the documentation of oVirt, but cannot find if following
> function can work on oVirt or not.
> - NFV (Network Functions Virtualization)
>
> Does someone know NFV can work on oVirt?
>
> For your reference, Red Hat OpenStack Platform seems to support NFV as
> follows
>
> https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/12/html-single/network_functions_virtualization_product_guide/index
>
> Regards,
> Fukumoto
>
>
I think you can find useful information here for RHV 4.4, that should be
applicable to oVirt 4.4 too:

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/administration_guide/sect-virtual_network_interface_cards#Enabling_Passthrough_on_a_vNIC_Profile
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/administration_guide/sect-hosts_and_networking#setting-up-and-configuring-sr-iov
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/hardware_considerations_for_implementing_sr-iov/
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/virtual_machine_management_guide/sect-migrating_virtual_machines_between_hosts#Live_migration_prerequisites

I don't know if it is supported to also use NFV with OVN external provider
in oVirt/RHV

HIH,
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/IGW7BI3H4IW55OKSBMVCUERQJDFCNVRH/


[ovirt-users] Re: Windows 7 vm lost network connection under heavy network load

2020-12-31 Thread Gianluca Cecchi
On Thu, Dec 31, 2020 at 8:04 AM Strahil Nikolov via Users 
wrote:

> Are you using E1000 on the VMs or on the Host ?
> If it's the second , you should change the hardware .
>
> I have never used e1000 for VMs as it is an old tech. Better to install
> the virtio drivers and then use the virtio type of NIC.
>
> Best Regards,
> Strahil Nikolov
>
> [snip]

>
> Hi folks,
>
> Happy holidays.
>
> I'm having an urgent problem :smile: .
>
> I've installed oVirt 4.4.2 on CentOS 8.2 and then created several Windows
> 7 vms for stress testing. I found that the heavy network load would lead to
> the e1000 net card NOT able to receive packets, it seemed totally blocked.
> In the meantime, packet sending was fine.
>
> Only re-enabling the net card can restore the network. Has anyone also had
> this problem? Looking forward to your insights. Much appreciated.
>
>
> Best regards,
> Joey
>
>
>
You should follow what described here that seems somehow updated because
the previously "oVirt Guest Tools" iso is no longer referred there.

https://www.ovirt.org/documentation/virtual_machine_management_guide/#chap-Installing_Windows_Virtual_Machines

In practice you have to install the virtio-win rpm package on your engine
(now at 1.9.14.4 version) and then upload the file
/usr/share/virtio-win/virtio-win.iso (actually a link to the exact release
version file) as a disk to a storage domain

Then you can attach the iso to the VM and inside the iso you will find
under the NetKVM directory some subdirs for the different os versions and
w7 (with both x86 and amd64 subdirs) is still there.
To use drivers for paravirtualized network devices you have to choose
VirtIO as the type of the network interface in web admin gui for the VM and
probably reconfigure it inside the OS because it will be detected as a new
one and will lose previous configuration.
You can also use (at install time or later) paravirtualized drivers for
disks.

HIH,
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/F2NFX4L4IPZ47G4RN6FTVU46SFV3PZ47/


[ovirt-users] Re: Moving VMs from 4.3.9 to 4.4.4

2020-12-28 Thread Gianluca Cecchi
On Mon, Dec 28, 2020 at 5:53 PM Diggy Mc  wrote:

> Templates?  Aren't the VM's templates automatically copied to the export
> domain when the VM is copied to the export domain as part of the Export
> operation?  Maybe I'm confused about how the export/import operations work
> and the purpose of the export domain.
>
> And noted, I will be sure to only have one environment at a time attached
> to the export domain.
>


I think Strahil is referring to the possible options when you create a VM
from a template (clone vs thin) and the impact when you export them; see
here (paragraph 6.13.1):
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/virtual_machine_management_guide/sect-exporting_and_importing_virtual_machines_and_templates

HIH,
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/QK3YUYIJ7AIYT4T2PEVWOLFDMSMJCMEZ/


[ovirt-users] Re: Moving VMs from 4.3.9 to 4.4.4

2020-12-28 Thread Gianluca Cecchi
On Mon, Dec 28, 2020 at 12:26 PM Strahil Nikolov via Users 
wrote:

> Keep the export domain attached only to 1 environment at a time... it's
> way more safer. Usually each engine updates some metafiles on the storage
> domain and when both try to do it ... you got a bad situation there.
>
> Attach to 4.3 , move VMs, power off them , detach the storage domain - so
> you can attach it to 4.4 and migrate those VMs. And don't forget the
> templates the VMs were created from.
>
> Best Regards,
> Strahil Nikolov
>
>
Trying to attach an export domain to a second infra should give you an
error about being "already attached elsewhere" and prevent it.
It often happens to me using the same export domain to share resources
between 3 different environments.
Not tried with heterogeneous env yet (eg activated on 4.3 and trying to
activate in 4.4, or vice versa) but I think it should give the same error
message.

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


[ovirt-users] Re: Unable to live migrate a VM from 4.4.2 to 4.4.3 CentOS Linux host

2020-12-23 Thread Gianluca Cecchi
On Thu, Nov 12, 2020 at 11:08 AM Gianluca Cecchi 
wrote:

> On Wed, Nov 11, 2020 at 10:01 PM Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>>
>> NOTE: this was a cluster in 4.3.10 and I updated it to 4.4.2 and I
>> noticed that the OVN config was not retained and I had to run on hosts:
>>
>> [root@ov200 ~]# vdsm-tool ovn-config engine_ip ov200_ip_on_mgmt
>> Using default PKI files
>> Created symlink
>> /etc/systemd/system/multi-user.target.wants/openvswitch.service →
>> /usr/lib/systemd/system/openvswitch.service.
>> Created symlink
>> /etc/systemd/system/multi-user.target.wants/ovn-controller.service →
>> /usr/lib/systemd/system/ovn-controller.service.
>> [root@ov200 ~]#
>>
>> Now it seems the problem persists...
>> Why do I have to run each time?
>>
>> Gianluca
>>
>
> In the mean time I confirm that the manual step below on ov301 let me saw
> it again between the chassis of OVN southbound on engine and I was able to
> migrate VMs to update the other host and then for example to successfully
> ping between VMs on OVN across the two hosts:
>
> [root@ov301 vdsm]# vdsm-tool ovn-config 10.4.192.43 10.4.192.34
> Using default PKI files
> Created symlink
> /etc/systemd/system/multi-user.target.wants/openvswitch.service →
> /usr/lib/systemd/system/openvswitch.service.
> Created symlink
> /etc/systemd/system/multi-user.target.wants/ovn-controller.service →
> /usr/lib/systemd/system/ovn-controller.service.
> [root@ov301 vdsm]#
>
>
As this OVN related problem seems often impacting me, I created this
bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1910340

Thanks for watching
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/QNC3ILLHR6YKW7UYRXNRWH3673SUYB4S/


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

2020-12-23 Thread Gianluca Cecchi
On Tue, Dec 22, 2020 at 11:03 AM Sandro Bonazzola 
wrote:

>
>
> Cluster compatibility level has been introduced with:
> *Bug 1877675*  - [RFE]
> Introduce Datacenter and cluster level 4.5
>
> It tracks:
> *- Bug 1725166  -
> [RFE] Private VLAN / port isolation*
> *- Support for Intel Icelake Server Family *
> *- **Bug 1814565*  - 
> Report
> disk.usage for VMs with RHEL 8 guests
> - *Bug 1852718*  - vGPU:
> VM failed to run with mdev_type instance
> - *Bug 1853194*  - VM
> with disk on iscsi on environment with SELinux enforced fails to start on
> host - Exit message: Wake up from hibernation failed:internal error: child
> reported (status=125): unable to set security context
> - *Bug 1876605*  - VM
> with scsi hostdev (scsi_generic custom property) fails on start:'node-name
> too long for qemu'
>
> +Martin Perina  , +Arik Hadas  , +Tal
> Nisan  , +Dominik Holler   feel
> free to add if I missed something.
> I think that having a page on oVirt documentation with features and
> requirements per supported cluster compatibility level would help.
> Gianluca, maybe you can open a bug for it?
>

Done. It is here:
https://bugzilla.redhat.com/show_bug.cgi?id=1910332

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


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

2020-12-21 Thread Gianluca Cecchi
On Mon, Dec 21, 2020 at 2:36 PM Sandro Bonazzola 
wrote:

>
>
> Il giorno lun 21 dic 2020 alle ore 14:31 Gianluca Cecchi <
> gianluca.cec...@gmail.com> ha scritto:
>
>> Hi Sandro,
>> thanks for the release!
>>
>> Should this fix the upgrade problems to cluster version 4.5 too when
>> using CentOS 8.3 + updates?
>>
>
> Yes
>
>
>
Hi Sandro,
I confirm that on a test cluster with 3 plain CentOS 8.3 hosts and an
external CentOS 8.3 based engine I was able to update all of them to 4.4.4
and then update both cluster and DC level to 4.5.
Can you recall, apart from being now at the latest level, what kind of new
features I should expect in 4.5 vs 4.4 so that I can also test and use them
for improvements (eg in storage domain version/features, incremental
backup, snapshotting features, export and such...)?

thanks
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/ZAWPFUPA7V4XGO5KKYI7PY5I7DFL52MY/


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

2020-12-21 Thread Gianluca Cecchi
Hi Sandro,
thanks for the release!

Should this fix the upgrade problems to cluster version 4.5 too when using
CentOS 8.3 + updates?

Thanks,
Gianluca

On Mon, Dec 21, 2020 at 2:26 PM Sandro Bonazzola 
wrote:

> oVirt 4.4.4 is now generally available
>
> The oVirt project is excited to announce the general availability of oVirt
> 4.4.4 , as of December 21st, 2020.
>
> This release unleashes an altogether more powerful and flexible open
> source virtualization solution that encompasses hundreds of individual
> changes and a wide range of enhancements across the engine, storage,
> network, user interface, and analytics, as compared to oVirt 4.3.
> Important notes before you install / upgrade
>
> Please note that oVirt 4.4 only supports clusters and data centers with
> compatibility version 4.2 and above. If clusters or data centers are
> running with an older compatibility version, you need to upgrade them to at
> least 4.2 (4.3 is recommended).
>
> Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7
> are no longer supported.
>
> For example, the megaraid_sas driver is removed. If you use Enterprise
> Linux 8 hosts you can try to provide the necessary drivers for the
> deprecated hardware using the DUD method (See the users’ mailing list
> thread on this at
> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJNPHOXUH4HOOWRIRSB4/
> )
> 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
>.
>
> What’s new in oVirt 4.4.4 Release?
>
> This update is the fourth in a series of stabilization updates to the 4.4
> series.
>
> This release is available now on x86_64 architecture for:
>
>-
>
>Red Hat Enterprise Linux 8.3
>-
>
>CentOS Linux (or similar) 8.3
>-
>
>CentOS Stream (tech preview)
>
>
> This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
> for:
>
>-
>
>Red Hat Enterprise Linux 8.3
>-
>
>CentOS Linux (or similar) 8.3
>-
>
>oVirt Node (based on CentOS Linux 8.3)
>-
>
>CentOS Stream (tech preview)
>
>
>
> oVirt Node and Appliance have been updated, including:
>
>-
>
>oVirt 4.4.4: https://www.ovirt.org/release/4.4.4/
>-
>
>Ansible 2.9.16:
>
> https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst#v2-9-16
>
>-
>
>CentOS Linux 8 (2011):
>
> https://lists.centos.org/pipermail/centos-announce/2020-December/048207.html
>-
>
>Advanced Virtualization 8.3
>
>
>
> 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.4 release highlights:
>https://www.ovirt.org/release/4.4.4/
>-
>
>Get more oVirt project updates on Twitter: https://twitter.com/ovirt
>-
>
>Check out the latest project news on the oVirt blog:
>https://blogs.ovirt.org/
>
>
> [1] https://www.ovirt.org/release/4.4.4/
> [2] https://resources.ovirt.org/pub/ovirt-4.4/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/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/KMYD2GAHZXWLE45SZWAMOXN4WYKV54MK/
>
___
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/IDZNKNJSMN5K3WAZDXAI4UNPGHKKHEMP/


[ovirt-users] Re: High performance VM cannot migrate due to TSC frequency

2020-12-17 Thread Gianluca Cecchi
On Thu, Dec 17, 2020 at 5:30 PM Milan Zamazal  wrote:

> Gianluca Cecchi  writes:
>
> > On Wed, Dec 16, 2020 at 8:59 PM Milan Zamazal 
> wrote:
> >
> >>
> >> If the checkbox is unchecked, the migration shouldn't be prevented.
> >> I think the TSC frequency shouldn't be written to the VM domain XML in
> >> such a case and then there should be no restrictions (and no guarantees)
> >> on the frequency.
> >>
> >> Do you mean you can't migrate even with the checkbox unchecked?  If so,
> >> what error message do you get in such a case?
> >>
> >
> > Yes, exactly.
> > I powered off the VM and then disabled the check and then powered on the
> VM
> > again, that is running on host ov301. ANd I have other two hosts: ov300
> and
> > ov200.
> > From web admin gui if I select the VM and "migrate" button I cannot
> select
> > the destination host and inside the bix there is the words "No available
> > host to migrate VMs to" and going to engine.log, as soon as I click the
> > "migrate" button I see these new lines:
>
> I see, I can reproduce it.  It looks like a bug in Engine.  While the VM
> is correctly started without TSC frequency set, the migration filter in
> Engine apparently still applies.
>
> I'll add a note about it to the TSC migration bug.
>
> Regards,
> Milan
>
>
Ok, thanks.
In the meantime do I have any sort of workaround to be able to migrate the
VM? Eg I could set the VM as non High Performance, or any better other
option?

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


[ovirt-users] Re: High performance VM cannot migrate due to TSC frequency

2020-12-16 Thread Gianluca Cecchi
On Wed, Dec 16, 2020 at 8:59 PM Milan Zamazal  wrote:

>
> If the checkbox is unchecked, the migration shouldn't be prevented.
> I think the TSC frequency shouldn't be written to the VM domain XML in
> such a case and then there should be no restrictions (and no guarantees)
> on the frequency.
>
> Do you mean you can't migrate even with the checkbox unchecked?  If so,
> what error message do you get in such a case?
>

Yes, exactly.
I powered off the VM and then disabled the check and then powered on the VM
again, that is running on host ov301. ANd I have other two hosts: ov300 and
ov200.
>From web admin gui if I select the VM and "migrate" button I cannot select
the destination host and inside the bix there is the words "No available
host to migrate VMs to" and going to engine.log, as soon as I click the
"migrate" button I see these new lines:

2020-12-16 23:13:27,949+01 INFO
 [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-41)
[308a29e2-2c4f-45fe-bdce-b032b36d4656] Candidate host 'ov300'
('07b979fb-4779-4477-89f2-6a96093c06f7') was filtered out by
'VAR__FILTERTYPE__INTERNAL' filter 'Migration-Tsc-Frequency' (correlation
id: null)
2020-12-16 23:13:27,949+01 INFO
 [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-41)
[308a29e2-2c4f-45fe-bdce-b032b36d4656] Candidate host 'ov200'
('949d0087-2c24-4759-8427-f9eade1dd2cc') was filtered out by
'VAR__FILTERTYPE__INTERNAL' filter 'Migration-Tsc-Frequency' (correlation
id: null)
2020-12-16 23:13:28,032+01 INFO
 [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-38)
[5837b695-c70d-4f45-a452-2c7c1b4ea69b] Candidate host 'ov300'
('07b979fb-4779-4477-89f2-6a96093c06f7') was filtered out by
'VAR__FILTERTYPE__INTERNAL' filter 'Migration-Tsc-Frequency' (correlation
id: null)
2020-12-16 23:13:28,032+01 INFO
 [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-38)
[5837b695-c70d-4f45-a452-2c7c1b4ea69b] Candidate host 'ov200'
('949d0087-2c24-4759-8427-f9eade1dd2cc') was filtered out by
'VAR__FILTERTYPE__INTERNAL' filter 'Migration-Tsc-Frequency' (correlation
id: null)

On all three nodes I have this kind of running kernel and package versions:

[root@ov300 vdsm]# rpm -q qemu-kvm libvirt-daemon systemd
qemu-kvm-4.2.0-34.module_el8.3.0+555+a55c8938.x86_64
libvirt-daemon-6.0.0-28.module_el8.3.0+555+a55c8938.x86_64
systemd-239-41.el8_3.x86_64

and
[root@ov300 vdsm]# uname -r
4.18.0-240.1.1.el8_3.x86_64
[root@ov300 vdsm]#

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


[ovirt-users] Re: High performance VM cannot migrate due to TSC frequency

2020-12-11 Thread Gianluca Cecchi
On Fri, Dec 11, 2020 at 5:39 PM Milan Zamazal  wrote:

>
>
> TSC frequency is the frequency with which Time Stamp Counter register is
> updated, typically a nominal CPU frequency (see
> https://en.wikipedia.org/wiki/Time_Stamp_Counter for more details).
>
> You can check the value oVirt gets from libvirt by running
>
>   # virsh -r capabilities
>
> and looking at the line like
>
>   
>
> in the output.  Unless frequency scaling is available, the host
> frequencies must be almost the same in order to be able to migrate high
> performance VMs among them.
>
> Note there is a bug that may cause a migration failure for the VMs even
> between hosts with the same frequencies
> (https://bugzilla.redhat.com/1821199).  But this is apparently not your
> case, since the migration is prevented already by Engine.
>
> Regards,
> Milan
>
>
>
See here:

[root@ov200 ~]# virsh -r capabilities | grep "name='tsc'"
  
[root@ov200 ~]#

[root@ov300 ~]# virsh -r capabilities | grep "name='tsc'"
  
[root@ov300 ~]#

[root@ov301 ~]# virsh -r capabilities | grep "name='tsc'"
  
[root@ov301 ~]#

The three hosts have the same model cpu
Model name:  Intel(R) Xeon(R) CPU   X5690  @ 3.47GHz
and slightly different actual frequencies at a certain moment...

But what does it mean so the checkbox

Migrate only to hosts with the same TSC frequency

if even if I don't check it the migration is prevented?

BTW the command lscpu produces exactly the same output on the three hosts,
apart "CPU MHz" and corresponding "BogoMIPS" that slightly change each time
I run the command.

And the flags for all are:

Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl
vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt aes
lahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid
dtherm ida arat flush_l1d

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/2ZCLAOXITG4UT55B5YMOH2G5WVUM4ZBB/


[ovirt-users] High performance VM cannot migrate due to TSC frequency

2020-12-11 Thread Gianluca Cecchi
Hello,
I'm in 4.4.3 and CentOS 8.3 with 3 hosts.

I have a high performance VM that is running on ov300 and is configured to
be run on any host.

It seems that both if I set or not the option

Migrate only to hosts with the same TSC frequency

I always am unable to migrate the VM and inside engine.log I see this:

2020-12-11 15:56:03,424+01 INFO
 [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-36)
[e4801b28-c832-4474-aa53-4ebfd7c6e2d0] Candidate host 'ov301'
('382bfc8f-60d5-4e06-8571-7dae1700574d') was filtered out by
'VAR__FILTERTYPE__INTERNAL' filter 'Migration-Tsc-Frequency' (correlation
id: null)

2020-12-11 15:56:03,424+01 INFO
 [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-36)
[e4801b28-c832-4474-aa53-4ebfd7c6e2d0] Candidate host 'ov200'
('949d0087-2c24-4759-8427-f9eade1dd2cc') was filtered out by
'VAR__FILTERTYPE__INTERNAL' filter 'Migration-Tsc-Frequency' (correlation
id: null)

Can you verify if it is only my problem?

Apart from the problem itself, what is "TSC frequency" and how can I check
if my 3 hosts are different or not indeed?

Normal VMs are able to migrate without problems

Thanks,
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/2HYSCVHSVZS6KX5FF5MOXI6YTLQOJIK7/


[ovirt-users] Re: Nodes in CentOS 8.3 and oVirt 4.4.3.12-1.el8 but not able to update cluster version

2020-12-10 Thread Gianluca Cecchi
On Fri, Dec 11, 2020 at 7:08 AM Alex McWhirter  wrote:

> You have to put all hosts in the cluster to maintenance mode first, then
> you can change the compat version.
>
>
No, it never was this way. You only get a triangle on the VMs icon telling
you that for that VM to aquire the change it needs to be powered off and
then on again.
No full maintenance never required.
See also here:
https://www.ovirt.org/documentation/upgrade_guide/#Changing_the_Cluster_Compatibility_Version_4-2_local_db

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


[ovirt-users] Re: Nodes in CentOS 8.3 and oVirt 4.4.3.12-1.el8 but not able to update cluster version

2020-12-10 Thread Gianluca Cecchi
On Fri, Dec 11, 2020 at 6:39 AM Parth Dhanjal  wrote:

> Hello!
>
> To my knowledge, the latest build is oVirt/RHVH 4.4.3
> So there is no oVirt/RHVH - 4.5 as of now.
>
>
When 4.4.3 was released it was reported several times to the list that also
a 4.5 option for the cluster level had appeared.
And it was answered that this specific version (its logic seemed quite
strange to me indeed) would have been dedicated to linux nodes in RH EL 8.3
or CentOS 8.3 or RHVH/ovirt-node-ng built on top of this version.
Now my 3 nodes are all in CentOS 8.3 but no selection is possible.
I heard Sandro off the list and I think in a short time he or someone else
through the developers will answer more precisely about this.

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


[ovirt-users] Nodes in CentOS 8.3 and oVirt 4.4.3.12-1.el8 but not able to update cluster version

2020-12-10 Thread Gianluca Cecchi
Hello,
my engine is 4.4.3.12-1.el8 and my 3 oVirt nodes (based on plain CentOS due
to megaraid_sas kernel module needed) have been updated, bringing them to
CentOS 8.3.
But if I try to put cluster into 4.5 I get the error:
"
Error while executing action: Cannot change Cluster Compatibility Version
to higher version when there are active Hosts with lower version.
-Please move Host ov300, ov301, ov200 with lower version to maintenance
first.
"
Do I have to wait until final 4.4.4 or what is the problem?
Does 4.5 gives anything more apart the second number... (joking..)?

On nodes:

Software

OS Version: RHEL - 8.3 - 1.2011.el8
OS Description: CentOS Linux 8
Kernel Version: 4.18.0 - 240.1.1.el8_3.x86_64
KVM Version: 4.2.0 - 34.module_el8.3.0+555+a55c8938
LIBVIRT Version: libvirt-6.0.0-28.module_el8.3.0+555+a55c8938
VDSM Version: vdsm-4.40.35.1-1.el8
SPICE Version: 0.14.3 - 3.el8
GlusterFS Version: [N/A]
CEPH Version: librbd1-12.2.7-9.el8
Open vSwitch Version: [N/A]
Nmstate Version: nmstate-0.3.6-2.el8
Kernel Features: MDS: (Vulnerable: Clear CPU buffers attempted, no
microcode; SMT vulnerable), L1TF: (Mitigation: PTE Inversion; VMX:
conditional cache flushes, SMT vulnerable), SRBDS: (Not affected),
MELTDOWN: (Mitigation: PTI), SPECTRE_V1: (Mitigation: usercopy/swapgs
barriers and __user pointer sanitization), SPECTRE_V2: (Mitigation: Full
generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB
filling), ITLB_MULTIHIT: (KVM: Mitigation: Split huge pages),
TSX_ASYNC_ABORT: (Not affected), SPEC_STORE_BYPASS: (Mitigation:
Speculative Store Bypass disabled via prctl and seccomp)
VNC Encryption: Disabled
FIPS mode enabled: Disabled

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


[ovirt-users] Re: How to re-enroll (or renew) host certificates for a single-host hosted-engine deployment?

2020-12-07 Thread Gianluca Cecchi
On Mon, Dec 7, 2020 at 2:22 PM Derek Atkins  wrote:
[snip]

>
> The main advantages of ovirt over virt-manager is the access-control and
> remote-access capabilities.  Specifically, I have several users which have
> different access to different VMs and their consoles.  Without providing
> ssh access to the host, I wasn't sure how to provide that access in a
> clean way via virt-manager.
>
> I *used* to use vmware-server, and kept that running as long as I could
> (on a single server).  But that hardware was running long in the tooth, so
> I migrated to ovirt because it gave me a similar web-based UI interface to
> my users so it was relatively easy to migrate them.  When I migrated 4-5
> years ago, virt-manager was still in relative infancy and, IIRC, didn't
> have much remote capability.
>
>
+1 here.
And I think developers should put more attention in single host
environments than lastly done.
Derek explained very well what could be many common situations to have a
single host environment and the reason not to use virt-manager and such.
At time there was the all-in-one and then it was deprecated/abandoned in
favour of single host deployment.
Now due to perhaps ansible playbook or new logic in host upgrades it seems
to see more and more messages about single host not supported.
In my opinion to do a reinstall every minor update is not feasible.
The free version of ESXi could become a more appealing alternative in the
near future for these kind of usages, with the risk of potentially eating
away also the bigger shape scenario then.
Perhaps to support again the all-in-one effort could be a good approach.

If you think it can get more attention I can open an RFE for revamping
all-in-one or an RFE to provide a mechanism to have an host update itself
through a locally executed playbook and then "acquired" by the SHE in a
second time when exiting global maintenance.
I don't know the internals enough and I have not the coding skills, but I
can support testing the functionality

Thanks for listening
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/IXXAXY7IMAWSL7MSHHZN5JPHFWEI6GPF/


[ovirt-users] Re: Intel Cascade Lake Family supported

2020-11-23 Thread Gianluca Cecchi
On Mon, Nov 23, 2020 at 2:23 PM Ramon Sierra  wrote:

> Hi,
>
> We are planning to upgrade our cluster hardware. We would like to know
> if Intel Cascade Lake CPUs are supported on ovirt 4.4.3. Any
> recommendation is very welcome.
>
> Regards,
>
> Ramon
>
>
I think this could be a good starting point also for oVirt 4.4.x,
confirming your cpu as supported;
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/planning_and_prerequisites_guide/rhv_requirements#CPU_Requirements_RHV_planning

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


[ovirt-users] Re: Best and clean way to have oVirt qemu and libvirt versions on CentOS 8

2020-11-22 Thread Gianluca Cecchi
On Sun, Nov 22, 2020 at 12:16 PM Yedidyah Bar David  wrote:

> On Sun, Nov 22, 2020 at 12:41 PM Gianluca Cecchi
>  wrote:
> >
> > Hello,
> > normally with current CentOS 8.2 I get
> > qemu-kvm-core-15:2.12.0-99.module_el8.2.0+524+f765f7e0.4.x86_64
> > libvirt-daemon-4.5.0-42.module_el8.2.0+320+13f867d7.x86_64
> >
> > With oVirt 4.4 having
> > qemu-kvm-core-4.2.0-29.el8.3.x86_64
> > libvirt-daemon-6.0.0-25.2.el8.x86_64
> >
> > and in current Fedora 32 updates:
> > qemu-kvm-core-4.2.1-1.fc32.x86_64.rpm
> > libvirt-daemon-6.1.0-4.fc32.x86_64.rpm
>
>

> I think the most official/least-intrusive way outside of oVirt is
> something like:
>
> dnf install centos-release-advanced-virtualization
> dnf config-manager --set-enabled centos-advanced-virtualization-test
>

Thanks Didi!
I executed the two commands above and now I have:
qemu-kvm-core-4.2.0-29.el8.6.x86_64
libvirt-daemon-6.0.0-25.2.el8.x86_64

let's do some tests

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


[ovirt-users] Best and clean way to have oVirt qemu and libvirt versions on CentOS 8

2020-11-22 Thread Gianluca Cecchi
Hello,
normally with current CentOS 8.2 I get
qemu-kvm-core-15:2.12.0-99.module_el8.2.0+524+f765f7e0.4.x86_64
libvirt-daemon-4.5.0-42.module_el8.2.0+320+13f867d7.x86_64

With oVirt 4.4 having
qemu-kvm-core-4.2.0-29.el8.3.x86_64
libvirt-daemon-6.0.0-25.2.el8.x86_64

and in current Fedora 32 updates:
qemu-kvm-core-4.2.1-1.fc32.x86_64.rpm
libvirt-daemon-6.1.0-4.fc32.x86_64.rpm

I see on CentOS these groups somehow related to Virtualization:
   Virtualization Host
   Virtualization Client
   Virtualization Hypervisor
   Virtualization Platform
   Virtualization Tools

What could be the best and less intrusive repo to enable on plain CentOS
8.2 to get qemu-kvm and libvirt versions quite similar to oVirt shipped
ones, or fedora ones, without enabling all  the ovirt 4.4 repos?

Thanks,
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/NKEVOBLSRFLQEILECD2ERFXVPK7LLMG7/


[ovirt-users] Re: Hosted Engine can't migrate

2020-11-18 Thread Gianluca Cecchi
On Wed, Nov 18, 2020 at 7:08 AM McNamara, Bradley <
bradley.mcnam...@seattle.gov> wrote:

> I'm new to oVirt, but not new to virtualization technologies.  I've run
> into a wall, but the solution has gotta be simple.  I've seen other threads
> with the same issue, but a solution is never posted.
>
> I've followed the guide perfectly.  I get  the self-hosted engine up and
> running with no issues.  I add hosts to the cluster, but it won't let me
> migrate the HE because of Hosted Engine HA score of "N/A" on every host
> except the one it was initially deployed on.  The physical servers are
> exactly the same:  same networks, storage, OS, patches, etc.  The
> additional hosts are added thru the HE GUI and are added without issue.  Is
> there a secret button I gotta push?
>
> What am I missing?  This is with 4.3 on CentOS 7.9.
>
> HELP!  Thanks.  :-)
>

If you go in Compute --> Hosts in web admin gui, do the added hosts have a
crown icon on the left of their "Name" column?
If not, when you added them possibly you overlooked the "Hosted Engine"
section in the window, where by default, if I'm not wrong, the value is
"None": that means that the added host doesn't contributed to be one of the
"Hosted Engine" ones electable to host the engine VM, but only an
hyoervisor.

Long time ago I opened two bugzillas about this default with some notes for
improving a better experience
If this is the case, you can remove the hosts one by one and add them again
selecting "Deploy" in the Hosted Engine section, for how many you would
like to contribute to the score and to be able to host the hosted engine VM.

HIH,
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/VQJO2A7DHR5AIXSM3GXNB6PFSMPILHUZ/


[ovirt-users] Re: Upgrading engine from 4.3 -> 4.4

2020-11-17 Thread Gianluca Cecchi
On Tue, Nov 17, 2020 at 6:41 PM David Metcalf 
wrote:

> Followed this for standalone hosts:
> https://ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3
>
> but get this message..
>
> engine-backup --mode=restore --file=engine-backup-2020-11-16.bak
> --provision-all-databases
> ...
> FATAL: Backup was created by version '4.3.9.4' and can not be restored
> using the installed version 4.4.3.11
>
>
In another recent thread already replied that you need to be at latest 4.3
that for oVirt is 4.3.10.
So, in particular, the backup has to be taken while in 4.3.10.

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/5AK4EQ77PGCOAP6EWDAJSBUJEDPAT5CY/


[ovirt-users] Re: oVirt 4.4 vnic profile to substitute vdsm mac spoof hook

2020-11-15 Thread Gianluca Cecchi
It seems that the "No Network Filter" filter makes it and now my overcloud
node correctly gets the ip

Nov 15 18:25:15 director dnsmasq-dhcp[3453]: DHCPDISCOVER(tap9fdd5920-62)
172.23.0.232 56:6f:3d:48:00:3c
Nov 15 18:25:15 director dnsmasq-dhcp[1517]: 3907474188 available DHCP
range: 172.23.0.241 -- 172.23.0.251
Nov 15 18:25:15 director dnsmasq-dhcp[3453]: DHCPOFFER(tap9fdd5920-62)
172.23.0.232 56:6f:3d:48:00:3c
Nov 15 18:25:15 director dnsmasq-dhcp[1517]: 3907474188 client provides
name: ostack-ceph0
Nov 15 18:25:15 director dnsmasq-dhcp[1517]: 3907474188
DHCPDISCOVER(br-ctlplane) 56:6f:3d:48:00:3c ignored
Nov 15 18:25:15 director dnsmasq-dhcp[1517]: 3907474188 available DHCP
range: 172.23.0.241 -- 172.23.0.251
Nov 15 18:25:15 director dnsmasq-dhcp[1517]: 3907474188 client provides
name: ostack-ceph0
Nov 15 18:25:15 director dnsmasq-dhcp[3453]: DHCPREQUEST(tap9fdd5920-62)
172.23.0.232 56:6f:3d:48:00:3c
Nov 15 18:25:15 director dnsmasq-dhcp[3453]: DHCPACK(tap9fdd5920-62)
172.23.0.232 56:6f:3d:48:00:3c host-172-23-0-232

For clarity it is also to be said that after the upgrade of oVirt and the
import of the storage domain where the VM lived before, the network
interfaces resulted swapped.
So at begin I exchanged vlan assignment for the vnics to have correct
behaviour / binding of names.
Only thing I also missed is that the definition of ifcg-br-ctlplane was

[root@director ~]# cat /etc/sysconfig/network-scripts/ifcfg-br-ctlplane
# This file is autogenerated by os-net-config
DEVICE=br-ctlplane
ONBOOT=yes
HOTPLUG=no
NM_CONTROLLED=no
PEERDNS=no
DEVICETYPE=ovs
TYPE=OVSBridge
MTU=1500
BOOTPROTO=static
IPADDR=172.23.0.220
NETMASK=255.255.255.0
OVS_EXTRA="set bridge br-ctlplane other-config:hwaddr=56:6f:3d:48:00:14 --
br-set-external-id br-ctlplane bridge-id br-ctlplane -- set bridge
br-ctlplane fail_mode=standalone -- del-controller br-ctlplane -- set
bridge br-ctlplane fail_mode=standalone -- del-controller br-ctlplane"
[root@director ~]#

And so I had also to change other-config:hwaddr=56:6f:3d:48:00:14 in
other-config:hwaddr=56:6f:3d:48:00:13 due to the new mac of the eth1
interface being 56:6f:3d:48:00:13
In fact in my first post you can see the macs not matching

[root@director ~]# ovs-ofctl show br-ctlplane
. . .
 1(eth1): addr:56:6f:3d:48:00:13
 config: 0
 state:  0
 speed: 0 Mbps now, 0 Mbps max
 . . .
 LOCAL(br-ctlplane): addr:56:6f:3d:48:00:14
 config: 0
 state:  0
 speed: 0 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0
 [root@director ~]#

So after having the correct mac and using "No Network Filter" filter, all
seems as before with VDSM MAC Spoof hook.
I'm not sure if there is a less open filter accomplishing my needs...

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


[ovirt-users] Re: oVirt 4.4 vnic profile to substitute vdsm mac spoof hook

2020-11-15 Thread Gianluca Cecchi
On Sun, Nov 15, 2020 at 1:15 AM Gianluca Cecchi 
wrote:

> Hello,
> I have an Openstack Queens environment that is composed by VMs inside
> oVirt.
> Initially this oVirt environment was on 4.3 and on director I had to set
> vdsm mac spoof to be able to give dhcp address to the overcloud nodes.
> I tried something at that time with vnic profiles but I was not able to
> have it work as expected, so I used the hook.
> Now I have migrated this same environment to 4.4.2 and I see that vdsm mac
> spoof is no more an option:
> https://bugzilla.redhat.com/show_bug.cgi?id=1703840
>
> I tried some combinations of vnic profiles on director vnic but it seems
> not to work as a dhcpserver as before.
> I see DHCPDISCOVER from overcloud node in director messages (while before
> I saw DHCPREQUEST), I see the DHCPOFFER from director, but I don't see the
> DHCPACK from the overcloud node...
>
>
The vnic that should give dhcp address is vlan23
If I shutdown all VMs and set vnic profile with Network Filter
"clean-traffic" and run the VM, the xml of the director VM is of this type:

. . .

vlan19

4



vlan23

4


. . .

  
  
  
  
  
  
  
  
  
  


  
  
  
  
  
  
  
  
  
  

. . .
___
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/O25XU5WLZQYZC36DBISM5FEPPQ3I3UST/


[ovirt-users] oVirt 4.4 vnic profile to substitute vdsm mac spoof hook

2020-11-14 Thread Gianluca Cecchi
Hello,
I have an Openstack Queens environment that is composed by VMs inside oVirt.
Initially this oVirt environment was on 4.3 and on director I had to set
vdsm mac spoof to be able to give dhcp address to the overcloud nodes.
I tried something at that time with vnic profiles but I was not able to
have it work as expected, so I used the hook.
Now I have migrated this same environment to 4.4.2 and I see that vdsm mac
spoof is no more an option:
https://bugzilla.redhat.com/show_bug.cgi?id=1703840

I tried some combinations of vnic profiles on director vnic but it seems
not to work as a dhcpserver as before.
I see DHCPDISCOVER from overcloud node in director messages (while before I
saw DHCPREQUEST), I see the DHCPOFFER from director, but I don't see the
DHCPACK from the overcloud node...

On director I have the br-ctlplane vswitch using its interface eth1:

ovs-vsctl show
. . .
Bridge br-ctlplane
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port br-ctlplane
Interface br-ctlplane
type: internal
Port "eth1"
Interface "eth1"
Port phy-br-ctlplane
Interface phy-br-ctlplane
type: patch
options: {peer=int-br-ctlplane}
ovs_version: "2.11.0"

 [root@director ~]# ovs-ofctl show br-ctlplane
OFPT_FEATURES_REPLY (xid=0x2): dpid:566f3d480014
n_tables:254, n_buffers:0
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src
mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst
 1(eth1): addr:56:6f:3d:48:00:13
 config: 0
 state:  0
 speed: 0 Mbps now, 0 Mbps max
 2(phy-br-ctlplane): addr:76:76:8b:08:d4:2f
 config: 0
 state:  0
 speed: 0 Mbps now, 0 Mbps max
 LOCAL(br-ctlplane): addr:56:6f:3d:48:00:14
 config: 0
 state:  0
 speed: 0 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0
 [root@director ~]#

 [root@director ~]# ip addr show dev br-ctlplane
6: br-ctlplane:  mtu 1500 qdisc noqueue
state UNKNOWN group default qlen 1000
link/ether 56:6f:3d:48:00:14 brd ff:ff:ff:ff:ff:ff
inet 172.23.0.220/24 brd 172.23.0.255 scope global br-ctlplane
   valid_lft forever preferred_lft forever
inet 172.23.0.222/32 scope global br-ctlplane
   valid_lft forever preferred_lft forever
inet 172.23.0.221/32 scope global br-ctlplane
   valid_lft forever preferred_lft forever
inet6 fe80::546f:3dff:fe48:14/64 scope link
   valid_lft forever preferred_lft forever
 [root@director ~]#

The eth1 interface is configured in oVirt on vlan23.
The overcloud nodes have one vnic on vlan 23.

I have two dnsmasq processes on director, for ironic and for overcloud
nodes:

nobody1527 1  0 Nov14 ?00:00:00 /sbin/dnsmasq
--conf-file=/etc/ironic-inspector/dnsmasq.conf
nobody3288 1  0 Nov14 ?00:00:00 dnsmasq --no-hosts
--no-resolv
--pid-file=/var/lib/neutron/dhcp/22a5739b-acb6-4400-8247-080a66895f1a/pid
--dhcp-hostsfile=/var/lib/neutron/dhcp/22a5739b-acb6-4400-8247-080a66895f1a/host
--addn-hosts=/var/lib/neutron/dhcp/22a5739b-acb6-4400-8247-080a66895f1a/addn_hosts
--dhcp-optsfile=/var/lib/neutron/dhcp/22a5739b-acb6-4400-8247-080a66895f1a/opts
--dhcp-leasefile=/var/lib/neutron/dhcp/22a5739b-acb6-4400-8247-080a66895f1a/leases
--dhcp-match=set:ipxe,175 --local-service --bind-dynamic
--dhcp-range=set:subnet-d48e002b-f269-4ed5-a96e-9aeba0b119b9,172.23.0.0,static,255.255.255.0,86400s
--dhcp-option-force=option:mtu,1500 --dhcp-lease-max=256
--conf-file=/etc/dnsmasq-ironic.conf --domain=localdomain

In messages of director when booting the overcloud node:

Nov 15 00:42:45 director dnsmasq-dhcp[3288]: DHCPDISCOVER(tap9fdd5920-62)
172.23.0.232 56:6f:3d:48:00:3c
Nov 15 00:42:45 director dnsmasq-dhcp[1527]: 3792136019
DHCPDISCOVER(br-ctlplane) 56:6f:3d:48:00:3c ignored
Nov 15 00:42:45 director dnsmasq-dhcp[3288]: DHCPOFFER(tap9fdd5920-62)
172.23.0.232 56:6f:3d:48:00:3c
Nov 15 00:42:45 director dnsmasq-dhcp[3288]: DHCPOFFER(tap9fdd5920-62)
172.23.0.232 56:6f:3d:48:00:3c

In oVirt 4.3 with the same setup and VDSM MAC spoof hook configured I saw
this inside messages of director when booting the overcloud nodes:

Oct 18 04:50:05 director dnsmasq-dhcp[3230]: DHCPREQUEST(tap9fdd5920-62)
172.23.0.232 56:6f:3d:48:00:3c
Oct 18 04:50:05 director dnsmasq-dhcp[3230]: DHCPACK(tap9fdd5920-62)
172.23.0.232 56:6f:3d:48:00:3c host-172-23-0-232

Questions:
what is the filter to give to have it work?
is it dynamic the effect at runtime for a running VM to edit its vnic and
change its profile?
is it dynamic for running VMs that for a vNIC with a certain profile if I
go in Networks --> vNIC Profiles --> Edit vNIC Profile and change its
network filter value?

Thanks for any insight.

Gianluca
___
Users mailing list -- 

[ovirt-users] Re: Fail to upgrade cluster from 4.3 to 4.4

2020-11-13 Thread Gianluca Cecchi
On Fri, Nov 13, 2020 at 6:33 PM Gianluca Cecchi 
wrote:

> Hello,
> my environment was oVirt 4.3.10 with an external engine and 3 hosts.
> I have updated to 4.4.3 the whole infra, but know if I go and update the
> cluster to 4.4 I get the message in this window:
>
> https://drive.google.com/file/d/1hfs4FC8uZ-EjiCzQyitA3945U0Knnz2m/view?usp=sharing
>
> What is the reason for it?
>
> My Cluster is with Cluster CPU Type: "Intel Westmere IBRS SSBD Family"
>
> The signalled 'hostmaster' VM is a powered off VM used in the past to test
> nested virtualization and in "Virtual Machines" page aside it I see an
> exclamation mark with "The VM CPU doesn't match the Cluster Cpu Type"
>
> The VM is set as custom, optimized for Server
> Custom Chipset/Firmware Type "Cluster default (i440FX Chipset with BIOS)"
> Custom Emulated Machine (in grey): "Cluster default(pc-i440fx-rhel7.6.0)"
> Custom CPU (in grey): "Cluster default(Intel Westmere IBRS SSBD Family)"
>
> What I'm expected to change?
>
> Thanks,
> Gianluca
>
>
there is another field in System, Advanced Parameters (of cpu); this field
is "Custom Compatibility Version", but for all my VMs it is blank, also for
the "problematic one
___
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/LCERG3NPHIX57AMVHPQCPMDPB4AR6ZO3/


[ovirt-users] Fail to upgrade cluster from 4.3 to 4.4

2020-11-13 Thread Gianluca Cecchi
Hello,
my environment was oVirt 4.3.10 with an external engine and 3 hosts.
I have updated to 4.4.3 the whole infra, but know if I go and update the
cluster to 4.4 I get the message in this window:
https://drive.google.com/file/d/1hfs4FC8uZ-EjiCzQyitA3945U0Knnz2m/view?usp=sharing

What is the reason for it?

My Cluster is with Cluster CPU Type: "Intel Westmere IBRS SSBD Family"

The signalled 'hostmaster' VM is a powered off VM used in the past to test
nested virtualization and in "Virtual Machines" page aside it I see an
exclamation mark with "The VM CPU doesn't match the Cluster Cpu Type"

The VM is set as custom, optimized for Server
Custom Chipset/Firmware Type "Cluster default (i440FX Chipset with BIOS)"
Custom Emulated Machine (in grey): "Cluster default(pc-i440fx-rhel7.6.0)"
Custom CPU (in grey): "Cluster default(Intel Westmere IBRS SSBD Family)"

What I'm expected to change?

Thanks,
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/RZUC5V3X72APFSLJQN5DGAXAM4IRHSKS/


[ovirt-users] Re: Unable to live migrate a VM from 4.4.2 to 4.4.3 CentOS Linux host

2020-11-12 Thread Gianluca Cecchi
On Thu, Nov 12, 2020 at 11:08 AM Gianluca Cecchi 
wrote:

> On Wed, Nov 11, 2020 at 10:01 PM Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>>
>> NOTE: this was a cluster in 4.3.10 and I updated it to 4.4.2 and I
>> noticed that the OVN config was not retained and I had to run on hosts:
>>
>> [root@ov200 ~]# vdsm-tool ovn-config engine_ip ov200_ip_on_mgmt
>> Using default PKI files
>> Created symlink
>> /etc/systemd/system/multi-user.target.wants/openvswitch.service →
>> /usr/lib/systemd/system/openvswitch.service.
>> Created symlink
>> /etc/systemd/system/multi-user.target.wants/ovn-controller.service →
>> /usr/lib/systemd/system/ovn-controller.service.
>> [root@ov200 ~]#
>>
>> Now it seems the problem persists...
>> Why do I have to run each time?
>>
>> Gianluca
>>
>
> In the mean time I confirm that the manual step below on ov301 let me saw
> it again between the chassis of OVN southbound on engine and I was able to
> migrate VMs to update the other host and then for example to successfully
> ping between VMs on OVN across the two hosts:
>
> [root@ov301 vdsm]# vdsm-tool ovn-config 10.4.192.43 10.4.192.34
> Using default PKI files
> Created symlink
> /etc/systemd/system/multi-user.target.wants/openvswitch.service →
> /usr/lib/systemd/system/openvswitch.service.
> Created symlink
> /etc/systemd/system/multi-user.target.wants/ovn-controller.service →
> /usr/lib/systemd/system/ovn-controller.service.
> [root@ov301 vdsm]#
>
>
>
One further update.
On the other 4.4.2 host I applied the now recommended approach of updating
from web admin gui, after putting the host into maintenenace:
Hosts --> Select Host --> Installation --> Upgrade

I deselected the reboot host and the update completed successfully.
Then I manually rebooted the host from web admin gui:
Management --> SSH Management --> Restart
At reboot all is ok and I still see the host as one of the southbound
chassis

I can activate the host (why at least 10 popups with the same message
"Finished Activating Host ov200"???)

If I compare with diff the packages installed on the two hosts I see:

< = ov200 (the one from web admin gui)
> = ov301 (updated through dnf update)

19c19
< ansible-2.9.14-1.el8.noarch
---
> ansible-2.9.15-2.el8.noarch
262d261
< gpg-pubkey-56863776-5f117571
658c657
< NetworkManager-1.26.2-1.el8.x86_64
---
> NetworkManager-1.22.14-1.el8.x86_64
660,663c659,662
< NetworkManager-libnm-1.26.2-1.el8.x86_64
< NetworkManager-ovs-1.26.2-1.el8.x86_64
< NetworkManager-team-1.26.2-1.el8.x86_64
< NetworkManager-tui-1.26.2-1.el8.x86_64
---
> NetworkManager-libnm-1.22.14-1.el8.x86_64
> NetworkManager-ovs-1.22.14-1.el8.x86_64
> NetworkManager-team-1.22.14-1.el8.x86_64
> NetworkManager-tui-1.22.14-1.el8.x86_64
1079d1077
< yum-utils-4.0.12-4.el8_2.noarch

any comments?

On the host updated through the web admin gui, if I run dnf update I 'm
proposed with:

Dependencies resolved.
==
 PackageArch   Version Repository
 Size
==
Upgrading:
 NetworkManager-config-server
noarch 1:1.26.2-1.el8
 ovirt-4.4-copr:copr.fedorainfracloud.org:networkmanager:NetworkManager-1.26

117 k
 ansiblenoarch 2.9.15-2.el8ovirt-4.4-centos-ovirt44
 17 M
 nmstatenoarch 0.3.6-2.el8
ovirt-4.4-copr:copr.fedorainfracloud.org:nmstate:nmstate-0.3  34 k
 python3-libnmstate noarch 0.3.6-2.el8
ovirt-4.4-copr:copr.fedorainfracloud.org:nmstate:nmstate-0.3 178 k
Installing dependencies:
 python3-varlinknoarch 29.0.0-1.el8BaseOS
 49 k

Transaction Summary
==
Install  1 Package
Upgrade  4 Packages

Total download size: 18 M

Why ansible has not been updated?
Probably on CentOS lInux plain host I shouldn't run at all any "dnf update"
command? Or what is a clear statement for managing plain CentOS Linux hosts
in 4.4?
In case couldn't be put in place sort of global version lock to prevent
"dnf update" commands?

Thanks,
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/4XSGICBJOUDQZWMPBVGNTPEODJ6BE2DB/


[ovirt-users] Re: Unable to live migrate a VM from 4.4.2 to 4.4.3 CentOS Linux host

2020-11-12 Thread Gianluca Cecchi
On Wed, Nov 11, 2020 at 10:01 PM Gianluca Cecchi 
wrote:

>
> NOTE: this was a cluster in 4.3.10 and I updated it to 4.4.2 and I noticed
> that the OVN config was not retained and I had to run on hosts:
>
> [root@ov200 ~]# vdsm-tool ovn-config engine_ip ov200_ip_on_mgmt
> Using default PKI files
> Created symlink
> /etc/systemd/system/multi-user.target.wants/openvswitch.service →
> /usr/lib/systemd/system/openvswitch.service.
> Created symlink
> /etc/systemd/system/multi-user.target.wants/ovn-controller.service →
> /usr/lib/systemd/system/ovn-controller.service.
> [root@ov200 ~]#
>
> Now it seems the problem persists...
> Why do I have to run each time?
>
> Gianluca
>

In the mean time I confirm that the manual step below on ov301 let me saw
it again between the chassis of OVN southbound on engine and I was able to
migrate VMs to update the other host and then for example to successfully
ping between VMs on OVN across the two hosts:

[root@ov301 vdsm]# vdsm-tool ovn-config 10.4.192.43 10.4.192.34
Using default PKI files
Created symlink
/etc/systemd/system/multi-user.target.wants/openvswitch.service →
/usr/lib/systemd/system/openvswitch.service.
Created symlink
/etc/systemd/system/multi-user.target.wants/ovn-controller.service →
/usr/lib/systemd/system/ovn-controller.service.
[root@ov301 vdsm]#
___
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/4QQ2KG7O3DLNL52P6JNJLJTN7UAJS2BL/


[ovirt-users] Unable to live migrate a VM from 4.4.2 to 4.4.3 CentOS Linux host

2020-11-11 Thread Gianluca Cecchi
Hello,
I was able to update an external CentOS Linux 8.2 standalone engine from
4.4.2 to 4.4.3 (see dedicated thread).
Then I was able to put into maintenance one 4.4.2 host (CentOS Linux 8.2
based, not ovirt node ng) and run:

[root@ov301 ~]# dnf update
Last metadata expiration check: 0:27:11 ago on Wed 11 Nov 2020 08:48:04 PM
CET.
Dependencies resolved.
==
 Package   Arch   Version
 RepositorySize
==
Installing:
 kernelx86_64 4.18.0-193.28.1.el8_2
 BaseOS   2.8 M
 kernel-core   x86_64 4.18.0-193.28.1.el8_2
 BaseOS28 M
 kernel-modulesx86_64 4.18.0-193.28.1.el8_2
 BaseOS23 M
 ovirt-ansible-collection  noarch 1.2.1-1.el8
 ovirt-4.4276 k
 replacing  ovirt-ansible-engine-setup.noarch 1.2.4-1.el8
 replacing  ovirt-ansible-hosted-engine-setup.noarch 1.1.8-1.el8
Upgrading:
 ansible   noarch 2.9.15-2.el8
ovirt-4.4-centos-ovirt44  17 M
 bpftool   x86_64 4.18.0-193.28.1.el8_2
 BaseOS   3.4 M
 cockpit-ovirt-dashboard   noarch 0.14.13-1.el8
 ovirt-4.43.5 M
 ioprocess x86_64 1.4.2-1.el8
 ovirt-4.4 37 k
 kernel-tools  x86_64 4.18.0-193.28.1.el8_2
 BaseOS   3.0 M
 kernel-tools-libs x86_64 4.18.0-193.28.1.el8_2
 BaseOS   2.8 M
 libiscsi  x86_64 1.18.0-8.module_el8.2.0+524+f765f7e0
AppStream 89 k
 nftables  x86_64 1:0.9.3-12.el8_2.1
BaseOS   311 k
 ovirt-hosted-engine-hanoarch 2.4.5-1.el8
 ovirt-4.4325 k
 ovirt-hosted-engine-setup noarch 2.4.8-1.el8
 ovirt-4.4227 k
 ovirt-imageio-client  x86_64 2.1.1-1.el8
 ovirt-4.4 21 k
 ovirt-imageio-common  x86_64 2.1.1-1.el8
 ovirt-4.4155 k
 ovirt-imageio-daemon  x86_64 2.1.1-1.el8
 ovirt-4.4 15 k
 ovirt-provider-ovn-driver noarch 1.2.32-1.el8
ovirt-4.4 27 k
 ovirt-release44   noarch 4.4.3-1.el8
 ovirt-4.4 17 k
 python3-ioprocess x86_64 1.4.2-1.el8
 ovirt-4.4 33 k
 python3-nftables  x86_64 1:0.9.3-12.el8_2.1
BaseOS25 k
 python3-ovirt-engine-sdk4 x86_64 4.4.6-1.el8
 ovirt-4.4560 k
 python3-perf  x86_64 4.18.0-193.28.1.el8_2
 BaseOS   2.9 M
 python3-pyasn1noarch 0.4.6-3.el8
 ovirt-4.4-centos-opstools140 k
 python3-pyasn1-modulesnoarch 0.4.6-3.el8
 ovirt-4.4-centos-opstools151 k
 qemu-img  x86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization1.0 M
 qemu-kvm  x86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization118 k
 qemu-kvm-block-curl   x86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization129 k
 qemu-kvm-block-glusterx86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization131 k
 qemu-kvm-block-iscsi  x86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization136 k
 qemu-kvm-block-rbdx86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization130 k
 qemu-kvm-block-sshx86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization131 k
 qemu-kvm-common   x86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization1.2 M
 qemu-kvm-core x86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization3.4 M
 selinux-policynoarch 3.14.3-41.el8_2.8
 BaseOS   615 k
 selinux-policy-targeted   noarch 3.14.3-41.el8_2.8
 BaseOS15 M
 spice-server  x86_64 0.14.2-1.el8_2.1
AppStream404 k
 tzdatanoarch 2020d-1.el8
 BaseOS   471 k
 vdsm  x86_64 4.40.35.1-1.el8
 ovirt-4.41.4 M
 vdsm-api  noarch 4.40.35.1-1.el8
 ovirt-4.4106 k
 vdsm-client   noarch 4.40.35.1-1.el8
 ovirt-4.4 24 k
 vdsm-common   noarch 4.40.35.1-1.el8
 ovirt-4.4136 k
 

[ovirt-users] Re: Dependencies failure when upgrading from version 4.4.2 to 4.4.3

2020-11-11 Thread Gianluca Cecchi
On Wed, Nov 11, 2020 at 9:07 PM  wrote:

> Hi Martin.
>
> Sorry my english...
>
> So... the engine was updated successfully. I had already executed the
> commands and procedures you wrote below, but even so, the host fails to
> update.
>
>
Just as a complimentary follow up, I was able to update a CentOS Linux 8.2
from 4.4.2 to 4.4.3.

Here below the output.
After rebooting the host it seems I'm not able then to migrate VMs from a
4.4.2 host to it, but for this problem I'm going to open a new thread.



root@ov301 ~]# dnf update
Last metadata expiration check: 0:27:11 ago on Wed 11 Nov 2020 08:48:04 PM
CET.
Dependencies resolved.
==
 Package   Arch   Version
 RepositorySize
==
Installing:
 kernelx86_64 4.18.0-193.28.1.el8_2
 BaseOS   2.8 M
 kernel-core   x86_64 4.18.0-193.28.1.el8_2
 BaseOS28 M
 kernel-modulesx86_64 4.18.0-193.28.1.el8_2
 BaseOS23 M
 ovirt-ansible-collection  noarch 1.2.1-1.el8
 ovirt-4.4276 k
 replacing  ovirt-ansible-engine-setup.noarch 1.2.4-1.el8
 replacing  ovirt-ansible-hosted-engine-setup.noarch 1.1.8-1.el8
Upgrading:
 ansible   noarch 2.9.15-2.el8
ovirt-4.4-centos-ovirt44  17 M
 bpftool   x86_64 4.18.0-193.28.1.el8_2
 BaseOS   3.4 M
 cockpit-ovirt-dashboard   noarch 0.14.13-1.el8
 ovirt-4.43.5 M
 ioprocess x86_64 1.4.2-1.el8
 ovirt-4.4 37 k
 kernel-tools  x86_64 4.18.0-193.28.1.el8_2
 BaseOS   3.0 M
 kernel-tools-libs x86_64 4.18.0-193.28.1.el8_2
 BaseOS   2.8 M
 libiscsi  x86_64 1.18.0-8.module_el8.2.0+524+f765f7e0
AppStream 89 k
 nftables  x86_64 1:0.9.3-12.el8_2.1
BaseOS   311 k
 ovirt-hosted-engine-hanoarch 2.4.5-1.el8
 ovirt-4.4325 k
 ovirt-hosted-engine-setup noarch 2.4.8-1.el8
 ovirt-4.4227 k
 ovirt-imageio-client  x86_64 2.1.1-1.el8
 ovirt-4.4 21 k
 ovirt-imageio-common  x86_64 2.1.1-1.el8
 ovirt-4.4155 k
 ovirt-imageio-daemon  x86_64 2.1.1-1.el8
 ovirt-4.4 15 k
 ovirt-provider-ovn-driver noarch 1.2.32-1.el8
ovirt-4.4 27 k
 ovirt-release44   noarch 4.4.3-1.el8
 ovirt-4.4 17 k
 python3-ioprocess x86_64 1.4.2-1.el8
 ovirt-4.4 33 k
 python3-nftables  x86_64 1:0.9.3-12.el8_2.1
BaseOS25 k
 python3-ovirt-engine-sdk4 x86_64 4.4.6-1.el8
 ovirt-4.4560 k
 python3-perf  x86_64 4.18.0-193.28.1.el8_2
 BaseOS   2.9 M
 python3-pyasn1noarch 0.4.6-3.el8
 ovirt-4.4-centos-opstools140 k
 python3-pyasn1-modulesnoarch 0.4.6-3.el8
 ovirt-4.4-centos-opstools151 k
 qemu-img  x86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization1.0 M
 qemu-kvm  x86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization118 k
 qemu-kvm-block-curl   x86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization129 k
 qemu-kvm-block-glusterx86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization131 k
 qemu-kvm-block-iscsi  x86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization136 k
 qemu-kvm-block-rbdx86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization130 k
 qemu-kvm-block-sshx86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization131 k
 qemu-kvm-common   x86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization1.2 M
 qemu-kvm-core x86_64 15:4.2.0-29.el8.6
 ovirt-4.4-advanced-virtualization3.4 M
 selinux-policynoarch 3.14.3-41.el8_2.8
 BaseOS   615 k
 selinux-policy-targeted   noarch 3.14.3-41.el8_2.8
 BaseOS15 M
 spice-server  x86_64 0.14.2-1.el8_2.1
AppStream404 k
 tzdatanoarch 2020d-1.el8
 BaseOS   471 k
 vdsm  x86_64 4.40.35.1-1.el8
 ovirt-4.41.4 M
 vdsm-api  

[ovirt-users] Re: Engine update error from 4.4.2 to 4.4.3

2020-11-11 Thread Gianluca Cecchi
On Wed, Nov 11, 2020 at 8:13 PM Martin Perina  wrote:

> Hi,
> Could you please try to upgrade from 4.4.2 to 4.4.3 using below steps:
>
>   # dnf update ovirt\*setup\* --nobest
>   # engine-setup
>   # dnf update --nobest
>   # reboot
>
> Thanks,
> Martin
>
>
Hi,
it was successful and I updated the opened bugzilla with comments and
generated output

Thanks for the moment
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/ADSHGRQCN6JNGFEWMDSYM3M32WM27A4F/


[ovirt-users] Re: Engine update error from 4.4.2 to 4.4.3

2020-11-11 Thread Gianluca Cecchi
On Wed, Nov 11, 2020 at 4:12 PM shadow emy  wrote:

> Hello
>
> I have updated only the engine first using bellow command and could
> proceed with the update.
>
> dnf update ovirt-engine-setup ovirt-engine-setup-plugin-websocket-proxy
> ovirt-engine-dwh-setup ovirt-engine-dwh-grafana-integration-setup
>
> engine-setup
>
>
> "  yum update ovirt\*setup\* "   --  did not work and had the same error
> as you
>
>
Thanks for the info.
Were you then able to run "yum update" on engine without dependency errors?

Can you please add the info into the bugzilla link I provided for this,
thanks

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


[ovirt-users] Re: Engine update error from 4.4.2 to 4.4.3

2020-11-11 Thread Gianluca Cecchi
On Wed, Nov 11, 2020 at 3:35 PM Gianluca Cecchi 
wrote:

> No problem, Martin.
> Actually after so many RCs I remained sort of stumbled too... but possibly
> a last minute change on some repos without deeply considering impacts...
> Tell me which component: ovirt-engine? And if so what component type? I'm
> already inside the bugzilla form page ;-)
>
> Gianluca
>
> (sorry Martin for duplication)
>
> On Wed, Nov 11, 2020 at 3:29 PM Martin Perina  wrote:
>
>> Hi Gianluca,
>>
>> could you please file a bug for that? No idea how we could miss such a
>> blocker :-(
>>
>> Thanks,
>> Martin
>>
>>
>>

Bug opened:
https://bugzilla.redhat.com/show_bug.cgi?id=1896799
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/J33QCKWDN6APGWP7IR3CZVBTYIFF64X2/


[ovirt-users] Re: Engine update error from 4.4.2 to 4.4.3

2020-11-11 Thread Gianluca Cecchi
No problem, Martin.
Actually after so many RCs I remained sort of stumbled too... but possibly
a last minute change on some repos without deeply considering impacts...
Tell me which component: ovirt-engine? And if so what component type? I'm
already inside the bugzilla form page ;-)

Gianluca

(sorry Martin for duplication)

On Wed, Nov 11, 2020 at 3:29 PM Martin Perina  wrote:

> Hi Gianluca,
>
> could you please file a bug for that? No idea how we could miss such a
> blocker :-(
>
> Thanks,
> Martin
>
>
> On Wed, Nov 11, 2020 at 2:46 PM Gianluca Cecchi 
> wrote:
>
>> On Wed, Nov 11, 2020 at 2:02 PM Gilboa Davara  wrote:
>> [snip]
>>
>>
>>> $ yum update ovirt\*setup\*
>>> Last metadata expiration check: 1:50:00 ago on Wed 11 Nov 2020 01:03:00
>>> PM IST.
>>>
>>>
>> ??
>> Does it mean you too or what?
>> Please, words are (still) free so you can use some more... ;-)
>>
>> 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/P433UJQSTT3X2R7AG3SM345XY2WXE6VN/
>>
>
>
> --
> Martin Perina
> Manager, Software Engineering
> Red Hat Czech s.r.o.
>
___
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/JGTTLOKPLLIEMSNAZP57VS6TFOGNYDC4/


[ovirt-users] Re: Engine update error from 4.4.2 to 4.4.3

2020-11-11 Thread Gianluca Cecchi
On Wed, Nov 11, 2020 at 2:02 PM Gilboa Davara  wrote:
[snip]


> $ yum update ovirt\*setup\*
> Last metadata expiration check: 1:50:00 ago on Wed 11 Nov 2020 01:03:00 PM
> IST.
>
>
??
Does it mean you too or what?
Please, words are (still) free so you can use some more... ;-)

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


[ovirt-users] Re: Deploy oVirt Engine fail behind proxy

2020-11-11 Thread Gianluca Cecchi
On Wed, Nov 11, 2020 at 11:05 AM Yedidyah Bar David  wrote:

[snip]

> One suggestion for who will have the same problem:
> > This file was created by the first failed run of the deploy.
> > Without run the deploy, this file does not exists.
> > So you have to run the deploy one time, let it fail and then edit the
> file.
> > I know that it seems a stupid suggestion but i think could help someone.
>
> It's not stupid! :-). I think you unknowingly ran into something
> caused by the move to ovirt-ansible-roles in 4.4.3 [1].
>
> Until 4.4.2, this file was in the package ovirt-ansible-engine-setup , in:
>
> /usr/share/ansible/roles/ovirt.engine-setup/tasks/install_packages.yml
>
> In 4.4.3, this file, along with many others (including hosted-engine
> ansible code), is in ovirt-ansible-collection, in:
>
>
> /usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/install_packages.yml
>

Uhm...
Can this be related in any way with my dependency problems updating engine
from 4.4.2 to 4.4.3, as described in the thread just opened here:
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/JEZZ5CMFM4EFKT3637BZZDBRJCQYVFRH/

?

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


[ovirt-users] Engine update error from 4.4.2 to 4.4.3

2020-11-11 Thread Gianluca Cecchi
Hello,
is this still the correct command during updates through minor releases in
4.4.x?

yum update ovirt\*setup\*

Because my standalone external engine is now at level
ovirt-engine-4.4.2.6-1.el8.noarch

with
[root@ovmgr1 ~]# yum repolist
repo id
repo name
AppStream
CentOS-8 - AppStream
BaseOS
 CentOS-8 - Base
PowerTools
 CentOS-8 - PowerTools
extras
 CentOS-8 - Extras
ovirt-4.4
Latest oVirt 4.4 Release
ovirt-4.4-advanced-virtualization
Advanced Virtualization packages for x86_64
ovirt-4.4-centos-gluster7
CentOS-8 - Gluster 7
ovirt-4.4-centos-opstools
CentOS-8 - OpsTools - collectd
ovirt-4.4-centos-ovirt44
 CentOS-8 - oVirt 4.4
ovirt-4.4-copr:copr.fedorainfracloud.org:mdbarroso:ovsdbapp
Copr repo for ovsdbapp owned by mdbarroso
ovirt-4.4-copr:copr.fedorainfracloud.org:networkmanager:NetworkManager-1.22
Copr repo for NetworkManager-1.22 owned by networkmanager
ovirt-4.4-copr:copr.fedorainfracloud.org:nmstate:nmstate-0.2
 Copr repo for nmstate-stable owned by nmstate
ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible
 Copr repo for gluster-ansible owned by sac
ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection
 Copr repo for EL8_collection owned by sbonazzo
ovirt-4.4-epel
 Extra Packages for Enterprise Linux 8 - x86_64
ovirt-4.4-virtio-win-latest
virtio-win builds roughly matching what will be shipped in upcoming RHEL
[root@ovmgr1 ~]# yum repolist
repo id
repo name
AppStream
CentOS-8 - AppStream
BaseOS
 CentOS-8 - Base
PowerTools
 CentOS-8 - PowerTools
extras
 CentOS-8 - Extras
ovirt-4.4
Latest oVirt 4.4 Release
ovirt-4.4-advanced-virtualization
Advanced Virtualization packages for x86_64
ovirt-4.4-centos-gluster7
CentOS-8 - Gluster 7
ovirt-4.4-centos-opstools
CentOS-8 - OpsTools - collectd
ovirt-4.4-centos-ovirt44
 CentOS-8 - oVirt 4.4
ovirt-4.4-copr:copr.fedorainfracloud.org:mdbarroso:ovsdbapp
Copr repo for ovsdbapp owned by mdbarroso
ovirt-4.4-copr:copr.fedorainfracloud.org:networkmanager:NetworkManager-1.22
Copr repo for NetworkManager-1.22 owned by networkmanager
ovirt-4.4-copr:copr.fedorainfracloud.org:nmstate:nmstate-0.2
 Copr repo for nmstate-stable owned by nmstate
ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible
 Copr repo for gluster-ansible owned by sac
ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection
 Copr repo for EL8_collection owned by sbonazzo
ovirt-4.4-epel
 Extra Packages for Enterprise Linux 8 - x86_64
ovirt-4.4-virtio-win-latest
virtio-win builds roughly matching what will be shipped in upcoming RHEL
[root@ovmgr1 ~]#

- /etc/yum.repos.d/ovirt-4.4.repo
[ovirt-4.4]
name=Latest oVirt 4.4 Release
#baseurl=https://resources.ovirt.org/pub/ovirt-4.4/rpm/el$releasever/
mirrorlist=
https://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.4-el$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.4


But if I run the command above I get:

[root@ovmgr1 ~]# yum update ovirt\*setup\*
Last metadata expiration check: 0:39:59 ago on Wed 11 Nov 2020 09:02:05 AM
CET.
Error:
 Problem 1: package
ovirt-engine-setup-plugin-ovirt-engine-4.4.3.11-1.el8.noarch requires
ovirt-engine >= 4.4.0, but none of the providers can be installed
  - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles
>= 1.2.0, but none of the providers can be installed
  - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes
ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch
  - cannot install the best update candidate for package
ovirt-engine-setup-plugin-ovirt-engine-4.4.2.6-1.el8.noarch
  - cannot install the best update candidate for package
ovirt-ansible-cluster-upgrade-1.2.3-1.el8.noarch
  - package ovirt-engine-4.4.0.3-1.el8.noarch is filtered out by exclude
filtering
  - package ovirt-engine-4.4.1-1.el8.noarch is filtered out by exclude
filtering
  - package ovirt-engine-4.4.1.1-1.el8.noarch is filtered out by exclude
filtering
  - package ovirt-engine-4.4.1.10-1.el8.noarch is filtered out by exclude
filtering
  - package ovirt-engine-4.4.1.2-1.el8.noarch is filtered out by exclude
filtering
  - package ovirt-engine-4.4.1.3-1.el8.noarch is filtered out by exclude
filtering
  - package ovirt-engine-4.4.1.4-1.el8.noarch is filtered out by exclude
filtering
  - package ovirt-engine-4.4.1.5-1.el8.noarch is filtered out by exclude
filtering
  - package ovirt-engine-4.4.1.6-1.el8.noarch is filtered out by exclude
filtering
  - package ovirt-engine-4.4.1.7-1.el8.noarch is filtered out by exclude
filtering
  - package ovirt-engine-4.4.1.8-1.el8.noarch is filtered out by exclude
filtering
  - package ovirt-engine-4.4.3.10-1.el8.noarch is filtered out by exclude
filtering
  - package ovirt-engine-4.4.3.11-1.el8.noarch is filtered out by exclude
filtering
  - package ovirt-engine-4.4.3.3-1.el8.noarch is filtered out by exclude
filtering
  - package ovirt-engine-4.4.3.4-1.el8.noarch is filtered out by exclude
filtering
  - package ovirt-engine-4.4.3.5-1.el8.noarch is filtered out by exclude
filtering
  - package 

[ovirt-users] Re: Deploy oVirt Engine fail behind proxy

2020-11-10 Thread Gianluca Cecchi
On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi  wrote:

> > On Tue, Nov 10, 2020 at 9:14 AM Matteo Bonardi  wrote:
> >
> > Someone recently reported on this list that setting both environment
> > variables http_proxy and https_proxy worked for them.
>

yes it was me here:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/D5WQSM7OZNKJQK3L5CN367W2TRVZZVHZ/

But in my case it was simpler because the engine was external.
With hosted engine it is indeed a problem that should be addressed I think

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


[ovirt-users] different rendering chrome and firefox and corruptions in both

2020-10-30 Thread Gianluca Cecchi
Hello,
I'm using Fedora 31 with
google-chrome-stable-86.0.4240.111-1.x86_64
firefox-82.0-4.fc31.x86_64

Engine was deployed from a CentOS Linux 8.2 host and then with hosted
engine wizard, using the appliance rpm (Package
ovirt-engine-appliance.x86_64 4.4-20200916125954.1.el8)
Connecting to the same 4.4.2 engine I get:

1) different landing page graphics
firefox:
https://drive.google.com/file/d/142Ch7qXmmIP9sQQCS1rD75yexX64RmSu/view?usp=sharing

chrome:
https://drive.google.com/file/d/1KPvlNk65ltIBhr8GFdVm-GMtfq1Elt7J/view?usp=sharing

2) corruption in several editing pages in firefox, where a sort of top
white part seems to compromise the lower part of the window, making
impossible to complete.
eg in new network I don't see the lower part related to MTU...:
https://drive.google.com/file/d/18aQfDbl_9R9oQsTMwebJSiRZHETkUWIc/view?usp=sharing

3) in Stotrage --> volumes page if I click on a volume, firefox shows no
problem, but chrome gives a gui exception:
https://drive.google.com/file/d/1svzQjrGctRMQFvZEpW9zpOlUbv8XXl3Q/view?usp=sharing

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


[ovirt-users] Re: Install test lab single host HCI with plain CentOS as OS

2020-10-30 Thread Gianluca Cecchi
On Fri, Oct 30, 2020 at 3:33 PM Gobinda Das  wrote:

> HI Gianluca,
>  Glad to hear that your problem is solved. As you redeployed Hosted Engine
> , default gluster service is not enabled in cluster because of that you are
> not able to see gluster volumes.
> Please edit cluster in admin protal and select the checkbox "Enable
> Gluster service" and save, your problem will be resolved :)
>
>
Thanks Gobinda, it worked like a charm.
Actually I was indeed searching for it remembering in the past, but I was
misled by firefox showing a corrupt page: for this problem I'm going to
open a distinct thread.

Do I need to restart engine service?
Because I can go into Storage --> Volumes but as soon as I click inside one
if them (eg engine) I get a gui exception (Chrome 86.0.4240.111 (Official
Build) (64-bit) on Fedora 31 google-chrome-stable-86.0.4240.111-1.x86_64)
See here:
https://drive.google.com/file/d/1svzQjrGctRMQFvZEpW9zpOlUbv8XXl3Q/view?usp=sharing

Conversely instead Firefox 82 (firefox-82.0-4.fc31.x86_64) doesn't show
this GUI exception
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/IYPNCMBE2C2VLEQPHPJ6ZO2FOQ7QP633/


[ovirt-users] Re: Install test lab single host HCI with plain CentOS as OS

2020-10-30 Thread Gianluca Cecchi
On Fri, Oct 30, 2020 at 12:02 PM Gobinda Das  wrote:

> Looks like your gluster deployment is happy, all gluster volumes will be
> up and running. Only you need to cleanup hosted-engine-deployment
> And start with Hosted Engine deployment. run the command
> "ovirt-hosted-engine-cleanup -q" and from wizard use "Hosted Engine"
> deployment.
> Please make sure appliances is installed and vdsm service is up and
> running.
>
>
>
Thanks Gobinda and Parth.

I followed what indicated by Gobinda:

[root@ovirt ~]# ovirt-hosted-engine-cleanup -q
  -=== Destroy hosted-engine VM ===-
You must run deploy first
  -=== Killing left-behind HostedEngine processes ===-
/sbin/ovirt-hosted-engine-cleanup: line 57: kill: (18988) - No such process
error: failed to get domain 'HostedEngine'

  -=== Stop HA services ===-
  -=== Shutdown sanlock ===-
shutdown force 1 wait 0
shutdown done 0
  -=== Disconnecting the hosted-engine storage domain ===-
You must run deploy first
  -=== De-configure VDSM networks ===-
ovirtmgmt
ovirtmgmt
  -=== Stop other services ===-
Warning: Stopping libvirtd.service, but it can still be activated by:
  libvirtd-admin.socket
  libvirtd.socket
  libvirtd-ro.socket
  -=== De-configure external daemons ===-
Removing database file /var/lib/vdsm/storage/managedvolume.db
  -=== Removing configuration files ===-
? /etc/init/libvirtd.conf already missing
- removing /etc/libvirt/nwfilter/vdsm-no-mac-spoofing.xml
? /etc/ovirt-hosted-engine/answers.conf already missing
? /etc/ovirt-hosted-engine/hosted-engine.conf already missing
- removing /etc/vdsm/vdsm.conf
- removing /etc/pki/vdsm/certs/cacert.pem
- removing /etc/pki/vdsm/certs/vdsmcert.pem
- removing /etc/pki/vdsm/keys/vdsmkey.pem
- removing /etc/pki/vdsm/libvirt-migrate/ca-cert.pem
- removing /etc/pki/vdsm/libvirt-migrate/server-cert.pem
- removing /etc/pki/vdsm/libvirt-migrate/server-key.pem
- removing /etc/pki/vdsm/libvirt-spice/ca-cert.pem
- removing /etc/pki/vdsm/libvirt-spice/server-cert.pem
- removing /etc/pki/vdsm/libvirt-spice/server-key.pem
- removing /etc/pki/vdsm/libvirt-vnc/ca-cert.pem
- removing /etc/pki/vdsm/libvirt-vnc/server-cert.pem
- removing /etc/pki/vdsm/libvirt-vnc/server-key.pem
- removing /etc/pki/CA/cacert.pem
- removing /etc/pki/libvirt/clientcert.pem
- removing /etc/pki/libvirt/private/clientkey.pem
? /etc/pki/ovirt-vmconsole/*.pem already missing
- removing /var/cache/libvirt/qemu
? /var/run/ovirt-hosted-engine-ha/* already missing
? /var/tmp/localvm* already missing
  -=== Removing IP Rules ===-
[root@ovirt ~]#

Then I executed the hosted engine setup from the wizard and chose Gluster
as the shared storage and all worked ok.

Now I have the final engine up and the 3 storage domains active.
The only strange thing I see is that on the host the volumes are active
(obviously ;-) but in ovirt web admin gui the storage -> volumes page is
empty.

[root@ovirt ~]# gluster volume list
data
engine
vmstore

[root@ovirt ~]# gluster volume status engine
Status of volume: engine
Gluster process TCP Port  RDMA Port  Online  Pid
--
Brick ovirtst.righini.storage:/gluster_bric
ks/engine/engine49152 0  Y
12947

Task Status of Volume engine
--
There are no active volume tasks

[root@ovirt ~]# gluster volume status data
Status of volume: data
Gluster process TCP Port  RDMA Port  Online  Pid
--
Brick ovirtst.righini.storage:/gluster_bric
ks/data/data49153 0  Y
13195

Task Status of Volume data
--
There are no active volume tasks

[root@ovirt ~]# gluster volume status vmstore
Status of volume: vmstore
Gluster process TCP Port  RDMA Port  Online  Pid
--
Brick ovirtst.righini.storage:/gluster_bric
ks/vmstore/vmstore  49154 0  Y
13447

Task Status of Volume vmstore
--
There are no active volume tasks

[root@ovirt ~]#

[root@ovirt ~]# df -h | egrep "Size|rhev"
Filesystem Size  Used Avail Use%
Mounted on
ovirtst.mydomain.storage:/engine100G  8.6G   92G   9%
/rhev/data-center/mnt/glusterSD/ovirtst.mydomain.storage:_engine
ovirtst.mydomain.storage:/data  300G  5.2G  295G   2%
/rhev/data-center/mnt/glusterSD/ovirtst.mydomain.storage:_data
ovirtst.mydomain.storage:/vmstore   200G  3.5G  197G   2%
/rhev/data-center/mnt/glusterSD/ovirtst.mydomain.storage:_vmstore
[root@ovirt ~]#

domains:

[ovirt-users] Re: Install test lab single host HCI with plain CentOS as OS

2020-10-30 Thread Gianluca Cecchi
On Fri, Oct 30, 2020 at 11:43 AM Parth Dhanjal  wrote:

> Hey!
> It seems vdsm packages are missing.
> Can you try installing vdsm-gluster and ovirt-engine-appliance packages?
> In case you face repo issues, just install yum install
> https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm
> Then try again.
>
>
Ok, thanks.
The appliance was already installed but vdsm-gluster was indeed missing.

So currently before deployment I executed on CentOS host (initially
installed choosing "server" option):
yum update
yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
yum update
yum install cockpit-ovirt-dashboard gluster-ansible-roles glusterfs-server
vdsm-gluster
systemctl enable --now cockpit.socket
reboot

Is there a list of all what is needed for this test lab single host HCI
with gluster? Anything else?

And what is the safe way to clean up before retrying deploy?

Thanks,
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/FW3Q3M7OUB3S4YERZPVUXE5Z67K6VCQR/


[ovirt-users] Re: Install test lab single host HCI with plain CentOS as OS

2020-10-30 Thread Gianluca Cecchi
On Fri, Oct 30, 2020 at 6:32 AM Gobinda Das  wrote:

> Hi Gianluca,
>  Yes, You can use cockpit UI for deployment. You need to install
> cockpit-ovirt-dashboard pkg for that.
>
>
OK, thanks for confirmation.
At first try the graphical gui complained about:

"
gluster-ansible-roles is not installed on Host. To continue deployment,
please install gluster-ansible-roles on Host and try again.
"

So I installed gluster-ansible-roles package and its dependencies.
Then retried but during first phases of deploy I got:
"
...

TASK [gluster.infra/roles/firewall_config : Add/Delete services to
firewalld rules] ***
failed: [ovirtst.mydomain.storage] (item=glusterfs) => {"ansible_loop_var":
"item", "changed": false, "item": "glusterfs", "msg": "ERROR: Exception
caught: org.fedoraproject.FirewallD1.Exception: INVALID_SERVICE:
'glusterfs' not among existing services Permanent and
Non-Permanent(immediate) operation, Services are defined by port/tcp
relationship and named as they are in /etc/services (on most systems)"}

"
My current config was

[root@ovirt ~]# firewall-cmd --list-services
cockpit dhcpv6-client ssh
[root@ovirt ~]#

but the problem seemed that it didn't recognize glusterfs as a known
service to enable in firewalld...

In fact:
[root@ovirt ~]# firewall-cmd --get-services | grep gluster
[root@ovirt ~]#

After running

dnf install glusterfs-server

it added the glusterfs service to firewalld config

Now it fails at stage 3 Prepare VM
"
. . .
[ INFO ] TASK [ovirt.hosted_engine_setup : Enable GlusterFS at cluster
level]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Set VLAN ID at datacenter level]
[ INFO ] skipping: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Get active list of active
firewalld zones]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Configure libvirt firewalld zone]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Add host]
[ INFO ] changed: [localhost]
[ INFO ] skipping: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks]
[ INFO ] skipping: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Always revoke the SSO token]
[ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Obtain SSO token using
username/password credentials]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Wait for the host to be up]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Notify the user about a failure]
[ INFO ] skipping: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : set_fact]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Collect error events from the
Engine]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Generate the error message from
the engine events]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fail with error description]
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The
host has been set in non_operational status, deployment errors: code 4035:
Gluster command [] failed on server ., code 9000: Failed
to verify Power Management configuration for Host ovirt.mydomain.local.,
code 10802: VDSM ovirt.mydomain.local command GlusterServersListVDS failed:
The method does not exist or is not available: {'method':
'GlusterHost.list'}, fix accordingly and re-deploy."}
[ INFO ] TASK [ovirt.hosted_engine_setup : Sync on engine machine]
[ INFO ] changed: [localhost]

In the first phases it put the temporary ip in /etc/hosts

192.168.222.233 ovengine.mydomain.local

But now it seems the /etc/hosts of the host is already cleaned from the
temporary ip, but the engine is set at it yet

[root@ovirt ovirt-hosted-engine-setup]# ping -c 3 192.168.222.233
PING 192.168.222.233 (192.168.222.233) 56(84) bytes of data.
64 bytes from 192.168.222.233: icmp_seq=1 ttl=64 time=0.262 ms
64 bytes from 192.168.222.233: icmp_seq=2 ttl=64 time=0.276 ms
64 bytes from 192.168.222.233: icmp_seq=3 ttl=64 time=0.267 ms

--- 192.168.222.233 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 30ms
rtt min/avg/max/mdev = 0.262/0.268/0.276/0.014 ms
[root@ovirt ovirt-hosted-engine-setup]#

[root@ovirt ovirt-hosted-engine-setup]# grep 192.168.222.233 /etc/hosts
[root@ovirt ovirt-hosted-engine-setup]#

In
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-ansible-bootstrap_local_vm-20201030105013-yf9fv8.log

2020-10-30 11:02:39,758+0100 DEBUG ansible on_any args localhostTASK:
ovirt.hosted_engine_setup : Al
ways revoke the SSO token kwargs
2020-10-30 11:02:41,035+0100 ERROR ansible failed {
"ansible_host": "localhost",
"ansible_playbook":
"/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml",
"ansible_result": {
"_ansible_no_log": false,
"changed": false,
"invocation": {

[ovirt-users] Install test lab single host HCI with plain CentOS as OS

2020-10-29 Thread Gianluca Cecchi
Hello,
if I want to install a test lab environment of type single host HCI and
want to use CentOS 8.2 as the OS for the host, can I still use the
graphical wizard from cockpit? I see it accessing the server...
Or is it thought only to be run from ovirt-node-ng system?
In case it is not possible is there a command line workflow I can use to
get the same as the wizard playbook run?

BTW: I want to use CentOS for this test lab because I need to install
custom packages (for performance counters and other things) so I'd prefer
the flexibility to have a plain CentOS and not the NG node.

Thanks in advance,
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/O4ZURQ3SM2TBI2OIYWWHEERMKRX65B67/


[ovirt-users] update host to 4.4: manual ovn config necessary?

2020-10-27 Thread Gianluca Cecchi
Hello,
I have updated an external engine from 4.3 to 4.4 and the OVN configuration
seems to have been retained:

[root@ovmgr1 ovirt-engine]# ovn-nbctl show
switch fc2fc4e8-ff71-4ec3-ba03-536a870cd483
(ovirt-ovn192-1e252228-ade7-47c8-acda-5209be358fcf)
switch 101d686d-7930-4176-b41a-b306d7c30a1a
(ovirt-ovn17217-4bb1d1a7-020d-4843-9ac7-dc4204b528e5)
port c1ec60a4-b4f3-4cb5-8985-43c086156e83
addresses: ["00:1a:4a:19:01:89 dynamic"]
port 174b69f8-00ed-4e25-96fc-7db11ea8a8b9
addresses: ["00:1a:4a:19:01:59 dynamic"]
port ccbd6188-78eb-437b-9df9-9929e272974b
addresses: ["00:1a:4a:19:01:88 dynamic"]
port 7e96ca70-c9e3-4efe-9ac5-e56c18476437
addresses: ["00:1a:4a:19:01:83 dynamic"]
port d2c2d9f1-8fc3-4f17-9ada-76fe3a168e65
addresses: ["00:1a:4a:19:01:5e dynamic"]
port 4d13d63e-5ff3-41c1-9b6b-feac343b514b
addresses: ["00:1a:4a:19:01:60 dynamic"]
port 66359e79-56c4-47e0-8196-2241706329f6
addresses: ["00:1a:4a:19:01:68 dynamic"]
switch 87012fa6-ffaa-4fb0-bd91-b3eb7c0a2fc1
(ovirt-ovn193-d43a7928-0dc8-49d3-8755-5d766dff821a)
port 2ae7391b-4297-4247-a315-99312f6392e6
addresses: ["00:1a:4a:19:01:51 dynamic"]
switch 9e77163a-c4e4-4abf-a554-0388e6b5e4ce
(ovirt-ovn172-4ac7ba24-aad5-432d-b1d2-672eaeea7d63)
[root@ovmgr1 ovirt-engine]#

Then I updated one of the 3 Linux hosts (not node ng) through remove from
web admin gui, install from scratch of CentOS 8.2 OS, configure repos and
then add new host (with the same name) in engine and I was able to connect
to storage (iSCSI) and start VMs in general on the host.
Coming to OVN part it seems it has not been configured on the upgraded host.
Is it expected?

Eg on engine I only see chassis for the 2 hosts still in 4.3:

[root@ovmgr1 ovirt-engine]# ovn-sbctl show
Chassis "b8872ab5-4606-4a79-b77d-9d956a18d349"
hostname: "ov301.mydomain"
Encap geneve
ip: "10.4.192.34"
options: {csum="true"}
Port_Binding "174b69f8-00ed-4e25-96fc-7db11ea8a8b9"
Port_Binding "66359e79-56c4-47e0-8196-2241706329f6"
Chassis "ddecf0da-4708-4f93-958b-6af365a5eeca"
hostname: "ov300.mydomain"
Encap geneve
ip: "10.4.192.33"
options: {csum="true"}
Port_Binding "ccbd6188-78eb-437b-9df9-9929e272974b"
[root@ovmgr1 ovirt-engine]#

What to do to add the upgraded 4.4 host? Can they live together for the OVN
part?

Thanks,
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/HWXNXE4BXWGKDU7SJ325ZEYJRYXSPWML/


[ovirt-users] reinstall 4.3 host from 4.4 engine

2020-10-26 Thread Gianluca Cecchi
Hello,
supposing I'm with an already upgraded 4.4.2 engine and in my environment I
still have some 4.3.10 hosts based on CentOS Linux 7.x (or 4.3.10 ng
nodes), is it supported to reinstall such host in case of any modification
in configuration?
Or will the engine try to install them in a "4.4" way?

Thanks in advance,
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/MWJOIQWVRJIEEPSDLETUINME3SS3ZWSB/


[ovirt-users] Re: problems installing standard Linux as nodes in 4.4

2020-10-26 Thread Gianluca Cecchi
On Thu, Oct 15, 2020 at 12:25 PM Gianluca Cecchi 
wrote:

> On Thu, Oct 15, 2020 at 10:41 AM Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>>
>>
>> Any feedback on my latest comments?
>> In the meantime here:
>>
>> https://drive.google.com/file/d/1iN37znRtCo2vgyGTH_ymLhBJfs-2pWDr/view?usp=sharing
>> you can find inside the sosreport in tar.gz format, where I have modified
>> some file names and context in respect of hostnames.
>> The only file I have not put inside is the dump of the database, but I
>> can run any query you like in case.
>>
>> Gianluca
>>
>>
>
> I have also tried to put debug into the engine.
>
>
So after huge debugging work with Dana Elfassy and Martin Necas (thank you
very much to both!) and coordination of Sandro we found the culprit!

Inside firewall custom rules of my engine I had this (note the double
quotes for the comment about Nagios):

[root@ovmgr1 ovirt-engine]# engine-config -g IPTablesConfigSiteCustom
IPTablesConfigSiteCustom: -A INPUT -p tcp --dport 5666 -s 10.4.5.99/32 -m
comment --comment "Nagios NRPE daemon" -j ACCEPT version: general
[root@ovmgr1 ovirt-engine]#

So those double quotes  caused a wrong formatted json block that
ansible-runner-service was not able to manage in the http post phase

After changing with single quotes, with this command:

engine-config -s IPTablesConfigSiteCustom="-A INPUT -p tcp --dport 5666 -s
10.4.5.99/32 -m comment --comment 'Nagios NRPE daemon' -j ACCEPT"

and restarting the engine so that now I have

[root@ovmgr1 ovirt-engine]# engine-config -g IPTablesConfigSiteCustom
IPTablesConfigSiteCustom: -A INPUT -p tcp --dport 5666 -s 10.4.5.99/32 -m
comment --comment 'Nagios NRPE daemon' -j ACCEPT version: general
[root@ovmgr1 ovirt-engine]#

I was able to add the CentOS 8.2 host.
So mind if you have the double quotes in any engine-config key before
upgrading from 4.3 to 4.4.

What a nasty thing to detect...
Thanks again guys for your help

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/5P6M7RP4KPNEX7TCEIDE4Q4DY5MEJBVZ/


[ovirt-users] rhv 4.3.11 but not ovirt 4.3.11

2020-10-22 Thread Gianluca Cecchi
Hello,
I see that a 4.3.11 version is available for downstream RHV but not for
upstream oVirt.
Will it be released for oVirt too?
Are there only security fixes inside or also bug fixes (like the few lines
one related to export as OVA)?

Thanks,
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/GDLRJXSS525POCOQICJVGXFL55Q4RMWV/


[ovirt-users] Re: Add direct lun (Fibre Channel) to VM

2020-10-20 Thread Gianluca Cecchi
On Tue, Oct 20, 2020 at 1:22 PM  wrote:

> Hi
> how to add directly to a VM 4 fiber channel luns without losing the data
> they have, these luns need to be seen directly on the VM as "raw devices".
>
> Thks
>
> Plima
>
>
In general the page to add disks and also direct lun is this one:
https://www.ovirt.org/documentation/virtual_machine_management_guide/#sect-Virtual_Disks

If the host were previously given access to the LUNs, when you select
direct lun, you should see it and then add.
Please do a test with a non production lun to be able to verify no negative
effects.
You cannot live migrate a VM with direct lun attached.
Also, if you select a LUN that is already part of a storage domain you
should get the warning message:

LUN is already part of a Storage Domain: X

HIH,
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/H6DDDGG7ALS7DXMAQ4F2N4QUKAX7AGNJ/


[ovirt-users] Re: problems installing standard Linux as nodes in 4.4

2020-10-15 Thread Gianluca Cecchi
On Thu, Oct 15, 2020 at 10:41 AM Gianluca Cecchi 
wrote:

>
>
> Any feedback on my latest comments?
> In the meantime here:
>
> https://drive.google.com/file/d/1iN37znRtCo2vgyGTH_ymLhBJfs-2pWDr/view?usp=sharing
> you can find inside the sosreport in tar.gz format, where I have modified
> some file names and context in respect of hostnames.
> The only file I have not put inside is the dump of the database, but I can
> run any query you like in case.
>
> Gianluca
>
>

I have also tried to put debug into the engine.
Method used base on this link:

https://www.ovirt.org/develop/developer-guide/engine/engine-development-environment.html

and I used engine.core as the package

[root@ovmgr1 ~]# diff ovirt-engine.xml.in ovirt-engine.xml.in.debug
118c118
< 
---
> 
197a198,200
>   
> 
>   
[root@ovmgr1 ~]#

When the install fails I get this in engine.log now:

2020-10-15 12:16:15,394+02 INFO
 [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engine-Thread-31)
[c439aded-ade3-4474-a5f1-2f074ed5d920] EVENT_ID:
VDS_ANSIBLE_INSTALL_STARTED(560), Ansible host-deploy playbook execution
has started on host ov200.
2020-10-15 12:16:15,412+02 ERROR
[org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
(EE-ManagedThreadFactory-engine-Thread-31)
[c439aded-ade3-4474-a5f1-2f074ed5d920] Exception: Failed to execute call to
start playbook.
2020-10-15 12:16:15,412+02 DEBUG
[org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
(EE-ManagedThreadFactory-engine-Thread-31)
[c439aded-ade3-4474-a5f1-2f074ed5d920] Exception: :
org.ovirt.engine.core.common.utils.ansible.AnsibleRunnerCallException:
Failed to execute call to start playbook.
at
deployment.engine.ear.bll.jar//org.ovirt.engine.core.common.utils.ansible.AnsibleRunnerHTTPClient.runPlaybook(AnsibleRunnerHTTPClient.java:153)
at
deployment.engine.ear.bll.jar//org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor.runCommand(AnsibleExecutor.java:113)
at
deployment.engine.ear.bll.jar//org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor.runCommand(AnsibleExecutor.java:78)
at
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand.runAnsibleHostDeployPlaybook(InstallVdsInternalCommand.java:281)
at
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand.executeCommand(InstallVdsInternalCommand.java:145)
at
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1169)
at
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1327)
at
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:2003)
at
org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:140)
at
org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:79)
at
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1387)
at
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:419)
at
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.PrevalidatingMultipleActionsRunner.executeValidatedCommand(PrevalidatingMultipleActionsRunner.java:204)
at
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.PrevalidatingMultipleActionsRunner.runCommands(PrevalidatingMultipleActionsRunner.java:176)
at
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.PrevalidatingMultipleActionsRunner.lambda$invokeCommands$3(PrevalidatingMultipleActionsRunner.java:182)
at
org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil$InternalWrapperRunnable.run(ThreadPoolUtil.java:96)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
at
org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:227)

2020-10-15 12:16:15,412+02 ERROR
[org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
(EE-ManagedThreadFactory-engine-Thread-31)
[c439aded-ade3-4474-a5f1-2f074ed5d920] Host installation failed for host
'79da834f-d03a-4abc-b89e-8ad0186c173c', 'ov200': Failed to execute Ansible
host-deploy role: Fail

[ovirt-users] Re: problems installing standard Linux as nodes in 4.4

2020-10-15 Thread Gianluca Cecchi
On Tue, Oct 13, 2020 at 12:06 PM Gianluca Cecchi 
wrote:

> On Sat, Oct 10, 2020 at 10:13 AM Martin Perina  wrote:
>
> [snip]
>
>
>>> Can I replicate the command that the engine would run on host through
>>> ssh?
>>>
>>
>> I don't think so there is an easy way to do it
>> Let's see what else we can get from the logs...
>>
>> Martin
>>
>>
> Hi,
> I've run on engine the command
> ovirt-log-collector --no-hypervisors
> but potentially there is much sensitive information (like the dump of the
> database).
>
> Is there any particular file you are more interested in that archive I can
> share?
>
> BTW: can I put engine in debug for the time I'm trying to add the host so
> that we can see if more messages are shown?
> In that case how can I do?
>
> Another information I have noticed is that when the new host command from
> web admin GUI suddenly fails, anyway the ov200 host is now present in the
> host list, with the down icon and "Install failed" info.
> If I click on it and go in General subtab, in the section "Action Items" I
> see 3 items with exclamation mark in front of them:
>
> 1) Power Management is not configured for this Host.
> Enable Power Management
> --> OK, I skipped it
>
> 2) Host has no default route.
> ---> I don't know why it says this.
>
> [root@ov200 log]# ip route show
> default via 10.4.192.254 dev bond0.68 proto static metric 400
> 10.4.192.0/24 dev bond0.68 proto kernel scope link src 10.4.192.32 metric
> 400
> 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
> linkdown
> [root@ov200 log]#
>
> On the still in CentOS 7 active host I have:
>
> [root@ov300 ~]# ip route show
> default via 10.4.192.254 dev ovirtmgmntZ2Z3
> 10.4.187.0/24 dev p1p2.187 proto kernel scope link src 10.4.187.100
> 10.4.192.0/24 dev ovirtmgmntZ2Z3 proto kernel scope link src 10.4.192.33
> 10.10.100.0/24 dev p1p2 proto kernel scope link src 10.10.100.88
> 10.10.100.0/24 dev p1p1.100 proto kernel scope link src 10.10.100.87
> [root@ov300 ~]#
>
> [root@ov300 ~]# brctl show ovirtmgmntZ2Z3
> bridge name bridge id STP enabled interfaces
> ovirtmgmntZ2Z3 8000.1803730ba369 no bond0.68
> [root@ov300 ~]#
>
> Could it be the fact that for historical reasons my mgmt network has not
> the name ovirtmgmt but ovirtmgmntZ2Z3 that confuses the installer that
> expects ovirtmgmt to setup? And erroneously reports the no default route
> message?
>
> 3) The host CPU does not match the Cluster CPU Type and is running in a
> degraded mode. It is missing the following CPU flags: vmx, ssbd, nx,
> model_Westmere, aes, spec_ctrl. Please update the host CPU microcode or
> change the Cluster CPU Type.
>
> The cluster is set as "Intel Westmere IBRS SSBD Family".
> all the hosts are the same hw Dell PE M610, with same processor
>
> Host installed in CentOS 8:
> [root@ov200 log]# cat /proc/cpuinfo | grep "model name" | sort -u
> model name : Intel(R) Xeon(R) CPU   X5690  @ 3.47GHz
> [root@ov200 log]#
>
> Host still in CentOS 7:
> [root@ov300 ~]# cat /proc/cpuinfo | grep "model name" | sort -u
> model name : Intel(R) Xeon(R) CPU   X5690  @ 3.47GHz
> [root@ov300 ~]#
>
> If I compare the cpu flags inside the OS I see:
>
> CentOS 8:
> [root@ov200 log]# cat /proc/cpuinfo | grep flags | sort -u
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
> pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
> rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
> nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx
> est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt aes lahf_lm pti
> ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat
> flush_l1d
> [root@ov200 log]#
>
> CentOS 7:
> [root@ov300 ~]# cat /proc/cpuinfo | grep flags | sort -u
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
> pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
> rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
> nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx
> est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt aes lahf_lm ssbd
> ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat
> spec_ctrl intel_stibp flush_l1d
> [root@ov300 ~]#
>
> When still in CentOS 7, ov200 had the same flags as ov300
> ov200 has this more now:
> cpuid pti
>
> ov200 has these less now:
> eagerfpu spec_ctrl intel_stibp
>
> Gianluca
>

Any feedback on my latest comments?
In the meantime here

[ovirt-users] Re: oVirt 4.4.2.6-1.el8 (SHE). Grafana integration not configured. The link to the Monitoring portal is not displayed on the Manager home page.

2020-10-13 Thread Gianluca Cecchi
On Tue, Oct 13, 2020 at 3:27 PM Yedidyah Bar David  wrote:

> On Tue, Oct 13, 2020 at 3:48 PM Dmitry Kharlamov 
> wrote:
> >
> > Good afternoon, Lucie! Thanks for the info.
> >
> > After reinstalling engine with --reconfigure-optional-components Grafana
> is work and link to Monitoring portal present on home page.
> > SSO works the same way, but only for Internal users. Users
> ActiveDirectory cannot enter the Monitoring Portal - "Invalid User or
> Password".
>
> This is, for now, by design. You have to invite them, and then SSO
> works. See also:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1846256
>
> Best regards,
> --
> Didi
> __
>

Nice, it works.
It would be nice to have the domain line also in Grafana as in web admin
gui login page (the "Profile" line in 4.4).

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


[ovirt-users] Re: problems installing standard Linux as nodes in 4.4

2020-10-13 Thread Gianluca Cecchi
On Sat, Oct 10, 2020 at 10:13 AM Martin Perina  wrote:

[snip]


>> Can I replicate the command that the engine would run on host through ssh?
>>
>
> I don't think so there is an easy way to do it
> Let's see what else we can get from the logs...
>
> Martin
>
>
Hi,
I've run on engine the command
ovirt-log-collector --no-hypervisors
but potentially there is much sensitive information (like the dump of the
database).

Is there any particular file you are more interested in that archive I can
share?

BTW: can I put engine in debug for the time I'm trying to add the host so
that we can see if more messages are shown?
In that case how can I do?

Another information I have noticed is that when the new host command from
web admin GUI suddenly fails, anyway the ov200 host is now present in the
host list, with the down icon and "Install failed" info.
If I click on it and go in General subtab, in the section "Action Items" I
see 3 items with exclamation mark in front of them:

1) Power Management is not configured for this Host.
Enable Power Management
--> OK, I skipped it

2) Host has no default route.
---> I don't know why it says this.

[root@ov200 log]# ip route show
default via 10.4.192.254 dev bond0.68 proto static metric 400
10.4.192.0/24 dev bond0.68 proto kernel scope link src 10.4.192.32 metric
400
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
linkdown
[root@ov200 log]#

On the still in CentOS 7 active host I have:

[root@ov300 ~]# ip route show
default via 10.4.192.254 dev ovirtmgmntZ2Z3
10.4.187.0/24 dev p1p2.187 proto kernel scope link src 10.4.187.100
10.4.192.0/24 dev ovirtmgmntZ2Z3 proto kernel scope link src 10.4.192.33
10.10.100.0/24 dev p1p2 proto kernel scope link src 10.10.100.88
10.10.100.0/24 dev p1p1.100 proto kernel scope link src 10.10.100.87
[root@ov300 ~]#

[root@ov300 ~]# brctl show ovirtmgmntZ2Z3
bridge name bridge id STP enabled interfaces
ovirtmgmntZ2Z3 8000.1803730ba369 no bond0.68
[root@ov300 ~]#

Could it be the fact that for historical reasons my mgmt network has not
the name ovirtmgmt but ovirtmgmntZ2Z3 that confuses the installer that
expects ovirtmgmt to setup? And erroneously reports the no default route
message?

3) The host CPU does not match the Cluster CPU Type and is running in a
degraded mode. It is missing the following CPU flags: vmx, ssbd, nx,
model_Westmere, aes, spec_ctrl. Please update the host CPU microcode or
change the Cluster CPU Type.

The cluster is set as "Intel Westmere IBRS SSBD Family".
all the hosts are the same hw Dell PE M610, with same processor

Host installed in CentOS 8:
[root@ov200 log]# cat /proc/cpuinfo | grep "model name" | sort -u
model name : Intel(R) Xeon(R) CPU   X5690  @ 3.47GHz
[root@ov200 log]#

Host still in CentOS 7:
[root@ov300 ~]# cat /proc/cpuinfo | grep "model name" | sort -u
model name : Intel(R) Xeon(R) CPU   X5690  @ 3.47GHz
[root@ov300 ~]#

If I compare the cpu flags inside the OS I see:

CentOS 8:
[root@ov200 log]# cat /proc/cpuinfo | grep flags | sort -u
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx
est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt aes lahf_lm pti
ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat
flush_l1d
[root@ov200 log]#

CentOS 7:
[root@ov300 ~]# cat /proc/cpuinfo | grep flags | sort -u
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx
est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt aes lahf_lm ssbd
ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat
spec_ctrl intel_stibp flush_l1d
[root@ov300 ~]#

When still in CentOS 7, ov200 had the same flags as ov300
ov200 has this more now:
cpuid pti

ov200 has these less now:
eagerfpu spec_ctrl intel_stibp

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


[ovirt-users] Re: problems installing standard Linux as nodes in 4.4

2020-10-09 Thread Gianluca Cecchi
On Fri, Oct 9, 2020 at 7:12 PM Martin Perina  wrote:

>
>
> Could you please share with us all logs from engine gathered by
> logcollector? We will try to find out any clue what's wrong in your env ...
>
> Thanks,
> Martin
>
>
I will try to collect.
In the mean time I've found that SSH could be in some way involved

When I add the host and get the immediate failure and apparently nothing
happens at all,  I see these two lines in /var/log/ovirt-engine/server.log

2020-10-09 18:15:09,369+02 WARN
 [org.apache.sshd.client.session.ClientConnectionService]
(sshd-SshClient[7cb54873]-nio2-thread-1)
globalRequest(ClientConnectionService[ClientSessionImpl[root@ov200
/10.4.192.32:22]])[hostkeys...@openssh.com, want-reply=false] failed
(SshException) to process: EdDSA provider not supported
2020-10-09 18:15:09,699+02 WARN
 [org.apache.sshd.client.session.ClientConnectionService]
(sshd-SshClient[2cbceeab]-nio2-thread-1)
globalRequest(ClientConnectionService[ClientSessionImpl[root@ov200
/10.4.192.32:22]])[hostkeys...@openssh.com, want-reply=false] failed
(SshException) to process: EdDSA provider not supported

could it be that the ssh client embedded is not able to connect to the
CentOS 8.2 for some reason?

On host at the moment when I try to add it I see again two sessions opened
and immediately closed (tried several times), eg in the timeframe above I
have:

Oct  9 18:15:09 ov200 systemd-logind[1237]: New session 41 of user root.
Oct  9 18:15:09 ov200 systemd[1]: Started Session 41 of user root.
Oct  9 18:15:09 ov200 systemd-logind[1237]: Session 41 logged out. Waiting
for processes to exit.
Oct  9 18:15:09 ov200 systemd-logind[1237]: Removed session 41.
Oct  9 18:15:09 ov200 systemd-logind[1237]: New session 42 of user root.
Oct  9 18:15:09 ov200 systemd[1]: Started Session 42 of user root.
Oct  9 18:15:09 ov200 systemd-logind[1237]: Session 42 logged out. Waiting
for processes to exit.
Oct  9 18:15:09 ov200 systemd-logind[1237]: Removed session 42.

anyway at sshd service level it seems it is ok om the host:

journalctl -u sshd.service has

Oct 09 18:15:09 ov200 sshd[13379]: Accepted password for root from
10.4.192.43 port 46008 ssh2
Oct 09 18:15:09 ov200 sshd[13379]: pam_unix(sshd:session): session opened
for user root by (uid=0)
Oct 09 18:15:09 ov200 sshd[13379]: pam_unix(sshd:session): session closed
for user root
Oct 09 18:15:09 ov200 sshd[13398]: Accepted password for root from
10.4.192.43 port 46014 ssh2
Oct 09 18:15:09 ov200 sshd[13398]: pam_unix(sshd:session): session opened
for user root by (uid=0)
Oct 09 18:15:09 ov200 sshd[13398]: pam_unix(sshd:session): session closed
for user root

On the host I have not customized anything ssh related:

[root@ov200 ssh]# ps -ef|grep sshd
root1274   1  0 Oct08 ?00:00:00 /usr/sbin/sshd -D
-oCiphers=aes256-...@openssh.com,chacha20-poly1...@openssh.com
,aes256-ctr,aes256-cbc,aes128-...@openssh.com,aes128-ctr,aes128-cbc -oMACs=
hmac-sha2-256-...@openssh.com,hmac-sha1-...@openssh.com,
umac-128-...@openssh.com,hmac-sha2-512-...@openssh.com
,hmac-sha2-256,hmac-sha1,umac-...@openssh.com,hmac-sha2-512
-oGSSAPIKexAlgorithms=gss-gex-sha1-,gss-group14-sha1-
-oKexAlgorithms=curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1
-oHostKeyAlgorithms=rsa-sha2-256,rsa-sha2-256-cert-...@openssh.com
,ecdsa-sha2-nistp256,ecdsa-sha2-nistp256-cert-...@openssh.com
,ecdsa-sha2-nistp384,ecdsa-sha2-nistp384-cert-...@openssh.com,rsa-sha2-512,
rsa-sha2-512-cert-...@openssh.com,ecdsa-sha2-nistp521,
ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519,
ssh-ed25519-cert-...@openssh.com,ssh-rsa,ssh-rsa-cert-...@openssh.com
-oPubkeyAcceptedKeyTypes=rsa-sha2-256,rsa-sha2-256-cert-...@openssh.com
,ecdsa-sha2-nistp256,ecdsa-sha2-nistp256-cert-...@openssh.com
,ecdsa-sha2-nistp384,ecdsa-sha2-nistp384-cert-...@openssh.com,rsa-sha2-512,
rsa-sha2-512-cert-...@openssh.com,ecdsa-sha2-nistp521,
ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519,
ssh-ed25519-cert-...@openssh.com,ssh-rsa,ssh-rsa-cert-...@openssh.com
-oCASignatureAlgorithms=rsa-sha2-256,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,rsa-sha2-512,ecdsa-sha2-nistp521,ssh-ed25519,ssh-rsa

and in sshd_config

HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
HostKey /etc/ssh/ssh_host_ed25519_key

Can I replicate the command that the engine would run on host through ssh?

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


[ovirt-users] Re: problems installing standard Linux as nodes in 4.4

2020-10-09 Thread Gianluca Cecchi
On Fri, Oct 9, 2020 at 6:29 PM Martin Perina  wrote:

>
>
> On Fri, Oct 9, 2020 at 5:54 PM Gianluca Cecchi 
> wrote:
>
>> On Fri, Oct 9, 2020 at 4:58 PM Martin Perina  wrote:
>>
>>> Hi Gianluca,
>>>
>>> could you please check selinux context of
>>> /var/log/ovirt-engine/ansible-runner-service.log to see if you are not
>>> affected by https://bugzilla.redhat.com/show_bug.cgi?id=1880171#c5 ?
>>>
>>> Thanks,
>>> Martin
>>>
>>
>> Thanks for answering.
>> It seems ok. On the engine:
>> [root@ovmgr1 ~]# ls -Z /var/log/ovirt-engine/ansible-runner-service.log
>> system_u:object_r:httpd_log_t:s0
>> /var/log/ovirt-engine/ansible-runner-service.log
>> [root@ovmgr1 ~]#
>>
>> Gianluca
>>
>
> OK, so could you please apply the workaround mentioned in
> https://bugzilla.redhat.com/show_bug.cgi?id=1880171#c5 to resolve the
> issue until oVirt 4.4.3 is released?
>
>
Sorry, but isn't it already ok? The SELinux security context for the file
is already httpd_log_t, so I don't have to apply anything.
I also applied the more brutal workaround described in
https://bugzilla.redhat.com/show_bug.cgi?id=1880171#c4 without any effect,
so I'm not in this bugzilla context.
Do I have to apply also for the directory /var/log/ovirt-engine itself,
that currently has a context of var_log_t? I don't think so...

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


[ovirt-users] Re: problems installing standard Linux as nodes in 4.4

2020-10-09 Thread Gianluca Cecchi
On Fri, Oct 9, 2020 at 4:58 PM Martin Perina  wrote:

> Hi Gianluca,
>
> could you please check selinux context of
> /var/log/ovirt-engine/ansible-runner-service.log to see if you are not
> affected by https://bugzilla.redhat.com/show_bug.cgi?id=1880171#c5 ?
>
> Thanks,
> Martin
>

Thanks for answering.
It seems ok. On the engine:
[root@ovmgr1 ~]# ls -Z /var/log/ovirt-engine/ansible-runner-service.log
system_u:object_r:httpd_log_t:s0
/var/log/ovirt-engine/ansible-runner-service.log
[root@ovmgr1 ~]#

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


[ovirt-users] Re: problems installing standard Linux as nodes in 4.4

2020-10-09 Thread Gianluca Cecchi
On Thu, Oct 8, 2020 at 5:13 PM Gianluca Cecchi 
wrote:

>
>
> On Thu, Oct 8, 2020 at 5:08 PM Gianluca Cecchi 
> wrote:
>
>> On Thu, Oct 8, 2020 at 4:59 PM Dana Elfassy  wrote:
>>
>>> And also please attach the content of the file found at:
>>> /etc/ansible-runner-service/config.yaml
>>>
>>> On Thu, Oct 8, 2020 at 5:55 PM Dana Elfassy  wrote:
>>>
>>>> Hi Gianluca,
>>>> Please execute the following command on your engine, save the output
>>>> into a file and attach it:
>>>> sudo journalctl -u ansible-runner-service
>>>> Dana
>>>>
>>>>
>> Thanks for answering, Dana.
>>
>>  [root@ovmgr1 ansible-runner-service]# sudo journalctl -u
>> ansible-runner-service
>> -- Logs begin at Tue 2020-10-06 11:12:46 CEST, end at Thu 2020-10-08
>> 17:02:25 CEST. --
>> -- No entries --
>> [root@ovmgr1 ansible-runner-service]#
>>
>>
>> [root@ovmgr1 ansible-runner-service]# cat
>> /etc/ansible-runner-service/config.yaml
>>
>> version: 1
>> playbooks_root_dir:
>> '/usr/share/ovirt-engine/ansible-runner-service-project'
>> ssh_private_key: '/etc/pki/ovirt-engine/keys/engine_id_rsa'
>> port: 50001
>> target_user: root
>> log_path: '/var/log/ovirt-engine'
>> [root@ovmgr1 ansible-runner-service]#
>>
>> I noticed that both on engine and on host the "ansible-runner" package is
>> not installed. Is it correct and only ansible-runner-service package to be
>> installed only on the engine?
>> Also, does the "service" in the name imply that I should have any systemd
>> or other kind of related service on engine?
>> Finally, I have to use a proxy for dnf/yum.
>> To be able to run "engine-setup" on engine I had to set http_proxy and
>> https_proxy eng variables inside the shell session, because it seems that
>> engine-setup was not able to leverage the global configuration. Could it be
>> something similar due to the host having to use a proxy too (that I already
>> setup in /etc/dnf/dnf.conf)? Just a guess.
>>
>> Gianluca
>>
>
> Also, the host already existed in 4.3. I upgraded the standalone engine
> from 4.3.10 to 4.4.2 following the guide.
> Now to update my hosts I put a host into maintenance, removed the host
> from the gui, reinstalled the server in CentOS 8.2 with same network
> parameters, and then add new host with the same name/hostname as before.
> Could it be a problem to reuse the host?
>
> Gianluca
>

Any other thing to check to be able to provision a node in 4.4.2 using
plain CentOS 8.2 host?
Thanks,
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/AJN3ENCAXNCTGWD4AXGCXQQEE6KOSXDN/


[ovirt-users] Re: problems installing standard Linux as nodes in 4.4

2020-10-08 Thread Gianluca Cecchi
On Thu, Oct 8, 2020 at 5:08 PM Gianluca Cecchi 
wrote:

> On Thu, Oct 8, 2020 at 4:59 PM Dana Elfassy  wrote:
>
>> And also please attach the content of the file found at:
>> /etc/ansible-runner-service/config.yaml
>>
>> On Thu, Oct 8, 2020 at 5:55 PM Dana Elfassy  wrote:
>>
>>> Hi Gianluca,
>>> Please execute the following command on your engine, save the output
>>> into a file and attach it:
>>> sudo journalctl -u ansible-runner-service
>>> Dana
>>>
>>>
> Thanks for answering, Dana.
>
>  [root@ovmgr1 ansible-runner-service]# sudo journalctl -u
> ansible-runner-service
> -- Logs begin at Tue 2020-10-06 11:12:46 CEST, end at Thu 2020-10-08
> 17:02:25 CEST. --
> -- No entries --
> [root@ovmgr1 ansible-runner-service]#
>
>
> [root@ovmgr1 ansible-runner-service]# cat
> /etc/ansible-runner-service/config.yaml
>
> version: 1
> playbooks_root_dir:
> '/usr/share/ovirt-engine/ansible-runner-service-project'
> ssh_private_key: '/etc/pki/ovirt-engine/keys/engine_id_rsa'
> port: 50001
> target_user: root
> log_path: '/var/log/ovirt-engine'
> [root@ovmgr1 ansible-runner-service]#
>
> I noticed that both on engine and on host the "ansible-runner" package is
> not installed. Is it correct and only ansible-runner-service package to be
> installed only on the engine?
> Also, does the "service" in the name imply that I should have any systemd
> or other kind of related service on engine?
> Finally, I have to use a proxy for dnf/yum.
> To be able to run "engine-setup" on engine I had to set http_proxy and
> https_proxy eng variables inside the shell session, because it seems that
> engine-setup was not able to leverage the global configuration. Could it be
> something similar due to the host having to use a proxy too (that I already
> setup in /etc/dnf/dnf.conf)? Just a guess.
>
> Gianluca
>

Also, the host already existed in 4.3. I upgraded the standalone engine
from 4.3.10 to 4.4.2 following the guide.
Now to update my hosts I put a host into maintenance, removed the host from
the gui, reinstalled the server in CentOS 8.2 with same network parameters,
and then add new host with the same name/hostname as before. Could it be a
problem to reuse the host?

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


[ovirt-users] Re: problems installing standard Linux as nodes in 4.4

2020-10-08 Thread Gianluca Cecchi
On Thu, Oct 8, 2020 at 4:59 PM Dana Elfassy  wrote:

> And also please attach the content of the file found at:
> /etc/ansible-runner-service/config.yaml
>
> On Thu, Oct 8, 2020 at 5:55 PM Dana Elfassy  wrote:
>
>> Hi Gianluca,
>> Please execute the following command on your engine, save the output into
>> a file and attach it:
>> sudo journalctl -u ansible-runner-service
>> Dana
>>
>>
Thanks for answering, Dana.

 [root@ovmgr1 ansible-runner-service]# sudo journalctl -u
ansible-runner-service
-- Logs begin at Tue 2020-10-06 11:12:46 CEST, end at Thu 2020-10-08
17:02:25 CEST. --
-- No entries --
[root@ovmgr1 ansible-runner-service]#


[root@ovmgr1 ansible-runner-service]# cat
/etc/ansible-runner-service/config.yaml

version: 1
playbooks_root_dir: '/usr/share/ovirt-engine/ansible-runner-service-project'
ssh_private_key: '/etc/pki/ovirt-engine/keys/engine_id_rsa'
port: 50001
target_user: root
log_path: '/var/log/ovirt-engine'
[root@ovmgr1 ansible-runner-service]#

I noticed that both on engine and on host the "ansible-runner" package is
not installed. Is it correct and only ansible-runner-service package to be
installed only on the engine?
Also, does the "service" in the name imply that I should have any systemd
or other kind of related service on engine?
Finally, I have to use a proxy for dnf/yum.
To be able to run "engine-setup" on engine I had to set http_proxy and
https_proxy eng variables inside the shell session, because it seems that
engine-setup was not able to leverage the global configuration. Could it be
something similar due to the host having to use a proxy too (that I already
setup in /etc/dnf/dnf.conf)? Just a guess.

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/6VVTX45DRCNZP6MKS4EZ7FHE2EF5OZQL/


[ovirt-users] problems installing standard Linux as nodes in 4.4

2020-10-08 Thread Gianluca Cecchi
Hello,
due to missing megaraid_sas kernel module in RH EL 8 and CentOS 8, I'm
deploying a new oVirt host using CentOS 8 and elrepo kernel driver and not
ovirt node ng.

Based on installation guide:

- install CentOS 8.2 ("Server" chosen as base environment)
- yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
- yum install cockpit-ovirt-dashboard
- yum update
- reboot

Try to add host from engine web admin gui, I get:
Host ov200 installation failed. Failed to execute Ansible host-deploy role:
Failed to execute call to start playbook. . Please check logs for more
details: /var/log/ovirt-engine/ansible-runner-service.log.

Inside the log file above on engine:
2020-10-08 11:58:43,389 - runner_service.controllers.hosts - DEBUG -
Request received, content-type :None
2020-10-08 11:58:43,390 - runner_service.controllers.hosts - INFO -
127.0.0.1 - GET /api/v1/hosts/ov200
2020-10-08 11:58:43,398 - runner_service.controllers.playbooks - DEBUG -
Request received, content-type :application/json; charset=UTF-8
2020-10-08 11:58:43,398 - runner_service.controllers.playbooks - INFO -
127.0.0.1 - POST /api/v1/playbooks/ovirt-host-deploy.yml

Do I have to enable any module or pre-install anything else before adding
it?

BTW: on host

[root@ov200 ~]# rpm -q ansible
ansible-2.9.13-2.el8.noarch
[root@ov200 ~]#

Thanks,
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/FT4S5MRJGJJNMGXCRTSKBCXQZ42LSB5U/


[ovirt-users] Upgrade oVirt from 4.3.10 to 4.4.2 and AD users

2020-10-06 Thread Gianluca Cecchi
Hello,
I'm upgrading a standalone engine with local database and with 3 hosts from
oVirt 4.3.10 to 4.4.2 and I'm cross checking both oVirt and RHV documents.
In my oVirt environment I have integration with AD for web admin access.

Inside RHV upgrade guide docs there is this statement regarding manager
upgrade:
"
Install optional extension packages if they were installed on the Red Hat
Virtualization Manager 4.3 machine.
# yum install ovirt-engine-extension-aaa-ldap
ovirt-engine-extension-aaa-misc ovirt-engine-extension-logger-log4j
NOTE
The configuration for these package extensions must be manually reapplied
because they are not migrated as part of the backup and restore process.
"

In my case I had ovirt-engine-extension-aaa-ldap and
ovirt-engine-extension-aaa-misc installed on 4.3.10.
So after "engine-backup --mode=restore " command I executed:

[root@ovmgr1 ~]# yum install ovirt-engine-extension-aaa-ldap
ovirt-engine-extension-aaa-misc
Last metadata expiration check: 0:01:11 ago on Tue 06 Oct 2020 11:23:04 AM
CEST.
Dependencies resolved.
==
 Package  ArchVersion Repository
  Size
==
Installing:
 ovirt-engine-extension-aaa-ldap  noarch  1.4.1-1.el8 ovirt-4.4
127 k
 ovirt-engine-extension-aaa-misc  noarch  1.1.0-1.el8 ovirt-4.4
 37 k
Installing dependencies:
 unboundid-ldapsdknoarch  4.0.14-2.el8
 ovirt-4.4-centos-ovirt44  4.0 M

Transaction Summary
==
Install  3 Packages

Total download size: 4.2 M
Installed size: 4.5 M

and followed the next upgrade flow steps.
After finishing the engine upgrade with the "engine-setup" step, it seems
actually that I can still connect to my engine with my AD accounts, so that
I don't have to do any manual step described...

Does it match any one other experience?

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


[ovirt-users] Re: engine-setup in 4.4.2 not using yum/dnf proxy?

2020-10-06 Thread Gianluca Cecchi
On Tue, Oct 6, 2020 at 11:33 AM Gianluca Cecchi 
wrote:

> Hello,
> I'm testing upgrade from 4.3.10 to 4.4.2 for a standalone manager with
> local database environment.
> I configured the new engine system as a CentOS 8.2 with a proxy in
> /etc/yum.conf (that is a link to /etc/dnf/dnf.com) and that worked for
> all the steps until engine-setup.
> Now I get this
>
> [root@ovmgr1 ~]# engine-setup
> [ INFO  ] Stage: Initializing
> [ INFO  ] Stage: Environment setup
>   Configuration files:
> /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf,
> /etc/ovirt-engine-setup.conf.d/10-packaging.conf,
> /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf
>   Log file:
> /var/log/ovirt-engine/setup/ovirt-engine-setup-20201006112458-p84x9i.log
>   Version: otopi-1.9.2 (otopi-1.9.2-1.el8)
> [ INFO  ] DNF Downloading 1 files, 0.00KB
> [ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
> [ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
> [ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
> [ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
> [ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
> [ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
> [ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
> [ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
> [ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
> [ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
> [ INFO  ] DNF Downloaded CentOS-8 - AppStream
> [ INFO  ] DNF Errors during downloading metadata for repository
> 'AppStream':
> 
> [ ERROR ] Execution of setup failed
>
> and I see in netstat during the phase
>
> tcp0  1 10.4.192.43:33418   18.225.36.18:80
> SYN_SENT
>
> so it seems it is not using the proxy.
> Do I have to put proxy info into any other file?
>
> Thanks,
> Gianluca
>

It was necessary and sufficient to set both:

[root@ovmgr1 ~]# export http_proxy=my.proxy.host:proxy_port

[root@ovmgr1 ~]# export https_proxy=my.proxy.host:proxy_port

It seems some repos are using http and other https.
A smarter way would be to leverage the already systemwide dnf proxy config.

Anyway the upgrade of the engine from 4.3.10 to 4.4.2 went smooth and ok
and I was able to move VMs from a host to start upgrading it.
Let's see how it goes.

HIH others,
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/GW4YI5D7TTKCAWY3N4BZ3QOIPLIN66VI/


[ovirt-users] Re: ovirt-engine and host certification is expired in ovirt4.0

2020-10-06 Thread Gianluca Cecchi
On Tue, Oct 6, 2020 at 11:33 AM Martin Perina  wrote:

> Hi,
>
> we have mentioned several times that it doesn't make sense to oVirt on a
> single host setup. So you really need to add 2nd host to your setup, move
> the 1st host to Maintenance and execute Enroll certificates.
>
> Regards,
> Martin
>
>
>
Again, just fallen from the moon this morning?

It is indeed true that some scenarios, like upgrading a self hosted engine
environment composed by only a single host, are not coverable and need some
extra work, but the single host environment is usable
Did you miss this perhaps for RHV 4.4 (and the same for 4.3):

https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure_for_virtualization/1.8/html/deploying_red_hat_hyperconverged_infrastructure_for_virtualization_on_a_single_node/index

?

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


[ovirt-users] Re: oVirt Node 4.4.2 is now generally available

2020-10-06 Thread Gianluca Cecchi
On Tue, Oct 6, 2020 at 11:25 AM Martin Perina  wrote:

>
>> You say to drive a command form the engine that is a VM that runs inside
>> the host, but ask to shutdown VMs running on host before...
>> This is a self hosted engine composed by only one single host.
>> Normally I would use the procedure from the engine web admin gui, one
>> host at a time, but with single host it is not possible.
>>
>
> We have said several times, that it doesn't make sense to use oVirt on a
> single host system. So you either need to attach 2nd host to your setup
> (preferred) or shutdown all VMS and run manual upgrade of your host OS
>
>
We who
In old times there was the all-in-one setup that was substituted from
single host HCI ... developers also put extra efforts to setup the wizard
comprising the single host scenario.
Obviously it is aimed at test bed / devel / home environments, not
production ones.
Do you want me to send you the list of bugzilla contributed by users using
single host environments that helped Red Hat to have a better working RHV
too?

Please think more deeply next time, thanks

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


[ovirt-users] engine-setup in 4.4.2 not using yum/dnf proxy?

2020-10-06 Thread Gianluca Cecchi
Hello,
I'm testing upgrade from 4.3.10 to 4.4.2 for a standalone manager with
local database environment.
I configured the new engine system as a CentOS 8.2 with a proxy in
/etc/yum.conf (that is a link to /etc/dnf/dnf.com) and that worked for all
the steps until engine-setup.
Now I get this

[root@ovmgr1 ~]# engine-setup
[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup
  Configuration files:
/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf,
/etc/ovirt-engine-setup.conf.d/10-packaging.conf,
/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf
  Log file:
/var/log/ovirt-engine/setup/ovirt-engine-setup-20201006112458-p84x9i.log
  Version: otopi-1.9.2 (otopi-1.9.2-1.el8)
[ INFO  ] DNF Downloading 1 files, 0.00KB
[ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO  ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO  ] DNF Downloaded CentOS-8 - AppStream
[ INFO  ] DNF Errors during downloading metadata for repository 'AppStream':

[ ERROR ] Execution of setup failed

and I see in netstat during the phase

tcp0  1 10.4.192.43:33418   18.225.36.18:80
SYN_SENT

so it seems it is not using the proxy.
Do I have to put proxy info into any other file?

Thanks,
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/D5WQSM7OZNKJQK3L5CN367W2TRVZZVHZ/


[ovirt-users] Re: oVirt Node 4.4.2 is now generally available

2020-10-05 Thread Gianluca Cecchi
On Mon, Oct 5, 2020 at 3:13 PM Dana Elfassy  wrote:

> Can you shutdown the vms just for the upgrade process?
>
> On Mon, Oct 5, 2020 at 1:57 PM Gianluca Cecchi 
> wrote:
>
>> On Mon, Oct 5, 2020 at 12:52 PM Dana Elfassy  wrote:
>>
>>> In order to run the playbooks you would also need the parameters that
>>> they use - some are set on the engine side
>>> Why can't you upgrade the host from the engine admin portal?
>>>
>>>
>> Because when you upgrade a host you put it into maintenance before.
>> And this implies no VMs in execution on it.
>> But if you are in a single host composed environment you cannot
>>
>> Gianluca
>>
>
we are talking about chicken-egg problem.

You say to drive a command form the engine that is a VM that runs inside
the host, but ask to shutdown VMs running on host before...
This is a self hosted engine composed by only one single host.
Normally I would use the procedure from the engine web admin gui, one host
at a time, but with single host it is not possible.

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/3ZU43KQXYJO43CWTDDT733H4YZS4JA2U/


[ovirt-users] Re: oVirt Node 4.4.2 is now generally available

2020-10-05 Thread Gianluca Cecchi
On Mon, Oct 5, 2020 at 12:52 PM Dana Elfassy  wrote:

> In order to run the playbooks you would also need the parameters that they
> use - some are set on the engine side
> Why can't you upgrade the host from the engine admin portal?
>
>
Because when you upgrade a host you put it into maintenance before.
And this implies no VMs in execution on it.
But if you are in a single host composed environment you cannot

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


[ovirt-users] Re: oVirt Node 4.4.2 is now generally available

2020-10-05 Thread Gianluca Cecchi
On Mon, Oct 5, 2020 at 10:37 AM Dana Elfassy  wrote:

> Yes.
> The additional main tasks that we execute during host upgrade besides
> updating packages are certificates related (check for certificates
> validity, enroll certificates) , configuring advanced virtualization and
> lvm filter
> Dana
>
>
Thanks,
What if I want to directly execute on the host? Any command / pointer to
run after "yum update"?
This is to cover a scenario with single host, where I cannot drive it from
the engine...

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/6BDBZMEDS4NDV7D6MGLF2C35M4G66V5K/


[ovirt-users] Re: oVirt Node 4.4.2 is now generally available

2020-10-05 Thread Gianluca Cecchi
On Mon, Oct 5, 2020 at 8:31 AM Sandro Bonazzola  wrote:

>
>> OK, so I tried on my single host HCI installed with ovirt-node-ng 4.4.0
>> and gluster wizard and never update until now.
>> Updated self hosted engine to 4.4.2 without problems.
>>
>> My host doesn't have any filter or global_filter set up in lvm.conf  in
>> 4.4.0.
>>
>> So I update it:
>>
>> [root@ovirt01 vdsm]# yum update
>>
>
> Please use the update command from the engine admin portal.
> The ansible code running from there also performs additional steps other
> than just yum update.
> +Dana Elfassy  can you elaborate on other steps
> performed during the upgrade?
>
>
Yes, in general.
But for single host environments is not possible, at least I think.
Because you are upgrading the host where the engine is running...

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


[ovirt-users] Re: oVirt Node 4.4.2 is now generally available

2020-10-05 Thread Gianluca Cecchi
On Mon, Oct 5, 2020 at 2:19 AM Nir Soffer  wrote:

> On Sun, Oct 4, 2020 at 6:09 PM Amit Bawer  wrote:
> >
> >
> >
> > On Sun, Oct 4, 2020 at 5:28 PM Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
> >>
> >> On Sun, Oct 4, 2020 at 10:21 AM Amit Bawer  wrote:
> >>>
> >>>
> >>>
> >>> Since there wasn't a filter set on the node, the 4.4.2 update added
> the default filter for the root-lv pv
> >>> if there was some filter set before the upgrade, it would not have
> been added by the 4.4.2 update.
> >>>>
> >>>>
> >>
> >> Do you mean that I will get the same problem upgrading from 4.4.2 to an
> upcoming 4.4.3, as also now I don't have any filter set?
> >> This would not be desirable
> >
> > Once you have got back into 4.4.2, it's recommended to set the lvm
> filter to fit the pvs you use on your node
> > for the local root pv you can run
> > # vdsm-tool config-lvm-filter -y
> > For the gluster bricks you'll need to add their uuids to the filter as
> well.
>
> vdsm-tool is expected to add all the devices needed by the mounted
> logical volumes, so adding devices manually should not be needed.
>
> If this does not work please file a bug and include all the info to
> reproduce
> the issue.
>
>
I don't know what exactly happened when I installed ovirt-ng-node in 4.4.0,
but the effect was that no filter at all was set up in lvm.conf, and so the
problem I had upgrading to 4.4.2.
Any way to see related logs for 4.4.0? In which phase of the install of the
node itself or of the gluster based wizard is it supposed to run the
vdsm-tool command?

Right now in 4.4.2 I get this output, so it seems it works in 4.4.2:

"
[root@ovirt01 ~]# vdsm-tool config-lvm-filter
Analyzing host...
Found these mounted logical volumes on this host:

  logical volume:  /dev/mapper/gluster_vg_sda-gluster_lv_data
  mountpoint:  /gluster_bricks/data
  devices:
/dev/disk/by-id/lvm-pv-uuid-5D4JSI-vqEc-ir4o-BGnG-sZmh-ILjS-jgzICr

  logical volume:  /dev/mapper/gluster_vg_sda-gluster_lv_engine
  mountpoint:  /gluster_bricks/engine
  devices:
/dev/disk/by-id/lvm-pv-uuid-5D4JSI-vqEc-ir4o-BGnG-sZmh-ILjS-jgzICr

  logical volume:  /dev/mapper/gluster_vg_sda-gluster_lv_vmstore
  mountpoint:  /gluster_bricks/vmstore
  devices:
/dev/disk/by-id/lvm-pv-uuid-5D4JSI-vqEc-ir4o-BGnG-sZmh-ILjS-jgzICr

  logical volume:  /dev/mapper/onn-home
  mountpoint:  /home
  devices:
/dev/disk/by-id/lvm-pv-uuid-52iT6N-L9sU-ubqE-6vPt-dn7T-W19c-NOXjc7

  logical volume:  /dev/mapper/onn-ovirt--node--ng--4.4.2--0.20200918.0+1
  mountpoint:  /
  devices:
/dev/disk/by-id/lvm-pv-uuid-52iT6N-L9sU-ubqE-6vPt-dn7T-W19c-NOXjc7

  logical volume:  /dev/mapper/onn-swap
  mountpoint:  [SWAP]
  devices:
/dev/disk/by-id/lvm-pv-uuid-52iT6N-L9sU-ubqE-6vPt-dn7T-W19c-NOXjc7

  logical volume:  /dev/mapper/onn-tmp
  mountpoint:  /tmp
  devices:
/dev/disk/by-id/lvm-pv-uuid-52iT6N-L9sU-ubqE-6vPt-dn7T-W19c-NOXjc7

  logical volume:  /dev/mapper/onn-var
  mountpoint:  /var
  devices:
/dev/disk/by-id/lvm-pv-uuid-52iT6N-L9sU-ubqE-6vPt-dn7T-W19c-NOXjc7

  logical volume:  /dev/mapper/onn-var_crash
  mountpoint:  /var/crash
  devices:
/dev/disk/by-id/lvm-pv-uuid-52iT6N-L9sU-ubqE-6vPt-dn7T-W19c-NOXjc7

  logical volume:  /dev/mapper/onn-var_log
  mountpoint:  /var/log
  devices:
/dev/disk/by-id/lvm-pv-uuid-52iT6N-L9sU-ubqE-6vPt-dn7T-W19c-NOXjc7

  logical volume:  /dev/mapper/onn-var_log_audit
  mountpoint:  /var/log/audit
  devices:
/dev/disk/by-id/lvm-pv-uuid-52iT6N-L9sU-ubqE-6vPt-dn7T-W19c-NOXjc7

This is the recommended LVM filter for this host:

  filter = [
"a|^/dev/disk/by-id/lvm-pv-uuid-52iT6N-L9sU-ubqE-6vPt-dn7T-W19c-NOXjc7$|",
"a|^/dev/disk/by-id/lvm-pv-uuid-5D4JSI-vqEc-ir4o-BGnG-sZmh-ILjS-jgzICr$|",
"r|.*|" ]

This filter allows LVM to access the local devices used by the
hypervisor, but not shared storage owned by Vdsm. If you add a new
device to the volume group, you will need to edit the filter manually.

To use the recommended filter we need to add multipath
blacklist in /etc/multipath/conf.d/vdsm_blacklist.conf:

  blacklist {
  wwid "Samsung_SSD_850_EVO_500GB_S2RBNXAH108545V"
  wwid "Samsung_SSD_850_EVO_M.2_250GB_S24BNXAH209481K"
  }


Configure host? [yes,NO]

"
Does this mean that answering "yes" I will get both lvm and multipath
related files modified?

Right now my multipath is configured this way:

[root@ovirt01 ~]# grep -v "^#" /etc/multipath.conf | grep -v "^#" |
grep -v "^$"
defaults {
polling_interval5
no_path_retry   4
user_friendly_names no
flush_on_last_del   yes
fast_io_fail_tmo5
dev_loss_tmo  

[ovirt-users] Re: oVirt Node 4.4.2 is now generally available

2020-10-04 Thread Gianluca Cecchi
On Sun, Oct 4, 2020 at 10:21 AM Amit Bawer  wrote:

>
>
> Since there wasn't a filter set on the node, the 4.4.2 update added the
> default filter for the root-lv pv
> if there was some filter set before the upgrade, it would not have been
> added by the 4.4.2 update.
>
>>
>>
Do you mean that I will get the same problem upgrading from 4.4.2 to an
upcoming 4.4.3, as also now I don't have any filter set?
This would not be desirable



>
>> Right now only two problems:
>>
>> 1) a long running problem that from engine web admin all the volumes are
>> seen as up and also the storage domains up, while only the hosted engine
>> one is up, while "data" and vmstore" are down, as I can verify from the
>> host, only one /rhev/data-center/ mount:
>>
>> [snip]

>
>> I already reported this, but I don't know if there is yet a bugzilla open
>> for it.
>>
> Did you get any response for the original mail? haven't seen it on the
> users-list.
>

I think it was this thread related to 4.4.0 released and question about
auto-start of VMs.
A script from Derek that tested if domains were active and got false
positive, and my comments about the same registered behaviour:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/25KYZTFKX5Y4UOEL2SNHUUC7M4WAJ5NO/

But I think there was no answer on that particular item/problem.
Indeed I think you can easily reproduce, I don't know if only with Gluster
or also with other storage domains.
I don't know if it can have a part the fact that on the last host during a
whole shutdown (and the only host in case of single host) you have to run
the script
/usr/share/glusterfs/scripts/stop-all-gluster-processes.sh
otherwise you risk not to get a complete shutdown sometimes.
And perhaps this stop can have an influence on the following startup.
In any case the web admin gui (and the API access) should not show the
domains active when they are not. I think there is a bug in the code that
checks this.


>
>> 2) I see that I cannot connect to cockpit console of node.
>>
>> [snip]

> NOTE: the ost is not resolved by DNS but I put an entry in my hosts client.
>>
> Might be required to set DNS for authenticity, maybe other members on the
> list could tell better.
>

It would be the first time I see it. The access to web admin GUI works ok
even without DNS resolution.
I'm not sure if I had the same problem with the cockpit host console on
4.4.0.

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


[ovirt-users] Re: oVirt Node 4.4.2 is now generally available

2020-10-03 Thread Gianluca Cecchi
On Sat, Oct 3, 2020 at 9:42 PM Amit Bawer  wrote:

>
>
> On Sat, Oct 3, 2020 at 10:24 PM Amit Bawer  wrote:
>
>>
>>
>> For the gluster bricks being filtered out in 4.4.2, this seems like [1].
>>
>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1883805
>>
>
> Maybe remove the lvm filter from /etc/lvm/lvm.conf while in 4.4.2
> maintenance mode
> if the fs is mounted as read only, try
>
> mount -o remount,rw /
>
> sync and try to reboot 4.4.2.
>
>
Indeed if i run, when in emergency shell in 4.4.2, the command:

lvs --config 'devices { filter = [ "a|.*|" ] }'

I see also all the gluster volumes, so I think the update injected the
nasty filter.
Possibly during update the command
# vdsm-tool config-lvm-filter -y
was executed and erroneously created the filter?

Anyway remounting read write the root filesystem and removing the filter
line from lvm.conf and rebooting worked and 4.4.2 booted ok and I was able
to exit global maintenance and have the engine up.

Thanks Amit for the help and all the insights.

Right now only two problems:

1) a long running problem that from engine web admin all the volumes are
seen as up and also the storage domains up, while only the hosted engine
one is up, while "data" and vmstore" are down, as I can verify from the
host, only one /rhev/data-center/ mount:

[root@ovirt01 ~]# df -h
Filesystem  Size  Used Avail
Use% Mounted on
devtmpfs 16G 0   16G
0% /dev
tmpfs16G   16K   16G
1% /dev/shm
tmpfs16G   18M   16G
1% /run
tmpfs16G 0   16G
0% /sys/fs/cgroup
/dev/mapper/onn-ovirt--node--ng--4.4.2--0.20200918.0+1  133G  3.9G  129G
3% /
/dev/mapper/onn-tmp1014M   40M  975M
4% /tmp
/dev/mapper/gluster_vg_sda-gluster_lv_engine100G  9.0G   91G
9% /gluster_bricks/engine
/dev/mapper/gluster_vg_sda-gluster_lv_data  500G  126G  375G
 26% /gluster_bricks/data
/dev/mapper/gluster_vg_sda-gluster_lv_vmstore90G  6.9G   84G
8% /gluster_bricks/vmstore
/dev/mapper/onn-home   1014M   40M  975M
4% /home
/dev/sdb2   976M  307M  603M
 34% /boot
/dev/sdb1   599M  6.8M  593M
2% /boot/efi
/dev/mapper/onn-var  15G  263M   15G
2% /var
/dev/mapper/onn-var_log 8.0G  541M  7.5G
7% /var/log
/dev/mapper/onn-var_crash10G  105M  9.9G
2% /var/crash
/dev/mapper/onn-var_log_audit   2.0G   79M  2.0G
4% /var/log/audit
ovirt01st.lutwyn.storage:/engine100G   10G   90G
 10% /rhev/data-center/mnt/glusterSD/ovirt01st.lutwyn.storage:_engine
tmpfs   3.2G 0  3.2G
0% /run/user/1000
[root@ovirt01 ~]#

I can also wait 10 minutes and no change. The way I use to exit from this
stalled situation is power on a VM, so that obviously it fails
VM f32 is down with error. Exit message: Unable to get volume size for
domain d39ed9a3-3b10-46bf-b334-e8970f5deca1 volume
242d16c6-1fd9-4918-b9dd-0d477a86424c.
10/4/20 12:50:41 AM

and suddenly all the data storage domains are deactivated (from engine
point of view, because actually they were not active...):
Storage Domain vmstore (Data Center Default) was deactivated by system
because it's not visible by any of the hosts.
10/4/20 12:50:31 AM

and I can go in Data Centers --> Default --> Storage and activate "vmstore"
and "data" storage domains and suddenly I get them activated and
filesystems mounted.

[root@ovirt01 ~]# df -h | grep rhev
ovirt01st.lutwyn.storage:/engine100G   10G   90G
 10% /rhev/data-center/mnt/glusterSD/ovirt01st.lutwyn.storage:_engine
ovirt01st.lutwyn.storage:/data  500G  131G  370G
 27% /rhev/data-center/mnt/glusterSD/ovirt01st.lutwyn.storage:_data
ovirt01st.lutwyn.storage:/vmstore90G  7.8G   83G
9% /rhev/data-center/mnt/glusterSD/ovirt01st.lutwyn.storage:_vmstore
[root@ovirt01 ~]#

and VM starts ok now.

I already reported this, but I don't know if there is yet a bugzilla open
for it.

2) I see that I cannot connect to cockpit console of node.

In firefox (version 80) in my Fedora 31 I get:
"
Secure Connection Failed

An error occurred during a connection to ovirt01.lutwyn.local:9090.
PR_CONNECT_RESET_ERROR

The page you are trying to view cannot be shown because the
authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.

Learn more…
"
In Chrome (build 85.0.4183.121)

"
Your connection is not private
Attackers might be trying to steal your information from
ovirt01.lutwyn.local (for example, 

[ovirt-users] Re: oVirt Node 4.4.2 is now generally available

2020-10-03 Thread Gianluca Cecchi
On Sat, Oct 3, 2020 at 6:33 PM Gianluca Cecchi 
wrote:

> Sorry I see that there was an error in the lsinitrd command in 4.4.2,
> inerting the "-f" position.
> Here the screenshot that shows anyway no filter active:
>
> https://drive.google.com/file/d/19VmgvsHU2DhJCRzCbO9K_Xyr70x4BqXX/view?usp=sharing
>
> Gianluca
>
>
> On Sat, Oct 3, 2020 at 6:26 PM Gianluca Cecchi 
> wrote:
>
>> On Sat, Oct 3, 2020 at 4:06 PM Amit Bawer  wrote:
>>
>>> From the info it seems that startup panics because gluster bricks cannot
>>> be mounted.
>>>
>>>
>> Yes, it is so
>> This is a testbed NUC I use for testing.
>> It has 2 disks, the one named sdb is where ovirt node has been installed.
>> The one named sda is where I configured gluster though the wizard,
>> configuring the 3 volumes for engine, vm, data
>>
>> The filter that you do have in the 4.4.2 screenshot should correspond to
>>> your root pv,
>>> you can confirm that by doing (replace the pv-uuid with the one from
>>> your filter):
>>>
>>> #udevadm info
>>>  /dev/disk/by-id/lvm-pv-uuid-DXgufc-7riC-TqhU-f8yH-EfZt-ivvH-TVcnEQ
>>> P:
>>> /devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sda/sda2
>>> N: sda2
>>> S: disk/by-id/ata-QEMU_HARDDISK_QM3-part2
>>> S: disk/by-id/lvm-pv-uuid-DXgufc-7riC-TqhU-f8yH-EfZt-ivvH-TVcnEQ
>>>
>>> In this case sda2 is the partition of the root-lv shown by lsblk.
>>>
>>
>> Yes it is so. Of course it works only in 4.4.0. In 4.4.2 there is no
>> special file created of type /dev/disk/by-id/
>> See here for udevadm command on 4.4.0 that shows sdb3 that is the
>> partition corresponding to PV of root disk
>>
>> https://drive.google.com/file/d/1-bsa0BLNHINFs48X8LGUafjFnUGPCsCH/view?usp=sharing
>>
>>
>>
>>> Can you give the output of lsblk on your node?
>>>
>>
>> Here lsblk as seen by 4.4.0 with gluster volumes on sda:
>>
>> https://drive.google.com/file/d/1Czx28YKttmO6f6ldqW7TmxV9SNWzZKSQ/view?usp=sharing
>>
>> ANd here lsblk as seen from 4.4.2 with an empty sda:
>>
>> https://drive.google.com/file/d/1wERp9HkFxbXVM7rH3aeIAT-IdEjseoA0/view?usp=sharing
>>
>>
>>> Can you check that the same filter is in initramfs?
>>> # lsinitrd -f  /etc/lvm/lvm.conf | grep filter
>>>
>>
>> Here the command from 4.4.0 that shows no filter
>>
>> https://drive.google.com/file/d/1NKXAhkjh6bqHWaDZgtbfHQ23uqODWBrO/view?usp=sharing
>>
>> And here from 4.4.2 emergency mode, where I have to use the path
>> /boot/ovirt-node-ng-4.4.2-0/initramfs-
>> because no initrd file in /boot (in screenshot you also see output of "ll
>> /boot)
>>
>> https://drive.google.com/file/d/1ilZ-_GKBtkYjJX-nRTybYihL9uXBJ0da/view?usp=sharing
>>
>>
>>
>>> We have the following tool on the hosts
>>> # vdsm-tool config-lvm-filter -y
>>> it only sets the filter for local lvm devices, this is run as part of
>>> deployment and upgrade when done from
>>> the engine.
>>>
>>> If you have other volumes which have to be mounted as part of your
>>> startup
>>> then you should add their uuids to the filter as well.
>>>
>>
>> I didn't anything special in 4.4.0: I installed node on the intended
>> disk, that was seen as sdb and then through the single node hci wizard I
>> configured the gluster volumes on sda
>>
>> Any suggestion on what to do on 4.4.2 initrd or running correct dracut
>> command from 4.4.0 to correct initramfs of 4.4.2?
>>
>> BTW: could in the mean time if necessary also boot from 4.4.0 and let it
>> go with engine in 4.4.2?
>>
>> Thanks,
>> Gianluca
>>
>

Two many photos... ;-)

I used the 4.4.0 initramfs.
Here the output using the 4.4.2 initramfs

https://drive.google.com/file/d/1yLzJzokK5C1LHNuFbNoXWHXfzFncXe0O/view?usp=sharing

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


[ovirt-users] Re: oVirt Node 4.4.2 is now generally available

2020-10-03 Thread Gianluca Cecchi
Sorry I see that there was an error in the lsinitrd command in 4.4.2,
inerting the "-f" position.
Here the screenshot that shows anyway no filter active:
https://drive.google.com/file/d/19VmgvsHU2DhJCRzCbO9K_Xyr70x4BqXX/view?usp=sharing

Gianluca


On Sat, Oct 3, 2020 at 6:26 PM Gianluca Cecchi 
wrote:

> On Sat, Oct 3, 2020 at 4:06 PM Amit Bawer  wrote:
>
>> From the info it seems that startup panics because gluster bricks cannot
>> be mounted.
>>
>>
> Yes, it is so
> This is a testbed NUC I use for testing.
> It has 2 disks, the one named sdb is where ovirt node has been installed.
> The one named sda is where I configured gluster though the wizard,
> configuring the 3 volumes for engine, vm, data
>
> The filter that you do have in the 4.4.2 screenshot should correspond to
>> your root pv,
>> you can confirm that by doing (replace the pv-uuid with the one from your
>> filter):
>>
>> #udevadm info
>>  /dev/disk/by-id/lvm-pv-uuid-DXgufc-7riC-TqhU-f8yH-EfZt-ivvH-TVcnEQ
>> P:
>> /devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sda/sda2
>> N: sda2
>> S: disk/by-id/ata-QEMU_HARDDISK_QM3-part2
>> S: disk/by-id/lvm-pv-uuid-DXgufc-7riC-TqhU-f8yH-EfZt-ivvH-TVcnEQ
>>
>> In this case sda2 is the partition of the root-lv shown by lsblk.
>>
>
> Yes it is so. Of course it works only in 4.4.0. In 4.4.2 there is no
> special file created of type /dev/disk/by-id/
> See here for udevadm command on 4.4.0 that shows sdb3 that is the
> partition corresponding to PV of root disk
>
> https://drive.google.com/file/d/1-bsa0BLNHINFs48X8LGUafjFnUGPCsCH/view?usp=sharing
>
>
>
>> Can you give the output of lsblk on your node?
>>
>
> Here lsblk as seen by 4.4.0 with gluster volumes on sda:
>
> https://drive.google.com/file/d/1Czx28YKttmO6f6ldqW7TmxV9SNWzZKSQ/view?usp=sharing
>
> ANd here lsblk as seen from 4.4.2 with an empty sda:
>
> https://drive.google.com/file/d/1wERp9HkFxbXVM7rH3aeIAT-IdEjseoA0/view?usp=sharing
>
>
>> Can you check that the same filter is in initramfs?
>> # lsinitrd -f  /etc/lvm/lvm.conf | grep filter
>>
>
> Here the command from 4.4.0 that shows no filter
>
> https://drive.google.com/file/d/1NKXAhkjh6bqHWaDZgtbfHQ23uqODWBrO/view?usp=sharing
>
> And here from 4.4.2 emergency mode, where I have to use the path
> /boot/ovirt-node-ng-4.4.2-0/initramfs-
> because no initrd file in /boot (in screenshot you also see output of "ll
> /boot)
>
> https://drive.google.com/file/d/1ilZ-_GKBtkYjJX-nRTybYihL9uXBJ0da/view?usp=sharing
>
>
>
>> We have the following tool on the hosts
>> # vdsm-tool config-lvm-filter -y
>> it only sets the filter for local lvm devices, this is run as part of
>> deployment and upgrade when done from
>> the engine.
>>
>> If you have other volumes which have to be mounted as part of your startup
>> then you should add their uuids to the filter as well.
>>
>
> I didn't anything special in 4.4.0: I installed node on the intended disk,
> that was seen as sdb and then through the single node hci wizard I
> configured the gluster volumes on sda
>
> Any suggestion on what to do on 4.4.2 initrd or running correct dracut
> command from 4.4.0 to correct initramfs of 4.4.2?
>
> BTW: could in the mean time if necessary also boot from 4.4.0 and let it
> go with engine in 4.4.2?
>
> Thanks,
> 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/GMP6UHTWIR3BCCNEJT6KU4QRORFSC5DB/


[ovirt-users] Re: oVirt Node 4.4.2 is now generally available

2020-10-03 Thread Gianluca Cecchi
On Sat, Oct 3, 2020 at 4:06 PM Amit Bawer  wrote:

> From the info it seems that startup panics because gluster bricks cannot
> be mounted.
>
>
Yes, it is so
This is a testbed NUC I use for testing.
It has 2 disks, the one named sdb is where ovirt node has been installed.
The one named sda is where I configured gluster though the wizard,
configuring the 3 volumes for engine, vm, data

The filter that you do have in the 4.4.2 screenshot should correspond to
> your root pv,
> you can confirm that by doing (replace the pv-uuid with the one from your
> filter):
>
> #udevadm info
>  /dev/disk/by-id/lvm-pv-uuid-DXgufc-7riC-TqhU-f8yH-EfZt-ivvH-TVcnEQ
> P:
> /devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sda/sda2
> N: sda2
> S: disk/by-id/ata-QEMU_HARDDISK_QM3-part2
> S: disk/by-id/lvm-pv-uuid-DXgufc-7riC-TqhU-f8yH-EfZt-ivvH-TVcnEQ
>
> In this case sda2 is the partition of the root-lv shown by lsblk.
>

Yes it is so. Of course it works only in 4.4.0. In 4.4.2 there is no
special file created of type /dev/disk/by-id/
See here for udevadm command on 4.4.0 that shows sdb3 that is the partition
corresponding to PV of root disk
https://drive.google.com/file/d/1-bsa0BLNHINFs48X8LGUafjFnUGPCsCH/view?usp=sharing



> Can you give the output of lsblk on your node?
>

Here lsblk as seen by 4.4.0 with gluster volumes on sda:
https://drive.google.com/file/d/1Czx28YKttmO6f6ldqW7TmxV9SNWzZKSQ/view?usp=sharing

ANd here lsblk as seen from 4.4.2 with an empty sda:
https://drive.google.com/file/d/1wERp9HkFxbXVM7rH3aeIAT-IdEjseoA0/view?usp=sharing


> Can you check that the same filter is in initramfs?
> # lsinitrd -f  /etc/lvm/lvm.conf | grep filter
>

Here the command from 4.4.0 that shows no filter
https://drive.google.com/file/d/1NKXAhkjh6bqHWaDZgtbfHQ23uqODWBrO/view?usp=sharing

And here from 4.4.2 emergency mode, where I have to use the path
/boot/ovirt-node-ng-4.4.2-0/initramfs-
because no initrd file in /boot (in screenshot you also see output of "ll
/boot)
https://drive.google.com/file/d/1ilZ-_GKBtkYjJX-nRTybYihL9uXBJ0da/view?usp=sharing



> We have the following tool on the hosts
> # vdsm-tool config-lvm-filter -y
> it only sets the filter for local lvm devices, this is run as part of
> deployment and upgrade when done from
> the engine.
>
> If you have other volumes which have to be mounted as part of your startup
> then you should add their uuids to the filter as well.
>

I didn't anything special in 4.4.0: I installed node on the intended disk,
that was seen as sdb and then through the single node hci wizard I
configured the gluster volumes on sda

Any suggestion on what to do on 4.4.2 initrd or running correct dracut
command from 4.4.0 to correct initramfs of 4.4.2?

BTW: could in the mean time if necessary also boot from 4.4.0 and let it go
with engine in 4.4.2?

Thanks,
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/VV4NAZ6XFITMYPRDMHRWVWOMFCASTKY6/


[ovirt-users] oVirt 4.3.10 and ansible default timeouts

2020-10-02 Thread Gianluca Cecchi
Hello,
in the past when I was in 4.3.7 I used this file:
/etc/ovirt-engine/engine.conf.d/99-ansible-playbook-timeout.conf
with
ANSIBLE_PLAYBOOK_EXEC_DEFAULT_TIMEOUT=80

to bypass the default of 30 minutes at that time.
I updated in steps to 4.3.8 (in February), 4.3.9 (in April) and 4.3.10 (in
July).

Due to an error on my side I noticed that the task for which I extended the
ansible timeout (this task I didn't execute anymore in latest months) fails
with timeout after 80 minutes indeed.
With the intent to extend again the custom timeout I went to
/usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf, provided
by ovirt-engine-backend-4.3.10.4-1.el7.noarch
and actually I see this inside:
"
# Specify the ansible-playbook command execution timeout in minutes. It's
used for any task, which executes
# AnsibleExecutor class. To change the value permanentaly create a conf
file 99-ansible-playbook-timeout.conf in
# /etc/ovirt-engine/engine.conf.d/
ANSIBLE_PLAYBOOK_EXEC_DEFAULT_TIMEOUT=120
"
and the file seems the original provided, not tampered:

[root@ovmgr1 test_backup]# rpm -qvV
ovirt-engine-backend-4.3.10.4-1.el7.noarch | grep virt-engine.conf$
./usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf
[root@ovmgr1 test_backup]#

So the question is: has the default intended value passed to 120 in 4.3.10
(or in any version after 4.3.7)?

Thanks,
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/WXFVIYC4LYOQHWU4IGKGVLNQ7OFVPENI/


[ovirt-users] Re: VM AutoStart

2020-10-01 Thread Gianluca Cecchi
On Wed, Sep 30, 2020 at 9:14 PM Jeremey Wise  wrote:

> i would like to eventually go ansible route..  and was starting down that
> path but this is fabulous.
>
> I will modify and post how it went.
>
> One question:  How /where do you set this saved new and delicious script
> so once oVirt-engine comes up... it runs?
>
> Thanks
>
>
This was the original thread where Derek discussed about VM autostart:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/2SWGNCELQXAQ6RB6KPQ3RR62G63OLKAS/

And this was my answer regarding the possible Ansible route:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/46MHN2NYGIBP736RICI2EOYQERD7Z27N/

HIH,
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/USJDFFO4U2X5WFQRFKQUMXSXHOOED2ZM/


[ovirt-users] Source storage domain info in storage live migration

2020-09-29 Thread Gianluca Cecchi
Hello,
having to monitor and check live storage migrations, it seems to me that
scrolling through events I can see information about the target storage
domain name, but nothing about the source. Is it correct?

Can it be added? Which kind of rfe bugzilla should I use in case? Against
what?

Thanks,
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/JJDHV2QV43Y2BAC5IGSOJZEWLXUM55HZ/


[ovirt-users] Re: oVirt Node 4.4.2 is now generally available

2020-09-25 Thread Gianluca Cecchi
On Fri, Sep 25, 2020 at 1:57 PM Sandro Bonazzola 
wrote:

> oVirt Node 4.4.2 is now generally available
>
> The oVirt project is pleased to announce the general availability of oVirt
> Node 4.4.2 , as of September 25th, 2020.
>
> This release completes the oVirt 4.4.2 release published on September 17th
>

Thanks fir the news!

How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1
>
>
> 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.2 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.2 (redeploy in case of already being on 4.4.2).
>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.
>
>
>
What if I'm currently in 4.4.0 and want to upgrade to 4.4.2? Do I have to
follow the same steps as if I were in 4.4.1 or what?
I would like to avoid going through 4.4.1 if possible.

Thanks,
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/PI2LS3NCULH3FXQKBSB4IGXLKUBXE6UL/


[ovirt-users] Re: info on iSCSI connection setup in oVirt 4.4

2020-09-23 Thread Gianluca Cecchi
On Wed, Sep 23, 2020 at 1:22 PM Ales Musil  wrote:

>
>
> On Wed, Sep 23, 2020 at 1:18 PM Nir Soffer  wrote:
>
>> On Wed, Sep 23, 2020 at 1:29 PM Gianluca Cecchi
>>  wrote:
>> >
>> > Hello,
>> > supposing to have a node that connects to an iSCSI storage domain in
>> oVirt 4.4, is there any particular requirement in the configuration of the
>> network adapter (ifcfg-eno1 file) when I pre-configure the server OS?
>> > Eg, do I need to have it managed by NetworkManager in 4.4? Can I
>> instead set NM_CONTROLLED=no for this controller?
>>
>> 4.4 is using NetworkManager, so it is unlikely be able to manage the nic
>> in the
>> suggested configuration.
>>
>> Adding Ales to add more info on this.
>>
>> Nir
>>
>>
> As Nir said, 4.4 is using NetworkManager to manage every network on the
> host.
> What would be the reason to disable it? The networking should work the
> same way at least from
> oVirt point of view.
>
> Best regards,
> Ales
>
> --
>
> Ales Musil
>
> Software Engineer - RHV Network
>
> Red Hat EMEA <https://www.redhat.com>
>
> amu...@redhat.comIM: amusil
> <https://red.ht/sig>
>

In this particular case I would like to see if NetworkManager could be in
any way responsible for some disconnect/reconnect events we are registering
when pushing to the iSCSI storage.
But I'm not sure about it, only a test I would like to do (mainly to
exclude it), as I also see NetworkManager registered events about the state
of the link.
I'm more inclined to think that the problem could be related to the ixgbe
10gb kernel module shipped with 4.4.1 ovirt node ng.
we see this in messages:

Sep 23 08:00:46 host3 kernel: ixgbe :18:00.1 eno2: NIC Link is Down
Sep 23 08:00:55 host3 kernel: connection1:0: ping timeout of 5 secs
expired, recv timeout 5, last rx 4348764427, last ping 4348769472, now
4348774912
Sep 23 08:00:55 host3 kernel: connection1:0: detected conn error (1022)
Sep 23 08:00:55 host3 kernel: sd 15:0:0:0: [sdb] tag#30 FAILED Result:
hostbyte=DID_TRANSPORT_DISRUPTED driverbyte=DRIVER_OK cmd_age=6s
Sep 23 08:00:55 host3 kernel: sd 15:0:0:0: [sdb] tag#30 CDB: Test Unit
Ready 00 00 00 00 00 00
Sep 23 08:00:55 host3 kernel: sd 15:0:0:1: [sdc] tag#29 FAILED Result:
hostbyte=DID_TRANSPORT_DISRUPTED driverbyte=DRIVER_OK cmd_age=6s
Sep 23 08:00:55 host3 kernel: sd 15:0:0:1: [sdc] tag#29 CDB: Test Unit
Ready 00 00 00 00 00 00
Sep 23 08:00:55 host3 iscsid[2879]: iscsid: Kernel reported iSCSI
connection 1:0 error (1022 - ISCSI_ERR_NOP_TIMEDOUT: A NOP has timed out)
state (3)
Sep 23 08:01:00 host3 kernel: session1: session recovery timed out after 5
secs
Sep 23 08:01:00 host3 kernel: sd 15:0:0:0: rejecting I/O to offline device
Sep 23 08:01:00 host3 kernel: blk_update_request: I/O error, dev sdb,
sector 1020005680 op 0x1:(WRITE) flags 0xca00 phys_seg 1 prio class 0
Sep 23 08:01:00 host3 kernel: sd 15:0:0:0: rejecting I/O to offline device
Sep 23 08:01:00 host3 kernel: blk_update_request: I/O error, dev sdb,
sector 264192 op 0x0:(READ) flags 0x4200 phys_seg 1 prio class 0
Sep 23 08:01:00 host3 kernel: sd 15:0:0:0: rejecting I/O to offline device
Sep 23 08:01:00 host3 kernel: sd 15:0:0:0: rejecting I/O to offline device
Sep 23 08:01:00 host3 multipathd[1919]: sdb: mark as failed
Sep 23 08:01:00 host3 multipathd[1919]: 3600140502d7e875e48740398630ef780:
Entering recovery mode: max_retries=4
Sep 23 08:01:00 host3 multipathd[1919]: 3600140502d7e875e48740398630ef780:
remaining active paths: 0
Sep 23 08:01:00 host3 kernel: device-mapper: multipath: 253:13: Failing
path 8:16.
Sep 23 08:01:00 host3 kernel: sd 15:0:0:1: rejecting I/O to offline device
Sep 23 08:01:00 host3 kernel: blk_update_request: I/O error, dev sdc,
sector 264192 op 0x0:(READ) flags 0x4200 phys_seg 1 prio class 0
Sep 23 08:01:00 host3 kernel: sd 15:0:0:1: rejecting I/O to offline device
Sep 23 08:01:00 host3 kernel: device-mapper: multipath: 253:12: Failing
path 8:32.
Sep 23 08:01:01 host3 kernel: ixgbe :18:00.1 eno2: NIC Link is Up 10
Gbps, Flow Control: None
Sep 23 08:01:01 host3 NetworkManager[2247]:   [1600840861.5116]
device (eno2): carrier: link connected

Other 4.4.1 nodes with different network adapters and connected to the same
iSCSI storage don't have this problem
Any suggested way to substitute the provided module (5.1.0-k-rh8.2.0) of
kernel 4.18.0-193.14.2.el8_2.x86_64 with a more recent one and see if it
solves the problems? Or suggestions regarding iscsid.conf customization if
using ixgbe based network cards...?

Thanks,
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/SLIDYUXOI2O2AIR2GD2HU7A24FGTXHN2/


[ovirt-users] info on iSCSI connection setup in oVirt 4.4

2020-09-23 Thread Gianluca Cecchi
Hello,
supposing to have a node that connects to an iSCSI storage domain in oVirt
4.4, is there any particular requirement in the configuration of the
network adapter (ifcfg-eno1 file) when I pre-configure the server OS?
Eg, do I need to have it managed by NetworkManager in 4.4? Can I instead
set NM_CONTROLLED=no for this controller?
Thanks in advance,
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/5I6APYP3NVBJBNWRUKI6LD72FB5LXC6K/


[ovirt-users] Re: How to discover why a VM is getting suspended without recovery possibility?

2020-09-22 Thread Gianluca Cecchi
On Tue, Sep 22, 2020 at 9:12 AM Vinícius Ferrão via Users 
wrote:

> Hi Strahil, yes I can’t find anything recently either. You digged way
> further then me, I found some regressions on the kernel but I don’t know if
> it’s related or not:
>
> https://patchwork.kernel.org/patch/5526561/
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1045027
>
> Regarding the OS, nothing new was installed, just regular Windows Updates.
> And finally about nested virtualisation, it’s disabled on hypervisor.
>
>
>
In your original post you wrote about the VM going suspended.
So I think there could be something useful in engine.log on the engine
and/or vdsm.log on the hypervisor.
Could you check those?
Also, do you see anything in event viewer of the WIndows VM and/or in
Freenas logs?

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


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

2020-09-21 Thread Gianluca Cecchi
On Mon, Sep 21, 2020 at 5:26 PM Sandro Bonazzola 
wrote:

>
>
> Il giorno lun 21 set 2020 alle ore 17:13 Gianluca Cecchi <
> gianluca.cec...@gmail.com> ha scritto:
>
>>
>> On Thu, Sep 17, 2020 at 4:06 PM Lev Veyde  wrote:
>>
>>> The oVirt project is excited to announce the general availability of
>>> oVirt 4.4.2 , as of September 17th, 2020.
>>>
>>>
>>>
>> [snip]
>>
>>> oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)
>>> will be released separately due to a blocker issue (Bug 1837864
>>> <https://bugzilla.redhat.com/show_bug.cgi?id=1837864>).
>>>
>>>
>>> [snip]
>>
>> hi,
>> will you post an update to the list when the iso is available?
>>
>
>
> Sure, we'll issue a release announcement for the oVirt Node update as soon
> as we get the bug fixed.
>
>
> OK, thanks.

But indeed there is something strange.
Suppose I have an 4.4.0 node (when CentOS 8.2 not already released and
there was the pre-release), can I update to 4.4.2?

If I execute "yum update" on this system I get:

 [root@ovirt01 ~]# yum update
Extra Packages for Enterprise Linux 8 - x86_64   49
kB/s |  32 kB 00:00
CentOS-8 - Gluster 7 14
kB/s | 3.0 kB 00:00
virtio-win builds roughly matching what will be shipped in upcoming 5.6
kB/s | 3.0 kB 00:00
Copr repo for EL8_collection owned by sbonazzo  8.2
kB/s | 3.6 kB 00:00
Copr repo for gluster-ansible owned by sac  9.4
kB/s | 3.3 kB 00:00
Copr repo for ovsdbapp owned by mdbarroso   9.6
kB/s | 3.3 kB 00:00
Copr repo for nmstate-stable owned by nmstate   8.5
kB/s | 3.3 kB 00:00
Copr repo for NetworkManager-1.22 owned by networkmanager   8.3
kB/s | 3.3 kB 00:00
Advanced Virtualization packages for x86_64  36
kB/s | 3.0 kB 00:00
CentOS-8 - oVirt 4.4 19
kB/s | 3.0 kB 00:00
CentOS-8 - OpsTools - collectd   23
kB/s | 3.0 kB 00:00
Latest oVirt 4.4 Release3.9
kB/s | 3.0 kB 00:00
Dependencies resolved.

 PackageArchitecture   Version
 Repository Size

Installing:
 ovirt-node-ng-image-update noarch 4.4.1.5-1.el8
 ovirt-4.4 781 M
 replacing  ovirt-node-ng-image-update-placeholder.noarch 4.4.0-2.el8

Transaction Summary

Install  1 Package

Total download size: 781 M
Is this ok [y/N]:

And another guy I'm in contact with, who already has 4.4.1 installed, get
no updates available
Does this mean that even if 4.4.2 has been released (at which level at this
point), an ovirt node cannot be upgraded?
And a plain CentOS host instead, could it be updated?

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


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

2020-09-21 Thread Gianluca Cecchi
On Mon, Sep 21, 2020 at 5:12 PM Gianluca Cecchi 
wrote:

>
> On Thu, Sep 17, 2020 at 4:06 PM Lev Veyde  wrote:
>
>> The oVirt project is excited to announce the general availability of
>> oVirt 4.4.2 , as of September 17th, 2020.
>>
>>
>>
> [snip]
>
>> oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) will
>> be released separately due to a blocker issue (Bug 1837864
>> <https://bugzilla.redhat.com/show_bug.cgi?id=1837864>).
>>
>>
>> [snip]
>
> hi,
> will you post an update to the list when the iso is available?
> Thanks,
> Gianluca
>
>
BTW: the iso blocker bug is indeed related to upgrade failure and host
entering into emergency mode...
It is not clear to me if it is ok and safe to update from 4.4.0 (deployed
as node ng sytem) to 4.4.2 (involving install of the new .img filelayer) if
the bug is not completely solved

Can anyone shed some light, please?

Thanks,
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/2SWESDW3GVXGXAWDUT673JJU3EK7PLHD/


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

2020-09-21 Thread Gianluca Cecchi
On Thu, Sep 17, 2020 at 4:06 PM Lev Veyde  wrote:

> The oVirt project is excited to announce the general availability of oVirt
> 4.4.2 , as of September 17th, 2020.
>
>
>
[snip]

> oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) will
> be released separately due to a blocker issue (Bug 1837864
> ).
>
>
> [snip]

hi,
will you post an update to the list when the iso is available?
Thanks,
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/TGYBEG4KGUJRZJZCDNSHPE75DPUVDRKK/


[ovirt-users] Any eta for 4.4.2 final?

2020-09-15 Thread Gianluca Cecchi
Hello,
I would like to upgrade a 4.4.0 environment to the latest 4.4.2 when
available.
Any indication if there are any show stoppers after the rc5 released on
27th of August or any eta about other release candidates?

Thanks,
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:


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

2020-08-27 Thread Gianluca Cecchi
On Thu, Aug 27, 2020 at 11:06 AM Lev Veyde  wrote:

> oVirt 4.4.2 Fifth Release Candidate is now available for testing
>
> The oVirt Project is pleased to announce the availability of oVirt 4.4.2
> Fifth Release Candidate for testing, as of August 27th, 2020.
>
> This update is the second in a series of stabilization updates to the 4.4
> series.
>
>
>
Hi Lev, thanks for this update.
Is there a tracking to understand the need of this 5thrc and so a tracking
of things fixed/enhanced from rc4 (that I'm testing) and rc5, so that I can
address only those specific things in further tests after installing rc5?

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


[ovirt-users] Re: Error exporting into ova

2020-08-27 Thread Gianluca Cecchi
On Tue, Aug 25, 2020 at 3:29 PM Tommaso - Shellrent 
wrote:

> Hi Gianluca.
>
> We have a problem wit "export as ova" too.
>
> In our env we back up all the vm with a python script that run an export.
>
> If we run multiple export at the same time, also on different
> datacenter[but same engine], the wait for each other and do not run in
> async mode.
>
> If only one of those export takes 10h, all of them taskes 10+h too.
>
> seems that all the export have to end a step of the playbook to go on, but
> we see only one "nasible-playbook" process at a time.
>
> Have you got any hint?
>
>
> Regards,
> Tommaso.
>
>
>
>
>
>
>
My post was one year old.
In the meantime you can check these two posts in archives by Jayme (I cc
him):
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/U65CV5A6WC6SCB2R5N66Y7HPXQ3ZQT2H/#FAVZG32TPSX67DTXIHMGIQXUXNG3W3OE
and
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JNSY6GYNS6LPNUJXERUO2EOG5F3P7B2M/

In the first post it appears that by default the exports were of type fire
and forget (that is what you need) and so he included a wait_for task to
instead have them sequential.
I think you can borrow from his github playbooks and adapt to your needs.
Or Jayme, you could apply a general change where you set a variable (eg
sequential_flow) that by default is true and then you modify the
export_vm.yml playbook in the task

- name: "Wait for export"

with the wait condition becoming of kind

when: (export_result is not failed) or (sequential_flow|bool == False)

This way by default the play workflow remains unchanged, but a user can set
sequential_flow to False
What do you think about it?
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/P4XQXETOVU3VS6JMAWNXHS2CZCVGMO7R/


[ovirt-users] Re: TroubleshootingoVirt Node deploy FQDN not reachable

2020-08-27 Thread Gianluca Cecchi
On Thu, Aug 27, 2020 at 2:49 AM David White via Users 
wrote:

>
>
> The responses to the bugzilla make it sound like a second, unused, disk,
> is required. Is that the case?
>

yes, it is required to install the OS from the ovirt-node-ng iso on the
first disk and then select the second empty disk for gluster bricks/volumes
during the wizard phase.
Please note also that when you run anaconda from the iso it by default
selects both the disks as target of the OS install (with a warning), so
that you have to click on the second disk (and deselect it this way) and
proceed with the install on only the first disk
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/WVHQ5V6UKCIJB3HLAJL34Q6EAJ72FZ6P/


[ovirt-users] Re: i/o wait and slow system

2020-08-26 Thread Gianluca Cecchi
On Wed, Aug 26, 2020 at 8:19 PM info--- via Users  wrote:

> I enabled libgfapi and powered off / on the VM.
>
> - engine-config --all
> - LibgfApiSupported: true version: 4.3
>
> How can I see that this is active on the VM? The disk looks the same like
> before.
>
> - virsh dumpxml 15
> 
>io='threads'/>
>   
> 
>   
>   
>   
>   
> 
>
>
>
Latest status I remember was this one reported by me at 4.3 RC2 time last
year:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/KHWQA72JZVGLVXCIQPU2FDFRS73BW4LY/

and I think nothing changed in the mean time, neither for 4.3 nor for 4.4.
But not directly tested.
Someone reported 4x-5x improvements using libgfapi but initially there were
some blockers related to snapshots and HA if I remember correctly and so
disabled.
My idea is that all previous problems in upstream qemu and libvirtd pieces
are now solved since many months but developers didn't consider
implementing them due to not so big improvements detected in their tests
and/or sufficient time to dedicate to fix and/or other priorities.

Some bugzilla referred, to dig into if interested:
https://bugzilla.redhat.com/show_bug.cgi?id=1484227
https://bugzilla.redhat.com/show_bug.cgi?id=1465810
https://bugzilla.redhat.com/show_bug.cgi?id=1633642

HIH revamping the interesting topic.

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


[ovirt-users] Re: Is oVirt suited for supporting long-lived VMs than OpenStack?

2020-08-24 Thread Gianluca Cecchi
On Mon, Aug 24, 2020 at 12:56 PM yam yam  wrote:

> thank you Gianluca for the good link.
> it was really helpful and, they are really different considering the
> notion.
>
> but as "OpenStack" implements many features not only for cloud but also
> for traditional workload, I guess it's also good fit for traditional
> workload.
> So, I'm wondering whether virtualization solutions like oVirt have
> meaningful strengths than OpenStack at this point in time.
>
> Best Regards
>
>
Good that it was of help.
Like other pieces of software, I see in recent years that "adjacent"
technologies tend to extend their capabilities to each other,
compenetrating ...
For example latest virtualization features of Openshift:
https://www.openshift.com/blog/blog-openshift-virtualization-whats-new-with-virtualization-from-red-hat
https://www.redhat.com/files/summit/session-assets/2019/T47177.pdf
and then these new VMs created in Openshift that should also be manageable
from oVirt 4.4...
Or OpenStack components landing in oVirt, like cinderlib and Open vSwitch

In my opinion some basic reasons to use oVirt for virtualization instead of
OpenStack:
- if the main need is compute, because network and storage are already
provided externally (while OpenStack as IAAS provides the whole
"Infrastructure" as a server of the capital "I")
- if there are already settled departments for network and storage, so that
who manages VMs is not in charge of the other infrastructure components and
with oVirt you easily keep segregation of duties/responsibilities
- small environments in terms of compute nodes (2-3 but also something like
10)
- very very easier upgrades through minor and major releases

HIH,
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/WVJY6XYL5P6JYKV7LZC4MGCUJ2KZCJMO/


  1   2   3   4   5   6   7   8   9   10   >