Dear Konstantin,




 Read the instruction for installation before
 Where did you see  CentOS7.3   ?


 with br, Ilya

 


 

oVirt 4.0.6 Release Notes

The oVirt Project is pleased to announce the availability of 4.0.6 Release as of January 10, 2017.

oVirt is an open source alternative to VMware™ vSphere™, and provides an awesome KVM management interface for multi-node virtualization. This release is available now for Red Hat Enterprise Linux 7.2, CentOS Linux 7.2 (or similar).

To find out more about features which were added in previous oVirt releases, check out the previous versions release notes. For a general overview of oVirt, read the Quick Start Guide and the about oVirt page.

An updated documentation has been provided by our downstream Red Hat Virtualization


2017-01-20 9:02 GMT+03:00 Стаценко Константин Юрьевич <statsenko_ky@interrao.ru>:

Anyone ?

 

From: users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Стаценко Константин Юрьевич
Sent: Thursday, January 19, 2017 5:08 PM
To: users <users@ovirt.org>
Subject: [ovirt-users] vdsm problem

 

Hello!

Today, after installing some of the updates, vdsmd suddenly dies. Running oVirt 4.0.6 CentOS 7.3.

It cannot start any more:

 

# journalctl -xe        

 

-- Subject: Unit vdsmd.service has begun start-up

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit vdsmd.service has begun starting up.

Jan 19 18:03:31 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: vdsm: Running mkdirs

Jan 19 18:03:31 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: vdsm: Running configure_coredump

Jan 19 18:03:31 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: vdsm: Running configure_vdsm_logs

Jan 19 18:03:31 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: vdsm: Running wait_for_network

Jan 19 18:03:31 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: vdsm: Running run_init_hooks

Jan 19 18:03:31 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: vdsm: Running upgraded_version_check

Jan 19 18:03:31 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: vdsm: Running check_is_configured

Jan 19 18:03:32 msk1-kvm001.interrao.ru sasldblistusers2[20115]: DIGEST-MD5 common mech free

Jan 19 18:03:32 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: Error:

Jan 19 18:03:32 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: One of the modules is not configured to work with VDSM.

Jan 19 18:03:32 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: To configure the module use the following:

Jan 19 18:03:32 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: 'vdsm-tool configure [--module module-name]'.

Jan 19 18:03:32 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: If all modules are not configured try to use:

Jan 19 18:03:32 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: 'vdsm-tool configure --force'

Jan 19 18:03:32 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: (The force flag will stop the module's service and start it

Jan 19 18:03:32 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: afterwards automatically to load the new configuration.)

Jan 19 18:03:32 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: Current revision of multipath.conf detected, preserving

Jan 19 18:03:32 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: libvirt is already configured for vdsm

Jan 19 18:03:32 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: Modules sebool are not configured

Jan 19 18:03:32 msk1-kvm001.interrao.ru vdsmd_init_common.sh[20079]: vdsm: stopped during execute check_is_configured task (task returned with error code 1).

Jan 19 18:03:32 msk1-kvm001.interrao.ru systemd[1]: vdsmd.service: control process exited, code=exited status=1

Jan 19 18:03:32 msk1-kvm001.interrao.ru systemd[1]: Failed to start Virtual Desktop Server Manager.

-- Subject: Unit vdsmd.service has failed

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit vdsmd.service has failed.

--

-- The result is failed.

Jan 19 18:03:32 msk1-kvm001.interrao.ru systemd[1]: Dependency failed for MOM instance configured for VDSM purposes.

-- Subject: Unit mom-vdsm.service has failed

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit mom-vdsm.service has failed.

--

-- The result is dependency.

Jan 19 18:03:32 msk1-kvm001.interrao.ru systemd[1]: Job mom-vdsm.service/start failed with result 'dependency'.

Jan 19 18:03:32 msk1-kvm001.interrao.ru systemd[1]: Unit vdsmd.service entered failed state.

Jan 19 18:03:32 msk1-kvm001.interrao.ru systemd[1]: vdsmd.service failed.

Jan 19 18:03:32 msk1-kvm001.interrao.ru systemd[1]: Cannot add dependency job for unit microcode.service, ignoring: Invalid argument

Jan 19 18:03:33 msk1-kvm001.interrao.ru systemd[1]: vdsmd.service holdoff time over, scheduling restart.

Jan 19 18:03:33 msk1-kvm001.interrao.ru systemd[1]: Cannot add dependency job for unit microcode.service, ignoring: Unit is not loaded properly: Invalid argumen

Jan 19 18:03:33 msk1-kvm001.interrao.ru systemd[1]: start request repeated too quickly for vdsmd.service

Jan 19 18:03:33 msk1-kvm001.interrao.ru systemd[1]: Failed to start Virtual Desktop Server Manager.

-- Subject: Unit vdsmd.service has failed

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit vdsmd.service has failed.

--

-- The result is failed.

Jan 19 18:03:33 msk1-kvm001.interrao.ru systemd[1]: Dependency failed for MOM instance configured for VDSM purposes.

-- Subject: Unit mom-vdsm.service has failed

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit mom-vdsm.service has failed.

--

-- The result is dependency.

Jan 19 18:03:33 msk1-kvm001.interrao.ru systemd[1]: Job mom-vdsm.service/start failed with result 'dependency'.

Jan 19 18:03:33 msk1-kvm001.interrao.ru systemd[1]: Unit vdsmd.service entered failed state.

Jan 19 18:03:33 msk1-kvm001.interrao.ru systemd[1]: vdsmd.service failed.

 

 

 

# vdsm-tool configure

 

Checking configuration status...

 

Current revision of multipath.conf detected, preserving

libvirt is already configured for vdsm

SUCCESS: ssl configured to true. No conflicts

 

Running configure...

libsepol.context_from_record: type ovirt_vmconsole_host_port_t is not defined (No such file or directory).

libsepol.context_from_record: could not create context structure (Invalid argument).

libsepol.port_from_record: could not create port structure for range 2223:2223 (tcp) (Invalid argument).

libsepol.sepol_port_modify: could not load port range 2223 - 2223 (tcp) (Invalid argument).

libsemanage.dbase_policydb_modify: could not modify record value (Invalid argument).

libsemanage.semanage_base_merge_components: could not merge local modifications into policy (Invalid argument).

Traceback (most recent call last):

  File "/bin/vdsm-tool", line 219, in main

    return tool_command[cmd]["command"](*args)

  File "/usr/lib/python2.7/site-packages/vdsm/tool/__init__.py", line 38, in wrapper

    func(*args, **kwargs)

  File "/usr/lib/python2.7/site-packages/vdsm/tool/configurator.py", line 141, in configure

    _configure(c)

  File "/usr/lib/python2.7/site-packages/vdsm/tool/configurator.py", line 88, in _configure

    getattr(module, 'configure', lambda: None)()

  File "/usr/lib/python2.7/site-packages/vdsm/tool/configurators/sebool.py", line 84, in configure

    _setup_booleans(True)

  File "/usr/lib/python2.7/site-packages/vdsm/tool/configurators/sebool.py", line 57, in _setup_booleans

    sebool_obj.finish()

  File "/usr/lib/python2.7/site-packages/seobject/__init__.py", line 320, in finish

    self.commit()

  File "/usr/lib/python2.7/site-packages/seobject/__init__.py", line 310, in commit

    rc = semanage_commit(self.sh)

OSError: [Errno 22] Invalid argument

 

How can we fix this issue ?

Thanks.


_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users