[ovirt-users] Error trying to add new hosted-engine host to upgraded oVirt cluster

Sandro Bonazzola sbonazzo at redhat.com
Thu Nov 13 16:01:55 UTC 2014


Il 13/11/2014 15:33, David King ha scritto:
> Hi,
> 
> Thanks for the patch - that appears to solve the lockspace problem.
> 
> Once I got past that error I got a second error at the CPU selection phase:
> 
>     [ ERROR ] Failed to execute stage 'Environment customization': Invalid CPU type specified: None
> 
> Investigating further I realized that I had not pulled the answers from the first host.  I switched to the first host and have added the new host
> without any issues.
> 
> Thanks for the help,

thanks for your feedback and for having tested the patch!

> 
> -David 
> 
> 
> On Thu, Nov 13, 2014 at 3:36 AM, Sandro Bonazzola <sbonazzo at redhat.com <mailto:sbonazzo at redhat.com>> wrote:
> 
>     Il 13/11/2014 09:12, Jiri Moskovcak ha scritto:
>     > On 11/12/2014 04:20 PM, Sandro Bonazzola wrote:
>     >> Il 12/11/2014 16:10, David King ha scritto:
>     >>> Hi everyone,
>     >>>
>     >>> I have upgraded my oVirt 3.4 hosted engine cluster to oVirt 3.5 using the
>     >>> upgrade instructions on the Wiki.  Everything appears to be working fine
>     >>> after the upgrade.
>     >>>
>     >>> However, I am now trying to add a new host to the hosted engine
>     >>> configuration but the hosted-engine --deploy fails after sshing the answers
>     >>> file from the upgraded primary configuration.  The following errors can be
>     >>> found in the setup log:
>     >>>
>     >>>
>     >>> Answer file lacks lockspace UUIDs, please use an answer file generated from
>     >>>> the same version you are using on this additional host
>     >>
>     >> Can you please open a BZ about this issue so we can track it?
>     >> Jiri, Martin, is the file backend able to handle this kind of upgrade?
>     >
>     > Hi Sandro,
>     > yes, it is able to handle it, the lockspace uuid is needed only form iscsi (lvm based) storage, which is not the case when upgrading from 3.4, so we
>     > should be safe skipping the check for lockspace UUID in the setup if the storage is on nfs.
>     >
>     > --Jirka
>     >
>     > @David, I'm afraid the setup is not able to add host to the cluster created in 3.4, the workaround might be to deploy the host with the setup from 3.4
>     > and then update it. Sorry for the inconvenience :-/
> 
>     David, can you apply this patch http://gerrit.ovirt.org/35104 on the host you're adding to the cluster?
>     It should solve your issue.
> 
>     >
>     > --Jirka
>     >
>     >>
>     >>
>     >>>
>     >>>
>     >>> I confirmed that the answers file on the upgraded host does not have any
>     >>> lockspace UUIDs:
>     >>>
>     >>> OVEHOSTED_STORAGE/storageDatacenterName=str:hosted_datacenter
>     >>>> OVEHOSTED_STORAGE/storageDomainName=str:hosted_storage
>     >>>> OVEHOSTED_STORAGE/storageType=none:None
>     >>>> OVEHOSTED_STORAGE/volUUID=str:da160775-07fe-4569-b45f-03be0c5896a5
>     >>>> OVEHOSTED_STORAGE/domainType=str:nfs3
>     >>>> OVEHOSTED_STORAGE/imgSizeGB=str:25
>     >>>> OVEHOSTED_STORAGE/storageDomainConnection=str:192.168.8.12 <http://192.168.8.12>:
>     >>>> /mnt/data2/vm/engine
>     >>>> OVEHOSTED_STORAGE/connectionUUID=str:880093ea-b0c1-448d-ac55-cde99feebc23
>     >>>> OVEHOSTED_STORAGE/spUUID=str:5e7ff7c2-6e75-4ba8-a5cc-e8dc5d37e478
>     >>>> OVEHOSTED_STORAGE/imgUUID=str:c9466bb6-a78c-4caa-bce3-22c87a5f3f1a
>     >>>> OVEHOSTED_STORAGE/sdUUID=str:b12fd59c-380a-40b3-b7f2-02d455de1d3b
>     >>>
>     >>>
>     >>> Is there something I can do to update the answers file on the updated 3.5
>     >>> working host so this will work?
>     >>>
>     >>> Thanks,
>     >>> David
>     >>>
>     >>> PS: Here is the relevant section of the hosted-engine setup log file:
>     >>>
>     >>> 2014-11-11 22:57:04 DEBUG otopi.context context._executeMethod:138 Stage
>     >>>> validation METHOD
>     >>>> otopi.plugins.ovirt_hosted_engine_setup.sanlock.lockspace.Plugin._validation
>     >>>> 2014-11-11 22:57:04 DEBUG otopi.context context._executeMethod:152 method
>     >>>> exception
>     >>>> Traceback (most recent call last):
>     >>>>    File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in
>     >>>> _executeMethod
>     >>>>      method['method']()
>     >>>>    File
>     >>>> "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/sanlock/lockspace.py",
>     >>>> line 102, in _validation
>     >>>>      'Answer file lacks lockspace UUIDs, please use an '
>     >>>> RuntimeError: Answer file lacks lockspace UUIDs, please use an answer file
>     >>>> generated from the same version you are using on this additional host
>     >>>> 2014-11-11 22:57:04 ERROR otopi.context context._executeMethod:161 Failed
>     >>>> to execute stage 'Setup validation': Answer file lacks lockspace UUIDs,
>     >>>> please use an answer file generated from the same version you are using on
>     >>>> this additional host
>     >>>> 2014-11-11 22:57:04 DEBUG otopi.context context.dumpEnvironment:490
>     >>>> ENVIRONMENT DUMP - BEGIN
>     >>>> 2014-11-11 22:57:04 DEBUG otopi.context context.dumpEnvironment:500 ENV
>     >>>> BASE/error=bool:'True'
>     >>>> 2014-11-11 22:57:04 DEBUG otopi.context context.dumpEnvironment:500 ENV
>     >>>> BASE/exceptionInfo=list:'[(<type 'exceptions.RuntimeError'>,
>     >>>> RuntimeError('Answer file lacks lockspace UUIDs, please use an answer file
>     >>>> generated from the same version you are using on this additional host',),
>     >>>> <traceback object at 0x34c85a8>)]'
>     >>>> 2014-11-11 22:57:04 DEBUG otopi.context context.dumpEnvironment:504
>     >>>> ENVIRONMENT DUMP - END
>     >>>> 2014-11-11 22:57:04 INFO otopi.context context.runSequence:417 Stage:
>     >>>> Clean up
>     >>>> 2014-11-11 22:57:04 DEBUG otopi.context context.runSequence:421 STAGE
>     >>>> cleanup
>     >>>> 2014-11-11 22:57:04 DEBUG otopi.context context._executeMethod:138 Stage
>     >>>> cleanup METHOD
>     >>>> otopi.plugins.ovirt_hosted_engine_setup.core.remote_answerfile.Plugin._cleanup
>     >>>> 2014-11-11 22:57:04 DEBUG otopi.context context._executeMethod:138 Stage
>     >>>> cleanup METHOD
>     >>>> otopi.plugins.ovirt_hosted_engine_setup.engine.add_host.Plugin._cleanup
>     >>>> 2014-11-11 22:57:04 DEBUG otopi.context context._executeMethod:138 Stage
>     >>>> cleanup METHOD
>     >>>> otopi.plugins.ovirt_hosted_engine_setup.pki.vdsmpki.Plugin._cleanup
>     >>>> 2014-11-11 22:57:04 DEBUG otopi.context context._executeMethod:138 Stage
>     >>>> cleanup METHOD
>     >>>> otopi.plugins.ovirt_hosted_engine_setup.storage.storage.Plugin._cleanup
>     >>>> 2014-11-11 22:57:04 DEBUG
>     >>>> otopi.plugins.ovirt_hosted_engine_setup.storage.storage
>     >>>> storage._spmStop:609 spmStop
>     >>>> 2014-11-11 22:57:04 DEBUG
>     >>>> otopi.plugins.ovirt_hosted_engine_setup.storage.storage
>     >>>> storage._cleanup:970 Not SPM?
>     >>>> Traceback (most recent call last):
>     >>>>    File
>     >>>> "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py",
>     >>>> line 968, in _cleanup
>     >>>>      self._spmStop()
>     >>>>    File
>     >>>> "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py",
>     >>>> line 617, in _spmStop
>     >>>>      raise RuntimeError(status_uuid)
>     >>>> RuntimeError: Not SPM
>     >>>> 2014-11-11 22:57:04 DEBUG
>     >>>> otopi.plugins.ovirt_hosted_engine_setup.storage.storage
>     >>>> storage._storagePoolConnection:580 disconnectStoragePool
>     >>>> 2014-11-11 22:57:08 DEBUG otopi.context context._executeMethod:138 Stage
>     >>>> cleanup METHOD
>     >>>> otopi.plugins.ovirt_hosted_engine_setup.vm.boot_disk.Plugin._cleanup
>     >>>> 2014-11-11 22:57:08 DEBUG otopi.context context._executeMethod:138 Stage
>     >>>> cleanup METHOD
>     >>>> otopi.plugins.ovirt_hosted_engine_setup.core.answerfile.Plugin._save_answers_at_cleanup
>     >>>> 2014-11-11 22:57:08 INFO
>     >>>> otopi.plugins.ovirt_hosted_engine_setup.core.answerfile
>     >>>> answerfile._save_answers:48 Generating answer file
>     >>>> '/etc/ovirt-hosted-engine/answers.conf'
>     >>>> 2014-11-11 22:57:09 INFO
>     >>>> otopi.plugins.ovirt_hosted_engine_setup.core.answerfile
>     >>>> answerfile._save_answers_at_cleanup:104 Answer file
>     >>>> '/etc/ovirt-hosted-engine/answers.conf' has been updated
>     >>>
>     >>>
>     >>>
>     >>> _______________________________________________
>     >>> Users mailing list
>     >>> Users at ovirt.org <mailto:Users at ovirt.org>
>     >>> http://lists.ovirt.org/mailman/listinfo/users
>     >>>
>     >>
>     >>
>     >
> 
> 
>     --
>     Sandro Bonazzola
>     Better technology. Faster innovation. Powered by community collaboration.
>     See how it works at redhat.com <http://redhat.com>
> 
> 


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com



More information about the Users mailing list