Re: [ovirt-users] [hosted-engine] Metadata too new error when adding 2nd host

2016-04-21 Thread Wee Sritippho
On 20 เมษายน 2016 18 นาฬิกา 29 นาที 26 วินาที GMT+07:00, Yedidyah Bar David wrote: >On Wed, Apr 20, 2016 at 1:42 PM, Wee Sritippho >wrote: >> Hi Didi & Martin, >> >> I followed your instructions and are able to add the 2nd host. Thank >you :) >> >> This is

Re: [ovirt-users] [hosted-engine] Metadata too new error when adding 2nd host

2016-04-20 Thread Martin Sivak
Hi everybody, I added the procedure to the wiki, it you would be so kind to review it. https://github.com/oVirt/ovirt-site/pull/188 Thanks Martin On Wed, Apr 20, 2016 at 1:29 PM, Yedidyah Bar David wrote: > On Wed, Apr 20, 2016 at 1:42 PM, Wee Sritippho

Re: [ovirt-users] [hosted-engine] Metadata too new error when adding 2nd host

2016-04-20 Thread Yedidyah Bar David
On Wed, Apr 20, 2016 at 1:42 PM, Wee Sritippho wrote: > Hi Didi & Martin, > > I followed your instructions and are able to add the 2nd host. Thank you :) > > This is what I've done: > > [root@host01 ~]# hosted-engine --set-maintenance --mode=global > > [root@host01 ~]#

Re: [ovirt-users] [hosted-engine] Metadata too new error when adding 2nd host

2016-04-20 Thread Wee Sritippho
Hi Didi & Martin, I followed your instructions and are able to add the 2nd host. Thank you :) This is what I've done: [root@host01 ~]# hosted-engine --set-maintenance --mode=global [root@host01 ~]# systemctl stop ovirt-ha-agent [root@host01 ~]# systemctl stop ovirt-ha-broker [root@host01

Re: [ovirt-users] [hosted-engine] Metadata too new error when adding 2nd host

2016-04-20 Thread Martin Sivak
> And we also do not clean on upgrades... Perhaps we can? Should? Optionally? > We can't. We do not execute any setup tool during upgrade and the clean procedure requires that all hosted engine tooling is shut down. Martin On Wed, Apr 20, 2016 at 11:40 AM, Yedidyah Bar David

Re: [ovirt-users] [hosted-engine] Metadata too new error when adding 2nd host

2016-04-20 Thread Yedidyah Bar David
On Wed, Apr 20, 2016 at 11:40 AM, Martin Sivak wrote: >> Doesn't cleaning sanlock lockspace require also to stop sanlock itself? >> I guess it's supposed to be able to handle this, but perhaps users want >> to clean the lockspace because dirt there causes also problems with >>

Re: [ovirt-users] [hosted-engine] Metadata too new error when adding 2nd host

2016-04-20 Thread Martin Sivak
> Doesn't cleaning sanlock lockspace require also to stop sanlock itself? > I guess it's supposed to be able to handle this, but perhaps users want > to clean the lockspace because dirt there causes also problems with > sanlock, no? Sanlock can be up, but the lockspace has to be unused. > So the

Re: [ovirt-users] [hosted-engine] Metadata too new error when adding 2nd host

2016-04-20 Thread Yedidyah Bar David
On Wed, Apr 20, 2016 at 11:20 AM, Martin Sivak wrote: >> after moving to global maintenance. > > Good point. > >> Martin - any advantage of this over '–reinitialize-lockspace'? Besides >> that it works also in older versions? Care to add this to the howto page? > > Reinitialize

Re: [ovirt-users] [hosted-engine] Metadata too new error when adding 2nd host

2016-04-20 Thread Martin Sivak
> after moving to global maintenance. Good point. > Martin - any advantage of this over '–reinitialize-lockspace'? Besides > that it works also in older versions? Care to add this to the howto page? Reinitialize lockspace clears the sanlock lockspace, not the metadata file. Those are two

Re: [ovirt-users] [hosted-engine] Metadata too new error when adding 2nd host

2016-04-20 Thread Yedidyah Bar David
On Wed, Apr 20, 2016 at 11:11 AM, Martin Sivak wrote: >> Assuming you never deployed a host with ID 52, this is likely a result of a >> corruption or dirt or something like that. > >> I see that you use FC storage. In previous versions, we did not clean such >> storage, so you

Re: [ovirt-users] [hosted-engine] Metadata too new error when adding 2nd host

2016-04-20 Thread Martin Sivak
> Assuming you never deployed a host with ID 52, this is likely a result of a > corruption or dirt or something like that. > I see that you use FC storage. In previous versions, we did not clean such > storage, so you might have dirt left. This is the exact reason for an error like yours. Using

Re: [ovirt-users] [hosted-engine] Metadata too new error when adding 2nd host

2016-04-20 Thread วีร์ ศรีทิพโพธิ์
etadataError: Metadata version 2 from host 52 too new for this agent (highest compatible version: 1) - ข้อความดั้งเดิม - จาก: "Yedidyah Bar David" <d...@redhat.com> ถึง: "Wee Sritippho" <we...@forest.go.th> สำเนา: "users" <users@ovirt.org> ส่งแล้ว: พุธ

Re: [ovirt-users] [hosted-engine] Metadata too new error when adding 2nd host

2016-04-20 Thread Yedidyah Bar David
On Wed, Apr 20, 2016 at 7:15 AM, Wee Sritippho wrote: > 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

[ovirt-users] [hosted-engine] Metadata too new error when adding 2nd host

2016-04-19 Thread Wee Sritippho
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