Re: [ovirt-users] sanlock ids file broken after server crash (Fixed)

2017-08-01 Thread Johan Bernhardsson
I have two options. One it got there when we moved the servers from our lab desk to the hosting site. We had some problems getting it running.  Or two a couple of weeks ago two servers rebooted after high load. That might have caused a damage to the file. I did manage to move all servers from

Re: [ovirt-users] Pass Discard guest OS support?

2017-08-01 Thread Yaniv Kaul
On Tue, Aug 1, 2017 at 6:05 PM, Doug Ingham wrote: > Hi All, > Just today I noticed that guests can now pass discards to the underlying > shared filesystem. > Or block storage. Most likely it works better on shared block storage. > >

Re: [ovirt-users] supervdsmd IOError to /dev/stdout

2017-08-01 Thread Nir Soffer
On Tue, Aug 1, 2017 at 3:07 PM Richard Chan wrote: > Hi, > > Could this be the cause of the access issue (old system upgraded from 3.4 > all the way to 4.1)? > ## change in python class name?? > > [handler_logfile] > -class=logUtils.UserGroupEnforcingHandler >

Re: [ovirt-users] oVirt and Foreman

2017-08-01 Thread Juan Hernández
On 07/28/2017 06:03 PM, Davide Ferrari wrote: On 28/07/17 17:46, Juan Hernández wrote: The oVirt access log indeed shows that three disks are added to the virtual machine. May it be that Foreman thinks that it has to explicitly add a boot disk? Ohad, Ivan, any idea? I've explicitly

[ovirt-users] Pass Discard guest OS support?

2017-08-01 Thread Doug Ingham
Hi All, Just today I noticed that guests can now pass discards to the underlying shared filesystem. http://www.ovirt.org/develop/release-management/features/storage/pass-discard-from-guest-to-underlying-storage/ Is this supported by all of the main Linux guest OS's running the virt agent? And

Re: [ovirt-users] oVirt 4.1.2 update but rubygem-fluent-plugin-viaq_data_model package missing

2017-08-01 Thread Sandro Bonazzola
On Tue, Aug 1, 2017 at 3:36 PM, Fabrice Moyen wrote: > > Hello, > > I'm running Ovirt 4.1.2 onto ppc64le platforms (running centOS 7 LE). I > see my ovirt manager has an issue upgrading my two hosts. When checking at > the engine.log log, I can see the following error

Re: [ovirt-users] After upgrading to 4.1.4 unable to start VM or migrate them

2017-08-01 Thread Arman Khalatyan
It is unclear now, I am not able to reproduce the error...probably changing the policy fixed the "null" record in the database. My upgrade went w/o error from 4.1.3 to 4.1.4. The engine.log from yesterday is here: with the password:BUG https://cloud.aip.de/index.php/s/N6xY0gw3GdEf63H (I hope I am

[ovirt-users] oVirt 4.1.2 update but rubygem-fluent-plugin-viaq_data_model package missing

2017-08-01 Thread Fabrice Moyen
  Hello,    I'm running Ovirt 4.1.2 onto ppc64le platforms (running centOS 7 LE). I see my ovirt manager has an issue upgrading my two hosts. When checking at the engine.log log, I can see the following error message:   2017-07-28 12:14:42,747+02 ERROR

[ovirt-users] Install external certificate

2017-08-01 Thread Marcelo Leandro
Good morning I bought a external certificate, in godaddy , and they send to me only one archive crt. I saw this: https://www.ovirt.org/documentation/admin-guide/appe-oVirt_and_SSL/ I don't know how I can generate a certificate p12. Can someone help me ? Thanks. Marcelo Leandro

Re: [ovirt-users] Deploying training lab

2017-08-01 Thread David Jaša
Hi, This sounds like something that might fit your needs: https://github.com/ThinStation/thinstation and the looks alive. I didn't try it myself though. If you're not satisfied with this or any other existing distro, you could either slim down an existing distro (e.g. creating your own lean

Re: [ovirt-users] supervdsmd IOError to /dev/stdout

2017-08-01 Thread Richard Chan
Hi, Could this be the cause of the access issue (old system upgraded from 3.4 all the way to 4.1)? ## change in python class name?? [handler_logfile] -class=logUtils.UserGroupEnforcingHandler +class=vdsm.logUtils.UserGroupEnforcingHandler When I copied svdsm.logger.conf.rpmnew over

Re: [ovirt-users] After upgrading to 4.1.4 unable to start VM or migrate them

2017-08-01 Thread Doron Fediuck
Yes, none is a valid policy assuming you don't need any special considerations when running a VM. If you could gather the relevant log entries and the error you see and open a new bug it'll help us track and fix the issue. Please specify exactly from which engine version you upgraded and into

Re: [ovirt-users] After upgrading to 4.1.4 unable to start VM or migrate them

2017-08-01 Thread Arman Khalatyan
Thank you for your response, I am looking now in to records of the menu "Scheduling Policy": there is an entry "none", is it suppose to be there?? Because when I selecting it then error occurs. On Tue, Aug 1, 2017 at 10:35 AM, Yanir Quinn wrote: > Thanks for the update, we

Re: [ovirt-users] After upgrading to 4.1.4 unable to start VM or migrate them

2017-08-01 Thread Jiri Belka
> Ok I found the ERROR: > After upgrade the schedule policy was "none", I dont know why it was moved to > none but to fix the problem I did following: > Edit Cluster->Scheduling Policy-> Select Policy: vm_evently_distributed > Now I can run/migrate the VMs. > > I think there should be a some bug

Re: [ovirt-users] Yum error while installing host on Centos7

2017-08-01 Thread Yanir Quinn
where did you manually install the packages ? engine or host machine ? you can you provide the engine.log to see what might cause the error on the engine's side. maybe rollback the last yum transaction you did and try to run the engine again. as far as for the host installation you might need to

Re: [ovirt-users] supervdsmd IOError to /dev/stdout

2017-08-01 Thread Yaniv Bronheim
Hi, Seems like I already bumped in such issue awhile ago - https://bugzilla.redhat.com/show_bug.cgi?id=1216880 but now I see what's wrong - it happens after failing to read /etc/vdsm/svdsm.logger.conf for some reason then we have a bug in our fallback which tries to run

Re: [ovirt-users] After upgrading to 4.1.4 unable to start VM or migrate them

2017-08-01 Thread Yanir Quinn
Thanks for the update, we will check if there is a bug in the upgrade process On Mon, Jul 31, 2017 at 6:32 PM, Arman Khalatyan wrote: > Ok I found the ERROR: > After upgrade the schedule policy was "none", I dont know why it was moved > to none but to fix the problem I did