Re: [ovirt-users] ovirt-engine-webadmin-portal-debuginfo

2017-02-06 Thread Yedidyah Bar David
On Tue, Feb 7, 2017 at 1:22 AM, Edward Clay  wrote:
> Looks like I originally had a newer version of the debuginfo packages
> installed that didn't work.  So the log output I provided did lead to the
> answer I needed.  Evidently yum install ovirt-engine*debuginfo seems to
> install the latest version available instead of the one that matches the
> currently installed ovirt-engine.

Indeed. We have a related bug, still didn't decide what to do with it:

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

>
> On Mon, Feb 6, 2017 at 2:47 PM, Edward Clay 
> wrote:
>>
>> Hello,  I've run into a situation where I'm getting an uncaught exception
>> error and it seems like the log entries are obfuscated and one needs to
>> install the ovirt-engine-weba-portal-debuginfo rpm to decipher whats really
>> going on.  I've installed this package and restarted the ovirt-engine but
>> I'm still not getting useful info in the ui.log.  Any ideas what how I can
>> resolve this?
>>
>>
>> # rpm -qa|grep ovirt.*debuginfo
>> ovirt-engine-userportal-debuginfo-4.0.5.5-1.el7.centos.noarch
>> ovirt-engine-webadmin-portal-debuginfo-4.0.5.5-1.el7.centos.noarch
>>
>> This is an example of the log entry when attempting to create a vm using a
>> template that contains a disk.
>> 2017-02-06 14:42:15,538 ERROR
>> [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default
>> task-67) [] Permutation name: 587E534EAE351BE2F229E0B865EFB2D3
>> 2017-02-06 14:42:15,539 ERROR
>> [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default
>> task-67) [] Uncaught exception:
>> com.google.gwt.core.client.JavaScriptException: (TypeError)
>>  __gwt$exception: : Cannot read property 'f' of undefined
>> at
>> org.ovirt.engine.ui.uicommonweb.models.storage.DisksAllocationModel.$updateImageToDestinationDomainMap(DisksAllocationModel.java:307)
>> at
>> org.ovirt.engine.ui.uicommonweb.models.storage.DisksAllocationModel.$getImageToDestinationDomainMap(DisksAllocationModel.java:133)
>> at
>> org.ovirt.engine.ui.uicommonweb.models.userportal.UserPortalListModel.$postVmNameUniqueCheck(UserPortalListModel.java:975)
>> at
>> org.ovirt.engine.ui.uicommonweb.models.userportal.UserPortalListModel$10.onSuccess(UserPortalListModel.java:921)
>> at
>> org.ovirt.engine.ui.frontend.Frontend$2.$onSuccess(Frontend.java:238)
>> [frontend.jar:]
>> at
>> org.ovirt.engine.ui.frontend.Frontend$2.onSuccess(Frontend.java:238)
>> [frontend.jar:]
>> at
>> org.ovirt.engine.ui.frontend.communication.OperationProcessor$2.$onSuccess(OperationProcessor.java:139)
>> [frontend.jar:]
>> at
>> org.ovirt.engine.ui.frontend.communication.OperationProcessor$2.onSuccess(OperationProcessor.java:139)
>> [frontend.jar:]
>> at
>> org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$3$1.$onSuccess(GWTRPCCommunicationProvider.java:160)
>> [frontend.jar:]
>> at
>> org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$3$1.onSuccess(GWTRPCCommunicationProvider.java:160)
>> [frontend.jar:]
>> at
>> com.google.gwt.rpc.client.impl.RpcCallbackAdapter.onResponseReceived(RpcCallbackAdapter.java:72)
>> [gwt-servlet.jar:]
>> at
>> com.google.gwt.http.client.Request.$fireOnResponseReceived(Request.java:237)
>> [gwt-servlet.jar:]
>> at
>> com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:409)
>> [gwt-servlet.jar:]
>> at Unknown.eval(userportal-0.js@65)
>> at com.google.gwt.core.client.impl.Impl.apply(Impl.java:296)
>> [gwt-servlet.jar:]
>> at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:335)
>> [gwt-servlet.jar:]
>> at Unknown.eval(userportal-0.js@54)
>>
>> Is this as clear as the ui.log will get?
>> --
>> Best regards,
>> Edward Clay
>> Systems Administrator
>> UK2 Group - US Operations
>> Phone: 1-800-222-2165
>> FAX: 435-755-3449
>> E-mail: edward.c...@uk2group.com
>>
>> Believe in Better Hosting
>> http://www.westhost.com
>
>
>
>
> --
> Best regards,
> Edward Clay
> Systems Administrator
> UK2 Group - US Operations
> Phone: 1-800-222-2165
> FAX: 435-755-3449
> E-mail: edward.c...@uk2group.com
>
> Believe in Better Hosting
> http://www.westhost.com
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



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


Re: [ovirt-users] node-ng update failed from ovirt-node-ng-4.1.0-0 to ovirt-node-ng-image-4.1.0-1, and NM + iscsi boo issue

2017-02-06 Thread Ryan Barry
Hey Sergey -

If you check "lvs" and ensure that there's not actually a new LV from the
update, you can cleanly 'rpm -e ovirt-node-ng-image-update', and be ok
without redeploying.

Unfortunately, it's hard to tell from the logs (and '--justdb' hanging)
what's happening here, but I'll try to reproduce.

NetworkManager disablement should "stick" across upgrades, but it's
possible that iscsi roots are doing something here. I'll check for a dracut
flag, also...

On Mon, Feb 6, 2017 at 1:14 PM, Sandro Bonazzola 
wrote:

> Adding Douglas and Ryan
>
> Il 06/Feb/2017 13:32, "Sergey Kulikov"  ha scritto:
>
>>
>> 1) I've updated from 4.0.6 to 4.1.0 (on Feb 01 node-ng was at version
>> 4.1.0-0)
>> After some time engine alerted, that this node have updates to
>> ovirt-node-ng-image-4.1.0-1,
>> but update from engine timed out, there were hanging processes in ps on
>> this node:
>>
>> root 36309  0.0  0.0 113120  1564 ?Ss   19:04   0:00 bash -c
>> umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t
>> ovirt-XX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm
>> -fr \"${MYTMP}\" > /dev/null 2>&1" 0; tar --warning=no-timestamp -C
>> "${MYTMP}" -x &&  "${MYTMP}"/ovirt-host-mgmt DIALOG/dialect=str:machine
>> DIALOG/customization=bool:True
>> root 36339  0.2  0.0 496700 94208 ?S19:04   0:21
>> /bin/python /tmp/ovirt-GCmVusccfe/pythonlib/otopi/__main__.py
>> "BASE/pluginPath=str:/tmp/ovirt-GCmVusccfe/otopi-plugins"
>> APPEND:BASE/pluginGroups=str:ovirt-host-common:ovirt-host-mgmt
>> DIALOG/dialect=str:machine DIALOG/customization=bool:True
>> root 37498  0.0  0.0 113124  1452 ?S19:09   0:00 /bin/sh
>> /var/tmp/rpm-tmp.4UqJ4e 1
>> root 37560  0.0  0.0  0 0 ?S<   21:42   0:00
>> [kworker/21:2H]
>> root 37626  0.0  0.0 174516  5996 ?S19:09   0:00 rpm -Uvh
>> --quiet --justdb /usr/share/imgbased/ovirt-node
>> -ng-image-update-4.1.0-1.el7.centos.noarch.rpm
>>
>> they were hanging forever, I ended up with rebooting the node, no errors
>> in log, it was just hanging at:
>>
>> 2017-02-03 19:09:16 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:SEND   ***CONFIRM GPG_KEY Confirm use of
>> GPG Key userid=oVirt  hexkeyid=FE590CB7
>> 2017-02-03 19:09:16 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:SEND   ###
>> 2017-02-03 19:09:16 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:SEND   ### Please confirm 'GPG_KEY'
>> Confirm use of GPG Key userid=oVirt  hexkeyid=FE590CB7
>> 2017-02-03 19:09:16 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:SEND   ### Response is CONFIRM
>> GPG_KEY=yes|no or ABORT GPG_KEY
>> 2017-02-03 19:09:16 DEBUG otopi.plugins.otopi.dialog.machine
>> dialog.__logString:204 DIALOG:RECEIVECONFIRM GPG_KEY=yes
>> 2017-02-03 19:09:16 INFO otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.info:80 Yum Status: Running Test Transaction
>> Running Transaction Check
>> 2017-02-03 19:09:16 INFO otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.info:80 Yum Status: Running Transaction
>> 2017-02-03 19:09:16 INFO otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.info:80 Yum install: 1/2: ovirt-node-ng-image-4.1.0-1.el
>> 7.centos.noarch
>> 2017-02-03 19:09:20 DEBUG otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-4.1.0-1.el
>> 7.centos.noarch
>> 2017-02-03 19:09:20 INFO otopi.plugins.otopi.packagers.yumpackager
>> yumpackager.info:80 Yum install: 2/2: ovirt-node-ng-image-update-4.1
>> .0-1.el7.centos.noarch
>>
>> now my node have this layout:
>> # imgbase layout
>> ovirt-node-ng-4.1.0-0.20170201.0
>>  +- ovirt-node-ng-4.1.0-0.20170201.0+1
>> (so update failed)
>> but 4.1.0-1 rpms are marked as "installed" and yum can't find any
>> updates, can I rollback to base layout without installed  4.1.0-1 rms ?
>> imgbase rollback needs at least 2 layers over base.
>>
>> Or maybe the only way is to reinstall this node?
>>
>> 2) And another question, how can I disable NetworkManger permanently, or
>> exclude some interfaces permanently?
>> I've tried to disable NetworkManger by systemctl, but after update from
>> 4.0 to 4.1 it was re-enabled(so it's not persistent between updates).
>> I've an issue with iscsi root and enabled NetworkManger, because NM tries
>> to bring down\up my iscsi interfaces on boot, and sometimes FS remounting RO
>> because of IO errors, I can't put NM_CONTROLLED=no in ifcfg, because
>> ifcfg is generated by dracut at every boot.
>>
>>
>> -
>>
>> ___
>> 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] VM fails to start - oVirt 4.1 and Node NG 4.1

2017-02-06 Thread Anantha Raghava

Hi,

Last evening on my new environment, I installed oVirt engine 4.1 and two 
nodes (Dell R 710) with Node ng 4.1. Post installation, node updates 
also completed successfully. I created a new VM and installed with 
Ubuntu Precise Pangolin LTS OS and OS installation also completed 
successfully. But when I try to shutdown VM and try to run again, engine 
reports VM run failed. But when I try to use "Run Once", the VM starts 
to Run.


Can some one guide how to fix this?

--

Thanks & Regards,


Anantha Raghava

eXzaTech Consulting And Services Pvt. Ltd.

Ph: +91-9538849179, E-mail: rag...@exzatechconsulting.com 



URL: http://www.exzatechconsulting.com 



DISCLAIMER:
This e-mail communication and any attachments may be privileged and 
confidential to eXza Technology Consulting & Services, and are intended 
only for the use of the recipients named above If you are not the 
addressee you may not copy, forward, disclose or use any part of it. If 
you have received this message in error, please delete it and all copies 
from your system and notify the sender immediately by return e-mail. 
Internet communications cannot be guaranteed to be timely, secure, error 
or virus-free. The sender does not accept liability for any errors or 
omissions.



Do not print this e-mail unless required. Save Paper & trees.

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


Re: [ovirt-users] ovirt-engine-webadmin-portal-debuginfo

2017-02-06 Thread Edward Clay
Looks like I originally had a newer version of the debuginfo packages
installed that didn't work.  So the log output I provided did lead to the
answer I needed.  Evidently yum install ovirt-engine*debuginfo seems to
install the latest version available instead of the one that matches the
currently installed ovirt-engine.

On Mon, Feb 6, 2017 at 2:47 PM, Edward Clay 
wrote:

> Hello,  I've run into a situation where I'm getting an uncaught exception
> error and it seems like the log entries are obfuscated and one needs to
> install the ovirt-engine-weba-portal-debuginfo rpm to decipher whats
> really going on.  I've installed this package and restarted the
> ovirt-engine but I'm still not getting useful info in the ui.log.  Any
> ideas what how I can resolve this?
>
>
> # rpm -qa|grep ovirt.*debuginfo
> ovirt-engine-userportal-debuginfo-4.0.5.5-1.el7.centos.noarch
> ovirt-engine-webadmin-portal-debuginfo-4.0.5.5-1.el7.centos.noarch
>
> This is an example of the log entry when attempting to create a vm using a
> template that contains a disk.
> 2017-02-06 14:42:15,538 ERROR 
> [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService]
> (default task-67) [] Permutation name: 587E534EAE351BE2F229E0B865EFB2D3
> 2017-02-06 14:42:15,539 ERROR 
> [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService]
> (default task-67) [] Uncaught exception: 
> com.google.gwt.core.client.JavaScriptException:
> (TypeError)
>  __gwt$exception: : Cannot read property 'f' of undefined
> at org.ovirt.engine.ui.uicommonweb.models.storage.
> DisksAllocationModel.$updateImageToDestinationDomain
> Map(DisksAllocationModel.java:307)
> at org.ovirt.engine.ui.uicommonweb.models.storage.
> DisksAllocationModel.$getImageToDestinationDomainMap
> (DisksAllocationModel.java:133)
> at org.ovirt.engine.ui.uicommonweb.models.userportal.
> UserPortalListModel.$postVmNameUniqueCheck(UserPortalListModel.java:975)
> at org.ovirt.engine.ui.uicommonweb.models.userportal.
> UserPortalListModel$10.onSuccess(UserPortalListModel.java:921)
> at 
> org.ovirt.engine.ui.frontend.Frontend$2.$onSuccess(Frontend.java:238)
> [frontend.jar:]
> at 
> org.ovirt.engine.ui.frontend.Frontend$2.onSuccess(Frontend.java:238)
> [frontend.jar:]
> at org.ovirt.engine.ui.frontend.communication.
> OperationProcessor$2.$onSuccess(OperationProcessor.java:139)
> [frontend.jar:]
> at org.ovirt.engine.ui.frontend.communication.
> OperationProcessor$2.onSuccess(OperationProcessor.java:139)
> [frontend.jar:]
> at org.ovirt.engine.ui.frontend.communication.
> GWTRPCCommunicationProvider$3$1.$onSuccess(GWTRPCCommunicationProvider.java:160)
> [frontend.jar:]
> at org.ovirt.engine.ui.frontend.communication.
> GWTRPCCommunicationProvider$3$1.onSuccess(GWTRPCCommunicationProvider.java:160)
> [frontend.jar:]
> at com.google.gwt.rpc.client.impl.RpcCallbackAdapter.
> onResponseReceived(RpcCallbackAdapter.java:72) [gwt-servlet.jar:]
> at 
> com.google.gwt.http.client.Request.$fireOnResponseReceived(Request.java:237)
> [gwt-servlet.jar:]
> at 
> com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:409)
> [gwt-servlet.jar:]
> at Unknown.eval(userportal-0.js@65)
> at com.google.gwt.core.client.impl.Impl.apply(Impl.java:296)
> [gwt-servlet.jar:]
> at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:335)
> [gwt-servlet.jar:]
> at Unknown.eval(userportal-0.js@54)
>
> Is this as clear as the ui.log will get?
> --
> Best regards,
> Edward Clay
> Systems Administrator
> UK2 Group - US Operations
> Phone: 1-800-222-2165
> FAX: 435-755-3449
> E-mail: edward.c...@uk2group.com
>
> Believe in Better Hosting
> http://www.westhost.com
>



-- 
Best regards,
Edward Clay
Systems Administrator
UK2 Group - US Operations
Phone: 1-800-222-2165
FAX: 435-755-3449
E-mail: edward.c...@uk2group.com

Believe in Better Hosting
http://www.westhost.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] missing hvc0 device on hosted engine

2017-02-06 Thread Martin Sivak
Hi,

we know about this and we already pushed patches that should resolve
this issue in 4.1.1 (one was merged today in fact).

We track the issue here:
https://bugzilla.redhat.com/show_bug.cgi?id=1364132 and the patch that
should resolve it is here: https://gerrit.ovirt.org/#/c/71472/

Applying the change manually or waiting for a new snapshot package in
http://resources.ovirt.org/pub/ovirt-4.1-snapshot/rpm//noarch/
might help you in the meantime.

Best regards

--
Martin Sivak
SLA / oVirt


On Mon, Feb 6, 2017 at 8:14 PM, Berger, Sandy  wrote:
> I’ve been running oVirt 4.0.x for a while now and upgraded the engine and
> hosts to 4.1. Sometimes, on both 4.0 and 4.1, trying to run the
> “hosted-engine –console” command gives the following results:
>
>
>
> The engine VM is running on this host
>
> Connected to domain HostedEngine
>
> Escape character is ^]
>
> error: internal error: cannot find character device 
>
>
>
> Once this starts occurring, it never works again.
>
>
>
> When this happens I note that the hvc0 device does not exist in /dev and
> therefore there is no getty process running for that device. I notice that
> the “Enable VirtIO serial console” box is not checked on the hosted engine
> VM but when I check it and click OK it’s unchecked again when I open up the
> edit window again.
>
>
>
> How do I get console control back from my oVirt hosts?
>
>
>
> Thank you,
>
>
>
> Sandy Berger
>
>
>
> Follow Us: Facebook | Twitter | LinkedIn | YouTube
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] ovirt-engine-webadmin-portal-debuginfo

2017-02-06 Thread Edward Clay
Hello,  I've run into a situation where I'm getting an uncaught exception
error and it seems like the log entries are obfuscated and one needs to
install the ovirt-engine-weba-portal-debuginfo rpm to decipher whats really
going on.  I've installed this package and restarted the ovirt-engine but
I'm still not getting useful info in the ui.log.  Any ideas what how I can
resolve this?


# rpm -qa|grep ovirt.*debuginfo
ovirt-engine-userportal-debuginfo-4.0.5.5-1.el7.centos.noarch
ovirt-engine-webadmin-portal-debuginfo-4.0.5.5-1.el7.centos.noarch

This is an example of the log entry when attempting to create a vm using a
template that contains a disk.
2017-02-06 14:42:15,538 ERROR
[org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService]
(default task-67) [] Permutation name: 587E534EAE351BE2F229E0B865EFB2D3
2017-02-06 14:42:15,539 ERROR
[org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService]
(default task-67) [] Uncaught exception:
com.google.gwt.core.client.JavaScriptException: (TypeError)
 __gwt$exception: : Cannot read property 'f' of undefined
at
org.ovirt.engine.ui.uicommonweb.models.storage.DisksAllocationModel.$updateImageToDestinationDomainMap(DisksAllocationModel.java:307)
at
org.ovirt.engine.ui.uicommonweb.models.storage.DisksAllocationModel.$getImageToDestinationDomainMap(DisksAllocationModel.java:133)
at
org.ovirt.engine.ui.uicommonweb.models.userportal.UserPortalListModel.$postVmNameUniqueCheck(UserPortalListModel.java:975)
at
org.ovirt.engine.ui.uicommonweb.models.userportal.UserPortalListModel$10.onSuccess(UserPortalListModel.java:921)
at
org.ovirt.engine.ui.frontend.Frontend$2.$onSuccess(Frontend.java:238)
[frontend.jar:]
at
org.ovirt.engine.ui.frontend.Frontend$2.onSuccess(Frontend.java:238)
[frontend.jar:]
at
org.ovirt.engine.ui.frontend.communication.OperationProcessor$2.$onSuccess(OperationProcessor.java:139)
[frontend.jar:]
at
org.ovirt.engine.ui.frontend.communication.OperationProcessor$2.onSuccess(OperationProcessor.java:139)
[frontend.jar:]
at
org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$3$1.$onSuccess(GWTRPCCommunicationProvider.java:160)
[frontend.jar:]
at
org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$3$1.onSuccess(GWTRPCCommunicationProvider.java:160)
[frontend.jar:]
at
com.google.gwt.rpc.client.impl.RpcCallbackAdapter.onResponseReceived(RpcCallbackAdapter.java:72)
[gwt-servlet.jar:]
at
com.google.gwt.http.client.Request.$fireOnResponseReceived(Request.java:237)
[gwt-servlet.jar:]
at
com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:409)
[gwt-servlet.jar:]
at Unknown.eval(userportal-0.js@65)
at com.google.gwt.core.client.impl.Impl.apply(Impl.java:296)
[gwt-servlet.jar:]
at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:335)
[gwt-servlet.jar:]
at Unknown.eval(userportal-0.js@54)

Is this as clear as the ui.log will get?
-- 
Best regards,
Edward Clay
Systems Administrator
UK2 Group - US Operations
Phone: 1-800-222-2165
FAX: 435-755-3449
E-mail: edward.c...@uk2group.com

Believe in Better Hosting
http://www.westhost.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] missing hvc0 device on hosted engine

2017-02-06 Thread Berger, Sandy
I've been running oVirt 4.0.x for a while now and upgraded the engine and hosts 
to 4.1. Sometimes, on both 4.0 and 4.1, trying to run the "hosted-engine 
-console" command gives the following results:

The engine VM is running on this host
Connected to domain HostedEngine
Escape character is ^]
error: internal error: cannot find character device 

Once this starts occurring, it never works again.

When this happens I note that the hvc0 device does not exist in /dev and 
therefore there is no getty process running for that device. I notice that the 
"Enable VirtIO serial console" box is not checked on the hosted engine VM but 
when I check it and click OK it's unchecked again when I open up the edit 
window again.

How do I get console control back from my oVirt hosts?

Thank you,

Sandy Berger

Follow Us: Facebook | 
Twitter | LinkedIn | 
YouTube
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] node-ng update failed from ovirt-node-ng-4.1.0-0 to ovirt-node-ng-image-4.1.0-1, and NM + iscsi boo issue

2017-02-06 Thread Sandro Bonazzola
Adding Douglas and Ryan

Il 06/Feb/2017 13:32, "Sergey Kulikov"  ha scritto:

>
> 1) I've updated from 4.0.6 to 4.1.0 (on Feb 01 node-ng was at version
> 4.1.0-0)
> After some time engine alerted, that this node have updates to
> ovirt-node-ng-image-4.1.0-1,
> but update from engine timed out, there were hanging processes in ps on
> this node:
>
> root 36309  0.0  0.0 113120  1564 ?Ss   19:04   0:00 bash -c
> umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t
> ovirt-XX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm
> -fr \"${MYTMP}\" > /dev/null 2>&1" 0; tar --warning=no-timestamp -C
> "${MYTMP}" -x &&  "${MYTMP}"/ovirt-host-mgmt DIALOG/dialect=str:machine
> DIALOG/customization=bool:True
> root 36339  0.2  0.0 496700 94208 ?S19:04   0:21
> /bin/python /tmp/ovirt-GCmVusccfe/pythonlib/otopi/__main__.py
> "BASE/pluginPath=str:/tmp/ovirt-GCmVusccfe/otopi-plugins"
> APPEND:BASE/pluginGroups=str:ovirt-host-common:ovirt-host-mgmt
> DIALOG/dialect=str:machine DIALOG/customization=bool:True
> root 37498  0.0  0.0 113124  1452 ?S19:09   0:00 /bin/sh
> /var/tmp/rpm-tmp.4UqJ4e 1
> root 37560  0.0  0.0  0 0 ?S<   21:42   0:00
> [kworker/21:2H]
> root 37626  0.0  0.0 174516  5996 ?S19:09   0:00 rpm -Uvh
> --quiet --justdb /usr/share/imgbased/ovirt-node-ng-image-update-4.1.0-1.
> el7.centos.noarch.rpm
>
> they were hanging forever, I ended up with rebooting the node, no errors
> in log, it was just hanging at:
>
> 2017-02-03 19:09:16 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   ***CONFIRM GPG_KEY Confirm use of
> GPG Key userid=oVirt  hexkeyid=FE590CB7
> 2017-02-03 19:09:16 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   ###
> 2017-02-03 19:09:16 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   ### Please confirm 'GPG_KEY'
> Confirm use of GPG Key userid=oVirt  hexkeyid=FE590CB7
> 2017-02-03 19:09:16 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:SEND   ### Response is CONFIRM
> GPG_KEY=yes|no or ABORT GPG_KEY
> 2017-02-03 19:09:16 DEBUG otopi.plugins.otopi.dialog.machine
> dialog.__logString:204 DIALOG:RECEIVECONFIRM GPG_KEY=yes
> 2017-02-03 19:09:16 INFO otopi.plugins.otopi.packagers.yumpackager
> yumpackager.info:80 Yum Status: Running Test Transaction
> Running Transaction Check
> 2017-02-03 19:09:16 INFO otopi.plugins.otopi.packagers.yumpackager
> yumpackager.info:80 Yum Status: Running Transaction
> 2017-02-03 19:09:16 INFO otopi.plugins.otopi.packagers.yumpackager
> yumpackager.info:80 Yum install: 1/2: ovirt-node-ng-image-4.1.0-1.
> el7.centos.noarch
> 2017-02-03 19:09:20 DEBUG otopi.plugins.otopi.packagers.yumpackager
> yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-4.1.0-1.
> el7.centos.noarch
> 2017-02-03 19:09:20 INFO otopi.plugins.otopi.packagers.yumpackager
> yumpackager.info:80 Yum install: 2/2: ovirt-node-ng-image-update-4.
> 1.0-1.el7.centos.noarch
>
> now my node have this layout:
> # imgbase layout
> ovirt-node-ng-4.1.0-0.20170201.0
>  +- ovirt-node-ng-4.1.0-0.20170201.0+1
> (so update failed)
> but 4.1.0-1 rpms are marked as "installed" and yum can't find any updates,
> can I rollback to base layout without installed  4.1.0-1 rms ?
> imgbase rollback needs at least 2 layers over base.
>
> Or maybe the only way is to reinstall this node?
>
> 2) And another question, how can I disable NetworkManger permanently, or
> exclude some interfaces permanently?
> I've tried to disable NetworkManger by systemctl, but after update from
> 4.0 to 4.1 it was re-enabled(so it's not persistent between updates).
> I've an issue with iscsi root and enabled NetworkManger, because NM tries
> to bring down\up my iscsi interfaces on boot, and sometimes FS remounting RO
> because of IO errors, I can't put NM_CONTROLLED=no in ifcfg, because ifcfg
> is generated by dracut at every boot.
>
>
> -
>
> ___
> 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] How to add to VM some 10Gbit Interfaces?

2017-02-06 Thread Yaniv Kaul
On Feb 6, 2017 8:16 PM, "Maton, Brett"  wrote:

Hi Arman,

  I've got 10Gb (intel) nics in my servers and they are detected by ovirt.
  In the network interfaces panel I see the speed listed as '1'...


Perhaps Arman refers to the vNics. Since they are virtual, we could have
selected any speed for virtio. 1000 was as good as any other value, but
under the right conditions you can certainly get higher than that.
Y.


Does you OS detect the nic speed properly ?

Regards,
Brett

On 6 February 2017 at 18:05, Arman Khalatyan  wrote:

> Hi,
> Are there way to add some 10Gbit Interfaces in ovirt 4.1?
>
> thanks,
> Arman.
>
>
> ___
> 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] planned mailman restart

2017-02-06 Thread Evgheni Dereveanchin
Reboot complete.
If you are reading this, it means that all
went smooth and lists are operational again.

Sorry for the inconvenience if any.

Regards, 
Evgheni Dereveanchin 

- Original Message -
From: "Evgheni Dereveanchin" 
To: "infra" 
Cc: users@ovirt.org, "devel" 
Sent: Monday, 6 February, 2017 7:14:28 PM
Subject: planned mailman restart

Hi everyone,

In a couple of minutes I will reboot the server 
hosting all of our mailing lists (including this one) 
to install software updates. It should come up quickly,
but if you have any problems sending to oVirt lists
please try again after a few minutes.

I will announce you as soon as the reboot is complete.

Regards, 
Evgheni Dereveanchin 
___
Infra mailing list
in...@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] How to add to VM some 10Gbit Interfaces?

2017-02-06 Thread Maton, Brett
Hi Arman,

  I've got 10Gb (intel) nics in my servers and they are detected by ovirt.
  In the network interfaces panel I see the speed listed as '1'...

Does you OS detect the nic speed properly ?

Regards,
Brett

On 6 February 2017 at 18:05, Arman Khalatyan  wrote:

> Hi,
> Are there way to add some 10Gbit Interfaces in ovirt 4.1?
>
> thanks,
> Arman.
>
>
> ___
> 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] planned mailman restart

2017-02-06 Thread Evgheni Dereveanchin
Hi everyone,

In a couple of minutes I will reboot the server 
hosting all of our mailing lists (including this one) 
to install software updates. It should come up quickly,
but if you have any problems sending to oVirt lists
please try again after a few minutes.

I will announce you as soon as the reboot is complete.

Regards, 
Evgheni Dereveanchin 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] How to add to VM some 10Gbit Interfaces?

2017-02-06 Thread Arman Khalatyan
Hi,
Are there way to add some 10Gbit Interfaces in ovirt 4.1?

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


Re: [ovirt-users] Ovirt 4.0.6 guests 'Not Responding'

2017-02-06 Thread Mark Greenall
Ok, thanks Pavel. I’ll file a bug report with the logs and report back once 
done.

From: Pavel Gashev [mailto:p...@acronis.com]
Sent: 06 February 2017 17:11
To: Mark Greenall ; users@ovirt.org
Subject: Re: [ovirt-users] Ovirt 4.0.6 guests 'Not Responding'

Mark,

In your case all 30 workers were busy by vdsm.virt.sampling.HostMonitor 
discarded by timeout, and there were 3000 tasks in the queue.
I encountered the problem. In my case ISO domain was not responding.

The issue is that vdsm executor doesn’t remove discarded workers. This is a bug.



From: Mark Greenall 
>
Date: Monday 6 February 2017 at 18:20
To: Pavel Gashev >, 
"users@ovirt.org" 
>
Subject: RE: [ovirt-users] Ovirt 4.0.6 guests 'Not Responding'

Hi Pavel,

Thanks for responding. I bounced the VDSMD service, the guests recovered and 
the monitor and queue full messages also cleared. However, we did keep getting 
intermittent “Guest x Not Responding “ messages being communicated by the 
Hosted Engine, in most cases the guests would actually almost immediately 
recover though. The odd occasion would result in guests staying “Not 
Responding” and me bouncing the VDSMD service again. The Host had a memory load 
of around 85% (out of 768GB) and a CPU load of around 65% (48 cores). I have 
since added another host to that cluster and spread the guests between the two 
hosts. This seems to have totally cleared the messages (at least for the last 5 
days anyway).

I suspect the problem is load related. At what capacity would Ovirt regard a 
host as being ‘full’?

Thanks,
Mark

From: Pavel Gashev [mailto:p...@acronis.com]
Sent: 31 January 2017 15:19
To: Mark Greenall 
>; 
users@ovirt.org
Subject: Re: [ovirt-users] Ovirt 4.0.6 guests 'Not Responding'

Mark,

Could you please file a bug report?

Restart of vdsmd service would help to resolve the “executor queue full” state.


From: > on behalf of 
Mark Greenall >
Date: Monday 30 January 2017 at 15:26
To: "users@ovirt.org" 
>
Subject: [ovirt-users] Ovirt 4.0.6 guests 'Not Responding'

Hi,

Host server: Dell PowerEdge R815 (40 cores and 768GB memory)
Stoage: Dell Equallogic (Firmware V8.1.4)
OS: Centos 7.3 (although the same thing happens on 7.2)
Ovirt: 4.0.6.3-1

We have several Ovirt clusters. Two of the hosts (in separate clusters) are 
showing as up in Hosted Engine but the guests running on them are showing as 
Not Responding. I can connect to the guests via ssh, etc but can’t interact 
with them from the Ovirt GUI. It was fine on Saturday (28th Jan) morning but 
looks like something happened Sunday morning around 07:14 as we suddenly see 
the following in engine.log on one host:

2017-01-29 07:14:26,952 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
(DefaultQuartzScheduler1) [53ca8dc5] VM 
'd0aa990f-e6aa-4e79-93ce-011fe1372fb0'(lnd-ion-lindev-01) moved from 'Up' --> 
'NotResponding'
2017-01-29 07:14:27,069 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [53ca8dc5] Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: VM lnd-ion-lindev-01 is not responding.
2017-01-29 07:14:27,070 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
(DefaultQuartzScheduler1) [53ca8dc5] VM 
'788bfc0e-1712-469e-9a0a-395b8bb3f369'(lnd-ion-windev-02) moved from 'Up' --> 
'NotResponding'
2017-01-29 07:14:27,088 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [53ca8dc5] Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: VM lnd-ion-windev-02 is not responding.
2017-01-29 07:14:27,089 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
(DefaultQuartzScheduler1) [53ca8dc5] VM 
'd7eaa4ec-d65e-45c0-bc4f-505100658121'(lnd-ion-windev-04) moved from 'Up' --> 
'NotResponding'
2017-01-29 07:14:27,103 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [53ca8dc5] Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: VM lnd-ion-windev-04 is not responding.
2017-01-29 07:14:27,104 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
(DefaultQuartzScheduler1) [53ca8dc5] VM 
'5af875ad-70f9-4f49-9640-ee2b9927348b'(lnd-anv9-sup1) moved from 'Up' --> 
'NotResponding'
2017-01-29 07:14:27,121 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [53ca8dc5] Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: VM lnd-anv9-sup1 is not responding.
2017-01-29 

Re: [ovirt-users] Ovirt 4.0.6 guests 'Not Responding'

2017-02-06 Thread Pavel Gashev
Mark,

In your case all 30 workers were busy by vdsm.virt.sampling.HostMonitor 
discarded by timeout, and there were 3000 tasks in the queue.
I encountered the problem. In my case ISO domain was not responding.

The issue is that vdsm executor doesn’t remove discarded workers. This is a bug.



From: Mark Greenall 
Date: Monday 6 February 2017 at 18:20
To: Pavel Gashev , "users@ovirt.org" 
Subject: RE: [ovirt-users] Ovirt 4.0.6 guests 'Not Responding'

Hi Pavel,

Thanks for responding. I bounced the VDSMD service, the guests recovered and 
the monitor and queue full messages also cleared. However, we did keep getting 
intermittent “Guest x Not Responding “ messages being communicated by the 
Hosted Engine, in most cases the guests would actually almost immediately 
recover though. The odd occasion would result in guests staying “Not 
Responding” and me bouncing the VDSMD service again. The Host had a memory load 
of around 85% (out of 768GB) and a CPU load of around 65% (48 cores). I have 
since added another host to that cluster and spread the guests between the two 
hosts. This seems to have totally cleared the messages (at least for the last 5 
days anyway).

I suspect the problem is load related. At what capacity would Ovirt regard a 
host as being ‘full’?

Thanks,
Mark

From: Pavel Gashev [mailto:p...@acronis.com]
Sent: 31 January 2017 15:19
To: Mark Greenall ; users@ovirt.org
Subject: Re: [ovirt-users] Ovirt 4.0.6 guests 'Not Responding'

Mark,

Could you please file a bug report?

Restart of vdsmd service would help to resolve the “executor queue full” state.


From: > on behalf of 
Mark Greenall >
Date: Monday 30 January 2017 at 15:26
To: "users@ovirt.org" 
>
Subject: [ovirt-users] Ovirt 4.0.6 guests 'Not Responding'

Hi,

Host server: Dell PowerEdge R815 (40 cores and 768GB memory)
Stoage: Dell Equallogic (Firmware V8.1.4)
OS: Centos 7.3 (although the same thing happens on 7.2)
Ovirt: 4.0.6.3-1

We have several Ovirt clusters. Two of the hosts (in separate clusters) are 
showing as up in Hosted Engine but the guests running on them are showing as 
Not Responding. I can connect to the guests via ssh, etc but can’t interact 
with them from the Ovirt GUI. It was fine on Saturday (28th Jan) morning but 
looks like something happened Sunday morning around 07:14 as we suddenly see 
the following in engine.log on one host:

2017-01-29 07:14:26,952 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
(DefaultQuartzScheduler1) [53ca8dc5] VM 
'd0aa990f-e6aa-4e79-93ce-011fe1372fb0'(lnd-ion-lindev-01) moved from 'Up' --> 
'NotResponding'
2017-01-29 07:14:27,069 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [53ca8dc5] Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: VM lnd-ion-lindev-01 is not responding.
2017-01-29 07:14:27,070 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
(DefaultQuartzScheduler1) [53ca8dc5] VM 
'788bfc0e-1712-469e-9a0a-395b8bb3f369'(lnd-ion-windev-02) moved from 'Up' --> 
'NotResponding'
2017-01-29 07:14:27,088 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [53ca8dc5] Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: VM lnd-ion-windev-02 is not responding.
2017-01-29 07:14:27,089 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
(DefaultQuartzScheduler1) [53ca8dc5] VM 
'd7eaa4ec-d65e-45c0-bc4f-505100658121'(lnd-ion-windev-04) moved from 'Up' --> 
'NotResponding'
2017-01-29 07:14:27,103 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [53ca8dc5] Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: VM lnd-ion-windev-04 is not responding.
2017-01-29 07:14:27,104 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
(DefaultQuartzScheduler1) [53ca8dc5] VM 
'5af875ad-70f9-4f49-9640-ee2b9927348b'(lnd-anv9-sup1) moved from 'Up' --> 
'NotResponding'
2017-01-29 07:14:27,121 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [53ca8dc5] Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: VM lnd-anv9-sup1 is not responding.
2017-01-29 07:14:27,121 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
(DefaultQuartzScheduler1) [53ca8dc5] VM 
'b3b7c5f3-0b5b-4d8f-9cc8-b758cc1ce3b9'(lnd-db-dev-03) moved from 'Up' --> 
'NotResponding'
2017-01-29 07:14:27,136 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [53ca8dc5] Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: VM lnd-db-dev-03 is not responding.

Re: [ovirt-users] Restoring Hosted-Engine from a stale backup

2017-02-06 Thread Martin Sivak
>> A serious issue could instead happen with HA VMs:
>> if the engine finds earlier an HA VM as running on a different host it
>> will simply update its record, the issue is if it finds earlier the VM a not
>> on the original host since it will try to restart it causing a split brain
>> and probably a VM corruption.

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

Uh? Why should this be the case? I think we need Arik to confirm this,
but the engine only does HA VM restarts during fencing. And fencing is
only activated 5 minutes after the engine start to make sure we
already have all host reports.

Martin


On Mon, Feb 6, 2017 at 5:45 PM, Doug Ingham  wrote:
> On 6 February 2017 at 13:30, Simone Tiraboschi  wrote:
>>
>>
>> What problems can I expect to have with VMs added/modified since the
>> last backup?

 Modified VMs will be reverted to the previous configuration; additional
 VMs should be seen as external VMs, then you could import.
>>>
>>>
>>> Given VDSM kept the VMs up whilst the HE's been down, how will the
>>> running VMs that were present before & after the backup be affected?
>>>
>>> Many of the VMs that were present during the last backup are now on
>>> different hosts, including the HE VM. Will that cause any issues?
>>
>>
>> For normal VMs I don't expect any issue: the engine will simply update the
>> correspondent record once it will find them on the managed hosts.
>> A serious issue could instead happen with HA VMs:
>> if the engine finds earlier an HA VM as running on a different host it
>> will simply update its record, the issue is if it finds earlier the VM a not
>> on the original host since it will try to restart it causing a split brain
>> and probably a VM corruption.
>> I opened a bug to track it:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1419649
>
>
> Ouch. *All* of our VMs are HA by default.
>
> So the simplest current solution would be to shutdown the running VMs in
> VDSM, before restoring the backup & running engine-setup?
>
> Cheers,
> --
> Doug
>
> ___
> 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] Restoring Hosted-Engine from a stale backup

2017-02-06 Thread Doug Ingham
On 6 February 2017 at 13:30, Simone Tiraboschi  wrote:

>
>
>1. What problems can I expect to have with VMs added/modified
>since the last backup?
>
> Modified VMs will be reverted to the previous configuration;
>>> additional VMs should be seen as external VMs, then you could import.
>>>
>>
>> Given VDSM kept the VMs up whilst the HE's been down, how will the
>> running VMs that were present before & after the backup be affected?
>>
>> Many of the VMs that were present during the last backup are now on
>> different hosts, including the HE VM. Will that cause any issues?
>>
>
> For normal VMs I don't expect any issue: the engine will simply update the
> correspondent record once it will find them on the managed hosts.
> A serious issue could instead happen with HA VMs:
> if the engine finds earlier an HA VM as running on a different host it
> will simply update its record, the issue is if it finds earlier the VM a
> not on the original host since it will try to restart it causing a split
> brain and probably a VM corruption.
> I opened a bug to track it:
> https://bugzilla.redhat.com/show_bug.cgi?id=1419649
>

Ouch. *All* of our VMs are HA by default.

So the simplest current solution would be to shutdown the running VMs in
VDSM, before restoring the backup & running engine-setup?

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


Re: [ovirt-users] Restoring Hosted-Engine from a stale backup

2017-02-06 Thread Simone Tiraboschi
On Mon, Feb 6, 2017 at 1:52 PM, Doug Ingham  wrote:

> Hi All, Simone,
>
> On 24 January 2017 at 10:11, Simone Tiraboschi 
> wrote:
>
>>
>>
>> On Tue, Jan 24, 2017 at 1:49 PM, Doug Ingham  wrote:
>>
>>> Hey guys,
>>>  Just giving this a bump in the hope that someone might be able to
>>> advise...
>>>
>>> Hi all,
  One of our engines has had a DB failure* & it seems there was an
 unnoticed problem in its backup routine, meaning the last backup I've got
 is a couple of weeks old.
 Luckily, VDSM has kept the underlying VMs running without any
 interruptions, so my objective is to get the HE back online & get the hosts
 & VMs back under its control with minimal downtime.

 So, my questions are the following...

1. What problems can I expect to have with VMs added/modified since
the last backup?

 Modified VMs will be reverted to the previous configuration; additional
>> VMs should be seen as external VMs, then you could import.
>>
>
> Given VDSM kept the VMs up whilst the HE's been down, how will the running
> VMs that were present before & after the backup be affected?
>
> Many of the VMs that were present during the last backup are now on
> different hosts, including the HE VM. Will that cause any issues?
>

For normal VMs I don't expect any issue: the engine will simply update the
correspondent record once it will find them on the managed hosts.
A serious issue could instead happen with HA VMs:
if the engine finds earlier an HA VM as running on a different host it will
simply update its record, the issue is if it finds earlier the VM a not on
the original host since it will try to restart it causing a split brain and
probably a VM corruption.
I opened a bug to track it:
https://bugzilla.redhat.com/show_bug.cgi?id=1419649



>
>
>>
>>
>>>
1. As it's only the DB that's been affected, can I skip redeploying
the Engine & jump straight to restoring the DB & rerunning engine-setup?


>> Yes, if the engine VM is fine, you could just import the previous backup
>> and run engine-setup again.
>> Please set the global maintenance mode for hosted-engine since
>> engine-backup and engine-setup are going to bring down the engine.
>>
>
> As per above, do I still only need to import the previous backup even if
> the all of the VMs (including the HE VM) are now on different hosts to when
> the backup was made?
>

Please take care of the HA VMs.


>
>
> And as for the future, is it going to be necessary to always keep an
> unused host in the cluster to allow for emergency restores? I'm a bit
> concerned that if we ever utilised all of our hosts for running VMs, then
> we'd be completely stuck if the HE ever imploded again.
>

Honestly I don't see any special issue there.


>
> Cheers,
> --
> Doug
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Ovirt 4.0.6 guests 'Not Responding'

2017-02-06 Thread Mark Greenall
Hi Pavel,

Thanks for responding. I bounced the VDSMD service, the guests recovered and 
the monitor and queue full messages also cleared. However, we did keep getting 
intermittent “Guest x Not Responding “ messages being communicated by the 
Hosted Engine, in most cases the guests would actually almost immediately 
recover though. The odd occasion would result in guests staying “Not 
Responding” and me bouncing the VDSMD service again. The Host had a memory load 
of around 85% (out of 768GB) and a CPU load of around 65% (48 cores). I have 
since added another host to that cluster and spread the guests between the two 
hosts. This seems to have totally cleared the messages (at least for the last 5 
days anyway).

I suspect the problem is load related. At what capacity would Ovirt regard a 
host as being ‘full’?

Thanks,
Mark

From: Pavel Gashev [mailto:p...@acronis.com]
Sent: 31 January 2017 15:19
To: Mark Greenall ; users@ovirt.org
Subject: Re: [ovirt-users] Ovirt 4.0.6 guests 'Not Responding'

Mark,

Could you please file a bug report?

Restart of vdsmd service would help to resolve the “executor queue full” state.


From: > on behalf of 
Mark Greenall >
Date: Monday 30 January 2017 at 15:26
To: "users@ovirt.org" 
>
Subject: [ovirt-users] Ovirt 4.0.6 guests 'Not Responding'

Hi,

Host server: Dell PowerEdge R815 (40 cores and 768GB memory)
Stoage: Dell Equallogic (Firmware V8.1.4)
OS: Centos 7.3 (although the same thing happens on 7.2)
Ovirt: 4.0.6.3-1

We have several Ovirt clusters. Two of the hosts (in separate clusters) are 
showing as up in Hosted Engine but the guests running on them are showing as 
Not Responding. I can connect to the guests via ssh, etc but can’t interact 
with them from the Ovirt GUI. It was fine on Saturday (28th Jan) morning but 
looks like something happened Sunday morning around 07:14 as we suddenly see 
the following in engine.log on one host:

2017-01-29 07:14:26,952 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
(DefaultQuartzScheduler1) [53ca8dc5] VM 
'd0aa990f-e6aa-4e79-93ce-011fe1372fb0'(lnd-ion-lindev-01) moved from 'Up' --> 
'NotResponding'
2017-01-29 07:14:27,069 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [53ca8dc5] Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: VM lnd-ion-lindev-01 is not responding.
2017-01-29 07:14:27,070 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
(DefaultQuartzScheduler1) [53ca8dc5] VM 
'788bfc0e-1712-469e-9a0a-395b8bb3f369'(lnd-ion-windev-02) moved from 'Up' --> 
'NotResponding'
2017-01-29 07:14:27,088 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [53ca8dc5] Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: VM lnd-ion-windev-02 is not responding.
2017-01-29 07:14:27,089 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
(DefaultQuartzScheduler1) [53ca8dc5] VM 
'd7eaa4ec-d65e-45c0-bc4f-505100658121'(lnd-ion-windev-04) moved from 'Up' --> 
'NotResponding'
2017-01-29 07:14:27,103 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [53ca8dc5] Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: VM lnd-ion-windev-04 is not responding.
2017-01-29 07:14:27,104 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
(DefaultQuartzScheduler1) [53ca8dc5] VM 
'5af875ad-70f9-4f49-9640-ee2b9927348b'(lnd-anv9-sup1) moved from 'Up' --> 
'NotResponding'
2017-01-29 07:14:27,121 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [53ca8dc5] Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: VM lnd-anv9-sup1 is not responding.
2017-01-29 07:14:27,121 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
(DefaultQuartzScheduler1) [53ca8dc5] VM 
'b3b7c5f3-0b5b-4d8f-9cc8-b758cc1ce3b9'(lnd-db-dev-03) moved from 'Up' --> 
'NotResponding'
2017-01-29 07:14:27,136 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [53ca8dc5] Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: VM lnd-db-dev-03 is not responding.
2017-01-29 07:14:27,137 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
(DefaultQuartzScheduler1) [53ca8dc5] VM 
'6c0a6e17-47c3-4464-939b-e83984dbeaa6'(lnd-db-dev-04) moved from 'Up' --> 
'NotResponding'
2017-01-29 07:14:27,167 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler1) [53ca8dc5] Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: VM lnd-db-dev-04 is not responding.
2017-01-29 07:14:27,168 INFO  

Re: [ovirt-users] [ANN] oVirt 4.1.0 Second Beta Release is now available for testing

2017-02-06 Thread Nathanaël Blanchet

Hi all,

We can close this issue, it was because of collectd version and 
collectd* dependencies.


Those packets were provided by two sources : epel-release in 4.1.1 
version (was manually installed) and by the regular ovirt repo 
(centos-opstools-testing) in 4.0.2 version.


Resinstalling vdsm after erasing epel-release and 4.1.1 collectd* was 
enough to solve the issue.


It could be a good idea to integrate a function so as to prevent vdsm 
installation to happen when conflicting pre-existing repos (such as 
epel) are already present...



Le 02/02/2017 à 15:28, Nir Soffer a écrit :

On Thu, Feb 2, 2017 at 3:15 PM, Yedidyah Bar David  wrote:

On Mon, Jan 30, 2017 at 3:09 PM, Yaniv Dary  wrote:

Adding one more person to look.

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
 8272306
Email: yd...@redhat.com
IRC : ydary


On Mon, Jan 30, 2017 at 1:35 PM, Sandro Bonazzola 
wrote:



On Mon, Jan 30, 2017 at 12:24 PM, Nathanaël Blanchet 
wrote:



Le 28/12/2016 à 15:25, Nathanaël Blanchet a écrit :



Le 28/12/2016 à 15:09, Yaniv Bronheim a écrit :



On Wed, Dec 28, 2016 at 3:43 PM, Nathanaël Blanchet 
wrote:

Hello,

On my 4.1 Second Beta test platform, I meet this issue on the three
hosts : VDSM gaua3 command failed: :'NoneType' object has no attribute
'statistics'">

Still the same error with RC2 and GA is on 1st of february...


Adding some people, looks related to metrics but I may be wrong.

Doesn't seem so to me.







Hi Nathanael, Thank you for the report

Hi Yaniv


please send also the following logs for deeper investigation
/var/log/vdsm.log
/var/log/supervdsm.log
/var/log/messages or joursnalctl -xn output

Did you attach the last one? Could not find it.

In vdsm.log I see:

2016-12-28 14:22:32,068 ERROR (periodic/1) [virt.periodic.Operation]
 operation failed
(periodic:192)
Traceback (most recent call last):
   File "/usr/lib/python2.7/site-packages/vdsm/virt/periodic.py", line
190, in __call__
 self._func()
   File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line
563, in __call__
 stats = hostapi.get_stats(self._cif, self._samples.stats())
   File "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 72,
in get_stats
 ret.update(cif.mom.getKsmStats())
   File "/usr/lib/python2.7/site-packages/vdsm/momIF.py", line 71, in 
getKsmStats
 stats = self._mom.getStatistics()['host']
   File "/usr/lib64/python2.7/xmlrpclib.py", line 1233, in __call__
 return self.__send(self.__name, args)
   File "/usr/lib64/python2.7/xmlrpclib.py", line 1587, in __request
 verbose=self.__verbose
   File "/usr/lib64/python2.7/xmlrpclib.py", line 1273, in request
 return self.single_request(host, handler, request_body, verbose)
   File "/usr/lib64/python2.7/xmlrpclib.py", line 1306, in single_request
 return self.parse_response(response)
   File "/usr/lib64/python2.7/xmlrpclib.py", line 1482, in parse_response
 return u.close()
   File "/usr/lib64/python2.7/xmlrpclib.py", line 794, in close
 raise Fault(**self._stack[0])
Fault: :'NoneType' object
has no attribute 'statistics'">

This traceback is a bug in the code connecting to mom; if mom is not
available we should see a clear error about this, not a traceback about
accesing the 'statistics' attribute on a None object.

Please file a bug about this.


2016-12-28 14:22:33,277 INFO  (jsonrpc/2) [dispatcher] Run and
protect: repoStats(options=None) (logUtils:49)
2016-12-28 14:22:33,277 INFO  (jsonrpc/2) [dispatcher] Run and
protect: repoStats, Return response:
{u'38eff02a-1061-4f33-b870-beaea860f59b': {'code': 0, 'actual': True,
'version': 0, 'acquired': True, 'delay': '0.000274322', 'lastCheck':
'0.2', 'valid': True}, u'5dd036bb-10dc-4f1d-b80b-3549ceabdc24':
{'code': 0, 'actual': True, 'version': 4, 'acquired': True, 'delay':
'0.000385412', 'lastCheck': '5.5', 'valid': True}} (logUtils:52)
2016-12-28 14:22:33,278 WARN  (jsonrpc/2) [MOM] MOM not available. (momIF:116)
2016-12-28 14:22:33,279 WARN  (jsonrpc/2) [MOM] MOM not available, KSM
stats will be missing. (momIF:79)

It seems to me like vdsm tries to connect to mom and fails.

Please attach the output of:

systemctl status mom-vdsm


If this still happens, I suggest to:
1. Move host to maintenance
2. Restart both vdsm daemons and mom
3. If it still happens, check/share all logs to find out why it fails.

Best,


Also, please specify a bit the platform you are running on and when this
issue occurs

3 el7 hosts, 1 gluster + virt cluster, FC domain storage with the latest
4.1 beta, independant el7 engine


Greetings,
Yaniv Bronhaim.




Le 21/12/2016 à 16:12, Sandro Bonazzola a écrit :

The oVirt Project is pleased to announce the availability of the Second
Beta Release of oVirt 4.1.0 for testing, as of December 21st, 2016

This is pre-release software. Please 

[ovirt-users] GUI node detail long delay

2017-02-06 Thread p...@email.cz

Hello everybody,

We are using oVirt Engine Version: 4.0.6.3-1.el7.centos on centos 7.3 
with gluster replica 3 arbiter  = (1+1)+1


I'm confused with GUI delaying -  if node details are wanted ( cluster 
-> nodes -> node detail = click on node raw ) then request generate over 
10 min delay to display details. This unexpected mistake  didn't occure 
initially, but later - not specified when .


The followed partial list of "engine.log" shows requests to "arbiter 
node" ( 16.0.0.159)  connectivity.
This requested 3rd node of gluster(arbiter)  is NOT included in oVirt 
environment and will NOT.

Maybe this is that problem, but I'm not shure, especially how to fix this.

2017-02-06 13:20:03,924 INFO 
[org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] 
(DefaultQuartzScheduler3) [49cebf0] START, 
GlusterServersListVDSCommand(HostName = 1kvm2, 
VdsIdVDSCommandParametersBase:{runAsync='true', 
hostId='258decac-46f4-4c15-b855-ad97b570ee60'}), log id: 6873151
2017-02-06 13:20:04,796 INFO 
[org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] 
(DefaultQuartzScheduler3) [49cebf0] FINISH, 
GlusterServersListVDSCommand, return: [172.16.5.162/24:CONNECTED, 
172.16.5.161:CONNECTED, 16.0.0.159:CONNECTED], log id: 6873151
2017-02-06 13:20:04,814 INFO 
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] 
(DefaultQuartzScheduler3) [49cebf0] START, 
GlusterVolumesListVDSCommand(HostName = 1kvm2, 
GlusterVolumesListVDSParameters:{runAsync='true', 
hostId='258decac-46f4-4c15-b855-ad97b570ee60'}), log id: 381ae630
2017-02-06 13:20:05,970 WARN 
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturnForXmlRpc] 
(DefaultQuartzScheduler3) [49cebf0] Could not add brick 
'16.0.0.159:/GLUSTER/1KVM12-sda2/GFS' to volume 
'19c27787-f1c9-4dee-8415-c6d1c81e3aa2' - server uuid 
'f7670ea9-2204-4310-96a6-243c2c6a00de' not found in cluster 
'587fa2d8-017d-03b3-0003-030d'
2017-02-06 13:20:05,987 WARN 
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturnForXmlRpc] 
(DefaultQuartzScheduler3) [49cebf0] Could not add brick 
'16.0.0.159:/GLUSTER/1KVM12-sda1/GFS' to volume 
'96adac2a-0dc4-4bd8-ad79-23dd3448f73b' - server uuid 
'f7670ea9-2204-4310-96a6-243c2c6a00de' not found in cluster 
'587fa2d8-017d-03b3-0003-030d'
2017-02-06 13:20:05,987 INFO 
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] 
(DefaultQuartzScheduler3) [49cebf0] FINISH, 
GlusterVolumesListVDSCommand, return: 
{19c27787-f1c9-4dee-8415-c6d1c81e3aa2=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@b9f51962, 
96adac2a-0dc4-4bd8-ad79-23dd3448f73b=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@86597dda}, 
log id: 381ae630


repeatelly occured several times per minute, so huge filling logs


OS Version:RHEL - 7 - 3.1611.el7.centos
OS Description:CentOS Linux 7 (Core)
Kernel Version:3.10.0 - 514.6.1.el7.x86_64
KVM Version:2.6.0 - 28.el7_3.3.1
LIBVIRT Version:libvirt-2.0.0-10.el7_3.4
VDSM Version:vdsm-4.18.21-1.el7.centos
SPICE Version:0.12.4 - 19.el7
GlusterFS Version:glusterfs-3.8.8-1.el7
CEPH Version:librbd1-0.94.5-1.el7


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


[ovirt-users] node-ng update failed from ovirt-node-ng-4.1.0-0 to ovirt-node-ng-image-4.1.0-1, and NM + iscsi boo issue

2017-02-06 Thread Sergey Kulikov

1) I've updated from 4.0.6 to 4.1.0 (on Feb 01 node-ng was at version 4.1.0-0)
After some time engine alerted, that this node have updates to 
ovirt-node-ng-image-4.1.0-1,
but update from engine timed out, there were hanging processes in ps on this 
node:

root 36309  0.0  0.0 113120  1564 ?Ss   19:04   0:00 bash -c umask 
0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t ovirt-XX)"; trap 
"chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm -fr \"${MYTMP}\" > /dev/null 
2>&1" 0; tar --warning=no-timestamp -C "${MYTMP}" -x &&  
"${MYTMP}"/ovirt-host-mgmt DIALOG/dialect=str:machine 
DIALOG/customization=bool:True
root 36339  0.2  0.0 496700 94208 ?S19:04   0:21 /bin/python 
/tmp/ovirt-GCmVusccfe/pythonlib/otopi/__main__.py 
"BASE/pluginPath=str:/tmp/ovirt-GCmVusccfe/otopi-plugins"  
APPEND:BASE/pluginGroups=str:ovirt-host-common:ovirt-host-mgmt 
DIALOG/dialect=str:machine DIALOG/customization=bool:True
root 37498  0.0  0.0 113124  1452 ?S19:09   0:00 /bin/sh 
/var/tmp/rpm-tmp.4UqJ4e 1
root 37560  0.0  0.0  0 0 ?S<   21:42   0:00 [kworker/21:2H]
root 37626  0.0  0.0 174516  5996 ?S19:09   0:00 rpm -Uvh 
--quiet --justdb 
/usr/share/imgbased/ovirt-node-ng-image-update-4.1.0-1.el7.centos.noarch.rpm

they were hanging forever, I ended up with rebooting the node, no errors in 
log, it was just hanging at:

2017-02-03 19:09:16 DEBUG otopi.plugins.otopi.dialog.machine 
dialog.__logString:204 DIALOG:SEND   ***CONFIRM GPG_KEY Confirm use of GPG 
Key userid=oVirt  hexkeyid=FE590CB7
2017-02-03 19:09:16 DEBUG otopi.plugins.otopi.dialog.machine 
dialog.__logString:204 DIALOG:SEND   ###
2017-02-03 19:09:16 DEBUG otopi.plugins.otopi.dialog.machine 
dialog.__logString:204 DIALOG:SEND   ### Please confirm 'GPG_KEY' Confirm 
use of GPG Key userid=oVirt  hexkeyid=FE590CB7
2017-02-03 19:09:16 DEBUG otopi.plugins.otopi.dialog.machine 
dialog.__logString:204 DIALOG:SEND   ### Response is CONFIRM GPG_KEY=yes|no 
or ABORT GPG_KEY
2017-02-03 19:09:16 DEBUG otopi.plugins.otopi.dialog.machine 
dialog.__logString:204 DIALOG:RECEIVECONFIRM GPG_KEY=yes
2017-02-03 19:09:16 INFO otopi.plugins.otopi.packagers.yumpackager 
yumpackager.info:80 Yum Status: Running Test Transaction
Running Transaction Check
2017-02-03 19:09:16 INFO otopi.plugins.otopi.packagers.yumpackager 
yumpackager.info:80 Yum Status: Running Transaction
2017-02-03 19:09:16 INFO otopi.plugins.otopi.packagers.yumpackager 
yumpackager.info:80 Yum install: 1/2: 
ovirt-node-ng-image-4.1.0-1.el7.centos.noarch
2017-02-03 19:09:20 DEBUG otopi.plugins.otopi.packagers.yumpackager 
yumpackager.verbose:76 Yum Done: ovirt-node-ng-image-4.1.0-1.el7.centos.noarch
2017-02-03 19:09:20 INFO otopi.plugins.otopi.packagers.yumpackager 
yumpackager.info:80 Yum install: 2/2: 
ovirt-node-ng-image-update-4.1.0-1.el7.centos.noarch

now my node have this layout:
# imgbase layout
ovirt-node-ng-4.1.0-0.20170201.0
 +- ovirt-node-ng-4.1.0-0.20170201.0+1
(so update failed)
but 4.1.0-1 rpms are marked as "installed" and yum can't find any updates, can 
I rollback to base layout without installed  4.1.0-1 rms ?
imgbase rollback needs at least 2 layers over base.

Or maybe the only way is to reinstall this node?

2) And another question, how can I disable NetworkManger permanently, or 
exclude some interfaces permanently?
I've tried to disable NetworkManger by systemctl, but after update from 4.0 to 
4.1 it was re-enabled(so it's not persistent between updates).
I've an issue with iscsi root and enabled NetworkManger, because NM tries to 
bring down\up my iscsi interfaces on boot, and sometimes FS remounting RO
because of IO errors, I can't put NM_CONTROLLED=no in ifcfg, because ifcfg is 
generated by dracut at every boot.


-

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


Re: [ovirt-users] [Call for feedback] did you install/update to 4.1.0?

2017-02-06 Thread Simone Tiraboschi
On Mon, Feb 6, 2017 at 12:42 PM, Ralf Schenk  wrote:

> Hello,
>
> I set the host to maintenance mode and tried to undeploy engine via GUI.
> The action in GUI doesn't show an error but afterwards it still shows only
> "Undeploy" on hosted-engine tab od the host.
>
> Even removing the host from the cluster doesn't work because the GUI says
> "The hosts maekred with * still have hosted engine deployed on them. Hosted
> engine should be undeployed before they are removed"
>
Yes, sorry: it's now a two step process, you have first to undeploy
hosted-engine from the host and only then you could remove the host.



> Bye
> Am 06.02.2017 um 11:44 schrieb Simone Tiraboschi:
>
>
>
> On Sat, Feb 4, 2017 at 11:52 AM, Ralf Schenk  wrote:
>
>> Hello,
>>
>> I have set up 3 hosts for engine, 2 of them are working correct. There is
>> no other host even having broker/agent installed. Is it possible that the
>> error occurs because the hosts are multihomed (Management IP, IP for
>> storage) and can communicate with different IP's ?
>>
> Having multiple logical networks for storage, management and so on is a
> good practice and it's advised so I tend to exclude any issue there.
> The point is why your microcloud27.sub.mydomain.de fails acquiring a lock
> as host 3.
> Probably the simplest fix is just setting it in maintenance mode from the
> engine, removing it and deploying it from the engine as an hosted engine
> host again.
>
>
>
>
> --
>
>
> *Ralf Schenk*
> fon +49 (0) 24 05 / 40 83 70 <+49%202405%20408370>
> fax +49 (0) 24 05 / 40 83 759 <+49%202405%204083759>
> mail *r...@databay.de* 
>
> *Databay AG*
> Jens-Otto-Krag-Straße 11
> D-52146 Würselen
> *www.databay.de* 
>
> Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202
> Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm.
> Philipp Hermanns
> Aufsichtsratsvorsitzender: Wilhelm Dohmen
> --
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] [Call for feedback] did you install/update to 4.1.0?

2017-02-06 Thread cmc
Hi Sandro,

I upgraded my 2 host setup + engine (engine is currently on separate
hardware, but I plan to make it self-hosted), and it went like
clockwork. My engine + hosts were running 4.0.5 and 7.2, so after
installing 4.1 release, I did an OS update to 7.3 first, starting with
the engine, then ran engine-setup. I opted to do a 'yum upgrade' on
the the first host, which actually updated all the ovirt packages as
well and rebooted (I'm not sure this is an approved method, but it
worked fine). After the first host was back, I upgraded the second
host from the GUI, but then I ran a yum upgrade to update all the OS
stuff, such as the kernel, libc etc, and rebooted.

Many thanks for making the upgrade process so smooth!

Cheers,

Cam

On Thu, Feb 2, 2017 at 12:19 PM, Sandro Bonazzola  wrote:
> Hi,
> did you install/update to 4.1.0? Let us know your experience!
> We end up knowing only when things doesn't work well, let us know it works
> fine for you :-)
>
> If you're not planning an update to 4.1.0 in the near future, let us know
> why.
> Maybe we can help.
>
> Thanks!
> --
> 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] [Call for feedback] did you install/update to 4.1.0?

2017-02-06 Thread Ralf Schenk
Hello,

I set the host to maintenance mode and tried to undeploy engine via GUI.
The action in GUI doesn't show an error but afterwards it still shows
only "Undeploy" on hosted-engine tab od the host.

Even removing the host from the cluster doesn't work because the GUI
says "The hosts maekred with * still have hosted engine deployed on
them. Hosted engine should be undeployed before they are removed"

Bye
Am 06.02.2017 um 11:44 schrieb Simone Tiraboschi:
>
>
> On Sat, Feb 4, 2017 at 11:52 AM, Ralf Schenk  > wrote:
>
> Hello,
>
> I have set up 3 hosts for engine, 2 of them are working correct.
> There is no other host even having broker/agent installed. Is it
> possible that the error occurs because the hosts are multihomed
> (Management IP, IP for storage) and can communicate with different
> IP's ?
>
> Having multiple logical networks for storage, management and so on is
> a good practice and it's advised so I tend to exclude any issue there.
> The point is why your microcloud27.sub.mydomain.de
>  fails acquiring a lock as host 3.
> Probably the simplest fix is just setting it in maintenance mode from
> the engine, removing it and deploying it from the engine as an hosted
> engine host again. 
>
>  

-- 


*Ralf Schenk*
fon +49 (0) 24 05 / 40 83 70
fax +49 (0) 24 05 / 40 83 759
mail *r...@databay.de* 

*Databay AG*
Jens-Otto-Krag-Straße 11
D-52146 Würselen
*www.databay.de* 

Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202
Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm.
Philipp Hermanns
Aufsichtsratsvorsitzender: Wilhelm Dohmen


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


Re: [ovirt-users] problem after rebooting the node

2017-02-06 Thread Edward Haas
The ones you mentioned before, we just need the whole files and not
snippets of them.
vdsm.log, supervdsm.log, messages.log and the ovs ones you previously
mentioned.

On Mon, Feb 6, 2017 at 1:14 PM, Shalabh Goel 
wrote:

> which all log files? Actually I am new to Ovirt, so it would be really
> helpful if  you can tell me which ones??
>
> Thanks
>
> On Mon, Feb 6, 2017 at 4:39 PM, Edward Haas  wrote:
>
>> Please package the logs (tar or zip) and send them.
>>
>> On Mon, Feb 6, 2017 at 12:05 PM, Shalabh Goel 
>> wrote:
>>
>>> Yes, I am using OVS as the switch type and I did not know that it was
>>> not supported officially.
>>>
>>> The output of ovs-vsctl show is as follows:
>>>
>>> f634d53e-4849-488b-8454-6b1fafa7c6ac
>>> ovs_version: "2.6.90"
>>>
>>> I am attaching OVS switch logs below:
>>>
>>> /var/log/openvswitch/ovsdb-server.log
>>>
>>>
>>> 2017-02-06T09:46:07.788Z|1|vlog|INFO|opened log file
>>> /var/log/openvswitch/ovsdb-server.log
>>> 2017-02-06T09:46:07.791Z|2|ovsdb_server|INFO|ovsdb-server (Open
>>> vSwitch) 2.6.90
>>> 2017-02-06T09:46:17.802Z|3|memory|INFO|2296 kB peak resident set
>>> size after 10.0 seconds
>>> 2017-02-06T09:46:17.802Z|4|memory|INFO|cells:16 json-caches:1
>>> monitors:1 sessions:1
>>>
>>> ovs-vswitchd.log
>>>
>>>
>>> 2017-02-06T09:46:07.999Z|1|vlog|INFO|opened log file
>>> /var/log/openvswitch/ovs-vswitchd.log
>>> 2017-02-06T09:46:08.036Z|2|ovs_numa|INFO|Discovered 24 CPU cores on
>>> NUMA node 0
>>> 2017-02-06T09:46:08.036Z|3|ovs_numa|INFO|Discovered 24 CPU cores on
>>> NUMA node 1
>>> 2017-02-06T09:46:08.036Z|4|ovs_numa|INFO|Discovered 2 NUMA nodes
>>> and 48 CPU cores
>>> 2017-02-06T09:46:08.037Z|5|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
>>> connecting...
>>> 2017-02-06T09:46:08.037Z|6|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
>>> connected
>>> 2017-02-06T09:46:08.039Z|7|bridge|INFO|ovs-vswitchd (Open vSwitch)
>>> 2.6.90
>>>
>>> What should I do now?
>>>
>>> The engine says that "Host host2 does not comply with the cluster
>>> Default networks, the following networks are missing on host: 'ovirtmgmt'
>>> "
>>>
>>> What other logs should I attach?
>>>
>>> Thanks
>>>
>>> Shalabh Goel
>>>
>>> On Sun, Feb 5, 2017 at 1:10 PM, Edward Haas  wrote:
>>>
 Based on what I can see, you used OVS as the switch type and it seems
 ovs (openvswitch) is not properly installed on your host.
 Make sure that you have ovs operational by issuing "ovs-vsctl show".

 You should note that OVS network support is not an official release
 feature, and you should use it on 4.1 and up versions.
 Fixes will be probably submitted to master (appearing in nightly
 builds).

 Next time please include the mailing-list in your replies and attach
 the log files, it is less spamming.

 Thanks,
 Edy.

 On Fri, Feb 3, 2017 at 5:07 AM, Shalabh Goel 
 wrote:

> log from messages
>
> Feb  3 08:27:53 ovirtnode3 ovs-vsctl: 
> ovs|1|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock:
> database connection failed (No such file or directory)
> Feb  3 08:27:53 ovirtnode3 journal: vdsm vds ERROR Executing commands
> failed: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database
> connection failed (No su
> ch file or directory)#012Traceback (most recent call last):#012  File
> "/usr/share/vdsm/API.py", line 1531, in setupNetworks#012
> supervdsm.getProxy().setup
> Networks(networks, bondings, options)#012  File
> "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in
> __call__#012return callMethod()#012  Fi
> le "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in
> #012**kwargs)#012  File "", line 2, in
> setupNetworks#012  File "/usr
> /lib64/python2.7/multiprocessing/managers.py", line 773, in
> _callmethod#012raise convert_to_error(kind,
> result)#012ConfigNetworkError: (21, 'Executing co
> mmands failed: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database
> connection failed (No such file or directory)')
>
> Log from vdsm.log
>
> Reactor thread::INFO::2017-02-03 08:32:24,638::protocoldetector
> ::72::ProtocolDetector.AcceptorImpl::(handle_accept) Accepted
> connection from ::1:53082
> Reactor thread::DEBUG::2017-02-03 08:32:24,643::protocoldetector
> ::91::ProtocolDetector.Detector::(__init__) Using required_size=11
> Reactor thread::INFO::2017-02-03 08:32:24,643::protocoldetector
> ::127::ProtocolDetector.Detector::(handle_read) Detected protocol xml
> from ::1:53082
> Reactor thread::DEBUG::2017-02-03 08:32:24,643::bindingxmlrpc::1
> 317::XmlDetector::(handle_socket) xml over http detected from ('::1',
> 53082)
> BindingXMLRPC::INFO::2017-02-03 
> 

Re: [ovirt-users] How to update ovirt nodes

2017-02-06 Thread Shalabh Goel
Now I got an error while installing the third node too. I am attaching the
log file.

2017-02-06 16:43:51,488+05 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [2a3cb164-9fe7-4487-9837-1c84c9a6a2d3] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Correlation ID:
2a3cb164-9fe7-4487-9837-1c84c9a6a2d3, Call Stack: null, Custom Event ID:
-1, Message: Installing Host NFShost-235.6. Yum Status: Check Package
Signatures.
2017-02-06 16:43:51,496+05 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [2a3cb164-9fe7-4487-9837-1c84c9a6a2d3] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Correlation ID:
2a3cb164-9fe7-4487-9837-1c84c9a6a2d3, Call Stack: null, Custom Event ID:
-1, Message: Installing Host NFShost-235.6. Yum Status: Running Test
Transaction.
2017-02-06 16:43:51,638+05 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [2a3cb164-9fe7-4487-9837-1c84c9a6a2d3] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Correlation ID:
2a3cb164-9fe7-4487-9837-1c84c9a6a2d3, Call Stack: null, Custom Event ID:
-1, Message: Installing Host NFShost-235.6. Yum Status: Running Transaction.
2017-02-06 16:43:51,746+05 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [2a3cb164-9fe7-4487-9837-1c84c9a6a2d3] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Correlation ID:
2a3cb164-9fe7-4487-9837-1c84c9a6a2d3, Call Stack: null, Custom Event ID:
-1, Message: Installing Host NFShost-235.6. Yum update: 1/4:
ovirt-node-ng-image-4.1.0-1.el7.centos.noarch.
2017-02-06 16:43:56,054+05 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [2a3cb164-9fe7-4487-9837-1c84c9a6a2d3] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Correlation ID:
2a3cb164-9fe7-4487-9837-1c84c9a6a2d3, Call Stack: null, Custom Event ID:
-1, Message: Installing Host NFShost-235.6. Yum update: 2/4:
ovirt-node-ng-image-update-4.1.0-1.el7.centos.noarch.
2017-02-06 16:47:26,376+05 ERROR
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy)
[2a3cb164-9fe7-4487-9837-1c84c9a6a2d3] Error during deploy dialog:
java.io.IOException: Unexpected connection termination
at
org.ovirt.otopi.dialog.MachineDialogParser.nextEvent(MachineDialogParser.java:376)
[otopi.jar:]
at
org.ovirt.otopi.dialog.MachineDialogParser.nextEvent(MachineDialogParser.java:393)
[otopi.jar:]
at
org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase.threadMain(VdsDeployBase.java:304)
[bll.jar:]
at
org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase.lambda$new$0(VdsDeployBase.java:383)
[bll.jar:]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]

2017-02-06 16:47:26,379+05 ERROR
[org.ovirt.engine.core.uutils.ssh.SSHDialog] (pool-5-thread-8)
[2a3cb164-9fe7-4487-9837-1c84c9a6a2d3] SSH error running command
root@10.1.235.6:'umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t
ovirt-XX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm
-fr \"${MYTMP}\" > /dev/null 2>&1" 0; tar --warning=no-timestamp -C
"${MYTMP}" -x &&  "${MYTMP}"/ovirt-host-mgmt DIALOG/dialect=str:machine
DIALOG/customization=bool:True': SSH session hard timeout host '
root@10.1.235.6'
2017-02-06 16:47:26,379+05 ERROR
[org.ovirt.engine.core.uutils.ssh.SSHDialog] (pool-5-thread-8)
[2a3cb164-9fe7-4487-9837-1c84c9a6a2d3] Exception:
javax.naming.TimeLimitExceededException: SSH session hard timeout host '
root@10.1.235.6'
at
org.ovirt.engine.core.uutils.ssh.SSHClient.executeCommand(SSHClient.java:475)
[uutils.jar:]
at
org.ovirt.engine.core.uutils.ssh.SSHDialog.executeCommand(SSHDialog.java:317)
[uutils.jar:]
at
org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase.execute(VdsDeployBase.java:563)
[bll.jar:]
at
org.ovirt.engine.core.bll.host.HostUpgradeManager.update(HostUpgradeManager.java:99)
[bll.jar:]
at
org.ovirt.engine.core.bll.hostdeploy.UpgradeHostInternalCommand.executeCommand(UpgradeHostInternalCommand.java:72)
[bll.jar:]
at
org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1251)
[bll.jar:]
at
org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1391)
[bll.jar:]
at
org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:2055)
[bll.jar:]
at
org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:164)
[utils.jar:]
at
org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:103)
[utils.jar:]
at org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1451)
[bll.jar:]
at
org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:397)
[bll.jar:]
at
org.ovirt.engine.core.bll.executor.DefaultBackendActionExecutor.execute(DefaultBackendActionExecutor.java:13)
[bll.jar:]
at org.ovirt.engine.core.bll.Backend.runAction(Backend.java:511)
[bll.jar:]
at org.ovirt.engine.core.bll.Backend.runAction(Backend.java:753)

Re: [ovirt-users] problem after rebooting the node

2017-02-06 Thread Shalabh Goel
which all log files? Actually I am new to Ovirt, so it would be really
helpful if  you can tell me which ones??

Thanks

On Mon, Feb 6, 2017 at 4:39 PM, Edward Haas  wrote:

> Please package the logs (tar or zip) and send them.
>
> On Mon, Feb 6, 2017 at 12:05 PM, Shalabh Goel 
> wrote:
>
>> Yes, I am using OVS as the switch type and I did not know that it was not
>> supported officially.
>>
>> The output of ovs-vsctl show is as follows:
>>
>> f634d53e-4849-488b-8454-6b1fafa7c6ac
>> ovs_version: "2.6.90"
>>
>> I am attaching OVS switch logs below:
>>
>> /var/log/openvswitch/ovsdb-server.log
>>
>>
>> 2017-02-06T09:46:07.788Z|1|vlog|INFO|opened log file
>> /var/log/openvswitch/ovsdb-server.log
>> 2017-02-06T09:46:07.791Z|2|ovsdb_server|INFO|ovsdb-server (Open
>> vSwitch) 2.6.90
>> 2017-02-06T09:46:17.802Z|3|memory|INFO|2296 kB peak resident set
>> size after 10.0 seconds
>> 2017-02-06T09:46:17.802Z|4|memory|INFO|cells:16 json-caches:1
>> monitors:1 sessions:1
>>
>> ovs-vswitchd.log
>>
>>
>> 2017-02-06T09:46:07.999Z|1|vlog|INFO|opened log file
>> /var/log/openvswitch/ovs-vswitchd.log
>> 2017-02-06T09:46:08.036Z|2|ovs_numa|INFO|Discovered 24 CPU cores on
>> NUMA node 0
>> 2017-02-06T09:46:08.036Z|3|ovs_numa|INFO|Discovered 24 CPU cores on
>> NUMA node 1
>> 2017-02-06T09:46:08.036Z|4|ovs_numa|INFO|Discovered 2 NUMA nodes and
>> 48 CPU cores
>> 2017-02-06T09:46:08.037Z|5|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
>> connecting...
>> 2017-02-06T09:46:08.037Z|6|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
>> connected
>> 2017-02-06T09:46:08.039Z|7|bridge|INFO|ovs-vswitchd (Open vSwitch)
>> 2.6.90
>>
>> What should I do now?
>>
>> The engine says that "Host host2 does not comply with the cluster Default
>> networks, the following networks are missing on host: 'ovirtmgmt'"
>>
>> What other logs should I attach?
>>
>> Thanks
>>
>> Shalabh Goel
>>
>> On Sun, Feb 5, 2017 at 1:10 PM, Edward Haas  wrote:
>>
>>> Based on what I can see, you used OVS as the switch type and it seems
>>> ovs (openvswitch) is not properly installed on your host.
>>> Make sure that you have ovs operational by issuing "ovs-vsctl show".
>>>
>>> You should note that OVS network support is not an official release
>>> feature, and you should use it on 4.1 and up versions.
>>> Fixes will be probably submitted to master (appearing in nightly builds).
>>>
>>> Next time please include the mailing-list in your replies and attach the
>>> log files, it is less spamming.
>>>
>>> Thanks,
>>> Edy.
>>>
>>> On Fri, Feb 3, 2017 at 5:07 AM, Shalabh Goel 
>>> wrote:
>>>
 log from messages

 Feb  3 08:27:53 ovirtnode3 ovs-vsctl: 
 ovs|1|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock:
 database connection failed (No such file or directory)
 Feb  3 08:27:53 ovirtnode3 journal: vdsm vds ERROR Executing commands
 failed: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database
 connection failed (No su
 ch file or directory)#012Traceback (most recent call last):#012  File
 "/usr/share/vdsm/API.py", line 1531, in setupNetworks#012
 supervdsm.getProxy().setup
 Networks(networks, bondings, options)#012  File
 "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in
 __call__#012return callMethod()#012  Fi
 le "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in
 #012**kwargs)#012  File "", line 2, in
 setupNetworks#012  File "/usr
 /lib64/python2.7/multiprocessing/managers.py", line 773, in
 _callmethod#012raise convert_to_error(kind,
 result)#012ConfigNetworkError: (21, 'Executing co
 mmands failed: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database
 connection failed (No such file or directory)')

 Log from vdsm.log

 Reactor thread::INFO::2017-02-03 08:32:24,638::protocoldetector
 ::72::ProtocolDetector.AcceptorImpl::(handle_accept) Accepted
 connection from ::1:53082
 Reactor thread::DEBUG::2017-02-03 08:32:24,643::protocoldetector
 ::91::ProtocolDetector.Detector::(__init__) Using required_size=11
 Reactor thread::INFO::2017-02-03 08:32:24,643::protocoldetector
 ::127::ProtocolDetector.Detector::(handle_read) Detected protocol xml
 from ::1:53082
 Reactor thread::DEBUG::2017-02-03 08:32:24,643::bindingxmlrpc::1
 317::XmlDetector::(handle_socket) xml over http detected from ('::1',
 53082)
 BindingXMLRPC::INFO::2017-02-03 
 08:32:24,643::xmlrpc::73::vds.XMLRPCServer::(handle_request)
 Starting request handler for ::1:53082
 Thread-20::INFO::2017-02-03 08:32:24,644::xmlrpc::83::vds.
 XMLRPCServer::(_process_requests) Request handler for ::1:53082 started
 Thread-20::DEBUG::2017-02-03 
 08:32:24,644::bindingxmlrpc::1263::vds::(wrapper)
 client [::1]::call getAllVmStats with () {}
 

Re: [ovirt-users] problem after rebooting the node

2017-02-06 Thread Edward Haas
Please package the logs (tar or zip) and send them.

On Mon, Feb 6, 2017 at 12:05 PM, Shalabh Goel 
wrote:

> Yes, I am using OVS as the switch type and I did not know that it was not
> supported officially.
>
> The output of ovs-vsctl show is as follows:
>
> f634d53e-4849-488b-8454-6b1fafa7c6ac
> ovs_version: "2.6.90"
>
> I am attaching OVS switch logs below:
>
> /var/log/openvswitch/ovsdb-server.log
>
>
> 2017-02-06T09:46:07.788Z|1|vlog|INFO|opened log file
> /var/log/openvswitch/ovsdb-server.log
> 2017-02-06T09:46:07.791Z|2|ovsdb_server|INFO|ovsdb-server (Open
> vSwitch) 2.6.90
> 2017-02-06T09:46:17.802Z|3|memory|INFO|2296 kB peak resident set size
> after 10.0 seconds
> 2017-02-06T09:46:17.802Z|4|memory|INFO|cells:16 json-caches:1
> monitors:1 sessions:1
>
> ovs-vswitchd.log
>
>
> 2017-02-06T09:46:07.999Z|1|vlog|INFO|opened log file
> /var/log/openvswitch/ovs-vswitchd.log
> 2017-02-06T09:46:08.036Z|2|ovs_numa|INFO|Discovered 24 CPU cores on
> NUMA node 0
> 2017-02-06T09:46:08.036Z|3|ovs_numa|INFO|Discovered 24 CPU cores on
> NUMA node 1
> 2017-02-06T09:46:08.036Z|4|ovs_numa|INFO|Discovered 2 NUMA nodes and
> 48 CPU cores
> 2017-02-06T09:46:08.037Z|5|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
> connecting...
> 2017-02-06T09:46:08.037Z|6|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
> connected
> 2017-02-06T09:46:08.039Z|7|bridge|INFO|ovs-vswitchd (Open vSwitch)
> 2.6.90
>
> What should I do now?
>
> The engine says that "Host host2 does not comply with the cluster Default
> networks, the following networks are missing on host: 'ovirtmgmt'"
>
> What other logs should I attach?
>
> Thanks
>
> Shalabh Goel
>
> On Sun, Feb 5, 2017 at 1:10 PM, Edward Haas  wrote:
>
>> Based on what I can see, you used OVS as the switch type and it seems ovs
>> (openvswitch) is not properly installed on your host.
>> Make sure that you have ovs operational by issuing "ovs-vsctl show".
>>
>> You should note that OVS network support is not an official release
>> feature, and you should use it on 4.1 and up versions.
>> Fixes will be probably submitted to master (appearing in nightly builds).
>>
>> Next time please include the mailing-list in your replies and attach the
>> log files, it is less spamming.
>>
>> Thanks,
>> Edy.
>>
>> On Fri, Feb 3, 2017 at 5:07 AM, Shalabh Goel 
>> wrote:
>>
>>> log from messages
>>>
>>> Feb  3 08:27:53 ovirtnode3 ovs-vsctl: 
>>> ovs|1|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock:
>>> database connection failed (No such file or directory)
>>> Feb  3 08:27:53 ovirtnode3 journal: vdsm vds ERROR Executing commands
>>> failed: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database
>>> connection failed (No su
>>> ch file or directory)#012Traceback (most recent call last):#012  File
>>> "/usr/share/vdsm/API.py", line 1531, in setupNetworks#012
>>> supervdsm.getProxy().setup
>>> Networks(networks, bondings, options)#012  File
>>> "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in
>>> __call__#012return callMethod()#012  Fi
>>> le "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in
>>> #012**kwargs)#012  File "", line 2, in
>>> setupNetworks#012  File "/usr
>>> /lib64/python2.7/multiprocessing/managers.py", line 773, in
>>> _callmethod#012raise convert_to_error(kind,
>>> result)#012ConfigNetworkError: (21, 'Executing co
>>> mmands failed: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database
>>> connection failed (No such file or directory)')
>>>
>>> Log from vdsm.log
>>>
>>> Reactor thread::INFO::2017-02-03 08:32:24,638::protocoldetector
>>> ::72::ProtocolDetector.AcceptorImpl::(handle_accept) Accepted
>>> connection from ::1:53082
>>> Reactor thread::DEBUG::2017-02-03 08:32:24,643::protocoldetector
>>> ::91::ProtocolDetector.Detector::(__init__) Using required_size=11
>>> Reactor thread::INFO::2017-02-03 08:32:24,643::protocoldetector
>>> ::127::ProtocolDetector.Detector::(handle_read) Detected protocol xml
>>> from ::1:53082
>>> Reactor thread::DEBUG::2017-02-03 08:32:24,643::bindingxmlrpc::1
>>> 317::XmlDetector::(handle_socket) xml over http detected from ('::1',
>>> 53082)
>>> BindingXMLRPC::INFO::2017-02-03 
>>> 08:32:24,643::xmlrpc::73::vds.XMLRPCServer::(handle_request)
>>> Starting request handler for ::1:53082
>>> Thread-20::INFO::2017-02-03 08:32:24,644::xmlrpc::83::vds.
>>> XMLRPCServer::(_process_requests) Request handler for ::1:53082 started
>>> Thread-20::DEBUG::2017-02-03 
>>> 08:32:24,644::bindingxmlrpc::1263::vds::(wrapper)
>>> client [::1]::call getAllVmStats with () {}
>>> Thread-20::DEBUG::2017-02-03 
>>> 08:32:24,644::bindingxmlrpc::1270::vds::(wrapper)
>>> return getAllVmStats with {'status': {'message': 'Done', 'code': 0},
>>> 'statsLis
>>> t': (suppressed)}
>>> Thread-20::INFO::2017-02-03 
>>> 08:32:24,644::bindingxmlrpc::1297::vds::(wrapper)
>>> RPC call getAllVmStats finished (code=0) in 0.00 seconds

Re: [ovirt-users] VDAgent

2017-02-06 Thread Sandro Bonazzola
On Sat, Feb 4, 2017 at 9:59 PM, Fernando Fuentes 
wrote:

> Hello Sandro,
> Thanks for your reply!
>
> I will do that. I want to make sure though that updating the host will not
> make my guests loose the ability to use spice and nor will it create a
> problem with my oVirt Manager been on 4.0.X branch?
>

Adding some people that may confirm but I think there shouldn't be any
regression on it.


>
> Thanks!
>
> Regards,
>
> --
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
>
>
>
> On Fri, Feb 3, 2017, at 01:11 PM, Sandro Bonazzola wrote:
>
>
>
> Il 30/Gen/2017 09:56 PM, "Fernando Fuentes"  ha
> scritto:
>
>
> Sandro,
>
> I did the update from the hosts tab on ovirt:
> The ovirt version is: oVirt Engine Version: 4.0.2.6-1.el7.centos
>
>
>
> Sorry Fernando I missed your email.
> I would suggest to update your hosts to centos 7.3 and oVirt 4.1.
> If you don't want to upgrade to 4.1 please upgrade at least to latest 4.0
> which is 4.0.6.
>
>
>
>
>
> All of my hosts are Cent7 x86_64
> [root@ogias ~]# uname -a
> Linux ogias.aasteel.net 3.10.0-327.22.2.el7.x86_64 #1 SMP Thu Jun 23
> 17:05:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> [root@ogias ~]# cat /etc/redhat-release
> CentOS Linux release 7.2.1511 (Core)
> [root@ogias ~]#
>
> I am trying to email you the sos report but it exceeds our mail server
> size limit :(
>
> Regards,
>
>
> --
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
>
>
>
> On Sat, Jan 28, 2017, at 12:29 PM, Sandro Bonazzola wrote:
>
>
>
> Il 27/Gen/2017 16:51, "Fernando Fuentes"  ha
> scritto:
>
> Team,
>
> After a host update on my cluster, All of my Windows vm's running the
> vdagent from the ovirt tools are running at 100% CPU utilization.
>
> Any ideas why would this happen?
>
>
> Hi,
> Can you please share details about the update?
> Which distribution? What has been updated? Can you share a sos report from
> the host?
>
>
>
>
> Regards,
>
>
> --
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
> ___
> 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] How to update ovirt nodes

2017-02-06 Thread Shalabh Goel
Hi,

I have 3 nodes. 2 compute and 1 storage (NFS) and separate server for
engine. I upgraded the engine first. I went on smoothly without any errors.

Then I started upgrade on all 3 of them by installing the
ovirt-release41.rpm. But the upgrade timed out and failed on all the 3
nodes.

Then I restarted upgrade on first node from within the engine again. The
engine event log said the upgrade timed out but when I checked on the node,
it was successful (means the yum service was running on the node and it
installed the upagrde but the engine said otherwise). So I restarted that
node. But after the reboot, the node was moved to non-operational by the
engine because of the following error,
 "Host host1 does not comply with the cluster Default networks, the
following networks are missing on host: 'ovirtmgmt'".

UPDATE: I enabled open-vswitch service on the this node and it has been
successfully added to the engine.

After that my second node developed some hardware problem. So I did a fresh
install of ovirt 4.0.3 on it and then changed the repo files on it by
replacing 40 by 41 in all the files (including ovirt-dependencies.repo). I
upgraded it successfully and rebooted and logged in to 4.1. Now, in engine
I removed the second node and tried to add it but I got the same error on
this node too. I have enabled the open-vswitch service on this node too and
rebooted the machine but the error stays the same. I think that the issue
has something to do with OVS. Do you still want me to attach engine.log and
host-deploy.log files?

Meanwhile I have changed the changed the cluster and data center
compatibility to 4.1


Now regarding upgrade of the third node (storage). I moved the node to
maintenance and ran the following command on the node:

*yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm
*

When I run yum update, I am getting the following errors:




























































































































































































































































































*Loaded plugins: fastestmirror, imgbased-warningWarning: yum operations are
not persisted across upgrades!Repository virtio-win-stable is listed more
than once in the
configurationcentos-opstools-testing
| 2.9 kB  00:00:00
centos-ovirt-common-candidate
| 3.4 kB  00:00:00
centos-ovirt41-candidate
| 3.4 kB  00:00:00
ovirt-4.1
| 2.9 kB  00:00:00
ovirt-4.1-centos-gluster38
| 2.9 kB  00:00:00
ovirt-4.1-epel/x86_64/metalink
| 6.2 kB  00:00:00
ovirt-4.1-epel
| 4.3 kB  00:00:00
ovirt-4.1-patternfly1-noarch-epel
| 3.0 kB  00:00:00 (1/3):
ovirt-4.1/7/primary_db
|  88 kB  00:00:00 ovirt-4.1-epel/x86_64/primary_
FAILED
https://repo.fedoralinux.ir/pub/epel/7/x86_64/repodata/e8dcf6c8fd1618b376ebc6b71cab2f7d1e8f10d02bc9404825f0a2a0b524ef4c-primary.sqlite.xz
:
[Errno 14] curl#60 - "Peer's Certificate has expired."Trying other
mirror.It was impossible to connect to the CentOS servers.This could mean a
connectivity issue in your environment, such as the requirement to
configure a proxy,or a transparent proxy that tampers with TLS security, or
an incorrect system clock.Please collect information about the specific
failure that occurs in your environment,using the instructions in:
https://access.redhat.com/solutions/1527033
 and create a bug on
https://bugs.centos.org/ (2/3):
ovirt-4.1-epel/x86_64/updateinfo
| 730 kB  00:00:15 (3/3):
ovirt-4.1-epel/x86_64/primary_db
| 4.5 MB  00:00:27 Loading mirror speeds from cached hostfile *
ovirt-4.0: ftp.nluug.nl  * ovirt-4.0-epel:
ae.mirror.rasanegar.com  * ovirt-4.1:
ftp.nluug.nl  * ovirt-4.1-epel:
ae.mirror.rasanegar.com Resolving
Dependencies--> Running transaction check---> Package
cockpit-ovirt-dashboard.noarch 0:0.10.6-1.3.6.el7.centos will be
updated---> Package cockpit-ovirt-dashboard.noarch
0:0.10.7-0.0.6.el7.centos will be an update---> Package glusterfs.x86_64
0:3.7.13-1.el7 will be updated---> Package glusterfs.x86_64 0:3.8.8-1.el7
will be an update---> Package glusterfs-api.x86_64 0:3.7.13-1.el7 will be
updated---> Package glusterfs-api.x86_64 0:3.8.8-1.el7 will be an
update---> Package glusterfs-cli.x86_64 0:3.7.13-1.el7 will be updated--->
Package glusterfs-cli.x86_64 0:3.8.8-1.el7 will be an update---> Package
glusterfs-client-xlators.x86_64 0:3.7.13-1.el7 will be updated---> Package
glusterfs-client-xlators.x86_64 0:3.8.8-1.el7 will be an update---> Package
glusterfs-fuse.x86_64 0:3.7.13-1.el7 will be updated---> Package
glusterfs-fuse.x86_64 

Re: [ovirt-users] [Call for feedback] did you install/update to 4.1.0?

2017-02-06 Thread Simone Tiraboschi
On Sat, Feb 4, 2017 at 11:52 AM, Ralf Schenk  wrote:

> Hello,
>
> I have set up 3 hosts for engine, 2 of them are working correct. There is
> no other host even having broker/agent installed. Is it possible that the
> error occurs because the hosts are multihomed (Management IP, IP for
> storage) and can communicate with different IP's ?
>
Having multiple logical networks for storage, management and so on is a
good practice and it's advised so I tend to exclude any issue there.
The point is why your microcloud27.sub.mydomain.de fails acquiring a lock
as host 3.
Probably the simplest fix is just setting it in maintenance mode from the
engine, removing it and deploying it from the engine as an hosted engine
host again.



> hosted-engine --vm-status on both working hosts seems correct: (3 is out
> of order...)
>
> [root@microcloud21 ~]# hosted-engine --vm-status
>
>
> --== Host 1 status ==--
>
> conf_on_shared_storage : True
> Status up-to-date  : True
> Hostname   : microcloud21.sub.mydomain.de
> Host ID: 1
> Engine status  : {"health": "good", "vm": "up",
> "detail": "up"}
> Score  : 3400
> stopped: False
> Local maintenance  : False
> crc32  : 5941227d
> local_conf_timestamp   : 152316
> Host timestamp : 152302
> Extra metadata (valid at timestamp):
> metadata_parse_version=1
> metadata_feature_version=1
> timestamp=152302 (Sat Feb  4 11:49:29 2017)
> host-id=1
> score=3400
> vm_conf_refresh_time=152316 (Sat Feb  4 11:49:43 2017)
> conf_on_shared_storage=True
> maintenance=False
> state=EngineUp
> stopped=False
>
>
> --== Host 2 status ==--
>
> conf_on_shared_storage : True
> Status up-to-date  : True
> Hostname   : microcloud24.sub.mydomain.de
> Host ID: 2
> Engine status  : {"reason": "vm not running on this
> host", "health": "bad", " vm": "down",
> "detail": "unknown"}
> Score  : 3400
> stopped: False
> Local maintenance  : False
> crc32  : 77e25433
> local_conf_timestamp   : 157637
> Host timestamp : 157623
> Extra metadata (valid at timestamp):
> metadata_parse_version=1
> metadata_feature_version=1
> timestamp=157623 (Sat Feb  4 11:49:34 2017)
> host-id=2
> score=3400
> vm_conf_refresh_time=157637 (Sat Feb  4 11:49:48 2017)
> conf_on_shared_storage=True
> maintenance=False
> state=EngineDown
> stopped=False
>
>
> --== Host 3 status ==--
>
> conf_on_shared_storage : True
> Status up-to-date  : False
> Hostname   : microcloud27.sub.mydomain.de
> Host ID: 3
> Engine status  : unknown stale-data
> Score  : 0
> stopped: True
> Local maintenance  : False
> crc32  : 74798986
> local_conf_timestamp   : 77946
> Host timestamp : 77932
> Extra metadata (valid at timestamp):
> metadata_parse_version=1
> metadata_feature_version=1
> timestamp=77932 (Fri Feb  3 15:19:25 2017)
> host-id=3
> score=0
> vm_conf_refresh_time=77946 (Fri Feb  3 15:19:39 2017)
> conf_on_shared_storage=True
> maintenance=False
> state=AgentStopped
> stopped=True
>
> Am 03.02.2017 um 19:20 schrieb Simone Tiraboschi:
>
>
>
> On Fri, Feb 3, 2017 at 5:22 PM, Ralf Schenk  wrote:
>
>> Hello,
>>
>> of course:
>>
>> [root@microcloud27 mnt]# sanlock client status
>> daemon 8a93c9ea-e242-408c-a63d-a9356bb22df5.microcloud
>> p -1 helper
>> p -1 listener
>> p -1 status
>>
>> sanlock.log attached. (Beginning 2017-01-27 where everything was fine)
>>
> Thanks, the issue is here:
>
> 2017-02-02 19:01:22+0100 4848 [1048]: s36 lockspace 
> 7c8deaa8-be02-4aaf-b9b4-ddc8da99ad96:3:/rhev/data-center/mnt/glusterSD/glusterfs.sub.mydomain.de:_engine/7c8deaa8-be02-4aaf-b9b4-ddc8da99ad96/dom_md/ids:0
> 2017-02-02 19:03:42+0100 4988 [12983]: s36 delta_acquire host_id 3 busy1 3 15 
> 13129 7ad427b1-fbb6-4cee-b9ee-01f596fddfbb.microcloud
> 2017-02-02 19:03:43+0100 4989 [1048]: s36 add_lockspace fail result -262
>
> Could you please check if you have other hosts contending for the same ID
> (id=3 in this case).
>
>
>
> --
>
>
> *Ralf Schenk*
> fon +49 (0) 24 05 / 40 83 70 <+49%202405%20408370>
> fax +49 (0) 24 05 / 40 83 759 <+49%202405%204083759>
> mail *r...@databay.de* 

[ovirt-users] [oVirt 4.1.0] experimental container support

2017-02-06 Thread Francesco Romani
Hi all,


In case you missed it, oVirt 4.1.0 gained some support to run container
side to side to VMs.

Read the full story here:
https://fromanirh.github.io/containers-in-ovirt.html


I'll be happy to answer any question - make sure to CC me to have a
faster response time!


Bests,

-- 
Francesco Romani
Red Hat Engineering Virtualization R & D
IRC: fromani

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


Re: [ovirt-users] problem after rebooting the node

2017-02-06 Thread Shalabh Goel
Yes, I am using OVS as the switch type and I did not know that it was not
supported officially.

The output of ovs-vsctl show is as follows:

f634d53e-4849-488b-8454-6b1fafa7c6ac
ovs_version: "2.6.90"

I am attaching OVS switch logs below:

/var/log/openvswitch/ovsdb-server.log


2017-02-06T09:46:07.788Z|1|vlog|INFO|opened log file
/var/log/openvswitch/ovsdb-server.log
2017-02-06T09:46:07.791Z|2|ovsdb_server|INFO|ovsdb-server (Open
vSwitch) 2.6.90
2017-02-06T09:46:17.802Z|3|memory|INFO|2296 kB peak resident set size
after 10.0 seconds
2017-02-06T09:46:17.802Z|4|memory|INFO|cells:16 json-caches:1
monitors:1 sessions:1

ovs-vswitchd.log


2017-02-06T09:46:07.999Z|1|vlog|INFO|opened log file
/var/log/openvswitch/ovs-vswitchd.log
2017-02-06T09:46:08.036Z|2|ovs_numa|INFO|Discovered 24 CPU cores on
NUMA node 0
2017-02-06T09:46:08.036Z|3|ovs_numa|INFO|Discovered 24 CPU cores on
NUMA node 1
2017-02-06T09:46:08.036Z|4|ovs_numa|INFO|Discovered 2 NUMA nodes and 48
CPU cores
2017-02-06T09:46:08.037Z|5|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connecting...
2017-02-06T09:46:08.037Z|6|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connected
2017-02-06T09:46:08.039Z|7|bridge|INFO|ovs-vswitchd (Open vSwitch)
2.6.90

What should I do now?

The engine says that "Host host2 does not comply with the cluster Default
networks, the following networks are missing on host: 'ovirtmgmt'"

What other logs should I attach?

Thanks

Shalabh Goel

On Sun, Feb 5, 2017 at 1:10 PM, Edward Haas  wrote:

> Based on what I can see, you used OVS as the switch type and it seems ovs
> (openvswitch) is not properly installed on your host.
> Make sure that you have ovs operational by issuing "ovs-vsctl show".
>
> You should note that OVS network support is not an official release
> feature, and you should use it on 4.1 and up versions.
> Fixes will be probably submitted to master (appearing in nightly builds).
>
> Next time please include the mailing-list in your replies and attach the
> log files, it is less spamming.
>
> Thanks,
> Edy.
>
> On Fri, Feb 3, 2017 at 5:07 AM, Shalabh Goel 
> wrote:
>
>> log from messages
>>
>> Feb  3 08:27:53 ovirtnode3 ovs-vsctl: 
>> ovs|1|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock:
>> database connection failed (No such file or directory)
>> Feb  3 08:27:53 ovirtnode3 journal: vdsm vds ERROR Executing commands
>> failed: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database
>> connection failed (No su
>> ch file or directory)#012Traceback (most recent call last):#012  File
>> "/usr/share/vdsm/API.py", line 1531, in setupNetworks#012
>> supervdsm.getProxy().setup
>> Networks(networks, bondings, options)#012  File
>> "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in
>> __call__#012return callMethod()#012  Fi
>> le "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in
>> #012**kwargs)#012  File "", line 2, in
>> setupNetworks#012  File "/usr
>> /lib64/python2.7/multiprocessing/managers.py", line 773, in
>> _callmethod#012raise convert_to_error(kind,
>> result)#012ConfigNetworkError: (21, 'Executing co
>> mmands failed: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database
>> connection failed (No such file or directory)')
>>
>> Log from vdsm.log
>>
>> Reactor thread::INFO::2017-02-03 08:32:24,638::protocoldetector
>> ::72::ProtocolDetector.AcceptorImpl::(handle_accept) Accepted connection
>> from ::1:53082
>> Reactor thread::DEBUG::2017-02-03 08:32:24,643::protocoldetector
>> ::91::ProtocolDetector.Detector::(__init__) Using required_size=11
>> Reactor thread::INFO::2017-02-03 08:32:24,643::protocoldetector
>> ::127::ProtocolDetector.Detector::(handle_read) Detected protocol xml
>> from ::1:53082
>> Reactor thread::DEBUG::2017-02-03 08:32:24,643::bindingxmlrpc::1
>> 317::XmlDetector::(handle_socket) xml over http detected from ('::1',
>> 53082)
>> BindingXMLRPC::INFO::2017-02-03 
>> 08:32:24,643::xmlrpc::73::vds.XMLRPCServer::(handle_request)
>> Starting request handler for ::1:53082
>> Thread-20::INFO::2017-02-03 08:32:24,644::xmlrpc::83::vds.
>> XMLRPCServer::(_process_requests) Request handler for ::1:53082 started
>> Thread-20::DEBUG::2017-02-03 
>> 08:32:24,644::bindingxmlrpc::1263::vds::(wrapper)
>> client [::1]::call getAllVmStats with () {}
>> Thread-20::DEBUG::2017-02-03 
>> 08:32:24,644::bindingxmlrpc::1270::vds::(wrapper)
>> return getAllVmStats with {'status': {'message': 'Done', 'code': 0},
>> 'statsLis
>> t': (suppressed)}
>> Thread-20::INFO::2017-02-03 08:32:24,644::bindingxmlrpc::1297::vds::(wrapper)
>> RPC call getAllVmStats finished (code=0) in 0.00 seconds
>> Thread-20::INFO::2017-02-03 08:32:24,645::xmlrpc::91::vds.
>> XMLRPCServer::(_process_requests) Request handler for ::1:53082 stopped
>> periodic/0::DEBUG::2017-02-03 08:32:24,907::sampling::508::v
>> irt.sampling.VMBulkSampler::(__call__) sampled timestamp 4347942.15
>> elapsed 0.010 

Re: [ovirt-users] jumbo frames inside vm best practices?

2017-02-06 Thread Edward Haas
Your described setup seems correct.

Please attempt to isolate the issue by trying to pass traffic between the
hosts, taking the VM/s out of the equation.
You may also consider connecting the hosts directly to each other, to make
sure this is not a switch problem.

Thanks,
Edy.



On Mon, Feb 6, 2017 at 1:50 AM, Gianluca Cecchi 
wrote:

> Hello,
> I'm testing an Oracle RAC with 2 Oracle Linux VMs inside a 4.0.6
> environment.
> They run on two different hosts
> I would like to configure RAC intracluster communication with jumbo frames.
> At VM level network adapter is eth1 (mapped to a vlan 95 at oVirt hosts
> side)
> At oVirt side I configured a vm enabled vlan with mtu=9000
> I verified that at hosts side I have
>
> vlan95: flags=4163  mtu 9000
> ether 00:1c:c4:ab:be:ba  txqueuelen 1000  (Ethernet)
> RX packets 61706  bytes 3631426 (3.4 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 3  bytes 258 (258.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> And able to do a
> ping -M do -s 8972 ip
> from each host to the other one
> In VMs I configure the same MTU=9000 in ifcfg-eth1
>
> But actually inside VMs it works erratically: the same ping test is ok
> between the VMs but Oracle checks sometimes work and sometimes give error
> on communication.
> At initial cluster config, the second node fails to start the cluster.
> I tried 5-6 times and also tried then to set mtu=8000 inside the VMs,
> supposing some sort of inner overhead to consider (such as 2 times 28
> bytes) but nothing.
> As soon as I set MTU=1500 at VM side, the cluster is able to form without
> any problem.
> I can survive without jumbo frames in this particular case, because this
> is only a test, but the question remains about eventual best practices to
> put in place if I want to use jumbo frames.
>
> One thing I see is that at VM side I see many drops when interface mtu was
> 9000, such as
>
> eth1  Link encap:Ethernet  HWaddr 00:1A:4A:17:01:57
>   inet addr:192.168.10.32  Bcast:192.168.10.255  Mask:255.255.255.0
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:93046 errors:0 dropped:54964 overruns:0 frame:0
>   TX packets:26258 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:25726242 (24.5 MiB)  TX bytes:33573207 (32.0 MiB)
>
> at host side I see drops at bond0 level only:
>
> [root@ovmsrv05 ~]# brctl show
> bridge namebridge idSTP enabledinterfaces
> ;vdsmdummy;8000.no
> vlan1008000.001cc446ef73nobond1.100
> vlan658000.001cc446ef73nobond1.65
> vnet0
> vnet1
> vlan958000.001cc4abbebanobond0.95
> vnet2
>
> bond0: flags=5187  mtu 9000
> ether 00:1c:c4:ab:be:ba  txqueuelen 1000  (Ethernet)
> RX packets 2855175  bytes 3126868334 <(312)%20686-8334> (2.9 GiB)
> RX errors 0  dropped 11686  overruns 0  frame 0
> TX packets 1012849  bytes 478702140 (456.5 MiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> bond0.95: flags=4163  mtu 9000
> ether 00:1c:c4:ab:be:ba  txqueuelen 1000  (Ethernet)
> RX packets 100272  bytes 27125992 (25.8 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 42355  bytes 40833904 (38.9 MiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> vlan95: flags=4163  mtu 9000
> ether 00:1c:c4:ab:be:ba  txqueuelen 1000  (Ethernet)
> RX packets 62576  bytes 3719175 (3.5 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 3  bytes 258 (258.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> vnet2: flags=4163  mtu 9000
> inet6 fe80::fc1a:4aff:fe17:157  prefixlen 64  scopeid 0x20
> ether fe:1a:4a:17:01:57  txqueuelen 1000  (Ethernet)
> RX packets 21014  bytes 24139492 (23.0 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 85777  bytes 21089777 (20.1 MiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> [root@ovmsrv05 ~]# cat /proc/net/bonding/bond0
> Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
>
> Bonding Mode: fault-tolerance (active-backup)
> Primary Slave: None
> Currently Active Slave: enp3s0
> MII Status: up
> MII Polling Interval (ms): 100
> Up Delay (ms): 0
> Down Delay (ms): 0
>
> Slave Interface: enp3s0
> MII Status: up
> Speed: 1000 Mbps
> Duplex: full
> Link Failure Count: 0
> Permanent HW addr: 00:1c:c4:ab:be:ba
> Slave queue ID: 0
>
> Slave Interface: enp5s0
> MII Status: up
> Speed: 

Re: [ovirt-users] Guest IP

2017-02-06 Thread Edward Haas
It does show the same Guest Agent Data on the user portal.
Assuming you have added the UserRole permission to the VM, you should see
the VM on the user portal under the Extended tab, similar to what is seen
on the admin portal.

Thanks,
Edy.

On Thu, Feb 2, 2017 at 5:25 PM, Alexandr Krivulya 
wrote:

> Hi,
>
> is there any way to get guest ip provided by guest tools from user portal?
> It present in an admin portal, but not in user.
>
> ___
> 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