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

2020-11-11 Thread Yedidyah Bar David 
On Wed, Nov 11, 2020 at 11:49 AM Matteo Bonardi  wrote:
>
> Hi Didi,
>
> > On Tue, Nov 10, 2020 at 7:18 PM Strahil Nikolov via Users
> >  >
> > I already suggested to open a bug for this earlier in this thread.
>
> I will open a bug for that.

Thanks.

>
> > I am not sure. I talked with Sandro about this, and we agreed that a
> > common enterprise requirement is being able to use a local _mirror_
> > (e.g. Foreman), mainly for disconnected use (without an Internet
> > connection). A proxy is technically quite different, even if in
> > principle can be used for the same need.
> >
>
> I can understand your point, but since the deploy script already checks that 
> the proxy is set, I don't see why it can't pass this information to the 
> engine.

Sorry, where?

Also:

On Wed, Nov 11, 2020 at 11:39 AM Matteo Bonardi  wrote:
>
> Thanks to all yours suggestions I, finally, complete the deploy with success.
> The solution is been to edit the file 
> /usr/share/ansible/roles/ovirt.engine-setup/tasks/install_packages.yml adding 
> the proxy variable:

Which version?

Perhaps you had 4.4.2 and then updated to 4.4.3 before retrying, or
something similar?

>
> - name: Install oVirt Engine package
>   package:
> name: "ovirt-engine"
> state: present
>   environment:
> https_proxy: "http://:"
> http_proxy: "http://:"
> ftp_proxy: "http://:"
>   when: ovirt_engine_setup_product_type | lower == 'ovirt'
> [..]
>
> 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

Can't guess, though, your exact flow - if you suspect a bug, please
check/share relevant logs (including dnf, but perhaps also ansible),
perhaps in a separate bug.

Sorry if this is confusing/messy. Feel free to comment on [1] if you
have something specific to add (it's a RHV bug, though, so if unsure,
perhaps file another bug. RHV's and oVirt's documentation are not as
aligned as their source code).

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1891749

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

[ovirt-users] Upgrade Problem oVirt engine 4.4.1.8-1.el8 -> 4.4.3

2020-11-11 Thread Andrei Verovski 
Hi !

I’m trying to upgrade oVirt engine 4.4.1.8-1.el8 to the latest 4.4.3, running 
as KVM appliance (not hosted engine).

This sequence of commands

yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
engine-upgrade-check
yum update ovirt\*setup\*

Results in a long list of dependency errors, short excerpt below.
Looks like something (e.g. repo) is missing. How to fix this? Thanks in advance.

— LOG --

Problem 1: problem with installed package 
ovirt-engine-ui-extensions-1.2.2-1.el8.noarch
 - package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch requires 
ovirt-ansible-cluster-upgrade >= 1.1.12, but none of the providers can be 
installed

Problem 2: package ovirt-engine-4.4.1.8-1.el8.noarch requires 
ovirt-engine-ui-extensions >= 1.0.4, but none of the providers can be installed

 - package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch requires 
ovirt-ansible-cluster-upgrade >= 1.1.12, but none of the providers can be 
installed
 - package ovirt-engine-4.4.1.8-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-cluster-upgrade provided by 
ovirt-ansible-cluster-upgrade-1.2.3-1.el8.noarch


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

[ovirt-users] Re: Upgrade Problem oVirt engine 4.4.1.8-1.el8 -> 4.4.3

2020-11-11 Thread tfe...@swissonline.ch 

Hi

I would like to add to this thread that I had experienced a very similar 
problem yesterday on my test system.


Notice that I have a different installation (engine installed on same 
host as oVirt host).


I worked around the issue with the following steps:

 * make engine-backup of the oVirt engine (pre-upgrade)
 * yum history rollback (to the state before the upgrade)
 * yum remove ovirt-engine
 * yum clean all
 * yum update
 * yum install ovirt-engine
 * engine-backup --restore the backup file of my engine backup
 * engine-setup

Hope this helps

Toni Feric


On 11.11.20 13:00, Andrei Verovski wrote:

Hi !

I’m trying to upgrade oVirt engine 4.4.1.8-1.el8 to the latest 4.4.3, running 
as KVM appliance (not hosted engine).

This sequence of commands

yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
engine-upgrade-check
yum update ovirt\*setup\*

Results in a long list of dependency errors, short excerpt below.
Looks like something (e.g. repo) is missing. How to fix this? Thanks in advance.

— LOG --

Problem 1: problem with installed package 
ovirt-engine-ui-extensions-1.2.2-1.el8.noarch
  - package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch requires 
ovirt-ansible-cluster-upgrade >= 1.1.12, but none of the providers can be 
installed

Problem 2: package ovirt-engine-4.4.1.8-1.el8.noarch requires 
ovirt-engine-ui-extensions >= 1.0.4, but none of the providers can be installed

  - package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch requires 
ovirt-ansible-cluster-upgrade >= 1.1.12, but none of the providers can be 
installed
  - package ovirt-engine-4.4.1.8-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-cluster-upgrade provided by 
ovirt-ansible-cluster-upgrade-1.2.3-1.el8.noarch


___
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/EMRQIDUGHYRUISAHDVWZ763NVHZP2NCM/
___
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/F7ZOGKQRU32UROQBWANGAPBCH34P24CW/

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

2020-11-11 Thread Yedidyah Bar David 
On Tue, Nov 10, 2020 at 7:18 PM Strahil Nikolov via Users
 wrote:
>
> the delegate_to stanza should use the variable for the HostedEngine, but I 
> think this one from the code should work:
>
> delegate_to: "{{ groups.engine[0] }}"
>
> @Sandro Bonazzola ,
> Maybe we should open a feature request for allowing the installer to deploy a 
> proxy ?

I already suggested to open a bug for this earlier in this thread.

> I think it's quite common in Enterprise environments .

I am not sure. I talked with Sandro about this, and we agreed that a
common enterprise requirement is being able to use a local _mirror_
(e.g. Foreman), mainly for disconnected use (without an Internet
connection). A proxy is technically quite different, even if in
principle can be used for the same need.

Best regards,

>
> Best Regards,
> Strahil Nikolov
>
>
>
>
>
>
> В вторник, 10 ноември 2020 г., 18:57:03 Гринуич+2, Strahil Nikolov 
>  написа:
>
>
>
>
>
> Simeon's proposal will be valid only for the deployment of the package - and 
> it should allow the deployment to pass.
>
> The example from the previous won't work as yum/dns is not using system proxy 
> -> my bad I didn't realize it earlier.
>
> I guess the task for the engine to use the proxy when installing software 
> would look like ( I haven't tested it,though):
>
>   - name: Deploy_proxy
> lineinfile:
>   line:  "proxy=http://myproxy.localdomain:3399;
>   state: "present"
>   path: "/etc/dnf/dnf.conf"
> delegate_to: localhost
>
>
>
> Best Regards,
> Strahil Nikolov
>
>
>
>
>
> В вторник, 10 ноември 2020 г., 17:59:29 Гринуич+2, Simon Coter 
>  написа:
>
>
>
>
>
> Hi Matteo,
>
> this one is the solution we’ve applied on OLVM that should also work for 
> oVirt:
>
> Before Deploying Self Hosted Engine(SHE) update the below lines in 
> /usr/share/ansible/roles/ovirt.hosted-engine-setup/hooks/enginevm_before_engine_setup/install_pre_setup_packages.yml
>
> From
> - name:Install oVirt Engine packages for restoring backup
> package:
> name: "ovirt-engine"
> state: present
> when: ovirt_engine_setup_product_type | lower == 'ovirt'
>  To
> -name: Install oVirt Engine packages for restoring backup
> package:
>  name: "ovirt-engine"
>  state: present
> environment:
>  https_proxy: 
>  http_proxy: 
> when: ovirt_engine_setup_product_type | lower == 'ovirt'
>
> In place of  add your own proxy; example: http://myproxy:3128
>
> Hope this helps.
>
> Simon
>
> > On Nov 10, 2020, at 4:45 PM, Matteo Bonardi  wrote:
> >
> > Hi Strahil,
> >
> > How can I define that task and pass it to the deploy?
> >
> > Thanks,
> > Matteo
> >
> > Il mar 10 nov 2020, 16:33 Strahil Nikolov  ha 
> > scritto:
> >> Did anyone try to define a task to deploy the variables in the 
> >> HostedEngine before the task?
> >>
> >> For example (take only the task):
> >> ---
> >> - name: Deploy proxy
> >>  hosts: localhost
> >>  tasks:
> >>  - name: Deploy_proxy
> >>blockinfile:
> >>  block:
> >>http_proxy=http://myproxy.localdomain:3399
> >>https_proxy=https://myproxy.localdomain:3340
> >>no_proxy=localhost
> >>  create: True
> >>  mode: "0444"
> >>  owner: "root"
> >>  selevel: "s0"
> >>  serole: "object_r"
> >>  setype: "bin_t"
> >>  seuser: "system_u"
> >>  state: "present"
> >>  path: "/etc/profile.d/proxy.sh"
> >>delegate_to: localhost
> >>
> >> And the result is:
> >> [root@engine ~]# echo $http_proxy
> >> http://myproxy.localdomain:3399
> >> [root@engine ~]# echo $https_proxy
> >> https://myproxy.localdomain:3340
> >> [root@engine ~]# echo $no_proxy
> >> localhost
> >>
> >>
> >> Best Regards,
> >> Strahil Nikolov
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> В вторник, 10 ноември 2020 г., 12:17:52 Гринуич+2, 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/
> >>
> >>
> > ___
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to

[ovirt-users] Re: Host NonResponsive after migration to oVirt 4.4

2020-11-11 Thread Yedidyah Bar David 
On Wed, Nov 11, 2020 at 12:38 PM tfe...@swissonline.ch
 wrote:
>
> Hello Yedidyah
>
> Many thanks for clarification.
>
> If I wanted to convert my all-in-one installation to a "supported" one (on a 
> single box), would I have to migrate my engine into a self-hosted VM? What 
> would be the most common way to conform?

Basically one of two approaches, depending on your needs:

1. For production, I think most people use hyper-converged
hosted-engine (meaning, local gluster storage and engine its a
self-hosted vm). If you do not want to use gluster, some people also
reported using local NFS/iSCSI, although at least NFS used to be
considered risky (due to locking issues). Most people, though,
consider this overkill - you don't enjoy many of its features, but
it's more complex than e.g. virt-manager.

2. For learning/development/testing, I think most people use
virt-manager, or virsh (perhaps wrapped in custom scripts) or
something similar, to create separate VMs, and then use these as
machines for oVirt - can be a host (with nested-kvm) on one,
standalone engine or hosted-engine host on another, storage on another
(or on the physical machine) - depending on what you want to do.

If you feel like combining both - meaning, (2.), but using oVirt also
for the physical machine - that's just fine too.

>
>
> I was able to fix my problem by:
>
> uninstalling oVirt
> yum update
> installing oVirt 4.4.3
> installing cockpit-ovirt-dashboard (which installs vdsm etc. as dependency)
> modifying the engine-backup script (don't bail out on restore if 
> version<4.3.10)
> Restore engine from backup file
> engine-setup
> Reinstall host from oVirt UI

Seems reasonable. Thanks for the update!

Best regards,

>
>
> Many thanks
>
> Toni Feric
>
>
> On 10.11.20 14:22, Yedidyah Bar David wrote:
>
> On Tue, Nov 10, 2020 at 3:13 PM tfe...@swissonline.ch
>  wrote:
>
> Hello Ritesh
>
> Engine and host is the same. There is only one box.
>
> This is called all-in-one. Was officially supported until 3.6, and is
> unsupported, undocumented and untested these days, although people
> seem to be using it, and even more-or-less successfully.
>
> To get an overview of what you should do, if you follow the current
> documentation, you should read both engine-specific parts and
> hosts-specific parts.
>
> The vdsm daemon does not seem to exist.
>
> # systemctl status vdsmd
> Unit vdsmd.service could not be found.
>
> Should I assume that there is a component missing, which should have been 
> installed?
> I just checked the installation documentation, and was not able to spot a 
> step that could be missing.
> https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/#Installing_the_Red_Hat_Virtualization_Manager_SM_localDB_deploy
>
> Thanks, Toni
>
>
> On 10 Nov 2020, at 13:47, Ritesh Chikatwar  wrote:
>
> Hello,
>
> Looks like you are checking this directory in the engine. You will get this 
> in the host.
> Also check vdsm service is running or not using systemctl status vdsmd
>
> On Tue, Nov 10, 2020 at 6:09 PM tfe...@swissonline.ch  
> wrote:
>
> Hello Ritesh
>
> I can see the NIC attached to the host in the UI.
> However, I don’t have a directory /var/log/vdsm.
> I am sharing the filetree of my /var/log in the separately attached text file:
>
> Thanks, Toni
>
>
> On 10 Nov 2020, at 13:04, Ritesh Chikatwar  wrote:
>
> Hello,
>
> Can you share vdsm logs you can find at /var/log/vdsm/vdsm.log.
>
> I guess this might be a vdsm issue between an engine and host.
> also check in ui whether a nic is attached to the host after upgrade.
>
> On Tue, Nov 10, 2020 at 5:18 PM tfe...@swissonline.ch  
> wrote:
>
>  Hi
>
> I am looking for help after my oVirt upgrade failed.
>
>
> I have upgraded from ovirt 4.3 to 4.4 following the instructions here:
>
> https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3
>
> It's a single-host (standalone engine) test environment.
> I wiped CentOS 7 and reinstalled a fresh CentOS 8.
> I installed the oVirt 4.4 repo and all the necessary software packets.
>
> I used `engine-backup --mode=restore 
> --file=/tmp/ovirt-engine-pre-upgrade.backup --provision-all-databases` from a 
> backup file I created before I started the upgrade.
> After the restore, I ran `engine-setup`.
>
> I did not get any errors during any of these steps on the console.
> So the upgrade could be considered successful from that perspective.
>
> After the upgrade, I login to the ovirt admin portal, and I try to "Activate" 
> my host (was set to "Maintenance" mode before upgrade).
>
> Please try 'Reinstall'.
>
> This should install vdsm for you, among many other things.
>
> Best regards,
>
> The Activation fails with error "NonResponsive" in the GUI.
> Under the "bell" icon, I find the Event "Host nuc1.feric.ch is non 
> responsive.”
>
> In /var/log/ovirt-engine/engine.log, I find the following error:
> ```
> 2020-11-09 23:12:21,080+01 ERROR 
>

[ovirt-users] Ballooning disabled when creating a VmPool

2020-11-11 Thread Nicolás 

Hi,

We're using oVirt 4.3.8 along with ovirt-engine-sdk-python (4.4.1) to 
handle our pools.


Pools are based on a template which has ballooning enabled. However, 
when deploying a VmPool based on that template, has the "Ballooning 
enabled" field disabled, uneditable and an icon which states: "The field 
is not attached to any instance type" (screenshot attached).


We're handling a big number of VMs based on pools (> 1500), and we think 
this should be enabled.


However, I don't see a field in the types.VmPool definition that allows 
that.


Is that even doable? Our Python code is similar to this:

   newpool = types.VmPool(name='test',
                     cluster=cl,
                         template=t,
                     max_user_vms=1,
                         size=1,
   type=types.VmPoolType.MANUAL)
   vmpool_serv.add(newpool)

 * cl is a types.Cluster instance with ballooning_enabled=True
 * t is a types.Template instance with Ballooning enabled.

Thanks.

Nico

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

[ovirt-users] Re: Cannot restore engine from 4.3.9 to 4.4.3

2020-11-11 Thread Yedidyah Bar David 
On Wed, Nov 11, 2020 at 4:34 AM tfe...@swissonline.ch
 wrote:
>
> Hi
>
> I just tried to restore my engine backup taken from release 4.3.9.4 to a 
> newer oVirt installation release 4.4.3.11.
>
> The restore process fails with a FATAL error.
>
> I was under the impression that backups from all 4.3 versions were supposed 
> to be restorable on 4.4.

This used to be true, but was changed in 4.4.3:

https://bugzilla.redhat.com/1881119 [RFE] Make engine-backup refuse to
restore a backup from a version earlier than 4.3.10

Was filed due to:

https://bugzilla.redhat.com/1820642 [cinderlib] Cinderlib DB is
missing a backup and restore option [RHV clone - 4.3.10]

>
> My installation is a single-box all-in-one (Standalone Engine installed 
> together with oVirt node).

Please upgrade first to 4.3.10.

We did this to make sure the backup included the cinderlib db, if set up.
It's not really needed if you do not use cinderlib, but I didn't
consider making this requirement optional, as the documentation
already says to upgrade to latest 4.3 first, so I assumed it's not
really needed (and we did have concrete cases in the past, where
upgrading from an older version was broken, see e.g. the discussion in
bug 1366900, especially comment 7 and comment 15).

If that's a problem, you can edit the engine-backup script, reverting
the patch linked from the first bug above. It's enough to remove the
'if 4.3/.../fi' (lines 1281-1290).

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

[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-11 Thread Matteo Bonardi 
Thanks to all yours suggestions I, finally, complete the deploy with success.
The solution is been to edit the file 
/usr/share/ansible/roles/ovirt.engine-setup/tasks/install_packages.yml adding 
the proxy variable:

- name: Install oVirt Engine package
  package:
name: "ovirt-engine"
state: present
  environment:
https_proxy: "http://:"
http_proxy: "http://:"
ftp_proxy: "http://:"
  when: ovirt_engine_setup_product_type | lower == 'ovirt'
[..]

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.

Thank you all for the help!

Best regards,
Matteo
___
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/IMHIBGCFIED32NIOBZCUXIPVAGFNSDJZ/

[ovirt-users] Re: Host NonResponsive after migration to oVirt 4.4

2020-11-11 Thread tfe...@swissonline.ch 

Hello Yedidyah

Many thanks for clarification.

If I wanted to convert my all-in-one installation to a "supported" one 
(on a single box), would I have to migrate my engine into a self-hosted 
VM? What would be the most common way to conform?



I was able to fix my problem by:

 * uninstalling oVirt
 * yum update
 * installing oVirt 4.4.3
 * installing cockpit-ovirt-dashboard (which installs vdsm etc. as
   dependency)
 * modifying the engine-backup script (don't bail out on restore if
   version<4.3.10)
 * Restore engine from backup file
 * engine-setup
 * Reinstall host from oVirt UI


Many thanks

Toni Feric


On 10.11.20 14:22, Yedidyah Bar David wrote:

On Tue, Nov 10, 2020 at 3:13 PM tfe...@swissonline.ch
 wrote:

Hello Ritesh

Engine and host is the same. There is only one box.

This is called all-in-one. Was officially supported until 3.6, and is
unsupported, undocumented and untested these days, although people
seem to be using it, and even more-or-less successfully.

To get an overview of what you should do, if you follow the current
documentation, you should read both engine-specific parts and
hosts-specific parts.


The vdsm daemon does not seem to exist.

# systemctl status vdsmd
Unit vdsmd.service could not be found.

Should I assume that there is a component missing, which should have been 
installed?
I just checked the installation documentation, and was not able to spot a step 
that could be missing.
https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/#Installing_the_Red_Hat_Virtualization_Manager_SM_localDB_deploy

Thanks, Toni


On 10 Nov 2020, at 13:47, Ritesh Chikatwar  wrote:

Hello,

Looks like you are checking this directory in the engine. You will get this in 
the host.
Also check vdsm service is running or not using systemctl status vdsmd

On Tue, Nov 10, 2020 at 6:09 PM tfe...@swissonline.ch  
wrote:

Hello Ritesh

I can see the NIC attached to the host in the UI.
However, I don’t have a directory /var/log/vdsm.
I am sharing the filetree of my /var/log in the separately attached text file:

Thanks, Toni


On 10 Nov 2020, at 13:04, Ritesh Chikatwar  wrote:

Hello,

Can you share vdsm logs you can find at /var/log/vdsm/vdsm.log.

I guess this might be a vdsm issue between an engine and host.
also check in ui whether a nic is attached to the host after upgrade.

On Tue, Nov 10, 2020 at 5:18 PM tfe...@swissonline.ch  
wrote:

  Hi

I am looking for help after my oVirt upgrade failed.


I have upgraded from ovirt 4.3 to 4.4 following the instructions here:

https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3

It's a single-host (standalone engine) test environment.
I wiped CentOS 7 and reinstalled a fresh CentOS 8.
I installed the oVirt 4.4 repo and all the necessary software packets.

I used `engine-backup --mode=restore 
--file=/tmp/ovirt-engine-pre-upgrade.backup --provision-all-databases` from a 
backup file I created before I started the upgrade.
After the restore, I ran `engine-setup`.

I did not get any errors during any of these steps on the console.
So the upgrade could be considered successful from that perspective.

After the upgrade, I login to the ovirt admin portal, and I try to "Activate" my host 
(was set to "Maintenance" mode before upgrade).

Please try 'Reinstall'.

This should install vdsm for you, among many other things.

Best regards,


The Activation fails with error "NonResponsive" in the GUI.
Under the "bell" icon, I find the Event "Host nuc1.feric.ch is non responsive.”

In /var/log/ovirt-engine/engine.log, I find the following error:
```
2020-11-09 23:12:21,080+01 ERROR 
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [] 
Command 'GetCapabilitiesAsyncVDSCommand(HostName = nuc1.feric.ch, 
VdsIdAndVdsVDSCommandParametersBase:{hostId='d7c30cc0-ac59-4cf3-a1e7-b9fae9db83fb',
 vds=‘Host[nuc1.feric.h,d7c30cc0-ac59-4cf3-a1e7-b9fae9db83fb]'})' execution 
failed: java.net.ConnectException: Connection refused
```

`systemctl status ovirt-engine` shows that the engine is running.
I am able to reboot the host from the oVirt GUI directly.

Does anyone have an idea how to proceed?

Many thanks
Toni
___
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/QWVBKDG2Q4BJHDHXNAHIWIG3QLW5E235/



___
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: Deploy oVirt Engine fail behind proxy

2020-11-11 Thread Matteo Bonardi 
Hi Didi,

> On Tue, Nov 10, 2020 at 7:18 PM Strahil Nikolov via Users
>  
> I already suggested to open a bug for this earlier in this thread.

I will open a bug for that.

> I am not sure. I talked with Sandro about this, and we agreed that a
> common enterprise requirement is being able to use a local _mirror_
> (e.g. Foreman), mainly for disconnected use (without an Internet
> connection). A proxy is technically quite different, even if in
> principle can be used for the same need.
> 

I can understand your point, but since the deploy script already checks that 
the proxy is set, I don't see why it can't pass this information to the engine.

> Best regards,

Regards,
Matteo
___
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/47RCLJWNUXFCALQ5ZYISEE2CYDT3AY4Q/

[ovirt-users] Re: Clone a VM in the User Portal

2020-11-11 Thread Nicolás 

Hi Arik,

El 10/11/20 a las 15:22, Arik Hadas escribió:



On Tue, Nov 10, 2020 at 4:37 PM Nicolás > wrote:


Hi Arik,

El 10/11/20 a las 13:21, Arik Hadas escribió:



On Tue, Nov 10, 2020 at 3:08 PM Nicolás mailto:nico...@devels.es>> wrote:

Hi Sharon,

Thanks for the reply! I've opened [1], so hopefully someone
will be able to implement it.

Regards,

Nico

  [1]: https://github.com/oVirt/ovirt-site/issues/2389

El 10/11/20 a las 11:38, Sharon Gratch escribió:

Hi,

This feature of cloning a VM was indeed part of the old User
Portal and you are right that it's not supported by the
newer VM Portal (since oVirt 4.3).
It seemed that this wasn't required by VM Portal users (no
user complained up till now) and that's why we omitted it
and it's not part of our current roadmap to implement it as
well.

Nevertheless, there is no real reason not to include that
ability as part of VM Portal, so you are most welcome to
open an issue on https://github.com/oVirt/ovirt-web-ui/issues

and you can push a fix yourself if you have time (or someone
else from the community) :-)

Thanks!
Sharon

On Fri, Nov 6, 2020 at 11:06 AM Nicolás mailto:nico...@devels.es>> wrote:

Hi,

We're using oVirt 4.3.8, having an organization that
intensively uses
the User Portal. After upgrading from 4.2, we've noticed
that cloning a
VM from within the User Portal is not possible anymore.
In our case,
this feature was heavily used by hundreds of students
deploying their VMs.



Out of curiosity, why cloning a VM and not provisioning the VMs
from template(s)?


Most of our students are IT-related, and their professors want to
teach them the procedure to deploy a VM from scratch. Some other
courses surely deploy their VMs from a template as they are not
that IT oriented and they just want to have a working VM instead
of building it from scratch. We have a lot of casuistry, but in
our case about 400~500 students would very welcome having back the
clone option.


Thanks Nicolás.
I'd say that even for the IT-related students it may make more sense 
to provision VMs from templates instead of cloning VMs -
so you want them to deploy VMs from scratch, which means starting with 
a VM that is based on the blank template, add disk(s) and other 
devices, install and configure the guest and such; and then the 
students would use clone-VM to duplicate the VM they just prepared, right?


Yep, that's mostly it.

Why would you want them to clone the VM rather than creating a 
template out of this VM and provision further VMs from that template 
with thin-provisioned disks?




Because that would involve creating templates, and would require a 
permission they don't have. We've chosen a few permissions which make 
them able to deploy their own machines, but we don't want them to create 
templates or even access the admin panel.


Additionally, courses are composed of groups of students which deploy 
different infrastructures. So one could deploy an HAproxy architecture, 
some other could deploy a pacemaker+corosync architecture with different 
parameters (some of them need more disk, some of them need more 
memory...), so each group would need to create templates just to deploy 
a couple machines.


I think it's more practical (in this case) to deploy the couple of 
machines using a clone option. In some other courses, where all the VM 
parameters are equal, it's better to deploy the VM from a template and 
some subjects use this option too.


Thanks.

Nico



Regards,

Nico



Is this feature in the roadmap yet? If not, do you
consider it useful to
open a RFE?

Thank you.

Regards,

Nico
___
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/HFMFJRV3AC3GVLYZJ32KAZCIAO25P3X3/



___
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

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

2020-11-11 Thread Yedidyah Bar David 
On Wed, Nov 11, 2020 at 12:14 PM Gianluca Cecchi
 wrote:
>
> 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/

I am aware of your other thread, might reply later (or I hope someone
else will do the investigation...).

I do not think it's strictly related, but not sure yet. Yours was on
the engine machine, whereas current is about a host (hosted-engine)
machine.

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

[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] Re: Engine update error from 4.4.2 to 4.4.3

2020-11-11 Thread Martin Perina 
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/QNUU3GVYLO47KC6GGSDV4VWJTCTRHHGU/

[ovirt-users] Re: Single Node HCI upgrade procedure from CentOS7/oVirt 4.3 to CentOS8/oVirt 4.4?

2020-11-11 Thread Derek Atkins 
There are plenty of other reasons to be running a single-host
Hyperconverged  deployment, in production.  One of them is financial. 
Another is for small-scale production systems that don't have the space,
finances, or other resources to run a 3-node system.  Considering it a
"toy" doesn't mean it isn't (or shouldn't be) a supported deployment.

Having a tested upgrade path from EL 7.x/Ovirt 4.3.x to EL 8 / Ovirt 4.4
running on a single system would be extremely useful in those situations.

I do realize that any upgrade of a single-host system is rife with the
dangers of a failed upgrade, and it requires downtime either way.  However
I feel an in-place (yum/dnf) path is "safer" than a "reinstall from
scratch" path.  So having a well-documented path would be ideal.

Thanks!

-derek

PS: While I am LOOKING at expanding my 1-node system to 3, I don't see
that happening any time soon.  And even then, I would need to migrate my
NFS storage to something more distributed like Gluster.  So I suspect I
would need to reinstall the self-hosted engine regardless to change its
storage, and then I can migrate all existing VMs from NFS to Gluster.

On Sat, September 26, 2020 9:00 am, tho...@hoberg.net wrote:
> I can hear you saying: "You did understand that single node HCI is just a
> toy, right?"
>
> For me the primary use of a single node HCI is adding some disaster
> resilience in small server edge type scenarios, where a three node HCI
> provides the fault tolerance: 3+1 with a bit of distance, warm or even
> cold stand-by, potentially manual switch and reduced workload in case
> disaster strikes.
>
> Of course, another 3nHCI would be better, but who gets that type of
> budget, right?
>
> What I am trying say: If you want oVirt to gain market share, try to give
> HCI more love. And while you're at it, try to make expanding from 1nHCI to
> 3nHCI (and higher counts) a standard operational procedure to allow
> expanding a disaster stand-by into a production setup, while the original
> 3nHCI is being rebuilt.
>
> For me low-budget HCI is where oVirt has its biggest competitive advantage
> against vSan and Nutanix, so please don't treat the HCI/gluster variant
> like an unwanted child any more.
>
> In the mean-time OVA imports (from 4.3.10 exports) on my 4.4.2 1nHCI fail
> again, which I'll report separately.
> ___
> 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/QI3Z45SRJD72ZJIX6HZCVC7DVVSZCKUW/
>


-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant
___
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/5MMU7TOS2776IV72H75WMJTZCF7TAHDU/

[ovirt-users] Upgrade OVIRT from 3.6 to 4.3

2020-11-11 Thread Miguel Angel Costas 
Hi Guys!

I need to upgrade from 3.6 to 4.3 and I have a doubt.
Do I need to restard VMs for each upgrade (DC Compatibilty 1° 4.0  - 2° 4.1 - 
3° 4.2 and 4° 4.3) or can modify the compatibilty  from 3.6 to 4.2 and restart 
the vms in this only step.

Best regards   
___
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/DAXCGYEQM4BM3KWMRAY4HMGE2YAHDB2H/

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

2020-11-11 Thread shadow emy 
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 
___
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/OIURDUJ67AJOWFZH2JXZCGA2IME3NNKD/

[ovirt-users] Re: Upgrade Problem oVirt engine 4.4.1.8-1.el8 -> 4.4.3

2020-11-11 Thread Andrei Verovski 
Yes I know I can reinstall and import back database, but its kinda awkward.


> On 11 Nov 2020, at 14:21, tfe...@swissonline.ch wrote:
> 
> Hi
> 
> I would like to add to this thread that I had experienced a very similar 
> problem yesterday on my test system.
> 
> Notice that I have a different installation (engine installed on same host as 
> oVirt host).
> I worked around the issue with the following steps:
> 
> make engine-backup of the oVirt engine (pre-upgrade)
> yum history rollback (to the state before the upgrade)
> yum remove ovirt-engine
> yum clean all
> yum update
> yum install ovirt-engine
> engine-backup --restore the backup file of my engine backup
> engine-setup
> Hope this helps
> 
> Toni Feric
> 
> On 11.11.20 13:00, Andrei Verovski wrote:
>> Hi !
>> 
>> I’m trying to upgrade oVirt engine 4.4.1.8-1.el8 to the latest 4.4.3, 
>> running as KVM appliance (not hosted engine).
>> 
>> This sequence of commands
>> 
>> yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm 
>> 
>> engine-upgrade-check
>> yum update ovirt\*setup\*
>> 
>> Results in a long list of dependency errors, short excerpt below.
>> Looks like something (e.g. repo) is missing. How to fix this? Thanks in 
>> advance.
>> 
>> — LOG --
>> 
>> Problem 1: problem with installed package 
>> ovirt-engine-ui-extensions-1.2.2-1.el8.noarch
>>  - package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch requires 
>> ovirt-ansible-cluster-upgrade >= 1.1.12, but none of the providers can be 
>> installed
>> 
>> Problem 2: package ovirt-engine-4.4.1.8-1.el8.noarch requires 
>> ovirt-engine-ui-extensions >= 1.0.4, but none of the providers can be 
>> installed
>> 
>>  - package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch requires 
>> ovirt-ansible-cluster-upgrade >= 1.1.12, but none of the providers can be 
>> installed
>>  - package ovirt-engine-4.4.1.8-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-cluster-upgrade provided by 
>> ovirt-ansible-cluster-upgrade-1.2.3-1.el8.noarch
>> 
>> 
>> ___
>> 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/EMRQIDUGHYRUISAHDVWZ763NVHZP2NCM/
>>  
>> 

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

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

2020-11-11 Thread Gilboa Davara 
On Wed, Nov 11, 2020 at 3:45 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

Sorry. My mistake.
Seeing the same when running $ yum update ovirt\*setup\*.

- Gilboa
___
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/ISEHURXPGXXSBFDFIVRUNT3MAREZ3MGY/

[ovirt-users] Re: Upgrade Problem oVirt engine 4.4.1.8-1.el8 -> 4.4.3

2020-11-11 Thread shadow emy 
The way i resolved this,  was to update only specific packages first.
So i am not using  this step  " yum update ovirt\*setup\*   " and use the 
bellow  command  which updates the engine-setup.

dnf update ovirt-engine-setup ovirt-engine-setup-plugin-websocket-proxy 
ovirt-engine-dwh-setup ovirt-engine-dwh-grafana-integration-setup


After the engine-setup gets updated, i can run fine engine-setup and proceed 
with the update.


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

[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 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: 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: Cluster with Hosted Engine update BIOS Setting Ovirt 4.4.3

2020-11-11 Thread shadow emy 
I had the same problem after Update.

What i did was set Chipset/Firmware Type to:  " I440FX Chipset with BIOS  "  
and it works.
Previous setting was "Q35 Chipset with BIOS " , which did not work with 4.4.3 .

I also can not change the Cluster Compatibility to 4.5 and if i want to do 
Spike VNC in any vm`s using  Remote Viewer via Console Tab in Gui , it does not 
open any connections.
Maybe i need to change the Cluster Compatibility for this to work, but i dont 
know how that works.
___
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/RQ7MYY466ULCM4ULPRVOCFY4LMTMFYNL/

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

2020-11-11 Thread Gilboa Davara 
On Wed, Nov 11, 2020 at 10:57 AM Gianluca Cecchi
 wrote:
>
> 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-users] Cluster with Hosted Engine update BIOS Setting Ovirt 4.4.3

2020-11-11 Thread scrik787 
I changed the type in the cluster and now my hosted-engine machine won't 
start!. There
are no backups. How can I manually change the parameters of the machine from 
under the
roof so that it starts and I can restore ovirt to work

Error in logs: XML error: The device at PCI address :00:02.0 cannot be 
plugged into
the PCI controller with index='0'. It requires a controller that accepts a
pcie-root-port

VDSM.log https://pastebin.com/vsAKy9rX
___
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/WLDNRSD4GXPXRCNY6EGTWFCGCZYD4Y4C/

[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] Cluster compatibility version 4.5 on oVirt 4.4

2020-11-11 Thread tfe...@swissonline.ch 

Hi

Today, I upgraded oVirt from 4.3 to 4.4.3.

After the upgrade, I upgraded the compatibility from 4.3 to 4.4.

I noticed that the cluster config is offering me another upgrade of the 
compatibility to version 4.5.


Up until now, I was under the impression that the compatibility version 
must match the oVirt version.


I am now reluctant to upgrade the compatibility to 4.5, while my oVirt 
version is still at 4.4 (there is no oVirt 4.5 at this time).


Is it safe to upgrade the compatibility in any case, or are there 
certain circumstances, where we should refrain from upgrading it?


I wasn't able to find anything in the documentation.


Kind regards

Toni Feric
___
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/XR4XU55CAL25CYNW7WBWJLIZLQXB4WIZ/

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

2020-11-11 Thread jorgevisentini 
When I update the Engine and Host, many dependencies are missing, as shown by 
the host error log:

Error:
 Problem 1: package ovirt-hosted-engine-setup-2.4.6-1.el8.noarch requires 
ovirt-ansible-engine-setup >= 1.1.9, but none of the providers can be installed
  - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes 
ovirt-ansible-engine-setup provided by 
ovirt-ansible-engine-setup-1.2.4-1.el8.noarch
  - cannot install the best update candidate for package 
ovirt-hosted-engine-setup-2.4.6-1.el8.noarch
  - cannot install the best update candidate for package 
ovirt-ansible-engine-setup-1.2.4-1.el8.noarch
 Problem 2: package ovirt-host-4.4.1-4.el8.x86_64 requires 
ovirt-hosted-engine-setup, but none of the providers can be installed
  - package ovirt-hosted-engine-setup-2.4.6-1.el8.noarch requires 
ovirt-ansible-hosted-engine-setup >= 1.0.34, but none of the providers can be 
installed
  - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes 
ovirt-ansible-hosted-engine-setup provided by 
ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch
  - cannot install the best update candidate for package 
ovirt-host-4.4.1-4.el8.x86_64
  - cannot install the best update candidate for package 
ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch
  - package ovirt-ansible-hosted-engine-setup-1.1.4-1.el8.noarch is filtered 
out by exclude filtering
  - package ovirt-ansible-hosted-engine-setup-1.1.5-1.el8.noarch is filtered 
out by exclude filtering
  - package ovirt-ansible-hosted-engine-setup-1.1.6-1.el8.noarch is filtered 
out by exclude filtering
  - package ovirt-ansible-hosted-engine-setup-1.1.7-1.el8.noarch is filtered 
out by exclude filtering
  - package ovirt-hosted-engine-setup-2.4.4-1.el8.noarch is filtered out by 
exclude filtering
  - package ovirt-hosted-engine-setup-2.4.5-1.el8.noarch is filtered out by 
exclude filtering
  - package ovirt-hosted-engine-setup-2.4.7-1.el8.noarch is filtered out by 
exclude filtering
  - package ovirt-hosted-engine-setup-2.4.8-1.el8.noarch is filtered out by 
exclude filtering
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use 
not only best candidate packages)
___
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/W4MLIPGT7CJQVZRFRE2MPJ7VTIZAYYEH/

[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: Dependencies failure when upgrading from version 4.4.2 to 4.4.3

2020-11-11 Thread Martin Perina 
Hi,

We already have https://bugzilla.redhat.com/show_bug.cgi?id=1896799 open to
track this issue. Could you please to upgrade your standalone engine using
below steps?

  # dnf update ovirt\*setup\* --nobest
  # engine-setup
  # dnf update --nobest
  # reboot

If engine upgrade is successful, could you please upgrade yours hosts from
webadmin using below steps?

1. Move the host to Maintenance
2. Execute Check for Update
3. Execute Upgrade

Manual upgrade of host using command line has been deprecated, because
manual steps are missing important parts (for example renewal of
certificates close to expiration date)

Thanks,
Martin



On Wed, Nov 11, 2020 at 7:47 PM  wrote:

> When I update the Engine and Host, many dependencies are missing, as shown
> by the host error log:
>
> Error:
>  Problem 1: package ovirt-hosted-engine-setup-2.4.6-1.el8.noarch requires
> ovirt-ansible-engine-setup >= 1.1.9, but none of the providers can be
> installed
>   - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes
> ovirt-ansible-engine-setup provided by
> ovirt-ansible-engine-setup-1.2.4-1.el8.noarch
>   - cannot install the best update candidate for package
> ovirt-hosted-engine-setup-2.4.6-1.el8.noarch
>   - cannot install the best update candidate for package
> ovirt-ansible-engine-setup-1.2.4-1.el8.noarch
>  Problem 2: package ovirt-host-4.4.1-4.el8.x86_64 requires
> ovirt-hosted-engine-setup, but none of the providers can be installed
>   - package ovirt-hosted-engine-setup-2.4.6-1.el8.noarch requires
> ovirt-ansible-hosted-engine-setup >= 1.0.34, but none of the providers can
> be installed
>   - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes
> ovirt-ansible-hosted-engine-setup provided by
> ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch
>   - cannot install the best update candidate for package
> ovirt-host-4.4.1-4.el8.x86_64
>   - cannot install the best update candidate for package
> ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch
>   - package ovirt-ansible-hosted-engine-setup-1.1.4-1.el8.noarch is
> filtered out by exclude filtering
>   - package ovirt-ansible-hosted-engine-setup-1.1.5-1.el8.noarch is
> filtered out by exclude filtering
>   - package ovirt-ansible-hosted-engine-setup-1.1.6-1.el8.noarch is
> filtered out by exclude filtering
>   - package ovirt-ansible-hosted-engine-setup-1.1.7-1.el8.noarch is
> filtered out by exclude filtering
>   - package ovirt-hosted-engine-setup-2.4.4-1.el8.noarch is filtered out
> by exclude filtering
>   - package ovirt-hosted-engine-setup-2.4.5-1.el8.noarch is filtered out
> by exclude filtering
>   - package ovirt-hosted-engine-setup-2.4.7-1.el8.noarch is filtered out
> by exclude filtering
>   - package ovirt-hosted-engine-setup-2.4.8-1.el8.noarch is filtered out
> by exclude filtering
> (try to add '--skip-broken' to skip uninstallable packages or '--nobest'
> to use not only best candidate packages)
> ___
> 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/W4MLIPGT7CJQVZRFRE2MPJ7VTIZAYYEH/
>


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

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

2020-11-11 Thread jorgevisentini 
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.

Below are some messages from the events of the engine's web interface:
   - Failed to upgrade Host kcmi1kvm03.kosmo.cloud (User: admin@internal-authz).
   - Update of host kcmi1kvm03.kosmo.cloud. Prepare NGN host for upgrade.
   - Check for available updates on host kcmi1kvm03.kosmo.cloud was completed 
successfully with message 'found updates for packages 
ovirt-ansible-collection.noarch'.



For more details, I performed the update manually, and the errors found were as 
follows:

yum upgrade --nobest
Last metadata expiration check: 0:04:21 ago on Wed 11 Nov 2020 04:59:59 PM -03.
Dependencies resolved.

 Problem 1: package ovirt-hosted-engine-setup-2.4.6-1.el8.noarch requires 
ovirt-ansible-engine-setup >= 1.1.9, but none of the providers can be installed
  - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes 
ovirt-ansible-engine-setup provided by 
ovirt-ansible-engine-setup-1.2.4-1.el8.noarch
  - cannot install the best update candidate for package 
ovirt-hosted-engine-setup-2.4.6-1.el8.noarch
  - cannot install the best update candidate for package 
ovirt-ansible-engine-setup-1.2.4-1.el8.noarch
 Problem 2: package ovirt-host-4.4.1-4.el8.x86_64 requires 
ovirt-hosted-engine-setup, but none of the providers can be installed
  - package ovirt-hosted-engine-setup-2.4.6-1.el8.noarch requires 
ovirt-ansible-hosted-engine-setup >= 1.0.34, but none of the providers can be 
installed
  - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes 
ovirt-ansible-hosted-engine-setup provided by 
ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch
  - cannot install the best update candidate for package 
ovirt-host-4.4.1-4.el8.x86_64
  - cannot install the best update candidate for package 
ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch
  - package ovirt-ansible-hosted-engine-setup-1.1.4-1.el8.noarch is filtered 
out by exclude filtering
  - package ovirt-ansible-hosted-engine-setup-1.1.5-1.el8.noarch is filtered 
out by exclude filtering
  - package ovirt-ansible-hosted-engine-setup-1.1.6-1.el8.noarch is filtered 
out by exclude filtering
  - package ovirt-ansible-hosted-engine-setup-1.1.7-1.el8.noarch is filtered 
out by exclude filtering
  - package ovirt-hosted-engine-setup-2.4.4-1.el8.noarch is filtered out by 
exclude filtering
  - package ovirt-hosted-engine-setup-2.4.5-1.el8.noarch is filtered out by 
exclude filtering
  - package ovirt-hosted-engine-setup-2.4.7-1.el8.noarch is filtered out by 
exclude filtering
  - package ovirt-hosted-engine-setup-2.4.8-1.el8.noarch is filtered out by 
exclude filtering
Nothing to do.
Complete!
___
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/QWWJCVAB3P2BXKM7QYDMOUWDX43MUYAZ/

[ovirt-users] Adding iscsi issue 4.3

2020-11-11 Thread thilburn 
When connecting an iscsi connection from an array I get the following popup "A 
database error occurred. Please contact your system administrator." I have 
checked everything and the only device connected right now is the single host 
in the datacenter. If I check the box " Approve operation" and click Ok it will 
error out with "A database error occurred. Please contact your system 
administrator." This is a new volume and no other machine is connected to this 
LUN or array. Below is from the vdsm log

2020-11-11 10:42:26,087-0800 INFO  (jsonrpc/0) [vdsm.api] START 
getDeviceList(storageType=3, guids=[u'32021001378a6ddad'], checkStatus=True, 
options={}) from=:::XX,46208, 
flow_id=d09dbfd6-2256-48ad-8597-b6c581def1fd, 
task_id=67c17255-3ffb-4e8b-b6d3-a4e40836d12c (api:48)
2020-11-11 10:42:26,650-0800 INFO  (jsonrpc/0) [storage.LVM] Overriding 
read_only mode current=True override=False (lvm:398)
2020-11-11 10:42:26,822-0800 INFO  (jsonrpc/0) [vdsm.api] FINISH getDeviceList 
return={'devList': [{'status': 'used', 'vendorID': 'ETIUSA', 'capacity': 
'3999688294400', 'fwrev': '10E', 'discard_zeroes_data': 0, 'vgUUID': '', 
'pvsize': '', 'pathlist': [{'connection': u'10.87.172.100', 'iqn': 
u'XX.XX.XX:storage3', 'portal': '0', 'port': '3260', 
'initiatorname': u'default'}], 'logicalblocksize': '512', 'discard_max_bytes': 
0, 'pathstatus': [{'type': 'iSCSI', 'physdev': 'sdc', 'capacity': 
'3999688294400', 'state': 'active', 'lun': '0'}], 'devtype': 'iSCSI', 
'physicalblocksize': '512', 'pvUUID': '', 'serial': 
'SETIUSA_UltraStorRS8IP4_2021001378A6DDAD', 'GUID': '32021001378a6ddad', 
'productID': 'UltraStorRS8IP4'}]} from=:::X,46208, 
flow_id=d09dbfd6-2256-48ad-8597-b6c581def1fd, 
task_id=67c17255-3ffb-4e8b-b6d3-a4e40836d12c (api:54)
2020-11-11 10:42:26,823-0800 INFO  (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call 
Host.getDeviceList succeeded in 0.74 seconds (__init__:312)
2020-11-11 10:42:27,158-0800 INFO  (jsonrpc/2) [api.host] START getAllVmStats() 
from=::1,48480 (api:48)
2020-11-11 10:42:27,159-0800 INFO  (jsonrpc/2) [api.host] FINISH getAllVmStats 
return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} 
from=::1,48480 (api:54)
2020-11-11 10:42:27,159-0800 INFO  (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call 
Host.getAllVmStats succeeded in 0.00 seconds (__init__:312)
2020-11-11 10:42:27,393-0800 INFO  (jsonrpc/1) [api.host] START getAllVmStats() 
from=:::X,46208 (api:48)
2020-11-11 10:42:27,394-0800 INFO  (jsonrpc/1) [api.host] FINISH getAllVmStats 
return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} 
from=:::X,46208 (api:54)
2020-11-11 10:42:27,394-0800 INFO  (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call 
Host.getAllVmStats succeeded in 0.00 seconds (__init__:312)


2020-11-11 10:43:12,323-0800 INFO  (jsonrpc/6) [vdsm.api] START 
createVG(vgname=u'35e95355-75db-4640-bf99-e576b9ce39aa', 
devlist=[u'32021001378a6ddad'], force=True, options=None) 
from=:::X,46208, flow_id=2c973734, 
task_id=91f2ab5b-017a-4c88-aa45-ece3bd920ce0 (api:48)
2020-11-11 10:43:12,348-0800 INFO  (jsonrpc/6) [storage.LVM] Overriding 
read_only mode current=True override=False (lvm:398)
2020-11-11 10:43:12,409-0800 INFO  (jsonrpc/4) [api.host] START getAllVmStats() 
from=:::XX,46208 (api:48)
2020-11-11 10:43:12,410-0800 INFO  (jsonrpc/4) [api.host] FINISH getAllVmStats 
return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} 
from=:::XXX,46208 (api:54)
2020-11-11 10:43:12,410-0800 INFO  (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC call 
Host.getAllVmStats succeeded in 0.00 seconds (__init__:312)
2020-11-11 10:43:12,520-0800 ERROR (jsonrpc/6) [storage.LVM] pvcreate failed 
with rc=5 (lvm:988)
2020-11-11 10:43:12,520-0800 ERROR (jsonrpc/6) [storage.LVM] [], ['  Device 
/dev/mapper/32021001378a6ddad excluded by a filter.'] (lvm:989)
2020-11-11 10:43:12,520-0800 INFO  (jsonrpc/6) [vdsm.api] FINISH createVG 
error=Failed to initialize physical device: 
("[u'/dev/mapper/32021001378a6ddad']",) from=:::XX,46208, 
flow_id=2c973734, task_id=91f2ab5b-017a-4c88-aa45-ece3bd920ce0 (api:52)
2020-11-11 10:43:12,520-0800 ERROR (jsonrpc/6) [storage.TaskManager.Task] 
(Task='91f2ab5b-017a-4c88-aa45-ece3bd920ce0') Unexpected error (task:875)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in 
_run
return fn(*args, **kargs)
  File "", line 2, in createVG
  File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method
ret = func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2146, in 
createVG
force=force)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/lvm.py", line 1256, in 
createVG
_initpvs(pvs, metadataSize, force)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/lvm.py", line 990, in 
_initpvs
raise se.PhysDevInitializationError(str(devices))
PhysDevInitializationError:

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

2020-11-11 Thread Martin Perina 
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

On Wed, Nov 11, 2020 at 4:32 PM Gianluca Cecchi 
wrote:

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


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

[ovirt-users] Re: Adding iscsi issue 4.3

2020-11-11 Thread thilburn 
Disregard, the array was setting the LBA support to 32 bit which was causing 
the block size to go way up. Also it was doing an auto partition of the volume 
which was causing the LV create to error out. Once I ran dd on the volume it 
all works correctly now.
___
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/T4MISVGF7WOWHJWZEZRI3KRS3RG42GCB/

[ovirt-users] Re: Cluster compatibility version 4.5 on oVirt 4.4

2020-11-11 Thread shadow emy 

Just to confirm i face similar problem.
Yes i saw that  warning too :  "Upgrade Cluster Compatibility Level"   to 
upgrade the Cluster to version 4.5.
Though when i try to do that there are a lot of errors.
 
In GUI :

Error while executing action: Cannot change Cluster Compatibility Version to 
higher version when there are active Hosts with lower version.
-Please move Host host1, host2, host3  with lower version to maintenance first.

In engine.log :

WARN  [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-163) 
[2c681b74-8666-4f2f-b2e0-6b20e98f417e] Validation of action 'UpdateCluster' 
failed for user admin@internal-authz. Reasons: 
VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,$host host1, host2, 
host3,CLUSTER_CANNOT_UPDATE_COMPATIBILITY_VERSION_WITH_LOWER_HOSTS

I did not find any documentation for 4.5 cluster compatibility,  so i like as 
well to understand why is that option present there.
It will be used when ovirt 4.5.x will be released ? 

___
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/3UGQ6HPT2HTEGEP6GZUZ737SXR4K7TTJ/

[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 shadow emy 
Yes after that i run  engine-setup, then  i was able to run " yum update"  on 
the hosted-engine vm without errors.

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

[ovirt-users] Re: Upgrade OVIRT from 3.6 to 4.3

2020-11-11 Thread Alex K 
On Wed, Nov 11, 2020, 17:03 Miguel Angel Costas 
wrote:

> Hi Guys!
>
> I need to upgrade from 3.6 to 4.3 and I have a doubt.
> Do I need to restard VMs for each upgrade (DC Compatibilty 1° 4.0  - 2°
> 4.1 - 3° 4.2 and 4° 4.3) or can modify the compatibilty  from 3.6 to 4.2
> and restart the vms in this only step.
>
I would restart to complete each step at a time.

>
> Best regards
> ___
> 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/DAXCGYEQM4BM3KWMRAY4HMGE2YAHDB2H/
>
___
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/J573QMSFII62CBPC47CJJ73AITZETWMI/

[ovirt-users] BUG: after upgrading 4.4.2 to 4.4.3 ISO Domain show empty list

2020-11-11 Thread Tarun Kushwaha 
I have upgraded 4.4.2 to 4.4.3 afterthat ISO Domain is not showing any ISO 
files .its show empty list i think this is bug in 4.4.3
___
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/NIDCLKBZXJTXOENFIJZFC6HFXURGP6OI/

[ovirt-users] Re: Cluster compatibility version 4.5 on oVirt 4.4

2020-11-11 Thread Ritesh Chikatwar 
Hello,

To upgrade to cluster 4.5 you need a 8.3 host.
I guess still CentOS 8.3 is not available. I am not sure on CentOS 8.3
availability.
If it's available please make sure your host is upgraded to 8.3 .


On Thu, Nov 12, 2020, 5:38 AM shadow emy  wrote:

>
> Just to confirm i face similar problem.
> Yes i saw that  warning too :  "Upgrade Cluster Compatibility Level"   to
> upgrade the Cluster to version 4.5.
> Though when i try to do that there are a lot of errors.
>
> In GUI :
>
> Error while executing action: Cannot change Cluster Compatibility Version
> to higher version when there are active Hosts with lower version.
> -Please move Host host1, host2, host3  with lower version to maintenance
> first.
>
> In engine.log :
>
> WARN  [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-163)
> [2c681b74-8666-4f2f-b2e0-6b20e98f417e] Validation of action 'UpdateCluster'
> failed for user admin@internal-authz. Reasons:
> VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,$host host1, host2,
> host3,CLUSTER_CANNOT_UPDATE_COMPATIBILITY_VERSION_WITH_LOWER_HOSTS
>
> I did not find any documentation for 4.5 cluster compatibility,  so i like
> as well to understand why is that option present there.
> It will be used when ovirt 4.5.x will be released ?
>
> ___
> 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/3UGQ6HPT2HTEGEP6GZUZ737SXR4K7TTJ/
>
___
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/ZPLFRE7TMLQDSVVTQYU7BYGNAIOKC5HF/

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

2020-11-11 Thread Matteo Bonardi 
Il giorno mer 11 nov 2020 alle ore 11:01 Yedidyah Bar David 
ha scritto:

> On Wed, Nov 11, 2020 at 11:49 AM Matteo Bonardi  wrote:
> >
> > Hi Didi,
> >
> > > On Tue, Nov 10, 2020 at 7:18 PM Strahil Nikolov via Users
> > >  > >
> > > I already suggested to open a bug for this earlier in this thread.
> >
> > I will open a bug for that.
>
> Thanks.
>
> >
> > > I am not sure. I talked with Sandro about this, and we agreed that a
> > > common enterprise requirement is being able to use a local _mirror_
> > > (e.g. Foreman), mainly for disconnected use (without an Internet
> > > connection). A proxy is technically quite different, even if in
> > > principle can be used for the same need.
> > >
> >
> > I can understand your point, but since the deploy script already checks
> that the proxy is set, I don't see why it can't pass this information to
> the engine.
>
> Sorry, where?
>

Sincerely I didn't read the code, but reading the log there are more than
one reference to proxy.
For example:

2020-11-10 18:15:48,518+0100 WARNING
otopi.plugins.gr_he_common.network.gateway gateway._setup:88 It seems that
this host is configured to use a *proxy*, please ensure that this host will
be able to reach the engine VM trough that proxy or add a specific
exception.
2020-11-10 18:15:49,637+0100 DEBUG
otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:197
ansible-playbook: env: {'LS_COLORS': [..], 'USER': 'root', 'PWD': '',
'HOME': '', 'SSH_CLIENT': '', *'https_proxy': 'http://10.248.2.50:3128/
', 'http_proxy': 'http://10.248.2.50:3128/
', 'no_proxy': '.'*,
'SSH_TTY': '/dev/pts/0', 'MAIL': '/var/spool/mail/root', 'SHELL':
'/bin/bash', 'TERM': 'xterm', 'SHLVL': '1', 'PYTHONPATH':
'/usr/share/ovirt-hosted-engine-setup/scripts/..:',[..],
'HE_ANSIBLE_LOG_PATH':
'/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-ansible-get_network_interfaces-20201110181549-tppuv6.log'}
2020-11-10 18:17:11,505+0100 INFO
otopi.ovirt_hosted_engine_setup.ansible_utils
ansible_utils._process_output:111 TASK
[ovirt.ovirt.hosted_engine_setup : *Check
http/https proxy*]

I'm not sure at all, but the log makes me think the proxy is being checked
more than once.
Of course I can be wrong.


> Also:
>
> On Wed, Nov 11, 2020 at 11:39 AM Matteo Bonardi  wrote:
> >
> > Thanks to all yours suggestions I, finally, complete the deploy with
> success.
> > The solution is been to edit the file
> /usr/share/ansible/roles/ovirt.engine-setup/tasks/install_packages.yml
> adding the proxy variable:
>
> Which version?
>
> Perhaps you had 4.4.2 and then updated to 4.4.3 before retrying, or
> something similar?
>

Before retry the deploy, I have completely cleanup the installation with:

[root@ ~]# ovirt-hosted-engine-cleanup
[root@ ~]# yum remove ovirt-*

And then reinstall all:

[root@ ~]# yum install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
[root@ ~]# yum install ovirt-engine-appliance
[root@ ~]# yum install ovirt-hosted-engine-setup

I am a bit confused on how to check the version (it is embarrassing, but I
am new on ovirt and ansible).
There is a mismatch between the version in deployment server and in engine
vm.
I have attached the rpm version of both.
The manager web console shows 4.4.2 as version.


> >
> > - name: Install oVirt Engine package
> >   package:
> > name: "ovirt-engine"
> > state: present
> >   environment:
> > https_proxy: "http://:"
> > http_proxy: "http://:"
> > ftp_proxy: "http://:"
> >   when: ovirt_engine_setup_product_type | lower == 'ovirt'
> > [..]
> >
> > 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
>
> Can't guess, though, your exact flow - if you suspect a bug, please
> check/share relevant logs (including dnf, but perhaps also ansible),
> perhaps in a separate bug.
>
> Sorry if this is confusing/messy. Feel free to comment on [1] if you
> have something specific to add (it's a RHV bug, though, so if unsure,
> perhaps file another bug. RHV's and oVirt's documentation are not as
> aligned as their source code).
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1891749
>
> Thanks and best regards,
> --
> Didi
>
>
Regards,
Matteo