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 what I've done:
>>
>> [root@host01 ~]
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 wrote:
>> Hi Didi & Martin,
>>
>> I f
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 ~]# systemctl stop ovirt-ha-agen
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 ~]#
> 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 wrote:
> On Wed, Ap
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
>> sanlock, no?
>
> San
> 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
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 lockspace clears th
> 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 differe
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 might have dirt left
> 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 d
atalMetadataError: Metadata version 2
from host 52 too new for this agent (highest compatible version: 1)
- ข้อความดั้งเดิม -
จาก: "Yedidyah Bar David"
ถึง: "Wee Sritippho"
สำเนา: "users"
ส่งแล้ว: พุธ, 20 เมษายน, 2016 1:20:44 PM
เรื่อง: Re: [ovirt-users] [hosted
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 execute stage 'Setup va
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 agen
14 matches
Mail list logo