5:08 a.m.
Hi !
After upgrade from ovirt 3.5 to 3.6 I'm not able to manually start
hosted-engine vm using "hosted-engine --vm-start"
I have only one host.
I put engine in global maintenance mode, I shutdown all VM and hosted
engine VM.
I reboot the host and run "hosted-engine --vm-start", but the VM never
start (I waited for 10 minutes).
When I run " hosted-engine --set-maintenance --mode=none" engine VM
start immediately.
[root@ovirt01 ~]# hosted-engine --vm-start
b66ae2c5-de0f-4361-953b-f10226da7eb8
Status = WaitForLaunch
nicModel = rtl8139,pv
statusTime = 4294711929
emulatedMachine = pc
pid = 0
vmName = HostedEngine
devices = [{'index': '2', 'iface': 'ide',
'specParams': {},
'readonly': 'true', 'deviceId':
'9866b541-20db-40c8-9512-b4f5277700fd',
'address': {'bus': '1', 'controller': '0',
'type': 'drive', 'target':
'0', 'unit': '0'}, 'device': 'cdrom',
'shared': 'false', 'path':
'/home/pacchetti/iso/CentOS-7.0-1406-x86_64-Minimal.iso', 'type':
'disk'}, {'index': '0', 'iface': 'virtio',
'format': 'raw', 'bootOrder':
'1', 'poolID': '00000000-0000-0000-0000-000000000000',
'volumeID':
'f89cf2a9-af3c-4c07-9e45-5f2c5fd8e155', 'imageID':
'c0c575cf-9107-49b8-8a0f-95c8efa6ad06', 'specParams': {},
'readonly':
'false', 'domainID': '46f55a31-f35f-465c-b3e2-df45c05e06a7',
'optional':
'false', 'deviceId': 'c0c575cf-9107-49b8-8a0f-95c8efa6ad06',
'address':
{'slot': '0x06', 'bus': '0x00', 'domain':
'0x0000', 'type': 'pci',
'function': '0x0'}, 'device': 'disk', 'shared':
'exclusive',
'propagateErrors': 'off', 'type': 'disk'},
{'device': 'scsi', 'model':
'virtio-scsi', 'type': 'controller'}, {'nicModel':
'pv', 'macAddr':
'00:16:3e:12:d5:35', 'linkActive': 'true', 'network':
'ovirtmgmt',
'filter': 'vdsm-no-mac-spoofing', 'specParams': {},
'deviceId':
'3f76ab15-bf91-41ad-b02d-dbdb21fae828', 'address': {'slot':
'0x03',
'bus': '0x00', 'domain': '0x0000', 'type':
'pci', 'function': '0x0'},
'device': 'bridge', 'type': 'interface'},
{'device': 'console',
'specParams': {}, 'type': 'console', 'deviceId':
'a40e268c-bef7-4ca4-832a-28e550e9e012', 'alias': 'console0'}]
guestDiskMapping = {}
vmType = kvm
clientIp =
displaySecurePort = -1
memSize = 4096
displayPort = -1
cpuType = SandyBridge
spiceSecureChannels =
smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir
smp = 2
displayIp = 0
display = vnc
[root@ovirt01 ~]# hosted-engine --vm-status
!! Cluster is in GLOBAL MAINTENANCE mode !!
--== Host 1 status ==--
Status up-to-date : False
Hostname : ovirt01.hawai.lan
Host ID : 1
Engine status : unknown stale-data
Score : 3400
stopped : False
Local maintenance : False
crc32 : d2fb89cb
Host timestamp : 3569
5:18 a.m.
On Mon, Jan 4, 2016 at 1:08 PM, Stefano Danzi <s.danzi(a)hawai.it> wrote:
Hi !
After upgrade from ovirt 3.5 to 3.6 I'm not able to manually start
hosted-engine vm using "hosted-engine --vm-start"
I have only one host.
I put engine in global maintenance mode, I shutdown all VM and hosted
engine VM.
I reboot the host and run "hosted-engine --vm-start", but the VM never
start (I waited for 10 minutes).
When I run " hosted-engine --set-maintenance --mode=none" engine VM start
immediately.
[root@ovirt01 ~]# hosted-engine --vm-start
b66ae2c5-de0f-4361-953b-f10226da7eb8
Status = WaitForLaunch
nicModel = rtl8139,pv
statusTime = 4294711929
emulatedMachine = pc
pid = 0
vmName = HostedEngine
devices = [{'index': '2', 'iface': 'ide',
'specParams': {},
'readonly': 'true', 'deviceId':
'9866b541-20db-40c8-9512-b4f5277700fd',
'address': {'bus': '1', 'controller': '0',
'type': 'drive', 'target': '0',
'unit': '0'}, 'device': 'cdrom', 'shared':
'false', 'path':
'/home/pacchetti/iso/CentOS-7.0-1406-x86_64-Minimal.iso', 'type':
'disk'},
{'index': '0', 'iface': 'virtio', 'format':
'raw', 'bootOrder': '1',
'poolID': '00000000-0000-0000-0000-000000000000', 'volumeID':
'f89cf2a9-af3c-4c07-9e45-5f2c5fd8e155', 'imageID':
'c0c575cf-9107-49b8-8a0f-95c8efa6ad06', 'specParams': {},
'readonly':
'false', 'domainID': '46f55a31-f35f-465c-b3e2-df45c05e06a7',
'optional':
'false', 'deviceId': 'c0c575cf-9107-49b8-8a0f-95c8efa6ad06',
'address':
{'slot': '0x06', 'bus': '0x00', 'domain':
'0x0000', 'type': 'pci',
'function': '0x0'}, 'device': 'disk', 'shared':
'exclusive',
'propagateErrors': 'off', 'type': 'disk'},
{'device': 'scsi', 'model':
'virtio-scsi', 'type': 'controller'}, {'nicModel':
'pv', 'macAddr':
'00:16:3e:12:d5:35', 'linkActive': 'true', 'network':
'ovirtmgmt',
'filter': 'vdsm-no-mac-spoofing', 'specParams': {},
'deviceId':
'3f76ab15-bf91-41ad-b02d-dbdb21fae828', 'address': {'slot':
'0x03', 'bus':
'0x00', 'domain': '0x0000', 'type': 'pci',
'function': '0x0'}, 'device':
'bridge', 'type': 'interface'}, {'device':
'console', 'specParams': {},
'type': 'console', 'deviceId':
'a40e268c-bef7-4ca4-832a-28e550e9e012',
'alias': 'console0'}]
guestDiskMapping = {}
vmType = kvm
clientIp =
displaySecurePort = -1
memSize = 4096
displayPort = -1
cpuType = SandyBridge
spiceSecureChannels =
smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir
smp = 2
displayIp = 0
display = vnc
[root@ovirt01 ~]# hosted-engine --vm-status
!! Cluster is in GLOBAL MAINTENANCE mode !!
yes, pull you cluster out of global maintenance:
$ hosted-engine --set-maintenance --mode=none
$ hosted-engine --vm-start
--== Host 1 status ==--
Status up-to-date : False
Hostname : ovirt01.hawai.lan
Host ID : 1
Engine status : unknown stale-data
Score : 3400
stopped : False
Local maintenance : False
crc32 : d2fb89cb
Host timestamp : 3569
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
5:20 a.m.
On Mon, Jan 4, 2016 at 1:18 PM, Roy Golan <rgolan(a)redhat.com> wrote:
On Mon, Jan 4, 2016 at 1:08 PM, Stefano Danzi <s.danzi(a)hawai.it> wrote:
> Hi !
> After upgrade from ovirt 3.5 to 3.6 I'm not able to manually start
> hosted-engine vm using "hosted-engine --vm-start"
>
> I have only one host.
> I put engine in global maintenance mode, I shutdown all VM and hosted
> engine VM.
> I reboot the host and run "hosted-engine --vm-start", but the VM never
> start (I waited for 10 minutes).
> When I run " hosted-engine --set-maintenance --mode=none" engine VM start
> immediately.
>
> [root@ovirt01 ~]# hosted-engine --vm-start
>
> b66ae2c5-de0f-4361-953b-f10226da7eb8
> Status = WaitForLaunch
> nicModel = rtl8139,pv
> statusTime = 4294711929
> emulatedMachine = pc
> pid = 0
> vmName = HostedEngine
> devices = [{'index': '2', 'iface': 'ide',
'specParams': {},
> 'readonly': 'true', 'deviceId':
'9866b541-20db-40c8-9512-b4f5277700fd',
> 'address': {'bus': '1', 'controller': '0',
'type': 'drive', 'target': '0',
> 'unit': '0'}, 'device': 'cdrom', 'shared':
'false', 'path':
> '/home/pacchetti/iso/CentOS-7.0-1406-x86_64-Minimal.iso', 'type':
'disk'},
> {'index': '0', 'iface': 'virtio', 'format':
'raw', 'bootOrder': '1',
> 'poolID': '00000000-0000-0000-0000-000000000000',
'volumeID':
> 'f89cf2a9-af3c-4c07-9e45-5f2c5fd8e155', 'imageID':
> 'c0c575cf-9107-49b8-8a0f-95c8efa6ad06', 'specParams': {},
'readonly':
> 'false', 'domainID': '46f55a31-f35f-465c-b3e2-df45c05e06a7',
'optional':
> 'false', 'deviceId': 'c0c575cf-9107-49b8-8a0f-95c8efa6ad06',
'address':
> {'slot': '0x06', 'bus': '0x00', 'domain':
'0x0000', 'type': 'pci',
> 'function': '0x0'}, 'device': 'disk',
'shared': 'exclusive',
> 'propagateErrors': 'off', 'type': 'disk'},
{'device': 'scsi', 'model':
> 'virtio-scsi', 'type': 'controller'}, {'nicModel':
'pv', 'macAddr':
> '00:16:3e:12:d5:35', 'linkActive': 'true', 'network':
'ovirtmgmt',
> 'filter': 'vdsm-no-mac-spoofing', 'specParams': {},
'deviceId':
> '3f76ab15-bf91-41ad-b02d-dbdb21fae828', 'address': {'slot':
'0x03', 'bus':
> '0x00', 'domain': '0x0000', 'type': 'pci',
'function': '0x0'}, 'device':
> 'bridge', 'type': 'interface'}, {'device':
'console', 'specParams': {},
> 'type': 'console', 'deviceId':
'a40e268c-bef7-4ca4-832a-28e550e9e012',
> 'alias': 'console0'}]
> guestDiskMapping = {}
> vmType = kvm
> clientIp =
> displaySecurePort = -1
> memSize = 4096
> displayPort = -1
> cpuType = SandyBridge
> spiceSecureChannels =
> smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir
> smp = 2
> displayIp = 0
> display = vnc
> [root@ovirt01 ~]# hosted-engine --vm-status
>
>
> !! Cluster is in GLOBAL MAINTENANCE mode !!
>
>
yes, pull you cluster out of global maintenance:
$ hosted-engine --set-maintenance --mode=none
$ hosted-engine --vm-start
Sorry I was quick to answer and now I saw you already tried and it
immediately started the vm.
>
> --== Host 1 status ==--
>
> Status up-to-date : False
> Hostname : ovirt01.hawai.lan
> Host ID : 1
> Engine status : unknown stale-data
> Score : 3400
> stopped : False
> Local maintenance : False
> crc32 : d2fb89cb
> Host timestamp : 3569
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
5:28 a.m.
On Mon, Jan 4, 2016 at 12:20 PM, Roy Golan <rgolan(a)redhat.com> wrote:
>
> On Mon, Jan 4, 2016 at 1:08 PM, Stefano Danzi <s.danzi(a)hawai.it> wrote:
>
>> Hi !
>> After upgrade from ovirt 3.5 to 3.6 I'm not able to manually start
>> hosted-engine vm using "hosted-engine --vm-start"
>>
>> I have only one host.
>> I put engine in global maintenance mode, I shutdown all VM and hosted
>> engine VM.
>> I reboot the host and run "hosted-engine --vm-start", but the VM never
>> start (I waited for 10 minutes).
>> When I run " hosted-engine --set-maintenance --mode=none" engine VM
>> start immediately.
>>
>>
>
Sorry I was quick to answer and now I saw you already tried and it
immediately started the vm.
Possibly the original question was of different kind?
So how to manually start engine VM if environment is in global maintenance
and I have previously shutdown it? Should it be possible?
For example one wants to check it from an OS point of view and not oVirt
point of view, before exiting maintenance...
Gianluca
5:37 a.m.
This is a multi-part message in MIME format.
--------------060903020405030107030502
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Il 04/01/2016 12.28, Gianluca Cecchi ha scritto:
On Mon, Jan 4, 2016 at 12:20 PM, Roy Golan <rgolan(a)redhat.com
<mailto:rgolan@redhat.com>> wrote:
On Mon, Jan 4, 2016 at 1:08 PM, Stefano Danzi
<s.danzi(a)hawai.it <mailto:s.danzi@hawai.it>> wrote:
Hi !
After upgrade from ovirt 3.5 to 3.6 I'm not able to
manually start hosted-engine vm using "hosted-engine
--vm-start"
I have only one host.
I put engine in global maintenance mode, I shutdown all VM
and hosted engine VM.
I reboot the host and run "hosted-engine --vm-start", but
the VM never start (I waited for 10 minutes).
When I run " hosted-engine --set-maintenance --mode=none"
engine VM start immediately.
Sorry I was quick to answer and now I saw you already tried and it
immediately started the vm.
Possibly the original question was of different kind?
So how to manually start engine VM if environment is in global
maintenance and I have previously shutdown it? Should it be possible?
For example one wants to check it from an OS point of view and not
oVirt point of view, before exiting maintenance...
Gianluca
Gianluca you are right!!!
ovirt 3.5 permit to start engine VM when cluster is in maintenance... I did it many
times!!! From oVirt 3.6 it is no longer possible.
VM remain in state "WaitingForLaunch" until cluster exit from maintenance.
--------------060903020405030107030502
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">Il 04/01/2016 12.28, Gianluca Cecchi ha
scritto:<br>
</div>
<blockquote
cite="mid:CAG2kNCzN53OuU14uf9jOJXkQWnXZAA7zW0C5MPib1VS5PwRQzA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Mon, Jan 4, 2016 at 12:20 PM, Roy
Golan <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:rgolan@redhat.com"
target="_blank">rgolan(a)redhat.com</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">
<div>
<div class="h5">
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">
<div>
<div>On Mon, Jan 4, 2016 at 1:08 PM,
Stefano Danzi <span
dir="ltr"><<a
moz-do-not-send="true"
href="mailto:s.danzi@hawai.it"
target="_blank"><a
class="moz-txt-link-abbreviated"
href="mailto:s.danzi@hawai.it">s.danzi@hawai.it</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">Hi !<br>
After upgrade from ovirt 3.5 to
3.6 I'm not able to manually start
hosted-engine vm using
"hosted-engine --vm-start"<br>
<br>
I have only one host.<br>
I put engine in global maintenance
mode, I shutdown all VM and hosted
engine VM.<br>
I reboot the host and run
"hosted-engine --vm-start", but
the VM never start (I waited for
10 minutes).<br>
When I run " hosted-engine
--set-maintenance --mode=none"
engine VM start immediately.<br>
<br>
</blockquote>
</div>
</div>
<div> <br>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</div>
</div>
<div>Sorry I was quick to answer and now I saw you
already tried and it immediately started the vm.<br>
<br>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Possibly the original question was of different kind?</div>
<div>So how to manually start engine VM if environment is in
global maintenance and I have previously shutdown it?
Should it be possible?</div>
<div>For example one wants to check it from an OS point of
view and not oVirt point of view, before exiting
maintenance...</div>
<div><br>
</div>
<div>Gianluca </div>
</div>
<br>
</div>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">Gianluca you are
right!!!
ovirt 3.5 permit to start engine VM when cluster is in maintenance... I did it many
times!!! From oVirt 3.6 it is no longer possible.
VM remain in state "WaitingForLaunch" until cluster exit from maintenance.
</pre>
</body>
</html>
--------------060903020405030107030502--
6:16 a.m.
On Mon, Jan 4, 2016 at 1:37 PM, Stefano Danzi <s.danzi(a)hawai.it> wrote:
Il 04/01/2016 12.28, Gianluca Cecchi ha scritto:
On Mon, Jan 4, 2016 at 12:20 PM, Roy Golan <rgolan(a)redhat.com> wrote:
>
>
>
>>
>> On Mon, Jan 4, 2016 at 1:08 PM, Stefano Danzi < <s.danzi(a)hawai.it>
>> s.danzi(a)hawai.it> wrote:
>>
>>> Hi !
>>> After upgrade from ovirt 3.5 to 3.6 I'm not able to manually start
>>> hosted-engine vm using "hosted-engine --vm-start"
>>>
>>> I have only one host.
>>> I put engine in global maintenance mode, I shutdown all VM and hosted
>>> engine VM.
>>> I reboot the host and run "hosted-engine --vm-start", but the VM
never
>>> start (I waited for 10 minutes).
>>> When I run " hosted-engine --set-maintenance --mode=none" engine
VM
>>> start immediately.
>>>
>>>
>>
>
> Sorry I was quick to answer and now I saw you already tried and it
> immediately started the vm.
>
>
>
Possibly the original question was of different kind?
So how to manually start engine VM if environment is in global maintenance
and I have previously shutdown it? Should it be possible?
For example one wants to check it from an OS point of view and not oVirt
point of view, before exiting maintenance...
Gianluca
Gianluca you are right!!!
ovirt 3.5 permit to start engine VM when cluster is in maintenance... I did it many
times!!! From oVirt 3.6 it is no longer possible.
VM remain in state "WaitingForLaunch" until cluster exit from maintenance.
in 3.6 maintenance means we can't run the vm. Running it means we needs its
disks available, meaning we need the domain up and monitored and with a
sanlock monitoring it. We can't
achieve maintenance action like yum update of sanlock, vdsm, agent , if the
the whole system is up.
Simone, Martin any additions?
3033
days inactive
3033
days old
5 comments
3 participants
participants (3)
-
Gianluca Cecchi -
Roy Golan -
Stefano Danzi