Re: [ovirt-users] improvement for web ui during the create template stage.

[Eyal Shenitzky]

Thanks Nicolas

On Sun, Mar 18, 2018 at 11:44 PM, Nicolas Vaye  wrote:

> Yes, bug submitted
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1557803
>
>
>  Message initial 
>
> Date: Wed, 14 Mar 2018 11:25:56 +0200
> Objet: Re: [ovirt-users] improvement for web ui during the create template
> stage.
> À: Nicolas Vaye  3cnicolas.v...@province-sud.nc%3e>>
> De: Eyal Shenitzky  al%20shenitzky%20%3ceshen...@redhat.com%3e>>
> Hi Nicolas,
>
> Please submit a bug using - https://bugzilla.redhat.com/
> enter_bug.cgi?product=ovirt-engine.
>
> Thanks,
>
> On Wed, Mar 14, 2018 at 6:04 AM, Nicolas Vaye <
> nicolas.v...@province-sud.nc> wrote:
> Hi,
> I 'have 2 ovirt node with HE in version 4.2.1.7-1.
>
> If i make a template from a VM's snapshot in the web ui, there is a form
> ui to enter several parameter
> [cid:1521000255.509.1.camel@province-sud.nc 3a1521000255.509.1.ca...@province-sud.nc>]
>
> if the name of the template is missing and if we clic on the OK button,
> there is an highlighting red border on the name to indicate the problem.
> if i enter a long name for the template and if we clic on the OK button,
> nothing happend, and there is no highlight or error message to indicate
> there is a problem with the long name.
>
> Could you improve that ?
>
> Thanks,
>
> Regards,
>
> Nicolas VAYE
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
>
> --
> Regards,
> Eyal Shenitzky
>



-- 
Regards,
Eyal Shenitzky
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Postgresql read only user difficulties

[Maton, Brett]

No worries, glad you got there in the end

On 19 March 2018 at 04:16, Vincent Royer  wrote:

> I just did it again with another user and this time it seemed to work.
>
> Thanks for your help.
>
> *Vincent Royer*
> *778-825-1057*
>
>
> 
> *SUSTAINABLE MOBILE ENERGY SOLUTIONS*
>
>
>
>
> On Sun, Mar 18, 2018 at 8:50 PM, Maton, Brett 
> wrote:
>
>> Ok that may well  be the case :)
>>
>> If generated the password as per the instructions with
>>
>> ENCRYPTED PASSWORD
>>
>> Postgres is expecting the password to be pre-encrypted.
>>
>> If you connect to postgres as postgres (psql)
>>
>> Try
>>
>> ALTER ROLE grafana WITH PASSWORD 'clear txt password';
>>
>>
>>
>> On 18 March 2018 at 18:49, Vincent Royer  wrote:
>>
>>> well this is frustrating.  I added the read only user, but still can't
>>> connect.
>>>
>>> pq: password authentication failed for user "grafana"
>>>
>>>
>>> *Vincent Royer*
>>> *778-825-1057 <(778)%20825-1057>*
>>>
>>>
>>> 
>>> *SUSTAINABLE MOBILE ENERGY SOLUTIONS*
>>>
>>>
>>>
>>>
>>> On Sat, Mar 17, 2018 at 11:43 AM, Maton, Brett >> > wrote:
>>>
 Yeah if postgres won't start you've probably got a typo in pg_hba.conf

 On 17 March 2018 at 18:11, Vincent Royer  wrote:

> I think I see the issue.  Extra space after the IP address in
> pg_hba.conf
>
> I'll try again later.
>
> Thanks for your help!
>
>
>
>
> On Sat, Mar 17, 2018 at 10:44 AM, Vincent Royer  > wrote:
>
>> hmmm.  not a great result...
>>
>>  rh-postgresql95-postgresql.service:...1
>> Mar 17 10:36:32 ovirt-engine systemd[1]: Failed to start PostgreSQL
>> database
>> Mar 17 10:36:32 ovirt-engine systemd[1]: Unit
>> rh-postgresql95-postgresql.ser
>> Mar 17 10:36:32 ovirt-engine systemd[1]:
>> rh-postgresql95-postgresql.service 
>>
>> and can no longer login to ovirt-engine gui:
>>
>> server_error: Connection refused. Check that the hostname and port
>> are correct and that the postmaster is accepting TCP/IP connections.
>>
>> tried to restart ovirt-engine and it won't come up - internal server
>> error.
>>
>>
>>
>> *Vincent Royer*
>> *778-825-1057 <(778)%20825-1057>*
>>
>>
>> 
>> *SUSTAINABLE MOBILE ENERGY SOLUTIONS*
>>
>>
>>
>>
>> On Sat, Mar 17, 2018 at 4:34 AM, Maton, Brett <
>> mat...@ltresources.co.uk> wrote:
>>
>>> You could always try reloading the configuration, pretty sure pg_hba
>>> gets reloaded these days:
>>>
>>> su - postgres
>>> scl enable rh-postgresql95 bash
>>> pg_ctl reload -D /var/opt/rh/rh-postgresql95/lib/pgsql/data
>>>
>>> or as root
>>>
>>> systemctl restart rh-postgresql95-postgresql.service
>>>
>>>
>>> On 17 March 2018 at 11:20, Vincent Royer 
>>> wrote:
>>>
 ok thanks, I did see it there but assumed that was a temp file.  I
 updated it according to the instructions, but I still get the same 
 error.

 # TYPE  DATABASEUSERADDRESS
  METHOD

 # "local" is for Unix domain socket connections only
 local   all all peer
 hostovirt_engine_history ovirt_engine_history 0.0.0.0/0
md5
 hostovirt_engine_history ovirt_engine_history ::0/0
md5
 hostovirt_engine_history grafana 172.16.30.10 /0
  md5
 hostovirt_engine_history grafana ::0/0   md5
 hostengine  engine  0.0.0.0/0   md5
 hostengine  engine  ::0/0   md5


 did a systemctl restart postgresql.service and I get "Unit not
 found".   So I did systemctl restart ovirt-engine.service...

 and the error I get when accessing from 172.16.30.10 is:

 pq: no pg_hba.conf entry for host "172.16.30.10", user "grafana",
 database "ovirt_engine_history", SSL off




 *Vincent Royer*
 *778-825-1057 <(778)%20825-1057>*


 
 *SUSTAINABLE MOBILE ENERGY SOLUTIONS*




 On Sat, Mar 17, 2018 at 3:42 AM, Maton, Brett <
 mat...@ltresources.co.uk> wrote:

> Hi Vincent,
>
>   oVirt isn't using the stock PostgreSQL but an SCL version
>   You should find pg_hba.conf here /var/opt/rh/rh-postgresql95/li
> b/pgsql/data/pg_hba.conf
>
> Hope this helps.
>
> On 17 March 

Re: [ovirt-users] Postgresql read only user difficulties

[Maton, Brett]

Ok that may well  be the case :)

If generated the password as per the instructions with

ENCRYPTED PASSWORD

Postgres is expecting the password to be pre-encrypted.

If you connect to postgres as postgres (psql)

Try

ALTER ROLE grafana WITH PASSWORD 'clear txt password';


On 18 March 2018 at 18:49, Vincent Royer  wrote:

> well this is frustrating.  I added the read only user, but still can't
> connect.
>
> pq: password authentication failed for user "grafana"
>
>
> *Vincent Royer*
> *778-825-1057*
>
>
> 
> *SUSTAINABLE MOBILE ENERGY SOLUTIONS*
>
>
>
>
> On Sat, Mar 17, 2018 at 11:43 AM, Maton, Brett 
> wrote:
>
>> Yeah if postgres won't start you've probably got a typo in pg_hba.conf
>>
>> On 17 March 2018 at 18:11, Vincent Royer  wrote:
>>
>>> I think I see the issue.  Extra space after the IP address in pg_hba.conf
>>>
>>> I'll try again later.
>>>
>>> Thanks for your help!
>>>
>>>
>>>
>>>
>>> On Sat, Mar 17, 2018 at 10:44 AM, Vincent Royer 
>>> wrote:
>>>
 hmmm.  not a great result...

  rh-postgresql95-postgresql.service:...1
 Mar 17 10:36:32 ovirt-engine systemd[1]: Failed to start PostgreSQL
 database
 Mar 17 10:36:32 ovirt-engine systemd[1]: Unit
 rh-postgresql95-postgresql.ser
 Mar 17 10:36:32 ovirt-engine systemd[1]: rh-postgresql95-postgresql.service
 

 and can no longer login to ovirt-engine gui:

 server_error: Connection refused. Check that the hostname and port are
 correct and that the postmaster is accepting TCP/IP connections.

 tried to restart ovirt-engine and it won't come up - internal server
 error.



 *Vincent Royer*
 *778-825-1057 <(778)%20825-1057>*


 
 *SUSTAINABLE MOBILE ENERGY SOLUTIONS*




 On Sat, Mar 17, 2018 at 4:34 AM, Maton, Brett  wrote:

> You could always try reloading the configuration, pretty sure pg_hba
> gets reloaded these days:
>
> su - postgres
> scl enable rh-postgresql95 bash
> pg_ctl reload -D /var/opt/rh/rh-postgresql95/lib/pgsql/data
>
> or as root
>
> systemctl restart rh-postgresql95-postgresql.service
>
>
> On 17 March 2018 at 11:20, Vincent Royer 
> wrote:
>
>> ok thanks, I did see it there but assumed that was a temp file.  I
>> updated it according to the instructions, but I still get the same error.
>>
>> # TYPE  DATABASEUSERADDRESS METHOD
>>
>> # "local" is for Unix domain socket connections only
>> local   all all peer
>> hostovirt_engine_history ovirt_engine_history 0.0.0.0/0
>>  md5
>> hostovirt_engine_history ovirt_engine_history ::0/0
>>  md5
>> hostovirt_engine_history grafana 172.16.30.10 /0   md5
>> hostovirt_engine_history grafana ::0/0   md5
>> hostengine  engine  0.0.0.0/0   md5
>> hostengine  engine  ::0/0   md5
>>
>>
>> did a systemctl restart postgresql.service and I get "Unit not
>> found".   So I did systemctl restart ovirt-engine.service...
>>
>> and the error I get when accessing from 172.16.30.10 is:
>>
>> pq: no pg_hba.conf entry for host "172.16.30.10", user "grafana",
>> database "ovirt_engine_history", SSL off
>>
>>
>>
>>
>> *Vincent Royer*
>> *778-825-1057 <(778)%20825-1057>*
>>
>>
>> 
>> *SUSTAINABLE MOBILE ENERGY SOLUTIONS*
>>
>>
>>
>>
>> On Sat, Mar 17, 2018 at 3:42 AM, Maton, Brett <
>> mat...@ltresources.co.uk> wrote:
>>
>>> Hi Vincent,
>>>
>>>   oVirt isn't using the stock PostgreSQL but an SCL version
>>>   You should find pg_hba.conf here /var/opt/rh/rh-postgresql95/li
>>> b/pgsql/data/pg_hba.conf
>>>
>>> Hope this helps.
>>>
>>> On 17 March 2018 at 09:50, Vincent Royer 
>>> wrote:
>>>
 Hi,

 I followed these instructions on Ovirt self hosted engine 4.2.1:

 https://www.ovirt.org/documentation/data-warehouse/Allowing_
 Read_Only_Access_to_the_History_Database/

 when connecting to the db from an external host I receive this
 error:

 pq: no pg_hba.conf entry for host "", user "", database
 "ovirt_engine_history", SSL off

 I looked in the normal place for pg_hba.conf but the file does not
 exist, /data does not exist in /var/lib/pgsql

 Do i need to run engine-setup again to configure this?

 Thank you!

Re: [ovirt-users] Query about running ovirt-4.2.1 engine support 3.x nodes ?

[Joseph Kelly]

Sorry to ask again, But I can see from the link below the that nodes and 
engines should work between minor number

upgrades. But is ovirt 4.2.x backward compatible with, say, 3.6 nodes. Does 
anyone know ? Is this documented  anywhere ?


[ovirt-users] compatibility relationship between datacenter, ovirt and cluster

https://www.mail-archive.com/users@ovirt.org/msg17092.html

Thanks,
Joe.


From: Joseph Kelly
Sent: Wednesday, March 14, 2018 5:32 PM
To: users@ovirt.org
Subject: Query about running ovirt-4.2.1 engine support 3.x nodes ?


Hello All,


I have two hopefully easy questions regarding an ovirt-4.2.1 engine support and 
3.x nodes ?


1) Does an ovirt-4.2.x engine support 3.x nodes ? As This page states:


"The cluster compatibility is set according to the version of the least capable 
host operating system in the cluster."


https://www.ovirt.org/documentation/upgrade-guide/chap-Post-Upgrade_Tasks/


Which seems to indicate that you can run say a 4.2.1 engine with lower version 
nodes, but is that correct ?


2) And can you just upgrade the nodes directly from 3.x to 4.2.x as per these 
steps ?


1. Move the node to maintenance
2. Add 4.2.x repos
3. yum update
4. reboot
5. Activate (exit maintenance)


I've looked in the release notes but wasn't able to find much detail on 
ovirt-nodes upgrades.


Thanks,

Joe.


--
J. Kelly
Infrastructure Engineer
TradingScreen
www.tradingscreen.com

Follow TradingScreen on Twitter, 
Facebook, or our 
blog, Trading Smarter

This message is intended only for the recipient(s) named above and may contain 
confidential information. If you are not an intended recipient, you should not 
review, distribute or copy this message. Please notify the sender immediately 
by e-mail if you have received this message in error and delete it from your 
system.




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

Re: [ovirt-users] VDSM SSL validity

[Punaatua PAINT-KOUI]

Up

2018-02-17 2:57 GMT-10:00 Punaatua PAINT-KOUI :

> Any idea someone ?
>
> Le 14 févr. 2018 23:19, "Punaatua PAINT-KOUI"  a
> écrit :
>
>> Hi,
>>
>> I setup an hyperconverged solution with 3 nodes, hosted engine on
>> glusterfs.
>> We run this setup in a PCI-DSS environment. According to PCI-DSS
>> requirements, we are required to reduce the validity of any certificate
>> under 39 months.
>>
>> I saw in this link https://www.ovirt.org/dev
>> elop/release-management/features/infra/pki/ that i can use the option
>> VdsCertificateValidityInYears at engine-config.
>>
>> I'm running ovirt engine 4.2.1 and i checked when i was on 4.2 how to
>> edit the option with engine-config --all and engine-config --list but the
>> option is not listed
>>
>> Am i missing something ?
>>
>> I thing i can regenerate a VDSM certificate with openssl and the CA conf
>> in /etc/pki/ovirt-engine on the hosted-engine but i would rather modifiy
>> the option for future host that I will add.
>>
>> --
>> -
>> PAINT-KOUI Punaatua
>>
>


-- 
-
PAINT-KOUI Punaatua
Licence Pro Réseaux et Télecom IAR
Université du Sud Toulon Var
La Garde France
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Using VDSM to edit management interface

[Kirin van der Veer]

Hi Peter,
Thanks again for trying to help out on this one.
Unfortunately this sent me right back to where I started.
When you grep for DNS entries the only matching file is
/etc/sysconfig/network-scripts/ifcfg-ovirtmgmt
As per my previous email this file is also generated (by VDSM this time)
and I don't see how to update the VDSM database so that it generates the
file with different entries.
It's turtles all the way down :)

Kirin.

On Fri, Mar 16, 2018 at 5:12 PM, Peter Hudec  wrote:

> Remove any settings about dns from the network manager adn the
> /etc/resolv.conf won't be auto generated.
>
> https://ma.ttias.be/centos-7-networkmanager-keeps-
> overwriting-etcresolv-conf/
>
> Peter
>
> On 16/03/2018 02:15, Kirin van der Veer wrote:
> > Ďakujem Peter, but this doesn't seem to work in my case.
> > /etc/resolv.conf is regenerated by Network Manager after a reboot
> > and my domain settings are lost. Your comments regarding the
> > reliance on DNS make sense for most installations, but in my case
> > oVirt is a secondary service that I would not expect to run unless
> > our core infrastructure is working correctly. I'm hesitant to edit
> > /etc/hosts directly, since that can lead to confusion when the
> > underlying IP addresses change. For now I will hardcode the IPs of
> > my servers. It's frustrating (and surprising) that there is not an
> > easy way to do this.
> >
> > Kirin.
> >
> > On Thu, Mar 15, 2018 at 5:17 PM, Peter Hudec  > > wrote:
> >
> > Hi Kirin,
> >
> > I suggest to do it old way and edit the /etc/resolv.conf manually.
> >
> > And one advice. Do not relay on the DNS on infrastructure servers.
> > Use /etc/hosts. If he DNS will not be accessible, you will have
> > problem to put it infrastructure up/working. As side effect the
> > hosts allow you to use short names to access servers.
> >
> > If you are ansible positive, you could use
> >
> > hudecof.resolv  https://galaxy.ansible.com/hudecof/resolv/
> >  hudecof.hosts
> > https://galaxy.ansible.com/hudecof/hosts/
> > 
> >
> >
> > Peter
> >
> > On 15/03/2018 06:03, Kirin van der Veer wrote:
> >> Hi oVirt people, I have setup a new cluster consisting of many
> >> oVirt Nodes with a single dedicated oVirt Engine machine. For
> >> the most part things are working, however despite entering the
> >> DNS search domain during install on the Nodes the management
> >> interface is not aware of my search domain and it has not been
> >> added to /etc/resolv.conf (perhaps that is unnecessary?). I
> >> eventually worked out that the DNS search domain should be
> >> included in /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt
> >> However as per the header/warning, that file is generated by
> >> VDSM. I assumed that I should be able to edit the search domain
> >> with vdsClient, but when I run "vdsClient -m" I don't see any
> >> options related to network config. I found the following page on
> >> DNS config:
> >>
> > https://www.ovirt.org/develop/release-management/features/network/
> allowExplicitDnsConfiguration/
> >
> >
>  allowExplicitDnsConfiguration/>
> >>
> >>
> > But it does not seem to offer a way of specifying the DNS search
> > domain
> >> (other than perhaps directly editing /etc/resolv.conf - which is
> >> generated/managed by Network Manager). nmcli reports that all of
> >> my interfaces (including ovirtmgmt) are "unmanaged". Indeed when
> >> I attempt to run nmtui there is nothing listed to configure.
> >> This should be really simple! I just want to add my local search
> >> domain so I can use the short name for my NFS server. I'd
> >> appreciate any advice.
> >>
> >> Thanks in advance, Kirin.
> >>
> >>
> >> .
> >>
> >> *IMPORTANT NOTE. *If you are NOT AN AUTHORISED RECIPIENT of this
> >> e-mail, please contact Planet Innovation Pty Ltd by return
> >> e-mail or by telephone on +613 9945 7510
> >> .  In
> > this case, you should not
> >> read, print, re-transmit, store or act in reliance on this
> >> e-mail or any attachments, and should destroy all copies of them.
> >> This e-mail and any attachments are confidential and may contain
> >> legally privileged information and/or copyright material of
> >> Planet Innovation Pty Ltd or third parties.  You should only
> >> re-transmit, distribute or commercialise the material if you are
> >> authorised to do so.  Although we use virus scanning software, we
> >> deny all liability for viruses or alike in any message or
> >> attachment. This notice should not be removed.
> >>
> >> **
> >>
> >>
> >> ___ Users mailing
> >> list Users@ovirt.org 
> > http://lists.ovirt.org/mailman/listinfo/users
> > 
> >>
> >
> >
> > -- *Peter Hudec* Infraštruktúrny 

Re: [ovirt-users] improvement for web ui during the create template stage.

[Nicolas Vaye]

 Message initial 

Date: Thu, 15 Mar 2018 08:38:57 -0400
Objet: Re: [ovirt-users] improvement for web ui during the create template 
stage.
Cc: users@ovirt.org 
>
À: Nicolas Vaye 
>
De: Alexander Wels 
>

On Wednesday, March 14, 2018 5:19:55 PM EDT Nicolas Vaye wrote:


Hi,

I thought it was the problem.
I did a test again and i have recorded the test (in attachment).
What is the problem ?

Regards,

Nicolas VAYE




Interesting, as that name is not long enough to trigger the name length
validation. You have 64 characters total for the name. I just tried your
scenario on the latest master branch, and it worked as expected, it created
the template from the snapshot without issues with that exact same name.

I don't see any recent changes to the frontend code for that dialog either. If
you look in the engine.log does it say anything? I can only assume some
validation is failing, and that validation message is not properly propagated
to the frontend, but it should show something in the backend log regardless.



 Message initial 

Date: Wed, 14 Mar 2018 08:36:48 -0400
Objet: Re: [ovirt-users] improvement for web ui during the create template
stage.


 À: users@ovirt.org, Nicolas 
Vaye


> De: Alexander Wels
>
On Wednesday, March 14, 2018 12:04:18 AM EDT Nicolas Vaye wrote:


Hi,
I 'have 2 ovirt node with HE in version 4.2.1.7-1.

If i make a template from a VM's snapshot in the web ui, there is a form ui
to enter several parameter


 
[cid:1521000255.509.1.camel@province-sud.nc]


bug submitted

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






if the name of the template is missing and if we clic on the OK button,
there is an highlighting red border on the name to indicate the problem.
if i enter a long name for the template and if we clic on the OK button,
nothing happend, and there is no highlight or error message to indicate
there is a problem with the long name.
Could you improve that ?

Thanks,

Regards,

Nicolas VAYE




It appears to me it already does that, this a screenshot of me putting in a
long template name, and it is highlighted right and if I hover I see a
tooltip explaining I can't have more than 64 characters.








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

[ovirt-users] Workflow after restoring engine from backup

[Sven Achtelik]

Hi All,

I had issue with the storage that hosted my engine vm. The disk got corrupted 
and I needed to restore the engine from a backup. That worked as expected, I 
just didn't start the engine yet. I know that after the backup was taken some 
machines where migrated around before the engine disks failed. My question is 
what will happen once I start the engine service which has the restored backup 
on it ? Will it query the hosts for the running VMs or will it assume that the 
VMs are still on the hosts as they resided at the point of backup ? Would I 
need to change the DB manual to let the engine know where VMs are up at this 
point ? What will happen to HA VMs ? I feel that it might try to start them a 
second time.  My biggest issue is that I can't get a service Windows to 
shutdown all VMs and then lat them restart by the engine.

Is there a known workflow for that ?

Thank you,
Sven
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] #2 Failed to run VM

[Andrei Verovski]

On 03/18/2018 09:34 PM, maoz zadok wrote:
> Thank you Arik you are right, my version is 4.2.0.2, how can I upgrade?

Sorry, didn't notice this problem solved only in pre-release 4.2.2
Then this:

1) upgrade engine as described here
https://www.ovirt.org/release/4.2.2/

2) login into ovirt engine, stop all VMs, choose host -> maintenance,
then upgrade node software.

>
> On Sun, Mar 18, 2018 at 4:11 PM, Arik Hadas  > wrote:
>
>
>
> On Sun, Mar 18, 2018 at 3:43 PM, maoz zadok  > wrote:
>
> Hello All,
> I'm receiving this message every time that I try to start VM,
> any idea?
>
>
> Seems you enounter [1] that is solved in 4.2.2.
> I assume you're using 4.2.1, right? By just looking at the code,
> it seems that restarting the engine could be a possible workaround
> for this.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1532884
> 
>  
>
>
>
>
> 2018-03-18 09:39:51,479-04 ERROR
> [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
> (EE-ManagedThreadFactory-engineScheduled-Thread-11) [] Failed
> during monitoring vm: 2445a47e-b102-11e6-ad11-1866da511add ,
> error is: {}: java.lang.NullPointerException
>
> 2018-03-18 09:39:51,480-04 ERROR
> [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
> (EE-ManagedThreadFactory-engineScheduled-Thread-11) []
> Exception:: java.lang.NullPointerException
>
> 2018-03-18 09:39:57,802-04 INFO 
> [org.ovirt.engine.core.bll.RunVmCommand] (default task-79)
> [b3b98e2c-6176-413d-9d75-315626918150] Lock Acquired to object
> 
> 'EngineLock:{exclusiveLocks='[fccee2da-92a3-4187-8aad-d6c1f9d5a3fb=VM]',
> sharedLocks=''}'
> 2018-03-18 09:39:57,822-04 INFO 
> [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand]
> (default task-79) [b3b98e2c-6176-413d-9d75-315626918150]
> START, IsVmDuringInitiatingVDSCommand(
> 
> IsVmDuringInitiatingVDSCommandParameters:{vmId='fccee2da-92a3-4187-8aad-d6c1f9d5a3fb'}),
> log id: 2217c887
> 2018-03-18 09:39:57,822-04 INFO 
> [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand]
> (default task-79) [b3b98e2c-6176-413d-9d75-315626918150]
> FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id:
> 2217c887
> 2018-03-18 09:39:57,927-04 INFO 
> [org.ovirt.engine.core.bll.RunVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Running command:
> RunVmCommand internal: false. Entities affected :  ID:
> fccee2da-92a3-4187-8aad-d6c1f9d5a3fb Type: VMAction group
> RUN_VM with role type USER
> 2018-03-18 09:39:57,944-04 INFO 
> 
> [org.ovirt.engine.core.bll.scheduling.policyunits.PreferredHostsWeightPolicyUnit]
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Penalizing host 'kvm5'
> because it is not preferred.
> 2018-03-18 09:39:57,944-04 INFO 
> 
> [org.ovirt.engine.core.bll.scheduling.policyunits.PreferredHostsWeightPolicyUnit]
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Penalizing host 'kvm6'
> because it is not preferred.
> 2018-03-18 09:39:57,944-04 INFO 
> 
> [org.ovirt.engine.core.bll.scheduling.policyunits.PreferredHostsWeightPolicyUnit]
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Penalizing host 'kvm7'
> because it is not preferred.
> 2018-03-18 09:39:57,945-04 WARN 
> [org.ovirt.engine.core.bll.scheduling.pending.PendingResourceManager]
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending
> resource
> org.ovirt.engine.core.bll.scheduling.pending.PendingCpuCores@1d15d667
> (host: e044db3f-c49b-467f-9f04-21b44ffe78c4, vm:
> fccee2da-92a3-4187-8aad-d6c1f9d5a3fb)
> 2018-03-18 09:39:57,945-04 WARN 
> [org.ovirt.engine.core.bll.scheduling.pending.PendingResourceManager]
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending
> resource
> org.ovirt.engine.core.bll.scheduling.pending.PendingMemory@1d15d667
> (host: e044db3f-c49b-467f-9f04-21b44ffe78c4, vm:
> fccee2da-92a3-4187-8aad-d6c1f9d5a3fb)
> 2018-03-18 09:39:57,946-04 WARN 
> [org.ovirt.engine.core.bll.scheduling.pending.PendingResourceManager]
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Clearing 

Re: [ovirt-users] Failed to run VM

[Andrei Verovski]

On 03/18/2018 09:34 PM, maoz zadok wrote:
> Thank you Arik you are right, my version is 4.2.0.2, how can I upgrade?

1) upgrade engine as described here
https://www.ovirt.org/release/4.2.1/

2) login into ovirt engine, stop all VMs, choose host -> maintenance,
then upgrade node software.

>
> On Sun, Mar 18, 2018 at 4:11 PM, Arik Hadas  > wrote:
>
>
>
> On Sun, Mar 18, 2018 at 3:43 PM, maoz zadok  > wrote:
>
> Hello All,
> I'm receiving this message every time that I try to start VM,
> any idea?
>
>
> Seems you enounter [1] that is solved in 4.2.2.
> I assume you're using 4.2.1, right? By just looking at the code,
> it seems that restarting the engine could be a possible workaround
> for this.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1532884
> 
>  
>
>
>
>
> 2018-03-18 09:39:51,479-04 ERROR
> [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
> (EE-ManagedThreadFactory-engineScheduled-Thread-11) [] Failed
> during monitoring vm: 2445a47e-b102-11e6-ad11-1866da511add ,
> error is: {}: java.lang.NullPointerException
>
> 2018-03-18 09:39:51,480-04 ERROR
> [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
> (EE-ManagedThreadFactory-engineScheduled-Thread-11) []
> Exception:: java.lang.NullPointerException
>
> 2018-03-18 09:39:57,802-04 INFO 
> [org.ovirt.engine.core.bll.RunVmCommand] (default task-79)
> [b3b98e2c-6176-413d-9d75-315626918150] Lock Acquired to object
> 
> 'EngineLock:{exclusiveLocks='[fccee2da-92a3-4187-8aad-d6c1f9d5a3fb=VM]',
> sharedLocks=''}'
> 2018-03-18 09:39:57,822-04 INFO 
> [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand]
> (default task-79) [b3b98e2c-6176-413d-9d75-315626918150]
> START, IsVmDuringInitiatingVDSCommand(
> 
> IsVmDuringInitiatingVDSCommandParameters:{vmId='fccee2da-92a3-4187-8aad-d6c1f9d5a3fb'}),
> log id: 2217c887
> 2018-03-18 09:39:57,822-04 INFO 
> [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand]
> (default task-79) [b3b98e2c-6176-413d-9d75-315626918150]
> FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id:
> 2217c887
> 2018-03-18 09:39:57,927-04 INFO 
> [org.ovirt.engine.core.bll.RunVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Running command:
> RunVmCommand internal: false. Entities affected :  ID:
> fccee2da-92a3-4187-8aad-d6c1f9d5a3fb Type: VMAction group
> RUN_VM with role type USER
> 2018-03-18 09:39:57,944-04 INFO 
> 
> [org.ovirt.engine.core.bll.scheduling.policyunits.PreferredHostsWeightPolicyUnit]
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Penalizing host 'kvm5'
> because it is not preferred.
> 2018-03-18 09:39:57,944-04 INFO 
> 
> [org.ovirt.engine.core.bll.scheduling.policyunits.PreferredHostsWeightPolicyUnit]
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Penalizing host 'kvm6'
> because it is not preferred.
> 2018-03-18 09:39:57,944-04 INFO 
> 
> [org.ovirt.engine.core.bll.scheduling.policyunits.PreferredHostsWeightPolicyUnit]
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Penalizing host 'kvm7'
> because it is not preferred.
> 2018-03-18 09:39:57,945-04 WARN 
> [org.ovirt.engine.core.bll.scheduling.pending.PendingResourceManager]
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending
> resource
> org.ovirt.engine.core.bll.scheduling.pending.PendingCpuCores@1d15d667
> (host: e044db3f-c49b-467f-9f04-21b44ffe78c4, vm:
> fccee2da-92a3-4187-8aad-d6c1f9d5a3fb)
> 2018-03-18 09:39:57,945-04 WARN 
> [org.ovirt.engine.core.bll.scheduling.pending.PendingResourceManager]
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending
> resource
> org.ovirt.engine.core.bll.scheduling.pending.PendingMemory@1d15d667
> (host: e044db3f-c49b-467f-9f04-21b44ffe78c4, vm:
> fccee2da-92a3-4187-8aad-d6c1f9d5a3fb)
> 2018-03-18 09:39:57,946-04 WARN 
> [org.ovirt.engine.core.bll.scheduling.pending.PendingResourceManager]
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending
> resource
> 
> 

Re: [ovirt-users] Failed to run VM

[maoz zadok]

Thank you Arik you are right, my version is 4.2.0.2, how can I upgrade?

On Sun, Mar 18, 2018 at 4:11 PM, Arik Hadas  wrote:

>
>
> On Sun, Mar 18, 2018 at 3:43 PM, maoz zadok  wrote:
>
>> Hello All,
>> I'm receiving this message every time that I try to start VM,
>> any idea?
>>
>
> Seems you enounter [1] that is solved in 4.2.2.
> I assume you're using 4.2.1, right? By just looking at the code, it seems
> that restarting the engine could be a possible workaround for this.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1532884
>
>
>>
>>
>>
>> 2018-03-18 09:39:51,479-04 ERROR 
>> [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-11) [] Failed during
>> monitoring vm: 2445a47e-b102-11e6-ad11-1866da511add , error is: {}:
>> java.lang.NullPointerException
>>
>> 2018-03-18 09:39:51,480-04 ERROR 
>> [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-11) [] Exception::
>> java.lang.NullPointerException
>>
>> 2018-03-18 09:39:57,802-04 INFO  [org.ovirt.engine.core.bll.RunVmCommand]
>> (default task-79) [b3b98e2c-6176-413d-9d75-315626918150] Lock Acquired
>> to object 
>> 'EngineLock:{exclusiveLocks='[fccee2da-92a3-4187-8aad-d6c1f9d5a3fb=VM]',
>> sharedLocks=''}'
>> 2018-03-18 09:39:57,822-04 INFO  [org.ovirt.engine.core.vdsbrok
>> er.IsVmDuringInitiatingVDSCommand] (default task-79)
>> [b3b98e2c-6176-413d-9d75-315626918150] START,
>> IsVmDuringInitiatingVDSCommand( IsVmDuringInitiatingVDSCommand
>> Parameters:{vmId='fccee2da-92a3-4187-8aad-d6c1f9d5a3fb'}), log id:
>> 2217c887
>> 2018-03-18 09:39:57,822-04 INFO  [org.ovirt.engine.core.vdsbrok
>> er.IsVmDuringInitiatingVDSCommand] (default task-79)
>> [b3b98e2c-6176-413d-9d75-315626918150] FINISH,
>> IsVmDuringInitiatingVDSCommand, return: false, log id: 2217c887
>> 2018-03-18 09:39:57,927-04 INFO  [org.ovirt.engine.core.bll.RunVmCommand]
>> (EE-ManagedThreadFactory-engine-Thread-929544)
>> [b3b98e2c-6176-413d-9d75-315626918150] Running command: RunVmCommand
>> internal: false. Entities affected :  ID: 
>> fccee2da-92a3-4187-8aad-d6c1f9d5a3fb
>> Type: VMAction group RUN_VM with role type USER
>> 2018-03-18 09:39:57,944-04 INFO  [org.ovirt.engine.core.bll.sch
>> eduling.policyunits.PreferredHostsWeightPolicyUnit]
>> (EE-ManagedThreadFactory-engine-Thread-929544)
>> [b3b98e2c-6176-413d-9d75-315626918150] Penalizing host 'kvm5' because it
>> is not preferred.
>> 2018-03-18 09:39:57,944-04 INFO  [org.ovirt.engine.core.bll.sch
>> eduling.policyunits.PreferredHostsWeightPolicyUnit]
>> (EE-ManagedThreadFactory-engine-Thread-929544)
>> [b3b98e2c-6176-413d-9d75-315626918150] Penalizing host 'kvm6' because it
>> is not preferred.
>> 2018-03-18 09:39:57,944-04 INFO  [org.ovirt.engine.core.bll.sch
>> eduling.policyunits.PreferredHostsWeightPolicyUnit]
>> (EE-ManagedThreadFactory-engine-Thread-929544)
>> [b3b98e2c-6176-413d-9d75-315626918150] Penalizing host 'kvm7' because it
>> is not preferred.
>> 2018-03-18 09:39:57,945-04 WARN  [org.ovirt.engine.core.bll.sch
>> eduling.pending.PendingResourceManager] 
>> (EE-ManagedThreadFactory-engine-Thread-929544)
>> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending resource
>> org.ovirt.engine.core.bll.scheduling.pending.PendingCpuCores@1d15d667
>> (host: e044db3f-c49b-467f-9f04-21b44ffe78c4, vm:
>> fccee2da-92a3-4187-8aad-d6c1f9d5a3fb)
>> 2018-03-18 09:39:57,945-04 WARN  [org.ovirt.engine.core.bll.sch
>> eduling.pending.PendingResourceManager] 
>> (EE-ManagedThreadFactory-engine-Thread-929544)
>> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending resource
>> org.ovirt.engine.core.bll.scheduling.pending.PendingMemory@1d15d667
>> (host: e044db3f-c49b-467f-9f04-21b44ffe78c4, vm:
>> fccee2da-92a3-4187-8aad-d6c1f9d5a3fb)
>> 2018-03-18 09:39:57,946-04 WARN  [org.ovirt.engine.core.bll.sch
>> eduling.pending.PendingResourceManager] 
>> (EE-ManagedThreadFactory-engine-Thread-929544)
>> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending resource
>> org.ovirt.engine.core.bll.scheduling.pending.PendingOvercomm
>> itMemory@1d15d667 (host: e044db3f-c49b-467f-9f04-21b44ffe78c4, vm:
>> fccee2da-92a3-4187-8aad-d6c1f9d5a3fb)
>> 2018-03-18 09:39:57,946-04 WARN  [org.ovirt.engine.core.bll.sch
>> eduling.pending.PendingResourceManager] 
>> (EE-ManagedThreadFactory-engine-Thread-929544)
>> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending resource
>> org.ovirt.engine.core.bll.scheduling.pending.PendingVM@1d15d667 (host:
>> e044db3f-c49b-467f-9f04-21b44ffe78c4, vm: fccee2da-92a3-4187-8aad-d6c1f9
>> d5a3fb)
>> 2018-03-18 09:39:57,946-04 ERROR [org.ovirt.engine.core.bll.RunVmCommand]
>> (EE-ManagedThreadFactory-engine-Thread-929544)
>> [b3b98e2c-6176-413d-9d75-315626918150] Command
>> 'org.ovirt.engine.core.bll.RunVmCommand' failed: null
>> 2018-03-18 09:39:57,946-04 ERROR [org.ovirt.engine.core.bll.RunVmCommand]
>> 

Re: [ovirt-users] Postgresql read only user difficulties

[Vincent Royer]

well this is frustrating.  I added the read only user, but still can't
connect.

pq: password authentication failed for user "grafana"


*Vincent Royer*
*778-825-1057*



*SUSTAINABLE MOBILE ENERGY SOLUTIONS*




On Sat, Mar 17, 2018 at 11:43 AM, Maton, Brett 
wrote:

> Yeah if postgres won't start you've probably got a typo in pg_hba.conf
>
> On 17 March 2018 at 18:11, Vincent Royer  wrote:
>
>> I think I see the issue.  Extra space after the IP address in pg_hba.conf
>>
>> I'll try again later.
>>
>> Thanks for your help!
>>
>>
>>
>>
>> On Sat, Mar 17, 2018 at 10:44 AM, Vincent Royer 
>> wrote:
>>
>>> hmmm.  not a great result...
>>>
>>>  rh-postgresql95-postgresql.service:...1
>>> Mar 17 10:36:32 ovirt-engine systemd[1]: Failed to start PostgreSQL
>>> database
>>> Mar 17 10:36:32 ovirt-engine systemd[1]: Unit
>>> rh-postgresql95-postgresql.ser
>>> Mar 17 10:36:32 ovirt-engine systemd[1]: rh-postgresql95-postgresql.service
>>> 
>>>
>>> and can no longer login to ovirt-engine gui:
>>>
>>> server_error: Connection refused. Check that the hostname and port are
>>> correct and that the postmaster is accepting TCP/IP connections.
>>>
>>> tried to restart ovirt-engine and it won't come up - internal server
>>> error.
>>>
>>>
>>>
>>> *Vincent Royer*
>>> *778-825-1057 <(778)%20825-1057>*
>>>
>>>
>>> 
>>> *SUSTAINABLE MOBILE ENERGY SOLUTIONS*
>>>
>>>
>>>
>>>
>>> On Sat, Mar 17, 2018 at 4:34 AM, Maton, Brett 
>>> wrote:
>>>
 You could always try reloading the configuration, pretty sure pg_hba
 gets reloaded these days:

 su - postgres
 scl enable rh-postgresql95 bash
 pg_ctl reload -D /var/opt/rh/rh-postgresql95/lib/pgsql/data

 or as root

 systemctl restart rh-postgresql95-postgresql.service


 On 17 March 2018 at 11:20, Vincent Royer  wrote:

> ok thanks, I did see it there but assumed that was a temp file.  I
> updated it according to the instructions, but I still get the same error.
>
> # TYPE  DATABASEUSERADDRESS METHOD
>
> # "local" is for Unix domain socket connections only
> local   all all peer
> hostovirt_engine_history ovirt_engine_history 0.0.0.0/0
>  md5
> hostovirt_engine_history ovirt_engine_history ::0/0
>md5
> hostovirt_engine_history grafana 172.16.30.10 /0   md5
> hostovirt_engine_history grafana ::0/0   md5
> hostengine  engine  0.0.0.0/0   md5
> hostengine  engine  ::0/0   md5
>
>
> did a systemctl restart postgresql.service and I get "Unit not
> found".   So I did systemctl restart ovirt-engine.service...
>
> and the error I get when accessing from 172.16.30.10 is:
>
> pq: no pg_hba.conf entry for host "172.16.30.10", user "grafana",
> database "ovirt_engine_history", SSL off
>
>
>
>
> *Vincent Royer*
> *778-825-1057 <(778)%20825-1057>*
>
>
> 
> *SUSTAINABLE MOBILE ENERGY SOLUTIONS*
>
>
>
>
> On Sat, Mar 17, 2018 at 3:42 AM, Maton, Brett <
> mat...@ltresources.co.uk> wrote:
>
>> Hi Vincent,
>>
>>   oVirt isn't using the stock PostgreSQL but an SCL version
>>   You should find pg_hba.conf here /var/opt/rh/rh-postgresql95/li
>> b/pgsql/data/pg_hba.conf
>>
>> Hope this helps.
>>
>> On 17 March 2018 at 09:50, Vincent Royer 
>> wrote:
>>
>>> Hi,
>>>
>>> I followed these instructions on Ovirt self hosted engine 4.2.1:
>>>
>>> https://www.ovirt.org/documentation/data-warehouse/Allowing_
>>> Read_Only_Access_to_the_History_Database/
>>>
>>> when connecting to the db from an external host I receive this error:
>>>
>>> pq: no pg_hba.conf entry for host "", user "", database
>>> "ovirt_engine_history", SSL off
>>>
>>> I looked in the normal place for pg_hba.conf but the file does not
>>> exist, /data does not exist in /var/lib/pgsql
>>>
>>> Do i need to run engine-setup again to configure this?
>>>
>>> Thank you!
>>>
>>> ___
>>> 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] Failed to run VM

[Arik Hadas]

On Sun, Mar 18, 2018 at 3:43 PM, maoz zadok  wrote:

> Hello All,
> I'm receiving this message every time that I try to start VM,
> any idea?
>

Seems you enounter [1] that is solved in 4.2.2.
I assume you're using 4.2.1, right? By just looking at the code, it seems
that restarting the engine could be a possible workaround for this.

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


>
>
>
> 2018-03-18 09:39:51,479-04 ERROR [org.ovirt.engine.core.
> vdsbroker.monitoring.VmsMonitoring] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-11)
> [] Failed during monitoring vm: 2445a47e-b102-11e6-ad11-1866da511add ,
> error is: {}: java.lang.NullPointerException
>
> 2018-03-18 09:39:51,480-04 ERROR [org.ovirt.engine.core.
> vdsbroker.monitoring.VmsMonitoring] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-11)
> [] Exception:: java.lang.NullPointerException
>
> 2018-03-18 09:39:57,802-04 INFO  [org.ovirt.engine.core.bll.RunVmCommand]
> (default task-79) [b3b98e2c-6176-413d-9d75-315626918150] Lock Acquired to
> object 
> 'EngineLock:{exclusiveLocks='[fccee2da-92a3-4187-8aad-d6c1f9d5a3fb=VM]',
> sharedLocks=''}'
> 2018-03-18 09:39:57,822-04 INFO  [org.ovirt.engine.core.vdsbroker.
> IsVmDuringInitiatingVDSCommand] (default task-79)
> [b3b98e2c-6176-413d-9d75-315626918150] START,
> IsVmDuringInitiatingVDSCommand( IsVmDuringInitiatingVDSCommand
> Parameters:{vmId='fccee2da-92a3-4187-8aad-d6c1f9d5a3fb'}), log id:
> 2217c887
> 2018-03-18 09:39:57,822-04 INFO  [org.ovirt.engine.core.vdsbroker.
> IsVmDuringInitiatingVDSCommand] (default task-79)
> [b3b98e2c-6176-413d-9d75-315626918150] FINISH,
> IsVmDuringInitiatingVDSCommand, return: false, log id: 2217c887
> 2018-03-18 09:39:57,927-04 INFO  [org.ovirt.engine.core.bll.RunVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-929544) 
> [b3b98e2c-6176-413d-9d75-315626918150]
> Running command: RunVmCommand internal: false. Entities affected :  ID:
> fccee2da-92a3-4187-8aad-d6c1f9d5a3fb Type: VMAction group RUN_VM with
> role type USER
> 2018-03-18 09:39:57,944-04 INFO  [org.ovirt.engine.core.bll.
> scheduling.policyunits.PreferredHostsWeightPolicyUnit]
> (EE-ManagedThreadFactory-engine-Thread-929544) 
> [b3b98e2c-6176-413d-9d75-315626918150]
> Penalizing host 'kvm5' because it is not preferred.
> 2018-03-18 09:39:57,944-04 INFO  [org.ovirt.engine.core.bll.
> scheduling.policyunits.PreferredHostsWeightPolicyUnit]
> (EE-ManagedThreadFactory-engine-Thread-929544) 
> [b3b98e2c-6176-413d-9d75-315626918150]
> Penalizing host 'kvm6' because it is not preferred.
> 2018-03-18 09:39:57,944-04 INFO  [org.ovirt.engine.core.bll.
> scheduling.policyunits.PreferredHostsWeightPolicyUnit]
> (EE-ManagedThreadFactory-engine-Thread-929544) 
> [b3b98e2c-6176-413d-9d75-315626918150]
> Penalizing host 'kvm7' because it is not preferred.
> 2018-03-18 09:39:57,945-04 WARN  [org.ovirt.engine.core.bll.
> scheduling.pending.PendingResourceManager] 
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending resource
> org.ovirt.engine.core.bll.scheduling.pending.PendingCpuCores@1d15d667
> (host: e044db3f-c49b-467f-9f04-21b44ffe78c4, vm: fccee2da-92a3-4187-8aad-
> d6c1f9d5a3fb)
> 2018-03-18 09:39:57,945-04 WARN  [org.ovirt.engine.core.bll.
> scheduling.pending.PendingResourceManager] 
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending resource
> org.ovirt.engine.core.bll.scheduling.pending.PendingMemory@1d15d667
> (host: e044db3f-c49b-467f-9f04-21b44ffe78c4, vm: fccee2da-92a3-4187-8aad-
> d6c1f9d5a3fb)
> 2018-03-18 09:39:57,946-04 WARN  [org.ovirt.engine.core.bll.
> scheduling.pending.PendingResourceManager] 
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending resource
> org.ovirt.engine.core.bll.scheduling.pending.PendingOvercommitMemory@1d15d667
> (host: e044db3f-c49b-467f-9f04-21b44ffe78c4, vm: fccee2da-92a3-4187-8aad-
> d6c1f9d5a3fb)
> 2018-03-18 09:39:57,946-04 WARN  [org.ovirt.engine.core.bll.
> scheduling.pending.PendingResourceManager] 
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending resource
> org.ovirt.engine.core.bll.scheduling.pending.PendingVM@1d15d667 (host:
> e044db3f-c49b-467f-9f04-21b44ffe78c4, vm: fccee2da-92a3-4187-8aad-
> d6c1f9d5a3fb)
> 2018-03-18 09:39:57,946-04 ERROR [org.ovirt.engine.core.bll.RunVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-929544) 
> [b3b98e2c-6176-413d-9d75-315626918150]
> Command 'org.ovirt.engine.core.bll.RunVmCommand' failed: null
> 2018-03-18 09:39:57,946-04 ERROR [org.ovirt.engine.core.bll.RunVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-929544) 
> [b3b98e2c-6176-413d-9d75-315626918150]
> Exception: java.lang.NullPointerException
> at org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring.
> refreshCommitedMemory(HostMonitoring.java:687) [vdsbroker.jar:]
> at 

[ovirt-users] Failed to run VM

[maoz zadok]

Hello All,
I'm receiving this message every time that I try to start VM,
any idea?



2018-03-18 09:39:51,479-04 ERROR
[org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
(EE-ManagedThreadFactory-engineScheduled-Thread-11) [] Failed during
monitoring vm: 2445a47e-b102-11e6-ad11-1866da511add , error is: {}:
java.lang.NullPointerException

2018-03-18 09:39:51,480-04 ERROR
[org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
(EE-ManagedThreadFactory-engineScheduled-Thread-11) [] Exception::
java.lang.NullPointerException

2018-03-18 09:39:57,802-04 INFO  [org.ovirt.engine.core.bll.RunVmCommand]
(default task-79) [b3b98e2c-6176-413d-9d75-315626918150] Lock Acquired to
object
'EngineLock:{exclusiveLocks='[fccee2da-92a3-4187-8aad-d6c1f9d5a3fb=VM]',
sharedLocks=''}'
2018-03-18 09:39:57,822-04 INFO
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default
task-79) [b3b98e2c-6176-413d-9d75-315626918150] START,
IsVmDuringInitiatingVDSCommand(
IsVmDuringInitiatingVDSCommandParameters:{vmId='fccee2da-92a3-4187-8aad-d6c1f9d5a3fb'}),
log id: 2217c887
2018-03-18 09:39:57,822-04 INFO
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default
task-79) [b3b98e2c-6176-413d-9d75-315626918150] FINISH,
IsVmDuringInitiatingVDSCommand, return: false, log id: 2217c887
2018-03-18 09:39:57,927-04 INFO  [org.ovirt.engine.core.bll.RunVmCommand]
(EE-ManagedThreadFactory-engine-Thread-929544)
[b3b98e2c-6176-413d-9d75-315626918150] Running command: RunVmCommand
internal: false. Entities affected :  ID:
fccee2da-92a3-4187-8aad-d6c1f9d5a3fb Type: VMAction group RUN_VM with role
type USER
2018-03-18 09:39:57,944-04 INFO
[org.ovirt.engine.core.bll.scheduling.policyunits.PreferredHostsWeightPolicyUnit]
(EE-ManagedThreadFactory-engine-Thread-929544)
[b3b98e2c-6176-413d-9d75-315626918150] Penalizing host 'kvm5' because it is
not preferred.
2018-03-18 09:39:57,944-04 INFO
[org.ovirt.engine.core.bll.scheduling.policyunits.PreferredHostsWeightPolicyUnit]
(EE-ManagedThreadFactory-engine-Thread-929544)
[b3b98e2c-6176-413d-9d75-315626918150] Penalizing host 'kvm6' because it is
not preferred.
2018-03-18 09:39:57,944-04 INFO
[org.ovirt.engine.core.bll.scheduling.policyunits.PreferredHostsWeightPolicyUnit]
(EE-ManagedThreadFactory-engine-Thread-929544)
[b3b98e2c-6176-413d-9d75-315626918150] Penalizing host 'kvm7' because it is
not preferred.
2018-03-18 09:39:57,945-04 WARN
[org.ovirt.engine.core.bll.scheduling.pending.PendingResourceManager]
(EE-ManagedThreadFactory-engine-Thread-929544)
[b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending resource
org.ovirt.engine.core.bll.scheduling.pending.PendingCpuCores@1d15d667
(host: e044db3f-c49b-467f-9f04-21b44ffe78c4, vm:
fccee2da-92a3-4187-8aad-d6c1f9d5a3fb)
2018-03-18 09:39:57,945-04 WARN
[org.ovirt.engine.core.bll.scheduling.pending.PendingResourceManager]
(EE-ManagedThreadFactory-engine-Thread-929544)
[b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending resource
org.ovirt.engine.core.bll.scheduling.pending.PendingMemory@1d15d667 (host:
e044db3f-c49b-467f-9f04-21b44ffe78c4, vm:
fccee2da-92a3-4187-8aad-d6c1f9d5a3fb)
2018-03-18 09:39:57,946-04 WARN
[org.ovirt.engine.core.bll.scheduling.pending.PendingResourceManager]
(EE-ManagedThreadFactory-engine-Thread-929544)
[b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending resource
org.ovirt.engine.core.bll.scheduling.pending.PendingOvercommitMemory@1d15d667
(host: e044db3f-c49b-467f-9f04-21b44ffe78c4, vm:
fccee2da-92a3-4187-8aad-d6c1f9d5a3fb)
2018-03-18 09:39:57,946-04 WARN
[org.ovirt.engine.core.bll.scheduling.pending.PendingResourceManager]
(EE-ManagedThreadFactory-engine-Thread-929544)
[b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending resource
org.ovirt.engine.core.bll.scheduling.pending.PendingVM@1d15d667 (host:
e044db3f-c49b-467f-9f04-21b44ffe78c4, vm:
fccee2da-92a3-4187-8aad-d6c1f9d5a3fb)
2018-03-18 09:39:57,946-04 ERROR [org.ovirt.engine.core.bll.RunVmCommand]
(EE-ManagedThreadFactory-engine-Thread-929544)
[b3b98e2c-6176-413d-9d75-315626918150] Command
'org.ovirt.engine.core.bll.RunVmCommand' failed: null
2018-03-18 09:39:57,946-04 ERROR [org.ovirt.engine.core.bll.RunVmCommand]
(EE-ManagedThreadFactory-engine-Thread-929544)
[b3b98e2c-6176-413d-9d75-315626918150] Exception:
java.lang.NullPointerException
at
org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring.refreshCommitedMemory(HostMonitoring.java:687)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.VdsManager.updatePendingData(VdsManager.java:476)
[vdsbroker.jar:]
at
org.ovirt.engine.core.bll.scheduling.pending.PendingResourceManager.notifyHostManagers(PendingResourceManager.java:227)
[bll.jar:]
at
org.ovirt.engine.core.bll.scheduling.SchedulingManager.schedule(SchedulingManager.java:361)
[bll.jar:]
at
org.ovirt.engine.core.bll.RunVmCommand.getVdsToRunOn(RunVmCommand.java:878)
[bll.jar:]
at org.ovirt.engine.core.bll.RunVmCommand.runVm(RunVmCommand.java:266)
[bll.jar:]
at

Re: [ovirt-users] oVirt 4.2 Fresh Install - Storage Domain

[Maton, Brett]

Right fresh install of CentOS 7.4 all updated

Installed ovirt using the repositories from provided by ovirt-release42.rpm

The install seems to go fine, once the hosted engine is up /var/log/message
is getting filled with the following messages:

journal: ovirt-ha-agent
ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config ERROR Unable
to identify the OVF_STORE volume, falling back to initial vm.conf. Please
ensure you already added your first data domain for regular VMs


I've added a new storage domain as used to be required, but as Nir
suggested earlier the expected behaviour in 4.2 is that the hosted_storage
domain remains master and /var/log/messages continues to fill with the
above messages.



One other niggle I've found in the current installer is the space required
to generate hosted_engine, the instructions on this page Deploying
Self-Hosted Engine

suggest that the installer will check that there is enough available space
or prompt for an alternative location if there isn't enough at /var/tmp.
Actually it does neither and fails the deployment only saying to check the
log files for a possible cause.



On 18 March 2018 at 11:12, Maton, Brett  wrote:

> Ok, that does make sense.
>
> I'm rebuilding again at the moment anyway, I'll keep this thread updated
> as deployment progresses.
>
> On 18 March 2018 at 10:55, Nir Soffer  wrote:
>
>> On Sun, Mar 18, 2018 at 12:01 PM Maton, Brett 
>> wrote:
>>
>>> Yes, both are on NFS and both are mounted.
>>>
>>> For what it's worth all the storage this cluster will connect to is on
>>> the same NAS device, same permissions etc etc, and it does connect it's
>>> just not 'flipping' the master domain.
>>>
>>> This is the first time I've tried a fresh install of
>>> 4.2.1.7-1.el7.centos, I generally in-place upgrade on this cluster.
>>>
>>>  If there are any logs they might give a clue as to what's happening I'm
>>> happy to shre those.
>>>
>>> In the mean time I'll flatten the host and deploy from scratch again.
>>>
>>
>> No need to flatten the host, I think the behavior is expected in 4.2. The
>> installation process
>> was streamlines and there is no need now to create another storage domain
>> to force the
>> system to import the hosted engine domain.
>>
>> Since the hosted engine storage domain cannot be deactivated, using it
>> for master is good.
>> it meas you can deactivate any other storage domain if needed.
>>
>> Maybe the documentation needs update?
>>
>> On 17 March 2018 at 18:54, Juan Pablo  wrote:
>>>
 as soon as you install ovirt when you add a second storage domain, it
 should switch to it as the master, not hosted storage as you have. are both
 nfs?

 JP


 2018-03-17 15:45 GMT-03:00 Maton, Brett :

> I have added a new domain, but it's not playing ball.
>
> hosted_storage Data (master)  Active
> vm_storage Data   Active
>
> On 17 March 2018 at 17:24, Juan Pablo 
> wrote:
>
>> you need to configure first a domain (can be temporary) then, import
>> the storage domain.
>>
>>
>>
>> 2018-03-17 7:13 GMT-03:00 Maton, Brett :
>>
>>> I've just reinstalled ovirt 4.2 (ovirt-release42.rpm) on a clean
>>> CentOS 7.4 host, all went fine however
>>>
>>> Now that the hosted engine is up, I've added a data storage domain
>>> but it looks like the next step that detects / promotes the new data 
>>> domain
>>> to master isn't being triggered.
>>>
>>> Hosted engine and data domain are on NFS storage, /var/log/messages
>>> is filling with these messages
>>>
>>> journal: ovirt-ha-agent ovirt_hosted_engine_ha.agent.h
>>> osted_engine.HostedEngine.config ERROR Unable to identify the
>>> OVF_STORE volume, falling back to initial vm.conf. Please ensure you
>>> already added your first data domain for regular VMs
>>>
>>>
>>> I ran into the same issue when I imported an existing domain.
>>>
>>> ___
>>> 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
>>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 4.2 Fresh Install - Storage Domain

[Maton, Brett]

Ok, that does make sense.

I'm rebuilding again at the moment anyway, I'll keep this thread updated as
deployment progresses.

On 18 March 2018 at 10:55, Nir Soffer  wrote:

> On Sun, Mar 18, 2018 at 12:01 PM Maton, Brett 
> wrote:
>
>> Yes, both are on NFS and both are mounted.
>>
>> For what it's worth all the storage this cluster will connect to is on
>> the same NAS device, same permissions etc etc, and it does connect it's
>> just not 'flipping' the master domain.
>>
>> This is the first time I've tried a fresh install of
>> 4.2.1.7-1.el7.centos, I generally in-place upgrade on this cluster.
>>
>>  If there are any logs they might give a clue as to what's happening I'm
>> happy to shre those.
>>
>> In the mean time I'll flatten the host and deploy from scratch again.
>>
>
> No need to flatten the host, I think the behavior is expected in 4.2. The
> installation process
> was streamlines and there is no need now to create another storage domain
> to force the
> system to import the hosted engine domain.
>
> Since the hosted engine storage domain cannot be deactivated, using it for
> master is good.
> it meas you can deactivate any other storage domain if needed.
>
> Maybe the documentation needs update?
>
> On 17 March 2018 at 18:54, Juan Pablo  wrote:
>>
>>> as soon as you install ovirt when you add a second storage domain, it
>>> should switch to it as the master, not hosted storage as you have. are both
>>> nfs?
>>>
>>> JP
>>>
>>>
>>> 2018-03-17 15:45 GMT-03:00 Maton, Brett :
>>>
 I have added a new domain, but it's not playing ball.

 hosted_storage Data (master)  Active
 vm_storage Data   Active

 On 17 March 2018 at 17:24, Juan Pablo 
 wrote:

> you need to configure first a domain (can be temporary) then, import
> the storage domain.
>
>
>
> 2018-03-17 7:13 GMT-03:00 Maton, Brett :
>
>> I've just reinstalled ovirt 4.2 (ovirt-release42.rpm) on a clean
>> CentOS 7.4 host, all went fine however
>>
>> Now that the hosted engine is up, I've added a data storage domain
>> but it looks like the next step that detects / promotes the new data 
>> domain
>> to master isn't being triggered.
>>
>> Hosted engine and data domain are on NFS storage, /var/log/messages
>> is filling with these messages
>>
>> journal: ovirt-ha-agent ovirt_hosted_engine_ha.agent.
>> hosted_engine.HostedEngine.config ERROR Unable to identify the
>> OVF_STORE volume, falling back to initial vm.conf. Please ensure you
>> already added your first data domain for regular VMs
>>
>>
>> I ran into the same issue when I imported an existing domain.
>>
>> ___
>> 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
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 4.2 Fresh Install - Storage Domain

[Nir Soffer]

On Sun, Mar 18, 2018 at 12:01 PM Maton, Brett 
wrote:

> Yes, both are on NFS and both are mounted.
>
> For what it's worth all the storage this cluster will connect to is on the
> same NAS device, same permissions etc etc, and it does connect it's just
> not 'flipping' the master domain.
>
> This is the first time I've tried a fresh install of 4.2.1.7-1.el7.centos,
> I generally in-place upgrade on this cluster.
>
>  If there are any logs they might give a clue as to what's happening I'm
> happy to shre those.
>
> In the mean time I'll flatten the host and deploy from scratch again.
>

No need to flatten the host, I think the behavior is expected in 4.2. The
installation process
was streamlines and there is no need now to create another storage domain
to force the
system to import the hosted engine domain.

Since the hosted engine storage domain cannot be deactivated, using it for
master is good.
it meas you can deactivate any other storage domain if needed.

Maybe the documentation needs update?

On 17 March 2018 at 18:54, Juan Pablo  wrote:
>
>> as soon as you install ovirt when you add a second storage domain, it
>> should switch to it as the master, not hosted storage as you have. are both
>> nfs?
>>
>> JP
>>
>>
>> 2018-03-17 15:45 GMT-03:00 Maton, Brett :
>>
>>> I have added a new domain, but it's not playing ball.
>>>
>>> hosted_storage Data (master)  Active
>>> vm_storage Data   Active
>>>
>>> On 17 March 2018 at 17:24, Juan Pablo  wrote:
>>>
 you need to configure first a domain (can be temporary) then, import
 the storage domain.



 2018-03-17 7:13 GMT-03:00 Maton, Brett :

> I've just reinstalled ovirt 4.2 (ovirt-release42.rpm) on a clean
> CentOS 7.4 host, all went fine however
>
> Now that the hosted engine is up, I've added a data storage domain but
> it looks like the next step that detects / promotes the new data domain to
> master isn't being triggered.
>
> Hosted engine and data domain are on NFS storage, /var/log/messages is
> filling with these messages
>
> journal: ovirt-ha-agent
> ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config ERROR 
> Unable
> to identify the OVF_STORE volume, falling back to initial vm.conf. Please
> ensure you already added your first data domain for regular VMs
>
>
> I ran into the same issue when I imported an existing domain.
>
> ___
> 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
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 4.2 Fresh Install - Storage Domain

[Maton, Brett]

Yes, both are on NFS and both are mounted.

For what it's worth all the storage this cluster will connect to is on the
same NAS device, same permissions etc etc, and it does connect it's just
not 'flipping' the master domain.

This is the first time I've tried a fresh install of 4.2.1.7-1.el7.centos,
I generally in-place upgrade on this cluster.

 If there are any logs they might give a clue as to what's happening I'm
happy to shre those.

In the mean time I'll flatten the host and deploy from scratch again.


On 17 March 2018 at 18:54, Juan Pablo  wrote:

> as soon as you install ovirt when you add a second storage domain, it
> should switch to it as the master, not hosted storage as you have. are both
> nfs?
>
> JP
>
>
> 2018-03-17 15:45 GMT-03:00 Maton, Brett :
>
>> I have added a new domain, but it's not playing ball.
>>
>> hosted_storage Data (master)  Active
>> vm_storage Data   Active
>>
>> On 17 March 2018 at 17:24, Juan Pablo  wrote:
>>
>>> you need to configure first a domain (can be temporary) then, import the
>>> storage domain.
>>>
>>>
>>>
>>> 2018-03-17 7:13 GMT-03:00 Maton, Brett :
>>>
 I've just reinstalled ovirt 4.2 (ovirt-release42.rpm) on a clean CentOS
 7.4 host, all went fine however

 Now that the hosted engine is up, I've added a data storage domain but
 it looks like the next step that detects / promotes the new data domain to
 master isn't being triggered.

 Hosted engine and data domain are on NFS storage, /var/log/messages is
 filling with these messages

 journal: ovirt-ha-agent ovirt_hosted_engine_ha.agent.h
 osted_engine.HostedEngine.config ERROR Unable to identify the
 OVF_STORE volume, falling back to initial vm.conf. Please ensure you
 already added your first data domain for regular VMs


 I ran into the same issue when I imported an existing domain.

 ___
 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] VM has been paused due to NO STORAGE SPACE ERROR ?!?!?!?!

[Yaniv Kaul]

On Fri, Mar 16, 2018 at 1:25 PM, Enrico Becchetti <
enrico.becche...@pg.infn.it> wrote:

>   Dear All,
> Does someone had seen that error ? When I run this command from my virtual
> machine:
>
> # time dd if=/dev/zero of=enrico.dd bs=4k count=1000
>

I don't think it's a very interesting test case for IO performance, but in
any case, it may cause the VM to try to write faster than its thin
provisioned disk can be extended.
A simple workaround would be to change in VDSM the threshold of when it
gets extended and by how much.
For example:
[irs]
volume_utilization_percent = 15
volume_utilization_chunk_mb = 4048

Y.


> VM was paused due to kind a storage error/problem. Strange message
> because tell about "no storage space error" but ovirt puts virtual machine
> in
> a paused state.
>
> Inside events  from  ovirt web interface  I see this:
>
> "VM has been paused due to lack of storage space"
>
> but no ERROR found in /var/log/vdsm.log.
>
> My oVirt enviroment 4.2.1 has three hypervivosr with FC storage and before
> now
> I haven't see any other problem during the normal functioning of the vm ,
> it's seem
> that this error occurs only when there is massive I/O.
>
> Any ideas ?
> Thanks a lot.
> Best Regards
> Enrico
>
>
> --
> ___
>
> Enrico BecchettiServizio di Calcolo e Reti
>
> Istituto Nazionale di Fisica Nucleare - Sezione di Perugia
> Via Pascoli,c/o Dipartimento di Fisica  06123 Perugia (ITALY)
> Phone:+39 075 5852777 Mail: Enrico.Becchettipg.infn.it
> __
>
> ___
> 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] Hosted engine : rebuild without backups ?

[Yedidyah Bar David]

On Fri, Mar 16, 2018 at 2:48 PM,   wrote:
> Hi,
>
> In case of a total failure of the hosted engine VM, it is recommended to
> recreate a new one and restore a backup. I hope it works, I will probably
> have to do this very soon.
>
> But is there some kind of "plug and play" features, able to rebuild
> configuration by browsing storage domains, if the restore process doesn't
> work ?

It's called "Import Storage Domain" in oVirt.

>
> Something like identifying VMs and their snapshots in the subdirectories,
> and the guess what is linked to what, ... ?
>
> I have a few machines but if I have to rebuild all the engine setup and
> content, I would like to be able to identify resources easily.
>
> A few times ago, I was doing some experiments with XenServer and
> destroyed/recreated some setup items : I ended with a lot of oprhan
> resources, and it was a mess to reattach snapshots to their respective VMs.
> So if oVirt is more helpful in that way ...

If you try this:

1. Try first on a test setup, as always
2. Make sure to _not_ import the hosted-storage domain, the one used to
host the hosted-engine VM.
3. So: setup a new hosted-engine system, then import your _other_ storage
domains. Ideally make sure the old hosted storage is not accessible to
the new system, so that the new engine does not try to import it accidentally.
4. If you do try to import, for testing, the old hosted-storage, would be
interesting if you share the results...

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

Re: [ovirt-users] Warning: CentOS Upgrade with Host Engine - 503 Service Temporarily Unavailable

[Yedidyah Bar David]

On Thu, Mar 15, 2018 at 5:39 PM, Andrei Verovski  wrote:
> Hi !
>
> I have upgraded CentOS 7.4 with oVirt 4.2.1 host engine (with yum upgrade),
> and its resulted in broken system - "503 Service Temporarily Unavailable"
> when connecting to the host engine via web.
> Service ovirt-engine failed to starts (logs attached at the bottom of this
> email), other ovirt services seem to run fine.
>
> yum update "ovirt-*-setup*” (upgrade 4.2 -> 4.2.1)
> engine-setup
> yum upgrade (OS upgrade)
>
> Is this issue somehow related to JDK as described here?
> https://bugzilla.redhat.com/show_bug.cgi?id=1217023

Not very likely. This is a very old bug.

>
> New packages:
> java-1.8.0-openjdk  x86_64   1:1.8.0.161-0.b14.el7_4
> java-1.8.0-openjdk-develx86_64   1:1.8.0.161-0.b14.el7_4
> java-1.8.0-openjdk-headless x86_64   1:1.8.0.161-0.b14.el7_4
>
> installed packages (seem to be also 1.8x):
> [root@node00 ~]# rpm -qa | grep jdk
> java-1.8.0-openjdk-1.8.0.151-5.b12.el7_4.x86_64
> java-1.8.0-openjdk-devel-1.8.0.151-5.b12.el7_4.x86_64
> java-1.8.0-openjdk-headless-1.8.0.151-5.b12.el7_4.x86_64
> copy-jdk-configs-2.2-5.el7_4.noarch

Indeed. Some versions of the engine could work with both openjdk 1.7
and 1.8, but recent versions require 1.8.

>
> Since my host engine is actually a KVM appliance under another SuSE server,
> I simply discarded it and reverted back old qcow2 image.

OK. Any chance you kept a copy, or at least more logs, for further debugging?

>
> So this is a warning to anyone - don’t upgrade CentOS, or at least keep a
> copy of disk image before ANY upgrade !

Having regular backups, both before significant changes like upgrades
and also routine, on-going, is always a good idea :-)

If you have all of server.log, we can try to understand the cause for
the failure. If not, and you try again to upgrade and if fails again,
please share all relevant logs before reverting to the backup. Thanks!

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