On 29/7/2559 17:07, Simone Tiraboschi wrote:
On Fri, Jul 29, 2016 at 11:35 AM, Wee Sritippho <we...@forest.go.th> wrote:
On 29/7/2559 15:50, Simone Tiraboschi wrote:
On Fri, Jul 29, 2016 at 6:31 AM, Wee Sritippho <we...@forest.go.th> wrote:
On 28/7/2559 15:54, Simone Tiraboschi wr
On 29/7/2559 15:50, Simone Tiraboschi wrote:
On Fri, Jul 29, 2016 at 6:31 AM, Wee Sritippho <we...@forest.go.th> wrote:
On 28/7/2559 15:54, Simone Tiraboschi wrote:
On Thu, Jul 28, 2016 at 10:41 AM, Wee Sritippho <we...@forest.go.th> wrote:
On 21/7/2559 16:53, Simone Tiraboschi wr
On 28/7/2559 15:54, Simone Tiraboschi wrote:
On Thu, Jul 28, 2016 at 10:41 AM, Wee Sritippho <we...@forest.go.th
<mailto:we...@forest.go.th>> wrote:
On 21/7/2559 16:53, Simone Tiraboschi wrote:
On Thu, Jul 21, 2016 at 11:43 AM, Wee Sritippho
<we...@forest.g
On 21/7/2559 16:53, Simone Tiraboschi wrote:
On Thu, Jul 21, 2016 at 11:43 AM, Wee Sritippho <we...@forest.go.th
<mailto:we...@forest.go.th>> wrote:
Can I just follow
http://www.ovirt.org/documentation/how-to/hosted-engine/#upgrade-hosted-engine
until step 3 and do eve
Hi,
I used to follow
http://www.ovirt.org/documentation/how-to/hosted-engine/#upgrade-hosted-engine
when upgrading Hosted Engine (HE) but always fail to make the engine VM
migrate to the fresh upgraded host as described in step 7. Furthermore,
the update available icon never disappeared from
On 7/7/2559 15:41, Simone Tiraboschi wrote:
On Thu, Jul 7, 2016 at 7:17 AM, Wee Sritippho <we...@forest.go.th> wrote:
Hi, I followed this instruction:
http://www.ovirt.org/documentation/how-to/hosted-engine/#upgrade-hosted-engine
However, when I exited the global maintenance mode in
I'm sorry. After looking thoroughly, the ordinary VM *did* migrated, the
one that didn't migrate is the engine VM.
I've added agent.log & broker.log to the logs folder:
https://app.box.com/s/ibi8pjxyxv4khek2menho1orumstek8y
On 7/7/2559 15:34, Wee Sritippho wrote:
Hi, I was tr
Hi, I was trying to upgrade the hosted-engine environment from v3.6.5 to
v3.6.7.
Upgrading host01 and host02 is OK. But when I was trying to put host03
(which has the engine VM in it) to maintenance mode, the process stuck -
only the engine VM was migrated, another ordinary VM didn't.
I
Hi, I followed this instruction:
http://www.ovirt.org/documentation/how-to/hosted-engine/#upgrade-hosted-engine
However, when I exited the global maintenance mode in step 7 and waited
for about 15 minutes, the engine VM still doesn't migrate to the fresh
upgraded host.
BTW, after step 6,
Hi,
I used to have a similar problem where one of my host can't be deployed due to
the absence of ovirtmgmt bridge. Simone said it's a bug (
https://bugzilla.redhat.com/1323465 ) which would be fixed in 3.6.6.
This is what I've done to solve it:
1. In the web UI, set the failed host to
all experiment with power_wait parameter, here are the results:
- power_wait=60 : HA VMs restarted and are pingable in ~2:45 minutes
after connection lost
- power_wait=30 : HA VMs restarted and are pingable in ~2:15 minutes
after connection lost
On 10/5/2559 12:52, Wee Sritippho wrote:
Hi,
I'm
Hi,
I'm running an oVirt hosted-engine environment on 3 hosts. To test VMs'
HA functionality, I shutdown host02's link, where one of my HA VMs is
running on, using this command:
2016-05-10 09:59:19 ICT [root@host02 ~]# ip link set bond0 down
Few seconds later, an attempt to fence host02 was
ssue.
Yes, exactly the same issue.
Thank you.
>Regards
>
>--
>Martin Sivak
>SLA / oVirt
>
>
>On Wed, May 4, 2016 at 8:34 AM, Wee Sritippho <we...@forest.go.th>
>wrote:
>> I've tried again and made sure all hosts have same clock.
>>
>> After a
d a lot maintenance mode.
You can try something like this to get some interesting lines from agent.log:
egrep -i 'start eng|shut|vm started|vm running|vm is running on|
maintenance detected|migra'
Best,
On Mon, Apr 25, 2016 at 12:27 PM, Wee Sritippho <we...@forest.go.th> wrote:
On 3/5/2559 13:25, knarra wrote:
On 05/03/2016 08:35 AM, Wee Sritippho wrote:
Hi,
I'm making a fresh hosted-engine installation on 3 hosts. First 2
hosts succeeded, but the 3rd one stuck at termination state
"Installing Host hosted_engine_3. Stage: Termination.", then, 3
min
Hi,
I'm making a fresh hosted-engine installation on 3 hosts. First 2 hosts
succeeded, but the 3rd one stuck at termination state "Installing Host
hosted_engine_3. Stage: Termination.", then, 3 minutes later, "VDSM
hosted_engine_3 command failed: Message timeout which can be caused by
Hi,
I used to install oVirt hosted-engine 3.5 using fibre channel storage.
It required a dedicated LUN, which can't be used by other VMs, to host
the hosted engine VM. Therefore, I have to create a small LUN (50GB) for
the engine VM in addition to the LUN that I used to host other VMs.
Does
On Mon, Apr 25, 2016 at 10:58 AM, Wee Sritippho <we...@forest.go.th> wrote:
Hi,
From the hosted-engine FAQ, the engine VM should be up and running in about
5 minutes after its host was forced poweroff. However, after updated oVirt
3.6.4 to 3.6.5, the engine VM won't restart automatically even
Hi,
From the hosted-engine FAQ, the engine VM should be up and running in
about 5 minutes after its host was forced poweroff. However, after
updated oVirt 3.6.4 to 3.6.5, the engine VM won't restart automatically
even after 10+ minutes (I already made sure that global maintenance mode
is set
M, Simone Tiraboschi
><stira...@redhat.com> wrote:
>> On Fri, Apr 22, 2016 at 9:44 AM, Wee Sritippho <we...@forest.go.th>
>wrote:
>>> Hi,
>>>
>>> I were upgrading oVirt from 3.6.4.1 to 3.6.5. The engine-vm was
>running on
>>> host02. Thes
Hi,
I were upgrading oVirt from 3.6.4.1 to 3.6.5. The engine-vm was running
on host02. These are the steps that I've done:
1. Set hosted engine maintenance mode to global
2. Accessed engine-vm and upgraded oVirt to latest version
3. Run 'reboot' in engine-vm
4. After about 10 minutes, the
On 20 เมษายน 2016 18 นาฬิกา 29 นาที 26 วินาที GMT+07:00, Yedidyah Bar David
<d...@redhat.com> wrote:
>On Wed, Apr 20, 2016 at 1:42 PM, Wee Sritippho <we...@forest.go.th>
>wrote:
>> Hi Didi & Martin,
>>
>> I followed your instructions and
d if=/dev/zero of=/path/to/metadata bs=1M to
clean it - But be CAREFUL to not touch any other file or disk you
might find.
Then restart the hosted engine tools and all should be fine.
Martin
On Wed, Apr 20, 2016 at 8:20 AM, Yedidyah Bar David <d...@redhat.com> wrote:
On Wed, Apr 20, 2
Hi,
I used CentOS-7-x86_64-Minimal-1511.iso to install the hosts and the engine.
The 1st host and the hosted-engine were installed successfully, but the
2nd host setup failed with this error message:
"Failed to execute stage 'Setup validation': Metadata version 2 from
host 52 too new for
Hi,
I used CentOS-7-x86_64-Minimal-1511.iso to install the hosts and the engine.
The 1st host and the hosted-engine were installed successfully, but the
2nd host failed with this error message:
"Failed to execute stage 'Setup validation': Metadata version 2 from
host 52 too new for this
David wrote:
On Wed, Mar 23, 2016 at 6:40 AM, Wee Sritippho <we...@forest.go.th> wrote:
Hi,
I'm installing oVirt hosted-engine using a fibre channel storage. During the
deployment I found this error:
[ ERROR ] The VDSM host was found in a failed state. Please check engine
and boo
Hi,
I'm trying to deploy a 2nd host to my hosted-engine environment, but at
some point, the setup ask me to type a password for admin@internal
again. Do I need to type the same password that I choose when deploying
the 1st host? If not, would it replace the old password?
Thank you,
Wee
---
note, since you are using gv0 as storage domain, set
the virt group profile on this volume - "gluster volume set gv0 group
virt"
On 02/23/2016 01:39 PM, Wee Sritippho wrote:
Hi,
I'm trying to deploy an oVirt Hosed Engine environment using this
glusterfs volume:
# gluster volum
'GlusterFS' as my 'Storage Type' every text field become grayed-out.
4. When host A restarted again, I notice that 'Use Host' was changed
from host A to host B instead. Is this an expected behavior?
Regards,
Wee Sritippho
P.S: Please excuse my poor English
29 matches
Mail list logo
