[ovirt-users] since upgrade of hosted engine, its not starting anymore

[Wu, Qiong]

I can access the storage domain with vdsclient but the state is not online
or okay:

 

[root at ovirt ovirt-hosted-engine]# vdsClient -s 0 getStorageDomainInfo
48fb7be2-d8eb-44e4-8690-7770ccaf3766

        uuid = 48fb7be2-d8eb-44e4-8690-7770ccaf3766

        version = 3

        role = Regular

        remotePath = ovirt-nfs.lab:/engine

        type = NFS

        class = Data

        pool = ['90cb594c-3c65-4485-822f-e932f14fd18b']

        name = hosted_storage

 

also when I do getStoragePoolInfo  I get this: 

 

[root at ovirt ovirt-hosted-engine]# vdsClient -s 0 getStoragePoolInfo
90cb594c-3c65-4485-822f-e932f14fd18b

Unknown pool id, pool not connected:
('90cb594c-3c65-4485-822f-e932f14fd18b',)

 

Thanks for help, hope I can recover somehow from this L

 

Cheers

Qiong

 

 

Von: Wu, Qiong 
Gesendet: Dienstag, 5. Januar 2016 15:42
An: 'users at ovirt.org'
Betreff: since upgrade of hosted engine, its not starting anymore

 

Hi everyone,

 

I have an issue with my ovirt deployment with hosted engine.

After an upgrade of the hosted engine I am not able to start it anymore.

 

I see this in my vdsm.log

 

Thread-1323::ERROR::2016-01-05
15:36:48,489::dispatcher::76::Storage.Dispatcher::(wrapper) {'status':
{'message': "Unknown pool id, pool not connected:
('90cb594c-3c65-4485-822f-e932f14fd18b',)", 'code': 309}}

 

Is somebody able to help? I am kind of desperate already, as I tried lots of
things already, including changing dom_md/metadata at the storage domain

Gluster is working properly, I am able to connect and write via nfs.

 

Thanks & Cheers

Qiong

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20160105/d0a17ce0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5641 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20160105/d0a17ce0/attachment-0001.bin>