[ovirt-users] Leaving maintenace mode

Martin Sivak msivak at redhat.com
Wed Jan 11 09:12:11 UTC 2017


Hi,

we will focus on this exact issue (and couple of similar ones) in the
next release, but the reason is actually pretty simple.. the ISO
domain is mounted to the /rhev space and a when a simple traversal
hits the unavailable NFS ISO domain, it gets stuck.. and the timeout
is somewhat long.

Martin

On Tue, Jan 10, 2017 at 6:37 PM, Stefano Danzi <s.danzi at hawai.it> wrote:
> Hi!
>
> You are right! But I think isn't correct that the command fail if the iso
> domain isn't available.
> I'ts ok if the comman fail when the self hosted engine storage is not
> available, but not for iso domain.
>
>
>
> Il 10/01/2017 17.47, Martin Sivak ha scritto:
>>
>> Hi,
>>
>> the appliance we publish actually does not enable the ISO domain on
>> the VM anymore for exactly this reason. I believe we mention this in
>> the documentation somewhere too.
>>
>> Please do not put or disable all domains that are served from inside
>> the engine VM.
>>
>> Best regards
>>
>> --
>> Martin Sivak
>> SLA / oVirt
>>
>> On Tue, Jan 10, 2017 at 3:41 PM, Stefano Danzi <s.danzi at hawai.it> wrote:
>>>
>>> Hi!
>>>
>>> I have a testing oVirt installation with only one host and running self
>>> hosted engine.
>>>
>>> If I put host in global maintenance mode:
>>>
>>>   hosted-engine  --set-maintenance --mode=global
>>>
>>> then ssh into self hosted engine VM, shoutdown VM using 'init 0', when
>>> I run on the host:
>>>
>>> hosted-engine  --set-maintenance --mode=none
>>>
>>> I have:
>>>
>>> Traceback (most recent call last):
>>>    File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
>>>      "__main__", fname, loader, pkg_name)
>>>    File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
>>>      exec code in run_globals
>>>    File
>>>
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
>>> line 73, in <module>
>>>      if not maintenance.set_mode(sys.argv[1]):
>>>    File
>>>
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/set_maintenance.py",
>>> line 61, in set_mode
>>>      value=m_global,
>>>    File
>>>
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
>>> line 259, in set_maintenance_mode
>>>      str(value))
>>>    File
>>>
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
>>> line 202, in set_global_md_flag
>>>      self._configure_broker_conn(broker)
>>>    File
>>>
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
>>> line 180, in _configure_broker_conn
>>>      dom_type=dom_type)
>>>    File
>>>
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
>>> line 176, in set_storage_domain
>>>      .format(sd_type, options, e))
>>> ovirt_hosted_engine_ha.lib.exceptions.RequestError: Failed to set storage
>>> domain FilesystemBackend, options {'dom_type': 'nfs3', 'sd_uuid':
>>> '46f55a31-f35f-465c-b3e2-df45c05e06a7'}: Connection timed out
>>>
>>>
>>> This because the host has the iso domain nfs export mounted but the self
>>> hosted engine VM is not running, I think...
>>> So I have to reboot the host before change the maintenance mode.
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>
>


More information about the Users mailing list