date:20170523

[ovirt-users] Disk image upload

2017-05-23 Thread Anantha Raghava


Hi,

I am trying to upload a Disk image using Web Admin UI. It is pausing the 
process and throwing up this error.


"Unable to upload image to disk 3e71c278-e03b-40e5-afaa-a13bed115229 due 
to a network error. Make sure ovirt-imageio-proxy service is installed 
and configured, and ovirt-engine's certificate is registered as a valid 
CA in the browser. The certificate can be fetched from 
https:///ovirt-engine/services/pki-resource?resource=ca-certificate=X509-PEM-CA


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

Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4

2017-05-23 Thread support

I downgraded the jdbc to 9.2.1002 and it's working again.  Thank you for your 
help!

The full setup is as such in case it helps anyone in the future:

OS: CentOS 7.3.1611

Backend: Ceph via Cinder

oVirt: 4.0.6.3

Postgres is remote and 9.5.7 on client and server

Postgres jdbc: 9.2.1002

Logan

> 
> On May 23, 2017 at 4:15 PM Yedidyah Bar David  wrote:
> 
> On Wed, May 24, 2017 at 12:06 AM,  wrote:
> 
> > > 
> > Wow, that looks almost exactly like what we're seeing.
> > 
> > Unfortunately, downgrading from postgresql-jdbc-42.1.1 to 42.0.0, 
> > restarting ovirt-engine and rerunning engine-setup produces the same error 
> > messages.
> > 
> > > 
> Please try 9.2. Thanks!
> 
> > > 
> > Logan
> > 
> > > > > 
> > > On May 23, 2017 at 3:39 PM Yedidyah Bar David 
> > >  wrote:
> > > 
> > > On Tue, May 23, 2017 at 11:19 PM, Logan Kuhn 
> > >  wrote:
> > > 
> > > > > > > 
> > > > Hi
> > > > 
> > > > We recently upgraded from postgres 9.5.4 to 9.5.6 and 
> > > > then to 9.5.7. We
> > > > restarted ovirt-engine between 9.5.4 and it worked as 
> > > > expected. After we
> > > > updated to 9.5.7 we have started to get postgres errors 
> > > > in engine.log and a
> > > > 404 error in the browser when we try to start 
> > > > ovirt-engine.
> > > > 
> > > > Updates were done on client and server to keep them in 
> > > > sync.
> > > > 
> > > > The error is complaining about a missing function, but 
> > > > we can verify that
> > > > the function exists in the database. We've also 
> > > > restored engine and
> > > > ovirt_engine_history from a backup at 8am this morning 
> > > > when it was working
> > > > and before we upgraded to 9.5.7 with no apparent help 
> > > > and run engine-setup
> > > > afterwards, still no luck.
> > > > 
> > > > 2017-05-23 15:07:48,418 INFO 
> > > > [org.ovirt.engine.core.dal.dbbroker.DbFacade]
> > > > (ServerService Thread Pool -- 51) [] Initializing the 
> > > > DbFacade
> > > > 2017-05-23 15:07:48,480 INFO 
> > > > [org.ovirt.engine.core.bll.Backend]
> > > > (ServerService Thread Pool -- 51) [] Start initializing 
> > > > Backend
> > > > 2017-05-23 15:07:48,502 ERROR
> > > > 
> > > > [org.ovirt.engine.core.bll.network.macpool.MacPoolPerDc] (ServerService
> > > > Thread Pool -- 46) [] Error initializing: 
> > > > PreparedStatementCallback; bad SQL
> > > > grammar [select * from 
> > > > getallmacpoolrangesbymacpoolid()]; nested exception
> > > > is org.postgresql.util.PSQL
> > > > Exception: ERROR: function 
> > > > getallmacpoolrangesbymacpoolid() does not exist
> > > > Hint: No function matches the given name and argument 
> > > > types. You might need
> > > > to add explicit type casts.
> > > > Position: 16
> > > > 2017-05-23 15:07:48,517 ERROR 
> > > > [org.ovirt.engine.core.bll.Backend]
> > > > (ServerService Thread Pool -- 51) [] Error during 
> > > > initialization:
> > > > org.jboss.weld.exceptions.WeldException: WELD-49: 
> > > > Unable to invoke
> > > > public void
> > > > 
> > > > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost.cre
> > > > ate() on
> > > > 
> > > > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost@3a35f461
> > > > at
> > > > 
> > > > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100)
> > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> > > > at
> > > > 
> > > > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81)
> > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> > > > at
> > > > 
> > > > org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126)
> > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> > > > at 
> > > > org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162)
> > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> > > > at
> > > > 
> > > > org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
> > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> > > > at
> > > > 
> > > >

Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4

2017-05-23 Thread support

Wow, that looks almost exactly like what we're seeing.

Unfortunately, downgrading from postgresql-jdbc-42.1.1 to 42.0.0, restarting 
ovirt-engine and rerunning engine-setup produces the same error messages.

Logan

> On May 23, 2017 at 3:39 PM Yedidyah Bar David  wrote:
> 
> 
> On Tue, May 23, 2017 at 11:19 PM, Logan Kuhn  
> wrote:
> > Hi
> >
> > We recently upgraded from postgres 9.5.4 to 9.5.6 and then to 9.5.7.  We
> > restarted ovirt-engine between 9.5.4 and it worked as expected.  After we
> > updated to 9.5.7 we have started to get postgres errors in engine.log and a
> > 404 error in the browser when we try to start ovirt-engine.
> >
> > Updates were done on client and server to keep them in sync.
> >
> > The error is complaining about a missing function, but we can verify that
> > the function exists in the database.  We've also restored engine and
> > ovirt_engine_history from a backup at 8am this morning when it was working
> > and before we upgraded to 9.5.7 with no apparent help and run engine-setup
> > afterwards, still no luck.
> >
> > 2017-05-23 15:07:48,418 INFO  [org.ovirt.engine.core.dal.dbbroker.DbFacade]
> > (ServerService Thread Pool -- 51) [] Initializing the DbFacade
> > 2017-05-23 15:07:48,480 INFO  [org.ovirt.engine.core.bll.Backend]
> > (ServerService Thread Pool -- 51) [] Start initializing Backend
> > 2017-05-23 15:07:48,502 ERROR
> > [org.ovirt.engine.core.bll.network.macpool.MacPoolPerDc] (ServerService
> > Thread Pool -- 46) [] Error initializing: PreparedStatementCallback; bad SQL
> > grammar [select * from  getallmacpoolrangesbymacpoolid()]; nested exception
> > is org.postgresql.util.PSQL
> > Exception: ERROR: function getallmacpoolrangesbymacpoolid() does not exist
> >  Hint: No function matches the given name and argument types. You might need
> > to add explicit type casts.
> >  Position: 16
> > 2017-05-23 15:07:48,517 ERROR [org.ovirt.engine.core.bll.Backend]
> > (ServerService Thread Pool -- 51) [] Error during initialization:
> > org.jboss.weld.exceptions.WeldException: WELD-49: Unable to invoke
> > public void
> > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost.cre
> > ate() on
> > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost@3a35f461
> >at
> > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.bean.builtin.InstanceImpl.getBeanInstance(InstanceImpl.java:189)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:100)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at org.ovirt.engine.core.bll.Backend.loadService(Backend.java:301)
> > [bll.jar:]
> >at org.ovirt.engine.core.bll.Backend.initialize(Backend.java:212)
> > [bll.jar:]
> >at org.ovirt.engine.core.bll.Backend.create(Backend.java:159)
> > [bll.jar:]
> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > [rt.jar:1.8.0_131]
> >at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > [rt.jar:1.8.0_131]
> >at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > [rt.jar:1.8.0_131]
> >at java.lang.reflect.Method.invoke(Method.java:498)
> > [rt.jar:1.8.0_131]
> >at
> > org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:96)
> >at
> >

Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4

2017-05-23 Thread Yedidyah Bar David

On Tue, May 23, 2017 at 11:19 PM, Logan Kuhn  wrote:
> Hi
>
> We recently upgraded from postgres 9.5.4 to 9.5.6 and then to 9.5.7.  We
> restarted ovirt-engine between 9.5.4 and it worked as expected.  After we
> updated to 9.5.7 we have started to get postgres errors in engine.log and a
> 404 error in the browser when we try to start ovirt-engine.
>
> Updates were done on client and server to keep them in sync.
>
> The error is complaining about a missing function, but we can verify that
> the function exists in the database.  We've also restored engine and
> ovirt_engine_history from a backup at 8am this morning when it was working
> and before we upgraded to 9.5.7 with no apparent help and run engine-setup
> afterwards, still no luck.
>
> 2017-05-23 15:07:48,418 INFO  [org.ovirt.engine.core.dal.dbbroker.DbFacade]
> (ServerService Thread Pool -- 51) [] Initializing the DbFacade
> 2017-05-23 15:07:48,480 INFO  [org.ovirt.engine.core.bll.Backend]
> (ServerService Thread Pool -- 51) [] Start initializing Backend
> 2017-05-23 15:07:48,502 ERROR
> [org.ovirt.engine.core.bll.network.macpool.MacPoolPerDc] (ServerService
> Thread Pool -- 46) [] Error initializing: PreparedStatementCallback; bad SQL
> grammar [select * from  getallmacpoolrangesbymacpoolid()]; nested exception
> is org.postgresql.util.PSQL
> Exception: ERROR: function getallmacpoolrangesbymacpoolid() does not exist
>  Hint: No function matches the given name and argument types. You might need
> to add explicit type casts.
>  Position: 16
> 2017-05-23 15:07:48,517 ERROR [org.ovirt.engine.core.bll.Backend]
> (ServerService Thread Pool -- 51) [] Error during initialization:
> org.jboss.weld.exceptions.WeldException: WELD-49: Unable to invoke
> public void
> org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost.cre
> ate() on
> org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost@3a35f461
>at
> org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100)
> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
>at
> org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81)
> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
>at
> org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126)
> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
>at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162)
> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
>at
> org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
>at
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)
> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
>at
> org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141)
> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
>at
> org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
>at
> org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742)
> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
>at
> org.jboss.weld.bean.builtin.InstanceImpl.getBeanInstance(InstanceImpl.java:189)
> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
>at
> org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:100)
> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
>at org.ovirt.engine.core.bll.Backend.loadService(Backend.java:301)
> [bll.jar:]
>at org.ovirt.engine.core.bll.Backend.initialize(Backend.java:212)
> [bll.jar:]
>at org.ovirt.engine.core.bll.Backend.create(Backend.java:159)
> [bll.jar:]
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [rt.jar:1.8.0_131]
>at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [rt.jar:1.8.0_131]
>at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [rt.jar:1.8.0_131]
>at java.lang.reflect.Method.invoke(Method.java:498)
> [rt.jar:1.8.0_131]
>at
> org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:96)
>at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
>at
> org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
>at
> org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:70)
> [wildfly-weld-10.1.0.Final.jar:10.1.0.Final]
>at
> org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doLifecycleInterception(Jsr299BindingsInterceptor.java:117)
> [wildfly-weld-10.1.0.Final.jar:10.1.0.Final]
>at
>

Re: [ovirt-users] Info on host not responding event and related actions

2017-05-23 Thread Piotr Kliczewski

+Marin to answer fencing configuration settings

On Tue, May 23, 2017 at 3:03 PM, Gianluca Cecchi
 wrote:
> Hello,
> I have an oVirt 4.1.1 environment with:
>
> - engine is a vSphere CentOS 7.3 VM with its nic on say vlan1
> - 2 x hosts (CentOS 7.3) with their ovirtmgmt lan on a bonding
> (active-backup) on say vlan2
>
> network architecture layout is to put hypervisors and mgmt servers in
> different vlans
>
> Today we had these 4 events below shown in our engine, with root cause
> apparently a maintenance network routing activity (it should have been
> transparent, network guys told..., but this is another story ;-)
> No alert message inside VMs
>
> 4) May 23, 2017 1:43:58 PM Host ov300 power management was verified
> successfully.
> 3) May 23, 2017 1:43:58 PM Status of host ov300 was set to Up.
> 2) May 23, 2017 1:43:55 PM Executing power management status on Host ov300
> using Proxy Host ov301 and Fence Agent ipmilan:10.10.193.103.
> 1) May 23, 2017 1:43:37 PM Host ov300 is not responding. It will stay in
> Connecting state for a grace period of 61 seconds and after that an attempt
> to fence the host will be issued.

Can you check in the logs what caused the host to become not responding?

>
> Can anyone tell exactly the meaning of the different lines?
> Is the 1) detected because the engine, from only a network point of view,
> was not able to ping/reach the hostname of the host ov300, or the "not
> responding" is any particular specific check?
> Is the "61 seconds" delay tunable?
> Is 2) an additional check to verify status of ov300?
> In case of failure of test in 2) would the fencing have been immediate or
> the delay described in 1) would have taken place?
> Are 3) and 4) messages independent from the engine being able to reach ov300
> or the 61 seconds delay would have been true anyway?
>
> Hope I have explained my doubts related to events that could determine a
> potential fencing of an active node with its running VMs... with the "only"
> temporary problem of connectivity between the engine and one of the nodes...
>
> Thanks in advance,
> Gianluca
>
> ___
> 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] migration of a VM: fails

2017-05-23 Thread cmc

Hi Michal,

>
> is it from older host to newr host or vice versa?

They are now on the same version, and I still have some troubles
migrating hosts, but not consistently

> can you downgrade the new one to the same version and try again?

I've upgraded both now. I'll await Francesco's reply after the latest
tests, but as it happens after updating both hosts, I'm guessing it is
not specific to the older version

Thanks,

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

Re: [ovirt-users] migration of a VM: fails

2017-05-23 Thread cmc

Hi Francesco,

>
> do you always have the same error?

Yes

> Are you by any chance using the post copy migration mode?

Not sure what that is. The migration is initiated by either putting
the host in maintenance, or selecting 'upgrade' from the menu.

> Could you please share the libvirt debug logs, at least on the source side?
>
> https://wiki.libvirt.org/page/DebugLogs
>
> You may want to do a test run with the debug logs turned on and disable them
> just after, those are VERY verbose.
>

Before I put it into debug mode, I'd tried to migrate the troublesome
VM by itself, and it worked. So I then thought I try putting the host
that has that VM into maintenance, and it successfully copied that VM
over, but failed on another VM this time (a Linux VM). I took the host
out of maintenance, and switched on debug mode (restarting libvirtd
made the host rather unhappy, but it sorted itself out), and then
tried putting the host back into maintenance. It complained about
another VM failing to be migrated, though I couldn't see that VM on
the host. It did succeed in moving the VM that was causing it
problems, and is now in maintenance mode. So it seems a bit hit and
miss. Do you still want the logs?

Thanks,

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

Re: [ovirt-users] Snapshot Image ID

2017-05-23 Thread Marcelo Leandro

I see now that image base id stay in snapshot the before of the last. I
think that should stay in the last. correct?

Thanks,
Marcelo Leandro

2017-05-23 11:16 GMT-03:00 Marcelo Leandro :

> Good morning,
> I have a problem with snapshot, my last snapshot that should have the
> image base ID not contain this reference in sub-tab in the dashboard.
> how can see in the picture attached.
> I think that is necessary add this reference in the database again. The
> image exist in the storage and it is used for VM execution, but i think
> when I shutdown the VM it not start anymore.
>
> someone help me?
>
> Thanks,
> Marcelo Leandro
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Snapshot Image ID

2017-05-23 Thread Marcelo Leandro

Good morning,
I have a problem with snapshot, my last snapshot that should have the image
base ID not contain this reference in sub-tab in the dashboard.
how can see in the picture attached.
I think that is necessary add this reference in the database again. The
image exist in the storage and it is used for VM execution, but i think
when I shutdown the VM it not start anymore.

someone help me?

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

Re: [ovirt-users] Error when taking snapshot on gluster SD

2017-05-23 Thread Sahina Bose

Engine.log only indicated a timeout. Could you check the vdsm.log and the
gluster mount logs if there are any errors related to snapshot creation?

On Tue, May 23, 2017 at 6:47 PM, Sven Achtelik <sven.achte...@eps.aero>
wrote:

> Hi All,
>
>
>
> I was taking a snapshot from a gluster based SD and got this errors:
>
>
>
> [root@ovirt-engine ovirt-engine]# zgrep -e 
> 3102e526-172b-49a7-ae64-5879a7eb8079
> engine.log-*
>
> engine.log-20170523.gz:2017-05-23 01:54:13,223-05 INFO
> [org.ovirt.engine.core.bll.snapshots.CreateAllSnapshotsFromVmCommand]
> (default task-18) [3102e526-172b-49a7-ae64-5879a7eb8079] Lock Acquired to
> object 'EngineLock:{exclusiveLocks='[4eeaa622-17f9-4586-b99a-cddb3ad942de=<VM,
> ACTION_TYPE_FAILED_SNAPSHOT_IS_BEING_TAKEN_FOR_VM$VmName wc_app01>]',
> sharedLocks='null'}'
>
>
>
> engine.log-20170523.gz:2017-05-23 01:54:13,247-05 INFO
> [org.ovirt.engine.core.bll.memory.MemoryStorageHandler] (default task-18)
> [3102e526-172b-49a7-ae64-5879a7eb8079] The memory volumes of VM (name
> 'wc_app01', id '4eeaa622-17f9-4586-b99a-cddb3ad942de') will be stored in
> storage domain (name 'data', id '185718c7-1da9-442c-bedc-776e4ac95c33')
>
>
>
> engine.log-20170523.gz:2017-05-23 01:54:13,295-05 INFO
> [org.ovirt.engine.core.bll.snapshots.CreateAllSnapshotsFromVmCommand]
> (default task-18) [3102e526-172b-49a7-ae64-5879a7eb8079] Running command:
> CreateAllSnapshotsFromVmCommand internal: false. Entities affected :  ID:
> 4eeaa622-17f9-4586-b99a-cddb3ad942de Type: VMAction group
> MANIPULATE_VM_SNAPSHOTS with role type USER
>
>
>
> engine.log-20170523.gz:2017-05-23 01:54:17,717-05 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (default task-18) [2ff883d4] EVENT_ID: USER_CREATE_SNAPSHOT(45),
> Correlation ID: 3102e526-172b-49a7-ae64-5879a7eb8079, Job ID:
> 020b9b14-16d9-4303-8fa3-d60b248bc158, Call Stack: null, Custom Event ID:
> -1, Message: Snapshot 'Sesam_SC20170523015128500@5aH9YZNk4-A' creation
> for VM 'wc_app01' was initiated by sven@asl.local@asl.local-authz.
>
>
>
> engine.log-20170523.gz:2017-05-23 01:57:27,103-05 WARN
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (DefaultQuartzScheduler1) [1b15b09b] EVENT_ID: 
> USER_CREATE_LIVE_SNAPSHOT_FINISHED_FAILURE(170),
> Correlation ID: 3102e526-172b-49a7-ae64-5879a7eb8079, Job ID:
> 020b9b14-16d9-4303-8fa3-d60b248bc158, Call Stack:
> org.ovirt.engine.core.common.errors.EngineException: EngineException:
> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
> VDSGenericException: VDSNetworkException: Message timeout which can be
> caused by communication issues (Failed with error VDS_NETWORK_ERROR and
> code 5022)
>
>
>
> engine.log-20170523.gz:2017-05-23 01:58:11,969-05 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (DefaultQuartzScheduler1) [] EVENT_ID: 
> USER_CREATE_SNAPSHOT_FINISHED_FAILURE(69),
> Correlation ID: 3102e526-172b-49a7-ae64-5879a7eb8079, Job ID:
> 020b9b14-16d9-4303-8fa3-d60b248bc158, Call Stack:
> org.ovirt.engine.core.common.errors.EngineException: EngineException:
> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
> VDSGenericException: VDSNetworkException: Message timeout which can be
> caused by communication issues (Failed with error VDS_NETWORK_ERROR and
> code 5022)
>
>
>
> [root@ovirt-engine ovirt-engine]# zgrep -e  
> 020b9b14-16d9-4303-8fa3-d60b248bc158
> engine.log-*
>
> engine.log-20170523.gz:2017-05-23 01:54:17,717-05 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (default task-18) [2ff883d4] EVENT_ID: USER_CREATE_SNAPSHOT(45),
> Correlation ID: 3102e526-172b-49a7-ae64-5879a7eb8079, Job ID:
> 020b9b14-16d9-4303-8fa3-d60b248bc158, Call Stack: null, Custom Event ID:
> -1, Message: Snapshot 'Sesam_SC20170523015128500@5aH9YZNk4-A' creation
> for VM 'wc_app01' was initiated by sven@asl.local@asl.local-authz.
>
>
>
> engine.log-20170523.gz:2017-05-23 01:57:27,103-05 WARN
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (DefaultQuartzScheduler1) [1b15b09b] EVENT_ID: 
> USER_CREATE_LIVE_SNAPSHOT_FINISHED_FAILURE(170),
> Correlation ID: 3102e526-172b-49a7-ae64-5879a7eb8079, Job ID:
> 020b9b14-16d9-4303-8fa3-d60b248bc158, Call Stack:
> org.ovirt.engine.core.common.errors.EngineException: EngineException:
> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
> VDSGenericException: VDSNetworkException: Message timeout which can be
> caused by communication issues (Failed with error VDS_NETWORK_ERROR and
> code 5022)
>
>
>
> engine.log-20170523.gz:2017-05-23 01:58:11,969-05 ERROR
> [org.ovirt.eng

[ovirt-users] Error when taking snapshot on gluster SD

2017-05-23 Thread Sven Achtelik

Hi All,

I was taking a snapshot from a gluster based SD and got this errors:

[root@ovirt-engine ovirt-engine]# zgrep -e 3102e526-172b-49a7-ae64-5879a7eb8079 
engine.log-*
engine.log-20170523.gz:2017-05-23 01:54:13,223-05 INFO  
[org.ovirt.engine.core.bll.snapshots.CreateAllSnapshotsFromVmCommand] (default 
task-18) [3102e526-172b-49a7-ae64-5879a7eb8079] Lock Acquired to object 
'EngineLock:{exclusiveLocks='[4eeaa622-17f9-4586-b99a-cddb3ad942de=<VM, 
ACTION_TYPE_FAILED_SNAPSHOT_IS_BEING_TAKEN_FOR_VM$VmName wc_app01>]', 
sharedLocks='null'}'

engine.log-20170523.gz:2017-05-23 01:54:13,247-05 INFO  
[org.ovirt.engine.core.bll.memory.MemoryStorageHandler] (default task-18) 
[3102e526-172b-49a7-ae64-5879a7eb8079] The memory volumes of VM (name 
'wc_app01', id '4eeaa622-17f9-4586-b99a-cddb3ad942de') will be stored in 
storage domain (name 'data', id '185718c7-1da9-442c-bedc-776e4ac95c33')

engine.log-20170523.gz:2017-05-23 01:54:13,295-05 INFO  
[org.ovirt.engine.core.bll.snapshots.CreateAllSnapshotsFromVmCommand] (default 
task-18) [3102e526-172b-49a7-ae64-5879a7eb8079] Running command: 
CreateAllSnapshotsFromVmCommand internal: false. Entities affected :  ID: 
4eeaa622-17f9-4586-b99a-cddb3ad942de Type: VMAction group 
MANIPULATE_VM_SNAPSHOTS with role type USER

engine.log-20170523.gz:2017-05-23 01:54:17,717-05 INFO  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default 
task-18) [2ff883d4] EVENT_ID: USER_CREATE_SNAPSHOT(45), Correlation ID: 
3102e526-172b-49a7-ae64-5879a7eb8079, Job ID: 
020b9b14-16d9-4303-8fa3-d60b248bc158, Call Stack: null, Custom Event ID: -1, 
Message: Snapshot 'Sesam_SC20170523015128500@5aH9YZNk4-A' creation for VM 
'wc_app01' was initiated by 
sven@asl.local@asl.local-authz<mailto:sven@asl.local@asl.local-authz>.

engine.log-20170523.gz:2017-05-23 01:57:27,103-05 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [1b15b09b] EVENT_ID: 
USER_CREATE_LIVE_SNAPSHOT_FINISHED_FAILURE(170), Correlation ID: 
3102e526-172b-49a7-ae64-5879a7eb8079, Job ID: 
020b9b14-16d9-4303-8fa3-d60b248bc158, Call Stack: 
org.ovirt.engine.core.common.errors.EngineException: EngineException: 
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: 
VDSGenericException: VDSNetworkException: Message timeout which can be caused 
by communication issues (Failed with error VDS_NETWORK_ERROR and code 5022)

engine.log-20170523.gz:2017-05-23 01:58:11,969-05 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [] EVENT_ID: 
USER_CREATE_SNAPSHOT_FINISHED_FAILURE(69), Correlation ID: 
3102e526-172b-49a7-ae64-5879a7eb8079, Job ID: 
020b9b14-16d9-4303-8fa3-d60b248bc158, Call Stack: 
org.ovirt.engine.core.common.errors.EngineException: EngineException: 
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: 
VDSGenericException: VDSNetworkException: Message timeout which can be caused 
by communication issues (Failed with error VDS_NETWORK_ERROR and code 5022)

[root@ovirt-engine ovirt-engine]# zgrep -e  
020b9b14-16d9-4303-8fa3-d60b248bc158 engine.log-*
engine.log-20170523.gz:2017-05-23 01:54:17,717-05 INFO  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default 
task-18) [2ff883d4] EVENT_ID: USER_CREATE_SNAPSHOT(45), Correlation ID: 
3102e526-172b-49a7-ae64-5879a7eb8079, Job ID: 
020b9b14-16d9-4303-8fa3-d60b248bc158, Call Stack: null, Custom Event ID: -1, 
Message: Snapshot 'Sesam_SC20170523015128500@5aH9YZNk4-A' creation for VM 
'wc_app01' was initiated by 
sven@asl.local@asl.local-authz<mailto:sven@asl.local@asl.local-authz>.

engine.log-20170523.gz:2017-05-23 01:57:27,103-05 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [1b15b09b] EVENT_ID: 
USER_CREATE_LIVE_SNAPSHOT_FINISHED_FAILURE(170), Correlation ID: 
3102e526-172b-49a7-ae64-5879a7eb8079, Job ID: 
020b9b14-16d9-4303-8fa3-d60b248bc158, Call Stack: 
org.ovirt.engine.core.common.errors.EngineException: EngineException: 
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: 
VDSGenericException: VDSNetworkException: Message timeout which can be caused 
by communication issues (Failed with error VDS_NETWORK_ERROR and code 5022)

engine.log-20170523.gz:2017-05-23 01:58:11,969-05 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [] EVENT_ID: 
USER_CREATE_SNAPSHOT_FINISHED_FAILURE(69), Correlation ID: 
3102e526-172b-49a7-ae64-5879a7eb8079, Job ID: 
020b9b14-16d9-4303-8fa3-d60b248bc158, Call Stack: 
org.ovirt.engine.core.common.errors.EngineException: EngineException: 
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: 
VDSGenericException: VDSNetworkException: Message timeout which can be caused 
by communication issues (Failed with error VDS_NETWORK_ERROR and code 5022)

I would be great if someone could guide me to the next files to look at to fi

[ovirt-users] Info on host not responding event and related actions

2017-05-23 Thread Gianluca Cecchi

Hello,
I have an oVirt 4.1.1 environment with:

- engine is a vSphere CentOS 7.3 VM with its nic on say vlan1
- 2 x hosts (CentOS 7.3) with their ovirtmgmt lan on a bonding
(active-backup) on say vlan2

network architecture layout is to put hypervisors and mgmt servers in
different vlans

Today we had these 4 events below shown in our engine, with root cause
apparently a maintenance network routing activity (it should have been
transparent, network guys told..., but this is another story ;-)
No alert message inside VMs

4) May 23, 2017 1:43:58 PM Host ov300 power management was verified
successfully.
3) May 23, 2017 1:43:58 PM Status of host ov300 was set to Up.
2) May 23, 2017 1:43:55 PM Executing power management status on Host ov300
using Proxy Host ov301 and Fence Agent ipmilan:10.10.193.103.
1) May 23, 2017 1:43:37 PM Host ov300 is not responding. It will stay in
Connecting state for a grace period of 61 seconds and after that an attempt
to fence the host will be issued.

Can anyone tell exactly the meaning of the different lines?
Is the 1) detected because the engine, from only a network point of view,
was not able to ping/reach the hostname of the host ov300, or the "not
responding" is any particular specific check?
Is the "61 seconds" delay tunable?
Is 2) an additional check to verify status of ov300?
In case of failure of test in 2) would the fencing have been immediate or
the delay described in 1) would have taken place?
Are 3) and 4) messages independent from the engine being able to reach
ov300 or the 61 seconds delay would have been true anyway?

Hope I have explained my doubts related to events that could determine a
potential fencing of an active node with its running VMs... with the "only"
temporary problem of connectivity between the engine and one of the nodes...

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

Re: [ovirt-users] Building ovirt-engine fails due to failing estCanReadFile(org.ovirt.engine.core.utils.servlet.ServletUtilsTest): We should not be able to read this file.

2017-05-23 Thread Yedidyah Bar David

On Tue, May 23, 2017 at 12:16 PM, Leni Kadali Mutungi
 wrote:
> On 5/23/17, Yedidyah Bar David  wrote:
>> On Tue, May 23, 2017 at 6:21 AM, Leni Kadali Mutungi
>>  wrote:
>>> Tried to build ovirt-engine on my computer using the command `make
>>> clean install-dev`, on Debian Testing.
>>>
>>> The full output of the error is as follows:
>>> https://paste.fedoraproject.org/paste/F6p~LVdNtFlpzQijMbSIYV5M1UNdIGYhyRLivL9gydE=
>>
>> Did you search the code for relevant parts of the error message?
>> Searching for 'We should not be able to read this file' finds it in
>> backend/manager/modules/utils/src/test/java/org/ovirt/engine/core/utils/servlet/ServletUtilsTest.java
>> twice - once when trying to read '/doesnotexist/iamprettysure', and
>> the other when trying to read '/etc/securetty'.
> I did not think to look for the file. Will remember this in future.
>
>> The latter file is 0600 on Fedora, RHEL and derivatives. I guess it's
>> readable for your user on your system, which might not be a good idea
>> in itself - but that's a different discussion.
>>
>> Some options for how to continue:
>>
>> 1. Submit a patch for the engine to change this test to test for some
>> other file that is more likely to be unreadable, e.g. /etc/shadow.
>>
>> 2. Locally set it on your system to be unreadable to you.
>>
>> 3. Assuming it's Debian's default, ask on Debian lists/forums to
>> change it to be non-world-readable and/or why it's not like that
>> already.
>>
>> 4. Ignore unit tests for now, 'make BUILD_UT=0 install-dev'. Check
>> README.adoc for details.
> I am ccing the Deb Virtualization Team for this, in the hopes that
> they may have a different opinion, but when I asked in the #debian IRC
> channel on OFTC, I was told that the file is now presently read by
> pam_securetty so permissions of 0600 would be fine, though the person
> responding didn't see the use of making the permissions stricter than
> they already are (0644). Maybe you could elaborate on the importance
> of having this set to 0600?

I suggest to search the net etc. for more info on this. My intuitive
answer is that if a user can read the list of terminals that root can
login through, that user now has some useful information when trying
to break into the system, so better hide that if possible.

Fedora dropped this file altogether:

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

Which is another reason for going with (1.) above.

> Pending that I will go for option 4, and
> choose from options 1 to 3 when packaging for Debian.
>
>>> I modified the following variables in the Makefile to suit where the
>>> required files are:
>>>
>>> JS_DEPS_DIR=/home/user/ovirt-js-dependencies
>>> PYFLAKES=/usr/bin/pyflakes
>>> JBOSS_HOME=/home/user/wildfly-11.0.0.Alpha1
>>> WILDFLY_OVERLAY_MODULES=/home/user/wildfly-11.0.0.Alpha1/modules
>>>
>>> I have pep8 but was unable to know how to correctly reference it in
>>> the Makefile, the syntax being:
>>>
>>> PEP8=pep8
>>
>> This should probably be ok, unless your version of pep8 is too old/
>> too new/has different defaults than what we use in CI (which is the
>> "common denominator").
>>
>> Good luck,
>>
>>>
>>> Advice on this would be welcome.
>>>
>>>
>>> --
>>> - Warm regards
>>> Leni Kadali Mutungi
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>
>> --
>> Didi
>
>
> --
> - Warm regards
> Leni Kadali Mutungi



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

Re: [ovirt-users] Building ovirt-engine fails due to failing estCanReadFile(org.ovirt.engine.core.utils.servlet.ServletUtilsTest): We should not be able to read this file.

2017-05-23 Thread Leni Kadali Mutungi

On 5/23/17, Yedidyah Bar David  wrote:
> On Tue, May 23, 2017 at 6:21 AM, Leni Kadali Mutungi
>  wrote:
>> Tried to build ovirt-engine on my computer using the command `make
>> clean install-dev`, on Debian Testing.
>>
>> The full output of the error is as follows:
>> https://paste.fedoraproject.org/paste/F6p~LVdNtFlpzQijMbSIYV5M1UNdIGYhyRLivL9gydE=
>
> Did you search the code for relevant parts of the error message?
> Searching for 'We should not be able to read this file' finds it in
> backend/manager/modules/utils/src/test/java/org/ovirt/engine/core/utils/servlet/ServletUtilsTest.java
> twice - once when trying to read '/doesnotexist/iamprettysure', and
> the other when trying to read '/etc/securetty'.
I did not think to look for the file. Will remember this in future.

> The latter file is 0600 on Fedora, RHEL and derivatives. I guess it's
> readable for your user on your system, which might not be a good idea
> in itself - but that's a different discussion.
>
> Some options for how to continue:
>
> 1. Submit a patch for the engine to change this test to test for some
> other file that is more likely to be unreadable, e.g. /etc/shadow.
>
> 2. Locally set it on your system to be unreadable to you.
>
> 3. Assuming it's Debian's default, ask on Debian lists/forums to
> change it to be non-world-readable and/or why it's not like that
> already.
>
> 4. Ignore unit tests for now, 'make BUILD_UT=0 install-dev'. Check
> README.adoc for details.
I am ccing the Deb Virtualization Team for this, in the hopes that
they may have a different opinion, but when I asked in the #debian IRC
channel on OFTC, I was told that the file is now presently read by
pam_securetty so permissions of 0600 would be fine, though the person
responding didn't see the use of making the permissions stricter than
they already are (0644). Maybe you could elaborate on the importance
of having this set to 0600? Pending that I will go for option 4, and
choose from options 1 to 3 when packaging for Debian.

>> I modified the following variables in the Makefile to suit where the
>> required files are:
>>
>> JS_DEPS_DIR=/home/user/ovirt-js-dependencies
>> PYFLAKES=/usr/bin/pyflakes
>> JBOSS_HOME=/home/user/wildfly-11.0.0.Alpha1
>> WILDFLY_OVERLAY_MODULES=/home/user/wildfly-11.0.0.Alpha1/modules
>>
>> I have pep8 but was unable to know how to correctly reference it in
>> the Makefile, the syntax being:
>>
>> PEP8=pep8
>
> This should probably be ok, unless your version of pep8 is too old/
> too new/has different defaults than what we use in CI (which is the
> "common denominator").
>
> Good luck,
>
>>
>> Advice on this would be welcome.
>>
>>
>> --
>> - Warm regards
>> Leni Kadali Mutungi
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
> --
> Didi


-- 
- Warm regards
Leni Kadali Mutungi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] upload image

2017-05-23 Thread qinglong.d...@horebdata.cn

It worked. Thanks a lot!

From: Daniel Erez
Date: 2017-05-22 20:24
To: qinglong.d...@horebdata.cn; Niyazi Elvan
CC: users
Subject: Re: [ovirt-users] upload image
The oVirt's CA certificate can be fetched from 
http:///ovirt-engine/services/pki-resource?resource=ca-certificate=X509-PEM-CA

(more details in 'SSL installation' section at: 
https://github.com/oVirt/ovirt-imageio/blob/master/proxy/README).

For importing the certificate to firefox, try the following instruction demo :
https://danielerez.github.io/slides-image-io/#/3/2

On Mon, May 22, 2017 at 10:56 AM qinglong.d...@horebdata.cn 
 wrote:
Thanks! But I don't know how to import CA to browser. I have tried to import 
the CA to my firefox browser, but I failed. Is there any documentations about 
that?

From: Niyazi Elvan
Date: 2017-05-19 15:54
To: qinglong.dong
CC: users
Subject: Re: [ovirt-users] upload image
Most probably it's ovirt engine CA certificate. You need to import it to your 
browser.

On May 19, 2017 6:36 AM, "qinglong.d...@horebdata.cn" 
 wrote:
Hi all,
I wanted to upload a qcow2 image using web UI. But I got an error:
 "Unable to upload image to disk a38f29f4-594a-438b-a8e0-6a85ac56055d due to a 
network error. Make sure ovirt-imageio-proxy service is installed and 
configured, and ovirt-engine's certificate is registered as a valid CA in the 
browser."
The ovirt-imageio-proxy service had been installed when I excuted 
"engine-setup". What shoud I do about ovirt-imageio-proxy or CA? Hope someone 
can help, thanks!

___
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

[ovirt-users] [ANN] oVirt 4.1.2 Release is now available

2017-05-23 Thread Sandro Bonazzola

The oVirt Project is pleased to announce the availability of the oVirt
4.1.2 Release, as of May 23rd, 2017

This update is the second in a series of stabilization updates to the 4.1
series.
4.1.2 brings 24 enhancements and 230 bugfixes, including 101 high or urgent
severity fixes, on top of oVirt 4.1 series

This release is available now for:
* Fedora 24 (tech preview)
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later
* oVirt Node 4.1
* Fedora 24 (tech preview)

See the release notes [3] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Live has been already built [4]
- oVirt Node will be available soon [4]

Additional Resources:
* Read more about the oVirt 4.1.2 release highlights:
http://www.ovirt.org/release/4.1.2/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] https://www.ovirt.org/community/
[2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
[3] http://www.ovirt.org/release/4.1.2/
[4] http://resources.ovirt.org/pub/ovirt-4.1/iso/


-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R

Red Hat EMEA 

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

Re: [ovirt-users] adding a nic with its network with ansible module

2017-05-23 Thread Ondra Machacek

Hi,

this was fixed by the this PR[1], but it didn't get to 2.3.
So if it's OK to you you can download the ovirt_nics module
from the devel branch and add it to your library path.

[1] https://github.com/ansible/ansible/pull/22684

On Mon, May 22, 2017 at 11:34 AM, Nathanaël Blanchet 
wrote:

> Hello,
>
> I'm used to easily add multiple network to vm with the following
> ovirt-shell command:
>
> add nic --parent-vm-name acier --network-name brv106 --name admin
>
> I try to do the same with ovirt_nics module (with ansible-console or with
> regular yml file)
>
> ovirt_nics vm=acier name=admin network=brv106 profile=brv106 state=present
>
> interface is successfully created but network is empty, as if network
> field were skipped.
>
> Thanks for your help
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14
> blanc...@abes.fr
>
> ___
> 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] Building ovirt-engine fails due to failing estCanReadFile(org.ovirt.engine.core.utils.servlet.ServletUtilsTest): We should not be able to read this file.

2017-05-23 Thread Yedidyah Bar David

On Tue, May 23, 2017 at 6:21 AM, Leni Kadali Mutungi
 wrote:
> Tried to build ovirt-engine on my computer using the command `make
> clean install-dev`, on Debian Testing.
>
> The full output of the error is as follows:
> https://paste.fedoraproject.org/paste/F6p~LVdNtFlpzQijMbSIYV5M1UNdIGYhyRLivL9gydE=

Did you search the code for relevant parts of the error message?
Searching for 'We should not be able to read this file' finds it in
backend/manager/modules/utils/src/test/java/org/ovirt/engine/core/utils/servlet/ServletUtilsTest.java
twice - once when trying to read '/doesnotexist/iamprettysure', and
the other when trying to read '/etc/securetty'.

The latter file is 0600 on Fedora, RHEL and derivatives. I guess it's
readable for your user on your system, which might not be a good idea
in itself - but that's a different discussion.

Some options for how to continue:

1. Submit a patch for the engine to change this test to test for some
other file that is more likely to be unreadable, e.g. /etc/shadow.

2. Locally set it on your system to be unreadable to you.

3. Assuming it's Debian's default, ask on Debian lists/forums to
change it to be non-world-readable and/or why it's not like that
already.

4. Ignore unit tests for now, 'make BUILD_UT=0 install-dev'. Check
README.adoc for details.

>
> I modified the following variables in the Makefile to suit where the
> required files are:
>
> JS_DEPS_DIR=/home/user/ovirt-js-dependencies
> PYFLAKES=/usr/bin/pyflakes
> JBOSS_HOME=/home/user/wildfly-11.0.0.Alpha1
> WILDFLY_OVERLAY_MODULES=/home/user/wildfly-11.0.0.Alpha1/modules
>
> I have pep8 but was unable to know how to correctly reference it in
> the Makefile, the syntax being:
>
> PEP8=pep8

This should probably be ok, unless your version of pep8 is too old/
too new/has different defaults than what we use in CI (which is the
"common denominator").

Good luck,

>
> Advice on this would be welcome.
>
>
> --
> - Warm regards
> Leni Kadali Mutungi
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

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

[ovirt-users] Disk image upload

Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4

Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4

Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4

Re: [ovirt-users] Info on host not responding event and related actions

Re: [ovirt-users] migration of a VM: fails

Re: [ovirt-users] migration of a VM: fails

Re: [ovirt-users] Snapshot Image ID

[ovirt-users] Snapshot Image ID

Re: [ovirt-users] Error when taking snapshot on gluster SD

[ovirt-users] Error when taking snapshot on gluster SD

[ovirt-users] Info on host not responding event and related actions

Re: [ovirt-users] Building ovirt-engine fails due to failing estCanReadFile(org.ovirt.engine.core.utils.servlet.ServletUtilsTest): We should not be able to read this file.

Re: [ovirt-users] Building ovirt-engine fails due to failing estCanReadFile(org.ovirt.engine.core.utils.servlet.ServletUtilsTest): We should not be able to read this file.

Re: [ovirt-users] upload image

[ovirt-users] [ANN] oVirt 4.1.2 Release is now available

Re: [ovirt-users] adding a nic with its network with ansible module

Re: [ovirt-users] Building ovirt-engine fails due to failing estCanReadFile(org.ovirt.engine.core.utils.servlet.ServletUtilsTest): We should not be able to read this file.

18 matches

Site Navigation

Mail list logo

Footer information