[ovirt-users] ovirt upgrade - Failed to execute stage 'Misc configuration' FATAL: Ident authentication failed for user "root"

[marek]

upgrade from ovirt 4.4.4 to 4.5.5

engine-setup

2023-01-24 00:35:17,885+0100 DEBUG otopi.context 
context._executeMethod:145 method exception

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, 
in _executeMethod

    method['method']()
  File 
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-grafana-dwh/db/default_privileges.py", 
line 51, in _misc_set_default_privileges

    user=self.environment[ogdwhcons.GrafanaDBEnv.USER],
  File 
"/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py", 
line 1808, in setDefaultPrivilegesReadOnlyForUser

    ownConnection=True,
  File 
"/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py", 
line 249, in execute

    database=database,
  File 
"/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py", 
line 182, in connect

    sslmode=sslmode,
  File "/usr/lib64/python3.6/site-packages/psycopg2/__init__.py", line 
127, in connect

    conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: FATAL:  Ident authentication failed for user 
"root"

FATAL:  Ident authentication failed for user "root"

2023-01-24 00:35:17,886+0100 ERROR otopi.context 
context._executeMethod:154 Failed to execute stage 'Misc configuration': 
FATAL:  Ident authentication failed for user "root"

FATAL:  Ident authentication failed for user "root"


any tips?

Marek
___
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/KYCCMZW6Y5EO4LLIP2NDG2Y2SCVHUCJB/

[ovirt-users] OVirt Upgrade from 4.3 to 4.4 - Hosted engine

[ccesario]

Hello,
Could someone please inform if Upgrade from OVirt 4.3 to 4.4 when using Hosted 
engine is it supported !? According the documentation 
https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3 the 
upgrade procedure make reference only  to "standalone engine".
If it is supported, what is correct steps to do it?

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

[ovirt-users] oVirt upgrade problems...

[matteo fedeli]

Hi at all, I have many problems after upgrade ovirt version. I come from 
4.3.5.2. 

When I upgraded to 4.3.7 my three host (hyperconverged emviroment) I passed a 
few days of instability: HA agent down gluster problem...
When I rebooted for the umpteenth time (after reinitialized lockspace, heal, 
heal full...) all cames up ha agent and broker included.
Two days after arrived 4.3.8, so i decided to start the update, america with 
success, europa after a various problems (as described before) came up.
Asia host, after 30 second of updating the engine goes down together with all 
three nodes ... Are there any known important bugs?

This is the state of my nodes: 
https://pastebin.com/2XsnTyHi
https://pastebin.com/ZeKTdaZ7
https://pastebin.com/ZDUBg4vG
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/SUWZZFCRUSXIITRTV2TBWAMWKKP3L2PS/

[ovirt-users] ovirt upgrade

[David David]

hi all

how do upgrade from 4.2.5 to 4.3.7 ?
what steps are necessary, are the same as when upgrading from 4.1 to 4.2?

 # engine-upgrade-check
 # yum update ovirt*setup*
 # engine-setup


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

[ovirt-users] oVirt upgrade version from 4.2 to 4.3

[dmarini]

I cannot find an official upgrade procedure from 4.2 to 4.3 oVirt version on 
this page: https://www.ovirt.org/documentation/upgrade-guide/upgrade-guide.html

Can you help me?

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

[ovirt-users] oVirt upgrade to specific version

[Leo David]

Hi,
I have a running 4.2.7 hci cluster which I would upgrade to 4.2.8.
If I do this in the standard manner (yum update in engine vm and then the
nodes from engine UI) I assume it will go to 4.3, which I would rather
avoid for now.
Is there a way for getting it updated strictelly to 4.2.8 ?

Thanks,

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

[ovirt-users] ovirt upgrade 4.3 - dashboard is dispalyed 2x in top left corner menu

[mhumaj]

After the upgrade to ovirt 4.3, I can see two entry for dashboard in top left 
corner menu. Is there any way how to get rid of the duplicity?

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

[ovirt-users] oVirt upgrade 4.1 to 4.2

[p . staniforth]

Hello when we did a live upgrade of our VDC from 4.1 to 4.2 we had a large 
number of VMs running that had a Custom Compatibility Version set to 4.1 to 
allow them to keep running while the cluster and VDC were upgraded. 
Unfortunately there was a large number of snapshots taken be the users before 
they were restarted their VMs so they have the Custom_Compatibility_Version set 
to 4.1 and so can't run in the 4.2 VDC, is there a way to search for them in 
the API or SDK because I can only find them in the events log when they fail to 
start.

Thanks,
  Paul S.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/4A5WZ3ULHI7IAG44P3T5RTH5LPXK6BJT/

[ovirt-users]ovirt upgrade 4.1 - 4.2 fail

[Альбов Леонид]

Hello!

After upgrade engin from 4.1 to 4.2 all Host in status Activate or Non 
Operational.

Error Message:
VDSM cluster-nodeXX command GetCapabilitiesAsyncVDS failed: General SSLEngine 
problem

Need help!

(Centos 7)

engine.log
2018-07-18 17:37:46,903+03 INFO 
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] 
Connecting to cluster-node11.office.vliga/10.252.252.211
2018-07-18 17:37:46,905+03 ERROR 
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable 
to process messages General SSLEngine problem
2018-07-18 17:37:46,906+03 ERROR 
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] 
(EE-ManagedThreadFactory-engineScheduled-Thread-5) [] Unable to 
RefreshCapabilities: VDSNetworkException: VDSGenericException: 
VDSNetworkException: General SSLEngine problem
2018-07-18 17:37:47,744+03 INFO 
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] 
Connecting to cluster-node10.office.vliga/10.252.252.210
2018-07-18 17:37:47,747+03 ERROR 
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable 
to process messages General SSLEngine problem
2018-07-18 17:37:47,747+03 ERROR 
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] 
(EE-ManagedThreadFactory-engineScheduled-Thread-95) [] Unable to 
RefreshCapabilities: VDSNetworkException: VDSGenericException: 
VDSNetworkException: General SSLEngine problem
2018-07-18 17:37:52,814+03 INFO 
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] 
Connecting to cluster-node6.office.vliga/10.252.252.206
2018-07-18 17:37:52,816+03 ERROR 
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable 
to process messages General SSLEngine problem
2018-07-18 17:37:52,816+03 ERROR 
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] 
(EE-ManagedThreadFactory-engineScheduled-Thread-55) [] Unable to 
RefreshCapabilities: VDSNetworkException: VDSGenericException: 
VDSNetworkException: General SSLEngine problem
2018-07-18 17:37:59,513+03 INFO 
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] 
Connecting to cluster-node6.office.vliga/10.252.252.206
2018-07-18 17:37:59,514+03 ERROR 
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable 
to process messages General SSLEngine problem
2018-07-18 17:37:59,517+03 INFO 
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] 
Connecting to cluster-node10.office.vliga/10.252.252.210
2018-07-18 17:37:59,519+03 ERROR 
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable 
to process messages General SSLEngine problem
-- 
Леонид Альбов___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/KET4ZHPCUJGVGNYSC7XHRZRF22CKV6ED/

[ovirt-users] ovirt upgrade 4.1 -> 4.2: host bricks down

[Alex K]

Hi all,

I have a ovirt 2 node cluster for testing with self hosted engine on top
gluster.

The cluster was running on 4.1. After the upgrade to 4.2, which generally
went smoothly, I am seeing that the bricks of one of the hosts (v1) are
detected as down, while the gluster is ok when checked with command lines
and all volumes mounted.

Below is the error that the engine logs:

2018-06-17 00:21:26,309+03 ERROR
[org.ovirt.engine.core.bll.gluster.GlusterSyncJob] (DefaultQuartzScheduler2)
[98d7e79] Error while refreshing brick statuses for volume 'vms' of cluster
'test': null
2018-06-17 00:21:26,318+03 ERROR
[org.ovirt.engine.core.vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand]
(DefaultQuartzScheduler2) [98d7e79] Command
'GetGlusterLocalLogicalVolumeListVDSCommand(HostName = v0.test-group.com,
VdsIdVDSCommandParametersBase:{hostId='d5a96118-ca49-411f-86cb-280c7f9c421f'})'
execution failed: null
2018-06-17 00:21:26,323+03 ERROR
[org.ovirt.engine.core.vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand]
(DefaultQuartzScheduler2) [98d7e79] Command
'GetGlusterLocalLogicalVolumeListVDSCommand(HostName = v1.test-group.com,
VdsIdVDSCommandParametersBase:{hostId='12dfea4a-8142-484e-b912-0cbd5f281aba'})'
execution failed: null
2018-06-17 00:21:27,015+03 INFO
[org.ovirt.engine.core.bll.lock.InMemoryLockManager]
(DefaultQuartzScheduler9)
[426e7c3d] Failed to acquire lock and wait lock
'EngineLock:{exclusiveLocks='[0002-0002-0002-0002-017a=GLUSTER]',
sharedLocks=''}'
2018-06-17 00:21:27,926+03 ERROR
[org.ovirt.engine.core.bll.gluster.GlusterSyncJob] (DefaultQuartzScheduler2)
[98d7e79] Error while refreshing brick statuses for volume 'engine' of
cluster 'test': null

Apart from this everything else is operating normally and VMs are running
on both hosts.

Any idea to isolate this issue?

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

[ovirt-users] oVirt upgrade node from 4.1.9 to 4.2.3

[rcasebier]

My engine is upgraded and running 4.2.3. I am testing out upgrading my first 
local storage node. I installed the 4.2 release repo and ran a yum update. I 
had to manually install the following packages form CentOS (yum install udisks2 
lshw iotop libvirt-daemon-config-network virt-install python-prettytable) for 
some reason these dependencies did not exist in the oVirt repo's. I was able to 
run yum update after fixing this issue and my host was installed with 4.2.3. 
After a reboot, it failed to boot, the host failed to start the login service 
and the authorization manager. Has anyone run into this issue? 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org

Re: [ovirt-users] oVirt Upgrade 4.1 -> 4.2 fails with YUM dependency problems (CentOS)

[Frank Thommen]

Following the minor release upgrade instructions on 
https://www.ovirt.org/documentation/upgrade-guide/chap-Updates_between_Minor_Releases/ 
solved this issue.  Now we are bumping into an other issue, for which 
I'll probably open an other thread.


frank


On 02/02/2018 05:33 PM, Chas Hockenbarger wrote:
I haven't tried this yet, but looking at the detailed error, the 
implication is that your current install is less than 4.1.7, which is 
where the conflict is. Have you tried updating to > 4.1.7 before upgrading?



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt Upgrade 4.1 -> 4.2 fails with YUM dependency problems (CentOS)

[Frank Thommen]

On 02/02/18 17:33, Chas Hockenbarger wrote:
I haven't tried this yet, but looking at the detailed error, the 
implication is that your current install is less than 4.1.7, which is 
where the conflict is. Have you tried updating to > 4.1.7 before upgrading?


I had tried with `yum upgrade` to no avail and just realized, that this 
has to be done with ovirt-engine commands.  I'll do this after the weekend.


frank

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt Upgrade 4.1 -> 4.2 fails with YUM dependency problems (CentOS)

[Chas Hockenbarger]

I haven't tried this yet, but looking at the detailed error, the implication is that your current install is less than 4.1.7, which is where the conflict is. Have you tried updating to > 4.1.7 before upgrading?___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] oVirt Upgrade 4.1 -> 4.2 fails with YUM dependency problems (CentOS)

[Frank Thommen]

Hi,

following the oVirt upgrade procedure on a CentOS system 
(https://www.ovirt.org/release/4.2.0/#centos--rhel) I fail at step `yum 
update "ovirt-*-setup*"` with a YUM dependency problem:



$ yum update "ovirt-*-setup*"
[...]
ovirt-engine-setup-plugin-ovirt-engine conflicts with 
ovirt-engine-4.1.3.5-1.el7.centos.noarch

[...]
$

For the complete yum update output see below.

I also noticed, that after having installed ovirt-release42, the old 
oVirt 4.1 repos were still present on the system.  I disabled them 
manually to no avail.


`yum update ovirt-engine` results in "No packages marked for update".


Does anyone know, how we can fix this problem?

Cheers
frank

- complete yum update output -
$ yum update "ovirt-*-setup*"
Loaded plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
 * base: centos.alpha-labs.net
 * extras: centos.mirror.iphh.net
 * ovirt-4.2: ftp.nluug.nl
 * ovirt-4.2-epel: epel.besthosting.ua
 * updates: centos.mirror.iphh.net
Resolving Dependencies
--> Running transaction check
---> Package ovirt-engine-dwh-setup.noarch 0:4.1.9-1.el7.centos will be 
updated
---> Package ovirt-engine-dwh-setup.noarch 0:4.2.1-1.el7.centos will be 
an update
--> Processing Dependency: rh-postgresql95-postgresql-server for 
package: ovirt-engine-dwh-setup-4.2.1-1.el7.centos.noarch
---> Package ovirt-engine-setup.noarch 0:4.1.9.1-1.el7.centos will be 
updated
---> Package ovirt-engine-setup.noarch 0:4.2.0.2-1.el7.centos will be an 
update
---> Package ovirt-engine-setup-base.noarch 0:4.1.9.1-1.el7.centos will 
be updated
---> Package ovirt-engine-setup-base.noarch 0:4.2.0.2-1.el7.centos will 
be an update
--> Processing Dependency: otopi >= 1.7.1 for package: 
ovirt-engine-setup-base-4.2.0.2-1.el7.centos.noarch
--> Processing Dependency: ovirt-engine-lib >= 4.2.0.2-1.el7.centos for 
package: ovirt-engine-setup-base-4.2.0.2-1.el7.centos.noarch
---> Package ovirt-engine-setup-plugin-ovirt-engine.noarch 
0:4.1.9.1-1.el7.centos will be updated
---> Package ovirt-engine-setup-plugin-ovirt-engine.noarch 
0:4.2.0.2-1.el7.centos will be an update
--> Processing Dependency: openvswitch-ovn-central >= 2.7 for package: 
ovirt-engine-setup-plugin-ovirt-engine-4.2.0.2-1.el7.centos.noarch
--> Processing Dependency: ovirt-provider-ovn for package: 
ovirt-engine-setup-plugin-ovirt-engine-4.2.0.2-1.el7.centos.noarch
---> Package ovirt-engine-setup-plugin-ovirt-engine-common.noarch 
0:4.1.9.1-1.el7.centos will be updated
---> Package ovirt-engine-setup-plugin-ovirt-engine-common.noarch 
0:4.2.0.2-1.el7.centos will be an update
---> Package ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch 
0:4.1.9.1-1.el7.centos will be updated
---> Package ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch 
0:4.2.0.2-1.el7.centos will be an update
---> Package ovirt-engine-setup-plugin-websocket-proxy.noarch 
0:4.1.9.1-1.el7.centos will be updated
---> Package ovirt-engine-setup-plugin-websocket-proxy.noarch 
0:4.2.0.2-1.el7.centos will be an update
---> Package ovirt-imageio-proxy-setup.noarch 
0:1.0.0-0.201701151456.git89ae3b4.el7.centos will be updated
---> Package ovirt-imageio-proxy-setup.noarch 0:1.2.0-1.el7.centos will 
be an update

--> Running transaction check
---> Package openvswitch-ovn-central.x86_64 1:2.7.3-1.1fc27.el7 will be 
installed
--> Processing Dependency: openvswitch-ovn-common for package: 
1:openvswitch-ovn-central-2.7.3-1.1fc27.el7.x86_64
--> Processing Dependency: openvswitch for package: 
1:openvswitch-ovn-central-2.7.3-1.1fc27.el7.x86_64

---> Package otopi.noarch 0:1.6.3-1.el7.centos will be updated
--> Processing Dependency: otopi = 1.6.3-1.el7.centos for package: 
otopi-java-1.6.3-1.el7.centos.noarch

---> Package otopi.noarch 0:1.7.5-1.el7.centos will be an update
---> Package ovirt-engine-lib.noarch 0:4.1.9.1-1.el7.centos will be updated
---> Package ovirt-engine-lib.noarch 0:4.2.0.2-1.el7.centos will be an 
update
---> Package ovirt-provider-ovn.noarch 0:1.2.2-1.el7.centos will be 
installed
--> Processing Dependency: python-openvswitch >= 2.7 for package: 
ovirt-provider-ovn-1.2.2-1.el7.centos.noarch
--> Processing Dependency: python2-ovsdbapp for package: 
ovirt-provider-ovn-1.2.2-1.el7.centos.noarch
---> Package rh-postgresql95-postgresql-server.x86_64 0:9.5.9-1.el7 will 
be installed
--> Processing Dependency: rh-postgresql95-postgresql-libs(x86-64) = 
9.5.9-1.el7 for package: 
rh-postgresql95-postgresql-server-9.5.9-1.el7.x86_64
--> Processing Dependency: rh-postgresql95-postgresql(x86-64) = 
9.5.9-1.el7 for package: 
rh-postgresql95-postgresql-server-9.5.9-1.el7.x86_64
--> Processing Dependency: rh-postgresql95-runtime for package: 
rh-postgresql95-postgresql-server-9.5.9-1.el7.x86_64
--> Processing Dependency: /usr/bin/scl_source for package: 
rh-postgresql95-postgresql-server-9.5.9-1.el7.x86_64
--> Processing Dependency: libpq.so.rh-postgresql95-5()(64bit) for 
package: rh-postgresql95-postgresql-server-9.5.9-1.el7.x86_64

--> Running transaction 

Re: [ovirt-users] ovirt upgrade problem

[Simone Tiraboschi]

On Tue, Sep 19, 2017 at 9:47 AM, Simone Tiraboschi 
wrote:

>
>
> On Mon, Sep 18, 2017 at 12:19 PM, gabriel_skup...@o2.pl <
> gabriel_skup...@o2.pl> wrote:
>
>> Hi,
>>
>> While trying to upgrade my ovirt node from 4.1.5 to 4.1.6 I get the below
>> errors. Can you help?
>>
>> .
>> .
>> .
>> 2017-09-18 09:25:30 DEBUG otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.verbose:76 Yum Downloading: ovirt-node-ng-image-update-4.1
>> .6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch.rpm 550 M(99%)
>> 2017-09-18 09:25:30 DEBUG otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.verbose:76 Yum Downloading: ovirt-node-ng-image-update-4.1
>> .6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch.rpm 551 M(99%)
>> 2017-09-18 09:25:30 DEBUG otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.verbose:76 Yum Downloading: ovirt-node-ng-image-update-4.1
>> .6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch.rpm 551 M(99%)
>> 2017-09-18 09:25:31 INFO otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.info:80 Yum Download/Verify: ovirt-node-ng-image-update-4.1
>> .6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch
>> 2017-09-18 09:25:35 DEBUG otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.verbose:76 Yum Downloading: ovirt-node-ng-image-update-4.1
>> .6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch.rpm 551 M(100%)
>> 2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.info:80 Yum Status: Check Package Signatures
>> 2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.info:80 Yum Status: Running Test Transaction
>> Running Transaction Check
>> 2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.info:80 Yum Status: Running Transaction
>> 2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.info:80 Yum obsoleting: 1/3: ovirt-node-ng-image-update-4.1
>> .6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch
>> 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.verbose:76 Yum Script sink: warning:
>> %post(ovirt-node-ng-image-update-4.1.6-0.2.rc2.2017083008275
>> 7.gite10769f.el7.centos.noarch) scriptlet failed, exit status 1
>>
>
> The upgrade issue seams here but from this log is not really clear.
> Could you please check /var/log/messages, yum logs and /tmp/imgbased.log ?
>

Ok, reproduced.
I filed this one to track it:
https://bugzilla.redhat.com/show_bug.cgi?id=1493033




>
> By the way ovirt-node-ng-image-update-4.1.6-0.2.rc2.20170830082757.
> gite10769f.el7.centos.noarch.rpm is just a pre-release package which
> shouldn't be there and the stable one for 4.1.6 is still waiting for
> qemu-kvm-ev 2.9.
>
>
>>
>> 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update.noarch
>> 0:4.1.6-0.2.rc2.20170830082757.gite10769f.el7.centos - u
>> 2017-09-18 09:32:11 ERROR otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.error:85 Yum Non-fatal POSTIN scriptlet failure in rpm package
>> ovirt-node-ng-image-update-4.1.6-0.2.rc2.20170830082757.gite
>> 10769f.el7.centos.noarch
>> 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update-4.1
>> .6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch
>> 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update-4.1
>> .6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch
>> 2017-09-18 09:32:11 INFO otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.info:80 Yum erase: 2/3: ovirt-node-ng-image-update-pla
>> ceholder
>> 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update-pla
>> ceholder-4.1.5-1.el7.centos.noarch
>> 2017-09-18 09:32:11 INFO otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.info:80 Yum updated: 3/3: ovirt-node-ng-image-update
>> 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update-4.1
>> .5-1.el7.centos.noarch
>> 2017-09-18 09:32:12 INFO otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.info:80 Yum Verify: 1/3: ovirt-node-ng-image-update.noarch
>> 0:4.1.6-0.2.rc2.20170830082757.gite10769f.el7.centos - u
>> 2017-09-18 09:32:12 INFO otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.info:80 Yum Verify: 2/3: 
>> ovirt-node-ng-image-update-placeholder.noarch
>> 0:4.1.5-1.el7.centos - od
>> 2017-09-18 09:32:12 INFO otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.info:80 Yum Verify: 3/3: ovirt-node-ng-image-update.noarch
>> 0:4.1.5-1.el7.centos - ud
>> 2017-09-18 09:32:12 DEBUG otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.verbose:76 Yum Transaction processed
>> 2017-09-18 09:32:12 DEBUG otopi.context context._executeMethod:142 method
>> exception
>> Traceback (most recen

Re: [ovirt-users] ovirt upgrade problem

[Simone Tiraboschi]

On Mon, Sep 18, 2017 at 12:19 PM, gabriel_skup...@o2.pl <
gabriel_skup...@o2.pl> wrote:

> Hi,
>
> While trying to upgrade my ovirt node from 4.1.5 to 4.1.6 I get the below
> errors. Can you help?
>
> .
> .
> .
> 2017-09-18 09:25:30 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:76 Yum Downloading: ovirt-node-ng-image-update-4.
> 1.6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch.rpm 550 M(99%)
> 2017-09-18 09:25:30 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:76 Yum Downloading: ovirt-node-ng-image-update-4.
> 1.6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch.rpm 551 M(99%)
> 2017-09-18 09:25:30 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:76 Yum Downloading: ovirt-node-ng-image-update-4.
> 1.6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch.rpm 551 M(99%)
> 2017-09-18 09:25:31 INFO otopi.plugins.otopi.packagers.yumpackager
> yumpackager.info:80 Yum Download/Verify: ovirt-node-ng-image-update-4.
> 1.6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch
> 2017-09-18 09:25:35 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:76 Yum Downloading: ovirt-node-ng-image-update-4.
> 1.6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch.rpm 551 M(100%)
> 2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers.yumpackager
> yumpackager.info:80 Yum Status: Check Package Signatures
> 2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers.yumpackager
> yumpackager.info:80 Yum Status: Running Test Transaction
> Running Transaction Check
> 2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers.yumpackager
> yumpackager.info:80 Yum Status: Running Transaction
> 2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers.yumpackager
> yumpackager.info:80 Yum obsoleting: 1/3: ovirt-node-ng-image-update-4.
> 1.6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch
> 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:76 Yum Script sink: warning: %post(ovirt-node-ng-image-
> update-4.1.6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch)
> scriptlet failed, exit status 1
>

The upgrade issue seams here but from this log is not really clear.
Could you please check /var/log/messages, yum logs and /tmp/imgbased.log ?

By the way
ovirt-node-ng-image-update-4.1.6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch.rpm
is just a pre-release package which shouldn't be there and the stable one
for 4.1.6 is still waiting for qemu-kvm-ev 2.9.


>
> 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update.noarch
> 0:4.1.6-0.2.rc2.20170830082757.gite10769f.el7.centos - u
> 2017-09-18 09:32:11 ERROR otopi.plugins.otopi.packagers.yumpackager
> yumpackager.error:85 Yum Non-fatal POSTIN scriptlet failure in rpm package
> ovirt-node-ng-image-update-4.1.6-0.2.rc2.20170830082757.
> gite10769f.el7.centos.noarch
> 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update-4.
> 1.6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch
> 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update-4.
> 1.6-0.2.rc2.20170830082757.gite10769f.el7.centos.noarch
> 2017-09-18 09:32:11 INFO otopi.plugins.otopi.packagers.yumpackager
> yumpackager.info:80 Yum erase: 2/3: ovirt-node-ng-image-update-placeholder
> 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update-
> placeholder-4.1.5-1.el7.centos.noarch
> 2017-09-18 09:32:11 INFO otopi.plugins.otopi.packagers.yumpackager
> yumpackager.info:80 Yum updated: 3/3: ovirt-node-ng-image-update
> 2017-09-18 09:32:11 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-update-4.
> 1.5-1.el7.centos.noarch
> 2017-09-18 09:32:12 INFO otopi.plugins.otopi.packagers.yumpackager
> yumpackager.info:80 Yum Verify: 1/3: ovirt-node-ng-image-update.noarch
> 0:4.1.6-0.2.rc2.20170830082757.gite10769f.el7.centos - u
> 2017-09-18 09:32:12 INFO otopi.plugins.otopi.packagers.yumpackager
> yumpackager.info:80 Yum Verify: 2/3: 
> ovirt-node-ng-image-update-placeholder.noarch
> 0:4.1.5-1.el7.centos - od
> 2017-09-18 09:32:12 INFO otopi.plugins.otopi.packagers.yumpackager
> yumpackager.info:80 Yum Verify: 3/3: ovirt-node-ng-image-update.noarch
> 0:4.1.5-1.el7.centos - ud
> 2017-09-18 09:32:12 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:76 Yum Transaction processed
> 2017-09-18 09:32:12 DEBUG otopi.context context._executeMethod:142 method
> exception
> Traceback (most recent call last):
>   File "/tmp/ovirt-kRPMlHbiO5/pythonlib/otopi/context.py", line 132, in
> _executeMethod
> method['method']()
>   File "/tmp/ovirt-kRPMlHbiO5/otopi-plugins/otopi/packagers/yumpackager.py",
> line 261, in _packages
> self._miniyum.processTransaction

[ovirt-users] ovirt upgrade problem

[gabriel_skupien]

Hi,   While trying to upgrade my ovirt node from 4.1.5 to 4.1.6 I get the below 
errors. Can you help?   .  .  .  2017-09-18 09:25:30 DEBUG 
otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: 
ovirt-node-ng-image-update-4.1 550 M(99%)  2017-09-18 09:25:30 DEBUG 
otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: 
ovirt-node-ng-image-update-4.1 551 M(99%)  2017-09-18 09:25:30 DEBUG 
otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: 
ovirt-node-ng-image-update-4.1 551 M(99%)  2017-09-18 09:25:31 INFO 
otopi.plugins.otopi.packagers. yumpackager.info:80 Yum Download/Verify: 
ovirt-node-ng-image-update-4.1  2017-09-18 09:25:35 DEBUG 
otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: 
ovirt-node-ng-image-update-4.1 551 M(100%)  2017-09-18 09:25:35 INFO 
otopi.plugins.otopi.packagers. yumpackager.info:80 Yum Status: Check Package 
Signatures  2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers. 
yumpackager.info:80 Yum Status: Running Test Transaction  Running Transaction 
Check  2017-09-18 09:25:35 INFO otopi.plugins.otopi.packagers. 
yumpackager.info:80 Yum Status: Running Transaction  2017-09-18 09:25:35 INFO 
otopi.plugins.otopi.packagers. yumpackager.info:80 Yum obsoleting: 1/3: 
ovirt-node-ng-image-update-4.1  2017-09-18 09:32:11 DEBUG 
otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Script sink: warning: 
%post(ovirt-node-ng-image-upda scriptlet failed, exit status 1   2017-09-18 
09:32:11 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Done: 
ovirt-node-ng-image-update.noa 0:4.1.6-0.2.rc2.20170830082757 - u  2017-09-18 
09:32:11 ERROR otopi.plugins.otopi.packagers. yumpackager.error:85 Yum 
Non-fatal POSTIN scriptlet failure in rpm package 
ovirt-node-ng-image-update-4.1  2017-09-18 09:32:11 DEBUG 
otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Done: 
ovirt-node-ng-image-update-4.1  2017-09-18 09:32:11 DEBUG 
otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Done: 
ovirt-node-ng-image-update-4.1  2017-09-18 09:32:11 INFO 
otopi.plugins.otopi.packagers. yumpackager.info:80 Yum erase: 2/3: 
ovirt-node-ng-image-update-pla  2017-09-18 09:32:11 DEBUG 
otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Done: 
ovirt-node-ng-image-update-pla  2017-09-18 09:32:11 INFO 
otopi.plugins.otopi.packagers. yumpackager.info:80 Yum updated: 3/3: 
ovirt-node-ng-image-update  2017-09-18 09:32:11 DEBUG 
otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Done: 
ovirt-node-ng-image-update-4.1  2017-09-18 09:32:12 INFO 
otopi.plugins.otopi.packagers. yumpackager.info:80 Yum Verify: 1/3: 
ovirt-node-ng-image-update.noa 0:4.1.6-0.2.rc2.20170830082757 - u  2017-09-18 
09:32:12 INFO otopi.plugins.otopi.packagers. yumpackager.info:80 Yum Verify: 
2/3: ovirt-node-ng-image-update-pla 0:4.1.5-1.el7.centos - od  2017-09-18 
09:32:12 INFO otopi.plugins.otopi.packagers. yumpackager.info:80 Yum Verify: 
3/3: ovirt-node-ng-image-update.noa 0:4.1.5-1.el7.centos - ud  2017-09-18 
09:32:12 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum 
Transaction processed  2017-09-18 09:32:12 DEBUG otopi.context 
context._executeMethod:142 method exception  Traceback (most recent call last): 
   File "/tmp/ovirt-kRPMlHbiO5/pythonl line 132, in _executeMethod      
method['method']()    File "/tmp/ovirt-kRPMlHbiO5/otopi-p line 261, 
in _packages      self._miniyum.processTransacti    File 
"/tmp/ovirt-kRPMlHbiO5/pythonl line 1049, in processTransaction      
_('One or more elements within Yum transaction failed')  RuntimeError: 
One or more elements within Yum transaction failed  2017-09-18 09:32:12 ERROR 
otopi.context context._executeMethod:151 Failed to execute stage 'Package 
installation': One or more elements within Yum transaction failed  
2017-09-18 09:32:12 DEBUG otopi.transaction transaction.abort:119 aborting 
'Yum Transaction'  2017-09-18 09:32:12 INFO 
otopi.plugins.otopi.packagers. yumpackager.info:80 Yum Performing yum 
transaction rollback  2017-09-18 09:32:12 DEBUG otopi.plugins.otopi.packagers. 
yumpackager.verbose:76 Yum Downloading: centos-opstools-release/7/x86_ (0%)  
2017-09-18 09:32:12 DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 
Yum Downloading: centos-opstools-release/7/x86_ 300 k(84%)  2017-09-18 09:32:13 
DEBUG otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: 
centos-opstools-release/7/x86_ 355 k(100%)  2017-09-18 09:32:13 DEBUG 
otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: 
centos-opstools-release/7/x86_ (0%)  2017-09-18 09:32:13 DEBUG 
otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: 
centos-opstools-release/7/x86_ 50 k(100%)  2017-09-18 09:32:14 DEBUG 
otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: 
ovirt-4.1/7/filelists_db (0%)  2017-09-18 09:32:14 DEBUG 
otopi.plugins.otopi.packagers. yumpackager.verbose:76 Yum Downloading: 
ovirt-4.1/7/filelists_db 41 k(4%)  2

Re: [ovirt-users] ovirt upgrade => vms refusing to (re)boot

[Michal Skrivanek]

> On 31 Mar 2017, at 15:49, Nelson Lameiras  
> wrote:
> 
> Hello,
> 
> We had a rather unpleseant surprise while upgrading our production 
> datacenters to oVirt 4.0 => 4.1 (although I think this problem is not related 
> to oVirt 4.1). 
> Some critical VMs simply refused to reboot without any particular error 
> message other than "VM failed to boot"
> 
> After a stressfull 2h of investigation, it turns out that the problematic VMs 
> shared the same "exotic" condition. They were not rebooted since the latest 
> major upgrade 3.6 => 4.0 (I know, this is not a good practise and we 
> underestimated it's priority, we will change our reboot policies)

it’s indeed not a good practice. You can’t use the features (those related to 
hw) without updating the guest HW and that will only happen once you shut the 
VM down. If you can’t do that then just keep the old cluster level, that is 
fully supported.

> Their "custom compatilibity setting" was set to 3.6 !! When changing this 
> setting to "Empty", The VM booted normaly. Hard to find, easy to fix !! ;)
> 
> Neverthess, there is little to none information/documentation about the 
> usefullness of this setting, and I have a hard time understanding the 
> consequences of changing it manually.
> 
> Our oVirt datacenter (which has  engine 4.1.1, but some hosts on 4.0, so it's 
> still on 4.0 compatibility) hosts currently +- 200 Vms,
> - 10 with "custom compatilibity setting" set to 3.6 - which will not 
> (reb)boot in current state,
> - 30some with "custom compatilibity setting" set to 4.0 - which (re)boot 
> normally 
> - the rest with "custom compatilibity setting" set to "empty" - which 
> (re)boot normally 
> 
> So can a oVirt guru please answer the following questions :
> 
> - What does this setting do? which are the consequences of changing it 
> manually ?

it emulates the corresponding guest hardware and engine feature behavior.

> - Is it "normal" that a VM not reboooted since the 3.6 update does not boot 
> if a new major upgrade is done on hostig host ? (maybe a exotic bug worth 
> correcting ?)

no, it’s a bug https://bugzilla.redhat.com/show_bug.cgi?id=1436325 

will be fixed in 4.1.2

> - Which are the possible consequences of manually setting this setting to 
> "Empty" in all my VMs (running or stopped) ?

then it will use the cluster settings. that is the “normal” state

> - Which events will change this setting automatically ? (cluster major 
> version upgrade, first reboot after upgrade, ...) ?

cluster level upgrade while VM is running. Since the VM is running the changes 
to hardware cannot be applied and it is temporarily reconfigured to use the 
previous cluster level. On VM shutdown the settings are all updated and the 
field set to empty.
there was another bug (hopefully fixed) which kept the value there even on 
shutdown. Just edit and put “empty”, then it will start as a regular VM in its 
cluster.

> - Some of my VMs have custom_compatibility_version set to 4.0 (in REST API)  
> eventough they have been recently rebooted and "custom compatilibity setting" 
> is empty in GUI, who's this possible ?

was it done before the reboot? are there pending changes to be applied perhaps?

Thanks,
michal

> 
> cordialement, regards,
> 
> 
>  
> Nelson LAMEIRAS
> Ingénieur Systèmes et Réseaux / Systems and Networks engineer
> Tel: +33 5 32 09 09 70
> nelson.lamei...@lyra-network.com 
> www.lyra-network.com  | www.payzen.eu 
> 
>  
> 
>  
> 
>  
>  
> Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] ovirt upgrade => vms refusing to (re)boot

[Nelson Lameiras]

Hello, 

We had a rather unpleseant surprise while upgrading our production datacenters 
to oVirt 4.0 => 4.1 (although I think this problem is not related to oVirt 
4.1). 
Some critical VMs simply refused to reboot without any particular error message 
other than "VM failed to boot" 

After a stressfull 2h of investigation, it turns out that the problematic VMs 
shared the same "exotic" condition. They were not rebooted since the latest 
major upgrade 3.6 => 4.0 (I know, this is not a good practise and we 
underestimated it's priority, we will change our reboot policies) 
Their "custom compatilibity setting" was set to 3.6 !! When changing this 
setting to "Empty", The VM booted normaly. Hard to find, easy to fix !! ;) 

Neverthess, there is little to none information/documentation about the 
usefullness of this setting, and I have a hard time understanding the 
consequences of changing it manually. 

Our oVirt datacenter (which has engine 4.1.1, but some hosts on 4.0, so it's 
still on 4.0 compatibility) hosts currently +- 200 Vms, 
- 10 with "custom compatilibity setting" set to 3.6 - which will not (reb)boot 
in current state, 
- 30some with "custom compatilibity setting" set to 4.0 - which (re)boot 
normally 
- the rest with "custom compatilibity setting" set to "empty" - which (re)boot 
normally 

So can a oVirt guru please answer the following questions : 

- What does this setting do? which are the consequences of changing it manually 
? 
- Is it "normal" that a VM not reboooted since the 3.6 update does not boot if 
a new major upgrade is done on hostig host ? (maybe a exotic bug worth 
correcting ?) 
- Which are the possible consequences of manually setting this setting to 
"Empty" in all my VMs (running or stopped) ? 
- Which events will change this setting automatically ? (cluster major version 
upgrade, first reboot after upgrade, ...) ? 
- Some of my VMs have custom_compatibility_version set to 4.0 (in REST API) 
eventough they have been recently rebooted and "custom compatilibity setting" 
is empty in GUI, who's this possible ? 

cordialement, regards, 


Nelson LAMEIRAS 
Ingénieur Systèmes et Réseaux / Systems and Networks engineer 
Tel: +33 5 32 09 09 70 
nelson.lamei...@lyra-network.com 

www.lyra-network.com | www.payzen.eu 





Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt upgrade

[Yedidyah Bar David]

On Thu, Aug 11, 2016 at 5:02 PM, Gianluca Cecchi
 wrote:
>
> On Wed, Aug 10, 2016 at 12:38 PM, Yedidyah Bar David 
> wrote:
>>
>>
>> >
>> > Ok, thanks for the update and clarifications.
>> > From an operational point of view, what will change?
>> > RIght now, in 4.0, if I select Default cluster and try to edit it and
>> > upgrade its Compatibility Version to 4.0, it seems I don't get any
>> > message
>> > in the gui, or at least I don't see it; it's something similar to when
>> > you
>> > have sort of syntactical or incomplete error in your input) ...
>> > and in engine.log I see
>> > 2016-08-10 11:59:43,780 WARN
>> > [org.ovirt.engine.core.bll.storage.pool.UpdateStoragePoolCommand]
>> > (default
>> > task-11) [6f626a79] Validation of action 'UpdateStoragePool' failed for
>> > user
>> > admin@internal-authz. Reasons:
>> > VAR__TYPE__STORAGE__POOL,VAR__ACTION__UPDATE,$ClustersList
>> >
>> > Default,ERROR_CANNOT_UPDATE_STORAGE_POOL_COMPATIBILITY_VERSION_BIGGER_THAN_CLUSTERS
>> >
>> > Instead in 4.0.2 it should allow me to do it so that I should see all
>> > running VMs, inlcluded the hosted engine VM, marked with configuration
>> > change needed symbol?
>>
>> That's what I understand too.
>>
>> > In this case for engine VM would it be sufficient to run something like
>> > thsi
>> > to commit its modifications?
>> >
>> > hosted-engine --set-maintenance --mode=global
>> > shutdown engine VM from os console
>> > hosted-engine --set-maintenance --mode=none
>> > verify engine VM is automatically started and without the flag about
>> > configuration changes needed?
>>
>> Looks ok to me, didn't try this myself.
>>
>> Best,
>> --
>> Didi
>
>
> Hello,
> so I upgraded from 4.0 to 4.0.2 RC4 both engine and host.
> I successfully verified the cluster upgrade workflow; see here the dialogue:
> https://drive.google.com/file/d/0BwoPbcrMv8mvSVFFVzE5RTh5ZFU/view?usp=sharing
>
> Then the virtual machines pane appears like this:
> https://drive.google.com/file/d/0BwoPbcrMv8mvTXFnTDFVSllPaVk/view?usp=sharing
>
> Tried to start a previously powered off VM and it appears running without
> mark.
> Tried to shutdown and then powered on a VM with the configuration mark (c6
> VM) and after correct start it doesn't have it
>
> The only doubt is related to hosted engine VM... it doesn't show any mark
> ... does this mean that actually I don't need to shutdown and power on the
> engine VM itself or is it an error that no configuration message icon is
> shown aside of engine VM?

Not sure, adding Michal.
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt upgrade

[Gianluca Cecchi]

On Wed, Aug 10, 2016 at 12:38 PM, Yedidyah Bar David 
wrote:

>
> >
> > Ok, thanks for the update and clarifications.
> > From an operational point of view, what will change?
> > RIght now, in 4.0, if I select Default cluster and try to edit it and
> > upgrade its Compatibility Version to 4.0, it seems I don't get any
> message
> > in the gui, or at least I don't see it; it's something similar to when
> you
> > have sort of syntactical or incomplete error in your input) ...
> > and in engine.log I see
> > 2016-08-10 11:59:43,780 WARN
> > [org.ovirt.engine.core.bll.storage.pool.UpdateStoragePoolCommand]
> (default
> > task-11) [6f626a79] Validation of action 'UpdateStoragePool' failed for
> user
> > admin@internal-authz. Reasons:
> > VAR__TYPE__STORAGE__POOL,VAR__ACTION__UPDATE,$ClustersList
> > Default,ERROR_CANNOT_UPDATE_STORAGE_POOL_COMPATIBILITY_
> VERSION_BIGGER_THAN_CLUSTERS
> >
> > Instead in 4.0.2 it should allow me to do it so that I should see all
> > running VMs, inlcluded the hosted engine VM, marked with configuration
> > change needed symbol?
>
> That's what I understand too.
>
> > In this case for engine VM would it be sufficient to run something like
> thsi
> > to commit its modifications?
> >
> > hosted-engine --set-maintenance --mode=global
> > shutdown engine VM from os console
> > hosted-engine --set-maintenance --mode=none
> > verify engine VM is automatically started and without the flag about
> > configuration changes needed?
>
> Looks ok to me, didn't try this myself.
>
> Best,
> --
> Didi
>

Hello,
so I upgraded from 4.0 to 4.0.2 RC4 both engine and host.
I successfully verified the cluster upgrade workflow; see here the dialogue:
https://drive.google.com/file/d/0BwoPbcrMv8mvSVFFVzE5RTh5ZFU/view?usp=sharing

Then the virtual machines pane appears like this:
https://drive.google.com/file/d/0BwoPbcrMv8mvTXFnTDFVSllPaVk/view?usp=sharing

Tried to start a previously powered off VM and it appears running without
mark.
Tried to shutdown and then powered on a VM with the configuration mark (c6
VM) and after correct start it doesn't have it

The only doubt is related to hosted engine VM... it doesn't show any mark
... does this mean that actually I don't need to shutdown and power on the
engine VM itself or is it an error that no configuration message icon is
shown aside of engine VM?

Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt upgrade

[Yedidyah Bar David]

On Wed, Aug 10, 2016 at 1:10 PM, Gianluca Cecchi
 wrote:
> On Wed, Aug 10, 2016 at 11:52 AM, Yedidyah Bar David 
> wrote:
>>
>>
>> >
>> > Can you give an update on this?
>>
>> Should be fixed in 4.0.2:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1348907
>>
>> As a general note, if you see a bug on 4.0.z in MODIFIED or QA,
>> the fix is already in the nightly 4.0 repos, in case you feel like trying:
>>
>> http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/
>>
>> Best,
>> --
>> Didi
>
>
> Ok, thanks for the update and clarifications.
> From an operational point of view, what will change?
> RIght now, in 4.0, if I select Default cluster and try to edit it and
> upgrade its Compatibility Version to 4.0, it seems I don't get any message
> in the gui, or at least I don't see it; it's something similar to when you
> have sort of syntactical or incomplete error in your input) ...
> and in engine.log I see
> 2016-08-10 11:59:43,780 WARN
> [org.ovirt.engine.core.bll.storage.pool.UpdateStoragePoolCommand] (default
> task-11) [6f626a79] Validation of action 'UpdateStoragePool' failed for user
> admin@internal-authz. Reasons:
> VAR__TYPE__STORAGE__POOL,VAR__ACTION__UPDATE,$ClustersList
> Default,ERROR_CANNOT_UPDATE_STORAGE_POOL_COMPATIBILITY_VERSION_BIGGER_THAN_CLUSTERS
>
> Instead in 4.0.2 it should allow me to do it so that I should see all
> running VMs, inlcluded the hosted engine VM, marked with configuration
> change needed symbol?

That's what I understand too.

> In this case for engine VM would it be sufficient to run something like thsi
> to commit its modifications?
>
> hosted-engine --set-maintenance --mode=global
> shutdown engine VM from os console
> hosted-engine --set-maintenance --mode=none
> verify engine VM is automatically started and without the flag about
> configuration changes needed?

Looks ok to me, didn't try this myself.

Best,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt upgrade

[Gianluca Cecchi]

On Wed, Aug 10, 2016 at 11:52 AM, Yedidyah Bar David 
wrote:

>
> >
> > Can you give an update on this?
>
> Should be fixed in 4.0.2:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1348907
>
> As a general note, if you see a bug on 4.0.z in MODIFIED or QA,
> the fix is already in the nightly 4.0 repos, in case you feel like trying:
>
> http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/
>
> Best,
> --
> Didi
>

Ok, thanks for the update and clarifications.
>From an operational point of view, what will change?
RIght now, in 4.0, if I select Default cluster and try to edit it and
upgrade its Compatibility Version to 4.0, it seems I don't get any message
in the gui, or at least I don't see it; it's something similar to when you
have sort of syntactical or incomplete error in your input) ...
and in engine.log I see
2016-08-10 11:59:43,780 WARN
 [org.ovirt.engine.core.bll.storage.pool.UpdateStoragePoolCommand] (default
task-11) [6f626a79] Validation of action 'UpdateStoragePool' failed for
user admin@internal-authz. Reasons:
VAR__TYPE__STORAGE__POOL,VAR__ACTION__UPDATE,$ClustersList
Default,ERROR_CANNOT_UPDATE_STORAGE_POOL_COMPATIBILITY_VERSION_BIGGER_THAN_CLUSTERS

Instead in 4.0.2 it should allow me to do it so that I should see all
running VMs, inlcluded the hosted engine VM, marked with configuration
change needed symbol?
In this case for engine VM would it be sufficient to run something like
thsi to commit its modifications?

hosted-engine --set-maintenance --mode=global
shutdown engine VM from os console
hosted-engine --set-maintenance --mode=none
verify engine VM is automatically started and without the flag about
configuration changes needed?

Thanks,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt upgrade

[Yedidyah Bar David]

On Wed, Aug 10, 2016 at 12:46 PM, Gianluca Cecchi
 wrote:
> On Wed, Aug 10, 2016 at 9:42 AM, Simone Tiraboschi 
> wrote:
>>
>> On Wed, Aug 10, 2016 at 7:53 AM, Yedidyah Bar David 
>> wrote:
>> > On Tue, Aug 9, 2016 at 8:39 PM, Budur Nagaraju 
>> > wrote:
>> >> HI
>> >>
>> >> How to upgrade oVirt3.5 to 4 ? am using centos6.7.
>> >
>> > First upgrade or reinstall your hosts with el7.
>> > oVirt 3.6+ does not provide packages for el6. el6 hosts will
>> > still work, but easiest to upgrade to el7 in 3.5.
>> >
>> > If you are using hosted-engine, you can follow [1].
>> >
>> > Then upgrade to 3.6 using regular docs [2].
>> >
>> > In 4.0, the engine is also el7 only. To upgrade, use engine-backup
>> > to backup, then reinstall the machine with el7, then restore. I do
>> > not think we have a special page for this, but you can follow the
>> > doc text of [3], which is also copied in the 4.0 release notes [4].
>> > Please review [5] for more information about engine backup and restore.
>> > If you using hosted-engine, you can use the new upgrade tool to upgrade
>> > the engine vm using the engine appliance. Not sure that's properly
>> > documented either, see also [6]. Also note that this bug is for 4.0.2,
>> > to be released soon.
>>
>> We have this:
>>
>> https://www.ovirt.org/develop/release-management/features/hosted-engine-migration-to-4-0/
>>
>>
>
> But I have not yet understood, based on this thread in June and the related
> bugzillas:
> http://lists.ovirt.org/pipermail/users/2016-June/040587.html
>
> what is the current situation in 4.0.1 and then 4.0.2 for the problem of
> upgrading cluster level of the cluster where engine vm is running, in case
> of Self Hosted Engine environments.
> And in case not feasible yet, if there is any supported workaround doing
> modifications at engine database level.
>
> Can you give an update on this?

Should be fixed in 4.0.2:

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

As a general note, if you see a bug on 4.0.z in MODIFIED or QA,
the fix is already in the nightly 4.0 repos, in case you feel like trying:

http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/

Best,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt upgrade

[Gianluca Cecchi]

On Wed, Aug 10, 2016 at 9:42 AM, Simone Tiraboschi 
wrote:

> On Wed, Aug 10, 2016 at 7:53 AM, Yedidyah Bar David 
> wrote:
> > On Tue, Aug 9, 2016 at 8:39 PM, Budur Nagaraju 
> wrote:
> >> HI
> >>
> >> How to upgrade oVirt3.5 to 4 ? am using centos6.7.
> >
> > First upgrade or reinstall your hosts with el7.
> > oVirt 3.6+ does not provide packages for el6. el6 hosts will
> > still work, but easiest to upgrade to el7 in 3.5.
> >
> > If you are using hosted-engine, you can follow [1].
> >
> > Then upgrade to 3.6 using regular docs [2].
> >
> > In 4.0, the engine is also el7 only. To upgrade, use engine-backup
> > to backup, then reinstall the machine with el7, then restore. I do
> > not think we have a special page for this, but you can follow the
> > doc text of [3], which is also copied in the 4.0 release notes [4].
> > Please review [5] for more information about engine backup and restore.
> > If you using hosted-engine, you can use the new upgrade tool to upgrade
> > the engine vm using the engine appliance. Not sure that's properly
> > documented either, see also [6]. Also note that this bug is for 4.0.2,
> > to be released soon.
>
> We have this:
> https://www.ovirt.org/develop/release-management/features/
> hosted-engine-migration-to-4-0/
>
>
>
But I have not yet understood, based on this thread in June and the related
bugzillas:
http://lists.ovirt.org/pipermail/users/2016-June/040587.html

what is the current situation in 4.0.1 and then 4.0.2 for the problem of
upgrading cluster level of the cluster where engine vm is running, in case
of Self Hosted Engine environments.
And in case not feasible yet, if there is any supported workaround doing
modifications at engine database level.

Can you give an update on this?
Thanks,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt upgrade

[Simone Tiraboschi]

On Wed, Aug 10, 2016 at 7:53 AM, Yedidyah Bar David  wrote:
> On Tue, Aug 9, 2016 at 8:39 PM, Budur Nagaraju  wrote:
>> HI
>>
>> How to upgrade oVirt3.5 to 4 ? am using centos6.7.
>
> First upgrade or reinstall your hosts with el7.
> oVirt 3.6+ does not provide packages for el6. el6 hosts will
> still work, but easiest to upgrade to el7 in 3.5.
>
> If you are using hosted-engine, you can follow [1].
>
> Then upgrade to 3.6 using regular docs [2].
>
> In 4.0, the engine is also el7 only. To upgrade, use engine-backup
> to backup, then reinstall the machine with el7, then restore. I do
> not think we have a special page for this, but you can follow the
> doc text of [3], which is also copied in the 4.0 release notes [4].
> Please review [5] for more information about engine backup and restore.
> If you using hosted-engine, you can use the new upgrade tool to upgrade
> the engine vm using the engine appliance. Not sure that's properly
> documented either, see also [6]. Also note that this bug is for 4.0.2,
> to be released soon.

We have this:
https://www.ovirt.org/develop/release-management/features/hosted-engine-migration-to-4-0/

>
> As always, if at all possible, better try first on a test system,
> especially if it's in production, and backup everything beforehand,
> including your VMs etc.
>
> Best regards,
>
> [1] https://www.ovirt.org/documentation/how-to/hosted-engine-host-OS-upgrade/
> [2] http://www.ovirt.org/develop/release-management/releases/3.6/
> [3] https://bugzilla.redhat.com/show_bug.cgi?id=1318580
> [4] https://www.ovirt.org/release/4.0.0/
> [5] 
> http://www.ovirt.org/develop/release-management/features/engine/engine-backup/
> [6] https://bugzilla.redhat.com/show_bug.cgi?id=1319457
> --
> Didi
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt upgrade

[Yedidyah Bar David]

On Tue, Aug 9, 2016 at 8:39 PM, Budur Nagaraju  wrote:
> HI
>
> How to upgrade oVirt3.5 to 4 ? am using centos6.7.

First upgrade or reinstall your hosts with el7.
oVirt 3.6+ does not provide packages for el6. el6 hosts will
still work, but easiest to upgrade to el7 in 3.5.

If you are using hosted-engine, you can follow [1].

Then upgrade to 3.6 using regular docs [2].

In 4.0, the engine is also el7 only. To upgrade, use engine-backup
to backup, then reinstall the machine with el7, then restore. I do
not think we have a special page for this, but you can follow the
doc text of [3], which is also copied in the 4.0 release notes [4].
Please review [5] for more information about engine backup and restore.
If you using hosted-engine, you can use the new upgrade tool to upgrade
the engine vm using the engine appliance. Not sure that's properly
documented either, see also [6]. Also note that this bug is for 4.0.2,
to be released soon.

As always, if at all possible, better try first on a test system,
especially if it's in production, and backup everything beforehand,
including your VMs etc.

Best regards,

[1] https://www.ovirt.org/documentation/how-to/hosted-engine-host-OS-upgrade/
[2] http://www.ovirt.org/develop/release-management/releases/3.6/
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1318580
[4] https://www.ovirt.org/release/4.0.0/
[5] 
http://www.ovirt.org/develop/release-management/features/engine/engine-backup/
[6] https://bugzilla.redhat.com/show_bug.cgi?id=1319457
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] oVirt upgrade

[Budur Nagaraju]

HI

How to upgrade oVirt3.5 to 4 ? am using centos6.7.

Thanks,
Nagaraju
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users