Hosted Engine Upgrades
by Gary Pedretty
What is the official recommended method in a Hosted Engine Data Center/Cluster to upgrade the hosted_engine VM. Applying the updates on the individual hosts is pretty straight forward using either the GUI or just running yum update on each host once they are in maintenance mode. But what about the engine? This is an engine vm that was created from the appliance rpm initially. The documentation seems to skip over applying the periodic updates except to the individual hosts.
Thanks
Gary
__________________
[cid:D51E31D3-90B6-4306-BCC8-4DA475005073]
5 years, 7 months
Slow vm transfer speed from vmware esxi 5
by Bernhard Dick
Hi,
currently I'm trying to move VMs from our vsphere 5 environment to
oVirt. While the io performance on oVirt and on the esxi platform is
quite well (about 100MByte/sec on a 1GBit storage link) the transfer
speed using the integrated v2v-feature is very slow (only 10MByte/sec).
That would result in transfer time of >24h for some machines.
Do you have any ideas how I can improve the transfer speed?
Regards
Bernhard Dick
5 years, 7 months
Error installing ovirt node
by Junaid Jadoon
Dear All,
I have Ovirt engine 4.2 and node version is 4.2.
After installing node in in ovirt engine when i try to install node it
gives following error
14:25:37,410+05 ERROR
[org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
(EE-ManagedThreadFactory-engine-Thread-19) [52669850] Host installation
failed for host 'bd8d007a-be92-4075-bba9-6cbeb890a1e5', 'node_2': Command
returned failure code 1 during SSH session 'root(a)192.168.20.20'
2018-02-27 14:25:37,416+05 INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-19) [52669850] START,
SetVdsStatusVDSCommand(HostName = node_2,
SetVdsStatusVDSCommandParameters:{hostId='bd8d007a-be92-4075-bba9-6cbeb890a1e5',
status='InstallFailed', nonOperationalReason='NONE',
stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 2b138e87
2018-02-27 14:25:37,423+05 INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-19) [52669850] FINISH,
SetVdsStatusVDSCommand, log id: 2b138e87
2018-02-27 14:25:37,429+05 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engine-Thread-19) [52669850] EVENT_ID:
VDS_INSTALL_FAILED(505), Host node_2 installation failed. Command returned
failure code 1 during SSH session 'root(a)192.168.20.20'.
2018-02-27 14:25:37,433+05 INFO
[org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
(EE-ManagedThreadFactory-engine-Thread-19) [52669850] Lock freed to object
'EngineLock:{exclusiveLocks='[bd8d007a-be92-4075-bba9-6cbeb890a1e5=VDS]',
sharedLocks=''}'
I have attached log file for your reference
Please help me out.
5 years, 7 months
VM fail to start with hook...
by Enrico Becchetti
Dear All,
I have three servers with VDSM and a vm with ovirt 4.2.4.5-1.el7, all
using a Centos 7.
I still need you for a problem with a virtual machine.
I needed to connect the tape of a hypervisor to a vm and then I changed
the Host Device by adding the ST driver.
After making this change the VM is no longer playing even after removing
this hook.
Does anyone have any ideas?
Thanks a lot
Best Regasrds
Enrico
--
_______________________________________________________________________
Enrico Becchetti Servizio di Calcolo e Reti
Istituto Nazionale di Fisica Nucleare - Sezione di Perugia
Via Pascoli,c/o Dipartimento di Fisica 06123 Perugia (ITALY)
Phone:+39 075 5852777 Mail: Enrico.Becchetti<at>pg.infn.it
______________________________________________________________________
5 years, 7 months
[aaa-ldap-setup] Login sequence fails on setup
by mopiel games
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]:
5 years, 7 months
How to change host ips in engine database
by Jayme
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
5 years, 7 months
RPC call StoragePool.connect failed: Cannot find master domain
by jtorres＠bsc.es
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.
5 years, 7 months
external profile error
by mopiel games
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 ?
5 years, 7 months
my ovirt can not login to openldap server
by mustafa.taha.mu95＠gmail.com
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 ?
5 years, 7 months
