Re: [ovirt-users] Regression in Gluster volume code?

[noc]

On 16-12-2015 17:06, Sahina Bose wrote:
>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1292173
Thanks. Will have a look at it and amend if needed.

Joop

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

Re: [ovirt-users] Ovirt Backup API

[Eli Mesika]

- Original Message -
> From: "Manuel Meier" 
> To: users@ovirt.org
> Sent: Thursday, December 17, 2015 11:40:04 AM
> Subject: [ovirt-users] Ovirt Backup API
> 
> Hi,
> 
> we are planning to use ovirt for our internal IT.
> At the moment we are not sure about the proposed backup procedure.
> It seems that there is an Backup API but not really well documented.
> Where can we get the documentation?
> Also what Backup Programs support the Ovirt Backup API ?

Hi Manuel
Please check http://www.ovirt.org/Features/Backup-Restore_API_Integration

Regards

Eli Mesika



> 
> 
> Thanks for your help
> 
> 
> ___
> 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] Network instability after upgrade 3.6.0 -> 3.6.1

[Stefano Danzi]

Hello,
I have one testing host (only one host) with self hosted engine and 2 VM 
(one linux and one windows).


After upgrade ovirt from 3.6.0 to 3.6.1 the network connection works 
discontinuously.
Every 10 minutes HA agent restart hosted engine VM because result down. 
But the machine is UP,

only the network stop to work for some minutes.
I activate global maintenace mode to prevent engine reboot. If I ssh to 
the hosted engine sometimes
the connection work and sometimes no.  Using VNC connection to engine I 
see that sometime VM reach external network

and sometimes no.
If I do a tcpdump on phisical ethernet interface I don't see any packet 
when network on vm don't work.


Same thing happens fo others two VM.

Before the upgrade I never had network problems.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Ovirt Backup API

[Manuel Meier]

Hi, 

we are planning to use ovirt for our internal IT. 
At the moment we are not sure about the proposed backup procedure. 
It seems that there is an Backup API but not really well documented. 
Where can we get the documentation? 
Also what Backup Programs support the Ovirt Backup API ? 


Thanks for your help 

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

Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not start

[Yedidyah Bar David]

On Thu, Dec 17, 2015 at 2:45 PM, Willard Dennis  wrote:
> Sure, which ones would be useful?
>
> [root@ovirt-node-01 ~]# cd /var/log/vdsm/
> [root@ovirt-node-01 vdsm]# ls -la
> total 11520
> drwxr-xr-x   3 vdsm kvm 4096 Dec 17 04:34 .
> drwxr-xr-x. 13 root root4096 Dec 13 03:32 ..
> drwxr-xr-x   2 vdsm kvm6 Nov 24 05:42 backup
> -rw-r--r--   1 vdsm kvm0 Dec  1 23:42 connectivity.log
> -rw-r--r--   1 vdsm kvm   966994 Dec 17 07:20 mom.log
> -rw-r--r--   1 vdsm kvm  2097091 Dec 17 04:34 mom.log.1
> -rw-r--r--   1 vdsm kvm  2097117 Dec 16 22:34 mom.log.2
> -rw-r--r--   1 vdsm kvm  2097119 Dec 16 16:33 mom.log.3
> -rw-r--r--   1 vdsm kvm  2097120 Dec 16 10:32 mom.log.4
> -rw-r--r--   1 vdsm kvm  2097115 Dec 16 04:32 mom.log.5
> -rw-r--r--   1 root root  168714 Dec  2 10:30 supervdsm.log
> -rw-r--r--   1 root root3069 Oct 16 12:25 upgrade.log
> -rw-r--r--   1 vdsm kvm0 Dec  1 23:42 vdsm.log

Perhaps just upload all of them somewhere?

Also might be selinux? Please check/post also audit logs.

>
>
>> On Dec 17, 2015, at 2:51 AM, Fabian Deutsch  wrote:
>>
>> On Wed, Dec 16, 2015 at 10:52 PM, Willard Dennis  
>> wrote:
>>> Any thoughts on this issue?? This is holding up my project (oVirt hosted
>>> engine install won’t proceed if VDSM service is not running…)  Why am I even
>>> having such problems with the VDSM service? It’s on a vanilla CentOS 7
>>> install…
>>
>> Hey,
>>
>> so it looks like vdsm has an issue, can you provide some logs?
>>
>> - fabian
>>
>>
>> --
>> Fabian Deutsch 
>> RHEV Hypervisor
>> Red Hat
>
> ___
> 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] gwt super dev mode

[Vojtech Szocs]

Hi,

oVirt UI currently uses GWT SDK version 2.6.1
In GWT 2.6.x "classic" dev mode is still the default one.

We tried to use "super" dev mode some time ago [1] but it
didn't work for us, probably due to using direct-eval RPC
mechanism (we got HTTP 500 responses for RPC requests).

  [1] https://gerrit.ovirt.org/#/c/26093/

Because "classic" dev mode relies on NPAPI-based browser
plugin, the downside is that developers must use old'ish
browsers that still support NPAPI (Firefox <= 26 etc).

I think we can revisit this and try to experiment with
"super" dev mode as I believe [1] was done in context of
GWT 2.5.x anyway.

Regards,
Vojtech


- Original Message -
> From: "royin rolland" 
> To: vsz...@redhat.com
> Cc: users@ovirt.org
> Sent: Wednesday, December 16, 2015 2:49:25 AM
> Subject: gwt super dev mode
> 
> hi，vszos：
>   ovirt engine when it supports super dev mode？ovirt 3.6?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not start

[Willard Dennis]

Sure, which ones would be useful?

[root@ovirt-node-01 ~]# cd /var/log/vdsm/
[root@ovirt-node-01 vdsm]# ls -la
total 11520
drwxr-xr-x   3 vdsm kvm 4096 Dec 17 04:34 .
drwxr-xr-x. 13 root root4096 Dec 13 03:32 ..
drwxr-xr-x   2 vdsm kvm6 Nov 24 05:42 backup
-rw-r--r--   1 vdsm kvm0 Dec  1 23:42 connectivity.log
-rw-r--r--   1 vdsm kvm   966994 Dec 17 07:20 mom.log
-rw-r--r--   1 vdsm kvm  2097091 Dec 17 04:34 mom.log.1
-rw-r--r--   1 vdsm kvm  2097117 Dec 16 22:34 mom.log.2
-rw-r--r--   1 vdsm kvm  2097119 Dec 16 16:33 mom.log.3
-rw-r--r--   1 vdsm kvm  2097120 Dec 16 10:32 mom.log.4
-rw-r--r--   1 vdsm kvm  2097115 Dec 16 04:32 mom.log.5
-rw-r--r--   1 root root  168714 Dec  2 10:30 supervdsm.log
-rw-r--r--   1 root root3069 Oct 16 12:25 upgrade.log
-rw-r--r--   1 vdsm kvm0 Dec  1 23:42 vdsm.log


> On Dec 17, 2015, at 2:51 AM, Fabian Deutsch  wrote:
> 
> On Wed, Dec 16, 2015 at 10:52 PM, Willard Dennis  wrote:
>> Any thoughts on this issue?? This is holding up my project (oVirt hosted
>> engine install won’t proceed if VDSM service is not running…)  Why am I even
>> having such problems with the VDSM service? It’s on a vanilla CentOS 7
>> install…
> 
> Hey,
> 
> so it looks like vdsm has an issue, can you provide some logs?
> 
> - fabian
> 
> 
> -- 
> Fabian Deutsch 
> RHEV Hypervisor
> Red Hat

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

[ovirt-users] [ANN] Async release for ovirt-hosted-engine-ha is now available

[Sandro Bonazzola]

The oVirt Team has just released a new version of ovirt-hosted-engine-ha
package that fixes several issues.[1].
We recommend to all users who have already upgraded to
ovirt-hosted-engine-ha 1.3.3.3 to update to the 1.3.3.4 release included in
this async release.
Thanks,

[1] http://www.ovirt.org/OVirt_3.6.1_Release_Notes#oVirt_Hosted_Engine_HA

-- 
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] Problem with hosted engine setup - vsdmd does not start

[Willard Dennis]

This is from /var/log/messages —

Dec 17 07:46:25 ovirt-node-01 systemd: vdsmd.service holdoff time over, 
scheduling restart.
Dec 17 07:46:35 ovirt-node-01 systemd: mom-vdsm.service stopping timed out. 
Killing.
Dec 17 07:46:35 ovirt-node-01 systemd: mom-vdsm.service: main process exited, 
code=killed, status=9/KILL
Dec 17 07:46:35 ovirt-node-01 systemd: Unit mom-vdsm.service entered failed 
state.
Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running mkdirs
Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
configure_coredump
Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
configure_vdsm_logs
Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
wait_for_network
Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running run_init_hooks
Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
upgraded_version_check
Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
check_is_configured
Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: Current revision of 
multipath.conf detected, preserving
Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: libvirt is already 
configured for vdsm
Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
validate_configuration
Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: SUCCESS: ssl configured to 
true. No conflicts
Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
prepare_transient_repository
Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
syslog_available
Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running nwfilter
Dec 17 07:46:37 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running dummybr
Dec 17 07:46:37 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running tune_system
Dec 17 07:46:37 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running test_space
Dec 17 07:46:37 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running test_lo
Dec 17 07:46:37 ovirt-node-01 vdsm: vdsm user could not manage to run sudo 
operation: (stderr: ['sudo: sorry, you must have a tty to run sudo']). Verify 
sudoer rules configuration
Dec 17 07:46:37 ovirt-node-01 systemd: vdsmd.service: main process exited, 
code=exited, status=1/FAILURE
Dec 17 07:46:37 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
run_final_hooks
Dec 17 07:46:37 ovirt-node-01 systemd: Unit vdsmd.service entered failed state.
Dec 17 07:46:37 ovirt-node-01 systemd: vdsmd.service holdoff time over, 
scheduling restart.


So, the message "vdsm user could not manage to run sudo operation: (stderr: 
['sudo: sorry, you must have a tty to run sudo']). Verify sudoer rules 
configuration” — what would have to be set in sudden rules to allow this to 
succeed?

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

Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not start

[Yedidyah Bar David]

On Thu, Dec 17, 2015 at 2:50 PM, Willard Dennis  wrote:
> This is from /var/log/messages —
>
> Dec 17 07:46:25 ovirt-node-01 systemd: vdsmd.service holdoff time over, 
> scheduling restart.
> Dec 17 07:46:35 ovirt-node-01 systemd: mom-vdsm.service stopping timed out. 
> Killing.
> Dec 17 07:46:35 ovirt-node-01 systemd: mom-vdsm.service: main process exited, 
> code=killed, status=9/KILL
> Dec 17 07:46:35 ovirt-node-01 systemd: Unit mom-vdsm.service entered failed 
> state.
> Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running mkdirs
> Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
> configure_coredump
> Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
> configure_vdsm_logs
> Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
> wait_for_network
> Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
> run_init_hooks
> Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
> upgraded_version_check
> Dec 17 07:46:35 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
> check_is_configured
> Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: Current revision of 
> multipath.conf detected, preserving
> Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: libvirt is already 
> configured for vdsm
> Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
> validate_configuration
> Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: SUCCESS: ssl configured 
> to true. No conflicts
> Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
> prepare_transient_repository
> Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
> syslog_available
> Dec 17 07:46:36 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running nwfilter
> Dec 17 07:46:37 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running dummybr
> Dec 17 07:46:37 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running tune_system
> Dec 17 07:46:37 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running test_space
> Dec 17 07:46:37 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running test_lo
> Dec 17 07:46:37 ovirt-node-01 vdsm: vdsm user could not manage to run sudo 
> operation: (stderr: ['sudo: sorry, you must have a tty to run sudo']). Verify 
> sudoer rules configuration
> Dec 17 07:46:37 ovirt-node-01 systemd: vdsmd.service: main process exited, 
> code=exited, status=1/FAILURE
> Dec 17 07:46:37 ovirt-node-01 vdsmd_init_common.sh: vdsm: Running 
> run_final_hooks
> Dec 17 07:46:37 ovirt-node-01 systemd: Unit vdsmd.service entered failed 
> state.
> Dec 17 07:46:37 ovirt-node-01 systemd: vdsmd.service holdoff time over, 
> scheduling restart.
>
>
> So, the message "vdsm user could not manage to run sudo operation: (stderr: 
> ['sudo: sorry, you must have a tty to run sudo']). Verify sudoer rules 
> configuration” — what would have to be set in sudden rules to allow this to 
> succeed?

I thought this was already discussed some messages ago.

No idea, but you should check your sudo (and perhaps related? e.g. pam
or whatever)
conf. vdsm ships /etc/sudoers.d/50_vdsm which normally works.
If you changed it, or have some other conflicting configuration,
this might break it.

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

Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not start

[Willard Dennis]

I checked and we do have a custom /etc/sudoers set —


[root@ovirt-node-01 vdsm]# cat /etc/sudoers
#
# NECLA custom /etc/sudoers
#
# *** Managed by Ansible; do not edit manually,
# file will be rewritten on next Ansible run! ***
#
# Do NOT add sudoers directly to this file; add them to the "wheel" group in 
/etc/group
#

Defaultsrequiretty
Defaults   !visiblepw
Defaultsalways_set_home
Defaultsenv_reset
Defaultsenv_keep =  "COLORS DISPLAY HOSTNAME HISTSIZE INPUTRC KDEDIR 
LS_COLORS"
Defaultsenv_keep += "MAIL PS1 PS2 QTDIR USERNAME LANG LC_ADDRESS LC_CTYPE"
Defaultsenv_keep += "LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT 
LC_MESSAGES"
Defaultsenv_keep += "LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE"
Defaultsenv_keep += "LC_TIME LC_ALL LANGUAGE LINGUAS _XKB_CHARSET 
XAUTHORITY"
Defaultssecure_path = /sbin:/bin:/usr/sbin:/usr/bin
rootALL=(ALL)   ALL
%wheel  ALL=(ALL)   ALL


What is missing / needs to be changed here to allow vdsmd to start correctly?


> On Dec 17, 2015, at 7:54 AM, Yedidyah Bar David  wrote:
> 
> I thought this was already discussed some messages ago.
> 
> No idea, but you should check your sudo (and perhaps related? e.g. pam
> or whatever)
> conf. vdsm ships /etc/sudoers.d/50_vdsm which normally works.
> If you changed it, or have some other conflicting configuration,
> this might break it.
> 
> -- 
> Didi

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

Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not start

[Willard Dennis]

Took the easy way out on selinux…

[root@ovirt-node-01 vdsm]# sestatus
SELinux status: disabled


> On Dec 17, 2015, at 7:48 AM, Yedidyah Bar David  wrote:
> 
> 
> Perhaps just upload all of them somewhere?
> 
> Also might be selinux? Please check/post also audit logs.

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

Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not start

[Yedidyah Bar David]

On Thu, Dec 17, 2015 at 2:53 PM, Willard Dennis  wrote:
> Took the easy way out on selinux…
>
> [root@ovirt-node-01 vdsm]# sestatus
> SELinux status: disabled

Up to you, but note that we do work hard to make sure things work
with it enabled.

>
>
> On Dec 17, 2015, at 7:48 AM, Yedidyah Bar David  wrote:
>
>
> Perhaps just upload all of them somewhere?
>
> Also might be selinux? Please check/post also audit logs.
>
>



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

Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not start (RESOLVED)

[Will Dennis]

The vdsmd startup failing problem is now resolved :) The root cause was that 
the /etc/sudoers file (that we maintain a customized version of which thru 
Ansible) was missing the "#includedir /etc/sudoers.d" stanza, which caused a 
sudo problem with the vdsmd startup, since the sudoers include file "50-vdsm" 
wasn't being parsed.

In going back and reviewing the thread, this was the first post that pointed 
out the real problem...

-Original Message-
From: Fabian Deutsch [mailto:fdeutsch at redhat.com] 
Sent: Tuesday, December 01, 2015 12:58 AM
To: Will Dennis
Cc: Simone Tiraboschi; users
Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not 
start

On Tue, Dec 1, 2015 at 4:52 AM, Will Dennis  wrote:
> Any clues out of the strace of vdsm?

read(9, "sudo: a password is required\n", 4096) = 29

Could it be that sudo is not configured to operate passwordless?

The strat-up can then fail, because sudo requires a ty, but this isn't 
available during service start.

- fabian

> On Nov 25, 2015, at 11:29 AM, Simone Tiraboschi  
> wrote:
> 
>> On Wed, Nov 25, 2015 at 5:22 PM, Willard Dennis  
>> wrote:
>> [root at ovirt-node-01 ~]# sudo -u vdsm /bin/bash
>> bash-4.2$ /usr/share/vdsm/vdsm
>> bash-4.2$ echo $?
>> 1
> 
> Can you please use strace on it?

-Message End-

However, not knowing about the missing sudoers include file, we continued to 
chase a vdsm config problem (uninstall / reinstall vdsm RPM pkgs, & use 
"vdsm-tool configure --force")

Shame on me, it looks like I didn't think to check /var/log/messages for 
"vdsm"-string entries until today, where we found the "vdsm user could not 
manage to run sudo operation: (stderr: ['sudo: sorry, you must have a tty to 
run sudo']). Verify sudoer rules configuration” message that ultimately led to 
the solution :(

However, not sure if it's possible to do so, but could /usr/share/vdsm/vdsm be 
made to emit a error to STDERR if it cannot run correctly? That's the only 
thing I could think of that may have helped me to resolve this earlier with 
what I did do...

Thanks for everyone's kind assistance, this really is a great community! :)

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

[ovirt-users] network configuration oVirt 3.5

[Kristof VAN DEN EYNDEN]

Hello everyone,

After trying to install oVirt 3.6 on CentOs which was a lot of pain, I ended up 
installing 3.5 without hassle.

BUT Now I'm trying to configure the network for my first cluster host but I'm 
having troubles doing so.

The server has 4 network ports,
Eth0 = Virtual management network, 172.16 range, only used for oVirt / KVM
Eth1 = Local network where the Guest should be accessible range 11.x
Eth2/3 unused..

Initially, no network is assigned, but I feel eth0 should be linked to 
ovirtmgmt I automatically using it's IP that is assigned?

When I assign ovirtmgmt to eth0 and set the IP to the corresponding IP it 
already has for that host and the local network to eth1 the host loses 
connection (until it resets it's connections...)
->not assigning an IP is no option as I can only select static /dhcp for 
ovirtmgmt


[cid:image004.jpg@01D138E8.A8BEF4F0]






Met vriendelijke groeten
Kristof VAN DEN EYNDEN
ICT Consulent
Dienst ICT
T. + 32 58 53 31 03 | G. +32 497 45 59 86

kristof.vandeneyn...@politiewestkust.be
[cid:image005.png@01D138E8.A8BEF4F0]

Pz Westkust
Zeelaan 48
8670 Koksijde
http://www.politiewestkust.be

P Please consider the environment before printing this e-mail.
Disclaimer

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

[ovirt-users] Hosted engine setup using Gluster - what is proper param's for the storage domain names?

[Willard Dennis]

Hi all,

Doing the hosted engine setup on Gluster; am at the point of configuring the 
storage domain / datacenter names, and not sure of what my best move is here… 
Here’s what I’m seeing:

——
  --== STORAGE CONFIGURATION ==--

  During customization use CTRL-D to abort.
  Please specify the storage you would like to use (glusterfs, iscsi, 
fc, nfs3, nfs4)[nfs3]: glusterfs
[ INFO  ] Please note that Replica 3 support is required for the shared storage.
  Please specify the full shared storage connection path to use 
(example: host:/path): localhost:/engine
[WARNING] Due to several bugs in mount.glusterfs the validation of GlusterFS 
share cannot be reliable.
[ INFO  ] GlusterFS replica 3 Volume detected
[ INFO  ] Installing on first host
  Please provide storage domain name. [hosted_storage]:
  Local storage datacenter name is an internal name
  and currently will not be shown in engine's admin UI.
  Please enter local datacenter name [hosted_datacenter]:
——

Concerned about the "Local storage datacenter name is an internal name and 
currently will not be shown in engine's admin UI” message… I want to use a 
second distributed Gluster volume (name = “vmdata”) for VM storage if I can, 
and don’t want to mess up the install… What should I consider when setting 
names for the storage domain name and local datacenter names?

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

Re: [ovirt-users] Network instability after upgrade 3.6.0 -> 3.6.1

[Stefano Danzi]

I partially solve the problem.

My host machine has 2 network interfaces with a bond. The bond was 
configured with  mode=4 (802.3ad) and switch was configured in the same way.
If I remove one network cable the network become stable. With both 
cables attached the network is instable.


I removed the link aggregation configuration from switch and change the 
bond in mode=2 (balance-xor). Now the network are stable.
The strange thing is that previous configuration worked fine for one 
year... since the last upgrade.


Now ha-agent don't reboot the hosted-engine anymore, but I receive two 
emails from brocker evere 2/5 minutes.
First a mail with "ovirt-hosted-engine state transition 
StartState-ReinitializeFSM" and after "ovirt-hosted-engine state 
transition ReinitializeFSM-EngineStarting"



Il 17/12/2015 10.51, Stefano Danzi ha scritto:

Hello,
I have one testing host (only one host) with self hosted engine and 2 
VM (one linux and one windows).


After upgrade ovirt from 3.6.0 to 3.6.1 the network connection works 
discontinuously.
Every 10 minutes HA agent restart hosted engine VM because result 
down. But the machine is UP,

only the network stop to work for some minutes.
I activate global maintenace mode to prevent engine reboot. If I ssh 
to the hosted engine sometimes
the connection work and sometimes no.  Using VNC connection to engine 
I see that sometime VM reach external network

and sometimes no.
If I do a tcpdump on phisical ethernet interface I don't see any 
packet when network on vm don't work.


Same thing happens fo others two VM.

Before the upgrade I never had network problems.
___
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] No hosted engine SD after upgrading to 3.6.1 RC4 from 3.6.0

[Justin Foreman]

Hello,

The Hosted Engine import did not work upon upgrading from 3.6.0 to 3.6.1 RC4. I 
had upgraded in an attempt to import the Hosted Engine storage domain and VM. 
Here’s my setup:

* 2x Dell R630s with SAS HBAs
* 1x Dell Compellent SAS SAN 
* Each R630 is connected to the SAS SAN via the SAS HBAs. 
* Storage domains are attached as FC (even though they’re SAS)
* Hosted-engine deployed from 3.6.0 using image in yum repo

Packages installed on engine:
ovirt-engine-setup-plugin-websocket-proxy-3.6.1.3-1.el7.centos.noarch
ovirt-engine-restapi-3.6.1.3-1.el7.centos.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-3.6.1.3-1.el7.centos.noarch
ovirt-engine-sdk-python-3.6.0.3-1.el7.centos.noarch
ovirt-engine-webadmin-portal-3.6.1.3-1.el7.centos.noarch
ovirt-engine-extension-aaa-ldap-setup-1.1.2-1.el7.centos.noarch
ovirt-image-uploader-3.6.0-1.el7.centos.noarch
ovirt-engine-extension-aaa-jdbc-1.0.4-1.el7.noarch
ovirt-release36-002-2.noarch
ovirt-engine-websocket-proxy-3.6.1.3-1.el7.centos.noarch
ovirt-engine-wildfly-overlay-8.0.4-1.el7.noarch
ovirt-engine-tools-3.6.1.3-1.el7.centos.noarch
ovirt-engine-extensions-api-impl-3.6.1.3-1.el7.centos.noarch
ovirt-vmconsole-1.0.0-1.el7.centos.noarch
ebay-cors-filter-1.0.1-0.1.ovirt.el7.noarch
ovirt-guest-agent-common-1.0.11-1.el7.noarch
ovirt-engine-wildfly-8.2.1-1.el7.x86_64
ovirt-engine-backend-3.6.1.3-1.el7.centos.noarch
ovirt-engine-setup-base-3.6.1.3-1.el7.centos.noarch
ovirt-engine-setup-plugin-vmconsole-proxy-helper-3.6.1.3-1.el7.centos.noarch
ovirt-engine-vmconsole-proxy-helper-3.6.1.3-1.el7.centos.noarch
ovirt-engine-cli-3.6.0.2-1.el7.centos.noarch
ovirt-engine-setup-3.6.1.3-1.el7.centos.noarch
ovirt-engine-dbscripts-3.6.1.3-1.el7.centos.noarch
ovirt-engine-extension-aaa-ldap-1.1.2-1.el7.centos.noarch
ovirt-iso-uploader-3.6.0-1.el7.centos.noarch
ovirt-engine-3.6.1.3-1.el7.centos.noarch
ovirt-vmconsole-proxy-1.0.0-1.el7.centos.noarch
ovirt-engine-setup-plugin-ovirt-engine-3.6.1.3-1.el7.centos.noarch
ovirt-host-deploy-java-1.4.1-1.el7.centos.noarch
ovirt-engine-lib-3.6.1.3-1.el7.centos.noarch
ovirt-engine-userportal-3.6.1.3-1.el7.centos.noarch
ovirt-host-deploy-1.4.1-1.el7.centos.noarch

I found this in engine.log. Please let me know what additional details I can 
provide.

2015-12-16 05:25:33,149 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVDSCommand] 
(DefaultQuartzScheduler_Worker-12) [fa1efd1] START, FullListVDSCommand(HostName 
= , FullListVDSCommandParameters:{runAsync='true', 
hostId='2fe6c27b-9346-4678-8cd3-c9d367ec447f', 
vds='Host[,2fe6c27b-9346-4678-8cd3-c9d367ec447f]', 
vmIds='[347620e8-79f1-4672-851d-2ad6103c0854]'}), log id: 7759b45b
2015-12-16 05:25:34,155 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVDSCommand] 
(DefaultQuartzScheduler_Worker-12) [fa1efd1] FINISH, FullListVDSCommand, 
return: [{status=Up, nicModel=rtl8139,pv, emulatedMachine=pc, 
guestDiskMapping={67805d76-66e4-4256-8={name=/dev/vda}, 
QEMU_DVD-ROM={name=/dev/sr0}}, vmId=347620e8-79f1-4672-851d-2ad6103c0854, 
pid=6377, devices=[Ljava.lang.Object;@76b3df47, smp=4, vmType=kvm, displayIp=0, 
display=vnc, displaySecurePort=-1, memSize=8192, displayPort=5900, 
cpuType=SandyBridge, 
spiceSecureChannels=smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir,
 statusTime=4298688650, vmName=HostedEngine, clientIp=, pauseCode=NOERR}], log 
id: 7759b45b
2015-12-16 05:25:34,162 INFO  
[org.ovirt.engine.core.bll.storage.GetExistingStorageDomainListQuery] 
(org.ovirt.thread.pool-8-thread-40) [1b9a02d1] START, 
GetExistingStorageDomainListQuery(GetExistingStorageDomainListParameters:{refresh='true',
 filtered='false'}), log id: d197cac
2015-12-16 05:25:34,163 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainsListVDSCommand] 
(org.ovirt.thread.pool-8-thread-40) [1b9a02d1] START, 
HSMGetStorageDomainsListVDSCommand(HostName = ov-101, 
HSMGetStorageDomainsListVDSCommandParameters:{runAsync='true', 
hostId='2fe6c27b-9346-4678-8cd3-c9d367ec447f', 
storagePoolId='----', storageType='null', 
storageDomainType='Data', path='null'}), log id: 7bc578c4
2015-12-16 05:25:35,422 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainsListVDSCommand] 
(org.ovirt.thread.pool-8-thread-40) [1b9a02d1] FINISH, 
HSMGetStorageDomainsListVDSCommand, return: 
[8c1981b2-ac04-433d-80f4-6cfd9023f935, 1fb79d91-b245-4447-91e0-e57671152a8c], 
log id: 7bc578c4
2015-12-16 05:25:35,431 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainInfoVDSCommand] 
(org.ovirt.thread.pool-8-thread-40) [1b9a02d1] START, 
HSMGetStorageDomainInfoVDSCommand(HostName = ov-101, 
HSMGetStorageDomainInfoVDSCommandParameters:{runAsync='true', 
hostId='2fe6c27b-9346-4678-8cd3-c9d367ec447f', 
storageDomainId='8c1981b2-ac04-433d-80f4-6cfd9023f935'}), log id: f35ad27
2015-12-16 05:25:37,622 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainInfoVDSCommand] 
(org.ovirt.thread.pool-8-thread-40) [1b9a02d1] 

[ovirt-users] ovirt-ha-broker issue after upgrade CentOS 7.1 => 7.2 and oVirt 3.6.0 => 3.6.1

[Bello Florent]

 

Hi, 

I upgrade my 3 servers to CentOS 7.2 and oVirt 3.6.1, the
oVirt engine works fine and my first host upgraded too. However, my
second and third host have a ovirt-ha-broker issue and is doesn't
start.
When i try to start the broker service, it failed with timeout.


Here my logs of my second upgraded server : 

[root@ovirt01 ~]#
systemctl status ovirt-ha-broker
● ovirt-ha-broker.service - oVirt
Hosted Engine High Availability Communications Broker
 Loaded: loaded
(/usr/lib/systemd/system/ovirt-ha-broker.service; enabled; vendor
preset: disabled)
 Active: activating (start) since jeu. 2015-12-17
17:41:46 GFT; 1min 3s ago
 Process: 15245
ExecStart=/usr/lib/systemd/systemd-ovirt-ha-broker start (code=exited,
status=0/SUCCESS)
 CGroup: /system.slice/ovirt-ha-broker.service

└─15259 /usr/bin/python
/usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker

déc. 17 17:41:46
ovirt01 systemd[1]: Starting oVirt Hosted Engine High Availability
Communications Broker...
déc. 17 17:41:46 ovirt01 systemd[1]: PID 15252
read from file /run/ovirt-hosted-engine-ha/broker.pid does not exist or
is a zombie. 

[root@ovirt01 ~]# systemctl start ovirt-ha-broker
Job for
ovirt-ha-broker.service failed because a timeout was exceeded. See
"systemctl status ovirt-ha-broker.service" and "journalctl -xe" for
details. 

[root@ovirt01 ~]# tail -f
/var/log/ovirt-hosted-engine-ha/broker.log
MainThread::INFO::2015-12-17
17:44:28,562::broker::57::ovirt_hosted_engine_ha.broker.broker.Broker::(run)
ovirt-hosted-engine-ha broker 1.3.3.4
started
MainThread::INFO::2015-12-17
17:44:28,588::monitor::40::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Searching for submonitors in
/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/submonitors
MainThread::INFO::2015-12-17
17:44:28,588::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor cpu-load
MainThread::INFO::2015-12-17
17:44:28,590::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor cpu-load-no-engine
MainThread::INFO::2015-12-17
17:44:28,591::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor engine-health
MainThread::INFO::2015-12-17
17:44:28,591::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor mem-free
MainThread::INFO::2015-12-17
17:44:28,591::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor mem-load
MainThread::INFO::2015-12-17
17:44:28,591::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor mgmt-bridge
MainThread::INFO::2015-12-17
17:44:28,592::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor ping
MainThread::INFO::2015-12-17
17:44:28,592::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor cpu-load
MainThread::INFO::2015-12-17
17:44:28,593::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor cpu-load-no-engine
MainThread::INFO::2015-12-17
17:44:28,593::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor engine-health
MainThread::INFO::2015-12-17
17:44:28,593::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor mem-free
MainThread::INFO::2015-12-17
17:44:28,594::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor mem-load
MainThread::INFO::2015-12-17
17:44:28,594::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor mgmt-bridge
MainThread::INFO::2015-12-17
17:44:28,594::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Loaded submonitor ping
MainThread::INFO::2015-12-17
17:44:28,594::monitor::50::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
Finished loading submonitors
MainThread::INFO::2015-12-17
17:44:28,595::listener::41::ovirt_hosted_engine_ha.broker.listener.Listener::(__init__)
Initializing SocketServer
MainThread::INFO::2015-12-17
17:44:28,595::listener::56::ovirt_hosted_engine_ha.broker.listener.Listener::(__init__)
SocketServer ready
MainThread::INFO::2015-12-17
17:45:59,215::broker::114::ovirt_hosted_engine_ha.broker.broker.Broker::(run)
Server shutting down 

[root@ovirt01 ~]# tail -f
/var/log/vdsm/vdsm.log
Reactor thread::INFO::2015-12-17
17:48:19,800::protocoldetector::72::ProtocolDetector.AcceptorImpl::(handle_accept)
Accepting connection from 127.0.0.1:44498
Reactor
thread::DEBUG::2015-12-17
17:48:19,808::protocoldetector::82::ProtocolDetector.Detector::(__init__)
Using required_size=11
Reactor thread::INFO::2015-12-17
17:48:19,808::protocoldetector::118::ProtocolDetector.Detector::(handle_read)
Detected protocol xml from 

Re: [ovirt-users] No hosted engine SD after upgrading to 3.6.1 RC4 from 3.6.0

[Simone Tiraboschi]

On Thu, Dec 17, 2015 at 7:55 PM, Justin Foreman 
wrote:

> Hello,
>
> The Hosted Engine import did not work upon upgrading from 3.6.0 to 3.6.1
> RC4. I had upgraded in an attempt to import the Hosted Engine storage
> domain and VM. Here’s my setup:
>

Hello Justin,
we have an open bug on that:
https://bugzilla.redhat.com/show_bug.cgi?id=1291634
It's specific to FC.
The solving patch will be in the next build.


>
> * 2x Dell R630s with SAS HBAs
> * 1x Dell Compellent SAS SAN
> * Each R630 is connected to the SAS SAN via the SAS HBAs.
> * Storage domains are attached as FC (even though they’re SAS)
> * Hosted-engine deployed from 3.6.0 using image in yum repo
>
> Packages installed on engine:
> ovirt-engine-setup-plugin-websocket-proxy-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-restapi-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-setup-plugin-ovirt-engine-common-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-sdk-python-3.6.0.3-1.el7.centos.noarch
> ovirt-engine-webadmin-portal-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-extension-aaa-ldap-setup-1.1.2-1.el7.centos.noarch
> ovirt-image-uploader-3.6.0-1.el7.centos.noarch
> ovirt-engine-extension-aaa-jdbc-1.0.4-1.el7.noarch
> ovirt-release36-002-2.noarch
> ovirt-engine-websocket-proxy-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-wildfly-overlay-8.0.4-1.el7.noarch
> ovirt-engine-tools-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-extensions-api-impl-3.6.1.3-1.el7.centos.noarch
> ovirt-vmconsole-1.0.0-1.el7.centos.noarch
> ebay-cors-filter-1.0.1-0.1.ovirt.el7.noarch
> ovirt-guest-agent-common-1.0.11-1.el7.noarch
> ovirt-engine-wildfly-8.2.1-1.el7.x86_64
> ovirt-engine-backend-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-setup-base-3.6.1.3-1.el7.centos.noarch
>
> ovirt-engine-setup-plugin-vmconsole-proxy-helper-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-vmconsole-proxy-helper-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-cli-3.6.0.2-1.el7.centos.noarch
> ovirt-engine-setup-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-dbscripts-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-extension-aaa-ldap-1.1.2-1.el7.centos.noarch
> ovirt-iso-uploader-3.6.0-1.el7.centos.noarch
> ovirt-engine-3.6.1.3-1.el7.centos.noarch
> ovirt-vmconsole-proxy-1.0.0-1.el7.centos.noarch
> ovirt-engine-setup-plugin-ovirt-engine-3.6.1.3-1.el7.centos.noarch
> ovirt-host-deploy-java-1.4.1-1.el7.centos.noarch
> ovirt-engine-lib-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-userportal-3.6.1.3-1.el7.centos.noarch
> ovirt-host-deploy-1.4.1-1.el7.centos.noarch
>
> I found this in engine.log. Please let me know what additional details I
> can provide.
>
> 2015-12-16 05:25:33,149 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVDSCommand]
> (DefaultQuartzScheduler_Worker-12) [fa1efd1] START,
> FullListVDSCommand(HostName = ,
> FullListVDSCommandParameters:{runAsync='true',
> hostId='2fe6c27b-9346-4678-8cd3-c9d367ec447f',
> vds='Host[,2fe6c27b-9346-4678-8cd3-c9d367ec447f]',
> vmIds='[347620e8-79f1-4672-851d-2ad6103c0854]'}), log id: 7759b45b
> 2015-12-16 05:25:34,155 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVDSCommand]
> (DefaultQuartzScheduler_Worker-12) [fa1efd1] FINISH, FullListVDSCommand,
> return: [{status=Up, nicModel=rtl8139,pv, emulatedMachine=pc,
> guestDiskMapping={67805d76-66e4-4256-8={name=/dev/vda},
> QEMU_DVD-ROM={name=/dev/sr0}}, vmId=347620e8-79f1-4672-851d-2ad6103c0854,
> pid=6377, devices=[Ljava.lang.Object;@76b3df47, smp=4, vmType=kvm,
> displayIp=0, display=vnc, displaySecurePort=-1, memSize=8192,
> displayPort=5900, cpuType=SandyBridge,
> spiceSecureChannels=smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir,
> statusTime=4298688650, vmName=HostedEngine, clientIp=, pauseCode=NOERR}],
> log id: 7759b45b
> 2015-12-16 05:25:34,162 INFO
> [org.ovirt.engine.core.bll.storage.GetExistingStorageDomainListQuery]
> (org.ovirt.thread.pool-8-thread-40) [1b9a02d1] START,
> GetExistingStorageDomainListQuery(GetExistingStorageDomainListParameters:{refresh='true',
> filtered='false'}), log id: d197cac
> 2015-12-16 05:25:34,163 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainsListVDSCommand]
> (org.ovirt.thread.pool-8-thread-40) [1b9a02d1] START,
> HSMGetStorageDomainsListVDSCommand(HostName = ov-101,
> HSMGetStorageDomainsListVDSCommandParameters:{runAsync='true',
> hostId='2fe6c27b-9346-4678-8cd3-c9d367ec447f',
> storagePoolId='----', storageType='null',
> storageDomainType='Data', path='null'}), log id: 7bc578c4
> 2015-12-16 05:25:35,422 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainsListVDSCommand]
> (org.ovirt.thread.pool-8-thread-40) [1b9a02d1] FINISH,
> HSMGetStorageDomainsListVDSCommand, return:
> [8c1981b2-ac04-433d-80f4-6cfd9023f935,
> 1fb79d91-b245-4447-91e0-e57671152a8c], log id: 7bc578c4
> 2015-12-16 05:25:35,431 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainInfoVDSCommand]
> (org.ovirt.thread.pool-8-thread-40) [1b9a02d1] START,
> 

Re: [ovirt-users] No hosted engine SD after upgrading to 3.6.1 RC4 from 3.6.0

[Justin Foreman]

Thanks, Simone!

> On Dec 17, 2015, at 4:33 PM, Simone Tiraboschi  wrote:
> 
> 
> 
> On Thu, Dec 17, 2015 at 7:55 PM, Justin Foreman  
> wrote:
> Hello,
> 
> The Hosted Engine import did not work upon upgrading from 3.6.0 to 3.6.1 RC4. 
> I had upgraded in an attempt to import the Hosted Engine storage domain and 
> VM. Here’s my setup:
> 
> Hello Justin,
> we have an open bug on that:
> https://bugzilla.redhat.com/show_bug.cgi?id=1291634
> It's specific to FC.
> The solving patch will be in the next build.
>  
> 
> * 2x Dell R630s with SAS HBAs
> * 1x Dell Compellent SAS SAN
> * Each R630 is connected to the SAS SAN via the SAS HBAs.
> * Storage domains are attached as FC (even though they’re SAS)
> * Hosted-engine deployed from 3.6.0 using image in yum repo
> 
> Packages installed on engine:
> ovirt-engine-setup-plugin-websocket-proxy-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-restapi-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-setup-plugin-ovirt-engine-common-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-sdk-python-3.6.0.3-1.el7.centos.noarch
> ovirt-engine-webadmin-portal-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-extension-aaa-ldap-setup-1.1.2-1.el7.centos.noarch
> ovirt-image-uploader-3.6.0-1.el7.centos.noarch
> ovirt-engine-extension-aaa-jdbc-1.0.4-1.el7.noarch
> ovirt-release36-002-2.noarch
> ovirt-engine-websocket-proxy-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-wildfly-overlay-8.0.4-1.el7.noarch
> ovirt-engine-tools-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-extensions-api-impl-3.6.1.3-1.el7.centos.noarch
> ovirt-vmconsole-1.0.0-1.el7.centos.noarch
> ebay-cors-filter-1.0.1-0.1.ovirt.el7.noarch
> ovirt-guest-agent-common-1.0.11-1.el7.noarch
> ovirt-engine-wildfly-8.2.1-1.el7.x86_64
> ovirt-engine-backend-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-setup-base-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-setup-plugin-vmconsole-proxy-helper-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-vmconsole-proxy-helper-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-cli-3.6.0.2-1.el7.centos.noarch
> ovirt-engine-setup-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-dbscripts-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-extension-aaa-ldap-1.1.2-1.el7.centos.noarch
> ovirt-iso-uploader-3.6.0-1.el7.centos.noarch
> ovirt-engine-3.6.1.3-1.el7.centos.noarch
> ovirt-vmconsole-proxy-1.0.0-1.el7.centos.noarch
> ovirt-engine-setup-plugin-ovirt-engine-3.6.1.3-1.el7.centos.noarch
> ovirt-host-deploy-java-1.4.1-1.el7.centos.noarch
> ovirt-engine-lib-3.6.1.3-1.el7.centos.noarch
> ovirt-engine-userportal-3.6.1.3-1.el7.centos.noarch
> ovirt-host-deploy-1.4.1-1.el7.centos.noarch
> 
> I found this in engine.log. Please let me know what additional details I can 
> provide.
> 
> 2015-12-16 05:25:33,149 INFO  
> [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVDSCommand] 
> (DefaultQuartzScheduler_Worker-12) [fa1efd1] START, 
> FullListVDSCommand(HostName = , 
> FullListVDSCommandParameters:{runAsync='true', 
> hostId='2fe6c27b-9346-4678-8cd3-c9d367ec447f', 
> vds='Host[,2fe6c27b-9346-4678-8cd3-c9d367ec447f]', 
> vmIds='[347620e8-79f1-4672-851d-2ad6103c0854]'}), log id: 7759b45b
> 2015-12-16 05:25:34,155 INFO  
> [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVDSCommand] 
> (DefaultQuartzScheduler_Worker-12) [fa1efd1] FINISH, FullListVDSCommand, 
> return: [{status=Up, nicModel=rtl8139,pv, emulatedMachine=pc, 
> guestDiskMapping={67805d76-66e4-4256-8={name=/dev/vda}, 
> QEMU_DVD-ROM={name=/dev/sr0}}, vmId=347620e8-79f1-4672-851d-2ad6103c0854, 
> pid=6377, devices=[Ljava.lang.Object;@76b3df47, smp=4, vmType=kvm, 
> displayIp=0, display=vnc, displaySecurePort=-1, memSize=8192, 
> displayPort=5900, cpuType=SandyBridge, 
> spiceSecureChannels=smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir,
>  statusTime=4298688650, vmName=HostedEngine, clientIp=, pauseCode=NOERR}], 
> log id: 7759b45b
> 2015-12-16 05:25:34,162 INFO  
> [org.ovirt.engine.core.bll.storage.GetExistingStorageDomainListQuery] 
> (org.ovirt.thread.pool-8-thread-40) [1b9a02d1] START, 
> GetExistingStorageDomainListQuery(GetExistingStorageDomainListParameters:{refresh='true',
>  filtered='false'}), log id: d197cac
> 2015-12-16 05:25:34,163 INFO  
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainsListVDSCommand]
>  (org.ovirt.thread.pool-8-thread-40) [1b9a02d1] START, 
> HSMGetStorageDomainsListVDSCommand(HostName = ov-101, 
> HSMGetStorageDomainsListVDSCommandParameters:{runAsync='true', 
> hostId='2fe6c27b-9346-4678-8cd3-c9d367ec447f', 
> storagePoolId='----', storageType='null', 
> storageDomainType='Data', path='null'}), log id: 7bc578c4
> 2015-12-16 05:25:35,422 INFO  
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainsListVDSCommand]
>  (org.ovirt.thread.pool-8-thread-40) [1b9a02d1] FINISH, 
> HSMGetStorageDomainsListVDSCommand, return: 
> [8c1981b2-ac04-433d-80f4-6cfd9023f935, 1fb79d91-b245-4447-91e0-e57671152a8c], 
> log id: 7bc578c4
> 2015-12-16 

Re: [ovirt-users] ovirt-ha-broker issue after upgrade CentOS 7.1 => 7.2 and oVirt 3.6.0 => 3.6.1

[Simone Tiraboschi]

On Thu, Dec 17, 2015 at 9:49 PM, Bello Florent <
florent.be...@ville-kourou.fr> wrote:

> Hi,
>
> I upgrade my 3 servers to CentOS 7.2 and oVirt 3.6.1, the oVirt engine
> works fine and my first host upgraded too. However, my second and third
> host have a ovirt-ha-broker issue and is doesn't start.
> When i try to start the broker service, it failed with timeout.
>
> Here my logs of my second upgraded server :
>
> [root@ovirt01 ~]# systemctl status  ovirt-ha-broker
> ● ovirt-ha-broker.service - oVirt Hosted Engine High Availability
> Communications Broker
>Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-broker.service;
> enabled; vendor preset: disabled)
>Active: activating (start) since jeu. 2015-12-17 17:41:46 GFT; 1min 3s
> ago
>   Process: 15245 ExecStart=/usr/lib/systemd/systemd-ovirt-ha-broker start
> (code=exited, status=0/SUCCESS)
>CGroup: /system.slice/ovirt-ha-broker.service
>└─15259 /usr/bin/python
> /usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker
>
> déc. 17 17:41:46 ovirt01 systemd[1]: Starting oVirt Hosted Engine High
> Availability Communications Broker...
> déc. 17 17:41:46 ovirt01 systemd[1]: PID 15252 read from file
> /run/ovirt-hosted-engine-ha/broker.pid does not exist or is a zombie.
>
>
>
> [root@ovirt01 ~]# systemctl start  ovirt-ha-broker
> Job for ovirt-ha-broker.service failed because a timeout was exceeded. See
> "systemctl status ovirt-ha-broker.service" and "journalctl -xe" for details.
>
>
>

Thanks for the report Florent,
just today I experimented it too: we are checking if it's related to this
last minute patch from this morning:
https://gerrit.ovirt.org/#/c/50662/

Adding Fabian and Martin.


> [root@ovirt01 ~]# tail -f /var/log/ovirt-hosted-engine-ha/broker.log
> MainThread::INFO::2015-12-17
> 17:44:28,562::broker::57::ovirt_hosted_engine_ha.broker.broker.Broker::(run)
> ovirt-hosted-engine-ha broker 1.3.3.4 started
> MainThread::INFO::2015-12-17
> 17:44:28,588::monitor::40::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Searching for submonitors in
> /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/submonitors
> MainThread::INFO::2015-12-17
> 17:44:28,588::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor cpu-load
> MainThread::INFO::2015-12-17
> 17:44:28,590::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor cpu-load-no-engine
> MainThread::INFO::2015-12-17
> 17:44:28,591::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor engine-health
> MainThread::INFO::2015-12-17
> 17:44:28,591::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor mem-free
> MainThread::INFO::2015-12-17
> 17:44:28,591::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor mem-load
> MainThread::INFO::2015-12-17
> 17:44:28,591::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor mgmt-bridge
> MainThread::INFO::2015-12-17
> 17:44:28,592::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor ping
> MainThread::INFO::2015-12-17
> 17:44:28,592::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor cpu-load
> MainThread::INFO::2015-12-17
> 17:44:28,593::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor cpu-load-no-engine
> MainThread::INFO::2015-12-17
> 17:44:28,593::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor engine-health
> MainThread::INFO::2015-12-17
> 17:44:28,593::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor mem-free
> MainThread::INFO::2015-12-17
> 17:44:28,594::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor mem-load
> MainThread::INFO::2015-12-17
> 17:44:28,594::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor mgmt-bridge
> MainThread::INFO::2015-12-17
> 17:44:28,594::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Loaded submonitor ping
> MainThread::INFO::2015-12-17
> 17:44:28,594::monitor::50::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors)
> Finished loading submonitors
> MainThread::INFO::2015-12-17
> 17:44:28,595::listener::41::ovirt_hosted_engine_ha.broker.listener.Listener::(__init__)
> Initializing SocketServer
> MainThread::INFO::2015-12-17
> 17:44:28,595::listener::56::ovirt_hosted_engine_ha.broker.listener.Listener::(__init__)
> SocketServer ready
> MainThread::INFO::2015-12-17
> 17:45:59,215::broker::114::ovirt_hosted_engine_ha.broker.broker.Broker::(run)
> Server shutting 

[ovirt-users] Disable HTTP Strict Transport Security?

[Blaster]

I've been having this problem for a while, but it's now impossible to 
get around as all my browsers have updated to prevent by passing HSTS.


I must be doing something wrong  as I don't see anyone else complaining 
about this in regards to Ovirt...


I'm running a Ovirt 3.5.4 All In One setup.  No matter what browser I 
use, I can no longer get to the GUI because it appears 3.5? started 
enforcing HTTP Strict Transport Security and since Ovirt uses self 
signed certs, the browsers are refusing to let me through.  It appears 
newer browsers no longer allow you to click through unsigned certs of 
HSTS is enabled.


What do I need to do to get around this?   What am I missing since no 
one else seems to be having this problem.


Thanks...

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

Re: [ovirt-users] ovirt-ha-broker issue after upgrade CentOS 7.1 => 7.2 and oVirt 3.6.0 => 3.6.1

[Matthew Trent]

(Sorry if this reply doesn't thread properly. Just subscribed to reply to this 
topic.)

I'm also experiencing this issue. Just upgraded to the latest packages and both 
ovirt-ha-agent and ovirt-ha-broker pause for a long time when being started, 
then timeout with errors.

[root@ovirt2 ~]# systemctl start ovirt-ha-broker
Job for ovirt-ha-broker.service failed because a timeout was exceeded. See 
"systemctl status ovirt-ha-broker.service" and "journalctl -xe" for details.
[root@ovirt2 ~]# systemctl start ovirt-ha-agent
Job for ovirt-ha-agent.service failed because a timeout was exceeded. See 
"systemctl status ovirt-ha-agent.service" and "journalctl -xe" for details.


Dec 17 15:27:53 ovirt2 systemd: Failed to start oVirt Hosted Engine High 
Availability Communications Broker.
Dec 17 15:27:53 ovirt2 systemd: Unit ovirt-ha-broker.service entered failed 
state.
Dec 17 15:27:53 ovirt2 systemd: ovirt-ha-broker.service failed.
Dec 17 15:27:53 ovirt2 systemd: ovirt-ha-broker.service holdoff time over, 
scheduling restart.
Dec 17 15:27:53 ovirt2 systemd: Starting oVirt Hosted Engine High Availability 
Communications Broker...
Dec 17 15:27:53 ovirt2 systemd-ovirt-ha-broker: Starting ovirt-ha-broker: [  OK 
 ]
Dec 17 15:27:53 ovirt2 systemd: PID 21125 read from file 
/run/ovirt-hosted-engine-ha/broker.pid does not exist or is a zombie.
Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service stop-final-sigterm timed 
out. Killing.
Dec 17 15:29:22 ovirt2 systemd: Failed to start oVirt Hosted Engine High 
Availability Monitoring Agent.
Dec 17 15:29:22 ovirt2 systemd: Unit ovirt-ha-agent.service entered failed 
state.
Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service failed.
Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service holdoff time over, 
scheduling restart.
Dec 17 15:29:23 ovirt2 systemd: ovirt-ha-broker.service start operation timed 
out. Terminating.
Dec 17 15:29:24 ovirt2 systemd: Failed to start oVirt Hosted Engine High 
Availability Communications Broker.
Dec 17 15:29:24 ovirt2 systemd: Unit ovirt-ha-broker.service entered failed 
state.
Dec 17 15:29:24 ovirt2 systemd: ovirt-ha-broker.service failed.
Dec 17 15:29:24 ovirt2 systemd: Starting oVirt Hosted Engine High Availability 
Monitoring Agent...
Dec 17 15:29:24 ovirt2 systemd-ovirt-ha-agent: Starting ovirt-ha-agent: [  OK  ]
Dec 17 15:29:24 ovirt2 systemd: PID 21288 read from file 
/run/ovirt-hosted-engine-ha/agent.pid does not exist or is a zombie.
Dec 17 15:29:24 ovirt2 systemd: ovirt-ha-broker.service holdoff time over, 
scheduling restart.
Dec 17 15:29:24 ovirt2 systemd: Starting oVirt Hosted Engine High Availability 
Communications Broker...
Dec 17 15:29:25 ovirt2 systemd-ovirt-ha-broker: Starting ovirt-ha-broker: [  OK 
 ]
Dec 17 15:29:25 ovirt2 systemd: PID 21304 read from file 
/run/ovirt-hosted-engine-ha/broker.pid does not exist or is a zombie.


--
Matthew Trent
Network Engineer
Lewis County IT Services
360.740.1247 - Helpdesk
360.740.3343 - Direct line
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not start

[Willard Dennis]

OK, should not have used the term “vanilla” I guess… I have customized the OS 
to fit into my environment (not so much with kickstart, mostly via Ansible) and 
of course have installed Gluster 3.7 and configured volumes for the engine and 
VM storage. So it’s not like it’s running on a completely stock CentOS 7 
install (that would be basically unusable for me…)

Doing a complete reinstall would be many hours of work (already have done that 
once to reconfigure Gluster) so not really interested in doing that…

I’d love to continue debugging; just frustrated that everything done so far has 
not worked (read thread for details…) and we cannot get the vdsmd service to 
run… I do very much appreciate the assistance of all the RHAT folks who have 
responded to this thread, you are my only hope of getting this stuff running, 
as I’m not an oVirt expert by far

-Will

> On Dec 17, 2015, at 1:40 AM, Yedidyah Bar David  wrote:
> 
> On Wed, Dec 16, 2015 at 11:52 PM, Willard Dennis  wrote:
>> Any thoughts on this issue?? This is holding up my project (oVirt hosted
>> engine install won’t proceed if VDSM service is not running…)  Why am I even
>> having such problems with the VDSM service? It’s on a vanilla CentOS 7
>> install…
> 
> (Only briefly skimming the history of this thread:)
> 
> If all you want is to have it up and running, I'd suggest reinstalling
> the OS and then try again. Quite likely you have there some local
> non-default configurations or something. If it still fails, I'd suggest
> to open a bug, describe exact flow, and attach all relevant logs. When
> you reinstall the OS, keep in mind that things like a custom kickstart
> file etc are also non-default configurations, so if you need them,
> attach them to the bug as well.
> 
> If you are aware of such non-default stuff but do need them, you
> basically have two choices:
> 1. Keep on debugging this til it works. We can try helping, but can't
> guess every change you did to your system. In particular, as Simone
> said before, sudo is configured to work out-of-the-box by default.
> 2. Try a clean vanilla OS install on another system and compare them
> to try and see what difference breaks. This can be done also on a VM
> with nested kvm, if you do not have a spare physical machine.
> 
> Best,
> -- 
> Didi

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

Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not start

[Yedidyah Bar David]

On Thu, Dec 17, 2015 at 9:51 AM, Fabian Deutsch  wrote:
> On Wed, Dec 16, 2015 at 10:52 PM, Willard Dennis  wrote:
>> Any thoughts on this issue?? This is holding up my project (oVirt hosted
>> engine install won’t proceed if VDSM service is not running…)  Why am I even
>> having such problems with the VDSM service? It’s on a vanilla CentOS 7
>> install…
>
> Hey,
>
> so it looks like vdsm has an issue, can you provide some logs?
>

Perhaps it's this one:

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

> - fabian
>
>> Thanks
>> Will
>>
>>
>> On Dec 2, 2015, at 10:35 AM, Will Dennis  wrote:
>>
>> Ran the configure the first time and got an error...
>>
>> root@ovirt-node-01 ~> vdsm-tool configure --force
>>
>> Checking configuration status...
>>
>> Current revision of multipath.conf detected, preserving
>> libvirt is not configured for vdsm yet
>> FAILED: conflicting vdsm and libvirt-qemu tls configuration.
>> vdsm.conf with ssl=True requires the following changes:
>> libvirtd.conf: listen_tcp=0, auth_tcp="sasl", listen_tls=1
>> qemu.conf: spice_tls=1.
>>
>> Running configure...
>> Reconfiguration of sebool is done.
>> Reconfiguration of passwd is done.
>> Reconfiguration of libvirt is done.
>>
>> Done configuring modules to VDSM.
>>
>> So, made the appropriate edits to libvirtd.conf and qemu.conf
>>
>> root@ovirt-node-01 ~> grep "^[a-z]" /etc/libvirt/libvirtd.conf
>> listen_tls = 1
>> listen_tcp = 0
>> auth_tcp = "sasl"
>> auth_unix_rw="sasl"
>> ca_file="/etc/pki/vdsm/certs/cacert.pem"
>> cert_file="/etc/pki/vdsm/certs/vdsmcert.pem"
>> host_uuid="2b026fff-bae2-429f-9386-c60ffc5f3f32"
>> keepalive_interval=-1
>> key_file="/etc/pki/vdsm/keys/vdsmkey.pem"
>> unix_sock_group="qemu"
>> unix_sock_rw_perms="0770"
>>
>> root@ovirt-node-01 ~> grep "^[a-z]" /etc/libvirt/qemu.conf
>> spice_tls = 1
>> auto_dump_path="/var/log/core"
>> dynamic_ownership=0
>> lock_manager="sanlock"
>> remote_display_port_max=6923
>> remote_display_port_min=5900
>> save_image_format="lzop"
>> spice_tls=1
>> spice_tls_x509_cert_dir="/etc/pki/vdsm/libvirt-spice"
>>
>> Then re-ran the config...
>>
>> root@ovirt-node-01 ~> vdsm-tool configure --force
>>
>> Checking configuration status...
>>
>> Current revision of multipath.conf detected, preserving
>> libvirt is already configured for vdsm
>> SUCCESS: ssl configured to true. No conflicts
>>
>> Running configure...
>> Reconfiguration of sebool is done.
>> Reconfiguration of libvirt is done.
>>
>> Done configuring modules to VDSM.
>>
>> Sadly, vdsmd STILL fails to start...
>>
>> root@ovirt-node-01 ~> systemctl restart vdsmd
>> root@ovirt-node-01 ~> systemctl status vdsmd
>> vdsmd.service - Virtual Desktop Server Manager
>>Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)
>>Active: activating (auto-restart) (Result: exit-code) since Wed
>> 2015-12-02 10:30:47 EST; 1s ago
>>   Process: 6522 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh
>> --post-stop (code=exited, status=0/SUCCESS)
>>   Process: 6506 ExecStart=/usr/share/vdsm/daemonAdapter -0 /dev/null -1
>> /dev/null -2 /dev/null /usr/share/vdsm/vdsm (code=exited, status=1/FAILURE)
>>   Process: 6433 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh
>> --pre-start (code=exited, status=0/SUCCESS)
>> Main PID: 6506 (code=exited, status=1/FAILURE)
>>
>> Dec 02 10:30:47 ovirt-node-01 systemd[1]: Unit vdsmd.service entered failed
>> 
>> Dec 02 10:30:47 ovirt-node-01 systemd[1]: vdsmd.service holdoff time over,
>> s
>> Hint: Some lines were ellipsized, use -l to show in full.
>>
>> :(
>>
>> From: Simone Tiraboschi [mailto:stira...@redhat.com]
>> Sent: Wednesday, December 02, 2015 3:57 AM
>> To: Will Dennis
>> Cc: Fabian Deutsch; users
>> Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not
>> start
>>
>> [snip]
>>
>> Now can you please now configure it with:
>>   vdsm-tool configure --force
>>
>> Then you have to restart it
>>
>>
>
>
>
> --
> Fabian Deutsch 
> RHEV Hypervisor
> Red Hat
> ___
> 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] ovirt-ha-broker issue after upgrade CentOS 7.1 => 7.2 and oVirt 3.6.0 => 3.6.1

[Matthew Trent]

Yes! That did it. All the errors are gone, and HA seems to be functioning 
normally. Thanks much!


--
Matthew Trent
Network Engineer
Lewis County IT Services
?

From: Simone Tiraboschi 
Sent: Thursday, December 17, 2015 4:50 PM
To: Matthew Trent
Cc: users@ovirt.org
Subject: Re: [ovirt-users] ovirt-ha-broker issue after upgrade CentOS 7.1 => 
7.2 and oVirt 3.6.0 => 3.6.1



On Fri, Dec 18, 2015 at 12:32 AM, Matthew Trent 
> wrote:
(Sorry if this reply doesn't thread properly. Just subscribed to reply to this 
topic.)

I'm also experiencing this issue. Just upgraded to the latest packages and both 
ovirt-ha-agent and ovirt-ha-broker pause for a long time when being started, 
then timeout with errors.

Please try manually reverting this patch https://gerrit.ovirt.org/#/c/50662/
by removing the lines that start with PIDFile= from
/usr/lib/systemd/system/ovirt-ha-broker.service and 
/usr/lib/systemd/system/ovirt-ha-agent.service
Then systemctl daemon-reload and restart the services



[root@ovirt2 ~]# systemctl start ovirt-ha-broker
Job for ovirt-ha-broker.service failed because a timeout was exceeded. See 
"systemctl status ovirt-ha-broker.service" and "journalctl -xe" for details.
[root@ovirt2 ~]# systemctl start ovirt-ha-agent
Job for ovirt-ha-agent.service failed because a timeout was exceeded. See 
"systemctl status ovirt-ha-agent.service" and "journalctl -xe" for details.


Dec 17 15:27:53 ovirt2 systemd: Failed to start oVirt Hosted Engine High 
Availability Communications Broker.
Dec 17 15:27:53 ovirt2 systemd: Unit ovirt-ha-broker.service entered failed 
state.
Dec 17 15:27:53 ovirt2 systemd: ovirt-ha-broker.service failed.
Dec 17 15:27:53 ovirt2 systemd: ovirt-ha-broker.service holdoff time over, 
scheduling restart.
Dec 17 15:27:53 ovirt2 systemd: Starting oVirt Hosted Engine High Availability 
Communications Broker...
Dec 17 15:27:53 ovirt2 systemd-ovirt-ha-broker: Starting ovirt-ha-broker: [  OK 
 ]
Dec 17 15:27:53 ovirt2 systemd: PID 21125 read from file 
/run/ovirt-hosted-engine-ha/broker.pid does not exist or is a zombie.
Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service stop-final-sigterm timed 
out. Killing.
Dec 17 15:29:22 ovirt2 systemd: Failed to start oVirt Hosted Engine High 
Availability Monitoring Agent.
Dec 17 15:29:22 ovirt2 systemd: Unit ovirt-ha-agent.service entered failed 
state.
Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service failed.
Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service holdoff time over, 
scheduling restart.
Dec 17 15:29:23 ovirt2 systemd: ovirt-ha-broker.service start operation timed 
out. Terminating.
Dec 17 15:29:24 ovirt2 systemd: Failed to start oVirt Hosted Engine High 
Availability Communications Broker.
Dec 17 15:29:24 ovirt2 systemd: Unit ovirt-ha-broker.service entered failed 
state.
Dec 17 15:29:24 ovirt2 systemd: ovirt-ha-broker.service failed.
Dec 17 15:29:24 ovirt2 systemd: Starting oVirt Hosted Engine High Availability 
Monitoring Agent...
Dec 17 15:29:24 ovirt2 systemd-ovirt-ha-agent: Starting ovirt-ha-agent: [  OK  ]
Dec 17 15:29:24 ovirt2 systemd: PID 21288 read from file 
/run/ovirt-hosted-engine-ha/agent.pid does not exist or is a zombie.
Dec 17 15:29:24 ovirt2 systemd: ovirt-ha-broker.service holdoff time over, 
scheduling restart.
Dec 17 15:29:24 ovirt2 systemd: Starting oVirt Hosted Engine High Availability 
Communications Broker...
Dec 17 15:29:25 ovirt2 systemd-ovirt-ha-broker: Starting ovirt-ha-broker: [  OK 
 ]
Dec 17 15:29:25 ovirt2 systemd: PID 21304 read from file 
/run/ovirt-hosted-engine-ha/broker.pid does not exist or is a zombie.


--
Matthew Trent
Network Engineer
Lewis County IT Services
360.740.1247 - Helpdesk
360.740.3343 - Direct line
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

Re: [ovirt-users] ovirt-ha-broker issue after upgrade CentOS 7.1 => 7.2 and oVirt 3.6.0 => 3.6.1

[Simone Tiraboschi]

On Fri, Dec 18, 2015 at 12:32 AM, Matthew Trent <
matthew.tr...@lewiscountywa.gov> wrote:

> (Sorry if this reply doesn't thread properly. Just subscribed to reply to
> this topic.)
>
> I'm also experiencing this issue. Just upgraded to the latest packages and
> both ovirt-ha-agent and ovirt-ha-broker pause for a long time when being
> started, then timeout with errors.
>

Please try manually reverting this patch https://gerrit.ovirt.org/#/c/50662/
by removing the lines that start with PIDFile= from
/usr/lib/systemd/system/ovirt-ha-broker.service and
/usr/lib/systemd/system/ovirt-ha-agent.service
Then systemctl daemon-reload and restart the services



>
> [root@ovirt2 ~]# systemctl start ovirt-ha-broker
> Job for ovirt-ha-broker.service failed because a timeout was exceeded. See
> "systemctl status ovirt-ha-broker.service" and "journalctl -xe" for details.
> [root@ovirt2 ~]# systemctl start ovirt-ha-agent
> Job for ovirt-ha-agent.service failed because a timeout was exceeded. See
> "systemctl status ovirt-ha-agent.service" and "journalctl -xe" for details.
>
>
> Dec 17 15:27:53 ovirt2 systemd: Failed to start oVirt Hosted Engine High
> Availability Communications Broker.
> Dec 17 15:27:53 ovirt2 systemd: Unit ovirt-ha-broker.service entered
> failed state.
> Dec 17 15:27:53 ovirt2 systemd: ovirt-ha-broker.service failed.
> Dec 17 15:27:53 ovirt2 systemd: ovirt-ha-broker.service holdoff time over,
> scheduling restart.
> Dec 17 15:27:53 ovirt2 systemd: Starting oVirt Hosted Engine High
> Availability Communications Broker...
> Dec 17 15:27:53 ovirt2 systemd-ovirt-ha-broker: Starting ovirt-ha-broker:
> [  OK  ]
> Dec 17 15:27:53 ovirt2 systemd: PID 21125 read from file
> /run/ovirt-hosted-engine-ha/broker.pid does not exist or is a zombie.
> Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service stop-final-sigterm
> timed out. Killing.
> Dec 17 15:29:22 ovirt2 systemd: Failed to start oVirt Hosted Engine High
> Availability Monitoring Agent.
> Dec 17 15:29:22 ovirt2 systemd: Unit ovirt-ha-agent.service entered failed
> state.
> Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service failed.
> Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service holdoff time over,
> scheduling restart.
> Dec 17 15:29:23 ovirt2 systemd: ovirt-ha-broker.service start operation
> timed out. Terminating.
> Dec 17 15:29:24 ovirt2 systemd: Failed to start oVirt Hosted Engine High
> Availability Communications Broker.
> Dec 17 15:29:24 ovirt2 systemd: Unit ovirt-ha-broker.service entered
> failed state.
> Dec 17 15:29:24 ovirt2 systemd: ovirt-ha-broker.service failed.
> Dec 17 15:29:24 ovirt2 systemd: Starting oVirt Hosted Engine High
> Availability Monitoring Agent...
> Dec 17 15:29:24 ovirt2 systemd-ovirt-ha-agent: Starting ovirt-ha-agent: [
> OK  ]
> Dec 17 15:29:24 ovirt2 systemd: PID 21288 read from file
> /run/ovirt-hosted-engine-ha/agent.pid does not exist or is a zombie.
> Dec 17 15:29:24 ovirt2 systemd: ovirt-ha-broker.service holdoff time over,
> scheduling restart.
> Dec 17 15:29:24 ovirt2 systemd: Starting oVirt Hosted Engine High
> Availability Communications Broker...
> Dec 17 15:29:25 ovirt2 systemd-ovirt-ha-broker: Starting ovirt-ha-broker:
> [  OK  ]
> Dec 17 15:29:25 ovirt2 systemd: PID 21304 read from file
> /run/ovirt-hosted-engine-ha/broker.pid does not exist or is a zombie.
>
>
> --
> Matthew Trent
> Network Engineer
> Lewis County IT Services
> 360.740.1247 - Helpdesk
> 360.740.3343 - Direct line
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Hosted engine setup using Gluster - what is proper param's for the storage domain names?

[Sahina Bose]

On 12/17/2015 10:32 PM, Willard Dennis wrote:

Hi all,

Doing the hosted engine setup on Gluster; am at the point of configuring the 
storage domain / datacenter names, and not sure of what my best move is here… 
Here’s what I’m seeing:

——
   --== STORAGE CONFIGURATION ==--

   During customization use CTRL-D to abort.
   Please specify the storage you would like to use (glusterfs, iscsi, 
fc, nfs3, nfs4)[nfs3]: glusterfs
[ INFO  ] Please note that Replica 3 support is required for the shared storage.
   Please specify the full shared storage connection path to use 
(example: host:/path): localhost:/engine
[WARNING] Due to several bugs in mount.glusterfs the validation of GlusterFS 
share cannot be reliable.
[ INFO  ] GlusterFS replica 3 Volume detected
[ INFO  ] Installing on first host
   Please provide storage domain name. [hosted_storage]:
   Local storage datacenter name is an internal name
   and currently will not be shown in engine's admin UI.
   Please enter local datacenter name [hosted_datacenter]:
——

Concerned about the "Local storage datacenter name is an internal name and 
currently will not be shown in engine's admin UI” message… I want to use a second 
distributed Gluster volume (name = “vmdata”) for VM storage if I can, and don’t want 
to mess up the install… What should I consider when setting names for the storage 
domain name and local datacenter names?


You can safely go with the defaults here.

To set up a second storage domain (using gluster volume) - once the 
engine VM is up and running, you can use the user interface to create 
the domain (vmdata).

Note: replica 3 gluster volume is recommended to use as storage domain



Thanks,
Will
___
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