Re: [ovirt-users] "Could not connect host to Data Center" after rebooting, how to resolve?
Hi, Could you please attach the vdsm logs for the host for the time around the logs you pasted from the engine.log? Thanks, Gadi Ickowicz - Original Message - From: "Boudewijn Ector ICT" To: "users" Sent: Wednesday, April 30, 2014 5:09:39 PM Subject: [ovirt-users] "Could not connect host to Data Center" after rebooting, how to resolve? Hi list, I had to do some fsck-related things last week on my ovirt box (centos, single node and NFS on localhost). Afterwards ovirt refused to start VMs according to the webinterface because it can't connect host to Data Center. On my OS it works fine (I just replaced the IP by 'IP'): [root@server ovirt-engine]# df Filesystem1K-blocks Used Available Use% Mounted on /dev/mapper/vg_leiden-lv_root 516061406872592 42112108 15% / tmpfs 3978120 03978120 0% /dev/shm /dev/sdb1495844 99542 370702 22% /boot /dev/mapper/vg_server-lv_home 629902602584272 57206196 5% /home /dev/sda15814366992 4629615452 1184751540 80% /raid IP:/raid/ovirt/data 5814367232 4629615616 1184751616 80% /rhev/data-center/mnt/IP:_raid_ovirt_data IP:/raid/ovirt/iso 5814367232 4629615616 1184751616 80% /rhev/data-center/mnt/IP:_raid_ovirt_iso in my event log in the webinterface I found correlation ID 7a735111 . So grepping my logs for that one: engine.log:2014-04-30 15:59:22,851 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (ajp--127.0.0.1-8702-8) [7a735111] Lock Acquired to object EngineLock [exclusiveLocks= key: 6bee0e2d-961c-453d-a266-e4623f91e162 value: STORAGE engine.log:2014-04-30 15:59:22,888 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] Running command: ActivateStorageDomainCommand internal: false. Entities affected : ID: 6bee0e2d-961c-453d-a266-e4623f91e162 Type: Storage engine.log:2014-04-30 15:59:22,894 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] Lock freed to object EngineLock [exclusiveLocks= key: 6bee0e2d-961c-453d-a266-e4623f91e162 value: STORAGE engine.log:2014-04-30 15:59:22,895 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] ActivateStorage Domain. Before Connect all hosts to pool. Time:4/30/14 3:59 PM engine.log:2014-04-30 15:59:22,945 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] START, ActivateStorageDomainVDSCommand( storagePoolId = 0002-0002-0002-0002-00ec, ignoreFailoverLimit = false, storageDomainId = 6bee0e2d-961c-453d-a266-e4623f91e162), log id: 5fecb439 engine.log:2014-04-30 15:59:23,011 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] hostFromVds::selectedVds - server, spmStatus Unknown_Pool, storage pool Default engine.log:2014-04-30 15:59:23,015 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] START, ConnectStoragePoolVDSCommand(HostName = server, HostId = ff23de79-f17c-439d-939e-d8f3d9672367, storagePoolId = 0002-0002-0002-0002-00ec, vds_spm_id = 1, masterDomainId = 6bee0e2d-961c-453d-a266-e4623f91e162, masterVersion = 1), log id: 15866a95 engine.log:2014-04-30 15:59:23,151 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] FINISH, ConnectStoragePoolVDSCommand, log id: 15866a95 engine.log:2014-04-30 15:59:23,152 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] IrsBroker::Failed::ActivateStorageDomainVDS due to: IRSNonOperationalException: IRSGenericException: IRSErrorException: IRSNonOperationalException: Could not connect host to Data Center(Storage issue) engine.log:2014-04-30 15:59:23,156 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] FINISH, ActivateStorageDomainVDSCommand, log id: 5fecb439 engine.log:2014-04-30 15:59:23,157 ERROR [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] Command org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand throw Vdc Bll exception. With error message VdcBLLException: org.ovirt.engine.core.vdsbroker.irsbroker.IRSNonOperationalException: IRSGenericException: IRSErrorException: IRSNonOperationalException: Could not connect host to Data Center(Storage issue) (Failed with error ENGINE and code 5001) engine.log:2014-04-30 15:59:23,162 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] Command [id=
Re: [ovirt-users] Storage Domain Not Found After upgrade from 3.3.2 to 3.4
Hi Paul,
Great to hear that you were able to get 3.4 working.
It makes sense that vdsm complained about the changed metadata - in general it
is not a good idea to alter this yourself (and if you do, it is better to
delete the checksum entry entirely and then let vdsm recalculate it next time
it tries to read the metadata).
It is still strange that 3.3.2 had no issue if this information was still in
the metadata *before* the upgrade, but the solution would still be to remove
the reference to it somehow, although the preferred method would be to tell
vdsm cli commands to do it using (hope this never happens again, but listing it
here for reference anyway ;) ):
vdsClient -s 0 deactivateStorageDomain
and
vdsClient -s 0 detachStorageDomain
Thanks,
Gadi Ickowicz
- Original Message -
From: re...@mccleary.me.uk
To: "Gadi Ickowicz"
Cc: users@ovirt.org
Sent: Wednesday, April 30, 2014 10:44:29 PM
Subject: Re: [ovirt-users] Storage Domain Not Found After upgrade from 3.3.2 to
3.4
Hi Gadi,
I thought I would have a look around for this "missing" storage domain.
I searched all the storage areas and in the master domain directory
structure I found a metadata file which had a reference to this storage
domain ID under POOL_DOMAINS.
I edited this file and removed the offending domain ID (all the other
domain IDs matched those listed by vdsClient), whilst the host was in
maintenance mode.
s2data1_s2mgt_boot1/0a897f2e-1b01-4577-9f91-cd136ef4a978/dom_md/metadata:
POOL_DOMAINS=7b083758-45f9-4896-913d-11fe02043e6e:Active,e637bb04-a8b7-4c77-809c-d58051494c52:Active,0a897f2e-1b01-4577-9f91-cd136ef4a978:Active,c2c4ade6-049e-4159-a294-a0c151f4983d:Active,9a4a80a1-5377-4a94-ade3-e58183e916ae:Active
The storage domains failed to come online and this message was in vdsm.log:
Thread-105::ERROR::2014-04-30
20:10:54,292::dispatcher::67::Storage.Dispatcher.Protect::(run)
{'status': {'message': "Meta Data seal is broken (checksum mismatch):
'cksum = e8b290eebc9a70d822b38a81d25d9f11eae6f282, computed_cksum =
83d6a7876b6a915f69818490610306b0287efe6f'", 'code': 752}}
I had seen a _SHA_CKSUM parameter in the metadata file, so I changed
this to the computed value listed in the logfile and the storage domains
activated fine.
I then upgraded to 3.4 and when I took it out of maintenance mode,
everything came online fine :)
So it looks to me like 3.4 or the upgrade to it, has a problem with this
erroneous storage domain ID being in the metadata file, that didn't
cause a problem for 3.3.2. Either way both my servers are now running
3.4 :)
Thanks for all your help with this.
Cheers,
Paul
On 30/04/2014 06:48, Gadi Ickowicz wrote:
> Hi Paul,
>
> Looking at what you sent, it seems a bit strange - another domain was added
> to the data-center according to the logs you sent in the other mail (the ones
> after the upgrade).
> If you could send the engine logs for for the same time period and the engine
> upgrade log, there may be some information there, but currently the log you
> sent just starts from the fact that there is a missing storage domain, and it
> is already listed in the storage pool's metadata.
>
> In any case, it is (somewhat) good to hear that reverting to 3.3.2 at least
> returned the system to a sane state.
>
> Thanks,
> Gadi Ickowicz
>
> - Original Message -
> From: re...@mccleary.me.uk
> To: "Gadi Ickowicz"
> Cc: users@ovirt.org
> Sent: Tuesday, April 29, 2014 7:52:15 PM
> Subject: Re: [ovirt-users] Storage Domain Not Found After upgrade from 3.3.2
> to 3.4
>
> Hi Gadi,
>
> Thanks for the response.
>
> I've only just had chance to restore that node back, which completed
> fine and the DC and it's storage domains activated ok. So the
> ovirt-node is now fully functional again on the 3.3.2 version; the
> ovirt-engine server remains untouched on 3.4 and is working fine.
>
> I collected the requested info, but it doesn't list the ID you pulled
> out of the vdsm.log:
>
> [root@ovirt-node ~]# vdsClient -s 0 getStorageDomainsList
> e637bb04-a8b7-4c77-809c-d58051494c52
> 7b083758-45f9-4896-913d-11fe02043e6e
> c2c4ade6-049e-4159-a294-a0c151f4983d
> 0a897f2e-1b01-4577-9f91-cd136ef4a978
>
> I tried anyway to list against that ID and I get the storage domain
> doesn't exist error, but maybe that's because it really doesn't exist!?
> [root@ovirt-node ~]# vdsClient -s 0 getStorageDomainInfo
> 9a4a80a1-5377-4a94-ade3-e58183e916ae
> Storage domain does not exist: ('9a4a80a1-5377-4a94-ade3-e58183e916ae',)
>
> I grabbed the info against all the Storage Domain IDs from the list
> without issue:
> [root@ovirt-node ~]#
> ## Storage Domain: e637bb04-a8b7-4c77-809c-d58051494c52 ##
> uuid = e637bb04-a8b7-4c77-809c-d58051494c52
> pool = ['c713062f-300f-4256-9ac8-2d3fcfcdb002']
> lver = -1
> version = 3
> role = Regular
> remotePath = /vdsm_store/s2data1_s2usr_boot1
> spm_id = -1
> type = LOCALFS
>
[ovirt-users] "Could not connect host to Data Center" after rebooting, how to resolve?
Hi list, I had to do some fsck-related things last week on my ovirt box (centos, single node and NFS on localhost). Afterwards ovirt refused to start VMs according to the webinterface because it can't connect host to Data Center. On my OS it works fine (I just replaced the IP by 'IP'): [root@server ovirt-engine]# df Filesystem1K-blocks Used Available Use% Mounted on /dev/mapper/vg_leiden-lv_root 516061406872592 42112108 15% / tmpfs 3978120 03978120 0% /dev/shm /dev/sdb1495844 99542 370702 22% /boot /dev/mapper/vg_server-lv_home 629902602584272 57206196 5% /home /dev/sda15814366992 4629615452 1184751540 80% /raid IP:/raid/ovirt/data 5814367232 4629615616 1184751616 80% /rhev/data-center/mnt/IP:_raid_ovirt_data IP:/raid/ovirt/iso 5814367232 4629615616 1184751616 80% /rhev/data-center/mnt/IP:_raid_ovirt_iso in my event log in the webinterface I found correlation ID 7a735111 . So grepping my logs for that one: engine.log:2014-04-30 15:59:22,851 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (ajp--127.0.0.1-8702-8) [7a735111] Lock Acquired to object EngineLock [exclusiveLocks= key: 6bee0e2d-961c-453d-a266-e4623f91e162 value: STORAGE engine.log:2014-04-30 15:59:22,888 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] Running command: ActivateStorageDomainCommand internal: false. Entities affected : ID: 6bee0e2d-961c-453d-a266-e4623f91e162 Type: Storage engine.log:2014-04-30 15:59:22,894 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] Lock freed to object EngineLock [exclusiveLocks= key: 6bee0e2d-961c-453d-a266-e4623f91e162 value: STORAGE engine.log:2014-04-30 15:59:22,895 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] ActivateStorage Domain. Before Connect all hosts to pool. Time:4/30/14 3:59 PM engine.log:2014-04-30 15:59:22,945 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] START, ActivateStorageDomainVDSCommand( storagePoolId = 0002-0002-0002-0002-00ec, ignoreFailoverLimit = false, storageDomainId = 6bee0e2d-961c-453d-a266-e4623f91e162), log id: 5fecb439 engine.log:2014-04-30 15:59:23,011 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] hostFromVds::selectedVds - server, spmStatus Unknown_Pool, storage pool Default engine.log:2014-04-30 15:59:23,015 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] START, ConnectStoragePoolVDSCommand(HostName = server, HostId = ff23de79-f17c-439d-939e-d8f3d9672367, storagePoolId = 0002-0002-0002-0002-00ec, vds_spm_id = 1, masterDomainId = 6bee0e2d-961c-453d-a266-e4623f91e162, masterVersion = 1), log id: 15866a95 engine.log:2014-04-30 15:59:23,151 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] FINISH, ConnectStoragePoolVDSCommand, log id: 15866a95 engine.log:2014-04-30 15:59:23,152 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] IrsBroker::Failed::ActivateStorageDomainVDS due to: IRSNonOperationalException: IRSGenericException: IRSErrorException: IRSNonOperationalException: Could not connect host to Data Center(Storage issue) engine.log:2014-04-30 15:59:23,156 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] FINISH, ActivateStorageDomainVDSCommand, log id: 5fecb439 engine.log:2014-04-30 15:59:23,157 ERROR [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] Command org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand throw Vdc Bll exception. With error message VdcBLLException: org.ovirt.engine.core.vdsbroker.irsbroker.IRSNonOperationalException: IRSGenericException: IRSErrorException: IRSNonOperationalException: Could not connect host to Data Center(Storage issue) (Failed with error ENGINE and code 5001) engine.log:2014-04-30 15:59:23,162 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] Command [id=c2d8b433-f203-4d9e-b241-222eebf3dbae]: Compensating CHANGED_STATUS_ONLY of org.ovirt.engine.core.common.businessentities.StoragePoolIsoMap; snapshot: EntityStatusSnapshot [id=storagePoolId = 0002-0002-0002-0002-00ec, storageId = 6bee0e2d-961c-453d-a266-e4623f91e162, status=InActive]. engine.log:2014-04-30 15:59:23,170 INFO [org.ovirt.engine.c
Re: [ovirt-users] Storage Domain Not Found After upgrade from 3.3.2 to 3.4
Hi Gadi,
I thought I would have a look around for this "missing" storage domain.
I searched all the storage areas and in the master domain directory
structure I found a metadata file which had a reference to this storage
domain ID under POOL_DOMAINS.
I edited this file and removed the offending domain ID (all the other
domain IDs matched those listed by vdsClient), whilst the host was in
maintenance mode.
s2data1_s2mgt_boot1/0a897f2e-1b01-4577-9f91-cd136ef4a978/dom_md/metadata:
POOL_DOMAINS=7b083758-45f9-4896-913d-11fe02043e6e:Active,e637bb04-a8b7-4c77-809c-d58051494c52:Active,0a897f2e-1b01-4577-9f91-cd136ef4a978:Active,c2c4ade6-049e-4159-a294-a0c151f4983d:Active,9a4a80a1-5377-4a94-ade3-e58183e916ae:Active
The storage domains failed to come online and this message was in vdsm.log:
Thread-105::ERROR::2014-04-30
20:10:54,292::dispatcher::67::Storage.Dispatcher.Protect::(run)
{'status': {'message': "Meta Data seal is broken (checksum mismatch):
'cksum = e8b290eebc9a70d822b38a81d25d9f11eae6f282, computed_cksum =
83d6a7876b6a915f69818490610306b0287efe6f'", 'code': 752}}
I had seen a _SHA_CKSUM parameter in the metadata file, so I changed
this to the computed value listed in the logfile and the storage domains
activated fine.
I then upgraded to 3.4 and when I took it out of maintenance mode,
everything came online fine :)
So it looks to me like 3.4 or the upgrade to it, has a problem with this
erroneous storage domain ID being in the metadata file, that didn't
cause a problem for 3.3.2. Either way both my servers are now running
3.4 :)
Thanks for all your help with this.
Cheers,
Paul
On 30/04/2014 06:48, Gadi Ickowicz wrote:
Hi Paul,
Looking at what you sent, it seems a bit strange - another domain was added to
the data-center according to the logs you sent in the other mail (the ones
after the upgrade).
If you could send the engine logs for for the same time period and the engine
upgrade log, there may be some information there, but currently the log you
sent just starts from the fact that there is a missing storage domain, and it
is already listed in the storage pool's metadata.
In any case, it is (somewhat) good to hear that reverting to 3.3.2 at least
returned the system to a sane state.
Thanks,
Gadi Ickowicz
- Original Message -
From: re...@mccleary.me.uk
To: "Gadi Ickowicz"
Cc: users@ovirt.org
Sent: Tuesday, April 29, 2014 7:52:15 PM
Subject: Re: [ovirt-users] Storage Domain Not Found After upgrade from 3.3.2 to
3.4
Hi Gadi,
Thanks for the response.
I've only just had chance to restore that node back, which completed
fine and the DC and it's storage domains activated ok. So the
ovirt-node is now fully functional again on the 3.3.2 version; the
ovirt-engine server remains untouched on 3.4 and is working fine.
I collected the requested info, but it doesn't list the ID you pulled
out of the vdsm.log:
[root@ovirt-node ~]# vdsClient -s 0 getStorageDomainsList
e637bb04-a8b7-4c77-809c-d58051494c52
7b083758-45f9-4896-913d-11fe02043e6e
c2c4ade6-049e-4159-a294-a0c151f4983d
0a897f2e-1b01-4577-9f91-cd136ef4a978
I tried anyway to list against that ID and I get the storage domain
doesn't exist error, but maybe that's because it really doesn't exist!?
[root@ovirt-node ~]# vdsClient -s 0 getStorageDomainInfo
9a4a80a1-5377-4a94-ade3-e58183e916ae
Storage domain does not exist: ('9a4a80a1-5377-4a94-ade3-e58183e916ae',)
I grabbed the info against all the Storage Domain IDs from the list
without issue:
[root@ovirt-node ~]#
## Storage Domain: e637bb04-a8b7-4c77-809c-d58051494c52 ##
uuid = e637bb04-a8b7-4c77-809c-d58051494c52
pool = ['c713062f-300f-4256-9ac8-2d3fcfcdb002']
lver = -1
version = 3
role = Regular
remotePath = /vdsm_store/s2data1_s2usr_boot1
spm_id = -1
type = LOCALFS
class = Data
master_ver = 0
name = s2data1_s2usr_boot1
## Storage Domain: 7b083758-45f9-4896-913d-11fe02043e6e ##
uuid = 7b083758-45f9-4896-913d-11fe02043e6e
pool = ['f027ec99-913f-4f00-ac95-ad484c9c6a4b',
'c713062f-300f-4256-9ac8-2d3fcfcdb002']
lver = -1
version = 0
role = Regular
remotePath = ovirt-engine:/iso
spm_id = -1
type = NFS
class = Iso
master_ver = 0
name = ISO1_ZFS
## Storage Domain: c2c4ade6-049e-4159-a294-a0c151f4983d ##
uuid = c2c4ade6-049e-4159-a294-a0c151f4983d
pool = ['c713062f-300f-4256-9ac8-2d3fcfcdb002']
lver = -1
version = 3
role = Regular
remotePath = /vdsm_store/s2data1_s2mgt_app1
spm_id = -1
type = LOCALFS
class = Data
master_ver = 0
name = s2data1_s2mgt_app1
## Storage Domain: 0a897f2e-1b01-4577-9f91-cd136ef4a978 ##
uuid = 0a897f2e-1b01-4577-9f91-cd136ef4a978
pool = ['c713062f-300f-4256-9ac8-2d3fcfcdb002'
[ovirt-users] "Could not connect host to Data Center" after rebooting, how to resolve?
Hi list, I had to do some fsck-related things last week on my ovirt box (centos, single node and NFS on localhost). Afterwards ovirt refused to start VMs according to the webinterface because it can't connect host to Data Center. On my OS it works fine (I just replaced the IP by 'IP'): [root@server ovirt-engine]# df Filesystem1K-blocks Used Available Use% Mounted on /dev/mapper/vg_leiden-lv_root 516061406872592 42112108 15% / tmpfs 3978120 03978120 0% /dev/shm /dev/sdb1495844 99542 370702 22% /boot /dev/mapper/vg_server-lv_home 629902602584272 57206196 5% /home /dev/sda15814366992 4629615452 1184751540 80% /raid IP:/raid/ovirt/data 5814367232 4629615616 1184751616 80% /rhev/data-center/mnt/IP:_raid_ovirt_data IP:/raid/ovirt/iso 5814367232 4629615616 1184751616 80% /rhev/data-center/mnt/IP:_raid_ovirt_iso in my event log in the webinterface I found correlation ID 7a735111 . So grepping my logs for that one: engine.log:2014-04-30 15:59:22,851 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (ajp--127.0.0.1-8702-8) [7a735111] Lock Acquired to object EngineLock [exclusiveLocks= key: 6bee0e2d-961c-453d-a266-e4623f91e162 value: STORAGE engine.log:2014-04-30 15:59:22,888 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] Running command: ActivateStorageDomainCommand internal: false. Entities affected : ID: 6bee0e2d-961c-453d-a266-e4623f91e162 Type: Storage engine.log:2014-04-30 15:59:22,894 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] Lock freed to object EngineLock [exclusiveLocks= key: 6bee0e2d-961c-453d-a266-e4623f91e162 value: STORAGE engine.log:2014-04-30 15:59:22,895 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] ActivateStorage Domain. Before Connect all hosts to pool. Time:4/30/14 3:59 PM engine.log:2014-04-30 15:59:22,945 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] START, ActivateStorageDomainVDSCommand( storagePoolId = 0002-0002-0002-0002-00ec, ignoreFailoverLimit = false, storageDomainId = 6bee0e2d-961c-453d-a266-e4623f91e162), log id: 5fecb439 engine.log:2014-04-30 15:59:23,011 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] hostFromVds::selectedVds - server, spmStatus Unknown_Pool, storage pool Default engine.log:2014-04-30 15:59:23,015 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] START, ConnectStoragePoolVDSCommand(HostName = server, HostId = ff23de79-f17c-439d-939e-d8f3d9672367, storagePoolId = 0002-0002-0002-0002-00ec, vds_spm_id = 1, masterDomainId = 6bee0e2d-961c-453d-a266-e4623f91e162, masterVersion = 1), log id: 15866a95 engine.log:2014-04-30 15:59:23,151 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] FINISH, ConnectStoragePoolVDSCommand, log id: 15866a95 engine.log:2014-04-30 15:59:23,152 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] IrsBroker::Failed::ActivateStorageDomainVDS due to: IRSNonOperationalException: IRSGenericException: IRSErrorException: IRSNonOperationalException: Could not connect host to Data Center(Storage issue) engine.log:2014-04-30 15:59:23,156 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] FINISH, ActivateStorageDomainVDSCommand, log id: 5fecb439 engine.log:2014-04-30 15:59:23,157 ERROR [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] Command org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand throw Vdc Bll exception. With error message VdcBLLException: org.ovirt.engine.core.vdsbroker.irsbroker.IRSNonOperationalException: IRSGenericException: IRSErrorException: IRSNonOperationalException: Could not connect host to Data Center(Storage issue) (Failed with error ENGINE and code 5001) engine.log:2014-04-30 15:59:23,162 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-6-thread-49) [7a735111] Command [id=c2d8b433-f203-4d9e-b241-222eebf3dbae]: Compensating CHANGED_STATUS_ONLY of org.ovirt.engine.core.common.businessentities.StoragePoolIsoMap; snapshot: EntityStatusSnapshot [id=storagePoolId = 0002-0002-0002-0002-00ec, storageId = 6bee0e2d-961c-453d-a266-e4623f91e162, status=InActive]. engine.log:2014-04-30 15:59:23,170 INFO [org.ovirt.engine.c
[ovirt-users] oVirt Weekly Meeting Minutes -- 2014-04-30
Minutes:http://ovirt.org/meetings/ovirt/2014/ovirt.2014-04-30-14.00.html Minutes (text): http://ovirt.org/meetings/ovirt/2014/ovirt.2014-04-30-14.00.txt Log: http://ovirt.org/meetings/ovirt/2014/ovirt.2014-04-30-14.00.log.html = #ovirt: oVirt Weekly Sync = Meeting started by doron at 14:00:33 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2014/ovirt.2014-04-30-14.00.log.html . Meeting summary --- * Agenda and roll Call (doron, 14:00:47) * infra update (doron, 14:00:49) * 3.4.z updates (doron, 14:00:50) * 3.5 status (doron, 14:00:52) * conferences and workshops (doron, 14:00:53) * other topics (doron, 14:00:55) * infra update (doron, 14:01:03) * infra ain updates;additional slaves based on OS1 added, (doron, 14:04:47) * Also, more work on new tasks (host-deploy and hosted-engine-setup) (doron, 14:05:28) * 3.4.z updates (doron, 14:05:41) * 3.4.1 branched today. we're preparing to release 3.4.1 GA on May 7th. No blockers currently. (doron, 14:07:19) * 3.5 status (doron, 14:07:50) * Gluster to update on 3.5 readiness. (doron, 14:10:39) * infra 3.5 feature readiness: 7 done, 3 in progress. All others should be re-evaluated and possibly postponed. (doron, 14:18:45) * integration 3.5 feature readiness: websocket on separate host and hosted-engine iSCSI support almost done. (doron, 14:20:44) * integration 3.5 feature readiness: DWH and Reports on separate host still in progress. (doron, 14:21:31) * integration 3.5 feature readiness: guest tools still requires some more design. (doron, 14:22:12) * network 3.5 readiness; The bridging_opts, ethtool_opts and the warning about the display network are being merged, and will be in by tomorrow. (doron, 14:26:34) * network 3.5 readiness; 1 feature ready, Neutron, both property features, and the display network warnings expected to make it by next week. Everything else will probably be postponed. (doron, 14:32:24) * sla 3,5 features update: iscsi for hosted engine almost done. 2 features postponed. 1 may slip and everything else should be ready in the coming week. (doron, 14:35:59) * UX 3.5 readiness: new look and feel should be ready. REST based UI postponed. (doron, 14:41:41) * virt 3.5 readiness: 7 completed, 6 should be ready and the rest should be reconsidered. (doron, 14:46:55) * storage 3.5 feature readiness: 2 features done. live merge should make it, possibly limited. sanlock fencing: at risk and the rest should be completed soon. (doron, 14:52:29) * Gluster 3.5 readiness: Gluster Top should be postponed. Everything else should make it by next week. (doron, 14:57:29) * dwh 3.5 readiness: 1 feature done. other 2 should make it in the next 1-2 weeks. (doron, 14:59:51) * node 3.5 readiness: registration feature may be postponed. Other 2 should make it on time. (doron, 15:01:02) * conferences and workshops (doron, 15:02:23) * bkp gathering locations of users who might be interested in helping with events. Please mail bkp if you want and can assist (doron, 15:03:46) * other topics (doron, 15:04:16) * A feature page cleanup project will be launched just after this meeting, pages that need datestamps added are listed here http://bit.ly/1iA1HQ3 more info will be provided in the devel list. (doron, 15:08:30) * LINK: http://www.redhat.com/about/news/press-archive/2014/4/red-hat-to-acquire-inktank-provider-of-ceph (bkp, 15:09:03) * oVirt may gain from Red Hat's acquisition of Ceph. See: http://www.redhat.com/about/news/press-archive/2014/4/red-hat-to-acquire-inktank-provider-of-ceph (doron, 15:09:48) * ACTION: please mail bkp if you have a stash of ovirt apparel. (doron, 15:10:31) * bkp will be in FISL and a CentOS dojo in Brazil next week. Expect slower response time. (doron, 15:11:24) * Thanks all for coming. Happy Labor day tomorrow (doron, 15:12:54) Meeting ended at 15:12:57 UTC. Action Items * please mail bkp if you have a stash of ovirt apparel. Action Items, by person --- * bkp * please mail bkp if you have a stash of ovirt apparel. * **UNASSIGNED** * (none) People Present (lines said) --- * doron (155) * ovedo (22) * bkp (15) * lvernia (14) * sbonazzo (10) * mskrivanek (9) * amureini_ (8) * awels (8) * ydary (7) * danken (6) * sahina (4) * dcaro (4) * knesenko (2) * gchaplik (2) * jb_netapp (2) * ovirtbot (2) * dneary (1) * acathrow1 (1) * sherold (1) * jmoskovc (1) * fsimonce (1) * mburns (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] ovirt-guest-agent
Hello, Following http://www.ovirt.org/Ovirt_guest_agent Where can I get disks usage or os version or several other informations through the webadmin or with an other way? -- Nathanaël Blanchet Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanc...@abes.fr ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Bugzilla Reports & DWH Components Name Change.
Hi, We have recently changed the name of bugzilla components of Reports & DWH: ovirt-report -> ovirt-engine-reports ovirt-dwh -> ovirt-engine-dwh Please update your queries accordingly. Thanks! --- Yaniv Dary BI Software Engineer Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 72306 Email: yd...@redhat.com IRC : Yaniv D ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] ovirt 3.4 and FreeIPA authentication
- Original Message - > From: "Yair Zaslavsky" > To: "Peter Harris" > Cc: Users@ovirt.org, "Sven Kieske" > Sent: Wednesday, April 30, 2014 12:19:57 PM > Subject: Re: [ovirt-users] ovirt 3.4 and FreeIPA authentication > > > As mentioned by Sven, > As far as I know all these bugs were solved for 3.4.1 > However, > > if possible, I would like to get the following information - > > a. select user_id, username, group_ids from users where username = > ''; > b. select id, name from ad_groups; of course this should be collected from the database. > > > > - Original Message - > > From: "Peter Harris" > > To: Users@ovirt.org > > Sent: Wednesday, April 30, 2014 11:55:04 AM > > Subject: [ovirt-users] ovirt 3.4 and FreeIPA authentication > > > > I have just create an oVirt 3.4 server as part of my test environment prior > > to moving from my production 3.3 environment. > > > > I authenticate against FreeIPA 3.0.0 > > > > I generally add a group in IPA, add the permissions in ovirt against the > > group, and then add/remove users from the groups in IPA. > > > > With oVirt3.4, I have justed added my vmadmin IPA group to ovirt, and given > > it the SuperUser role. > > > > I try to log in to oVirt 3.4 as myself (I am in the vmadmin group), and I > > can authenticate fine, but I do not have SuperUser privileges. If I log in > > to my live Ovirt (3.3), I do have SuperUser privileges. > > > > Has something changed? Or is there an extra step I have to take that I have > > missed to propogate privileges. > > > > Thanks > > > > Peter > > > > P.S. All work done in the ovirt Admin portal gui so far, not tried the CLI > > yet. > > > > ___ > > Users mailing list > > Users@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] ovirt 3.4 and FreeIPA authentication
As mentioned by Sven, As far as I know all these bugs were solved for 3.4.1 However, if possible, I would like to get the following information - a. select user_id, username, group_ids from users where username = ''; b. select id, name from ad_groups; - Original Message - > From: "Peter Harris" > To: Users@ovirt.org > Sent: Wednesday, April 30, 2014 11:55:04 AM > Subject: [ovirt-users] ovirt 3.4 and FreeIPA authentication > > I have just create an oVirt 3.4 server as part of my test environment prior > to moving from my production 3.3 environment. > > I authenticate against FreeIPA 3.0.0 > > I generally add a group in IPA, add the permissions in ovirt against the > group, and then add/remove users from the groups in IPA. > > With oVirt3.4, I have justed added my vmadmin IPA group to ovirt, and given > it the SuperUser role. > > I try to log in to oVirt 3.4 as myself (I am in the vmadmin group), and I > can authenticate fine, but I do not have SuperUser privileges. If I log in > to my live Ovirt (3.3), I do have SuperUser privileges. > > Has something changed? Or is there an extra step I have to take that I have > missed to propogate privileges. > > Thanks > > Peter > > P.S. All work done in the ovirt Admin portal gui so far, not tried the CLI > yet. > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] enabling rhevm fencing agent in ovirt
Hi Jason Can you please attache engine & VDSM logs , I would like to see the calls in order to analyze that Thanks - Original Message - > From: "Jason Brooks" > To: users@ovirt.org > Sent: Tuesday, April 29, 2014 1:32:38 AM > Subject: [ovirt-users] enabling rhevm fencing agent in ovirt > > Hi everyone -- > > I'm trying to enable the fence_rhevm agent in ovirt in order to enable > fencing on the (ovirt-hosted) virtual hosts I use for testing. > > I followed the directions at > https://www.mail-archive.com/users@ovirt.org/msg13433.html to add the > agent to ovirt. > > I appended "rhevm:secure=ssl,slot=plug" to the fencing agent option > mapping list in the VdsFenceOptionMapping rows of vdc_options, and I > appended "rhevm" to the list of agents in the VdsFenceType rows of > vdc_options. > > After restarting ovirt-engine, the rhevm agent appears in the list of > agents in the power management dialog. I supply the correct address, > user name & password values, and put the name of my VM into the slot > field (which I mapped to plug, above). > > The test fails with the message: > > "Test Failed, Parse error: Ignoring unknown option 'plug=ovirt34-el3' > Failed: You have to enter plug number Please use '-h' for usage" > > When I run a test directly, w/ "fence_rhevm -o fence_rhevm -o status -a > MYHOSTNAME -l admin@internal -p MYPASSWORD --ssl --plug=ovirt34-el3" the > fencing agent returns the status as expected. > > It seems that ovirt engine is deciding that my (valid) option is > invalid, so it withholds the option from the fencing agent, which then > complains that the withheld element is missing. > > Any ideas? > > I'm using ovirt 3.4 (self-hosted) on CentOS 6.5 hosts, which are running > on ovirt 3.4 (all in one engine) on Fedora 19 hosts. > > Here's the error passage from the vdsm.log: > > Thread-10347::DEBUG::2014-04-28 > 18:19:23,691::API::1160::vds::(fenceNode) rc 1 in agent=fence_rhevm > ipaddr=MYHOSTNAME > login=admin@internal > action=status > passwd= > plug=ovirt34-el3 > ssl=yes out err Parse error: Ignoring unknown option 'plug=ovirt34-el3' > Failed: You have to enter plug number > Please use '-h' for usage > > > Thanks, Jason > > > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] ovirt 3.4 and FreeIPA authentication
Hi, I recall there where some bugs which didn't propagate the correct rights inherited by group membership to all group members, maybe that's related? There are some BZ's for it, I don't know atm if this was resolved for 3.4.1 ? HTH -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] ovirt 3.4 and FreeIPA authentication
I have just create an oVirt 3.4 server as part of my test environment prior to moving from my production 3.3 environment. I authenticate against FreeIPA 3.0.0 I generally add a group in IPA, add the permissions in ovirt against the group, and then add/remove users from the groups in IPA. With oVirt3.4, I have justed added my vmadmin IPA group to ovirt, and given it the SuperUser role. I try to log in to oVirt 3.4 as myself (I am in the vmadmin group), and I can authenticate fine, but I do not have SuperUser privileges. If I log in to my live Ovirt (3.3), I do have SuperUser privileges. Has something changed? Or is there an extra step I have to take that I have missed to propogate privileges. Thanks Peter P.S. All work done in the ovirt Admin portal gui so far, not tried the CLI yet. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] [ovirt-devel] oVirt 3.4.1 branching
Il 29/04/2014 08:56, Sandro Bonazzola ha scritto: > Hi, > we're going to create ovirt-engine-3.4.1 branch tomorrow morning 08:00 UTC in > order to allow 3.4.2 development starting on 3.4 branch while we prepare > for 3.4.1 GA release. > So starting tomorrow morning, if you have patches targeted to 3.4.1 you'll > need to push them on 3.4.1 branch too. > Thanks, > ovirt-engine-3.4.1 branch has been created with hash f6f9e85200ccdba0a161b248842e5b6b1d1eeb32. version bump patch for ovirt-engine-3.4 branch have been pushed: http://gerrit.ovirt.org/27235 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
