Hi, affected version: oVirt 3.3 (ManagementNode) how to reproduce: setup 2 data centers with local storage, add data master storage domains to these 2 data centers add another data center with local storage, try to add another master storage domain. expected result: the data domain gets created just like the 2 before actual result: ovirt management complains that the data domain already exists, which is not true. This behaviour was introduced with version 3.3, we didn't see this in version 3.2 This is regardless of node versions. I would at first like to know if anybody can reproduce this? If this is the case I would create a bugzilla entry. Regards Sven _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Here is the excerpt from engine.log: 2013-10-10 15:06:06,390 INFO [org.ovirt.engine.core.bll.storage.AddStorageServerConnectionCommand] (ajp--127.0.0.1-8702-15) [_WEBADMIN_13422849_Configure_Local_Storage] Lock Acquired to object EngineLock [exclusiveLocks= key: /data/images/rhev value: STORAGE_CONNECTION , sharedLocks= ] 2013-10-10 15:06:06,390 WARN [org.ovirt.engine.core.bll.storage.AddStorageServerConnectionCommand] (ajp--127.0.0.1-8702-15) [_WEBADMIN_13422849_Configure_Local_Storage] CanDoAction of action AddStorageServerConnection failed. Reasons:VAR__ACTION__ADD,VAR__TYPE__STORAGE__CONNECTION,ACTION_TYPE_FAILED_STORAGE_CONNECTION_ALREADY_EXISTS 2013-10-10 15:06:06,391 INFO [org.ovirt.engine.core.bll.storage.AddStorageServerConnectionCommand] (ajp--127.0.0.1-8702-15) [_WEBADMIN_13422849_Configure_Local_Storage] Lock freed to object EngineLock [exclusiveLocks= key: /data/images/rhev value: STORAGE_CONNECTION , sharedLocks= ] Here is the API-Return of https://[your-rhevm-setup]/api/storagedomains: <storage_domains><storage_domain href="/api/storagedomains/e0c596b4-b751-46c7-8f5d-eaf21aab76a5" id="e0c596b4-b751-46c7-8f5d-eaf21aab76a5"><name>DATA_V3</name><link href="/api/storagedomains/e0c596b4-b751-46c7-8f5d-eaf21aab76a5/permissions" rel="permissions"/><link href="/api/storagedomains/e0c596b4-b751-46c7-8f5d-eaf21aab76a5/disks" rel="disks"/><type>data</type><master>true</master><storage><type>localfs</type><path>/home/DATA</path></storage><available>876173328384</available><used>47244640256</used><committed>32212254720</committed><storage_format>v3</storage_format></storage_domain><storage_domain href="/api/storagedomains/73407366-d658-4a37-ab25-6142b0f4381f" id="73407366-d658-4a37-ab25-6142b0f4381f"><name>DATA_V5</name><link href="/api/storagedomains/73407366-d658-4a37-ab25-6142b0f4381f/permissions" rel="permissions"/><link href="/api/storagedomains/73407366-d658-4a37-ab25-6142b0f4381f/disks" rel="disks"/><type>data</type><master>true</master><storage><type>localfs</type><path>/data/images/rhev</path></storage><available>922344226816</available><used>49392123904</used><committed>0</committed><storage_format>v3</storage_format></storage_domain></storage_domains> These are just our well known Storage Domains "DATA_V3" and "DATA_V5" from our hosts 3 and 5.

I tried to add another one for host 4, by putting the host into maintainence mode, and then clicking: "setup local storage" When you click then "ok" in the popup you get the error: "can't add storage connection, connection already exists"

The bugzilla entry seems not to fit as this is: a) no NFS Storage Domain

b) no Export Storage Domain

c) the name of our SD does not contain any spaces

d) the bug entry mentions this bug only occurs via api because the webfrontend doesn't allow to create SDs with spaces however how can I check if the postgres db doesn't contain any other storage domains, just to make 110% sure this is not this bug?

Hi Sven, What is the path of the third local storage domain you can't add. Could it be the same as the other existing connections (/home/DATA, /data/images/rhev)? It could be an issue of this bug https://bugzilla.redhat.com/1023739 - - Cannot create same Local SD path on different Hosts Regards, Maor On 10/10/2013 05:14 PM, Sven Kieske wrote: > I'm sorry, I misread the connections for the storage domains.. > > this is the output of the storageconnections: > > <storage_connections><storage > href="/api/storageconnections/b3eca2aa-5983-404f-af06-c7ca10b9fa23" > id="b3eca2aa-5983-404f-af06-c7ca10b9fa23"><type>localfs</type><path>/home/DATA</path></storage><storage > href="/api/storageconnections/87dc99f6-98fe-4828-99da-f228958748c0" > id="87dc99f6-98fe-4828-99da-f228958748c0"><type>localfs</type><path>/data/images/rhev</path></storage><storage > href="/api/storageconnections/84970346-ae22-49cf-8a4c-c1bd27a0b7a4" > id="84970346-ae22-49cf-8a4c-c1bd27a0b7a4"><address>managementserver32</address><type>nfs</type><path>/var/lib/exports/export</path></storage><storage > href="/api/storageconnections/1179a3b3-8f18-4696-bda8-094b7a2f5c35" > id="1179a3b3-8f18-4696-bda8-094b7a2f5c35"><address>managementserver32</address><type>nfs</type><path>/var/lib/exports/iso</path></storage></storage_connections> > > So this is one export domain, one iso domain and 2 localfs storage > domains, I suppose our two working ones. So no sign of this 5th > supposed connection? > > the fun part: the export domain does not show up any more in the > mangement, so I tried to delete the connection via curl: > > curl -X DELETE -H "Accept: application/xml" -u user:password > https://192.168.150.50/api/storageconnections/84970346-ae22-49cf-8a4c-c1b... > --insecure > > and got as response: > > <html><head><title>JBoss Web/7.0.13.Final - Error > report</title><style><!--H1 > {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} > H2 > {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} > H3 > {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} > BODY > {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B > {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} > P > {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A > {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> > </head><body><h1>HTTP Status 405 - </h1><HR size="1" > noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> > <u></u></p><p><b>description</b> <u>The specified HTTP method is not > allowed for the requested resource ().</u></p><HR size="1" > noshade="noshade"><h3>JBoss Web/7.0.13.Final</h3></body></html> > > so this method does not seem to be allowed? > > > Regards Sven > > >> >> https://[your-rhevm-setup]/api/storageconnections (!), please >> >> >>> I tried to add another one for host 4, by putting the host into >>> maintainence mode, and then clicking: "setup local storage" >>> When you click then "ok" in the popup you get the error: >>> >>> "can't add storage connection, connection already exists" >> >> So it means that you have a storage connection which is not used by any >> storage domain. One thing is how it was created (I suppose a duplicate >> of aforementioned bug), the other - how to fix it. >> >> Fix: >> * GET https://[your-rhevm-setup]/api/storageconnections >> * find id of the problematic connection >> * DELETE >> https://[your-rhevm-setup]/api/storageconnections/[id_of_the_connection] >> >> Last step perform with cURL or REST Client for Firefox or whatever is >> your favourite tool for REST API. >> >>> The bugzilla entry seems not to fit as this is: >>> a) no NFS Storage Domain >> >> Doesn't matter, it may happen for any non-iSCSI (and maybe non-FC) >> storage, localfs duplicate here: >> https://bugzilla.redhat.com/show_bug.cgi?id=1014966 >> >> >>> b) no Export Storage Domain >> >> Doesn't matter, I've seen it for data domains as well. >> Here you have duplicate for ISO: >> https://bugzilla.redhat.com/show_bug.cgi?id=991739 >> >>> c) the name of our SD does not contain any spaces >> >> Doesn't matter, the only important thing is if you ever tried to add >> this domain and the command failed. >> >>> d) the bug entry mentions this bug only occurs via api >>> because the webfrontend doesn't allow to create SDs with spaces >>> >>> however how can I check if the postgres db doesn't contain any other >>> storage domains, just to make 110% sure this is not this bug? >> >> You don't have additional storage domain, you have only additional >> storage connection. That's why I asked also for output of >> api/storageconnections >> >> Kasia >> >> >> >> > _______________________________________________ > Users mailing list > Users-dEQiMlfYlSzYtjvyW6yDsg(a)public.gmane.org > http://lists.ovirt.org/mailman/listinfo/users >

we delete one of the 2 functional data centers and then try to add the local storage domain inside the third data center, we succeed. If we then try to add the deleted data center 2 again, now as the third data center, the addition

Il 12/11/2013 10:34, Sven Kieske ha scritto: > Hi, > > I'm currently setting up a fresh 3.3.1 from ovirt.org beta repo Hi, may I invite you to add yourself to http://www.ovirt.org/Testing/Ovirt_3.3.1_testing?

On 11/12/2013 06:37 AM, Sven Kieske wrote: > Hi, > > done that. > > We encountered this bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1023739 > > we tested 3.3.1 from the beta ovirt.org repo. > > Could this bug fix please be included in 3.3.1 release? patch isn't small and 3.3.1 has been in beta/frozen for a while now (pending last vdsm issue). so i prefer this to wait to 3.3.2 (already fixed there) which beta should be available once we release 3.3.1.

From: "Itamar Heim" <iheim(a)redhat.com&gt; To: "Sven Kieske" <S.Kieske(a)mittwald.de&gt;, users(a)ovirt.org Sent: Tuesday, November 12, 2013 1:50:00 PM Subject: Re: [Users] Bug: adding LocalStorage Data Centers On 11/12/2013 06:37 AM, Sven Kieske wrote: > Hi, > > done that. > > We encountered this bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1023739 > > we tested 3.3.1 from the beta ovirt.org repo. > > Could this bug fix please be included in 3.3.1 release? patch isn't small and 3.3.1 has been in beta/frozen for a while now (pending last vdsm issue). so i prefer this to wait to 3.3.2 (already fixed there) which beta should be available once we release 3.3.1.

> > Am 12.11.2013 11:33, schrieb Sandro Bonazzola: >> Il 12/11/2013 10:34, Sven Kieske ha scritto: >>> Hi, >>> >>> I'm currently setting up a fresh 3.3.1 from ovirt.org beta repo >> >> Hi, may I invite you to add yourself to >> http://www.ovirt.org/Testing/Ovirt_3.3.1_testing? >> > > _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users