- Users - oVirt List Archives

[aaa-ldap-setup] Login sequence fails on setup
by mopiel games 19 Sep '18

19 Sep '18

When running setup for openldap , bind is successful with the provided user and pass but login fails. [ INFO ] Connection succeeded Enter search user DN (for example uid=username,dc=example,dc=com or leave empty for anonymous): cn=admin,dc=exalt,dc=ps Enter search user password: [ INFO ] Attempting to bind using 'cn=admin,dc=exalt,dc=ps' Please enter base DN (dc=exalt,dc=ps) [dc=exalt,dc=ps]: ou=users,dc=exalt,dc=ps Are you going to use Single Sign-On for Virtual Machines (Yes, No) [Yes]: NOTE: Profile name has to match domain name, otherwise Single Sign-On for Virtual Machines will not work. Please specify profile name that will be visible to users [ldap23.exalt.ps]: [ INFO ] Stage: Setup validation NOTE: It is highly recommended to test drive the configuration before applying it into engine. Login sequence is executed automatically, but it is recommended to also execute Search sequence manually after successful Login sequence. Please provide credentials to test login flow: Enter user name: uid=user,ou=users,dc=exalt,dc=ps Enter user password: [ INFO ] Executing login sequence... Login output: 2018-09-19 15:29:22,982+03 INFO ======================================================================== 2018-09-19 15:29:22,999+03 INFO ============================ Initialization ============================ 2018-09-19 15:29:23,000+03 INFO ======================================================================== 2018-09-19 15:29:23,025+03 INFO Loading extension 'ldap23.exalt.ps-authn' 2018-09-19 15:29:23,086+03 INFO Extension 'ldap23.exalt.ps-authn' loaded 2018-09-19 15:29:23,089+03 INFO Loading extension 'ldap23.exalt.ps' 2018-09-19 15:29:23,098+03 INFO Extension 'ldap23.exalt.ps' loaded 2018-09-19 15:29:23,099+03 INFO Initializing extension 'ldap23.exalt.ps-authn' 2018-09-19 15:29:23,101+03 INFO [ovirt-engine-extension-aaa-ldap.authn::ldap23.exalt.ps-authn] Creating LDAP pool 'authz' 2018-09-19 15:29:23,796+03 INFO [ovirt-engine-extension-aaa-ldap.authn::ldap23.exalt.ps-authn] LDAP pool 'authz' information: vendor='null' version='null' 2018-09-19 15:29:23,797+03 INFO [ovirt-engine-extension-aaa-ldap.authn::ldap23.exalt.ps-authn] Creating LDAP pool 'authn' 2018-09-19 15:29:24,196+03 INFO [ovirt-engine-extension-aaa-ldap.authn::ldap23.exalt.ps-authn] LDAP pool 'authn' information: vendor='null' version='null' 2018-09-19 15:29:24,197+03 INFO Extension 'ldap23.exalt.ps-authn' initialized 2018-09-19 15:29:24,197+03 INFO Initializing extension 'ldap23.exalt.ps' 2018-09-19 15:29:24,198+03 INFO [ovirt-engine-extension-aaa-ldap.authz::ldap23.exalt.ps]Creating LDAP pool 'authz' 2018-09-19 15:29:24,614+03 INFO [ovirt-engine-extension-aaa-ldap.authz::ldap23.exalt.ps]LDAP pool 'authz' information: vendor='null' version='null' 2018-09-19 15:29:24,615+03 INFO [ovirt-engine-extension-aaa-ldap.authz::ldap23.exalt.ps] Available Namespaces: [ou=users,dc=exalt,dc=ps] 2018-09-19 15:29:24,615+03 INFO Extension 'ldap23.exalt.ps' initialized 2018-09-19 15:29:24,615+03 INFO Start of enabled extensions list 2018-09-19 15:29:24,616+03 INFO Instance name: 'ldap23.exalt.ps-authn', Extension name: ' ovirt-engine-extension-aaa-ldap.authn', Version: '1.3.7', Notes: 'Display name: ovirt-engine-extension-aaa-ldap-1.3.7-1.el7.centos', License: 'ASL 2.0', Home: 'http://www.ovirt.org', Author 'The oVirt Project', Build interface Version: '0', File: '/tmp/tmphILEhJ/extensions.d/ldap23.exalt.ps-authn.properties', Initialized: 'true' 2018-09-19 15:29:24,616+03 INFO Instance name: 'ldap23.exalt.ps', Extension name: 'ovirt-engine-extension-aaa-ldap.authz', Version: '1.3.7', Notes: 'Display name: ovirt-engine-extension-aaa-ldap-1.3.7-1.el7.centos', License: 'ASL 2.0', Home: 'http://www.ovirt.org', Author 'The oVirt Project', Build interface Version: '0', File: '/tmp/tmphILEhJ/extensions.d/ldap23.exalt.ps.properties', Initialized: 'true' 2018-09-19 15:29:24,616+03 INFO End of enabled extensions list 2018-09-19 15:29:24,616+03 INFO ======================================================================== 2018-09-19 15:29:24,616+03 INFO ============================== Execution =============================== 2018-09-19 15:29:24,616+03 INFO ======================================================================== 2018-09-19 15:29:24,617+03 INFO Iteration: 0 2018-09-19 15:29:24,617+03 INFO Profile='ldap23.exalt.ps' authn='ldap23.exalt.ps-authn' authz='ldap23.exalt.ps' mapping='null' 2018-09-19 15:29:24,618+03 INFO API: -->Authn.InvokeCommands.AUTHENTICATE_CREDENTIALS profile='ldap23.exalt.ps' user='uid=user,ou=users,dc=exalt,dc=ps' 2018-09-19 15:29:24,638+03 INFO API: <--Authn.InvokeCommands.AUTHENTICATE_CREDENTIALS profile='ldap23.exalt.ps' result=CREDENTIALS_INVALID 2018-09-19 15:29:24,642+03 SEVERE Authn.Result code is: CREDENTIALS_INVALID [ ERROR ] Login sequence failed Please investigate details of the failure (search for lines containing SEVERE log level). Select test sequence to execute (Done, Abort, Login, Search) [Abort]:

2 1

[ANN] oVirt 4.2.7 First Release Candidate is now available
by Sandro Bonazzola 19 Sep '18

19 Sep '18

The oVirt Project is pleased to announce the availability of the oVirt 4.2.7 First Release Candidate, as of September 19th, 2018. This update is a release candidate of the seventh in a series of stabilization updates to the 4.2 series. This is pre-release software. This pre-release should not to be used in production. This release is available now for: * Red Hat Enterprise Linux 7.5 or later * CentOS Linux (or similar) 7.5 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.5 or later * CentOS Linux (or similar) 7.5 or later See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is available - oVirt Node is available [2] Additional Resources: * Read more about the oVirt 4.2.7 release highlights: http://www.ovirt.org/release/4.2.7/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.2.7/ [2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…>

1 0

How to change host ips in engine database
by Jayme 19 Sep '18

19 Sep '18

I changed engine and host ips to a totally different subnet. My cluster is up and engine is working but I'm seeing that network is out of sync. If I attempt to sync the network it's changing the host ips back to the old subnet. I assume I changed the IPS improperly. How can I update the Ovirt engine db and change the IPS manaully so when the sync operation occurs it sets the new and proper ips? The engine loses connectivity with the host when it changes the subnet back to the original since it has no routes to it

3 3

RPC call StoragePool.connect failed: Cannot find master domain
by jtorres＠bsc.es 19 Sep '18

19 Sep '18

Hi all, I'm testing the new oVirt version 4.2.6, with the ovirt-engine installed as a service in a physical host. I tried to recover an engine-backup from a previous ovirt deployment, where the ovirt-engine was self-hosted inside a VM , and it seems that all work properly, because the cluster, hosts, and network configuration was correctly redeployed. The problem was when in the new cluster, I put all the nodes on Maintenance to upgrade it, and when they go back to the UP state, the datacenter was on a Non Responsive Status, because the Master Storage Domain is Inactive, and if I try to reactivate it, I obtain this error message: Failed Activating Storage Domain gpfs_kvm on Data Center BSC-CNS I don't have any hosts in the cluster as a SPM. Due to this situacion, I've some questions: It's possible to force one host to be an SPM? I failed when I put all the nodes on maintenance to upgrade, beacause it's better to maintain one host active as an SPM to protect the cluster, and the storage? Maybe the restored config from a diferent architecture (hosted-engine vs engine installed on host), can affect the Storage? (Previously the Master Storage Domain was on NFS, but I delete it and changed the role of Master to one Posix domain added) At log level on one compute, I can see this events: 2018-09-19 11:40:11,878+0200 INFO (jsonrpc/5) [vdsm.api] FINISH connectStoragePool error=Cannot find master domain: u'spUUID=32168096-b763-11e8-a7aa-000af7b8b6ba, msdUUID=cb99c414-0d93-41b9-9396-d8a607652b49' from=::ffff:10.2.1.101,58538, task_id=eedeba4d-99bc-4e18-8f24-f501b73e0da6 (api:50) 2018-09-19 11:40:11,879+0200 ERROR (jsonrpc/5) [storage.TaskManager.Task] (Task='eedeba4d-99bc-4e18-8f24-f501b73e0da6') Unexpected error (task:875) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File "<string>", line 2, in connectStoragePool File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 48, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 1035, in connectStoragePool spUUID, hostID, msdUUID, masterVersion, domainsMap) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 1097, in _connectStoragePool res = pool.connect(hostID, msdUUID, masterVersion) File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 700, in connect self.__rebuild(msdUUID=msdUUID, masterVersion=masterVersion) File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1274, in __rebuild self.setMasterDomain(msdUUID, masterVersion) File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1495, in setMasterDomain raise se.StoragePoolMasterNotFound(self.spUUID, msdUUID) StoragePoolMasterNotFound: Cannot find master domain: u'spUUID=32168096-b763-11e8-a7aa-000af7b8b6ba, msdUUID=cb99c414-0d93-41b9-9396-d8a607652b49' 2018-09-19 11:40:11,879+0200 INFO (jsonrpc/5) [storage.TaskManager.Task] (Task='eedeba4d-99bc-4e18-8f24-f501b73e0da6') aborting: Task is aborted: "Cannot find master domain: u'spUUID=32168096-b763-11e8-a7aa-000af7b8b6ba, msdUUID=cb99c414-0d93-41b9-9396-d8a607652b49'" - code 304 (task:1181) 2018-09-19 11:40:11,879+0200 ERROR (jsonrpc/5) [storage.Dispatcher] FINISH connectStoragePool error=Cannot find master domain: u'spUUID=32168096-b763-11e8-a7aa-000af7b8b6ba, msdUUID=cb99c414-0d93-41b9-9396-d8a607652b49' (dispatcher:82) 2018-09-19 11:40:11,880+0200 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call StoragePool.connect failed (error 304) in 0.31 seconds (__init__:573) 2018-09-19 11:40:11,907+0200 INFO (jsonrpc/1) [vdsm.api] START getSpmStatus(spUUID=u'32168096-b763-11e8-a7aa-000af7b8b6ba', options=None) from=::ffff:10.2.1.101,58538, task_id=4133fa8c-88f8-44c5-a8b8-18ac6c67771e (api:46) 2018-09-19 11:40:11,907+0200 INFO (jsonrpc/1) [vdsm.api] FINISH getSpmStatus error=Unknown pool id, pool not connected: (u'32168096-b763-11e8-a7aa-000af7b8b6ba',) from=::ffff:10.2.1.101,58538, task_id=4133fa8c-88f8-44c5-a8b8-18ac6c67771e (api:50) 2018-09-19 11:40:11,908+0200 ERROR (jsonrpc/1) [storage.TaskManager.Task] (Task='4133fa8c-88f8-44c5-a8b8-18ac6c67771e') Unexpected error (task:875) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File "<string>", line 2, in getSpmStatus File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 48, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 634, in getSpmStatus pool = self.getPool(spUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 350, in getPool raise se.StoragePoolUnknown(spUUID) StoragePoolUnknown: Unknown pool id, pool not connected: (u'32168096-b763-11e8-a7aa-000af7b8b6ba',) 2018-09-19 11:40:11,908+0200 INFO (jsonrpc/1) [storage.TaskManager.Task] (Task='4133fa8c-88f8-44c5-a8b8-18ac6c67771e') aborting: Task is aborted: "Unknown pool id, pool not connected: (u'32168096-b763-11e8-a7aa-000af7b8b6ba',)" - code 309 (task:1181) 2018-09-19 11:40:11,908+0200 ERROR (jsonrpc/1) [storage.Dispatcher] FINISH getSpmStatus error=Unknown pool id, pool not connected: (u'32168096-b763-11e8-a7aa-000af7b8b6ba',) (dispatcher:82) 2018-09-19 11:40:11,908+0200 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call StoragePool.getSpmStatus failed (error 309) in 0.01 seconds (__init__:573) I tried to base my situation on other cases that other people reported before, but nothing fits with exactly my logged errors. Could you suggest me anything? The infrastructure is now on testing, and I'm able to redeploy it if its possible. Thanks in advance.

1 0

external profile error
by mopiel games 19 Sep '18

19 Sep '18

hi , i am new user at ovirt . i use this command ovirt-engine-extension-aaa-ldap-setup to make external profile to my ovirt engine so i follow the manual and connect to the openLDAP successfully but at the end of the command , its ask to login i try to login but then its show this error [ ERROR ] Login sequence failed Please investigate details of the failure what should i do ? where can i find the log file for this command ?

1 0

my ovirt can not login to openldap server
by mustafa.taha.mu95＠gmail.com 19 Sep '18

19 Sep '18

i configure ovirt with self-host , and i want then to configure an external LDAP provider i follow the step in this link https://www.ovirt.org/documentation/admin-guide/chap-Users_and_Roles/ but this following error appear when i true to login: Enter user name: user002 Enter user password: [ INFO ] Executing login sequence... Login output: 2018-09-13 12:59:01,015+03 INFO ======================================================================== 2018-09-13 12:59:01,032+03 INFO ============================ Initialization ============================ 2018-09-13 12:59:01,033+03 INFO ======================================================================== 2018-09-13 12:59:01,064+03 INFO Loading extension 'ldap23.exalt.ps-authn' 2018-09-13 12:59:01,119+03 INFO Extension 'ldap23.exalt.ps-authn' loaded 2018-09-13 12:59:01,122+03 INFO Loading extension 'ldap23.exalt.ps-authz' 2018-09-13 12:59:01,130+03 INFO Extension 'ldap23.exalt.ps-authz' loaded 2018-09-13 12:59:01,130+03 INFO Initializing extension 'ldap23.exalt.ps-authn' 2018-09-13 12:59:01,131+03 INFO [ovirt-engine-extension-aaa-ldap.authn::ldap23.exalt.ps-authn] Creating LDAP pool 'authz' 2018-09-13 12:59:01,628+03 INFO [ovirt-engine-extension-aaa-ldap.authn::ldap23.exalt.ps-authn] LDAP pool 'authz' information: vendor='null' version='null' 2018-09-13 12:59:01,629+03 INFO [ovirt-engine-extension-aaa-ldap.authn::ldap23.exalt.ps-authn] Creating LDAP pool 'authn' 2018-09-13 12:59:01,882+03 INFO [ovirt-engine-extension-aaa-ldap.authn::ldap23.exalt.ps-authn] LDAP pool 'authn' information: vendor='null' version='null' 2018-09-13 12:59:01,882+03 INFO Extension 'ldap23.exalt.ps-authn' initialized 2018-09-13 12:59:01,883+03 INFO Initializing extension 'ldap23.exalt.ps-authz' 2018-09-13 12:59:01,883+03 INFO [ovirt-engine-extension-aaa-ldap.authz::ldap23.exalt.ps-authz] Creating LDAP pool 'authz' 2018-09-13 12:59:02,168+03 INFO [ovirt-engine-extension-aaa-ldap.authz::ldap23.exalt.ps-authz] LDAP pool 'authz' information: vendor='null' version='null' 2018-09-13 12:59:02,169+03 INFO [ovirt-engine-extension-aaa-ldap.authz::ldap23.exalt.ps-authz] Available Namespaces: [dc=exalt,dc=ps] 2018-09-13 12:59:02,169+03 INFO Extension 'ldap23.exalt.ps-authz' initialized 2018-09-13 12:59:02,169+03 INFO Start of enabled extensions list 2018-09-13 12:59:02,170+03 INFO Instance name: 'ldap23.exalt.ps-authn', Extension name: 'ovirt-engine-extension-aaa-ldap.authn', Version: '1.3.7', Notes: 'Display name: ovirt-engine-extension-aaa-ldap-1.3.7-1.el7.centos', License: 'ASL 2.0', Home: 'http://www.ovirt.org', Author 'The oVirt Project', Build interface Version: '0', File: '/tmp/tmp1j67ra/extensions.d/ldap23.exalt.ps-authn.properties', Initialized: 'true' 2018-09-13 12:59:02,170+03 INFO Instance name: 'ldap23.exalt.ps-authz', Extension name: 'ovirt-engine-extension-aaa-ldap.authz', Version: '1.3.7', Notes: 'Display name: ovirt-engine-extension-aaa-ldap-1.3.7-1.el7.centos', License: 'ASL 2.0', Home: 'http://www.ovirt.org', Author 'The oVirt Project', Build interface Version: '0', File: '/tmp/tmp1j67ra/extensions.d/ldap23.exalt.ps-authz.properties', Initialized: 'true' 2018-09-13 12:59:02,170+03 INFO End of enabled extensions list 2018-09-13 12:59:02,170+03 INFO ======================================================================== 2018-09-13 12:59:02,170+03 INFO ============================== Execution =============================== 2018-09-13 12:59:02,170+03 INFO ======================================================================== 2018-09-13 12:59:02,171+03 INFO Iteration: 0 2018-09-13 12:59:02,171+03 INFO Profile='ldap23.exalt.ps' authn='ldap23.exalt.ps-authn' authz='ldap23.exalt.ps-authz' mapping='null' 2018-09-13 12:59:02,171+03 INFO API: -->Authn.InvokeCommands.AUTHENTICATE_CREDENTIALS profile='ldap23.exalt.ps' user='user002' 2018-09-13 12:59:02,198+03 INFO API: <--Authn.InvokeCommands.AUTHENTICATE_CREDENTIALS profile='ldap23.exalt.ps' result=CREDENTIALS_INVALID 2018-09-13 12:59:02,203+03 SEVERE Authn.Result code is: CREDENTIALS_INVALID [ ERROR ] Login sequence failed Please investigate details of the failure (search for lines containing SEVERE log level). can anybody help ?

2 2

Re: my ovirt can not login to openldap server
by mustafa taha 19 Sep '18

19 Sep '18

i make my CA in ldap server and import CRT file to ovirt-self-host , i try choose insecure option put nothing has changed the error still appears . do you have any suggestion ? Sent from Mail for Windows 10

1 0

could ovirt manage physics machine
by du_hongyu＠yeah.net 19 Sep '18

19 Sep '18

HI everyone I want to manage physics machine by oVirt， but I do not find any info , could give me some suggestion? Regards Hongyu Du

2 2

Errors when migrate VMWare to RHV
by Xiaoyu Liu 19 Sep '18

19 Sep '18

Hi All I met two kinds of error when I migrate VMWare VM to RHV using virt-v2v. Any suggestion? Thank in advanced. 1: After executing the next command to migrate a VM, windows2008R2.ova from VMWare to RHV, everything looks OK in command line interface. But we could not find the migrated VM in RHV web console. Why? >virt-v2v -i ova windows2008R2.ova -on windows2008R4.ova -o libvirt -of qcow2 -os Appliances1 -n ovirtmgmt 2: When executed the next command to migrate a VM from VMWare to RHV, an error message came up >virt-v2v -ic esx://XX.XX.XX.XX/?no_verify=1 -os /data/images -of raw --bridge vdsm-ovirtmgmt test_linux Error message virt-v2v: Output pool /data/images is not a valid storage pool. BRs Xiaoyu

1 0

gdeploy fails for unsupported disk (script problem)
by Jeremy Tourville 19 Sep '18

19 Sep '18

It seems as though there is a problem with the grafton sanity check script. It took me a moment to spot the error below. Note the inconsistencies in the host names. changed: [obe.cyber-range.lan] (this is the correct piece of info) ping: ovir-be.cyber-range.lan (the ping portion changed the host name somehow) I'm not quite strong enough with scripting to fix it. Can anyone take a look at it? [root@vmh ~]# gdeploy -c gdeploy.conf -vv ansible-playbook 2.6.2 config file = /etc/ansible/ansible.cfg configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible-playbook python version = 2.7.5 (default, Jul 13 2018, 13:06:57) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)] Using /etc/ansible/ansible.cfg as config file PLAYBOOK: run-script.yml *********************************************************************************************************************************************** 1 plays in /tmp/tmpubmQdM/run-script.yml PLAY [gluster_servers] ************************************************************************************************************************************************* META: ran handlers TASK [Run a shell script] ********************************************************************************************************************************************** task path: /tmp/tmpubmQdM/run-script.yml:7 changed: [obe.cyber-range.lan] => (item=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d /dev/sda -h ovir-be.cyber-range.lan) => {"changed": true, "failed_when_result": false, "item": "/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d /dev/sda -h ovir-be.cyber-range.lan", "rc": 0, "stderr": "Shared connection to obe.cyber-range.lan closed.\r\n", "stderr_lines": ["Shared connection to obe.cyber-range.lan closed."], "stdout": "ping: ovir-be.cyber-range.lan: Name or service not known\r\nping failed unable to reach ovir-be.cyber-range.lan\r\nUsage: grep [OPTION]... PATTERN [FILE]...\r\nTry 'grep --help' for more information.\r\n", "stdout_lines": ["ping: ovir-be.cyber-range.lan: Name or service not known", "ping failed unable to reach ovir-be.cyber-range.lan", "Usage: grep [OPTION]... PATTERN [FILE]...", "Try 'grep --help' for more information."]} META: ran handlers META: ran handlers PLAY RECAP ************************************************************************************************************************************************************* obe.cyber-range.lan : ok=1 changed=1 unreachable=0 failed=0 Error: Unsupported disk type! Only ['raid10', 'raid5', 'raid6', 'jbod'] are supported BTW, this is directly related to my previous post: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/IPSNXA3GHYFU63… . I did change some parameters since then. I made sure I blacklisted my multipath device and dont have GPT label in the MBR. This is the most recent results of my efforts. Closer but not done quite yet.... 😉

1 0