Re: [ovirt-users] ovirt 3.6.6 and gluster 3.7.13

[Frank Rothenstein]

As per my cluster the problem is on an higher level: you can't activate
the domains an FUSE, sanlock can't acquire the lock due to the
permission errors visible in brick log.
Am Donnerstag, den 21.07.2016, 19:17 + schrieb Scott:
> > You change the cache mode using a custom property per-VM I believe. 
I don't know if this would work for the hosted engine.
> > I've already downgraded my system, but once you have the test machine
up, perhaps you can try it.   The custom property would be:
> 
> viodiskcache=writethrough
> 
> or
> 
> viodiskcache=writeback
> 
> > > > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virt
ualization/3.6/html/Virtual_Machine_Management_Guide/appe-
Reference_Settings_in_Administration_Portal_and_User_Portal_Windows.h
tml#Virtual_Machine_Custom_Properties_settings_explained
> 
> Scott
>  
> > On Thu, Jul 21, 2016 at 12:53 PM David Gossage  wrote:
> > > > On Thu, Jul 21, 2016 at 11:47 AM, Scott  wrote:
> > > Hi David,
> > > My backend storage is ZFS.
> > > 
> > > > > > > > > > > > > > > I thought about moving from FUSE to NFS mounts 
> > > > > > > > > > > > > > > for my Gluster
volumes to help test.  But since I use hosted engine this would
be a real pain.  Its difficult to modify the storage domain
type/path in the hosted-engine.conf.  And I don't want to go
through the process of re-deploying hosted engine.
> > > 
> > > 
> > > 
> > 
> > 
> > 
> > I found this
> > https://bugzilla.redhat.com/show_bug.cgi?id=1347553
> > 
> > Not sure if related.
> > 
> > > > > > But I also have zfs backend, another user in gluster mailing list
had issues and used zfs backend although she used proxmox and got
it working by changing disk to writeback cache I think it was.
> > 
> > > > > > > > I also use hosted engine, but I run my gluster volume for HE
actually on a LVM separate from zfs on xfs and if i recall it did
not have the issues my gluster on zfs did.  I'm wondering now if
the issue was zfs settings.
> > 
> > > > Hopefully should have a test machone up soon I can play around with
more.
> > 
> > 
> > 
> > 
> > > Scott
> > > 
> > > 
> > > > > > On Thu, Jul 21, 2016 at 11:36 AM David Gossage  wrote:
> > > > What back end storage do you run gluster on?  xfs/zfs/ext4 etc?
> > > > 
> > > > David Gossage
> > > > 
> > > > 
> > > > Carousel Checks Inc. | System Administrator
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Office 708.613.2284
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > > > > > > > > > On Thu, Jul 21, 2016 at 8:18 AM, Scott 
> > > > > > > > > > > > 
wrote:
> > > > 
> > > > > > > > > > > > > > > I get similar problems with oVirt 4.0.1 and 
> > > > > > > > > > > > > > > hosted engine. 
After upgrading all my hosts to Gluster 3.7.13 (client and
server), I get the following:
> > > > > $ sudo hosted-engine --set-maintenance --mode=none
> > > > > Traceback (most recent call last):
> > > > > > > > > >   File "/usr/lib64/python2.7/runpy.py", line 162, in
_run_module_as_main
> > > > >     "__main__", fname, loader, pkg_name)
> > > > >   File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
> > > > >     exec code in run_globals
> > > > > > > > > > > > > > >   File "/usr/lib/python2.7/site-
packages/ovirt_hosted_engine_setup/set_maintenance.py", line
73, in 
> > > > >     if not maintenance.set_mode(sys.argv[1]):
> > > > > > > > > > > > > > >   File "/usr/lib/python2.7/site-
packages/ovirt_hosted_engine_setup/set_maintenance.py", line
61, in set_mode
> > > > >     value=m_global,
> > > > > > > > > > > > > > >   File "/usr/lib/python2.7/site-
packages/ovirt_hosted_engine_ha/client/client.py", line 259,
in set_maintenance_mode
> > > > >     str(value))
> > > > > > > > > > > > > > >   File "/usr/lib/python2.7/site-
packages/ovirt_hosted_engine_ha/client/client.py", line 204,
in set_global_md_flag
> > > > >     all_stats = broker.get_stats_from_storage(service)
> > > > > > > > > > > > > > >   File "/usr/lib/python2.7/site-
packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 232,
in get_stats_from_storage
> > > > >     result = self._checked_communicate(request)
> > > > > > > > > > > > > > >   File "/usr/lib/python2.7/site-
packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 260,
in _checked_communicate
> > > > >     .format(message or response))
> > > > > > > > > > > > > > > ovirt_hosted_engine_ha.lib.exceptions.RequestError:
> > > > > > > > > > > > > > >  Request
failed: failed to read metadata: [Errno 1] Operation not
permitted
> > > > > 
> > > > > 
> > > > > > > > > > > > > > > If I only upgrade one host, then things will 
> > > > > > > > > > > > > > > continue to work
but my nodes are constantly healing shards.  My logs are also
flooded with:
> > > > > 
> > > > > > > > > > > > > > > [2016-07-21 13:15:14.137734] W [fuse-
bridge.c:2227:fuse_readv_cbk] 0-glusterfs-fuse: 274714: READ
=> -1 gfid=4
> > > > > > > > > > 41f2789-f6b1-4918-a280-1b9905a11429 

Re: [ovirt-users] one export domain two DC

[Fernando Fuentes]

Colin,
Thanks for your reply.
Can you give me some details on how you did it?
You just put it on maintenance mode and detach it and the add it to the
other domain?
It wont complain about been part of another domain?
 
Regards,
 
On Wed, Jul 20, 2016 at 10:54 PM, Colin Coe  wrote:
 
> Not sure about 4.0, but We have RHEV 3.5 and RHEV 3.6 sharing the same
> export domain.  Caveat is it can only be attached to one DC at a time.
>
> CC
>
> On Thu, Jul 21, 2016 at 11:38 AM, Fernando Fuentes
>  wrote:
>> How about this one? :)
>>
>>  --
>>  Fernando Fuentes ffuen...@txweather.org http://www.txweather.org
>>
>> On Wed, Jul 20, 2016, at 06:04 AM, Fernando Fuentes wrote:
>>  > Is it possible to export all of my vms on my oVirt 3.5 Domain and
>>  > than
>>  > attach my export domain on my oVirt 4.0 DC and import the vm's?
>>  >
>>  > Regards,
>>  >
>>  > --
>>  > Fernando Fuentes
>>  > ffuen...@txweather.org
>>  > http://www.txweather.org
>>  > ___
>>  > 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] Windows 10 + qemu + Blue Iris = Blue screen

[Blaster]

I am running an application called Blue Iris which records video from IP cameras.This was working great under Ovirt 3.6.3 + Windows 7.  Now I’ve upgraded to Windows 10 and as soon as the Blue Iris service starts, the VM blue screens.I talked to the software vendor, and they said it’s not their problem, they aren’t doing anything that could cause a blue screen, so it must be  driver/memory/hardware problem.  They say the application works just fine under Windows 10.So thinking maybe the upgrade went bad, I created a new VM, used e1000 and IDE interfaces (i.e., no Virtualized hardware or drivers were used) and re-installed Blue Iris.Still blue screens.How do I go about figuring out what’s causing the blue screen?  Thanks….___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] 3.5 to 3.6 upgrade stuck

[Robert Story]

On Thu, 21 Jul 2016 14:43:50 -0400 Robert wrote:
RS> So after some debugging with Simone on irc, we've determined that the issue
RS> is the agent timing out trying to communicate with the broker. The problem
RS> is that we have no idea why.

So more detail attached. The agent is sending:

   
MainThread::hosted_engine::436::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine
  ::(start_monitoring) Processing engine state 
 
MainThread::brokerlink::111::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink
  ::(notify) Trying: notify time=1469129518.85 type=state_transition 
detail=StartState-ReinitializeFSM hostname='poseidon.netsec' 
MainThread::brokerlink::273::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink
  ::(_communicate) Sending request: notify time=1469129518.85 
type=state_transition detail=StartState-ReinitializeFSM 
hostname='poseidon.netsec'

Which the broker sees:

Thread-1::util::69::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler
 ::(socket_readline) socket_readline in blocking mode
Thread-1::listener::163::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler
 ::(handle) Input: notify time=1469129518.85 type=state_transition 
detail=StartState-ReinitializeFSM hostname='poseidon.netsec'

It then refreshes the local config file:

Thread-1::config::251::ovirt_hosted_engine_ha.broker.notifications.Notifications.config
 ::(refresh_local_conf_file) Reading 'broker.conf' from 
'/rhev/data-center/mnt/ovirt-nfs.netsec:_ovirt_hosted-engine/2daba0ab-2b3d-4026-bcfc-1cd071c30038/images/a04a45b9-e780-4104-ad4b-d5901a5490c4/34a7

Which succeeds:

Thread-1::config::271::ovirt_hosted_engine_ha.broker.notifications.Notifications.config
 ::(refresh_local_conf_file) Writing to 
'/var/lib/ovirt-hosted-engine-ha/broker.conf'
Thread-1::config::278::ovirt_hosted_engine_ha.broker.notifications.Notifications.config
 ::(refresh_local_conf_file) local conf file was correctly written

And then  nothing. It just hangs. Nothing more is logged Thread-1.



Robert

-- 
Senior Software Engineer @ Parsons



Robert

-- 
Senior Software Engineer @ Parsons

MainThread::DEBUG::2016-07-21 15:31:58,847::hosted_engine::436::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring) Processing engine state 
MainThread::INFO::2016-07-21 15:31:58,847::brokerlink::111::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(notify) Trying: notify time=1469129518.85 type=state_transition detail=StartState-ReinitializeFSM hostname='poseidon.netsec'
MainThread::DEBUG::2016-07-21 15:31:58,847::brokerlink::273::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(_communicate) Sending request: notify time=1469129518.85 type=state_transition detail=StartState-ReinitializeFSM hostname='poseidon.netsec'
MainThread::DEBUG::2016-07-21 15:31:58,848::util::77::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(socket_readline) socket_readline with 30.0 seconds timeout
MainThread::DEBUG::2016-07-21 15:32:28,866::util::88::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(socket_readline) Connection timeout while reading from socket
MainThread::ERROR::2016-07-21 15:32:28,867::brokerlink::279::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(_communicate) Connection closed: Connection timed out
MainThread::DEBUG::2016-07-21 15:32:28,867::brokerlink::86::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(disconnect) Closing connection to ha-broker
MainThread::ERROR::2016-07-21 15:32:28,867::agent::205::ovirt_hosted_engine_ha.agent.agent.Agent::(_run_agent) Error: 'Failed to start monitor state_transition, options {'hostname': 'poseidon.netsec'}: Connection timed out' - trying to restart agent


Thread-1::util::69::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler
 ::(socket_readline) socket_readline in blocking mode
Thread-1::listener::163::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler
 ::(handle) Input: notify time=1469129518.85 type=state_transition detail=StartState-ReinitializeFSM hostname='poseidon.netsec'
Thread-1::listener::238::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler
 ::(_dispatch) Request type notify from 139793244509952
Thread-1::notifications::46::ovirt_hosted_engine_ha.broker.notifications.Notifications
 ::(notify) nofity: {'hostname': 'poseidon.netsec', 'type': 'state_transition', 'detail': 'StartState-ReinitializeFSM', 'time': '1469129518.85'}
Thread-1::config::251::ovirt_hosted_engine_ha.broker.notifications.Notifications.config
 ::(refresh_local_conf_file) Reading 'broker.conf' from 

Re: [ovirt-users] Spice in 4.0

[Alexander Wels]

On Thursday, July 21, 2016 02:38:41 PM Melissa Mesler wrote:
> That worked! Thank you!!!
> 

Okay, great now if you want to set that as the default, so you don't have to 
do that manually each time do the following:

ssh into the engine box as root.
engine-config -s ClientModeSpiceDefault=Plugin

That should default it to be plugin for all the VMs.

> On Thu, Jul 21, 2016, at 02:14 PM, Alexander Wels wrote:
> > On Thursday, July 21, 2016 01:58:05 PM Melissa Mesler wrote:
> > > Yes, this is a workaround for us after upgrading to 4.0. I know it's
> > > going away in 4.1 but this buys us some time.
> > > 
> > > So the first option didn't work b/c like yous aid, it wasn't there. So
> > > we did the second step and it still didn't seem to work. We even tried
> > > restarting ovirt but that didn't help either. Any other ideas?
> > 
> > Looking at the code it also set the default mode to 'native' instead of
> > plugin. After you set the flag to true and restarted the engine, do you
> > see the
> > 'plugin' option when you right click on a running VM in webadmin and
> > select
> > console options? It should be under Console Invocation
> > 
> > > On Thu, Jul 21, 2016, at 01:39 PM, Alexander Wels wrote:
> > > > On Thursday, July 21, 2016 01:19:35 PM Melissa Mesler wrote:
> > > > > Yes we are trying to get spice working on a thin client where
> > > > > we can't
> > > > > use virt-viewer. I just don't know the steps in the bugzilla to
> > > > > accomplish it as it's not completely clear.
> > > > 
> > > > Okay gotcha,
> > > > Note in 4.1 this ability will be completely removed, the bugzilla is
> > > > for cases where people need it in some kind of production environment.
> > > > 
> > > > Assuming you can ssh into the machine that is running the engine
> > > > (either HE or standard engine) as root:
> > > > 
> > > > engine-config -s EnableDeprecatedClientModeSpicePlugin=true
> > > > 
> > > > If that doesn't work because the option was not added to engine-config
> > > > (couldn't tell from reading the code). Try this:
> > > > 
> > > > sudo su postgres
> > > > --this will log you in as the postgres user
> > > > psql -d engine
> > > > --this will start psql connecing to the engine database. The
> > > > default will be
> > > > --engine if you didn't specify something else during engine-
> > > > setup. psql -l
> > > > --will list all the databases.
> > > > update vdc_options set option_value=true where
> > > > option_name='EnableDeprecatedClientModeSpicePlugin';
> > > > 
> > > > > On Thu, Jul 21, 2016, at 01:14 PM, Alexander Wels wrote:
> > > > > > On Thursday, July 21, 2016 01:08:49 PM Melissa Mesler wrote:
> > > > > > > So I am trying to get spice working in ovirt 4.0. I found the
> > > > > > > following
> > > > > > > solution:
> > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1316560
> > > > > > 
> > > > > > That bugzilla relates to the legacy spice.xpi FF plugin, and
> > > > > > possibly
> > > > > > some
> > > > > > activex plugin for IE. The current way is the following:
> > > > > > 
> > > > > > 1. Get virt-viewer for your platform.
> > > > > > 2. Associated virt-viewer with .vv files in your browser.
> > > > > > 3. Click the button, which will download the .vv file with the
> > > > > > appropriate
> > > > > > ticket.
> > > > > > 4. The browser will launch virt-viewer with the .vv file as a
> > > > > > 
> > > > > >parameter
> > > > > > 
> > > > > > and it
> > > > > > should just all work.
> > > > > > 
> > > > > > > Where do you set
> > > > > > > vdc_options.EnableDeprecatedClientModeSpicePlugin to
> > > > > > > 'true'?? I see it says ENGINE_DB but what steps do I follow to
> > > > > > > do this?
> > > > > > > Can someone help me?
> > > > > > > ___
> > > > > > > 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] Spice in 4.0

[Melissa Mesler]

That worked! Thank you!!!

On Thu, Jul 21, 2016, at 02:14 PM, Alexander Wels wrote:
> On Thursday, July 21, 2016 01:58:05 PM Melissa Mesler wrote:
> > Yes, this is a workaround for us after upgrading to 4.0. I know it's
> > going away in 4.1 but this buys us some time.
> > 
> > So the first option didn't work b/c like yous aid, it wasn't there. So
> > we did the second step and it still didn't seem to work. We even tried
> > restarting ovirt but that didn't help either. Any other ideas?
> > 
> 
> Looking at the code it also set the default mode to 'native' instead of 
> plugin. After you set the flag to true and restarted the engine, do you
> see the 
> 'plugin' option when you right click on a running VM in webadmin and
> select 
> console options? It should be under Console Invocation
> 
> > On Thu, Jul 21, 2016, at 01:39 PM, Alexander Wels wrote:
> > > On Thursday, July 21, 2016 01:19:35 PM Melissa Mesler wrote:
> > > > Yes we are trying to get spice working on a thin client where
> > > > we can't
> > > > use virt-viewer. I just don't know the steps in the bugzilla to
> > > > accomplish it as it's not completely clear.
> > > 
> > > Okay gotcha,
> > > Note in 4.1 this ability will be completely removed, the bugzilla is
> > > for cases where people need it in some kind of production environment.
> > > 
> > > Assuming you can ssh into the machine that is running the engine
> > > (either HE or standard engine) as root:
> > > 
> > > engine-config -s EnableDeprecatedClientModeSpicePlugin=true
> > > 
> > > If that doesn't work because the option was not added to engine-config
> > > (couldn't tell from reading the code). Try this:
> > > 
> > > sudo su postgres
> > > --this will log you in as the postgres user
> > > psql -d engine
> > > --this will start psql connecing to the engine database. The
> > > default will be
> > > --engine if you didn't specify something else during engine-
> > > setup. psql -l
> > > --will list all the databases.
> > > update vdc_options set option_value=true where
> > > option_name='EnableDeprecatedClientModeSpicePlugin';
> > > 
> > > > On Thu, Jul 21, 2016, at 01:14 PM, Alexander Wels wrote:
> > > > > On Thursday, July 21, 2016 01:08:49 PM Melissa Mesler wrote:
> > > > > > So I am trying to get spice working in ovirt 4.0. I found the
> > > > > > following
> > > > > > solution:
> > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1316560
> > > > > 
> > > > > That bugzilla relates to the legacy spice.xpi FF plugin, and
> > > > > possibly
> > > > > some
> > > > > activex plugin for IE. The current way is the following:
> > > > > 
> > > > > 1. Get virt-viewer for your platform.
> > > > > 2. Associated virt-viewer with .vv files in your browser.
> > > > > 3. Click the button, which will download the .vv file with the
> > > > > appropriate
> > > > > ticket.
> > > > > 4. The browser will launch virt-viewer with the .vv file as a
> > > > > 
> > > > >parameter
> > > > > 
> > > > > and it
> > > > > should just all work.
> > > > > 
> > > > > > Where do you set
> > > > > > vdc_options.EnableDeprecatedClientModeSpicePlugin to
> > > > > > 'true'?? I see it says ENGINE_DB but what steps do I follow to
> > > > > > do this?
> > > > > > Can someone help me?
> > > > > > ___
> > > > > > 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 3.6.6 and gluster 3.7.13

[Scott]

You change the cache mode using a custom property per-VM I believe.  I
don't know if this would work for the hosted engine.

I've already downgraded my system, but once you have the test machine up,
perhaps you can try it.   The custom property would be:

viodiskcache=writethrough

or

viodiskcache=writeback

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html/Virtual_Machine_Management_Guide/appe-Reference_Settings_in_Administration_Portal_and_User_Portal_Windows.html#Virtual_Machine_Custom_Properties_settings_explained

Scott

On Thu, Jul 21, 2016 at 12:53 PM David Gossage 
wrote:

> On Thu, Jul 21, 2016 at 11:47 AM, Scott  wrote:
>
>> Hi David,
>>
>> My backend storage is ZFS.
>>
>> I thought about moving from FUSE to NFS mounts for my Gluster volumes to
>> help test.  But since I use hosted engine this would be a real pain.  Its
>> difficult to modify the storage domain type/path in the
>> hosted-engine.conf.  And I don't want to go through the process of
>> re-deploying hosted engine.
>>
>>
> I found this
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1347553
>
> Not sure if related.
>
> But I also have zfs backend, another user in gluster mailing list had
> issues and used zfs backend although she used proxmox and got it working by
> changing disk to writeback cache I think it was.
>
> I also use hosted engine, but I run my gluster volume for HE actually on a
> LVM separate from zfs on xfs and if i recall it did not have the issues my
> gluster on zfs did.  I'm wondering now if the issue was zfs settings.
>
> Hopefully should have a test machone up soon I can play around with more.
>
> Scott
>>
>> On Thu, Jul 21, 2016 at 11:36 AM David Gossage <
>> dgoss...@carouselchecks.com> wrote:
>>
>>> What back end storage do you run gluster on?  xfs/zfs/ext4 etc?
>>>
>>> *David Gossage*
>>> *Carousel Checks Inc. | System Administrator*
>>> *Office* 708.613.2284
>>>
>>> On Thu, Jul 21, 2016 at 8:18 AM, Scott  wrote:
>>>
 I get similar problems with oVirt 4.0.1 and hosted engine.  After
 upgrading all my hosts to Gluster 3.7.13 (client and server), I get the
 following:

 $ sudo hosted-engine --set-maintenance --mode=none
 Traceback (most recent call last):
   File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
 "__main__", fname, loader, pkg_name)
   File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
 exec code in run_globals
   File
 "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
 line 73, in 
 if not maintenance.set_mode(sys.argv[1]):
   File
 "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
 line 61, in set_mode
 value=m_global,
   File
 "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
 line 259, in set_maintenance_mode
 str(value))
   File
 "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
 line 204, in set_global_md_flag
 all_stats = broker.get_stats_from_storage(service)
   File
 "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
 line 232, in get_stats_from_storage
 result = self._checked_communicate(request)
   File
 "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
 line 260, in _checked_communicate
 .format(message or response))
 ovirt_hosted_engine_ha.lib.exceptions.RequestError: Request failed:
 failed to read metadata: [Errno 1] Operation not permitted

 If I only upgrade one host, then things will continue to work but my
 nodes are constantly healing shards.  My logs are also flooded with:

 [2016-07-21 13:15:14.137734] W [fuse-bridge.c:2227:fuse_readv_cbk]
 0-glusterfs-fuse: 274714: READ => -1 gfid=4
 41f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
 permitted)
 The message "W [MSGID: 114031]
 [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote
 operation failed [Operation not permitted]" repeated 6 times between
 [2016-07-21 13:13:24.134985] and [2016-07-21 13:15:04.132226]
 The message "W [MSGID: 114031]
 [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-1: remote
 operation failed [Operation not permitted]" repeated 8 times between
 [2016-07-21 13:13:34.133116] and [2016-07-21 13:15:14.137178]
 The message "W [MSGID: 114031]
 [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-2: remote
 operation failed [Operation not permitted]" repeated 7 times between
 [2016-07-21 13:13:24.135071] and [2016-07-21 13:15:14.137666]
 [2016-07-21 13:15:24.134647] W [MSGID: 114031]
 [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote
 operation failed [Operation not permitted]

Re: [ovirt-users] Spice in 4.0

[Alexander Wels]

On Thursday, July 21, 2016 01:58:05 PM Melissa Mesler wrote:
> Yes, this is a workaround for us after upgrading to 4.0. I know it's
> going away in 4.1 but this buys us some time.
> 
> So the first option didn't work b/c like yous aid, it wasn't there. So
> we did the second step and it still didn't seem to work. We even tried
> restarting ovirt but that didn't help either. Any other ideas?
> 

Looking at the code it also set the default mode to 'native' instead of 
plugin. After you set the flag to true and restarted the engine, do you see the 
'plugin' option when you right click on a running VM in webadmin and select 
console options? It should be under Console Invocation

> On Thu, Jul 21, 2016, at 01:39 PM, Alexander Wels wrote:
> > On Thursday, July 21, 2016 01:19:35 PM Melissa Mesler wrote:
> > > Yes we are trying to get spice working on a thin client where
> > > we can't
> > > use virt-viewer. I just don't know the steps in the bugzilla to
> > > accomplish it as it's not completely clear.
> > 
> > Okay gotcha,
> > Note in 4.1 this ability will be completely removed, the bugzilla is
> > for cases where people need it in some kind of production environment.
> > 
> > Assuming you can ssh into the machine that is running the engine
> > (either HE or standard engine) as root:
> > 
> > engine-config -s EnableDeprecatedClientModeSpicePlugin=true
> > 
> > If that doesn't work because the option was not added to engine-config
> > (couldn't tell from reading the code). Try this:
> > 
> > sudo su postgres
> > --this will log you in as the postgres user
> > psql -d engine
> > --this will start psql connecing to the engine database. The
> > default will be
> > --engine if you didn't specify something else during engine-
> > setup. psql -l
> > --will list all the databases.
> > update vdc_options set option_value=true where
> > option_name='EnableDeprecatedClientModeSpicePlugin';
> > 
> > > On Thu, Jul 21, 2016, at 01:14 PM, Alexander Wels wrote:
> > > > On Thursday, July 21, 2016 01:08:49 PM Melissa Mesler wrote:
> > > > > So I am trying to get spice working in ovirt 4.0. I found the
> > > > > following
> > > > > solution:
> > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1316560
> > > > 
> > > > That bugzilla relates to the legacy spice.xpi FF plugin, and
> > > > possibly
> > > > some
> > > > activex plugin for IE. The current way is the following:
> > > > 
> > > > 1. Get virt-viewer for your platform.
> > > > 2. Associated virt-viewer with .vv files in your browser.
> > > > 3. Click the button, which will download the .vv file with the
> > > > appropriate
> > > > ticket.
> > > > 4. The browser will launch virt-viewer with the .vv file as a
> > > > 
> > > >parameter
> > > > 
> > > > and it
> > > > should just all work.
> > > > 
> > > > > Where do you set
> > > > > vdc_options.EnableDeprecatedClientModeSpicePlugin to
> > > > > 'true'?? I see it says ENGINE_DB but what steps do I follow to
> > > > > do this?
> > > > > Can someone help me?
> > > > > ___
> > > > > 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] Spice in 4.0

[Melissa Mesler]

Yes, this is a workaround for us after upgrading to 4.0. I know it's
going away in 4.1 but this buys us some time.

So the first option didn't work b/c like yous aid, it wasn't there. So
we did the second step and it still didn't seem to work. We even tried
restarting ovirt but that didn't help either. Any other ideas?
 
 
On Thu, Jul 21, 2016, at 01:39 PM, Alexander Wels wrote:
> On Thursday, July 21, 2016 01:19:35 PM Melissa Mesler wrote:
> > Yes we are trying to get spice working on a thin client where
> > we can't
> > use virt-viewer. I just don't know the steps in the bugzilla to
> > accomplish it as it's not completely clear.
> >
>
> Okay gotcha,
> Note in 4.1 this ability will be completely removed, the bugzilla is
> for cases where people need it in some kind of production environment.
>
> Assuming you can ssh into the machine that is running the engine
> (either HE or standard engine) as root:
>
> engine-config -s EnableDeprecatedClientModeSpicePlugin=true
>
> If that doesn't work because the option was not added to engine-config
> (couldn't tell from reading the code). Try this:
>
> sudo su postgres
> --this will log you in as the postgres user
> psql -d engine
> --this will start psql connecing to the engine database. The
> default will be
> --engine if you didn't specify something else during engine-
> setup. psql -l
> --will list all the databases.
> update vdc_options set option_value=true where
> option_name='EnableDeprecatedClientModeSpicePlugin';
>
> > On Thu, Jul 21, 2016, at 01:14 PM, Alexander Wels wrote:
> > > On Thursday, July 21, 2016 01:08:49 PM Melissa Mesler wrote:
> > > > So I am trying to get spice working in ovirt 4.0. I found the
> > > > following
> > > > solution:
> > > > https://bugzilla.redhat.com/show_bug.cgi?id=1316560
> > >
> > > That bugzilla relates to the legacy spice.xpi FF plugin, and
> > > possibly
> > > some
> > > activex plugin for IE. The current way is the following:
> > >
> > > 1. Get virt-viewer for your platform.
> > > 2. Associated virt-viewer with .vv files in your browser.
> > > 3. Click the button, which will download the .vv file with the
> > > appropriate
> > > ticket.
> > > 4. The browser will launch virt-viewer with the .vv file as a
> > >parameter
> > > and it
> > > should just all work.
> > >
> > > > Where do you set
> > > > vdc_options.EnableDeprecatedClientModeSpicePlugin to
> > > > 'true'?? I see it says ENGINE_DB but what steps do I follow to
> > > > do this?
> > > > Can someone help me?
> > > > ___
> > > > 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] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

[Matt .]

OK, it seems that a snapshot was having the files but linux didn't saw
a change between the images as the size was still the same.

I'm going to dd back :)

2016-07-21 20:04 GMT+02:00 Matt . :
> OK, it seems that my config volume for the hosted engine is empty, I
> cannot tar anything out of it and I'm quite sure it has been empty for
> ever as I got some strange warning every time.
>
> Is there a way to recover that from files ? Backups/snapshots are empty so...
>
> 2016-07-21 13:43 GMT+02:00 Simone Tiraboschi :
>> On Thu, Jul 21, 2016 at 12:38 PM, Matt .  wrote:
>>> The deploy went OK from the GUI but it's still not "active" as Hosted
>>> engine Host. The install also wen very fast so it looked like it
>>> didn't do anything witl the deploy setting in the GUI @ the hosted
>>> engine tab.
>>
>> The difference with a standard host is just that it should create
>> /etc/ovirt-hosted-engine/hosted-engine.conf and start ovirt-ha-agent
>> and ovirt-ha-broker so it shouldn't be that longer.
>>
>> At the end, due to the issue with syncing the local maintenance mode
>> from the engine, you have to connect to the host and run
>> 'hosted-engine -set-maintenance --mode=none' from there.
>>
>> Can you please post the result of
>> hosted-engine --vm-status and the status of ovirt-ha-agent?
>>
>>> Or should I re-deploy again on the commandline after adding the host
>>> through the GUI ?
>>>
>>> About the initial GW, I didn't see that in the GUI.
>>>
>>> 2016-07-21 12:31 GMT+02:00 Simone Tiraboschi :
 On Thu, Jul 21, 2016 at 12:28 PM, Matt .  wrote:
> No problem I checked it out and applied it, no solution it seems.

 Do you mean that it's still referring to your initial gateway or that
 the deploy failed?

> 2016-07-21 12:14 GMT+02:00 Simone Tiraboschi :
>> On Thu, Jul 21, 2016 at 12:09 PM, Matt .  wrote:
>>> OK, I did a deploy from the engine and the Hosted is "Not Active" and
>>
>> Yes, sorry, I forgot to mention that.
>> We have an open bug about re-activating an hosted-engine host from the
>> engine: https://bugzilla.redhat.com/show_bug.cgi?id=1353600
>> Connecting to the host and exiting the maintenance mode from there is
>> the temporary solution.
>>
>>> Engine HA is empty on 4.0.1
>>>
>>> 2016-07-21 11:58 GMT+02:00 Matt . :
 True, but you can up an IP on any device in that case because you know
 what you are doing.

 I think that this can be finetuned, or at least multiple IPs would be
 nice as I now need to add one IP from my vrrp setup, so if there is a
 failover or I need to take down the second switch I'm also done.

 2016-07-21 10:23 GMT+02:00 Simone Tiraboschi :
> On Thu, Jul 21, 2016 at 10:03 AM, Matt .  
> wrote:
>> OK, I will check this laster on, as I was having issues with the
>> deploy from the GUI before as nothing really happened, I thought it
>> was a bug on the first 4.0 release ?
>>
>> I think this should be investigated, the whole deployment as it would
>> be good to have the possibility to list some GW's in case you use
>> failover.
>>
>> I was even thinking of setting the engine IP there, should be working
>> as good as also.
>
> Not really since the agent is pinging also when the engine VM is down
> due to maintenance.
>
>> 2016-07-21 9:53 GMT+02:00 Simone Tiraboschi :
>>> On Thu, Jul 21, 2016 at 9:47 AM, Matt .  
>>> wrote:
 OK, I already thought that but where is this saved as I don't have 
 any
 rights as root to the ha_agent folder on the HE storage ?
>>>
>>> It's not a folder: it's a tar file directly saved over a VDSM 
>>> volume.
>>> Editing it's a bit tricky.
>>>
 In worst case scenario, how would i be able to deploy a new hosted
 engine from a hosted engine ? This sounds undoable to me and also
 unwanted as the HE is OK so far.
>>>
>>> With a 4.0 engine, when you choose to deploy a new host from the
>>> webadmin or from the rest API you can also choose to deploy it as an
>>> hosted-engine host if the engine has been deployed with 
>>> hosted-engine.
>>> In this case, if I'm not wrong, you can also specify a different 
>>> gateway value.
>>>
>>>
 2016-07-21 9:41 GMT+02:00 Simone Tiraboschi :
> On Thu, Jul 21, 2016 at 9:27 AM, Matt .  
> wrote:
>> Even 

Re: [ovirt-users] ovirt 3.6.6 and gluster 3.7.13

[Karli Sjöberg]

Den 21 jul 2016 8:39 em skrev Scott :
>
> CentOS 7 for me as well, using the zfsonlinux.org packages.

Ok, so whatever problems there may be in those packages, at least you have them 
in common. That can also be a comfort:)

/K

>
> On Thu, Jul 21, 2016 at 1:26 PM David Gossage  
> wrote:
>>
>> On Thu, Jul 21, 2016 at 1:24 PM, Karli Sjöberg  wrote:
>>>
>>>
>>> Den 21 jul 2016 7:54 em skrev David Gossage :
>>> >
>>> > On Thu, Jul 21, 2016 at 11:47 AM, Scott  wrote:
>>> >>
>>> >> Hi David,
>>> >>
>>> >> My backend storage is ZFS.
>>> >>
>>> >> I thought about moving from FUSE to NFS mounts for my Gluster volumes to 
>>> >> help test.  But since I use hosted engine this would be a real pain.  
>>> >> Its difficult to modify the storage domain type/path in the 
>>> >> hosted-engine.conf.  And I don't want to go through the process of 
>>> >> re-deploying hosted engine.
>>> >>
>>> >
>>> > I found this
>>> >
>>> > https://bugzilla.redhat.com/show_bug.cgi?id=1347553
>>> >
>>> > Not sure if related.
>>> >
>>> > But I also have zfs backend, another user in gluster mailing list had 
>>> > issues and used zfs backend although she used proxmox and got it working 
>>> > by changing disk to writeback cache I think it was.
>>>
>>> David and Scott,
>>>
>>> just out of curiousity, what is the OS under ZFS?
>>
>> Centos 7
>>
>>>
>>> /K
>>>
>>> >
>>> > I also use hosted engine, but I run my gluster volume for HE actually on 
>>> > a LVM separate from zfs on xfs and if i recall it did not have the issues 
>>> > my gluster on zfs did.  I'm wondering now if the issue was zfs settings.
>>> >
>>> > Hopefully should have a test machone up soon I can play around with more.
>>> >
>>> >> Scott
>>> >>
>>> >> On Thu, Jul 21, 2016 at 11:36 AM David Gossage 
>>> >>  wrote:
>>> >>>
>>> >>> What back end storage do you run gluster on?  xfs/zfs/ext4 etc?
>>> >>>
>>> >>> David Gossage
>>> >>> Carousel Checks Inc. | System Administrator
>>> >>> Office 708.613.2284
>>> >>>
>>> >>> On Thu, Jul 21, 2016 at 8:18 AM, Scott  wrote:
>>> 
>>>  I get similar problems with oVirt 4.0.1 and hosted engine.  After 
>>>  upgrading all my hosts to Gluster 3.7.13 (client and server), I get 
>>>  the following:
>>> 
>>>  $ sudo hosted-engine --set-maintenance --mode=none
>>>  Traceback (most recent call last):
>>>    File "/usr/lib64/python2.7/runpy.py", line 162, in 
>>>  _run_module_as_main
>>>  "__main__", fname, loader, pkg_name)
>>>    File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
>>>  exec code in run_globals
>>>    File 
>>>  "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
>>>   line 73, in 
>>>  if not maintenance.set_mode(sys.argv[1]):
>>>    File 
>>>  "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
>>>   line 61, in set_mode
>>>  value=m_global,
>>>    File 
>>>  "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
>>>   line 259, in set_maintenance_mode
>>>  str(value))
>>>    File 
>>>  "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
>>>   line 204, in set_global_md_flag
>>>  all_stats = broker.get_stats_from_storage(service)
>>>    File 
>>>  "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
>>>   line 232, in get_stats_from_storage
>>>  result = self._checked_communicate(request)
>>>    File 
>>>  "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
>>>   line 260, in _checked_communicate
>>>  .format(message or response))
>>>  ovirt_hosted_engine_ha.lib.exceptions.RequestError: Request failed: 
>>>  failed to read metadata: [Errno 1] Operation not permitted
>>> 
>>>  If I only upgrade one host, then things will continue to work but my 
>>>  nodes are constantly healing shards.  My logs are also flooded with:
>>> 
>>>  [2016-07-21 13:15:14.137734] W [fuse-bridge.c:2227:fuse_readv_cbk] 
>>>  0-glusterfs-fuse: 274714: READ => -1 gfid=4
>>>  41f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not 
>>>  permitted)
>>>  The message "W [MSGID: 114031] 
>>>  [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote 
>>>  operation failed [Operation not permitted]" repeated 6 times between 
>>>  [2016-07-21 13:13:24.134985] and [2016-07-21 13:15:04.132226]
>>>  The message "W [MSGID: 114031] 
>>>  [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-1: remote 
>>>  operation failed [Operation not permitted]" repeated 8 times between 
>>>  [2016-07-21 13:13:34.133116] and [2016-07-21 13:15:14.137178]
>>>  The message "W [MSGID: 

Re: [ovirt-users] 3.5 to 3.6 upgrade stuck

[Robert Story]

So after some debugging with Simone on irc, we've determined that the issue
is the agent timing out trying to communicate with the broker. The problem
is that we have no idea why.

Thread-942::INFO::2016-07-21
09:19:51,934::listener::134::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(setup)
Connection established Thread-942::INFO::2016-07-21
09:19:51,936::listener::186::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle)
Connection closed Thread-943::INFO::2016-07-21
09:19:53,099::listener::134::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(setup)
Connection established Thread-943::INFO::2016-07-21
09:19:53,554::listener::186::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle)
Connection closed

Thread-135::DEBUG::2016-07-21
09:47:34,941::util::69::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(socket_readline)
socket_readline in blocking mode Thread-135::DEBUG::2016-07-21
09:47:34,941::util::99::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(socket_readline)
Connection closed while reading from socket


So I tried to reinstall instead:

- host -> maintenance
- host removed from cluster
- yum remove ovirt\*
- yum install ovirt-hosted-engine-setup
- hosted-engine --deploy
  - chose new node id
  - reused same name/hostname

Once the host activated, it went right back to the same state.

I'm open to any suggestions to get me back on track. The engine is at
3.6.7, but functioning hosts are still at 3.5.x. Should I try to upgrade
the engine and a host to 4.0.x? I had planned on having a stable 3.6 system
for a few days before trying to jump to 4.0. Or is there some way to go
back to 3.5?


Robert

-- 
Senior Software Engineer @ Parsons


pgpayyu94ifIL.pgp
Description: OpenPGP digital signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt 3.6.6 and gluster 3.7.13

[Scott]

CentOS 7 for me as well, using the zfsonlinux.org packages.

On Thu, Jul 21, 2016 at 1:26 PM David Gossage 
wrote:

> On Thu, Jul 21, 2016 at 1:24 PM, Karli Sjöberg 
> wrote:
>
>>
>> Den 21 jul 2016 7:54 em skrev David Gossage > >:
>> >
>> > On Thu, Jul 21, 2016 at 11:47 AM, Scott  wrote:
>> >>
>> >> Hi David,
>> >>
>> >> My backend storage is ZFS.
>> >>
>> >> I thought about moving from FUSE to NFS mounts for my Gluster volumes
>> to help test.  But since I use hosted engine this would be a real pain.
>> Its difficult to modify the storage domain type/path in the
>> hosted-engine.conf.  And I don't want to go through the process of
>> re-deploying hosted engine.
>> >>
>> >
>> > I found this
>> >
>> > https://bugzilla.redhat.com/show_bug.cgi?id=1347553
>> >
>> > Not sure if related.
>> >
>> > But I also have zfs backend, another user in gluster mailing list had
>> issues and used zfs backend although she used proxmox and got it working by
>> changing disk to writeback cache I think it was.
>>
>> David and Scott,
>>
>> just out of curiousity, what is the OS under ZFS?
>>
>> Centos 7
>
>
>> /K
>>
>> >
>> > I also use hosted engine, but I run my gluster volume for HE actually
>> on a LVM separate from zfs on xfs and if i recall it did not have the
>> issues my gluster on zfs did.  I'm wondering now if the issue was zfs
>> settings.
>> >
>> > Hopefully should have a test machone up soon I can play around with
>> more.
>> >
>> >> Scott
>> >>
>> >> On Thu, Jul 21, 2016 at 11:36 AM David Gossage <
>> dgoss...@carouselchecks.com> wrote:
>> >>>
>> >>> What back end storage do you run gluster on?  xfs/zfs/ext4 etc?
>> >>>
>> >>> David Gossage
>> >>> Carousel Checks Inc. | System Administrator
>> >>> Office 708.613.2284
>> >>>
>> >>> On Thu, Jul 21, 2016 at 8:18 AM, Scott  wrote:
>> 
>>  I get similar problems with oVirt 4.0.1 and hosted engine.  After
>> upgrading all my hosts to Gluster 3.7.13 (client and server), I get the
>> following:
>> 
>>  $ sudo hosted-engine --set-maintenance --mode=none
>>  Traceback (most recent call last):
>>    File "/usr/lib64/python2.7/runpy.py", line 162, in
>> _run_module_as_main
>>  "__main__", fname, loader, pkg_name)
>>    File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
>>  exec code in run_globals
>>    File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
>> line 73, in 
>>  if not maintenance.set_mode(sys.argv[1]):
>>    File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
>> line 61, in set_mode
>>  value=m_global,
>>    File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
>> line 259, in set_maintenance_mode
>>  str(value))
>>    File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
>> line 204, in set_global_md_flag
>>  all_stats = broker.get_stats_from_storage(service)
>>    File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
>> line 232, in get_stats_from_storage
>>  result = self._checked_communicate(request)
>>    File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
>> line 260, in _checked_communicate
>>  .format(message or response))
>>  ovirt_hosted_engine_ha.lib.exceptions.RequestError: Request failed:
>> failed to read metadata: [Errno 1] Operation not permitted
>> 
>>  If I only upgrade one host, then things will continue to work but my
>> nodes are constantly healing shards.  My logs are also flooded with:
>> 
>>  [2016-07-21 13:15:14.137734] W [fuse-bridge.c:2227:fuse_readv_cbk]
>> 0-glusterfs-fuse: 274714: READ => -1 gfid=4
>>  41f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
>> permitted)
>>  The message "W [MSGID: 114031]
>> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote
>> operation failed [Operation not permitted]" repeated 6 times between
>> [2016-07-21 13:13:24.134985] and [2016-07-21 13:15:04.132226]
>>  The message "W [MSGID: 114031]
>> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-1: remote
>> operation failed [Operation not permitted]" repeated 8 times between
>> [2016-07-21 13:13:34.133116] and [2016-07-21 13:15:14.137178]
>>  The message "W [MSGID: 114031]
>> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-2: remote
>> operation failed [Operation not permitted]" repeated 7 times between
>> [2016-07-21 13:13:24.135071] and [2016-07-21 13:15:14.137666]
>>  [2016-07-21 13:15:24.134647] W [MSGID: 114031]
>> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote
>> operation failed [Operation not permitted]
>>  [2016-07-21 13:15:24.134764] W [MSGID: 114031]
>> 

Re: [ovirt-users] Spice in 4.0

[Alexander Wels]

On Thursday, July 21, 2016 01:19:35 PM Melissa Mesler wrote:
> Yes we are trying to get spice working on a thin client where we can't
> use virt-viewer. I just don't know the steps in the bugzilla to
> accomplish it as it's not completely clear.
> 

Okay gotcha,
Note in 4.1 this ability will be completely removed, the bugzilla is for cases 
where 
people need it in some kind of production environment.

Assuming you can ssh into the machine that is running the engine (either HE or 
standard engine) as root:

engine-config -s EnableDeprecatedClientModeSpicePlugin=true

If that doesn't work because the option was not added to engine-config 
(couldn't tell 
from reading the code). Try this:

sudo su postgres
--this will log you in as the postgres user
psql -d engine
--this will start psql connecing to the engine database. The default will be
--engine if you didn't specify something else during engine-setup. psql -l
--will list all the databases.
update vdc_options set option_value=true where 
option_name='EnableDeprecatedClientModeSpicePlugin';


> On Thu, Jul 21, 2016, at 01:14 PM, Alexander Wels wrote:
> > On Thursday, July 21, 2016 01:08:49 PM Melissa Mesler wrote:
> > > So I am trying to get spice working in ovirt 4.0. I found the following
> > > solution:
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1316560
> > 
> > That bugzilla relates to the legacy spice.xpi FF plugin, and possibly
> > some
> > activex plugin for IE. The current way is the following:
> > 
> > 1. Get virt-viewer for your platform.
> > 2. Associated virt-viewer with .vv files in your browser.
> > 3. Click the button, which will download the .vv file with the
> > appropriate
> > ticket.
> > 4. The browser will launch virt-viewer with the .vv file as a parameter
> > and it
> > should just all work.
> > 
> > > Where do you set vdc_options.EnableDeprecatedClientModeSpicePlugin to
> > > 'true'?? I see it says ENGINE_DB but what steps do I follow to do this?
> > > Can someone help me?
> > > ___
> > > 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 3.6.6 and gluster 3.7.13

[David Gossage]

On Thu, Jul 21, 2016 at 1:24 PM, Karli Sjöberg  wrote:

>
> Den 21 jul 2016 7:54 em skrev David Gossage :
> >
> > On Thu, Jul 21, 2016 at 11:47 AM, Scott  wrote:
> >>
> >> Hi David,
> >>
> >> My backend storage is ZFS.
> >>
> >> I thought about moving from FUSE to NFS mounts for my Gluster volumes
> to help test.  But since I use hosted engine this would be a real pain.
> Its difficult to modify the storage domain type/path in the
> hosted-engine.conf.  And I don't want to go through the process of
> re-deploying hosted engine.
> >>
> >
> > I found this
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1347553
> >
> > Not sure if related.
> >
> > But I also have zfs backend, another user in gluster mailing list had
> issues and used zfs backend although she used proxmox and got it working by
> changing disk to writeback cache I think it was.
>
> David and Scott,
>
> just out of curiousity, what is the OS under ZFS?
>
> Centos 7


> /K
>
> >
> > I also use hosted engine, but I run my gluster volume for HE actually on
> a LVM separate from zfs on xfs and if i recall it did not have the issues
> my gluster on zfs did.  I'm wondering now if the issue was zfs settings.
> >
> > Hopefully should have a test machone up soon I can play around with more.
> >
> >> Scott
> >>
> >> On Thu, Jul 21, 2016 at 11:36 AM David Gossage <
> dgoss...@carouselchecks.com> wrote:
> >>>
> >>> What back end storage do you run gluster on?  xfs/zfs/ext4 etc?
> >>>
> >>> David Gossage
> >>> Carousel Checks Inc. | System Administrator
> >>> Office 708.613.2284
> >>>
> >>> On Thu, Jul 21, 2016 at 8:18 AM, Scott  wrote:
> 
>  I get similar problems with oVirt 4.0.1 and hosted engine.  After
> upgrading all my hosts to Gluster 3.7.13 (client and server), I get the
> following:
> 
>  $ sudo hosted-engine --set-maintenance --mode=none
>  Traceback (most recent call last):
>    File "/usr/lib64/python2.7/runpy.py", line 162, in
> _run_module_as_main
>  "__main__", fname, loader, pkg_name)
>    File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
>  exec code in run_globals
>    File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
> line 73, in 
>  if not maintenance.set_mode(sys.argv[1]):
>    File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
> line 61, in set_mode
>  value=m_global,
>    File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
> line 259, in set_maintenance_mode
>  str(value))
>    File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
> line 204, in set_global_md_flag
>  all_stats = broker.get_stats_from_storage(service)
>    File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
> line 232, in get_stats_from_storage
>  result = self._checked_communicate(request)
>    File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
> line 260, in _checked_communicate
>  .format(message or response))
>  ovirt_hosted_engine_ha.lib.exceptions.RequestError: Request failed:
> failed to read metadata: [Errno 1] Operation not permitted
> 
>  If I only upgrade one host, then things will continue to work but my
> nodes are constantly healing shards.  My logs are also flooded with:
> 
>  [2016-07-21 13:15:14.137734] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 274714: READ => -1 gfid=4
>  41f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
> permitted)
>  The message "W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote
> operation failed [Operation not permitted]" repeated 6 times between
> [2016-07-21 13:13:24.134985] and [2016-07-21 13:15:04.132226]
>  The message "W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-1: remote
> operation failed [Operation not permitted]" repeated 8 times between
> [2016-07-21 13:13:34.133116] and [2016-07-21 13:15:14.137178]
>  The message "W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-2: remote
> operation failed [Operation not permitted]" repeated 7 times between
> [2016-07-21 13:13:24.135071] and [2016-07-21 13:15:14.137666]
>  [2016-07-21 13:15:24.134647] W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote
> operation failed [Operation not permitted]
>  [2016-07-21 13:15:24.134764] W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-2: remote
> operation failed [Operation not permitted]
>  [2016-07-21 13:15:24.134793] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 274741: READ => -1
> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0038f4 (Operation not
> 

Re: [ovirt-users] ovirt 3.6.6 and gluster 3.7.13

[Karli Sjöberg]

Den 21 jul 2016 7:54 em skrev David Gossage :
>
> On Thu, Jul 21, 2016 at 11:47 AM, Scott  wrote:
>>
>> Hi David,
>>
>> My backend storage is ZFS.
>>
>> I thought about moving from FUSE to NFS mounts for my Gluster volumes to 
>> help test.  But since I use hosted engine this would be a real pain.  Its 
>> difficult to modify the storage domain type/path in the hosted-engine.conf.  
>> And I don't want to go through the process of re-deploying hosted engine.
>>
>
> I found this
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1347553
>
> Not sure if related.
>
> But I also have zfs backend, another user in gluster mailing list had issues 
> and used zfs backend although she used proxmox and got it working by changing 
> disk to writeback cache I think it was.

David and Scott,

just out of curiousity, what is the OS under ZFS?

/K

>
> I also use hosted engine, but I run my gluster volume for HE actually on a 
> LVM separate from zfs on xfs and if i recall it did not have the issues my 
> gluster on zfs did.  I'm wondering now if the issue was zfs settings.
>
> Hopefully should have a test machone up soon I can play around with more.
>
>> Scott
>>
>> On Thu, Jul 21, 2016 at 11:36 AM David Gossage  
>> wrote:
>>>
>>> What back end storage do you run gluster on?  xfs/zfs/ext4 etc?
>>>
>>> David Gossage
>>> Carousel Checks Inc. | System Administrator
>>> Office 708.613.2284
>>>
>>> On Thu, Jul 21, 2016 at 8:18 AM, Scott  wrote:

 I get similar problems with oVirt 4.0.1 and hosted engine.  After 
 upgrading all my hosts to Gluster 3.7.13 (client and server), I get the 
 following:

 $ sudo hosted-engine --set-maintenance --mode=none
 Traceback (most recent call last):
   File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
 "__main__", fname, loader, pkg_name)
   File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
 exec code in run_globals
   File 
 "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
  line 73, in 
 if not maintenance.set_mode(sys.argv[1]):
   File 
 "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
  line 61, in set_mode
 value=m_global,
   File 
 "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
  line 259, in set_maintenance_mode
 str(value))
   File 
 "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
  line 204, in set_global_md_flag
 all_stats = broker.get_stats_from_storage(service)
   File 
 "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
  line 232, in get_stats_from_storage
 result = self._checked_communicate(request)
   File 
 "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
  line 260, in _checked_communicate
 .format(message or response))
 ovirt_hosted_engine_ha.lib.exceptions.RequestError: Request failed: failed 
 to read metadata: [Errno 1] Operation not permitted

 If I only upgrade one host, then things will continue to work but my nodes 
 are constantly healing shards.  My logs are also flooded with:

 [2016-07-21 13:15:14.137734] W [fuse-bridge.c:2227:fuse_readv_cbk] 
 0-glusterfs-fuse: 274714: READ => -1 gfid=4
 41f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not 
 permitted)
 The message "W [MSGID: 114031] 
 [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote 
 operation failed [Operation not permitted]" repeated 6 times between 
 [2016-07-21 13:13:24.134985] and [2016-07-21 13:15:04.132226]
 The message "W [MSGID: 114031] 
 [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-1: remote 
 operation failed [Operation not permitted]" repeated 8 times between 
 [2016-07-21 13:13:34.133116] and [2016-07-21 13:15:14.137178]
 The message "W [MSGID: 114031] 
 [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-2: remote 
 operation failed [Operation not permitted]" repeated 7 times between 
 [2016-07-21 13:13:24.135071] and [2016-07-21 13:15:14.137666]
 [2016-07-21 13:15:24.134647] W [MSGID: 114031] 
 [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote 
 operation failed [Operation not permitted]
 [2016-07-21 13:15:24.134764] W [MSGID: 114031] 
 [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-2: remote 
 operation failed [Operation not permitted]
 [2016-07-21 13:15:24.134793] W [fuse-bridge.c:2227:fuse_readv_cbk] 
 0-glusterfs-fuse: 274741: READ => -1 
 gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0038f4 (Operation not 
 permitted)
 [2016-07-21 13:15:34.135413] W [fuse-bridge.c:2227:fuse_readv_cbk] 
 

Re: [ovirt-users] Spice in 4.0

[Melissa Mesler]

Yes we are trying to get spice working on a thin client where we can't
use virt-viewer. I just don't know the steps in the bugzilla to
accomplish it as it's not completely clear.

On Thu, Jul 21, 2016, at 01:14 PM, Alexander Wels wrote:
> On Thursday, July 21, 2016 01:08:49 PM Melissa Mesler wrote:
> > So I am trying to get spice working in ovirt 4.0. I found the following
> > solution:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1316560
> > 
> 
> That bugzilla relates to the legacy spice.xpi FF plugin, and possibly
> some 
> activex plugin for IE. The current way is the following:
> 
> 1. Get virt-viewer for your platform.
> 2. Associated virt-viewer with .vv files in your browser.
> 3. Click the button, which will download the .vv file with the
> appropriate 
> ticket.
> 4. The browser will launch virt-viewer with the .vv file as a parameter
> and it 
> should just all work.
> 
> > Where do you set vdc_options.EnableDeprecatedClientModeSpicePlugin to
> > 'true'?? I see it says ENGINE_DB but what steps do I follow to do this?
> > Can someone help me?
> > ___
> > 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] Spice in 4.0

[Alexander Wels]

On Thursday, July 21, 2016 01:08:49 PM Melissa Mesler wrote:
> So I am trying to get spice working in ovirt 4.0. I found the following
> solution:
> https://bugzilla.redhat.com/show_bug.cgi?id=1316560
> 

That bugzilla relates to the legacy spice.xpi FF plugin, and possibly some 
activex plugin for IE. The current way is the following:

1. Get virt-viewer for your platform.
2. Associated virt-viewer with .vv files in your browser.
3. Click the button, which will download the .vv file with the appropriate 
ticket.
4. The browser will launch virt-viewer with the .vv file as a parameter and it 
should just all work.

> Where do you set vdc_options.EnableDeprecatedClientModeSpicePlugin to
> 'true'?? I see it says ENGINE_DB but what steps do I follow to do this?
> Can someone help me?
> ___
> 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] Spice in 4.0

[Melissa Mesler]

So I am trying to get spice working in ovirt 4.0. I found the following
solution:
https://bugzilla.redhat.com/show_bug.cgi?id=1316560

Where do you set vdc_options.EnableDeprecatedClientModeSpicePlugin to
'true'?? I see it says ENGINE_DB but what steps do I follow to do this?
Can someone help me?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

[Matt .]

OK, it seems that my config volume for the hosted engine is empty, I
cannot tar anything out of it and I'm quite sure it has been empty for
ever as I got some strange warning every time.

Is there a way to recover that from files ? Backups/snapshots are empty so...

2016-07-21 13:43 GMT+02:00 Simone Tiraboschi :
> On Thu, Jul 21, 2016 at 12:38 PM, Matt .  wrote:
>> The deploy went OK from the GUI but it's still not "active" as Hosted
>> engine Host. The install also wen very fast so it looked like it
>> didn't do anything witl the deploy setting in the GUI @ the hosted
>> engine tab.
>
> The difference with a standard host is just that it should create
> /etc/ovirt-hosted-engine/hosted-engine.conf and start ovirt-ha-agent
> and ovirt-ha-broker so it shouldn't be that longer.
>
> At the end, due to the issue with syncing the local maintenance mode
> from the engine, you have to connect to the host and run
> 'hosted-engine -set-maintenance --mode=none' from there.
>
> Can you please post the result of
> hosted-engine --vm-status and the status of ovirt-ha-agent?
>
>> Or should I re-deploy again on the commandline after adding the host
>> through the GUI ?
>>
>> About the initial GW, I didn't see that in the GUI.
>>
>> 2016-07-21 12:31 GMT+02:00 Simone Tiraboschi :
>>> On Thu, Jul 21, 2016 at 12:28 PM, Matt .  wrote:
 No problem I checked it out and applied it, no solution it seems.
>>>
>>> Do you mean that it's still referring to your initial gateway or that
>>> the deploy failed?
>>>
 2016-07-21 12:14 GMT+02:00 Simone Tiraboschi :
> On Thu, Jul 21, 2016 at 12:09 PM, Matt .  wrote:
>> OK, I did a deploy from the engine and the Hosted is "Not Active" and
>
> Yes, sorry, I forgot to mention that.
> We have an open bug about re-activating an hosted-engine host from the
> engine: https://bugzilla.redhat.com/show_bug.cgi?id=1353600
> Connecting to the host and exiting the maintenance mode from there is
> the temporary solution.
>
>> Engine HA is empty on 4.0.1
>>
>> 2016-07-21 11:58 GMT+02:00 Matt . :
>>> True, but you can up an IP on any device in that case because you know
>>> what you are doing.
>>>
>>> I think that this can be finetuned, or at least multiple IPs would be
>>> nice as I now need to add one IP from my vrrp setup, so if there is a
>>> failover or I need to take down the second switch I'm also done.
>>>
>>> 2016-07-21 10:23 GMT+02:00 Simone Tiraboschi :
 On Thu, Jul 21, 2016 at 10:03 AM, Matt .  
 wrote:
> OK, I will check this laster on, as I was having issues with the
> deploy from the GUI before as nothing really happened, I thought it
> was a bug on the first 4.0 release ?
>
> I think this should be investigated, the whole deployment as it would
> be good to have the possibility to list some GW's in case you use
> failover.
>
> I was even thinking of setting the engine IP there, should be working
> as good as also.

 Not really since the agent is pinging also when the engine VM is down
 due to maintenance.

> 2016-07-21 9:53 GMT+02:00 Simone Tiraboschi :
>> On Thu, Jul 21, 2016 at 9:47 AM, Matt .  
>> wrote:
>>> OK, I already thought that but where is this saved as I don't have 
>>> any
>>> rights as root to the ha_agent folder on the HE storage ?
>>
>> It's not a folder: it's a tar file directly saved over a VDSM volume.
>> Editing it's a bit tricky.
>>
>>> In worst case scenario, how would i be able to deploy a new hosted
>>> engine from a hosted engine ? This sounds undoable to me and also
>>> unwanted as the HE is OK so far.
>>
>> With a 4.0 engine, when you choose to deploy a new host from the
>> webadmin or from the rest API you can also choose to deploy it as an
>> hosted-engine host if the engine has been deployed with 
>> hosted-engine.
>> In this case, if I'm not wrong, you can also specify a different 
>> gateway value.
>>
>>
>>> 2016-07-21 9:41 GMT+02:00 Simone Tiraboschi :
 On Thu, Jul 21, 2016 at 9:27 AM, Matt .  
 wrote:
> Even when I change that on each host before I do a new deploy it 
> still
> uses the old GW address.

 If you deploy additional hosts with the CLI utility, each new host
 will be deployed consuming the answerfile generated by the first 
 host
 and saved on 

Re: [ovirt-users] ovirt 3.6.6 and gluster 3.7.13

[David Gossage]

On Thu, Jul 21, 2016 at 11:47 AM, Scott  wrote:

> Hi David,
>
> My backend storage is ZFS.
>
> I thought about moving from FUSE to NFS mounts for my Gluster volumes to
> help test.  But since I use hosted engine this would be a real pain.  Its
> difficult to modify the storage domain type/path in the
> hosted-engine.conf.  And I don't want to go through the process of
> re-deploying hosted engine.
>
>
I found this

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

Not sure if related.

But I also have zfs backend, another user in gluster mailing list had
issues and used zfs backend although she used proxmox and got it working by
changing disk to writeback cache I think it was.

I also use hosted engine, but I run my gluster volume for HE actually on a
LVM separate from zfs on xfs and if i recall it did not have the issues my
gluster on zfs did.  I'm wondering now if the issue was zfs settings.

Hopefully should have a test machone up soon I can play around with more.

Scott
>
> On Thu, Jul 21, 2016 at 11:36 AM David Gossage <
> dgoss...@carouselchecks.com> wrote:
>
>> What back end storage do you run gluster on?  xfs/zfs/ext4 etc?
>>
>> *David Gossage*
>> *Carousel Checks Inc. | System Administrator*
>> *Office* 708.613.2284
>>
>> On Thu, Jul 21, 2016 at 8:18 AM, Scott  wrote:
>>
>>> I get similar problems with oVirt 4.0.1 and hosted engine.  After
>>> upgrading all my hosts to Gluster 3.7.13 (client and server), I get the
>>> following:
>>>
>>> $ sudo hosted-engine --set-maintenance --mode=none
>>> Traceback (most recent call last):
>>>   File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
>>> "__main__", fname, loader, pkg_name)
>>>   File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
>>> exec code in run_globals
>>>   File
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
>>> line 73, in 
>>> if not maintenance.set_mode(sys.argv[1]):
>>>   File
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
>>> line 61, in set_mode
>>> value=m_global,
>>>   File
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
>>> line 259, in set_maintenance_mode
>>> str(value))
>>>   File
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
>>> line 204, in set_global_md_flag
>>> all_stats = broker.get_stats_from_storage(service)
>>>   File
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
>>> line 232, in get_stats_from_storage
>>> result = self._checked_communicate(request)
>>>   File
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
>>> line 260, in _checked_communicate
>>> .format(message or response))
>>> ovirt_hosted_engine_ha.lib.exceptions.RequestError: Request failed:
>>> failed to read metadata: [Errno 1] Operation not permitted
>>>
>>> If I only upgrade one host, then things will continue to work but my
>>> nodes are constantly healing shards.  My logs are also flooded with:
>>>
>>> [2016-07-21 13:15:14.137734] W [fuse-bridge.c:2227:fuse_readv_cbk]
>>> 0-glusterfs-fuse: 274714: READ => -1 gfid=4
>>> 41f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
>>> permitted)
>>> The message "W [MSGID: 114031]
>>> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote
>>> operation failed [Operation not permitted]" repeated 6 times between
>>> [2016-07-21 13:13:24.134985] and [2016-07-21 13:15:04.132226]
>>> The message "W [MSGID: 114031]
>>> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-1: remote
>>> operation failed [Operation not permitted]" repeated 8 times between
>>> [2016-07-21 13:13:34.133116] and [2016-07-21 13:15:14.137178]
>>> The message "W [MSGID: 114031]
>>> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-2: remote
>>> operation failed [Operation not permitted]" repeated 7 times between
>>> [2016-07-21 13:13:24.135071] and [2016-07-21 13:15:14.137666]
>>> [2016-07-21 13:15:24.134647] W [MSGID: 114031]
>>> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote
>>> operation failed [Operation not permitted]
>>> [2016-07-21 13:15:24.134764] W [MSGID: 114031]
>>> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-2: remote
>>> operation failed [Operation not permitted]
>>> [2016-07-21 13:15:24.134793] W [fuse-bridge.c:2227:fuse_readv_cbk]
>>> 0-glusterfs-fuse: 274741: READ => -1
>>> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0038f4 (Operation not
>>> permitted)
>>> [2016-07-21 13:15:34.135413] W [fuse-bridge.c:2227:fuse_readv_cbk]
>>> 0-glusterfs-fuse: 274756: READ => -1
>>> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
>>> permitted)
>>> [2016-07-21 13:15:44.141062] W [fuse-bridge.c:2227:fuse_readv_cbk]
>>> 0-glusterfs-fuse: 274818: READ => -1
>>> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0038f4 (Operation 

Re: [ovirt-users] ovirt 3.6.6 and gluster 3.7.13

[Scott]

Hi David,

My backend storage is ZFS.

I thought about moving from FUSE to NFS mounts for my Gluster volumes to
help test.  But since I use hosted engine this would be a real pain.  Its
difficult to modify the storage domain type/path in the
hosted-engine.conf.  And I don't want to go through the process of
re-deploying hosted engine.

Scott

On Thu, Jul 21, 2016 at 11:36 AM David Gossage 
wrote:

> What back end storage do you run gluster on?  xfs/zfs/ext4 etc?
>
> *David Gossage*
> *Carousel Checks Inc. | System Administrator*
> *Office* 708.613.2284
>
> On Thu, Jul 21, 2016 at 8:18 AM, Scott  wrote:
>
>> I get similar problems with oVirt 4.0.1 and hosted engine.  After
>> upgrading all my hosts to Gluster 3.7.13 (client and server), I get the
>> following:
>>
>> $ sudo hosted-engine --set-maintenance --mode=none
>> Traceback (most recent call last):
>>   File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
>> "__main__", fname, loader, pkg_name)
>>   File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
>> exec code in run_globals
>>   File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
>> line 73, in 
>> if not maintenance.set_mode(sys.argv[1]):
>>   File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
>> line 61, in set_mode
>> value=m_global,
>>   File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
>> line 259, in set_maintenance_mode
>> str(value))
>>   File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
>> line 204, in set_global_md_flag
>> all_stats = broker.get_stats_from_storage(service)
>>   File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
>> line 232, in get_stats_from_storage
>> result = self._checked_communicate(request)
>>   File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
>> line 260, in _checked_communicate
>> .format(message or response))
>> ovirt_hosted_engine_ha.lib.exceptions.RequestError: Request failed:
>> failed to read metadata: [Errno 1] Operation not permitted
>>
>> If I only upgrade one host, then things will continue to work but my
>> nodes are constantly healing shards.  My logs are also flooded with:
>>
>> [2016-07-21 13:15:14.137734] W [fuse-bridge.c:2227:fuse_readv_cbk]
>> 0-glusterfs-fuse: 274714: READ => -1 gfid=4
>> 41f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
>> permitted)
>> The message "W [MSGID: 114031]
>> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote
>> operation failed [Operation not permitted]" repeated 6 times between
>> [2016-07-21 13:13:24.134985] and [2016-07-21 13:15:04.132226]
>> The message "W [MSGID: 114031]
>> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-1: remote
>> operation failed [Operation not permitted]" repeated 8 times between
>> [2016-07-21 13:13:34.133116] and [2016-07-21 13:15:14.137178]
>> The message "W [MSGID: 114031]
>> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-2: remote
>> operation failed [Operation not permitted]" repeated 7 times between
>> [2016-07-21 13:13:24.135071] and [2016-07-21 13:15:14.137666]
>> [2016-07-21 13:15:24.134647] W [MSGID: 114031]
>> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote
>> operation failed [Operation not permitted]
>> [2016-07-21 13:15:24.134764] W [MSGID: 114031]
>> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-2: remote
>> operation failed [Operation not permitted]
>> [2016-07-21 13:15:24.134793] W [fuse-bridge.c:2227:fuse_readv_cbk]
>> 0-glusterfs-fuse: 274741: READ => -1
>> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0038f4 (Operation not
>> permitted)
>> [2016-07-21 13:15:34.135413] W [fuse-bridge.c:2227:fuse_readv_cbk]
>> 0-glusterfs-fuse: 274756: READ => -1
>> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
>> permitted)
>> [2016-07-21 13:15:44.141062] W [fuse-bridge.c:2227:fuse_readv_cbk]
>> 0-glusterfs-fuse: 274818: READ => -1
>> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0038f4 (Operation not
>> permitted)
>> [2016-07-21 13:15:54.133582] W [MSGID: 114031]
>> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-1: remote
>> operation failed [Operation not permitted]
>> [2016-07-21 13:15:54.133629] W [fuse-bridge.c:2227:fuse_readv_cbk]
>> 0-glusterfs-fuse: 274853: READ => -1
>> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0036d8 (Operation not
>> permitted)
>> [2016-07-21 13:16:04.133666] W [fuse-bridge.c:2227:fuse_readv_cbk]
>> 0-glusterfs-fuse: 274879: READ => -1
>> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
>> permitted)
>> [2016-07-21 13:16:14.134954] W [fuse-bridge.c:2227:fuse_readv_cbk]
>> 0-glusterfs-fuse: 274894: READ => -1
>> gfid=441f2789-f6b1-4918-a280-1b9905a11429 

Re: [ovirt-users] ovirt 3.6.6 and gluster 3.7.13

[David Gossage]

What back end storage do you run gluster on?  xfs/zfs/ext4 etc?

*David Gossage*
*Carousel Checks Inc. | System Administrator*
*Office* 708.613.2284

On Thu, Jul 21, 2016 at 8:18 AM, Scott  wrote:

> I get similar problems with oVirt 4.0.1 and hosted engine.  After
> upgrading all my hosts to Gluster 3.7.13 (client and server), I get the
> following:
>
> $ sudo hosted-engine --set-maintenance --mode=none
> Traceback (most recent call last):
>   File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
> "__main__", fname, loader, pkg_name)
>   File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
> exec code in run_globals
>   File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
> line 73, in 
> if not maintenance.set_mode(sys.argv[1]):
>   File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
> line 61, in set_mode
> value=m_global,
>   File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
> line 259, in set_maintenance_mode
> str(value))
>   File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
> line 204, in set_global_md_flag
> all_stats = broker.get_stats_from_storage(service)
>   File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
> line 232, in get_stats_from_storage
> result = self._checked_communicate(request)
>   File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
> line 260, in _checked_communicate
> .format(message or response))
> ovirt_hosted_engine_ha.lib.exceptions.RequestError: Request failed: failed
> to read metadata: [Errno 1] Operation not permitted
>
> If I only upgrade one host, then things will continue to work but my nodes
> are constantly healing shards.  My logs are also flooded with:
>
> [2016-07-21 13:15:14.137734] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 274714: READ => -1 gfid=4
> 41f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
> permitted)
> The message "W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote
> operation failed [Operation not permitted]" repeated 6 times between
> [2016-07-21 13:13:24.134985] and [2016-07-21 13:15:04.132226]
> The message "W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-1: remote
> operation failed [Operation not permitted]" repeated 8 times between
> [2016-07-21 13:13:34.133116] and [2016-07-21 13:15:14.137178]
> The message "W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-2: remote
> operation failed [Operation not permitted]" repeated 7 times between
> [2016-07-21 13:13:24.135071] and [2016-07-21 13:15:14.137666]
> [2016-07-21 13:15:24.134647] W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote
> operation failed [Operation not permitted]
> [2016-07-21 13:15:24.134764] W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-2: remote
> operation failed [Operation not permitted]
> [2016-07-21 13:15:24.134793] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 274741: READ => -1
> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0038f4 (Operation not
> permitted)
> [2016-07-21 13:15:34.135413] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 274756: READ => -1
> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
> permitted)
> [2016-07-21 13:15:44.141062] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 274818: READ => -1
> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0038f4 (Operation not
> permitted)
> [2016-07-21 13:15:54.133582] W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-1: remote
> operation failed [Operation not permitted]
> [2016-07-21 13:15:54.133629] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 274853: READ => -1
> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0036d8 (Operation not
> permitted)
> [2016-07-21 13:16:04.133666] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 274879: READ => -1
> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
> permitted)
> [2016-07-21 13:16:14.134954] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 274894: READ => -1
> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0036d8 (Operation not
> permitted)
>
> Scott
>
>
> On Thu, Jul 21, 2016 at 6:57 AM Frank Rothenstein <
> f.rothenst...@bodden-kliniken.de> wrote:
>
>> Hey Devid,
>>
>> I have the very same problem on my test-cluster, despite on running ovirt
>> 4.0.
>> If you access your volumes via NFS all is fine, problem is FUSE. I stayed
>> on 3.7.13, but have no solution yet, now I use NFS.
>>
>> Frank
>>
>> Am Donnerstag, den 21.07.2016, 04:28 -0500 schrieb David Gossage:
>>
>> Anyone running one of recent 3.6.x lines and gluster using 

Re: [ovirt-users] Exporting VMs using cinder disks and importing ceph disks from cinder

[Nir Soffer]

On Thu, Jul 21, 2016 at 5:33 PM, Alessandro De Salvo
 wrote:
> Hi Nir,
>
> On Thu, 2016-07-21 at 17:25 +0300, Nir Soffer wrote:
>> On Thu, Jul 21, 2016 at 4:58 PM, Alessandro De Salvo
>>  wrote:
>> > Hi,
>> > I'm trying to export VMs using ceph disks on ovirt 4. The export itself
>> > works, but the disks are not saved in the export domains, only the VM
>> > definition is stored. Also, I cannot easily re-import them, unless I
>> > clone the VM instead of importing it, it just fails.
>> > Cinder itself can backup volumes, if instructed to do so.
>> > However, let's say I would like to export the machine from an ovirt
>> > infrastructure and load it into another one passing by the export domain
>> > and sharing the same underlying ceph cluster. I could easily load the VM
>> > from the export domain into the second ovirt infrastructure, but how can
>> > I define the disk, whose volume exists in the cinder instance, in the
>> > second ovirt? I do not see any obvious way to map an existing cinder
>> > volume into ovirt, without creating a new disk, which would not be
>> > helpful.
>> > As a consequence of all this, in case of problems with the disks, there
>> > is no way to recover them.
>> > Any help?
>>
>> We do not support copying, moving, or exporting disks to/from ceph yet.
>>
>> You can copy the disks manually from ceph using ceph command line
>> tools, and qemu-img should also handle them.
>
> Yes, I just found a trick to re-import the disk, using qemu-img to dump
> the image on a file from rbd:/, create a new disk in ovirt
> and use qemu-img to copy it back on the new image. Technically it is
> working, but it's a bit convoluted. Any plans to add the relevant
> support in ovirt?

We want to support all operations available with legacy storage
with ceph. I don't know about plans to improve the situation for 4.1.

>> After you copy an image, you will a have a raw image that can be
>> uploaded to new ovirt disk from engine ui (new image upload feature).
>
> Are you talking to the upload button in the Disks tab? I do not see how
> I can upload to cinder/ceph from there.

Yes, upload to ceph is not supported yet, hopefully we can do this in
4.1.

Today you can upload to any other storage after you copied the
image our of ceph to a local file. This automates creation of a new
disk and copying the file into the new disk, which is more tricky if
you want to copy into block storage.

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

Re: [ovirt-users] ovirt 3.6.6 and gluster 3.7.13

[David Gossage]

I'm creating a  test box I can more thoroughly mess with so I can submit to
bugzilla something.  Since my errors all popped up while trying to get
ovirt and gluster functional again rather than thoroughly gather logs and
test my data is kinda sketchy.

*David Gossage*
*Carousel Checks Inc. | System Administrator*
*Office* 708.613.2284

On Thu, Jul 21, 2016 at 8:18 AM, Scott  wrote:

> I get similar problems with oVirt 4.0.1 and hosted engine.  After
> upgrading all my hosts to Gluster 3.7.13 (client and server), I get the
> following:
>
> $ sudo hosted-engine --set-maintenance --mode=none
> Traceback (most recent call last):
>   File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
> "__main__", fname, loader, pkg_name)
>   File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
> exec code in run_globals
>   File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
> line 73, in 
> if not maintenance.set_mode(sys.argv[1]):
>   File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
> line 61, in set_mode
> value=m_global,
>   File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
> line 259, in set_maintenance_mode
> str(value))
>   File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
> line 204, in set_global_md_flag
> all_stats = broker.get_stats_from_storage(service)
>   File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
> line 232, in get_stats_from_storage
> result = self._checked_communicate(request)
>   File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
> line 260, in _checked_communicate
> .format(message or response))
> ovirt_hosted_engine_ha.lib.exceptions.RequestError: Request failed: failed
> to read metadata: [Errno 1] Operation not permitted
>
> If I only upgrade one host, then things will continue to work but my nodes
> are constantly healing shards.  My logs are also flooded with:
>
> [2016-07-21 13:15:14.137734] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 274714: READ => -1 gfid=4
> 41f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
> permitted)
> The message "W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote
> operation failed [Operation not permitted]" repeated 6 times between
> [2016-07-21 13:13:24.134985] and [2016-07-21 13:15:04.132226]
> The message "W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-1: remote
> operation failed [Operation not permitted]" repeated 8 times between
> [2016-07-21 13:13:34.133116] and [2016-07-21 13:15:14.137178]
> The message "W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-2: remote
> operation failed [Operation not permitted]" repeated 7 times between
> [2016-07-21 13:13:24.135071] and [2016-07-21 13:15:14.137666]
> [2016-07-21 13:15:24.134647] W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote
> operation failed [Operation not permitted]
> [2016-07-21 13:15:24.134764] W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-2: remote
> operation failed [Operation not permitted]
> [2016-07-21 13:15:24.134793] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 274741: READ => -1
> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0038f4 (Operation not
> permitted)
> [2016-07-21 13:15:34.135413] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 274756: READ => -1
> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
> permitted)
> [2016-07-21 13:15:44.141062] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 274818: READ => -1
> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0038f4 (Operation not
> permitted)
> [2016-07-21 13:15:54.133582] W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-1: remote
> operation failed [Operation not permitted]
> [2016-07-21 13:15:54.133629] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 274853: READ => -1
> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0036d8 (Operation not
> permitted)
> [2016-07-21 13:16:04.133666] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 274879: READ => -1
> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
> permitted)
> [2016-07-21 13:16:14.134954] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 274894: READ => -1
> gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0036d8 (Operation not
> permitted)
>
> Scott
>
>
> On Thu, Jul 21, 2016 at 6:57 AM Frank Rothenstein <
> f.rothenst...@bodden-kliniken.de> wrote:
>
>> Hey Devid,
>>
>> I have the very same problem on my test-cluster, despite on running ovirt
>> 4.0.
>> If you access your volumes via NFS all is fine, problem is FUSE. I stayed
>> on 3.7.13, but 

Re: [ovirt-users] Import of ova failed

[Cam Mac]

Bug ID 1358828. I can do another for the direct import of the OVF (without
virt-v2v) if needed.

Cheers,

Cam

On Thu, Jul 21, 2016 at 2:56 PM, Shahar Havivi  wrote:

> On 21.07.16 14:38, Cam Mac wrote:
> > I tried that already, and it fails. I gave it another try with the GUI on
> > the new VM I created, as you described, and it fails.
> > I can attach the engine log if you like.
> no need,
> please file a bug and attach the ova (without the disks - its a tar file
> that
> you can edit)
> >
> > Thanks,
> >
> > Cam
> >
> > On Thu, Jul 21, 2016 at 2:17 PM, Shahar Havivi 
> wrote:
> >
> > > On 21.07.16 14:01, Campbell McLeay wrote:
> > > > Thanks Shahar. Will do. I created a new VM on VMWare for the purposes
> > > > of testing the import again with a new hostname, and it failed with
> > > > the same error.
> > > What you are trying to do is as far as I understand is to use virt-v2v
> > > utility
> > > to put the ova in export domain, there may be something wrong between
> the
> > > virt-v2v output ovf and the oVirt engine.
> > > You can try the new feature to import ova strait on oVirt admin portal
> (if
> > > you
> > > already try that the forget it), go to the vms tab -> import and select
> > > "vmware ova" from the select box...
> > >
> > > >
> > > > Cheers,
> > > >
> > > > Cam
> > > >
> > > > On 21 July 2016 at 12:59, Shahar Havivi  wrote:
> > > > > On 21.07.16 14:58, Shahar Havivi wrote:
> > > > >> The error looks like you have a problem in the storage pool which
> is
> > > null by
> > > > >> the log.
> > > > >>
> > > > >> Please open a bug and specify the exact steps that you took,
> > > > >> ie.
> > > > >> 1. $ virt-v2v -o rhev ...
> > > > >> 2. goto the admin portal and try to view the VMs in the export
> domain
> > > > >> 3. etc...
> > > > >>
> > > > >> If you can attach the ova without the disk it will be great.
> > > > > And please attach the engine.log as well.
> > > > >>
> > > > >> Shahar.
> > > > >>
> > > > >> On 21.07.16 10:16, Cam Mac wrote:
> > > > >> > Sent, thanks Shahar.
> > > > >> >
> > > > >> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi <
> shav...@redhat.com>
> > > wrote:
> > > > >> >
> > > > >> > > On 21.07.16 10:03, Cam Mac wrote:
> > > > >> > > OK,
> > > > >> > > Can you please share the engine.log
> > > > >> > > > Hi Shahar,
> > > > >> > > >
> > > > >> > > > Doesn't appear to be there:
> > > > >> > > >
> > > > >> > > > engine=> select vm_name from vm_static where vm_name='wvm2';
> > > > >> > > >  vm_name
> > > > >> > > > -
> > > > >> > > > (0 rows)
> > > > >> > > >
> > > > >> > > > Thanks,
> > > > >> > > >
> > > > >> > > > Cam
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi <
> > > shav...@redhat.com>
> > > > >> > > wrote:
> > > > >> > > >
> > > > >> > > > > On 20.07.16 20:06, Richard W.M. Jones wrote:
> > > > >> > > > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > > > >> > > > > > > >
> > > > >> > > > > > > > The import doesn't happen automatically, you have
> to do
> > > the final
> > > > >> > > > > step
> > > > >> > > > > > > > manually (when using the command line).  See:
> > > > >> > > > > > > >
> > > > >> > > > > > > >
> http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > > > >> > > > > > > >
> > > > >> > > > > > > > However that error shouldn't happen.  It looks like
> the
> > > name is
> > > > >> > > the
> > > > >> > > > > > > > same as the name of an existing VM.  From virt-v2v
> you
> > > can do the
> > > > >> > > > > > > > whole conversion/import over again, this time adding
> > > the `-on
> > > > >> > > > > > > > new_name' option to the command line (obviously
> > > choosing a name
> > > > >> > > which
> > > > >> > > > > > > > is not otherwise being used).
> > > > >> > > > > > > >
> > > > >> > > > > > > > I don't know if there's a way to get oVirt to change
> > > the name
> > > > >> > > when
> > > > >> > > > > > > > importing from the export domain.  As far as I know
> you
> > > have to
> > > > >> > > start
> > > > >> > > > > > > > the import from scratch.
> > > > >> > > > > > > >
> > > > >> > > > > > > >
> > > > >> > > > > > > There's no existing VM with that name that I can see.
> It
> > > may have
> > > > >> > > come
> > > > >> > > > > from
> > > > >> > > > > > > one of my earlier import attempts,
> > > > >> > > > > > > though that earlier attempt did not show up in the
> GUI,
> > > it did
> > > > >> > > write
> > > > >> > > > > files
> > > > >> > > > > > > to the export domain.
> > > > >> > > > > > >
> > > > >> > > > > > > I re-ran the conversion again with a rename but it
> failed
> > > to
> > > > >> > > import it
> > > > >> > > > > > > again, with the same error.
> > > > >> > > > > > >
> > > > >> > > > > > > Could there be a record in the DB somewhere, or does
> it
> > > look at the
> > > > >> > > > > files
> > > > >> > > > > > > alone? Just trying to work out where the conflict is.
> > > > >> > > > > >

Re: [ovirt-users] VMs freeze during vm-host reboot

[bertjan]

Hi,

Sorry for my delayed response. I've been away on a holiday.

Around the time of the frozen VMs I see lots and lots and lots of "Transport 
endpoint is not connected"
messages in the 
'rhev-data-center-mnt-glusterSD-vmhost1.local:_vmstore1.log-20160711' log file, 
like:

[2016-07-06 08:13:08.297203] E [MSGID: 114031] 
[client-rpc-fops.c:972:client3_3_flush_cbk] 0-vmstore1-client-2: remote 
operation failed [Transport endpoint is not connected]
[2016-07-06 08:13:08.298066] W [MSGID: 114031] 
[client-rpc-fops.c:845:client3_3_statfs_cbk] 0-vmstore1-client-2: remote 
operation failed [Transport endpoint is not connected]
[2016-07-06 08:13:08.299478] W [MSGID: 114031] 
[client-rpc-fops.c:2974:client3_3_lookup_cbk] 0-vmstore1-client-2: remote 
operation failed. Path: /9056e6a8-105f-4c63-bfc1-848f674a942a/images 
(96ff2aa1-6ade-48e5-933d-d18680c29913) [Transport endpoint is not connected]
[2016-07-06 08:13:08.300435] W [MSGID: 114031] 
[client-rpc-fops.c:2974:client3_3_lookup_cbk] 0-vmstore1-client-2: remote 
operation failed. Path: (null) (----) 
[Transport endpoint is not connected]
[2016-07-06 08:13:08.300939] E [MSGID: 114031] 
[client-rpc-fops.c:1730:client3_3_entrylk_cbk] 0-vmstore1-client-2: remote 
operation failed [Transport endpoint is not connected]
[2016-07-06 08:13:08.301351] W [MSGID: 114031] 
[client-rpc-fops.c:2974:client3_3_lookup_cbk] 0-vmstore1-client-2: remote 
operation failed. Path:  
(e38729d9-320e-4230-acab-f363cf48089e) [Transport endpoint is not connected]
[2016-07-06 08:13:08.303396] W [MSGID: 114031] 
[client-rpc-fops.c:2974:client3_3_lookup_cbk] 0-vmstore1-client-2: remote 
operation failed. Path: (null) (----) 
[Transport endpoint is not connected]
[2016-07-06 08:13:08.303954] E [MSGID: 114031] 
[client-rpc-fops.c:2886:client3_3_opendir_cbk] 0-vmstore1-client-2: remote 
operation failed. Path: /9056e6a8-105f-4c63-bfc1-848f674a942a/images 
(96ff2aa1-6ade-48e5-933d-d18680c29913) [Transport endpoint is not connected]
[2016-07-06 08:13:08.306293] W [MSGID: 114031] 
[client-rpc-fops.c:845:client3_3_statfs_cbk] 0-vmstore1-client-2: remote 
operation failed [Transport endpoint is not connected]
[2016-07-06 08:13:08.314599] W [MSGID: 114031] 
[client-rpc-fops.c:845:client3_3_statfs_cbk] 0-vmstore1-client-2: remote 
operation failed [Transport endpoint is not connected]
(repeated thousands of times)

Together with:

[2016-07-06 08:16:49.233677] W [socket.c:589:__socket_rwv] 0-glusterfs: readv 
on 10.0.0.153:24007 failed (No data available)
[2016-07-06 08:16:50.326447] W [socket.c:589:__socket_rwv] 0-vmstore1-client-0: 
readv on 10.0.0.153:49152 failed (No data available)
[2016-07-06 08:16:50.326492] I [MSGID: 114018] 
[client.c:2030:client_rpc_notify] 0-vmstore1-client-0: disconnected from 
vmstore1-client-0. Client process will keep trying to connect to glusterd until 
brick's port is available
[2016-07-06 08:16:51.523632] W [fuse-bridge.c:2302:fuse_writev_cbk] 
0-glusterfs-fuse: 33314276: WRITE => -1 (Read-only file system)
[2016-07-06 08:16:51.523890] W [MSGID: 114061] 
[client-rpc-fops.c:4449:client3_3_flush] 0-vmstore1-client-2:  
(54da8812-7f5e-48e1-87a8-4f7f17e44918) remote_fd is -1. EBADFD [File descriptor 
in bad state]
[2016-07-06 08:16:59.575848] E [socket.c:2279:socket_connect_finish] 
0-glusterfs: connection to 10.0.0.153:24007 failed (Connection refused)
[2016-07-06 08:17:00.578271] E [socket.c:2279:socket_connect_finish] 
0-vmstore1-client-0: connection to 10.0.0.153:24007 failed (Connection refused)
[2016-07-06 08:20:42.236021] I [fuse-bridge.c:4997:fuse_thread_proc] 0-fuse: 
unmounting /rhev/data-center/mnt/glusterSD/vmhost1.local:_vmstore1
[2016-07-06 08:20:42.236230] W [glusterfsd.c:1251:cleanup_and_exit] 
(-->/lib64/libpthread.so.0(+0x7dc5) [0x7f94b8ba1dc5] 
-->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xe5) [0x7f94ba20c8b5] 
-->/usr/sbin/glusterfs(cleanup_and_exit+0x69) [0x7f94ba20c739] ) 0-: received 
signum (15), shutting down
[2016-07-06 08:20:42.236271] I [fuse-bridge.c:5704:fini] 0-fuse: Unmounting 
'/rhev/data-center/mnt/glusterSD/vmhost1.local:_vmstore1'.
[2016-07-06 08:30:09.594553] I [MSGID: 100030] [glusterfsd.c:2338:main] 
0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.7.12 
(args: /usr/sbin/glusterfs --volfile-server=vmhost1.local 
--volfile-server=10.0.0.153 --volfile-server=10.0.0.160 
--volfile-server=10.0.0.198 --volfile-id=/vmstore1 
/rhev/data-center/mnt/glusterSD/vmhost1.local:_vmstore1)

After the last line ("Started running /usr/sbin/glusterfs version 3.7.12") 
everything went back to normal. 
(I replaced the hostnames and IP-addresses).

Is this the information you need?

Thanks in advance!

Regards,

Bertjan


On Mon, Jul 11, 2016 at 01:49:19PM +0530, Sahina Bose wrote:
> Did you see any errors in the gluster mount logs during the time when the
> VMs were frozen ( I assume the I/O not responding during this time?) . There
> have been bugs fixed around concurrent 

Re: [ovirt-users] Error while extending a cinder/ceph disk

[Alessandro De Salvo]

Hi Daniel,

On Thu, 2016-07-21 at 17:34 +0300, Daniel Erez wrote:
> 
> 
> On Thu, Jul 21, 2016 at 4:21 PM, Alessandro De Salvo
>  wrote:
> Hi,
> when trying to extend a ceph disk in ovirt 4 (Virtual Machines
> => Edit
> Virtual Machine => Instance images => Edit => Extend size by)
> I get the
> following error:
> 
> Error while executing action: interface is required
> 
> 
> Sounds like a similar root cause
> of https://bugzilla.redhat.com/show_bug.cgi?id=1346887
> Should be already fixed on latest build. Can you please try to upgrade
> to latest?

I'm running on the latest snapshot, upgraded a few hours ago, so I guess
it's not totally fixed yet.
Those are the ovirt-engine-* RPMS I have in my machine:

ovirt-engine-setup-plugin-ovirt-engine-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-dashboard-1.0.1-1.el7.centos.noarch
ovirt-engine-sdk-python-3.6.8.0-1.el7.centos.noarch
ovirt-engine-setup-plugin-dockerc-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-tools-backup-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-tools-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-wildfly-10.0.0-1.el7.x86_64
ovirt-engine-setup-base-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-setup-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-vmconsole-proxy-helper-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-extension-aaa-jdbc-1.1.1-0.0.master.20160623200644.git2e68ef6.el7.noarch
ovirt-engine-restapi-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-wildfly-overlay-10.0.0-1.el7.noarch
ovirt-engine-dwh-setup-4.0.2-0.1.master.20160706084440.el7.centos.noarch
ovirt-engine-lib-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
python-ovirt-engine-sdk4-4.0.0-0.5.a5.el7.centos.x86_64
ovirt-engine-extensions-api-impl-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-cli-3.6.8.1-1.el7.centos.noarch
ovirt-engine-userportal-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-webadmin-portal-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-dwh-4.0.2-0.1.master.20160706084440.el7.centos.noarch
ovirt-engine-setup-plugin-websocket-proxy-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-websocket-proxy-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-backend-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch
ovirt-engine-dbscripts-4.0.3-0.0.master.20160720203246.git9c88731.el7.centos.noarch

> 
> 
> Or, try using the Edit disk dialog under 'VMs => Disks' instead (could
> be a specific issue with the 'Instance images' flow).

Tried this as well, but I still get the same error.
Thanks,

Alessandro

>  
> 
> In engine.log I see the following errors as well:
> 
> 2016-07-21 15:14:55,266 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (default task-35) [] Correlation ID: 47ce3344, Call Stack:
> null, Custom
> Event ID: -1, Message: Failed to update VM test01 disk
> test01_Disk1
> (User: admin@internal-authz).
> 2016-07-21 15:14:56,091 ERROR
> 
> [org.ovirt.engine.core.bll.storage.disk.cinder.ExtendCinderDiskCommandCallback]
>  (DefaultQuartzScheduler8) [2819eb7c] Failed extending disk. ID: 
> a5dd90b1-3a76-4e38-af8c-e829b3b86a40
> 2016-07-21 15:14:56,124 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (DefaultQuartzScheduler8) [2819eb7c] Correlation ID: 2819eb7c,
> Call
> Stack: null, Custom Event ID: -1, Message: Failed to extend
> size of the
> disk 'test01_Disk1' to 20 GB, User: admin@internal-authz.
> 2016-07-21 15:14:56,209 ERROR
> 
> [org.ovirt.engine.core.bll.storage.disk.cinder.ExtendCinderDiskCommand]
> (DefaultQuartzScheduler8) [2819eb7c] Ending command
> 
> 'org.ovirt.engine.core.bll.storage.disk.cinder.ExtendCinderDiskCommand'
> with failure.
> 
> 
> After this, the cinder image is flagged as illegal and I can
> just delete
> it.
> Extending the image on the cinder side is possible, and the
> command
> "cinder extend " works, but then the new size is not
> properly
> reported back in ovirt.
> Any clue?
> Thanks,
> 
> Alessandro
> 

Re: [ovirt-users] Error while extending a cinder/ceph disk

[Daniel Erez]

On Thu, Jul 21, 2016 at 4:21 PM, Alessandro De Salvo <
alessandro.desa...@roma1.infn.it> wrote:

> Hi,
> when trying to extend a ceph disk in ovirt 4 (Virtual Machines => Edit
> Virtual Machine => Instance images => Edit => Extend size by) I get the
> following error:
>
> Error while executing action: interface is required
>

Sounds like a similar root cause of
https://bugzilla.redhat.com/show_bug.cgi?id=1346887
Should be already fixed on latest build. Can you please try to upgrade to
latest?

Or, try using the Edit disk dialog under 'VMs => Disks' instead (could be a
specific issue with the 'Instance images' flow).


>
> In engine.log I see the following errors as well:
>
> 2016-07-21 15:14:55,266 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (default task-35) [] Correlation ID: 47ce3344, Call Stack: null, Custom
> Event ID: -1, Message: Failed to update VM test01 disk test01_Disk1
> (User: admin@internal-authz).
> 2016-07-21 15:14:56,091 ERROR
> [org.ovirt.engine.core.bll.storage.disk.cinder.ExtendCinderDiskCommandCallback]
> (DefaultQuartzScheduler8) [2819eb7c] Failed extending disk. ID:
> a5dd90b1-3a76-4e38-af8c-e829b3b86a40
> 2016-07-21 15:14:56,124 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (DefaultQuartzScheduler8) [2819eb7c] Correlation ID: 2819eb7c, Call
> Stack: null, Custom Event ID: -1, Message: Failed to extend size of the
> disk 'test01_Disk1' to 20 GB, User: admin@internal-authz.
> 2016-07-21 15:14:56,209 ERROR
> [org.ovirt.engine.core.bll.storage.disk.cinder.ExtendCinderDiskCommand]
> (DefaultQuartzScheduler8) [2819eb7c] Ending command
> 'org.ovirt.engine.core.bll.storage.disk.cinder.ExtendCinderDiskCommand'
> with failure.
>
>
> After this, the cinder image is flagged as illegal and I can just delete
> it.
> Extending the image on the cinder side is possible, and the command
> "cinder extend " works, but then the new size is not properly
> reported back in ovirt.
> Any clue?
> Thanks,
>
> Alessandro
>
> ___
> 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] Exporting VMs using cinder disks and importing ceph disks from cinder

[Alessandro De Salvo]

Hi Nir,

On Thu, 2016-07-21 at 17:25 +0300, Nir Soffer wrote:
> On Thu, Jul 21, 2016 at 4:58 PM, Alessandro De Salvo
>  wrote:
> > Hi,
> > I'm trying to export VMs using ceph disks on ovirt 4. The export itself
> > works, but the disks are not saved in the export domains, only the VM
> > definition is stored. Also, I cannot easily re-import them, unless I
> > clone the VM instead of importing it, it just fails.
> > Cinder itself can backup volumes, if instructed to do so.
> > However, let's say I would like to export the machine from an ovirt
> > infrastructure and load it into another one passing by the export domain
> > and sharing the same underlying ceph cluster. I could easily load the VM
> > from the export domain into the second ovirt infrastructure, but how can
> > I define the disk, whose volume exists in the cinder instance, in the
> > second ovirt? I do not see any obvious way to map an existing cinder
> > volume into ovirt, without creating a new disk, which would not be
> > helpful.
> > As a consequence of all this, in case of problems with the disks, there
> > is no way to recover them.
> > Any help?
> 
> We do not support copying, moving, or exporting disks to/from ceph yet.
> 
> You can copy the disks manually from ceph using ceph command line
> tools, and qemu-img should also handle them.

Yes, I just found a trick to re-import the disk, using qemu-img to dump
the image on a file from rbd:/, create a new disk in ovirt
and use qemu-img to copy it back on the new image. Technically it is
working, but it's a bit convoluted. Any plans to add the relevant
support in ovirt?

> 
> After you copy an image, you will a have a raw image that can be
> uploaded to new ovirt disk from engine ui (new image upload feature).

Are you talking to the upload button in the Disks tab? I do not see how
I can upload to cinder/ceph from there. The only way I found was the
trick described above.
Thanks,

Alessandro

> 
> Nir


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

Re: [ovirt-users] Exporting VMs using cinder disks and importing ceph disks from cinder

[Nir Soffer]

On Thu, Jul 21, 2016 at 4:58 PM, Alessandro De Salvo
 wrote:
> Hi,
> I'm trying to export VMs using ceph disks on ovirt 4. The export itself
> works, but the disks are not saved in the export domains, only the VM
> definition is stored. Also, I cannot easily re-import them, unless I
> clone the VM instead of importing it, it just fails.
> Cinder itself can backup volumes, if instructed to do so.
> However, let's say I would like to export the machine from an ovirt
> infrastructure and load it into another one passing by the export domain
> and sharing the same underlying ceph cluster. I could easily load the VM
> from the export domain into the second ovirt infrastructure, but how can
> I define the disk, whose volume exists in the cinder instance, in the
> second ovirt? I do not see any obvious way to map an existing cinder
> volume into ovirt, without creating a new disk, which would not be
> helpful.
> As a consequence of all this, in case of problems with the disks, there
> is no way to recover them.
> Any help?

We do not support copying, moving, or exporting disks to/from ceph yet.

You can copy the disks manually from ceph using ceph command line
tools, and qemu-img should also handle them.

After you copy an image, you will a have a raw image that can be
uploaded to new ovirt disk from engine ui (new image upload feature).

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

[ovirt-users] Snapshot creation using REST API

[Vishal Panchal]

Hello,

I have created a snapshot using Ovirt REST API. After creation in response
I found a link that gives me creation status of snapshot but when I am
using that URL I am getting 404 Error(URL Not Found). I am using
Ovirt version 3 API .

Regards,
*Vishal Panchal*
Software Developer
*+918140283911*

* *
*  

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

[ovirt-users] Exporting VMs using cinder disks and importing ceph disks from cinder

[Alessandro De Salvo]

Hi,
I'm trying to export VMs using ceph disks on ovirt 4. The export itself
works, but the disks are not saved in the export domains, only the VM
definition is stored. Also, I cannot easily re-import them, unless I
clone the VM instead of importing it, it just fails.
Cinder itself can backup volumes, if instructed to do so.
However, let's say I would like to export the machine from an ovirt
infrastructure and load it into another one passing by the export domain
and sharing the same underlying ceph cluster. I could easily load the VM
from the export domain into the second ovirt infrastructure, but how can
I define the disk, whose volume exists in the cinder instance, in the
second ovirt? I do not see any obvious way to map an existing cinder
volume into ovirt, without creating a new disk, which would not be
helpful.
As a consequence of all this, in case of problems with the disks, there
is no way to recover them.
Any help?
Thanks,

Alessandro

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

Re: [ovirt-users] Import of ova failed

[Shahar Havivi]

On 21.07.16 14:38, Cam Mac wrote:
> I tried that already, and it fails. I gave it another try with the GUI on
> the new VM I created, as you described, and it fails.
> I can attach the engine log if you like.
no need,
please file a bug and attach the ova (without the disks - its a tar file that
you can edit)
> 
> Thanks,
> 
> Cam
> 
> On Thu, Jul 21, 2016 at 2:17 PM, Shahar Havivi  wrote:
> 
> > On 21.07.16 14:01, Campbell McLeay wrote:
> > > Thanks Shahar. Will do. I created a new VM on VMWare for the purposes
> > > of testing the import again with a new hostname, and it failed with
> > > the same error.
> > What you are trying to do is as far as I understand is to use virt-v2v
> > utility
> > to put the ova in export domain, there may be something wrong between the
> > virt-v2v output ovf and the oVirt engine.
> > You can try the new feature to import ova strait on oVirt admin portal (if
> > you
> > already try that the forget it), go to the vms tab -> import and select
> > "vmware ova" from the select box...
> >
> > >
> > > Cheers,
> > >
> > > Cam
> > >
> > > On 21 July 2016 at 12:59, Shahar Havivi  wrote:
> > > > On 21.07.16 14:58, Shahar Havivi wrote:
> > > >> The error looks like you have a problem in the storage pool which is
> > null by
> > > >> the log.
> > > >>
> > > >> Please open a bug and specify the exact steps that you took,
> > > >> ie.
> > > >> 1. $ virt-v2v -o rhev ...
> > > >> 2. goto the admin portal and try to view the VMs in the export domain
> > > >> 3. etc...
> > > >>
> > > >> If you can attach the ova without the disk it will be great.
> > > > And please attach the engine.log as well.
> > > >>
> > > >> Shahar.
> > > >>
> > > >> On 21.07.16 10:16, Cam Mac wrote:
> > > >> > Sent, thanks Shahar.
> > > >> >
> > > >> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi 
> > wrote:
> > > >> >
> > > >> > > On 21.07.16 10:03, Cam Mac wrote:
> > > >> > > OK,
> > > >> > > Can you please share the engine.log
> > > >> > > > Hi Shahar,
> > > >> > > >
> > > >> > > > Doesn't appear to be there:
> > > >> > > >
> > > >> > > > engine=> select vm_name from vm_static where vm_name='wvm2';
> > > >> > > >  vm_name
> > > >> > > > -
> > > >> > > > (0 rows)
> > > >> > > >
> > > >> > > > Thanks,
> > > >> > > >
> > > >> > > > Cam
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi <
> > shav...@redhat.com>
> > > >> > > wrote:
> > > >> > > >
> > > >> > > > > On 20.07.16 20:06, Richard W.M. Jones wrote:
> > > >> > > > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > > >> > > > > > > >
> > > >> > > > > > > > The import doesn't happen automatically, you have to do
> > the final
> > > >> > > > > step
> > > >> > > > > > > > manually (when using the command line).  See:
> > > >> > > > > > > >
> > > >> > > > > > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > > >> > > > > > > >
> > > >> > > > > > > > However that error shouldn't happen.  It looks like the
> > name is
> > > >> > > the
> > > >> > > > > > > > same as the name of an existing VM.  From virt-v2v you
> > can do the
> > > >> > > > > > > > whole conversion/import over again, this time adding
> > the `-on
> > > >> > > > > > > > new_name' option to the command line (obviously
> > choosing a name
> > > >> > > which
> > > >> > > > > > > > is not otherwise being used).
> > > >> > > > > > > >
> > > >> > > > > > > > I don't know if there's a way to get oVirt to change
> > the name
> > > >> > > when
> > > >> > > > > > > > importing from the export domain.  As far as I know you
> > have to
> > > >> > > start
> > > >> > > > > > > > the import from scratch.
> > > >> > > > > > > >
> > > >> > > > > > > >
> > > >> > > > > > > There's no existing VM with that name that I can see. It
> > may have
> > > >> > > come
> > > >> > > > > from
> > > >> > > > > > > one of my earlier import attempts,
> > > >> > > > > > > though that earlier attempt did not show up in the GUI,
> > it did
> > > >> > > write
> > > >> > > > > files
> > > >> > > > > > > to the export domain.
> > > >> > > > > > >
> > > >> > > > > > > I re-ran the conversion again with a rename but it failed
> > to
> > > >> > > import it
> > > >> > > > > > > again, with the same error.
> > > >> > > > > > >
> > > >> > > > > > > Could there be a record in the DB somewhere, or does it
> > look at the
> > > >> > > > > files
> > > >> > > > > > > alone? Just trying to work out where the conflict is.
> > > >> > > > > >
> > > >> > > > > > I had a look at the ovirt-engine code where
> > > >> > > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it
> > appears to come
> > > >> > > > > > from a database check.  However I'm not really familiar
> > enough with
> > > >> > > > > > the code to be sure.  Probably best to ask an oVirt
> > developer, or try
> > > >> > > > > > dumping the database to see if "wvm2" appears in a column
> > anywhere.
> > > >> > > > > >
> > > >> > > > > > 

Re: [ovirt-users] Import of ova failed

[Cam Mac]

I tried that already, and it fails. I gave it another try with the GUI on
the new VM I created, as you described, and it fails.
I can attach the engine log if you like.

Thanks,

Cam

On Thu, Jul 21, 2016 at 2:17 PM, Shahar Havivi  wrote:

> On 21.07.16 14:01, Campbell McLeay wrote:
> > Thanks Shahar. Will do. I created a new VM on VMWare for the purposes
> > of testing the import again with a new hostname, and it failed with
> > the same error.
> What you are trying to do is as far as I understand is to use virt-v2v
> utility
> to put the ova in export domain, there may be something wrong between the
> virt-v2v output ovf and the oVirt engine.
> You can try the new feature to import ova strait on oVirt admin portal (if
> you
> already try that the forget it), go to the vms tab -> import and select
> "vmware ova" from the select box...
>
> >
> > Cheers,
> >
> > Cam
> >
> > On 21 July 2016 at 12:59, Shahar Havivi  wrote:
> > > On 21.07.16 14:58, Shahar Havivi wrote:
> > >> The error looks like you have a problem in the storage pool which is
> null by
> > >> the log.
> > >>
> > >> Please open a bug and specify the exact steps that you took,
> > >> ie.
> > >> 1. $ virt-v2v -o rhev ...
> > >> 2. goto the admin portal and try to view the VMs in the export domain
> > >> 3. etc...
> > >>
> > >> If you can attach the ova without the disk it will be great.
> > > And please attach the engine.log as well.
> > >>
> > >> Shahar.
> > >>
> > >> On 21.07.16 10:16, Cam Mac wrote:
> > >> > Sent, thanks Shahar.
> > >> >
> > >> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi 
> wrote:
> > >> >
> > >> > > On 21.07.16 10:03, Cam Mac wrote:
> > >> > > OK,
> > >> > > Can you please share the engine.log
> > >> > > > Hi Shahar,
> > >> > > >
> > >> > > > Doesn't appear to be there:
> > >> > > >
> > >> > > > engine=> select vm_name from vm_static where vm_name='wvm2';
> > >> > > >  vm_name
> > >> > > > -
> > >> > > > (0 rows)
> > >> > > >
> > >> > > > Thanks,
> > >> > > >
> > >> > > > Cam
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi <
> shav...@redhat.com>
> > >> > > wrote:
> > >> > > >
> > >> > > > > On 20.07.16 20:06, Richard W.M. Jones wrote:
> > >> > > > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > >> > > > > > > >
> > >> > > > > > > > The import doesn't happen automatically, you have to do
> the final
> > >> > > > > step
> > >> > > > > > > > manually (when using the command line).  See:
> > >> > > > > > > >
> > >> > > > > > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > >> > > > > > > >
> > >> > > > > > > > However that error shouldn't happen.  It looks like the
> name is
> > >> > > the
> > >> > > > > > > > same as the name of an existing VM.  From virt-v2v you
> can do the
> > >> > > > > > > > whole conversion/import over again, this time adding
> the `-on
> > >> > > > > > > > new_name' option to the command line (obviously
> choosing a name
> > >> > > which
> > >> > > > > > > > is not otherwise being used).
> > >> > > > > > > >
> > >> > > > > > > > I don't know if there's a way to get oVirt to change
> the name
> > >> > > when
> > >> > > > > > > > importing from the export domain.  As far as I know you
> have to
> > >> > > start
> > >> > > > > > > > the import from scratch.
> > >> > > > > > > >
> > >> > > > > > > >
> > >> > > > > > > There's no existing VM with that name that I can see. It
> may have
> > >> > > come
> > >> > > > > from
> > >> > > > > > > one of my earlier import attempts,
> > >> > > > > > > though that earlier attempt did not show up in the GUI,
> it did
> > >> > > write
> > >> > > > > files
> > >> > > > > > > to the export domain.
> > >> > > > > > >
> > >> > > > > > > I re-ran the conversion again with a rename but it failed
> to
> > >> > > import it
> > >> > > > > > > again, with the same error.
> > >> > > > > > >
> > >> > > > > > > Could there be a record in the DB somewhere, or does it
> look at the
> > >> > > > > files
> > >> > > > > > > alone? Just trying to work out where the conflict is.
> > >> > > > > >
> > >> > > > > > I had a look at the ovirt-engine code where
> > >> > > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it
> appears to come
> > >> > > > > > from a database check.  However I'm not really familiar
> enough with
> > >> > > > > > the code to be sure.  Probably best to ask an oVirt
> developer, or try
> > >> > > > > > dumping the database to see if "wvm2" appears in a column
> anywhere.
> > >> > > > > >
> > >> > > > > > Rich.
> > >> > > > > >
> > >> > > > > > --
> > >> > > > > > Richard Jones, Virtualization Group, Red Hat
> > >> > > > > http://people.redhat.com/~rjones
> > >> > > > > > Read my programming and virtualization blog:
> > >> > > http://rwmj.wordpress.com
> > >> > > > > > Fedora Windows cross-compiler. Compile Windows programs,
> test, and
> > >> > > > > > build Windows installers. Over 100 libraries supported.

[ovirt-users] Error while extending a cinder/ceph disk

[Alessandro De Salvo]

Hi,
when trying to extend a ceph disk in ovirt 4 (Virtual Machines => Edit
Virtual Machine => Instance images => Edit => Extend size by) I get the
following error:

Error while executing action: interface is required

In engine.log I see the following errors as well:

2016-07-21 15:14:55,266 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-35) [] Correlation ID: 47ce3344, Call Stack: null, Custom
Event ID: -1, Message: Failed to update VM test01 disk test01_Disk1
(User: admin@internal-authz).
2016-07-21 15:14:56,091 ERROR
[org.ovirt.engine.core.bll.storage.disk.cinder.ExtendCinderDiskCommandCallback] 
(DefaultQuartzScheduler8) [2819eb7c] Failed extending disk. ID: 
a5dd90b1-3a76-4e38-af8c-e829b3b86a40
2016-07-21 15:14:56,124 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler8) [2819eb7c] Correlation ID: 2819eb7c, Call
Stack: null, Custom Event ID: -1, Message: Failed to extend size of the
disk 'test01_Disk1' to 20 GB, User: admin@internal-authz.
2016-07-21 15:14:56,209 ERROR
[org.ovirt.engine.core.bll.storage.disk.cinder.ExtendCinderDiskCommand]
(DefaultQuartzScheduler8) [2819eb7c] Ending command
'org.ovirt.engine.core.bll.storage.disk.cinder.ExtendCinderDiskCommand'
with failure.


After this, the cinder image is flagged as illegal and I can just delete
it.
Extending the image on the cinder side is possible, and the command
"cinder extend " works, but then the new size is not properly
reported back in ovirt.
Any clue?
Thanks,

Alessandro

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

Re: [ovirt-users] stuck host in hosted engine migration 3.6->4.0

[Martin Perina]

So could you please share logs?

Thanks

Martin

On Thu, Jul 21, 2016 at 3:17 PM, Gervais de Montbrun  wrote:

> Hi Oved,
>
> Thanks for the suggestion.
>
> I tried setting "management_ip = 0.0.0.0" but same result.
> BTW, management_ip='0.0.0.0' (as suggested in the post) doesn't work for
> me. vdsmd wouldn't start.
>
> Cheers,
> Gervais
>
>
>
> On Jul 20, 2016, at 10:50 AM, Oved Ourfali  wrote:
>
> Also, this thread seems similar.
> Also talking about IPV4/IPV6 issue.
> Does it help?
>
> [1] http://lists.ovirt.org/pipermail/users/2016-June/040602.html
>
> On Wed, Jul 20, 2016 at 4:43 PM, Martin Perina  wrote:
>
>> Hi,
>>
>> could you please create a bug and attach engine host logs (all from
>> /var/log/ovirt-engine) and VDSM logs (from /var/log/vdsm)?
>>
>> Thanks
>>
>> Martin Perina
>>
>>
>> On Wed, Jul 20, 2016 at 1:50 PM, Gervais de Montbrun <
>> gerv...@demontbrun.com
>> > wrote:
>>
>> > Hi Qiong,
>> >
>> > I am experiencing the exact same issue. All four of my hosts are
>> throwing
>> > the same error to the vdsm.log If you find a solution, please let me
>> know
>>
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt 3.6.6 and gluster 3.7.13

[Scott]

I get similar problems with oVirt 4.0.1 and hosted engine.  After upgrading
all my hosts to Gluster 3.7.13 (client and server), I get the following:

$ sudo hosted-engine --set-maintenance --mode=none
Traceback (most recent call last):
  File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
line 73, in 
if not maintenance.set_mode(sys.argv[1]):
  File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
line 61, in set_mode
value=m_global,
  File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
line 259, in set_maintenance_mode
str(value))
  File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
line 204, in set_global_md_flag
all_stats = broker.get_stats_from_storage(service)
  File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
line 232, in get_stats_from_storage
result = self._checked_communicate(request)
  File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
line 260, in _checked_communicate
.format(message or response))
ovirt_hosted_engine_ha.lib.exceptions.RequestError: Request failed: failed
to read metadata: [Errno 1] Operation not permitted

If I only upgrade one host, then things will continue to work but my nodes
are constantly healing shards.  My logs are also flooded with:

[2016-07-21 13:15:14.137734] W [fuse-bridge.c:2227:fuse_readv_cbk]
0-glusterfs-fuse: 274714: READ => -1 gfid=4
41f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
permitted)
The message "W [MSGID: 114031] [client-rpc-fops.c:3050:client3_3_readv_cbk]
0-data-client-0: remote operation failed [Operation not permitted]"
repeated 6 times between [2016-07-21 13:13:24.134985] and [2016-07-21
13:15:04.132226]
The message "W [MSGID: 114031] [client-rpc-fops.c:3050:client3_3_readv_cbk]
0-data-client-1: remote operation failed [Operation not permitted]"
repeated 8 times between [2016-07-21 13:13:34.133116] and [2016-07-21
13:15:14.137178]
The message "W [MSGID: 114031] [client-rpc-fops.c:3050:client3_3_readv_cbk]
0-data-client-2: remote operation failed [Operation not permitted]"
repeated 7 times between [2016-07-21 13:13:24.135071] and [2016-07-21
13:15:14.137666]
[2016-07-21 13:15:24.134647] W [MSGID: 114031]
[client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-0: remote
operation failed [Operation not permitted]
[2016-07-21 13:15:24.134764] W [MSGID: 114031]
[client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-2: remote
operation failed [Operation not permitted]
[2016-07-21 13:15:24.134793] W [fuse-bridge.c:2227:fuse_readv_cbk]
0-glusterfs-fuse: 274741: READ => -1
gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0038f4 (Operation not
permitted)
[2016-07-21 13:15:34.135413] W [fuse-bridge.c:2227:fuse_readv_cbk]
0-glusterfs-fuse: 274756: READ => -1
gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
permitted)
[2016-07-21 13:15:44.141062] W [fuse-bridge.c:2227:fuse_readv_cbk]
0-glusterfs-fuse: 274818: READ => -1
gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0038f4 (Operation not
permitted)
[2016-07-21 13:15:54.133582] W [MSGID: 114031]
[client-rpc-fops.c:3050:client3_3_readv_cbk] 0-data-client-1: remote
operation failed [Operation not permitted]
[2016-07-21 13:15:54.133629] W [fuse-bridge.c:2227:fuse_readv_cbk]
0-glusterfs-fuse: 274853: READ => -1
gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0036d8 (Operation not
permitted)
[2016-07-21 13:16:04.133666] W [fuse-bridge.c:2227:fuse_readv_cbk]
0-glusterfs-fuse: 274879: READ => -1
gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0041d0 (Operation not
permitted)
[2016-07-21 13:16:14.134954] W [fuse-bridge.c:2227:fuse_readv_cbk]
0-glusterfs-fuse: 274894: READ => -1
gfid=441f2789-f6b1-4918-a280-1b9905a11429 fd=0x7f19bc0036d8 (Operation not
permitted)

Scott


On Thu, Jul 21, 2016 at 6:57 AM Frank Rothenstein <
f.rothenst...@bodden-kliniken.de> wrote:

> Hey Devid,
>
> I have the very same problem on my test-cluster, despite on running ovirt
> 4.0.
> If you access your volumes via NFS all is fine, problem is FUSE. I stayed
> on 3.7.13, but have no solution yet, now I use NFS.
>
> Frank
>
> Am Donnerstag, den 21.07.2016, 04:28 -0500 schrieb David Gossage:
>
> Anyone running one of recent 3.6.x lines and gluster using 3.7.13?  I am
> looking to upgrade gluster from 3.7.11->3.7.13 for some bug fixes, but have
> been told by users on gluster mail list due to some gluster changes I'd
> need to change the disk parameters to use writeback cache.  Something to do
> with aio support being removed.
>
> I believe this could be done with custom parameters?  But I believe strage
> tests are done using dd and would they fail with current 

Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

[Martin Perina]

Thanks a lot for you effort, I'm glad that you were able to upgrade
successfully although we were not able to find the cause for the issue :-(

On Thu, Jul 21, 2016 at 2:30 PM,  wrote:

> So I gave it another try and this time it worked without any issue (with
> 4.0.1.1 version). Strange, maybe the first upgrade failure left system in a
> weird state? Anyhow almost everything ([1]) is working fine now. Thanks for
> the help!
>
>   [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1358737
>

​Adding Tomas about this one
​


>
> El 2016-07-20 20:23, Martin Perina escribió:
>
>> On Wed, Jul 20, 2016 at 6:18 PM, Nicolás  wrote:
>>
>> El 20/07/16 a las 16:45, Martin Perina escribió:
>>>
>>> On Wed, Jul 20, 2016 at 4:44 PM, Nicolás  wrote:
>>>
>>> Hi Martin,
>>>
>>> Actually, up until now we had that cert configured in httpd and in
>>> websocket proxy. Seems that now in 4.0.x it's not enough, as opening
>>> the https://fqdn [1] complains about the cert not being imported in
>>> the key chain.
>>>
>>> ​Yes, there's an updated procedure on using external CA in 4.0,
>>> for details please take a look at Doc Text in
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1336838 [2]
>>> ​
>>> So I imported it via keytool, but I don't want to use it in the
>>> engine <-> VDSM communication.
>>>
>>> ​Hmm, so that would imply that we have some issue with existing
>>> internal enigne CA during upgrade ...
>>>
>>> The strange thing is that we test upgrades a lot but so far we
>>> haven't seen any issues which will broke
>>>
>>> SSL setup between engine and VDSM. You said that you had to
>>> downgrade back to 3.6.7 (so unfortunately for us we cannot
>>> investigate your nonworking setup more), but how did you do that?
>>>
>>> Removing all engine packages and configuration​, installing back
>>> 3.6.7 packaging and restoring configuration form backup?
>>>
>>> I'm asking to know what changed in your setup between not working
>>> 4.0 and working 3.6.7 ...
>>>
>>
>>  Indeed, those are the steps I followed to the point.
>>
>>  To add more strangeness, previously to upgrading this oVirt
>> infrastructure, we upgraded another one that we have (also using own
>> cert, a different one but from the same CA) and everything went
>> smoothly. And what's more, previously to upgrading the engine that
>> failed, I created a copy of that engine machine in a sandbox
>> environment to see if upgrade process would or not success, and it
>> worked perfectly.
>>
>>  The only difference between the sandbox and the real machine's
>> process was that when upgrading the real one, the first time I run
>> "engine-setup" it failed because 'systemd' reported PostgreSQL as it
>> was not running (actually it was, thougg), so everything rolled back.
>> I had to kill the PostgreSQL process, start it again with systemctl
>> and then run "engine-setup", where the process completed successfully
>> but the SSL issue appeared. Not sure if this rollback could have
>> shattered the whole thing...
>>
>>  Anyhow, tomorrow I'm going to create another copy of the engine
>> machine to a sandbox environment and try again. If it works I'll cross
>> my fingers and give another try on the real machine...
>>
>>  Thanks!
>>
>> ​Thanks a lot for you effort. I will try to perform same upgrade
>> tomorrow in my test env.
>> ​
>>
>> Thanks
>>>
>>> Martin
>>>
>>> Thanks!
>>> En 20/7/2016 2:48 p. m., Martin Perina 
>>> escribió:
>>>
>>> Hi,
>>>
>>> sorry for late response, I overlook your reply :-(
>>>
>>> ​I looked at your logs and it seems to me that​ there's SSL
>>> error when engine tries to contact VDSM.
>>>
>>> ​You have mentioned that your are using your own custom CA. ​Are
>>> you using it only for HTTPS certificate or do you want to use it
>>> also for Engine <-> VDSM communication?
>>> ​
>>>
>>> Martin Perina
>>>
>>>
>>>
>>> On Wed, Jul 20, 2016 at 9:18 AM,  wrote:
>>> Any hints about this?
>>>
>>> El 2016-07-13 11:13, nico...@devels.es escribió:
>>> Hi,
>>>
>>> Unfortunately, upgrading to 4.0.1RC didn't solve the problem.
>>> Actually, the error changed to 'General SSLEngine problem', but the
>>> result was the same, like this:
>>>
>>> 2016-07-13 09:52:22,010 INFO
>>> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
>>> Reactor) [] Connecting to /10.X.X.X
>>> 2016-07-13 09:52:22,018 ERROR
>>> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp
>>> Reactor)
>>> [] Unable to process messages: General SSLEngine problem
>>>
>>> It's worth mentioning that we're using our own SSL certificates
>>> (not
>>> self-signed), and I imported the combined certificate into the
>>> /etc/pki/ovirt-engine/.truststore key file. Not sure if related,
>>> but
>>> just in case.
>>>
>>
>> I had to downgrade to 3.6.7. I'm attaching requested logs, if you
>>> need
>>> anything else don't hesitate to ask.
>>>
>>> Regards.
>>>
>>> El 2016-07-13 09:45, Martin Perina escribió:
>>> Hi,

Re: [ovirt-users] Import of ova failed

[Shahar Havivi]

On 21.07.16 14:01, Campbell McLeay wrote:
> Thanks Shahar. Will do. I created a new VM on VMWare for the purposes
> of testing the import again with a new hostname, and it failed with
> the same error.
What you are trying to do is as far as I understand is to use virt-v2v utility
to put the ova in export domain, there may be something wrong between the
virt-v2v output ovf and the oVirt engine.
You can try the new feature to import ova strait on oVirt admin portal (if you
already try that the forget it), go to the vms tab -> import and select
"vmware ova" from the select box...

> 
> Cheers,
> 
> Cam
> 
> On 21 July 2016 at 12:59, Shahar Havivi  wrote:
> > On 21.07.16 14:58, Shahar Havivi wrote:
> >> The error looks like you have a problem in the storage pool which is null 
> >> by
> >> the log.
> >>
> >> Please open a bug and specify the exact steps that you took,
> >> ie.
> >> 1. $ virt-v2v -o rhev ...
> >> 2. goto the admin portal and try to view the VMs in the export domain
> >> 3. etc...
> >>
> >> If you can attach the ova without the disk it will be great.
> > And please attach the engine.log as well.
> >>
> >> Shahar.
> >>
> >> On 21.07.16 10:16, Cam Mac wrote:
> >> > Sent, thanks Shahar.
> >> >
> >> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi  
> >> > wrote:
> >> >
> >> > > On 21.07.16 10:03, Cam Mac wrote:
> >> > > OK,
> >> > > Can you please share the engine.log
> >> > > > Hi Shahar,
> >> > > >
> >> > > > Doesn't appear to be there:
> >> > > >
> >> > > > engine=> select vm_name from vm_static where vm_name='wvm2';
> >> > > >  vm_name
> >> > > > -
> >> > > > (0 rows)
> >> > > >
> >> > > > Thanks,
> >> > > >
> >> > > > Cam
> >> > > >
> >> > > >
> >> > > >
> >> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi 
> >> > > wrote:
> >> > > >
> >> > > > > On 20.07.16 20:06, Richard W.M. Jones wrote:
> >> > > > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> >> > > > > > > >
> >> > > > > > > > The import doesn't happen automatically, you have to do the 
> >> > > > > > > > final
> >> > > > > step
> >> > > > > > > > manually (when using the command line).  See:
> >> > > > > > > >
> >> > > > > > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> >> > > > > > > >
> >> > > > > > > > However that error shouldn't happen.  It looks like the name 
> >> > > > > > > > is
> >> > > the
> >> > > > > > > > same as the name of an existing VM.  From virt-v2v you can 
> >> > > > > > > > do the
> >> > > > > > > > whole conversion/import over again, this time adding the `-on
> >> > > > > > > > new_name' option to the command line (obviously choosing a 
> >> > > > > > > > name
> >> > > which
> >> > > > > > > > is not otherwise being used).
> >> > > > > > > >
> >> > > > > > > > I don't know if there's a way to get oVirt to change the name
> >> > > when
> >> > > > > > > > importing from the export domain.  As far as I know you have 
> >> > > > > > > > to
> >> > > start
> >> > > > > > > > the import from scratch.
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > There's no existing VM with that name that I can see. It may 
> >> > > > > > > have
> >> > > come
> >> > > > > from
> >> > > > > > > one of my earlier import attempts,
> >> > > > > > > though that earlier attempt did not show up in the GUI, it did
> >> > > write
> >> > > > > files
> >> > > > > > > to the export domain.
> >> > > > > > >
> >> > > > > > > I re-ran the conversion again with a rename but it failed to
> >> > > import it
> >> > > > > > > again, with the same error.
> >> > > > > > >
> >> > > > > > > Could there be a record in the DB somewhere, or does it look 
> >> > > > > > > at the
> >> > > > > files
> >> > > > > > > alone? Just trying to work out where the conflict is.
> >> > > > > >
> >> > > > > > I had a look at the ovirt-engine code where
> >> > > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to 
> >> > > > > > come
> >> > > > > > from a database check.  However I'm not really familiar enough 
> >> > > > > > with
> >> > > > > > the code to be sure.  Probably best to ask an oVirt developer, 
> >> > > > > > or try
> >> > > > > > dumping the database to see if "wvm2" appears in a column 
> >> > > > > > anywhere.
> >> > > > > >
> >> > > > > > Rich.
> >> > > > > >
> >> > > > > > --
> >> > > > > > Richard Jones, Virtualization Group, Red Hat
> >> > > > > http://people.redhat.com/~rjones
> >> > > > > > Read my programming and virtualization blog:
> >> > > http://rwmj.wordpress.com
> >> > > > > > Fedora Windows cross-compiler. Compile Windows programs, test, 
> >> > > > > > and
> >> > > > > > build Windows installers. Over 100 libraries supported.
> >> > > > > > http://fedoraproject.org/wiki/MinGW
> >> > > > > It may be in the DB...
> >> > > > > Try to run this via psql:
> >> > > > >
> >> > > > > select vm_name from vm_static where vm_name='wvm2';
> >> > > > >
> >> > > > > and see if there is a result...
> >> > > > >
> >> > >
> > 

Re: [ovirt-users] stuck host in hosted engine migration 3.6->4.0

[Gervais de Montbrun]

Hi Oved,

Thanks for the suggestion.

I tried setting "management_ip = 0.0.0.0" but same result.
BTW, management_ip='0.0.0.0' (as suggested in the post) doesn't work for me. 
vdsmd wouldn't start.

Cheers,
Gervais



> On Jul 20, 2016, at 10:50 AM, Oved Ourfali  wrote:
> 
> Also, this thread seems similar.
> Also talking about IPV4/IPV6 issue.
> Does it help?
> 
> [1] http://lists.ovirt.org/pipermail/users/2016-June/040602.html 
> 
> 
> On Wed, Jul 20, 2016 at 4:43 PM, Martin Perina  > wrote:
> Hi,
> 
> could you please create a bug and attach engine host logs (all from
> /var/log/ovirt-engine) and VDSM logs (from /var/log/vdsm)?
> 
> Thanks
> 
> Martin Perina
> 
> 
> On Wed, Jul 20, 2016 at 1:50 PM, Gervais de Montbrun  
> > wrote:
> 
> > Hi Qiong,
> >
> > I am experiencing the exact same issue. All four of my hosts are throwing
> > the same error to the vdsm.log If you find a solution, please let me know
> 

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

Re: [ovirt-users] Import of ova failed

[Campbell McLeay]

Thanks Shahar. Will do. I created a new VM on VMWare for the purposes
of testing the import again with a new hostname, and it failed with
the same error.

Cheers,

Cam

On 21 July 2016 at 12:59, Shahar Havivi  wrote:
> On 21.07.16 14:58, Shahar Havivi wrote:
>> The error looks like you have a problem in the storage pool which is null by
>> the log.
>>
>> Please open a bug and specify the exact steps that you took,
>> ie.
>> 1. $ virt-v2v -o rhev ...
>> 2. goto the admin portal and try to view the VMs in the export domain
>> 3. etc...
>>
>> If you can attach the ova without the disk it will be great.
> And please attach the engine.log as well.
>>
>> Shahar.
>>
>> On 21.07.16 10:16, Cam Mac wrote:
>> > Sent, thanks Shahar.
>> >
>> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi  wrote:
>> >
>> > > On 21.07.16 10:03, Cam Mac wrote:
>> > > OK,
>> > > Can you please share the engine.log
>> > > > Hi Shahar,
>> > > >
>> > > > Doesn't appear to be there:
>> > > >
>> > > > engine=> select vm_name from vm_static where vm_name='wvm2';
>> > > >  vm_name
>> > > > -
>> > > > (0 rows)
>> > > >
>> > > > Thanks,
>> > > >
>> > > > Cam
>> > > >
>> > > >
>> > > >
>> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi 
>> > > wrote:
>> > > >
>> > > > > On 20.07.16 20:06, Richard W.M. Jones wrote:
>> > > > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
>> > > > > > > >
>> > > > > > > > The import doesn't happen automatically, you have to do the 
>> > > > > > > > final
>> > > > > step
>> > > > > > > > manually (when using the command line).  See:
>> > > > > > > >
>> > > > > > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
>> > > > > > > >
>> > > > > > > > However that error shouldn't happen.  It looks like the name is
>> > > the
>> > > > > > > > same as the name of an existing VM.  From virt-v2v you can do 
>> > > > > > > > the
>> > > > > > > > whole conversion/import over again, this time adding the `-on
>> > > > > > > > new_name' option to the command line (obviously choosing a name
>> > > which
>> > > > > > > > is not otherwise being used).
>> > > > > > > >
>> > > > > > > > I don't know if there's a way to get oVirt to change the name
>> > > when
>> > > > > > > > importing from the export domain.  As far as I know you have to
>> > > start
>> > > > > > > > the import from scratch.
>> > > > > > > >
>> > > > > > > >
>> > > > > > > There's no existing VM with that name that I can see. It may have
>> > > come
>> > > > > from
>> > > > > > > one of my earlier import attempts,
>> > > > > > > though that earlier attempt did not show up in the GUI, it did
>> > > write
>> > > > > files
>> > > > > > > to the export domain.
>> > > > > > >
>> > > > > > > I re-ran the conversion again with a rename but it failed to
>> > > import it
>> > > > > > > again, with the same error.
>> > > > > > >
>> > > > > > > Could there be a record in the DB somewhere, or does it look at 
>> > > > > > > the
>> > > > > files
>> > > > > > > alone? Just trying to work out where the conflict is.
>> > > > > >
>> > > > > > I had a look at the ovirt-engine code where
>> > > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to 
>> > > > > > come
>> > > > > > from a database check.  However I'm not really familiar enough with
>> > > > > > the code to be sure.  Probably best to ask an oVirt developer, or 
>> > > > > > try
>> > > > > > dumping the database to see if "wvm2" appears in a column anywhere.
>> > > > > >
>> > > > > > Rich.
>> > > > > >
>> > > > > > --
>> > > > > > Richard Jones, Virtualization Group, Red Hat
>> > > > > http://people.redhat.com/~rjones
>> > > > > > Read my programming and virtualization blog:
>> > > http://rwmj.wordpress.com
>> > > > > > Fedora Windows cross-compiler. Compile Windows programs, test, and
>> > > > > > build Windows installers. Over 100 libraries supported.
>> > > > > > http://fedoraproject.org/wiki/MinGW
>> > > > > It may be in the DB...
>> > > > > Try to run this via psql:
>> > > > >
>> > > > > select vm_name from vm_static where vm_name='wvm2';
>> > > > >
>> > > > > and see if there is a result...
>> > > > >
>> > >
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users



-- 
Campbell McLeay · Senior Systems Administrator

London · New York · Los Angeles · Montréal
T  +44 (0)20 7344 8000
19-23 Wells Street, London W1T 3PQ
Twitter · Facebook · framestore.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

[nicolas]

So I gave it another try and this time it worked without any issue (with 
4.0.1.1 version). Strange, maybe the first upgrade failure left system 
in a weird state? Anyhow almost everything ([1]) is working fine now. 
Thanks for the help!


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

El 2016-07-20 20:23, Martin Perina escribió:

On Wed, Jul 20, 2016 at 6:18 PM, Nicolás  wrote:


El 20/07/16 a las 16:45, Martin Perina escribió:

On Wed, Jul 20, 2016 at 4:44 PM, Nicolás  wrote:

Hi Martin,

Actually, up until now we had that cert configured in httpd and in
websocket proxy. Seems that now in 4.0.x it's not enough, as opening
the https://fqdn [1] complains about the cert not being imported in
the key chain.

​Yes, there's an updated procedure on using external CA in 4.0,
for details please take a look at Doc Text in

https://bugzilla.redhat.com/show_bug.cgi?id=1336838 [2]
​  
So I imported it via keytool, but I don't want to use it in the
engine <-> VDSM communication.

​Hmm, so that would imply that we have some issue with existing
internal enigne CA during upgrade ...

The strange thing is that we test upgrades a lot but so far we
haven't seen any issues which will broke

SSL setup between engine and VDSM. You said that you had to
downgrade back to 3.6.7 (so unfortunately for us we cannot
investigate your nonworking setup more), but how did you do that?

Removing all engine packages and configuration​, installing back
3.6.7 packaging and restoring configuration form backup?

I'm asking to know what changed in your setup between not working
4.0 and working 3.6.7 ...


 Indeed, those are the steps I followed to the point.

 To add more strangeness, previously to upgrading this oVirt
infrastructure, we upgraded another one that we have (also using own
cert, a different one but from the same CA) and everything went
smoothly. And what's more, previously to upgrading the engine that
failed, I created a copy of that engine machine in a sandbox
environment to see if upgrade process would or not success, and it
worked perfectly.

 The only difference between the sandbox and the real machine's
process was that when upgrading the real one, the first time I run
"engine-setup" it failed because 'systemd' reported PostgreSQL as it
was not running (actually it was, thougg), so everything rolled back.
I had to kill the PostgreSQL process, start it again with systemctl
and then run "engine-setup", where the process completed successfully
but the SSL issue appeared. Not sure if this rollback could have
shattered the whole thing...

 Anyhow, tomorrow I'm going to create another copy of the engine
machine to a sandbox environment and try again. If it works I'll cross
my fingers and give another try on the real machine...

 Thanks!

​Thanks a lot for you effort. I will try to perform same upgrade
tomorrow in my test env.
​ 


Thanks

Martin

Thanks!
En 20/7/2016 2:48 p. m., Martin Perina 
escribió:

Hi,

sorry for late response, I overlook your reply :-(

​I looked at your logs and it seems to me that​ there's SSL
error when engine tries to contact VDSM.

​You have mentioned that your are using your own custom CA. ​Are
you using it only for HTTPS certificate or do you want to use it
also for Engine <-> VDSM communication?
​

Martin Perina

 

On Wed, Jul 20, 2016 at 9:18 AM,  wrote:
Any hints about this?

El 2016-07-13 11:13, nico...@devels.es escribió:
Hi,

Unfortunately, upgrading to 4.0.1RC didn't solve the problem.
Actually, the error changed to 'General SSLEngine problem', but the
result was the same, like this:

2016-07-13 09:52:22,010 INFO
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
Reactor) [] Connecting to /10.X.X.X
2016-07-13 09:52:22,018 ERROR
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp
Reactor)
[] Unable to process messages: General SSLEngine problem

It's worth mentioning that we're using our own SSL certificates
(not
self-signed), and I imported the combined certificate into the
/etc/pki/ovirt-engine/.truststore key file. Not sure if related,
but
just in case.



I had to downgrade to 3.6.7. I'm attaching requested logs, if you
need
anything else don't hesitate to ask.

Regards.

El 2016-07-13 09:45, Martin Perina escribió:
Hi,

could you please share also vdsm.log from your hosts and also
server.log and setup logs from /var/log/ovirt-engine/setup
directory?

Thanks

Martin Perina

On Wed, Jul 13, 2016 at 10:36 AM,  wrote:

Hi,

We upgraded from 3.6.6 to 4.0.0 and we have a big issue since the
engine cannot connect to hosts. In the logs all we see is this
error:

    ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL
Stomp Reactor) [] Unable to process messages

I'm attaching full logs.

Could someone help please?

Thanks.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users [3] [1]

[ovirt-users] [ANN] oVirt 4.0.2 Release Candidate is now available

[Sandro Bonazzola]

The oVirt Project is pleased to announce the availability of the First
Release Candidate of oVirt 4.0.2 for testing, as of July 21st, 2016.

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

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.2 or later
* CentOS Linux (or similar) 7.2 or later
* Fedora 23 (tech preview)
* oVirt Next Generation Node 4.0

This is pre-release software. Please take a look at our community page[1]
to know how to ask questions and interact with developers and users.
All issues or bugs should be reported via oVirt Bugzilla[2].
This pre-release should not to be used in production.

This update is the first release candidate of the second in a series of
stabilization updates to the 4.0 series.
4.0.2 brings 5 enhancements and nearly 100 bugfixes, including 38 high or
urgent severity fixes, on top of oVirt 4.0 series
See the release notes [3] for installation / upgrade instructions and a
list of new features and bugs fixed.

Notes:
* A new oVirt Live ISO is available. [4]
* A new oVirt Next Generation Node is available [4].
* A new oVirt Engine Appliance is already available.
* Mirrors[5] might need up to one day to synchronize.

Additional Resources:
* Read more about the oVirt 4.0.2 release highlights:
http://www.ovirt.org/release/4.0.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.0.2/
[4] http://resources.ovirt.org/pub/ovirt-4.0-pre/iso/
[5] http://www.ovirt.org/Repository_mirrors#Current_mirrors


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Shahar Havivi]

On 21.07.16 14:58, Shahar Havivi wrote:
> The error looks like you have a problem in the storage pool which is null by
> the log.
> 
> Please open a bug and specify the exact steps that you took,
> ie.
> 1. $ virt-v2v -o rhev ...
> 2. goto the admin portal and try to view the VMs in the export domain
> 3. etc...
> 
> If you can attach the ova without the disk it will be great.
And please attach the engine.log as well.
> 
> Shahar.
> 
> On 21.07.16 10:16, Cam Mac wrote:
> > Sent, thanks Shahar.
> > 
> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi  wrote:
> > 
> > > On 21.07.16 10:03, Cam Mac wrote:
> > > OK,
> > > Can you please share the engine.log
> > > > Hi Shahar,
> > > >
> > > > Doesn't appear to be there:
> > > >
> > > > engine=> select vm_name from vm_static where vm_name='wvm2';
> > > >  vm_name
> > > > -
> > > > (0 rows)
> > > >
> > > > Thanks,
> > > >
> > > > Cam
> > > >
> > > >
> > > >
> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi 
> > > wrote:
> > > >
> > > > > On 20.07.16 20:06, Richard W.M. Jones wrote:
> > > > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > > > > > > >
> > > > > > > > The import doesn't happen automatically, you have to do the 
> > > > > > > > final
> > > > > step
> > > > > > > > manually (when using the command line).  See:
> > > > > > > >
> > > > > > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > > > > > > >
> > > > > > > > However that error shouldn't happen.  It looks like the name is
> > > the
> > > > > > > > same as the name of an existing VM.  From virt-v2v you can do 
> > > > > > > > the
> > > > > > > > whole conversion/import over again, this time adding the `-on
> > > > > > > > new_name' option to the command line (obviously choosing a name
> > > which
> > > > > > > > is not otherwise being used).
> > > > > > > >
> > > > > > > > I don't know if there's a way to get oVirt to change the name
> > > when
> > > > > > > > importing from the export domain.  As far as I know you have to
> > > start
> > > > > > > > the import from scratch.
> > > > > > > >
> > > > > > > >
> > > > > > > There's no existing VM with that name that I can see. It may have
> > > come
> > > > > from
> > > > > > > one of my earlier import attempts,
> > > > > > > though that earlier attempt did not show up in the GUI, it did
> > > write
> > > > > files
> > > > > > > to the export domain.
> > > > > > >
> > > > > > > I re-ran the conversion again with a rename but it failed to
> > > import it
> > > > > > > again, with the same error.
> > > > > > >
> > > > > > > Could there be a record in the DB somewhere, or does it look at 
> > > > > > > the
> > > > > files
> > > > > > > alone? Just trying to work out where the conflict is.
> > > > > >
> > > > > > I had a look at the ovirt-engine code where
> > > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to 
> > > > > > come
> > > > > > from a database check.  However I'm not really familiar enough with
> > > > > > the code to be sure.  Probably best to ask an oVirt developer, or 
> > > > > > try
> > > > > > dumping the database to see if "wvm2" appears in a column anywhere.
> > > > > >
> > > > > > Rich.
> > > > > >
> > > > > > --
> > > > > > Richard Jones, Virtualization Group, Red Hat
> > > > > http://people.redhat.com/~rjones
> > > > > > Read my programming and virtualization blog:
> > > http://rwmj.wordpress.com
> > > > > > Fedora Windows cross-compiler. Compile Windows programs, test, and
> > > > > > build Windows installers. Over 100 libraries supported.
> > > > > > http://fedoraproject.org/wiki/MinGW
> > > > > It may be in the DB...
> > > > > Try to run this via psql:
> > > > >
> > > > > select vm_name from vm_static where vm_name='wvm2';
> > > > >
> > > > > and see if there is a result...
> > > > >
> > >
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Shahar Havivi]

The error looks like you have a problem in the storage pool which is null by
the log.

Please open a bug and specify the exact steps that you took,
ie.
1. $ virt-v2v -o rhev ...
2. goto the admin portal and try to view the VMs in the export domain
3. etc...

If you can attach the ova without the disk it will be great.

Shahar.

On 21.07.16 10:16, Cam Mac wrote:
> Sent, thanks Shahar.
> 
> On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi  wrote:
> 
> > On 21.07.16 10:03, Cam Mac wrote:
> > OK,
> > Can you please share the engine.log
> > > Hi Shahar,
> > >
> > > Doesn't appear to be there:
> > >
> > > engine=> select vm_name from vm_static where vm_name='wvm2';
> > >  vm_name
> > > -
> > > (0 rows)
> > >
> > > Thanks,
> > >
> > > Cam
> > >
> > >
> > >
> > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi 
> > wrote:
> > >
> > > > On 20.07.16 20:06, Richard W.M. Jones wrote:
> > > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > > > > > >
> > > > > > > The import doesn't happen automatically, you have to do the final
> > > > step
> > > > > > > manually (when using the command line).  See:
> > > > > > >
> > > > > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > > > > > >
> > > > > > > However that error shouldn't happen.  It looks like the name is
> > the
> > > > > > > same as the name of an existing VM.  From virt-v2v you can do the
> > > > > > > whole conversion/import over again, this time adding the `-on
> > > > > > > new_name' option to the command line (obviously choosing a name
> > which
> > > > > > > is not otherwise being used).
> > > > > > >
> > > > > > > I don't know if there's a way to get oVirt to change the name
> > when
> > > > > > > importing from the export domain.  As far as I know you have to
> > start
> > > > > > > the import from scratch.
> > > > > > >
> > > > > > >
> > > > > > There's no existing VM with that name that I can see. It may have
> > come
> > > > from
> > > > > > one of my earlier import attempts,
> > > > > > though that earlier attempt did not show up in the GUI, it did
> > write
> > > > files
> > > > > > to the export domain.
> > > > > >
> > > > > > I re-ran the conversion again with a rename but it failed to
> > import it
> > > > > > again, with the same error.
> > > > > >
> > > > > > Could there be a record in the DB somewhere, or does it look at the
> > > > files
> > > > > > alone? Just trying to work out where the conflict is.
> > > > >
> > > > > I had a look at the ovirt-engine code where
> > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come
> > > > > from a database check.  However I'm not really familiar enough with
> > > > > the code to be sure.  Probably best to ask an oVirt developer, or try
> > > > > dumping the database to see if "wvm2" appears in a column anywhere.
> > > > >
> > > > > Rich.
> > > > >
> > > > > --
> > > > > Richard Jones, Virtualization Group, Red Hat
> > > > http://people.redhat.com/~rjones
> > > > > Read my programming and virtualization blog:
> > http://rwmj.wordpress.com
> > > > > Fedora Windows cross-compiler. Compile Windows programs, test, and
> > > > > build Windows installers. Over 100 libraries supported.
> > > > > http://fedoraproject.org/wiki/MinGW
> > > > It may be in the DB...
> > > > Try to run this via psql:
> > > >
> > > > select vm_name from vm_static where vm_name='wvm2';
> > > >
> > > > and see if there is a result...
> > > >
> >
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt 3.6.6 and gluster 3.7.13

[Frank Rothenstein]

Hey Devid,

I have the very same problem on my test-cluster, despite on running
ovirt 4.0.
If you access your volumes via NFS all is fine, problem is FUSE. I
stayed on 3.7.13, but have no solution yet, now I use NFS.

Frank
Am Donnerstag, den 21.07.2016, 04:28 -0500 schrieb David Gossage:
> > > > > Anyone running one of recent 3.6.x lines and gluster using 3.7.13?  I
am looking to upgrade gluster from 3.7.11->3.7.13 for some bug fixes,
but have been told by users on gluster mail list due to some gluster
changes I'd need to change the disk parameters to use writeback
cache.  Something to do with aio support being removed.
> > > > > > I believe this could be done with custom parameters?  But I believe
strage tests are done using dd and would they fail with current
settings then? Last upgrade to 3.7.13 I had to rollback to 3.7.11 due
to stability isues where gluster storage would go into down state and
always show N/A as space available/used.  Even if hosts saw storage
still and VM's were running on it on all 3 hosts.
> 
> > Saw a lot of messages like these that went away once gluster rollback
finished
> 
> > > [2016-07-09 15:27:46.935694] I [fuse-bridge.c:4083:fuse_init] 0-
glusterfs-fuse: FUSE inited with protocol versions: glusterfs 7.22
kernel 7.22
> > > [2016-07-09 15:27:49.555466] W [MSGID: 114031] [client-rpc-
fops.c:3050:client3_3_readv_cbk] 0-GLUSTER1-client-1: remote
operation failed [Operation not permitted]
> > > [2016-07-09 15:27:49.556574] W [MSGID: 114031] [client-rpc-
fops.c:3050:client3_3_readv_cbk] 0-GLUSTER1-client-0: remote
operation failed [Operation not permitted]
> > > [2016-07-09 15:27:49.556659] W [fuse-bridge.c:2227:fuse_readv_cbk] 0-
glusterfs-fuse: 80: READ => -1 gfid=deb61291-5176-4b81-8315-
3f1cf8e3534d fd=0x7f5224002f68 (Operation not permitted)
> > > [2016-07-09 15:27:59.612477] W [MSGID: 114031] [client-rpc-
fops.c:3050:client3_3_readv_cbk] 0-GLUSTER1-client-1: remote
operation failed [Operation not permitted]
> > > [2016-07-09 15:27:59.613700] W [MSGID: 114031] [client-rpc-
fops.c:3050:client3_3_readv_cbk] 0-GLUSTER1-client-0: remote
operation failed [Operation not permitted]
> > > [2016-07-09 15:27:59.613781] W [fuse-bridge.c:2227:fuse_readv_cbk] 0-
glusterfs-fuse: 168: READ => -1 gfid=deb61291-5176-4b81-8315-
3f1cf8e3534d fd=0x7f5224002f68 (Operation not permitted)
> 
> 
> 
> David Gossage
> 
> 
> Carousel Checks Inc. | System Administrator
> 
> 
> 
> 
> Office 708.613.2284
> 
> 
> 
> 
> 
> 
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users



 

__
BODDEN-KLINIKEN Ribnitz-Damgarten GmbH
Sandhufe 2
18311 Ribnitz-Damgarten

Telefon: 03821-700-0
Fax:   03821-700-240

E-Mail: i...@bodden-kliniken.de   Internet: http://www.bodden-kliniken.de

Sitz: Ribnitz-Damgarten, Amtsgericht: Stralsund, HRB 2919, Steuer-Nr.: 
079/133/40188
Aufsichtsratsvorsitzende: Carmen Schröter, Geschäftsführer: Dr. Falko Milski

Der Inhalt dieser E-Mail ist ausschließlich für den bezeichneten Adressaten 
bestimmt. Wenn Sie nicht der vorge- 
sehene Adressat dieser E-Mail oder dessen Vertreter sein sollten, beachten Sie 
bitte, dass jede Form der Veröf- 
fentlichung, Vervielfältigung oder Weitergabe des Inhalts dieser E-Mail 
unzulässig ist. Wir bitten Sie, sofort den 
Absender zu informieren und die E-Mail zu löschen. 


 Bodden-Kliniken Ribnitz-Damgarten GmbH 2016
*** Virenfrei durch Kerio Mail Server und Sophos Antivirus ***
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

[Simone Tiraboschi]

On Thu, Jul 21, 2016 at 12:38 PM, Matt .  wrote:
> The deploy went OK from the GUI but it's still not "active" as Hosted
> engine Host. The install also wen very fast so it looked like it
> didn't do anything witl the deploy setting in the GUI @ the hosted
> engine tab.

The difference with a standard host is just that it should create
/etc/ovirt-hosted-engine/hosted-engine.conf and start ovirt-ha-agent
and ovirt-ha-broker so it shouldn't be that longer.

At the end, due to the issue with syncing the local maintenance mode
from the engine, you have to connect to the host and run
'hosted-engine -set-maintenance --mode=none' from there.

Can you please post the result of
hosted-engine --vm-status and the status of ovirt-ha-agent?

> Or should I re-deploy again on the commandline after adding the host
> through the GUI ?
>
> About the initial GW, I didn't see that in the GUI.
>
> 2016-07-21 12:31 GMT+02:00 Simone Tiraboschi :
>> On Thu, Jul 21, 2016 at 12:28 PM, Matt .  wrote:
>>> No problem I checked it out and applied it, no solution it seems.
>>
>> Do you mean that it's still referring to your initial gateway or that
>> the deploy failed?
>>
>>> 2016-07-21 12:14 GMT+02:00 Simone Tiraboschi :
 On Thu, Jul 21, 2016 at 12:09 PM, Matt .  wrote:
> OK, I did a deploy from the engine and the Hosted is "Not Active" and

 Yes, sorry, I forgot to mention that.
 We have an open bug about re-activating an hosted-engine host from the
 engine: https://bugzilla.redhat.com/show_bug.cgi?id=1353600
 Connecting to the host and exiting the maintenance mode from there is
 the temporary solution.

> Engine HA is empty on 4.0.1
>
> 2016-07-21 11:58 GMT+02:00 Matt . :
>> True, but you can up an IP on any device in that case because you know
>> what you are doing.
>>
>> I think that this can be finetuned, or at least multiple IPs would be
>> nice as I now need to add one IP from my vrrp setup, so if there is a
>> failover or I need to take down the second switch I'm also done.
>>
>> 2016-07-21 10:23 GMT+02:00 Simone Tiraboschi :
>>> On Thu, Jul 21, 2016 at 10:03 AM, Matt .  wrote:
 OK, I will check this laster on, as I was having issues with the
 deploy from the GUI before as nothing really happened, I thought it
 was a bug on the first 4.0 release ?

 I think this should be investigated, the whole deployment as it would
 be good to have the possibility to list some GW's in case you use
 failover.

 I was even thinking of setting the engine IP there, should be working
 as good as also.
>>>
>>> Not really since the agent is pinging also when the engine VM is down
>>> due to maintenance.
>>>
 2016-07-21 9:53 GMT+02:00 Simone Tiraboschi :
> On Thu, Jul 21, 2016 at 9:47 AM, Matt .  
> wrote:
>> OK, I already thought that but where is this saved as I don't have 
>> any
>> rights as root to the ha_agent folder on the HE storage ?
>
> It's not a folder: it's a tar file directly saved over a VDSM volume.
> Editing it's a bit tricky.
>
>> In worst case scenario, how would i be able to deploy a new hosted
>> engine from a hosted engine ? This sounds undoable to me and also
>> unwanted as the HE is OK so far.
>
> With a 4.0 engine, when you choose to deploy a new host from the
> webadmin or from the rest API you can also choose to deploy it as an
> hosted-engine host if the engine has been deployed with hosted-engine.
> In this case, if I'm not wrong, you can also specify a different 
> gateway value.
>
>
>> 2016-07-21 9:41 GMT+02:00 Simone Tiraboschi :
>>> On Thu, Jul 21, 2016 at 9:27 AM, Matt .  
>>> wrote:
 Even when I change that on each host before I do a new deploy it 
 still
 uses the old GW address.
>>>
>>> If you deploy additional hosts with the CLI utility, each new host
>>> will be deployed consuming the answerfile generated by the first 
>>> host
>>> and saved on the shared storage.
>>> You have to manually tweak there if you to avoid.
>>>
>>> Another smarted option is to deploy additional HE host from the
>>> webadmin interface.
>>>
>>>
 2016-07-21 9:24 GMT+02:00 Simone Tiraboschi :
> On Wed, Jul 20, 2016 at 11:57 PM, Matt .  
> wrote:
>> OK, I tried to edit the answerfiles on 

[ovirt-users] Ovirt Node Next mass deploy

[Giorgio Biacchi]

Hi list,
starting from here
(http://lists.ovirt.org/pipermail/devel/2016-January/012073.html) and adjusting
broken links now I'm able to pxe boot CentOS 7 + kernel arguments:

LABEL node_4
 MENU LABEL Ovirt Node 4.0
 KERNEL centos7/x86_64/vmlinuz
 APPEND initrd=centos7/x86_64/initrd.img ramdisk_size=10 ksdevice=link
inst.ks=http://172.20.22.10/ks/ks_ovirt-node-4.0.cfg
inst.updates=http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-fc22-x86_64/lastSuccessfulBuild/artifact/exported-artifacts/product.img
inst.stage2=http://mi.mirror.garr.it/mirrors/CentOS/7/os/x86_64/

I think this method is the best for me because with a custom kickstart I can set
ssh keys and custom hooks and have a fully automated installation, but I'm not
sure if the lastSuccessfulBuild/artifact/exported-artifacts/product.img is the
correct image to pass to have a "stable" node.

There's any other "stable" product.img I can use?

Thanks
-- 
gb

PGP Key: http://pgp.mit.edu/
Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt 3.6.6 and gluster 3.7.13

[Sandro Bonazzola]

On Thu, Jul 21, 2016 at 11:28 AM, David Gossage  wrote:

> Anyone running one of recent 3.6.x lines and gluster using 3.7.13?  I am
> looking to upgrade gluster from 3.7.11->3.7.13 for some bug fixes, but have
> been told by users on gluster mail list due to some gluster changes I'd
> need to change the disk parameters to use writeback cache.  Something to do
> with aio support being removed.
>


Be sure both gluster server and client have the same version.
Adding Sahina.



>
> I believe this could be done with custom parameters?  But I believe strage
> tests are done using dd and would they fail with current settings then?
> Last upgrade to 3.7.13 I had to rollback to 3.7.11 due to stability isues
> where gluster storage would go into down state and always show N/A as space
> available/used.  Even if hosts saw storage still and VM's were running on
> it on all 3 hosts.
>
> Saw a lot of messages like these that went away once gluster rollback
> finished
>
> [2016-07-09 15:27:46.935694] I [fuse-bridge.c:4083:fuse_init]
> 0-glusterfs-fuse: FUSE inited with protocol versions: glusterfs 7.22 kernel
> 7.22
> [2016-07-09 15:27:49.555466] W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-GLUSTER1-client-1: remote
> operation failed [Operation not permitted]
> [2016-07-09 15:27:49.556574] W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-GLUSTER1-client-0: remote
> operation failed [Operation not permitted]
> [2016-07-09 15:27:49.556659] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 80: READ => -1 gfid=deb61291-5176-4b81-8315-3f1cf8e3534d
> fd=0x7f5224002f68 (Operation not permitted)
> [2016-07-09 15:27:59.612477] W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-GLUSTER1-client-1: remote
> operation failed [Operation not permitted]
> [2016-07-09 15:27:59.613700] W [MSGID: 114031]
> [client-rpc-fops.c:3050:client3_3_readv_cbk] 0-GLUSTER1-client-0: remote
> operation failed [Operation not permitted]
> [2016-07-09 15:27:59.613781] W [fuse-bridge.c:2227:fuse_readv_cbk]
> 0-glusterfs-fuse: 168: READ => -1 gfid=deb61291-5176-4b81-8315-3f1cf8e3534d
> fd=0x7f5224002f68 (Operation not permitted)
>
> *David Gossage*
> *Carousel Checks Inc. | System Administrator*
> *Office* 708.613.2284
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] synchronize cache

[Sandro Bonazzola]

On Thu, Jul 21, 2016 at 12:43 PM, Markus Scherer 
wrote:

> sorry no success
>
>
> [root@vm02 ~]# dnf clean all
> 24 files removed
> [root@vm02 ~]# dnf check-update
> Fedora 24 - x86_64 - Updates3.1 MB/s |  11 MB 00:03
> Fehler: Failed to synchronize cache for repo 'ovirt-4.0'
> [root@vm02 ~]#
>
>
Wait, you said you were on fedora 23, not fedora 24.
Fedora 24 is not supported by oVirt 4.0 (yet)
For Fedora 24 you need to use ovirt master nightly:
http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/




>
> Am 21.07.2016 um 11:16 schrieb Sandro Bonazzola:
>
> try with:
> [ovirt-4.0]
> name=Latest oVirt 4.0 Release
> baseurl=http://resources.ovirt.org/pub/ovirt-4.0/rpm/fc$releasever/
> #mirrorlist=
> http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.0-fc$releasever
> enabled=1
> skip_if_unavailable=0
> gpgcheck=1
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.0
>
> On Thu, Jul 21, 2016 at 10:20 AM, Markus Scherer 
> wrote:
>
>> my ovirt.repo file
>>
>> [ovirt-4.0]
>> name=Latest oVirt 4.0 Release
>> #baseurl=http://resources.ovirt.org/pub/ovirt-4.0/rpm/fc$releasever/
>> mirrorlist=
>> http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.0-fc$releasever
>> enabled=1
>> skip_if_unavailable=0
>> gpgcheck=1
>> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.0
>>
>> Am 21.07.2016 um 09:08 schrieb Sandro Bonazzola:
>>
>>
>>
>> On Thu, Jul 21, 2016 at 7:11 AM, Markus Scherer 
>> wrote:
>>
>>> Sorry the same problem
>>>
>>>
>>>
>> Maybe you hit a mirror out of sync, can you try using baseurl instead of
>> mirrorlist in the ovirt .repo files?
>>
>>
>>
>>
>>> Thx
>>>
>>> Am 20.07.2016 um 16:45 schrieb Sandro Bonazzola:
>>>
>>>
>>>
>>> On Mon, Jul 18, 2016 at 9:41 AM, Markus Scherer  wrote:
>>>
 Hi,

 on an fresh installed fedora server 23 i got a "Failed to synchronize
 cache for repo 'ovirt-4.0'".
 I have done a "dnf clean all" a "dnf check-update" and a reboot but
 always the same problem.

 thx for help

>>>
>>> I regenerated the metadata within the repo, can you please try again?
>>> Thanks,
>>>
>>>
>>>
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

>>>
>>>
>>>
>>> --
>>> Sandro Bonazzola
>>> Better technology. Faster innovation. Powered by community collaboration.
>>> See how it works at redhat.com
>>>
>>>
>>>
>>
>>
>> --
>> Sandro Bonazzola
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at redhat.com
>>
>>
>> ___
>> Users mailing 
>> listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>>
>>
>>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
>
>


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] synchronize cache

[Markus Scherer]

and the log





During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/dnf/cli/main.py", line 60, in main
return _main(base, args)
  File "/usr/lib/python3.5/site-packages/dnf/cli/main.py", line 112, in 
_main

cli.run()
  File "/usr/lib/python3.5/site-packages/dnf/cli/cli.py", line 1095, in run
self._process_demands()
  File "/usr/lib/python3.5/site-packages/dnf/cli/cli.py", line 810, in 
_process_demands

load_available_repos=lar)
  File "/usr/lib/python3.5/site-packages/dnf/base.py", line 239, in 
fill_sack

self._add_repo_to_sack(r)
  File "/usr/lib/python3.5/site-packages/dnf/base.py", line 111, in 
_add_repo_to_sack

repo.load()
  File "/usr/lib/python3.5/site-packages/dnf/repo.py", line 847, in load
raise dnf.exceptions.RepoError(msg)
dnf.exceptions.RepoError: Failed to synchronize cache for repo 'ovirt-4.0'
Jul 21 12:41:20 CRITICAL Fehler: Failed to synchronize cache for repo 
'ovirt-4.0'

Jul 21 12:42:14 INFO --- logging initialized ---
Jul 21 12:42:14 DDEBUG timer: config: 4 ms
Jul 21 12:42:14 DEBUG cachedir: /var/cache/dnf
Jul 21 12:42:14 DEBUG Loaded plugins: download, noroot, builddep, Query, 
needs-restarting, copr, langpacks, reposync, config-manager, playground, 
debuginfo-install, protected_packages, generate_completion_cache

Jul 21 12:42:14 DEBUG langpacks: No languages are enabled
Jul 21 12:42:14 DEBUG Error reading file : 
/var/lib/dnf/plugins/langpacks/installed_langpacks as it does not exist

Jul 21 12:42:14 DEBUG initialized Langpacks plugin
Jul 21 12:42:14 DEBUG DNF version: 1.1.9
Jul 21 12:42:14 DDEBUG Command: dnf clean all
Jul 21 12:42:14 DDEBUG Installroot: /
Jul 21 12:42:14 DDEBUG Releasever: 24
Jul 21 12:42:14 DDEBUG Base command: clean
Jul 21 12:42:14 DDEBUG Extra commands: ['all']
Jul 21 12:42:14 DEBUG Cleaning data: dbcache packages metadata
Jul 21 12:42:14 DDEBUG Removing file /var/cache/dnf/updates.solv
Jul 21 12:42:14 DDEBUG Removing file /var/cache/dnf/updates-filenames.solvx
Jul 21 12:42:14 DDEBUG Removing file /var/cache/dnf/updates-updateinfo.solvx
Jul 21 12:42:14 DDEBUG Removing file /var/cache/dnf/updates-presto.solvx
Jul 21 12:42:14 DDEBUG Removing file /var/cache/dnf/@System.solv
Jul 21 12:42:14 DDEBUG Removing file 
/var/cache/dnf/updates-c4f1c95f64c2b794/metalink.xml
Jul 21 12:42:14 DDEBUG Removing file 
/var/cache/dnf/updates-c4f1c95f64c2b794/repodata/b747c4b18ee6243458bdfe74ee8dd646458276bd70c91a75096ed063bef9b804-filelists.xml.gz
Jul 21 12:42:14 DDEBUG Removing file 
/var/cache/dnf/updates-c4f1c95f64c2b794/repodata/repomd.xml
Jul 21 12:42:14 DDEBUG Removing file 
/var/cache/dnf/updates-c4f1c95f64c2b794/repodata/781757fbb297b45c9198498298511f1da75136b514071200b4a749514dea513d-comps-f24.xml.xz
Jul 21 12:42:14 DDEBUG Removing file 
/var/cache/dnf/updates-c4f1c95f64c2b794/repodata/86d5fab59fde143382fc6ee4ebd34a12187da8123b93a5d50f946e5bd4c0ea06-updateinfo.xml.xz
Jul 21 12:42:14 DDEBUG Removing file 
/var/cache/dnf/updates-c4f1c95f64c2b794/repodata/67b06459bd1f9137e934e355d566ae7358e17ba7ba87ef7a83ed2a5907b1b833-primary.xml.gz
Jul 21 12:42:14 DDEBUG Removing file 
/var/cache/dnf/updates-c4f1c95f64c2b794/repodata/84f4fad977e033c253bc8dcc1b3f1dd90acf5d42f85ed0b56b853e096aa94693-prestodelta.xml.xz

Jul 21 12:42:14 INFO 12 files removed
Jul 21 12:42:14 DDEBUG Cleaning up.
Jul 21 12:42:23 INFO --- logging initialized ---
Jul 21 12:42:23 DDEBUG timer: config: 4 ms
Jul 21 12:42:23 DEBUG cachedir: /var/cache/dnf
Jul 21 12:42:23 DEBUG Loaded plugins: copr, needs-restarting, 
protected_packages, noroot, config-manager, langpacks, 
generate_completion_cache, reposync, download, playground, builddep, 
Query, debuginfo-install

Jul 21 12:42:23 DEBUG langpacks: No languages are enabled
Jul 21 12:42:23 DEBUG Error reading file : 
/var/lib/dnf/plugins/langpacks/installed_langpacks as it does not exist

Jul 21 12:42:23 DEBUG initialized Langpacks plugin
Jul 21 12:42:23 DEBUG DNF version: 1.1.9
Jul 21 12:42:23 DDEBUG Command: dnf check-update
Jul 21 12:42:23 DDEBUG Installroot: /
Jul 21 12:42:23 DDEBUG Releasever: 24
Jul 21 12:42:23 DDEBUG Base command: check-update
Jul 21 12:42:23 DDEBUG Extra commands: []
Jul 21 12:42:23 DDEBUG repo: downloading from remote: fedora, _Handle: 
metalnk: 
https://mirrors.fedoraproject.org/metalink?repo=fedora-24=x86_64, 
mlist: None, urls [].

Jul 21 12:42:44 DEBUG not found deltainfo for: Fedora 24 - x86_64
Jul 21 12:42:44 DEBUG not found updateinfo for: Fedora 24 - x86_64
Jul 21 12:42:57 DDEBUG repo: downloading from remote: ovirt-4.0, 
_Handle: metalnk: None, mlist: None, urls 
['http://resources.ovirt.org/pub/ovirt-4.0/rpm/fc24/'].
Jul 21 12:42:59 DEBUG Cannot download 
'http://resources.ovirt.org/pub/ovirt-4.0/rpm/fc24/': Cannot download 
repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried.

Jul 21 12:42:59 DDEBUG Cleaning up.
Jul 21 12:42:59 SUBDEBUG
Traceback (most recent call last):
  File 

Re: [ovirt-users] synchronize cache

[Markus Scherer]

sorry no success


[root@vm02 ~]# dnf clean all
24 files removed
[root@vm02 ~]# dnf check-update
Fedora 24 - x86_64 - Updates3.1 MB/s |  11 MB 00:03
Fehler: Failed to synchronize cache for repo 'ovirt-4.0'
[root@vm02 ~]#


Am 21.07.2016 um 11:16 schrieb Sandro Bonazzola:

try with:
[ovirt-4.0]
name=Latest oVirt 4.0 Release
baseurl=http://resources.ovirt.org/pub/ovirt-4.0/rpm/fc$releasever/
#mirrorlist=http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.0-fc$releasever
enabled=1
skip_if_unavailable=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.0

On Thu, Jul 21, 2016 at 10:20 AM, Markus Scherer > wrote:


my ovirt.repo file

[ovirt-4.0]
name=Latest oVirt 4.0 Release
#baseurl=http://resources.ovirt.org/pub/ovirt-4.0/rpm/fc$releasever/

mirrorlist=http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.0-fc$releasever
enabled=1
skip_if_unavailable=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.0


Am 21.07.2016 um 09:08 schrieb Sandro Bonazzola:



On Thu, Jul 21, 2016 at 7:11 AM, Markus Scherer
> wrote:

Sorry the same problem



Maybe you hit a mirror out of sync, can you try using baseurl
instead of mirrorlist in the ovirt .repo files?


Thx


Am 20.07.2016 um 16:45 schrieb Sandro Bonazzola:



On Mon, Jul 18, 2016 at 9:41 AM, Markus Scherer
> wrote:

Hi,

on an fresh installed fedora server 23 i got a "Failed
to synchronize cache for repo 'ovirt-4.0'".
I have done a "dnf clean all" a "dnf check-update" and a
reboot but always the same problem.

thx for help


I regenerated the metadata within the repo, can you please
try again?
Thanks,

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




-- 
Sandro Bonazzola

Better technology. Faster innovation. Powered by community
collaboration.
See how it works at redhat.com 





-- 
Sandro Bonazzola

Better technology. Faster innovation. Powered by community
collaboration.
See how it works at redhat.com 


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





--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com 


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

Re: [ovirt-users] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

[Matt .]

The deploy went OK from the GUI but it's still not "active" as Hosted
engine Host. The install also wen very fast so it looked like it
didn't do anything witl the deploy setting in the GUI @ the hosted
engine tab.

Or should I re-deploy again on the commandline after adding the host
through the GUI ?

About the initial GW, I didn't see that in the GUI.

2016-07-21 12:31 GMT+02:00 Simone Tiraboschi :
> On Thu, Jul 21, 2016 at 12:28 PM, Matt .  wrote:
>> No problem I checked it out and applied it, no solution it seems.
>
> Do you mean that it's still referring to your initial gateway or that
> the deploy failed?
>
>> 2016-07-21 12:14 GMT+02:00 Simone Tiraboschi :
>>> On Thu, Jul 21, 2016 at 12:09 PM, Matt .  wrote:
 OK, I did a deploy from the engine and the Hosted is "Not Active" and
>>>
>>> Yes, sorry, I forgot to mention that.
>>> We have an open bug about re-activating an hosted-engine host from the
>>> engine: https://bugzilla.redhat.com/show_bug.cgi?id=1353600
>>> Connecting to the host and exiting the maintenance mode from there is
>>> the temporary solution.
>>>
 Engine HA is empty on 4.0.1

 2016-07-21 11:58 GMT+02:00 Matt . :
> True, but you can up an IP on any device in that case because you know
> what you are doing.
>
> I think that this can be finetuned, or at least multiple IPs would be
> nice as I now need to add one IP from my vrrp setup, so if there is a
> failover or I need to take down the second switch I'm also done.
>
> 2016-07-21 10:23 GMT+02:00 Simone Tiraboschi :
>> On Thu, Jul 21, 2016 at 10:03 AM, Matt .  wrote:
>>> OK, I will check this laster on, as I was having issues with the
>>> deploy from the GUI before as nothing really happened, I thought it
>>> was a bug on the first 4.0 release ?
>>>
>>> I think this should be investigated, the whole deployment as it would
>>> be good to have the possibility to list some GW's in case you use
>>> failover.
>>>
>>> I was even thinking of setting the engine IP there, should be working
>>> as good as also.
>>
>> Not really since the agent is pinging also when the engine VM is down
>> due to maintenance.
>>
>>> 2016-07-21 9:53 GMT+02:00 Simone Tiraboschi :
 On Thu, Jul 21, 2016 at 9:47 AM, Matt .  wrote:
> OK, I already thought that but where is this saved as I don't have any
> rights as root to the ha_agent folder on the HE storage ?

 It's not a folder: it's a tar file directly saved over a VDSM volume.
 Editing it's a bit tricky.

> In worst case scenario, how would i be able to deploy a new hosted
> engine from a hosted engine ? This sounds undoable to me and also
> unwanted as the HE is OK so far.

 With a 4.0 engine, when you choose to deploy a new host from the
 webadmin or from the rest API you can also choose to deploy it as an
 hosted-engine host if the engine has been deployed with hosted-engine.
 In this case, if I'm not wrong, you can also specify a different 
 gateway value.


> 2016-07-21 9:41 GMT+02:00 Simone Tiraboschi :
>> On Thu, Jul 21, 2016 at 9:27 AM, Matt .  
>> wrote:
>>> Even when I change that on each host before I do a new deploy it 
>>> still
>>> uses the old GW address.
>>
>> If you deploy additional hosts with the CLI utility, each new host
>> will be deployed consuming the answerfile generated by the first host
>> and saved on the shared storage.
>> You have to manually tweak there if you to avoid.
>>
>> Another smarted option is to deploy additional HE host from the
>> webadmin interface.
>>
>>
>>> 2016-07-21 9:24 GMT+02:00 Simone Tiraboschi :
 On Wed, Jul 20, 2016 at 11:57 PM, Matt .  
 wrote:
> OK, I tried to edit the answerfiles on the other hosts to use 
> another
> IP but it doesn't ping and still uses the old GW address.
>
> Any idea ?

 The gateway address is saved under
 /etc/ovirt-hosted-engine/hosted-engine.conf
 on each host.

> 2016-07-20 22:27 GMT+02:00 Matt . :
>> Maybe it's a good idea to be able to add multiple addresses it 
>> should
>> ping in order of response.
>>
>> 2016-07-20 22:13 GMT+02:00 Sandro Bonazzola 
>> :
>>> Il 20/Lug/2016 

Re: [ovirt-users] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

[Simone Tiraboschi]

On Thu, Jul 21, 2016 at 12:28 PM, Matt .  wrote:
> No problem I checked it out and applied it, no solution it seems.

Do you mean that it's still referring to your initial gateway or that
the deploy failed?

> 2016-07-21 12:14 GMT+02:00 Simone Tiraboschi :
>> On Thu, Jul 21, 2016 at 12:09 PM, Matt .  wrote:
>>> OK, I did a deploy from the engine and the Hosted is "Not Active" and
>>
>> Yes, sorry, I forgot to mention that.
>> We have an open bug about re-activating an hosted-engine host from the
>> engine: https://bugzilla.redhat.com/show_bug.cgi?id=1353600
>> Connecting to the host and exiting the maintenance mode from there is
>> the temporary solution.
>>
>>> Engine HA is empty on 4.0.1
>>>
>>> 2016-07-21 11:58 GMT+02:00 Matt . :
 True, but you can up an IP on any device in that case because you know
 what you are doing.

 I think that this can be finetuned, or at least multiple IPs would be
 nice as I now need to add one IP from my vrrp setup, so if there is a
 failover or I need to take down the second switch I'm also done.

 2016-07-21 10:23 GMT+02:00 Simone Tiraboschi :
> On Thu, Jul 21, 2016 at 10:03 AM, Matt .  wrote:
>> OK, I will check this laster on, as I was having issues with the
>> deploy from the GUI before as nothing really happened, I thought it
>> was a bug on the first 4.0 release ?
>>
>> I think this should be investigated, the whole deployment as it would
>> be good to have the possibility to list some GW's in case you use
>> failover.
>>
>> I was even thinking of setting the engine IP there, should be working
>> as good as also.
>
> Not really since the agent is pinging also when the engine VM is down
> due to maintenance.
>
>> 2016-07-21 9:53 GMT+02:00 Simone Tiraboschi :
>>> On Thu, Jul 21, 2016 at 9:47 AM, Matt .  wrote:
 OK, I already thought that but where is this saved as I don't have any
 rights as root to the ha_agent folder on the HE storage ?
>>>
>>> It's not a folder: it's a tar file directly saved over a VDSM volume.
>>> Editing it's a bit tricky.
>>>
 In worst case scenario, how would i be able to deploy a new hosted
 engine from a hosted engine ? This sounds undoable to me and also
 unwanted as the HE is OK so far.
>>>
>>> With a 4.0 engine, when you choose to deploy a new host from the
>>> webadmin or from the rest API you can also choose to deploy it as an
>>> hosted-engine host if the engine has been deployed with hosted-engine.
>>> In this case, if I'm not wrong, you can also specify a different 
>>> gateway value.
>>>
>>>
 2016-07-21 9:41 GMT+02:00 Simone Tiraboschi :
> On Thu, Jul 21, 2016 at 9:27 AM, Matt .  
> wrote:
>> Even when I change that on each host before I do a new deploy it 
>> still
>> uses the old GW address.
>
> If you deploy additional hosts with the CLI utility, each new host
> will be deployed consuming the answerfile generated by the first host
> and saved on the shared storage.
> You have to manually tweak there if you to avoid.
>
> Another smarted option is to deploy additional HE host from the
> webadmin interface.
>
>
>> 2016-07-21 9:24 GMT+02:00 Simone Tiraboschi :
>>> On Wed, Jul 20, 2016 at 11:57 PM, Matt .  
>>> wrote:
 OK, I tried to edit the answerfiles on the other hosts to use 
 another
 IP but it doesn't ping and still uses the old GW address.

 Any idea ?
>>>
>>> The gateway address is saved under
>>> /etc/ovirt-hosted-engine/hosted-engine.conf
>>> on each host.
>>>
 2016-07-20 22:27 GMT+02:00 Matt . :
> Maybe it's a good idea to be able to add multiple addresses it 
> should
> ping in order of response.
>
> 2016-07-20 22:13 GMT+02:00 Sandro Bonazzola :
>> Il 20/Lug/2016 10:06 PM, "Matt ."  ha 
>> scritto:
>>>
>>> Hi,
>>>
>>> I'm trying to add a host to a HE installation but my gateway is 
>>> not
>>> pingable. It's a floating IP which is usable but not pingable 
>>> in this
>>> case.
>>>
>>> During the first install of the HE I could give any IP to ping 
>>> and I
>>> used a source IP for the floating GW address.

Re: [ovirt-users] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

[Matt .]

No problem I checked it out and applied it, no solution it seems.

2016-07-21 12:14 GMT+02:00 Simone Tiraboschi :
> On Thu, Jul 21, 2016 at 12:09 PM, Matt .  wrote:
>> OK, I did a deploy from the engine and the Hosted is "Not Active" and
>
> Yes, sorry, I forgot to mention that.
> We have an open bug about re-activating an hosted-engine host from the
> engine: https://bugzilla.redhat.com/show_bug.cgi?id=1353600
> Connecting to the host and exiting the maintenance mode from there is
> the temporary solution.
>
>> Engine HA is empty on 4.0.1
>>
>> 2016-07-21 11:58 GMT+02:00 Matt . :
>>> True, but you can up an IP on any device in that case because you know
>>> what you are doing.
>>>
>>> I think that this can be finetuned, or at least multiple IPs would be
>>> nice as I now need to add one IP from my vrrp setup, so if there is a
>>> failover or I need to take down the second switch I'm also done.
>>>
>>> 2016-07-21 10:23 GMT+02:00 Simone Tiraboschi :
 On Thu, Jul 21, 2016 at 10:03 AM, Matt .  wrote:
> OK, I will check this laster on, as I was having issues with the
> deploy from the GUI before as nothing really happened, I thought it
> was a bug on the first 4.0 release ?
>
> I think this should be investigated, the whole deployment as it would
> be good to have the possibility to list some GW's in case you use
> failover.
>
> I was even thinking of setting the engine IP there, should be working
> as good as also.

 Not really since the agent is pinging also when the engine VM is down
 due to maintenance.

> 2016-07-21 9:53 GMT+02:00 Simone Tiraboschi :
>> On Thu, Jul 21, 2016 at 9:47 AM, Matt .  wrote:
>>> OK, I already thought that but where is this saved as I don't have any
>>> rights as root to the ha_agent folder on the HE storage ?
>>
>> It's not a folder: it's a tar file directly saved over a VDSM volume.
>> Editing it's a bit tricky.
>>
>>> In worst case scenario, how would i be able to deploy a new hosted
>>> engine from a hosted engine ? This sounds undoable to me and also
>>> unwanted as the HE is OK so far.
>>
>> With a 4.0 engine, when you choose to deploy a new host from the
>> webadmin or from the rest API you can also choose to deploy it as an
>> hosted-engine host if the engine has been deployed with hosted-engine.
>> In this case, if I'm not wrong, you can also specify a different gateway 
>> value.
>>
>>
>>> 2016-07-21 9:41 GMT+02:00 Simone Tiraboschi :
 On Thu, Jul 21, 2016 at 9:27 AM, Matt .  wrote:
> Even when I change that on each host before I do a new deploy it still
> uses the old GW address.

 If you deploy additional hosts with the CLI utility, each new host
 will be deployed consuming the answerfile generated by the first host
 and saved on the shared storage.
 You have to manually tweak there if you to avoid.

 Another smarted option is to deploy additional HE host from the
 webadmin interface.


> 2016-07-21 9:24 GMT+02:00 Simone Tiraboschi :
>> On Wed, Jul 20, 2016 at 11:57 PM, Matt .  
>> wrote:
>>> OK, I tried to edit the answerfiles on the other hosts to use 
>>> another
>>> IP but it doesn't ping and still uses the old GW address.
>>>
>>> Any idea ?
>>
>> The gateway address is saved under
>> /etc/ovirt-hosted-engine/hosted-engine.conf
>> on each host.
>>
>>> 2016-07-20 22:27 GMT+02:00 Matt . :
 Maybe it's a good idea to be able to add multiple addresses it 
 should
 ping in order of response.

 2016-07-20 22:13 GMT+02:00 Sandro Bonazzola :
> Il 20/Lug/2016 10:06 PM, "Matt ."  ha 
> scritto:
>>
>> Hi,
>>
>> I'm trying to add a host to a HE installation but my gateway is 
>> not
>> pingable. It's a floating IP which is usable but not pingable in 
>> this
>> case.
>>
>> During the first install of the HE I could give any IP to ping 
>> and I
>> used a source IP for the floating GW address.
>>
>> What can I do to get around this as the network is OK, even when 
>> the
>> GW is not pingable.
>
> I think that gw not pingable will be interpreted as network 
> failure by the
> agent and will 

Re: [ovirt-users] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

[Simone Tiraboschi]

On Thu, Jul 21, 2016 at 12:09 PM, Matt .  wrote:
> OK, I did a deploy from the engine and the Hosted is "Not Active" and

Yes, sorry, I forgot to mention that.
We have an open bug about re-activating an hosted-engine host from the
engine: https://bugzilla.redhat.com/show_bug.cgi?id=1353600
Connecting to the host and exiting the maintenance mode from there is
the temporary solution.

> Engine HA is empty on 4.0.1
>
> 2016-07-21 11:58 GMT+02:00 Matt . :
>> True, but you can up an IP on any device in that case because you know
>> what you are doing.
>>
>> I think that this can be finetuned, or at least multiple IPs would be
>> nice as I now need to add one IP from my vrrp setup, so if there is a
>> failover or I need to take down the second switch I'm also done.
>>
>> 2016-07-21 10:23 GMT+02:00 Simone Tiraboschi :
>>> On Thu, Jul 21, 2016 at 10:03 AM, Matt .  wrote:
 OK, I will check this laster on, as I was having issues with the
 deploy from the GUI before as nothing really happened, I thought it
 was a bug on the first 4.0 release ?

 I think this should be investigated, the whole deployment as it would
 be good to have the possibility to list some GW's in case you use
 failover.

 I was even thinking of setting the engine IP there, should be working
 as good as also.
>>>
>>> Not really since the agent is pinging also when the engine VM is down
>>> due to maintenance.
>>>
 2016-07-21 9:53 GMT+02:00 Simone Tiraboschi :
> On Thu, Jul 21, 2016 at 9:47 AM, Matt .  wrote:
>> OK, I already thought that but where is this saved as I don't have any
>> rights as root to the ha_agent folder on the HE storage ?
>
> It's not a folder: it's a tar file directly saved over a VDSM volume.
> Editing it's a bit tricky.
>
>> In worst case scenario, how would i be able to deploy a new hosted
>> engine from a hosted engine ? This sounds undoable to me and also
>> unwanted as the HE is OK so far.
>
> With a 4.0 engine, when you choose to deploy a new host from the
> webadmin or from the rest API you can also choose to deploy it as an
> hosted-engine host if the engine has been deployed with hosted-engine.
> In this case, if I'm not wrong, you can also specify a different gateway 
> value.
>
>
>> 2016-07-21 9:41 GMT+02:00 Simone Tiraboschi :
>>> On Thu, Jul 21, 2016 at 9:27 AM, Matt .  wrote:
 Even when I change that on each host before I do a new deploy it still
 uses the old GW address.
>>>
>>> If you deploy additional hosts with the CLI utility, each new host
>>> will be deployed consuming the answerfile generated by the first host
>>> and saved on the shared storage.
>>> You have to manually tweak there if you to avoid.
>>>
>>> Another smarted option is to deploy additional HE host from the
>>> webadmin interface.
>>>
>>>
 2016-07-21 9:24 GMT+02:00 Simone Tiraboschi :
> On Wed, Jul 20, 2016 at 11:57 PM, Matt .  
> wrote:
>> OK, I tried to edit the answerfiles on the other hosts to use another
>> IP but it doesn't ping and still uses the old GW address.
>>
>> Any idea ?
>
> The gateway address is saved under
> /etc/ovirt-hosted-engine/hosted-engine.conf
> on each host.
>
>> 2016-07-20 22:27 GMT+02:00 Matt . :
>>> Maybe it's a good idea to be able to add multiple addresses it 
>>> should
>>> ping in order of response.
>>>
>>> 2016-07-20 22:13 GMT+02:00 Sandro Bonazzola :
 Il 20/Lug/2016 10:06 PM, "Matt ."  ha 
 scritto:
>
> Hi,
>
> I'm trying to add a host to a HE installation but my gateway is 
> not
> pingable. It's a floating IP which is usable but not pingable in 
> this
> case.
>
> During the first install of the HE I could give any IP to ping 
> and I
> used a source IP for the floating GW address.
>
> What can I do to get around this as the network is OK, even when 
> the
> GW is not pingable.

 I think that gw not pingable will be interpreted as network 
 failure by the
 agent and will lower the score of the hosts.

>
> Any idea is welcome!
>
> Thanks!
> ___
> Users mailing list
> Users@ovirt.org
> 

Re: [ovirt-users] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

[Matt .]

OK, I did a deploy from the engine and the Hosted is "Not Active" and
Engine HA is empty on 4.0.1

2016-07-21 11:58 GMT+02:00 Matt . :
> True, but you can up an IP on any device in that case because you know
> what you are doing.
>
> I think that this can be finetuned, or at least multiple IPs would be
> nice as I now need to add one IP from my vrrp setup, so if there is a
> failover or I need to take down the second switch I'm also done.
>
> 2016-07-21 10:23 GMT+02:00 Simone Tiraboschi :
>> On Thu, Jul 21, 2016 at 10:03 AM, Matt .  wrote:
>>> OK, I will check this laster on, as I was having issues with the
>>> deploy from the GUI before as nothing really happened, I thought it
>>> was a bug on the first 4.0 release ?
>>>
>>> I think this should be investigated, the whole deployment as it would
>>> be good to have the possibility to list some GW's in case you use
>>> failover.
>>>
>>> I was even thinking of setting the engine IP there, should be working
>>> as good as also.
>>
>> Not really since the agent is pinging also when the engine VM is down
>> due to maintenance.
>>
>>> 2016-07-21 9:53 GMT+02:00 Simone Tiraboschi :
 On Thu, Jul 21, 2016 at 9:47 AM, Matt .  wrote:
> OK, I already thought that but where is this saved as I don't have any
> rights as root to the ha_agent folder on the HE storage ?

 It's not a folder: it's a tar file directly saved over a VDSM volume.
 Editing it's a bit tricky.

> In worst case scenario, how would i be able to deploy a new hosted
> engine from a hosted engine ? This sounds undoable to me and also
> unwanted as the HE is OK so far.

 With a 4.0 engine, when you choose to deploy a new host from the
 webadmin or from the rest API you can also choose to deploy it as an
 hosted-engine host if the engine has been deployed with hosted-engine.
 In this case, if I'm not wrong, you can also specify a different gateway 
 value.


> 2016-07-21 9:41 GMT+02:00 Simone Tiraboschi :
>> On Thu, Jul 21, 2016 at 9:27 AM, Matt .  wrote:
>>> Even when I change that on each host before I do a new deploy it still
>>> uses the old GW address.
>>
>> If you deploy additional hosts with the CLI utility, each new host
>> will be deployed consuming the answerfile generated by the first host
>> and saved on the shared storage.
>> You have to manually tweak there if you to avoid.
>>
>> Another smarted option is to deploy additional HE host from the
>> webadmin interface.
>>
>>
>>> 2016-07-21 9:24 GMT+02:00 Simone Tiraboschi :
 On Wed, Jul 20, 2016 at 11:57 PM, Matt .  
 wrote:
> OK, I tried to edit the answerfiles on the other hosts to use another
> IP but it doesn't ping and still uses the old GW address.
>
> Any idea ?

 The gateway address is saved under
 /etc/ovirt-hosted-engine/hosted-engine.conf
 on each host.

> 2016-07-20 22:27 GMT+02:00 Matt . :
>> Maybe it's a good idea to be able to add multiple addresses it should
>> ping in order of response.
>>
>> 2016-07-20 22:13 GMT+02:00 Sandro Bonazzola :
>>> Il 20/Lug/2016 10:06 PM, "Matt ."  ha 
>>> scritto:

 Hi,

 I'm trying to add a host to a HE installation but my gateway is not
 pingable. It's a floating IP which is usable but not pingable in 
 this
 case.

 During the first install of the HE I could give any IP to ping and 
 I
 used a source IP for the floating GW address.

 What can I do to get around this as the network is OK, even when 
 the
 GW is not pingable.
>>>
>>> I think that gw not pingable will be interpreted as network failure 
>>> by the
>>> agent and will lower the score of the hosts.
>>>

 Any idea is welcome!

 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

Re: [ovirt-users] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

[Matt .]

True, but you can up an IP on any device in that case because you know
what you are doing.

I think that this can be finetuned, or at least multiple IPs would be
nice as I now need to add one IP from my vrrp setup, so if there is a
failover or I need to take down the second switch I'm also done.

2016-07-21 10:23 GMT+02:00 Simone Tiraboschi :
> On Thu, Jul 21, 2016 at 10:03 AM, Matt .  wrote:
>> OK, I will check this laster on, as I was having issues with the
>> deploy from the GUI before as nothing really happened, I thought it
>> was a bug on the first 4.0 release ?
>>
>> I think this should be investigated, the whole deployment as it would
>> be good to have the possibility to list some GW's in case you use
>> failover.
>>
>> I was even thinking of setting the engine IP there, should be working
>> as good as also.
>
> Not really since the agent is pinging also when the engine VM is down
> due to maintenance.
>
>> 2016-07-21 9:53 GMT+02:00 Simone Tiraboschi :
>>> On Thu, Jul 21, 2016 at 9:47 AM, Matt .  wrote:
 OK, I already thought that but where is this saved as I don't have any
 rights as root to the ha_agent folder on the HE storage ?
>>>
>>> It's not a folder: it's a tar file directly saved over a VDSM volume.
>>> Editing it's a bit tricky.
>>>
 In worst case scenario, how would i be able to deploy a new hosted
 engine from a hosted engine ? This sounds undoable to me and also
 unwanted as the HE is OK so far.
>>>
>>> With a 4.0 engine, when you choose to deploy a new host from the
>>> webadmin or from the rest API you can also choose to deploy it as an
>>> hosted-engine host if the engine has been deployed with hosted-engine.
>>> In this case, if I'm not wrong, you can also specify a different gateway 
>>> value.
>>>
>>>
 2016-07-21 9:41 GMT+02:00 Simone Tiraboschi :
> On Thu, Jul 21, 2016 at 9:27 AM, Matt .  wrote:
>> Even when I change that on each host before I do a new deploy it still
>> uses the old GW address.
>
> If you deploy additional hosts with the CLI utility, each new host
> will be deployed consuming the answerfile generated by the first host
> and saved on the shared storage.
> You have to manually tweak there if you to avoid.
>
> Another smarted option is to deploy additional HE host from the
> webadmin interface.
>
>
>> 2016-07-21 9:24 GMT+02:00 Simone Tiraboschi :
>>> On Wed, Jul 20, 2016 at 11:57 PM, Matt .  wrote:
 OK, I tried to edit the answerfiles on the other hosts to use another
 IP but it doesn't ping and still uses the old GW address.

 Any idea ?
>>>
>>> The gateway address is saved under
>>> /etc/ovirt-hosted-engine/hosted-engine.conf
>>> on each host.
>>>
 2016-07-20 22:27 GMT+02:00 Matt . :
> Maybe it's a good idea to be able to add multiple addresses it should
> ping in order of response.
>
> 2016-07-20 22:13 GMT+02:00 Sandro Bonazzola :
>> Il 20/Lug/2016 10:06 PM, "Matt ."  ha 
>> scritto:
>>>
>>> Hi,
>>>
>>> I'm trying to add a host to a HE installation but my gateway is not
>>> pingable. It's a floating IP which is usable but not pingable in 
>>> this
>>> case.
>>>
>>> During the first install of the HE I could give any IP to ping and I
>>> used a source IP for the floating GW address.
>>>
>>> What can I do to get around this as the network is OK, even when the
>>> GW is not pingable.
>>
>> I think that gw not pingable will be interpreted as network failure 
>> by the
>> agent and will lower the score of the hosts.
>>
>>>
>>> Any idea is welcome!
>>>
>>> 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

Re: [ovirt-users] Safe to upgrade HE hosts from GUI?

[Simone Tiraboschi]

On Thu, Jul 21, 2016 at 11:43 AM, Wee Sritippho  wrote:

> Hi,
>
> I used to follow
> http://www.ovirt.org/documentation/how-to/hosted-engine/#upgrade-hosted-engine
> when upgrading Hosted Engine (HE) but always fail to make the engine VM
> migrate to the fresh upgraded host as described in step 7. Furthermore, the
> update available icon never disappeared from the GUI.
>
Yes, you are right on that: it will happen only upgrading from 3.5, where
maximum score for an hosted-engine hosts was 2400 points, to 3.6 where the
maximum score is 3400.
On 3.6.z upgrades all the hosts are already at 3400 points and so the VM
will not migrate fro that.


> So I though using the GUI might be better for an amateur like me.
>
> Can I just follow
> http://www.ovirt.org/documentation/how-to/hosted-engine/#upgrade-hosted-engine
> until step 3 and do everything else via GUI?
>
Yes, absolutely.


> Thank you,
>
> --
> Wee
>
>
> ___
> 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] Safe to upgrade HE hosts from GUI?

[Wee Sritippho]

Hi,

I used to follow 
http://www.ovirt.org/documentation/how-to/hosted-engine/#upgrade-hosted-engine 
when upgrading Hosted Engine (HE) but always fail to make the engine VM 
migrate to the fresh upgraded host as described in step 7. Furthermore, 
the update available icon never disappeared from the GUI.


So I though using the GUI might be better for an amateur like me.

Can I just follow 
http://www.ovirt.org/documentation/how-to/hosted-engine/#upgrade-hosted-engine 
until step 3 and do everything else via GUI?


Thank you,


--
Wee

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

Re: [ovirt-users] ovirt-3.6 : Hosted-engine crashed and can't restart

[Alexis HAUSER]

> The issue seams here: please ensure that you can correctly connect
> your storage server.
> Can you please attach vdsm logs?

Yes actually I figured out it was a DNS problem : as mentioned in the messages 
from the log I provided, it wasn't able to reach the NFS where the engine was 
(as it uses FQDN not IP with NFS it seems, I will fix that for not depending on 
DNS).

This is actually my setup : only Em1 is plugged, it has ovirtmgmt + one other 
logical VLAN network. This VLAN network as in DHCP and never had an IP, 
everything was working fine.
Since I added an IP address to that interface, the manager crashed. Actually it 
is trying to use that VLAN interface as the default route, I have no idea why, 
and cause DNS issue (one of the DNS was on another network, the the second was 
on the game network...it should actually have worked anyway...).
The only way I found to resolve this was ifdown of that interface, and route 
add default gw  ovirtmgmt

After that, I had errors like "unknown stale data" and "failed to reinitilize 
lockspace" ; removing the lockfile with hosted-engine command, and removing 
manually __DIRECT_IO__ file on the engine storage didn't fix it.

I actually found out what was happening : ovirt-ha-agent had errors in his 
status (with systemctl), ovirt-ha-broker had errors related to ha-agent and 
vdsdm had errors related to those 2 previous services.

I resolved my issue by restarting the service in the good order :

# systemctl restart ovirt-ha-agent.service
# systemctl restart ovirt-ha-broker.service
# systemctl restart vdsmd

Anyway thanks for your answer, I hope this topic will help people with similar 
issues
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] ovirt 3.6.6 and gluster 3.7.13

[David Gossage]

Anyone running one of recent 3.6.x lines and gluster using 3.7.13?  I am
looking to upgrade gluster from 3.7.11->3.7.13 for some bug fixes, but have
been told by users on gluster mail list due to some gluster changes I'd
need to change the disk parameters to use writeback cache.  Something to do
with aio support being removed.

I believe this could be done with custom parameters?  But I believe strage
tests are done using dd and would they fail with current settings then?
Last upgrade to 3.7.13 I had to rollback to 3.7.11 due to stability isues
where gluster storage would go into down state and always show N/A as space
available/used.  Even if hosts saw storage still and VM's were running on
it on all 3 hosts.

Saw a lot of messages like these that went away once gluster rollback
finished

[2016-07-09 15:27:46.935694] I [fuse-bridge.c:4083:fuse_init]
0-glusterfs-fuse: FUSE inited with protocol versions: glusterfs 7.22 kernel
7.22
[2016-07-09 15:27:49.555466] W [MSGID: 114031]
[client-rpc-fops.c:3050:client3_3_readv_cbk] 0-GLUSTER1-client-1: remote
operation failed [Operation not permitted]
[2016-07-09 15:27:49.556574] W [MSGID: 114031]
[client-rpc-fops.c:3050:client3_3_readv_cbk] 0-GLUSTER1-client-0: remote
operation failed [Operation not permitted]
[2016-07-09 15:27:49.556659] W [fuse-bridge.c:2227:fuse_readv_cbk]
0-glusterfs-fuse: 80: READ => -1 gfid=deb61291-5176-4b81-8315-3f1cf8e3534d
fd=0x7f5224002f68 (Operation not permitted)
[2016-07-09 15:27:59.612477] W [MSGID: 114031]
[client-rpc-fops.c:3050:client3_3_readv_cbk] 0-GLUSTER1-client-1: remote
operation failed [Operation not permitted]
[2016-07-09 15:27:59.613700] W [MSGID: 114031]
[client-rpc-fops.c:3050:client3_3_readv_cbk] 0-GLUSTER1-client-0: remote
operation failed [Operation not permitted]
[2016-07-09 15:27:59.613781] W [fuse-bridge.c:2227:fuse_readv_cbk]
0-glusterfs-fuse: 168: READ => -1 gfid=deb61291-5176-4b81-8315-3f1cf8e3534d
fd=0x7f5224002f68 (Operation not permitted)

*David Gossage*
*Carousel Checks Inc. | System Administrator*
*Office* 708.613.2284
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] synchronize cache

[Sandro Bonazzola]

try with:
[ovirt-4.0]
name=Latest oVirt 4.0 Release
baseurl=http://resources.ovirt.org/pub/ovirt-4.0/rpm/fc$releasever/
#mirrorlist=
http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.0-fc$releasever
enabled=1
skip_if_unavailable=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.0

On Thu, Jul 21, 2016 at 10:20 AM, Markus Scherer 
wrote:

> my ovirt.repo file
>
> [ovirt-4.0]
> name=Latest oVirt 4.0 Release
> #baseurl=http://resources.ovirt.org/pub/ovirt-4.0/rpm/fc$releasever/
> mirrorlist=
> http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.0-fc$releasever
> enabled=1
> skip_if_unavailable=0
> gpgcheck=1
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.0
>
> Am 21.07.2016 um 09:08 schrieb Sandro Bonazzola:
>
>
>
> On Thu, Jul 21, 2016 at 7:11 AM, Markus Scherer 
> wrote:
>
>> Sorry the same problem
>>
>>
>>
> Maybe you hit a mirror out of sync, can you try using baseurl instead of
> mirrorlist in the ovirt .repo files?
>
>
>
>
>> Thx
>>
>> Am 20.07.2016 um 16:45 schrieb Sandro Bonazzola:
>>
>>
>>
>> On Mon, Jul 18, 2016 at 9:41 AM, Markus Scherer  wrote:
>>
>>> Hi,
>>>
>>> on an fresh installed fedora server 23 i got a "Failed to synchronize
>>> cache for repo 'ovirt-4.0'".
>>> I have done a "dnf clean all" a "dnf check-update" and a reboot but
>>> always the same problem.
>>>
>>> thx for help
>>>
>>
>> I regenerated the metadata within the repo, can you please try again?
>> Thanks,
>>
>>
>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>
>>
>>
>> --
>> Sandro Bonazzola
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at redhat.com
>>
>>
>>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Cam Mac]

Sent, thanks Shahar.

On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi  wrote:

> On 21.07.16 10:03, Cam Mac wrote:
> OK,
> Can you please share the engine.log
> > Hi Shahar,
> >
> > Doesn't appear to be there:
> >
> > engine=> select vm_name from vm_static where vm_name='wvm2';
> >  vm_name
> > -
> > (0 rows)
> >
> > Thanks,
> >
> > Cam
> >
> >
> >
> > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi 
> wrote:
> >
> > > On 20.07.16 20:06, Richard W.M. Jones wrote:
> > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > > > > >
> > > > > > The import doesn't happen automatically, you have to do the final
> > > step
> > > > > > manually (when using the command line).  See:
> > > > > >
> > > > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > > > > >
> > > > > > However that error shouldn't happen.  It looks like the name is
> the
> > > > > > same as the name of an existing VM.  From virt-v2v you can do the
> > > > > > whole conversion/import over again, this time adding the `-on
> > > > > > new_name' option to the command line (obviously choosing a name
> which
> > > > > > is not otherwise being used).
> > > > > >
> > > > > > I don't know if there's a way to get oVirt to change the name
> when
> > > > > > importing from the export domain.  As far as I know you have to
> start
> > > > > > the import from scratch.
> > > > > >
> > > > > >
> > > > > There's no existing VM with that name that I can see. It may have
> come
> > > from
> > > > > one of my earlier import attempts,
> > > > > though that earlier attempt did not show up in the GUI, it did
> write
> > > files
> > > > > to the export domain.
> > > > >
> > > > > I re-ran the conversion again with a rename but it failed to
> import it
> > > > > again, with the same error.
> > > > >
> > > > > Could there be a record in the DB somewhere, or does it look at the
> > > files
> > > > > alone? Just trying to work out where the conflict is.
> > > >
> > > > I had a look at the ovirt-engine code where
> > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come
> > > > from a database check.  However I'm not really familiar enough with
> > > > the code to be sure.  Probably best to ask an oVirt developer, or try
> > > > dumping the database to see if "wvm2" appears in a column anywhere.
> > > >
> > > > Rich.
> > > >
> > > > --
> > > > Richard Jones, Virtualization Group, Red Hat
> > > http://people.redhat.com/~rjones
> > > > Read my programming and virtualization blog:
> http://rwmj.wordpress.com
> > > > Fedora Windows cross-compiler. Compile Windows programs, test, and
> > > > build Windows installers. Over 100 libraries supported.
> > > > http://fedoraproject.org/wiki/MinGW
> > > It may be in the DB...
> > > Try to run this via psql:
> > >
> > > select vm_name from vm_static where vm_name='wvm2';
> > >
> > > and see if there is a result...
> > >
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Shahar Havivi]

On 21.07.16 10:03, Cam Mac wrote:
OK,
Can you please share the engine.log
> Hi Shahar,
> 
> Doesn't appear to be there:
> 
> engine=> select vm_name from vm_static where vm_name='wvm2';
>  vm_name
> -
> (0 rows)
> 
> Thanks,
> 
> Cam
> 
> 
> 
> On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi  wrote:
> 
> > On 20.07.16 20:06, Richard W.M. Jones wrote:
> > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > > > >
> > > > > The import doesn't happen automatically, you have to do the final
> > step
> > > > > manually (when using the command line).  See:
> > > > >
> > > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > > > >
> > > > > However that error shouldn't happen.  It looks like the name is the
> > > > > same as the name of an existing VM.  From virt-v2v you can do the
> > > > > whole conversion/import over again, this time adding the `-on
> > > > > new_name' option to the command line (obviously choosing a name which
> > > > > is not otherwise being used).
> > > > >
> > > > > I don't know if there's a way to get oVirt to change the name when
> > > > > importing from the export domain.  As far as I know you have to start
> > > > > the import from scratch.
> > > > >
> > > > >
> > > > There's no existing VM with that name that I can see. It may have come
> > from
> > > > one of my earlier import attempts,
> > > > though that earlier attempt did not show up in the GUI, it did write
> > files
> > > > to the export domain.
> > > >
> > > > I re-ran the conversion again with a rename but it failed to import it
> > > > again, with the same error.
> > > >
> > > > Could there be a record in the DB somewhere, or does it look at the
> > files
> > > > alone? Just trying to work out where the conflict is.
> > >
> > > I had a look at the ovirt-engine code where
> > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come
> > > from a database check.  However I'm not really familiar enough with
> > > the code to be sure.  Probably best to ask an oVirt developer, or try
> > > dumping the database to see if "wvm2" appears in a column anywhere.
> > >
> > > Rich.
> > >
> > > --
> > > Richard Jones, Virtualization Group, Red Hat
> > http://people.redhat.com/~rjones
> > > Read my programming and virtualization blog: http://rwmj.wordpress.com
> > > Fedora Windows cross-compiler. Compile Windows programs, test, and
> > > build Windows installers. Over 100 libraries supported.
> > > http://fedoraproject.org/wiki/MinGW
> > It may be in the DB...
> > Try to run this via psql:
> >
> > select vm_name from vm_static where vm_name='wvm2';
> >
> > and see if there is a result...
> >
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Cam Mac]

Hi Shahar,

Doesn't appear to be there:

engine=> select vm_name from vm_static where vm_name='wvm2';
 vm_name
-
(0 rows)

Thanks,

Cam



On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi  wrote:

> On 20.07.16 20:06, Richard W.M. Jones wrote:
> > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > > >
> > > > The import doesn't happen automatically, you have to do the final
> step
> > > > manually (when using the command line).  See:
> > > >
> > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > > >
> > > > However that error shouldn't happen.  It looks like the name is the
> > > > same as the name of an existing VM.  From virt-v2v you can do the
> > > > whole conversion/import over again, this time adding the `-on
> > > > new_name' option to the command line (obviously choosing a name which
> > > > is not otherwise being used).
> > > >
> > > > I don't know if there's a way to get oVirt to change the name when
> > > > importing from the export domain.  As far as I know you have to start
> > > > the import from scratch.
> > > >
> > > >
> > > There's no existing VM with that name that I can see. It may have come
> from
> > > one of my earlier import attempts,
> > > though that earlier attempt did not show up in the GUI, it did write
> files
> > > to the export domain.
> > >
> > > I re-ran the conversion again with a rename but it failed to import it
> > > again, with the same error.
> > >
> > > Could there be a record in the DB somewhere, or does it look at the
> files
> > > alone? Just trying to work out where the conflict is.
> >
> > I had a look at the ovirt-engine code where
> > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come
> > from a database check.  However I'm not really familiar enough with
> > the code to be sure.  Probably best to ask an oVirt developer, or try
> > dumping the database to see if "wvm2" appears in a column anywhere.
> >
> > Rich.
> >
> > --
> > Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> > Read my programming and virtualization blog: http://rwmj.wordpress.com
> > Fedora Windows cross-compiler. Compile Windows programs, test, and
> > build Windows installers. Over 100 libraries supported.
> > http://fedoraproject.org/wiki/MinGW
> It may be in the DB...
> Try to run this via psql:
>
> select vm_name from vm_static where vm_name='wvm2';
>
> and see if there is a result...
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

[Simone Tiraboschi]

On Thu, Jul 21, 2016 at 10:03 AM, Matt .  wrote:
> OK, I will check this laster on, as I was having issues with the
> deploy from the GUI before as nothing really happened, I thought it
> was a bug on the first 4.0 release ?
>
> I think this should be investigated, the whole deployment as it would
> be good to have the possibility to list some GW's in case you use
> failover.
>
> I was even thinking of setting the engine IP there, should be working
> as good as also.

Not really since the agent is pinging also when the engine VM is down
due to maintenance.

> 2016-07-21 9:53 GMT+02:00 Simone Tiraboschi :
>> On Thu, Jul 21, 2016 at 9:47 AM, Matt .  wrote:
>>> OK, I already thought that but where is this saved as I don't have any
>>> rights as root to the ha_agent folder on the HE storage ?
>>
>> It's not a folder: it's a tar file directly saved over a VDSM volume.
>> Editing it's a bit tricky.
>>
>>> In worst case scenario, how would i be able to deploy a new hosted
>>> engine from a hosted engine ? This sounds undoable to me and also
>>> unwanted as the HE is OK so far.
>>
>> With a 4.0 engine, when you choose to deploy a new host from the
>> webadmin or from the rest API you can also choose to deploy it as an
>> hosted-engine host if the engine has been deployed with hosted-engine.
>> In this case, if I'm not wrong, you can also specify a different gateway 
>> value.
>>
>>
>>> 2016-07-21 9:41 GMT+02:00 Simone Tiraboschi :
 On Thu, Jul 21, 2016 at 9:27 AM, Matt .  wrote:
> Even when I change that on each host before I do a new deploy it still
> uses the old GW address.

 If you deploy additional hosts with the CLI utility, each new host
 will be deployed consuming the answerfile generated by the first host
 and saved on the shared storage.
 You have to manually tweak there if you to avoid.

 Another smarted option is to deploy additional HE host from the
 webadmin interface.


> 2016-07-21 9:24 GMT+02:00 Simone Tiraboschi :
>> On Wed, Jul 20, 2016 at 11:57 PM, Matt .  wrote:
>>> OK, I tried to edit the answerfiles on the other hosts to use another
>>> IP but it doesn't ping and still uses the old GW address.
>>>
>>> Any idea ?
>>
>> The gateway address is saved under
>> /etc/ovirt-hosted-engine/hosted-engine.conf
>> on each host.
>>
>>> 2016-07-20 22:27 GMT+02:00 Matt . :
 Maybe it's a good idea to be able to add multiple addresses it should
 ping in order of response.

 2016-07-20 22:13 GMT+02:00 Sandro Bonazzola :
> Il 20/Lug/2016 10:06 PM, "Matt ."  ha scritto:
>>
>> Hi,
>>
>> I'm trying to add a host to a HE installation but my gateway is not
>> pingable. It's a floating IP which is usable but not pingable in this
>> case.
>>
>> During the first install of the HE I could give any IP to ping and I
>> used a source IP for the floating GW address.
>>
>> What can I do to get around this as the network is OK, even when the
>> GW is not pingable.
>
> I think that gw not pingable will be interpreted as network failure 
> by the
> agent and will lower the score of the hosts.
>
>>
>> Any idea is welcome!
>>
>> 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

Re: [ovirt-users] synchronize cache

[Markus Scherer]

my ovirt.repo file

[ovirt-4.0]
name=Latest oVirt 4.0 Release
#baseurl=http://resources.ovirt.org/pub/ovirt-4.0/rpm/fc$releasever/
mirrorlist=http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.0-fc$releasever
enabled=1
skip_if_unavailable=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.0


Am 21.07.2016 um 09:08 schrieb Sandro Bonazzola:



On Thu, Jul 21, 2016 at 7:11 AM, Markus Scherer > wrote:


Sorry the same problem



Maybe you hit a mirror out of sync, can you try using baseurl instead 
of mirrorlist in the ovirt .repo files?



Thx


Am 20.07.2016 um 16:45 schrieb Sandro Bonazzola:



On Mon, Jul 18, 2016 at 9:41 AM, Markus Scherer > wrote:

Hi,

on an fresh installed fedora server 23 i got a "Failed to
synchronize cache for repo 'ovirt-4.0'".
I have done a "dnf clean all" a "dnf check-update" and a
reboot but always the same problem.

thx for help


I regenerated the metadata within the repo, can you please try again?
Thanks,

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




-- 
Sandro Bonazzola

Better technology. Faster innovation. Powered by community
collaboration.
See how it works at redhat.com 





--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com 


___
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] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

[Matt .]

OK, I will check this laster on, as I was having issues with the
deploy from the GUI before as nothing really happened, I thought it
was a bug on the first 4.0 release ?

I think this should be investigated, the whole deployment as it would
be good to have the possibility to list some GW's in case you use
failover.

I was even thinking of setting the engine IP there, should be working
as good as also.

2016-07-21 9:53 GMT+02:00 Simone Tiraboschi :
> On Thu, Jul 21, 2016 at 9:47 AM, Matt .  wrote:
>> OK, I already thought that but where is this saved as I don't have any
>> rights as root to the ha_agent folder on the HE storage ?
>
> It's not a folder: it's a tar file directly saved over a VDSM volume.
> Editing it's a bit tricky.
>
>> In worst case scenario, how would i be able to deploy a new hosted
>> engine from a hosted engine ? This sounds undoable to me and also
>> unwanted as the HE is OK so far.
>
> With a 4.0 engine, when you choose to deploy a new host from the
> webadmin or from the rest API you can also choose to deploy it as an
> hosted-engine host if the engine has been deployed with hosted-engine.
> In this case, if I'm not wrong, you can also specify a different gateway 
> value.
>
>
>> 2016-07-21 9:41 GMT+02:00 Simone Tiraboschi :
>>> On Thu, Jul 21, 2016 at 9:27 AM, Matt .  wrote:
 Even when I change that on each host before I do a new deploy it still
 uses the old GW address.
>>>
>>> If you deploy additional hosts with the CLI utility, each new host
>>> will be deployed consuming the answerfile generated by the first host
>>> and saved on the shared storage.
>>> You have to manually tweak there if you to avoid.
>>>
>>> Another smarted option is to deploy additional HE host from the
>>> webadmin interface.
>>>
>>>
 2016-07-21 9:24 GMT+02:00 Simone Tiraboschi :
> On Wed, Jul 20, 2016 at 11:57 PM, Matt .  wrote:
>> OK, I tried to edit the answerfiles on the other hosts to use another
>> IP but it doesn't ping and still uses the old GW address.
>>
>> Any idea ?
>
> The gateway address is saved under
> /etc/ovirt-hosted-engine/hosted-engine.conf
> on each host.
>
>> 2016-07-20 22:27 GMT+02:00 Matt . :
>>> Maybe it's a good idea to be able to add multiple addresses it should
>>> ping in order of response.
>>>
>>> 2016-07-20 22:13 GMT+02:00 Sandro Bonazzola :
 Il 20/Lug/2016 10:06 PM, "Matt ."  ha scritto:
>
> Hi,
>
> I'm trying to add a host to a HE installation but my gateway is not
> pingable. It's a floating IP which is usable but not pingable in this
> case.
>
> During the first install of the HE I could give any IP to ping and I
> used a source IP for the floating GW address.
>
> What can I do to get around this as the network is OK, even when the
> GW is not pingable.

 I think that gw not pingable will be interpreted as network failure by 
 the
 agent and will lower the score of the hosts.

>
> Any idea is welcome!
>
> 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

Re: [ovirt-users] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

[Simone Tiraboschi]

On Thu, Jul 21, 2016 at 9:47 AM, Matt .  wrote:
> OK, I already thought that but where is this saved as I don't have any
> rights as root to the ha_agent folder on the HE storage ?

It's not a folder: it's a tar file directly saved over a VDSM volume.
Editing it's a bit tricky.

> In worst case scenario, how would i be able to deploy a new hosted
> engine from a hosted engine ? This sounds undoable to me and also
> unwanted as the HE is OK so far.

With a 4.0 engine, when you choose to deploy a new host from the
webadmin or from the rest API you can also choose to deploy it as an
hosted-engine host if the engine has been deployed with hosted-engine.
In this case, if I'm not wrong, you can also specify a different gateway value.


> 2016-07-21 9:41 GMT+02:00 Simone Tiraboschi :
>> On Thu, Jul 21, 2016 at 9:27 AM, Matt .  wrote:
>>> Even when I change that on each host before I do a new deploy it still
>>> uses the old GW address.
>>
>> If you deploy additional hosts with the CLI utility, each new host
>> will be deployed consuming the answerfile generated by the first host
>> and saved on the shared storage.
>> You have to manually tweak there if you to avoid.
>>
>> Another smarted option is to deploy additional HE host from the
>> webadmin interface.
>>
>>
>>> 2016-07-21 9:24 GMT+02:00 Simone Tiraboschi :
 On Wed, Jul 20, 2016 at 11:57 PM, Matt .  wrote:
> OK, I tried to edit the answerfiles on the other hosts to use another
> IP but it doesn't ping and still uses the old GW address.
>
> Any idea ?

 The gateway address is saved under
 /etc/ovirt-hosted-engine/hosted-engine.conf
 on each host.

> 2016-07-20 22:27 GMT+02:00 Matt . :
>> Maybe it's a good idea to be able to add multiple addresses it should
>> ping in order of response.
>>
>> 2016-07-20 22:13 GMT+02:00 Sandro Bonazzola :
>>> Il 20/Lug/2016 10:06 PM, "Matt ."  ha scritto:

 Hi,

 I'm trying to add a host to a HE installation but my gateway is not
 pingable. It's a floating IP which is usable but not pingable in this
 case.

 During the first install of the HE I could give any IP to ping and I
 used a source IP for the floating GW address.

 What can I do to get around this as the network is OK, even when the
 GW is not pingable.
>>>
>>> I think that gw not pingable will be interpreted as network failure by 
>>> the
>>> agent and will lower the score of the hosts.
>>>

 Any idea is welcome!

 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

Re: [ovirt-users] ovirt-3.6 : Hosted-engine crashed and can't restart

[Simone Tiraboschi]

On Wed, Jul 20, 2016 at 5:01 PM, Alexis HAUSER
 wrote:
> After assigning an IP adress to a VLAN network (it was using DHCP by default) 
> that was on the same NIC than ovirtmgmt, my hosted-engine crashed and can't 
> start again...I have no idea how to fix this.
> I had a similar issue some months ago but with a different error. I tried to 
> restart the ha agent that seems to be linked with this error, also restarted 
> the host. I also tried to remove the _DIRECT_IO_ lockfile on the engine 
> storage as it fixed my problem last time but it didn't help...
>
> Any ideas ? Do you think editing manually the logical network in the host and 
> reverting them at it was before crash can help ?
>
>
>
>
>
>
> hosted-engine --vm-status
> Traceback (most recent call last):
>   File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
> "__main__", fname, loader, pkg_name)
>   File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
> exec code in run_globals
>   File 
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/vm_status.py", 
> line 117, in 
> if not status_checker.print_status():
>   File 
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/vm_status.py", 
> line 60, in print_status
> all_host_stats = ha_cli.get_all_host_stats()
>   File 
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", 
> line 160, in get_all_host_stats
> return self.get_all_stats(self.StatModes.HOST)
>   File 
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", 
> line 103, in get_all_stats
> self._configure_broker_conn(broker)
>   File 
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", 
> line 180, in _configure_broker_conn
> dom_type=dom_type)
>   File 
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", 
> line 176, in set_storage_domain
> .format(sd_type, options, e))
> ovirt_hosted_engine_ha.lib.exceptions.RequestError: Failed to set storage 
> domain FilesystemBackend, options {'dom_type': 'nfs3', 'sd_uuid': 
> 'e41807e5-ee68-40a2-a642-cc226ba0e82d'}: Request failed:  'ovirt_hosted_engine_ha.lib.storage_backends.BackendFailureException'>
>
>
> vdsClient -s 0 list
>
> 16450089-911e-4bad-a8b7-98e84a79ef3a
> Status = Down
> nicModel = rtl8139,pv
> statusTime = 4295559350
> exitMessage = Unable to get volume size for domain 
> e41807e5-ee68-40a2-a642-cc226ba0e82d volume 
> 053df3a6-db18-445a-8f75-61c630ab0003
> emulatedMachine = rhel6.5.0
> pid = 0
> vmName = HostedEngine
> devices = [{'index': '0', 'iface': 'virtio', 'format': 'raw', 
> 'bootOrder': '1', 'address': {'slot': '0x06', 'bus': '0x00', 'domain': 
> '0x', 'type': 'pci', 'function': '0x0'}, 'volumeID': 
> '053df3a6-db18-445a-8f75-61c630ab0003', 'imageID': 
> 'b6daa50d-adad-46a5-8f5f-accfb155a1e1', 'readonly': 'false', 'domainID': 
> 'e41807e5-ee68-40a2-a642-cc226ba0e82d', 'deviceId': 
> 'b6daa50d-adad-46a5-8f5f-accfb155a1e1', 'poolID': 
> '----', 'device': 'disk', 'shared': 
> 'exclusive', 'propagateErrors': 'off', 'type': 'disk'}, {'nicModel': 'pv', 
> 'macAddr': '00:16:3e:1c:4b:81', 'linkActive': 'true', 'network': 'ovirtmgmt', 
> 'deviceId': '0aeaea2f-a419-43cc-92d7-8422f6aa9223', 'address': 'None', 
> 'device': 'bridge', 'type': 'interface'}, {'index': '2', 'iface': 'ide', 
> 'readonly': 'true', 'deviceId': '8c3179ac-b322-4f5c-9449-c52e3665e0ae', 
> 'address': {'bus': '1', 'controller': '0', 'type': 'drive', 'target': '0', 
> 'unit': '0'}, 'device': 'cdrom', 'shared': 'false', 'path': '', 'type': 
> 'disk'}, {'device': 'scsi', 'model': 'virtio-scsi', 'type': 'controller', 
> 'deviceId': '21db0c6e-071c-48ff-b905-95478b37c384', 'address': {'slot': 
> '0x04', 'bus': '0x00', 'domain': '0x', 'type': 'pci', 'function': 
> '0x0'}}, {'device': 'usb', 'type': 'controller', 'deviceId': 
> 'c0384f68-d0c9-4ebb-a779-8dc9911ce2f8', 'address': {'slot': '0x01', 'bus': 
> '0x00', 'domain': '0x', 'type': 'pci', 'function': '0x2'}}, {'device': 
> 'ide', 'type': 'controller', 'deviceId': 
> 'd5a2dd13-138a-482b-9bc3-994b10ec4100', 'address': {'slot': '0x01', 'bus': 
> '0x00', 'domain': '0x', 'type': 'pci', 'function': '0x1'}}, {'device': 
> 'virtio-serial', 'type': 'controller', 'deviceId': 
> '9e695172-c9b0-47df-bc76-8170219dec28', 'address': {'slot': '0x05', 'bus': 
> '0x00', 'domain': '0x', 'type': 'pci', 'function': '0x0'}}]
> guestDiskMapping = {}
> vmType = kvm
> displaySecurePort = -1
> exitReason = 1
> memSize = 6000
> displayPort = -1
> clientIp =
> spiceSecureChannels = 
> smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir
> smp = 4
> displayIp = 0
> display = vnc
> exitCode = 1
>
>
> systemctl status ovirt-ha-agent.service -l
> ● 

Re: [ovirt-users] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

[Matt .]

OK, I already thought that but where is this saved as I don't have any
rights as root to the ha_agent folder on the HE storage ?

In worst case scenario, how would i be able to deploy a new hosted
engine from a hosted engine ? This sounds undoable to me and also
unwanted as the HE is OK so far.

2016-07-21 9:41 GMT+02:00 Simone Tiraboschi :
> On Thu, Jul 21, 2016 at 9:27 AM, Matt .  wrote:
>> Even when I change that on each host before I do a new deploy it still
>> uses the old GW address.
>
> If you deploy additional hosts with the CLI utility, each new host
> will be deployed consuming the answerfile generated by the first host
> and saved on the shared storage.
> You have to manually tweak there if you to avoid.
>
> Another smarted option is to deploy additional HE host from the
> webadmin interface.
>
>
>> 2016-07-21 9:24 GMT+02:00 Simone Tiraboschi :
>>> On Wed, Jul 20, 2016 at 11:57 PM, Matt .  wrote:
 OK, I tried to edit the answerfiles on the other hosts to use another
 IP but it doesn't ping and still uses the old GW address.

 Any idea ?
>>>
>>> The gateway address is saved under
>>> /etc/ovirt-hosted-engine/hosted-engine.conf
>>> on each host.
>>>
 2016-07-20 22:27 GMT+02:00 Matt . :
> Maybe it's a good idea to be able to add multiple addresses it should
> ping in order of response.
>
> 2016-07-20 22:13 GMT+02:00 Sandro Bonazzola :
>> Il 20/Lug/2016 10:06 PM, "Matt ."  ha scritto:
>>>
>>> Hi,
>>>
>>> I'm trying to add a host to a HE installation but my gateway is not
>>> pingable. It's a floating IP which is usable but not pingable in this
>>> case.
>>>
>>> During the first install of the HE I could give any IP to ping and I
>>> used a source IP for the floating GW address.
>>>
>>> What can I do to get around this as the network is OK, even when the
>>> GW is not pingable.
>>
>> I think that gw not pingable will be interpreted as network failure by 
>> the
>> agent and will lower the score of the hosts.
>>
>>>
>>> Any idea is welcome!
>>>
>>> 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

Re: [ovirt-users] trying to upgrade host engine 4.0 to 4.1

[Simone Tiraboschi]

On Wed, Jul 20, 2016 at 10:26 PM, Rafael Almeida
 wrote:
> Hello, i'm trying to upgrade my ovirt engine host  4.0.0.6-1 in my centos
> 7.2 x64 to 4.1, using:

We just released 4.0.1, not 4.1: https://www.ovirt.org/release/4.0.1/

> yum update "ovirt-engine-setup*"
>
> but not work:
>
> No packages marked for update
> my repos are:
>
> CentOS-Base.repo   CentOS-Media.repoepel-testing.repo
> CentOS-CR.repo CentOS-Sources.repo  ovirt-4.0-dependencies.repo
> CentOS-Debuginfo.repo  CentOS-Vault.repoovirt-4.0.repo
> CentOS-fasttrack.repo  epel.repo
> if I try with the command
>
> yum install vdsm*
>
> list the new version (4.1)
>
> vdsm  x86_64 4.18.4.1-0.el7.centos  ovirt-4.0
>
> what is the problem? please helpme
>
> Thnx
>
> Rafael Almeida Orellana
>
>
> ___
> 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] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

[Simone Tiraboschi]

On Thu, Jul 21, 2016 at 9:27 AM, Matt .  wrote:
> Even when I change that on each host before I do a new deploy it still
> uses the old GW address.

If you deploy additional hosts with the CLI utility, each new host
will be deployed consuming the answerfile generated by the first host
and saved on the shared storage.
You have to manually tweak there if you to avoid.

Another smarted option is to deploy additional HE host from the
webadmin interface.


> 2016-07-21 9:24 GMT+02:00 Simone Tiraboschi :
>> On Wed, Jul 20, 2016 at 11:57 PM, Matt .  wrote:
>>> OK, I tried to edit the answerfiles on the other hosts to use another
>>> IP but it doesn't ping and still uses the old GW address.
>>>
>>> Any idea ?
>>
>> The gateway address is saved under
>> /etc/ovirt-hosted-engine/hosted-engine.conf
>> on each host.
>>
>>> 2016-07-20 22:27 GMT+02:00 Matt . :
 Maybe it's a good idea to be able to add multiple addresses it should
 ping in order of response.

 2016-07-20 22:13 GMT+02:00 Sandro Bonazzola :
> Il 20/Lug/2016 10:06 PM, "Matt ."  ha scritto:
>>
>> Hi,
>>
>> I'm trying to add a host to a HE installation but my gateway is not
>> pingable. It's a floating IP which is usable but not pingable in this
>> case.
>>
>> During the first install of the HE I could give any IP to ping and I
>> used a source IP for the floating GW address.
>>
>> What can I do to get around this as the network is OK, even when the
>> GW is not pingable.
>
> I think that gw not pingable will be interpreted as network failure by the
> agent and will lower the score of the hosts.
>
>>
>> Any idea is welcome!
>>
>> 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

Re: [ovirt-users] 3.5 to 3.6 upgrade stuck

[Simone Tiraboschi]

On Thu, Jul 21, 2016 at 7:14 AM, Robert Story  wrote:
> I have a 3.5 hosted-engine with 5 el7 nodes. Today I tried upgrading to 3.6.
> The engine upgrade went great, no problems.
>
> I had a host in maintenance mode, so I added the 3.6 repos and ran yum
> update. I waited for the upgrade successful message. I checked the score
> for the node, and it was still 2400, not 3400. Tried rebooting, but no
> luck. So I put another host in maintenance mode, and had the same result.

MainThread::INFO::2016-07-20
23:44:30,352::upgrade::1031::ovirt_hosted_engine_ha.lib.upgrade.StorageServer::(upgrade_35_36)
Successfully upgraded

Everything seams OK on the upgrade path.


> Both nodes are getting this error:
>
> MainThread::ERROR::2016-07-21 
> 01:05:04,187::brokerlink::279::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(_communicate)
>  Connection closed: Connection timed out
> MainThread::ERROR::2016-07-21 
> 01:05:04,188::agent::205::ovirt_hosted_engine_ha.agent.agent.Agent::(_run_agent)
>  Error: 'Failed to start monitor , options {'hostname': 
> 'poseidon.netsec'}: Connection timed out' - trying to restart agent

Can you please attach also broker.log? maybe the issue is somewhere else.

> I've attached logs from the second host coming up after a reboot, along
> with engine log from the same timeframe.
>
> Any suggestions on a way forward would be greatly appreciated.
>
>
> Robert
>
> --
> Senior Software Engineer @ Parsons
>
> ___
> 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] vdsm ssl errors

[Швыгин Алексей Михайлович]

Check time/ntp settings on nodes and engine.

--
a.shvy...@grfc.ru

From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of C. 
Handel
Sent: Thursday, July 21, 2016 10:03 AM
To: Oved Ourfali
Cc: users
Subject: Re: [ovirt-users] vdsm ssl errors

as far as i can tell, everything is fine.

VMs are running, i can migrate them, they are restarted on crash, etc.

No events in the dashboard, performance data is available.

Greetings
   Christoph

On Thu, Jul 21, 2016 at 8:59 AM, Oved Ourfali 
> wrote:

Other than errors, anything that doesn't work on your environment?
On Jul 21, 2016 09:48, "Yaniv Kaul" > 
wrote:
Can you share engine and VDSM logs please?
TIA,
Y.

On Thu, Jul 21, 2016 at 9:22 AM, C. Handel 
> wrote:
i have an ovirt 4.0.1 installation on two nodes. Hosted Engine. San storage 
backend.

For some reason the vdsmd on the nodes is logging an error every few seconds:


vdsm vds.dispatcher ERROR SSL error during reading data: unexpected eof


Running tcpdump it is a connect from the node to itself. I can't figure out 
what is wrong. Can someone give me a hint?

Greetings
   Christoph

___
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] Import of ova failed

[Shahar Havivi]

On 20.07.16 20:06, Richard W.M. Jones wrote:
> On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > >
> > > The import doesn't happen automatically, you have to do the final step
> > > manually (when using the command line).  See:
> > >
> > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > >
> > > However that error shouldn't happen.  It looks like the name is the
> > > same as the name of an existing VM.  From virt-v2v you can do the
> > > whole conversion/import over again, this time adding the `-on
> > > new_name' option to the command line (obviously choosing a name which
> > > is not otherwise being used).
> > >
> > > I don't know if there's a way to get oVirt to change the name when
> > > importing from the export domain.  As far as I know you have to start
> > > the import from scratch.
> > >
> > >
> > There's no existing VM with that name that I can see. It may have come from
> > one of my earlier import attempts,
> > though that earlier attempt did not show up in the GUI, it did write files
> > to the export domain.
> > 
> > I re-ran the conversion again with a rename but it failed to import it
> > again, with the same error.
> > 
> > Could there be a record in the DB somewhere, or does it look at the files
> > alone? Just trying to work out where the conflict is.
> 
> I had a look at the ovirt-engine code where
> ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come
> from a database check.  However I'm not really familiar enough with
> the code to be sure.  Probably best to ask an oVirt developer, or try
> dumping the database to see if "wvm2" appears in a column anywhere.
> 
> Rich.
> 
> -- 
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> Fedora Windows cross-compiler. Compile Windows programs, test, and
> build Windows installers. Over 100 libraries supported.
> http://fedoraproject.org/wiki/MinGW
It may be in the DB...
Try to run this via psql:

select vm_name from vm_static where vm_name='wvm2';

and see if there is a result...
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] vdsm ssl errors

[C. Handel]

all nodes and engines are synced to the same timeserver.

as far as i can tell, the connection is from the node itself, to the vdsm
on the node, so no time difference can occur.

the certificate that get's presented be vdsm on port 54321 looks ok.

For what it is worth, I changed the certificate of the hosted-engine web
interface by reconfiguring apaches mod_ssl, not touching any certificate in
hosted-engine:/etc/pki/ovirt-*

On Thu, Jul 21, 2016 at 9:22 AM, Швыгин Алексей Михайлович <
a.shvy...@grfc.ru> wrote:

> Check time/ntp settings on nodes and engine.
>
>
>
> --
>
> a.shvy...@grfc.ru
>
>
>
> *From:* users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] *On
> Behalf Of *C. Handel
> *Sent:* Thursday, July 21, 2016 10:03 AM
> *To:* Oved Ourfali
> *Cc:* users
> *Subject:* Re: [ovirt-users] vdsm ssl errors
>
>
>
> as far as i can tell, everything is fine.
>
>
>
> VMs are running, i can migrate them, they are restarted on crash, etc.
>
>
>
> No events in the dashboard, performance data is available.
>
>
>
> Greetings
>
>Christoph
>
>
>
> On Thu, Jul 21, 2016 at 8:59 AM, Oved Ourfali  wrote:
>
> Other than errors, anything that doesn't work on your environment?
>
> On Jul 21, 2016 09:48, "Yaniv Kaul"  wrote:
>
> Can you share engine and VDSM logs please?
>
> TIA,
>
> Y.
>
>
>
> On Thu, Jul 21, 2016 at 9:22 AM, C. Handel  wrote:
>
> i have an ovirt 4.0.1 installation on two nodes. Hosted Engine. San
> storage backend.
>
>
>
> For some reason the vdsmd on the nodes is logging an error every few
> seconds:
>
>
>
>
>
> vdsm vds.dispatcher ERROR SSL error during reading data: unexpected eof
>
>
>
>
>
> Running tcpdump it is a connect from the node to itself. I can't figure
> out what is wrong. Can someone give me a hint?
>
>
>
> Greetings
>
>Christoph
>
>
> ___
> 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] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

[Matt .]

Even when I change that on each host before I do a new deploy it still
uses the old GW address.

2016-07-21 9:24 GMT+02:00 Simone Tiraboschi :
> On Wed, Jul 20, 2016 at 11:57 PM, Matt .  wrote:
>> OK, I tried to edit the answerfiles on the other hosts to use another
>> IP but it doesn't ping and still uses the old GW address.
>>
>> Any idea ?
>
> The gateway address is saved under
> /etc/ovirt-hosted-engine/hosted-engine.conf
> on each host.
>
>> 2016-07-20 22:27 GMT+02:00 Matt . :
>>> Maybe it's a good idea to be able to add multiple addresses it should
>>> ping in order of response.
>>>
>>> 2016-07-20 22:13 GMT+02:00 Sandro Bonazzola :
 Il 20/Lug/2016 10:06 PM, "Matt ."  ha scritto:
>
> Hi,
>
> I'm trying to add a host to a HE installation but my gateway is not
> pingable. It's a floating IP which is usable but not pingable in this
> case.
>
> During the first install of the HE I could give any IP to ping and I
> used a source IP for the floating GW address.
>
> What can I do to get around this as the network is OK, even when the
> GW is not pingable.

 I think that gw not pingable will be interpreted as network failure by the
 agent and will lower the score of the hosts.

>
> Any idea is welcome!
>
> 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

Re: [ovirt-users] New host HE 4.0 -> [ ERROR ] Failed to execute stage 'Environment customization': Specified gateway is not pingable

[Simone Tiraboschi]

On Wed, Jul 20, 2016 at 11:57 PM, Matt .  wrote:
> OK, I tried to edit the answerfiles on the other hosts to use another
> IP but it doesn't ping and still uses the old GW address.
>
> Any idea ?

The gateway address is saved under
/etc/ovirt-hosted-engine/hosted-engine.conf
on each host.

> 2016-07-20 22:27 GMT+02:00 Matt . :
>> Maybe it's a good idea to be able to add multiple addresses it should
>> ping in order of response.
>>
>> 2016-07-20 22:13 GMT+02:00 Sandro Bonazzola :
>>> Il 20/Lug/2016 10:06 PM, "Matt ."  ha scritto:

 Hi,

 I'm trying to add a host to a HE installation but my gateway is not
 pingable. It's a floating IP which is usable but not pingable in this
 case.

 During the first install of the HE I could give any IP to ping and I
 used a source IP for the floating GW address.

 What can I do to get around this as the network is OK, even when the
 GW is not pingable.
>>>
>>> I think that gw not pingable will be interpreted as network failure by the
>>> agent and will lower the score of the hosts.
>>>

 Any idea is welcome!

 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

Re: [ovirt-users] Cannot configure/save Network Interfaces in a freshly installed oVirt Node 4.0.1

[Michael Burman]

Hi Ariel,

It seems like you assigned a role to this network , from the name of your
network 'migration', i guess you assigned this network with migration role.)
In such case, this role requires a boot protocol(static ip or dhcp).
You can't setup networks if your network has one of this roles
(migration/display/gluster).

So, if you want this network to be your migration network, you must assign
a boot protocol.
If you don't want this network to be a migration network, you can choose
the default network for this 'ovirtmgmt' via the 'Clusters' main tab >
'Logical Networks' sub tab.

Thanks,



On Wed, Jul 20, 2016 at 6:26 PM, Ariel Perez - BookIt.com System
Administrator  wrote:

> Hi everyone,
> I'm trying to save the Network Interfaces configuration in a freshly
> installed hypervisor in version 4.0.1, and I'm getting this error:
>
>
> Error while executing action:
>
> blade1c1.ism.ld:
>
>- Cannot setup Networks. Role (migration/display/gluster) network
>'migration' hasn't boot protocol assigned.
>
>
> The configuration is exactly the same as in the rest of the nodes (3.6
> latest one). I've been googling it but nothing.
>
> Thank u in advance,
>
> Ariel
>
> --
> This email was Virus checked by UTM 9. For issues please contact the Windows 
> Systems Admin.
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 
Michael Burman
RedHat Israel, RHEV-M QE Network Team

Mobile: 054-5355725
IRC: mburman
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] synchronize cache

[Sandro Bonazzola]

On Thu, Jul 21, 2016 at 7:11 AM, Markus Scherer 
wrote:

> Sorry the same problem
>
>
>
Maybe you hit a mirror out of sync, can you try using baseurl instead of
mirrorlist in the ovirt .repo files?




> Thx
>
> Am 20.07.2016 um 16:45 schrieb Sandro Bonazzola:
>
>
>
> On Mon, Jul 18, 2016 at 9:41 AM, Markus Scherer  wrote:
>
>> Hi,
>>
>> on an fresh installed fedora server 23 i got a "Failed to synchronize
>> cache for repo 'ovirt-4.0'".
>> I have done a "dnf clean all" a "dnf check-update" and a reboot but
>> always the same problem.
>>
>> thx for help
>>
>
> I regenerated the metadata within the repo, can you please try again?
> Thanks,
>
>
>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
>
>


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] vdsm ssl errors

[C. Handel]

as far as i can tell, everything is fine.

VMs are running, i can migrate them, they are restarted on crash, etc.

No events in the dashboard, performance data is available.

Greetings
   Christoph

On Thu, Jul 21, 2016 at 8:59 AM, Oved Ourfali  wrote:

> Other than errors, anything that doesn't work on your environment?
> On Jul 21, 2016 09:48, "Yaniv Kaul"  wrote:
>
>> Can you share engine and VDSM logs please?
>> TIA,
>> Y.
>>
>> On Thu, Jul 21, 2016 at 9:22 AM, C. Handel  wrote:
>>
>>> i have an ovirt 4.0.1 installation on two nodes. Hosted Engine. San
>>> storage backend.
>>>
>>> For some reason the vdsmd on the nodes is logging an error every few
>>> seconds:
>>>
>>>
>>> vdsm vds.dispatcher ERROR SSL error during reading data: unexpected eof
>>>
>>>
>>> Running tcpdump it is a connect from the node to itself. I can't figure
>>> out what is wrong. Can someone give me a hint?
>>>
>>> Greetings
>>>Christoph
>>>
>>> ___
>>> 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] vdsm ssl errors

[C. Handel]

longer logs attached, excerpts:

---+ vdsm

Reactor thread::INFO::2016-07-21
08:01:19,544::protocoldetector::72::ProtocolDetector.AcceptorImpl::(handle_accept)
Accepting connection from :::140.181.138.208:59502
Reactor thread::DEBUG::2016-07-21
08:01:19,551::protocoldetector::85::ProtocolDetector.Detector::(__init__)
Using required_size=11
Reactor thread::INFO::2016-07-21
08:01:19,553::protocoldetector::121::ProtocolDetector.Detector::(handle_read)
Detected protocol stomp from :::140.181.138.208:59502
Reactor thread::INFO::2016-07-21
08:01:19,553::stompreactor::101::Broker.StompAdapter::(_cmd_connect)
Processing CONNECT request
Reactor thread::DEBUG::2016-07-21
08:01:19,554::stompreactor::492::protocoldetector.StompDetector::(handle_socket)
Stomp detected from (':::140.181.138.208', 59502)
JsonRpc (StompReactor)::INFO::2016-07-21
08:01:19,554::stompreactor::128::Broker.StompAdapter::(_cmd_subscribe)
Subscribe command received
...

JsonRpc (StompReactor)::ERROR::2016-07-21
08:01:21,411::betterAsyncore::113::vds.dispatcher::(recv) SSL error during
reading data: unexpected eof


---+ engine


2016-07-20 08:00:48,445 INFO
 [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler1) [1cff1b56] Fetched 7 VMs from VDS
'a46f9de2-4b79-45d4-bed5-f4f472eb8361'
2016-07-20 08:01:03,460 INFO
 [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler3) [78d8aa89] Fetched 0 VMs from VDS
'6f7a9201-e753-4875-b89d-024120067687'
2016-07-20 08:01:03,473 INFO
 [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler2) [71a27a96] Fetched 7 VMs from VDS
'a46f9de2-4b79-45d4-bed5-f4f472eb8361'
2016-07-20 08:01:18,488 INFO
 [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler2) [71a27a96] Fetched 0 VMs from VDS
'6f7a9201-e753-4875-b89d-024120067687'
2016-07-20 08:01:18,500 INFO
 [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler9) [47c419da] Fetched 7 VMs from VDS
'a46f9de2-4b79-45d4-bed5-f4f472eb8361'
2016-07-20 08:01:33,514 INFO
 [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler8) [735789] Fetched 0 VMs from VDS
'6f7a9201-e753-4875-b89d-024120067687'
2016-07-20 08:01:33,527 INFO
 [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler3) [78d8aa89] Fetched 7 VMs from VDS
'a46f9de2-4b79-45d4-bed5-f4f472eb8361'
2016-07-20 08:01:48,543 INFO
 [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher]
(DefaultQuartzScheduler8) [735789] Fetched 0 VMs from VDS
'6f7a9201-e753-4875-b89d-024120067687'


Greetings
   Christoph

On Thu, Jul 21, 2016 at 8:47 AM, Yaniv Kaul  wrote:

> Can you share engine and VDSM logs please?
> TIA,
> Y.
>
> On Thu, Jul 21, 2016 at 9:22 AM, C. Handel  wrote:
>
>> i have an ovirt 4.0.1 installation on two nodes. Hosted Engine. San
>> storage backend.
>>
>> For some reason the vdsmd on the nodes is logging an error every few
>> seconds:
>>
>>
>> vdsm vds.dispatcher ERROR SSL error during reading data: unexpected eof
>>
>>
>> Running tcpdump it is a connect from the node to itself. I can't figure
>> out what is wrong. Can someone give me a hint?
>>
>> Greetings
>>Christoph
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>


logs.tar.gz
Description: GNU Zip compressed data
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] vdsm ssl errors

[Oved Ourfali]

Other than errors, anything that doesn't work on your environment?
On Jul 21, 2016 09:48, "Yaniv Kaul"  wrote:

> Can you share engine and VDSM logs please?
> TIA,
> Y.
>
> On Thu, Jul 21, 2016 at 9:22 AM, C. Handel  wrote:
>
>> i have an ovirt 4.0.1 installation on two nodes. Hosted Engine. San
>> storage backend.
>>
>> For some reason the vdsmd on the nodes is logging an error every few
>> seconds:
>>
>>
>> vdsm vds.dispatcher ERROR SSL error during reading data: unexpected eof
>>
>>
>> Running tcpdump it is a connect from the node to itself. I can't figure
>> out what is wrong. Can someone give me a hint?
>>
>> Greetings
>>Christoph
>>
>> ___
>> 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] vdsm ssl errors

[Yaniv Kaul]

Can you share engine and VDSM logs please?
TIA,
Y.

On Thu, Jul 21, 2016 at 9:22 AM, C. Handel  wrote:

> i have an ovirt 4.0.1 installation on two nodes. Hosted Engine. San
> storage backend.
>
> For some reason the vdsmd on the nodes is logging an error every few
> seconds:
>
>
> vdsm vds.dispatcher ERROR SSL error during reading data: unexpected eof
>
>
> Running tcpdump it is a connect from the node to itself. I can't figure
> out what is wrong. Can someone give me a hint?
>
> Greetings
>Christoph
>
> ___
> 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] synchronize cache

[Markus Scherer]

Sorry the same problem


Thx


Am 20.07.2016 um 16:45 schrieb Sandro Bonazzola:



On Mon, Jul 18, 2016 at 9:41 AM, Markus Scherer > wrote:


Hi,

on an fresh installed fedora server 23 i got a "Failed to
synchronize cache for repo 'ovirt-4.0'".
I have done a "dnf clean all" a "dnf check-update" and a reboot
but always the same problem.

thx for help


I regenerated the metadata within the repo, can you please try again?
Thanks,

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




--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com 


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

[ovirt-users] vdsm ssl errors

[C. Handel]

i have an ovirt 4.0.1 installation on two nodes. Hosted Engine. San storage
backend.

For some reason the vdsmd on the nodes is logging an error every few
seconds:


vdsm vds.dispatcher ERROR SSL error during reading data: unexpected eof


Running tcpdump it is a connect from the node to itself. I can't figure out
what is wrong. Can someone give me a hint?

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