3.6 : iSCSI LUN not detected
Hi, I am reinstalling a new Node with a new hosted-engine and I would like to import an iSCSI storage from a previous ovirt installation. However, I can see all LUN present on that iSCSI but the one I want... I checked from the iSCSI array and this disk still exists, it's just not detected from Ovirt (3.6)... I tried to make a new data domain and chosed that same iSCSI and it's also not detected. Any ideas ? I didn't remove the storage from the Engine interface on the previous installation, just just turned off all VMs accessing the iSCSI and unplugged the cable. Is it possible there is still a lock file or something from the previous hypervisor ?
On Wed, Aug 10, 2016 at 10:38 AM, Alexis HAUSER <alexis.hauser@telecom-bretagne.eu> wrote:
Hi,
I am reinstalling a new Node with a new hosted-engine and I would like to import an iSCSI storage from a previous ovirt installation. However, I can see all LUN present on that iSCSI but the one I want... I checked from the iSCSI array and this disk still exists, it's just not detected from Ovirt (3.6)... I tried to make a new data domain and chosed that same iSCSI and it's also not detected.
Any ideas ?
Did you deployed the engine from scratch or did your restored there a backup? In 3.5 we were registering an hosted-engine iSCSI storage domain as a (fake) direct LUN into the engine to prevent any misuse.
I didn't remove the storage from the Engine interface on the previous installation, just just turned off all VMs accessing the iSCSI and unplugged the cable. Is it possible there is still a lock file or something from the previous hypervisor ?
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Did you deployed the engine from scratch or did your restored there a backup?
From scratch
In 3.5 we were registering an hosted-engine iSCSI storage domain as a (fake) direct LUN into the engine to prevent any misuse.
I have this problem for a data domain but not for the hosted_storage :) ----- Mail original ----- De: "Simone Tiraboschi" <stirabos@redhat.com> À: "Alexis HAUSER" <alexis.hauser@telecom-bretagne.eu> Cc: "users" <users@ovirt.org> Envoyé: Mercredi 10 Août 2016 11:37:15 Objet: Re: [ovirt-users] 3.6 : iSCSI LUN not detected On Wed, Aug 10, 2016 at 10:38 AM, Alexis HAUSER <alexis.hauser@telecom-bretagne.eu> wrote:
Hi,
I am reinstalling a new Node with a new hosted-engine and I would like to import an iSCSI storage from a previous ovirt installation. However, I can see all LUN present on that iSCSI but the one I want... I checked from the iSCSI array and this disk still exists, it's just not detected from Ovirt (3.6)... I tried to make a new data domain and chosed that same iSCSI and it's also not detected.
Any ideas ?
Did you deployed the engine from scratch or did your restored there a backup? In 3.5 we were registering an hosted-engine iSCSI storage domain as a (fake) direct LUN into the engine to prevent any misuse.
I didn't remove the storage from the Engine interface on the previous installation, just just turned off all VMs accessing the iSCSI and unplugged the cable. Is it possible there is still a lock file or something from the previous hypervisor ?
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Wed, Aug 10, 2016 at 11:38 AM, Alexis HAUSER <alexis.hauser@telecom-bretagne.eu> wrote:
Hi,
I am reinstalling a new Node with a new hosted-engine and I would like to import an iSCSI storage from a previous ovirt installation. However, I can see all LUN present on that iSCSI but the one I want... I checked from the iSCSI array and this disk still exists, it's just not detected from Ovirt (3.6)... I tried to make a new data domain and chosed that same iSCSI and it's also not detected.
You should see the lun in engine if you are logged in to the iscsi target. Are you sure this lun is configured properly so the new host can access it? Do you have correct /etc/iscsi/initiatorname.iscsi on the host?
I didn't remove the storage from the Engine interface on the previous installation, just just turned off all VMs accessing the iSCSI and unplugged the cable.
This is not a good idea, not sure that it is related to your problem, but what you should do is: 1. Shutdown vms using this storage domain 2. Put storage domain to maintenance 3. Detach storage domain 4. Import storage domain on the other setup - this will work only after you see the lun on the other setup Nir
Hi Alexis Were you able to resolve your storage LUN issue? Regards, Kevin On Wed, Aug 10, 2016 at 11:38 AM, Alexis HAUSER < alexis.hauser@telecom-bretagne.eu> wrote:
Hi,
I am reinstalling a new Node with a new hosted-engine and I would like to import an iSCSI storage from a previous ovirt installation. However, I can see all LUN present on that iSCSI but the one I want... I checked from the iSCSI array and this disk still exists, it's just not detected from Ovirt (3.6)... I tried to make a new data domain and chosed that same iSCSI and it's also not detected.
Any ideas ?
I didn't remove the storage from the Engine interface on the previous installation, just just turned off all VMs accessing the iSCSI and unplugged the cable. Is it possible there is still a lock file or something from the previous hypervisor ?
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
> Hi Alexis > Were you able to resolve your storage LUN issue? > Regards, > Kevin I am trying the suggested solution on this post by Nir Soffer : reconnect the storage to the older hypervisor and detach it correctly...But it doesn't work : >From the DC : 1. I set the storage (which is master data domain) to maintenance mode 2. I try to detach it. I get this error message : "Error while executing action: Cannot remove the master Storage Domain from the Data Center without another active Storage Domain to take its place. -Either activate another Storage Domain in the Data Center, or remove the Data Center. 3. If I go in the storage domain menu, I get only the "destroy option", not "remove", which is maybe not what I want. I'd like to be able to keep the data on it. 4. If I try to remove the datacenter as suggested in the error message I get this error (as the hosted-engine storage is still up) : "Error while executing action: Cannot remove Data Center which contains active/locked Storage Domains. -Please deactivate all domains and wait for tasks to finish before removing the Data Center." 5. I can't set the hosted engine storage to maintenance What should I do ?
On Thu, Aug 11, 2016 at 12:27 PM, Alexis HAUSER <alexis.hauser@telecom-bretagne.eu> wrote:
Hi Alexis
Were you able to resolve your storage LUN issue?
Regards,
Kevin
I am trying the suggested solution on this post by Nir Soffer : reconnect the storage to the older hypervisor and detach it correctly...But it doesn't work :
From the DC : 1. I set the storage (which is master data domain) to maintenance mode 2. I try to detach it. I get this error message :
"Error while executing action: Cannot remove the master Storage Domain from the Data Center without another active Storage Domain to take its place. -Either activate another Storage Domain in the Data Center, or remove the Data Center.
3. If I go in the storage domain menu, I get only the "destroy option", not "remove", which is maybe not what I want. I'd like to be able to keep the data on it. 4. If I try to remove the datacenter as suggested in the error message I get this error (as the hosted-engine storage is still up) :
"Error while executing action: Cannot remove Data Center which contains active/locked Storage Domains. -Please deactivate all domains and wait for tasks to finish before removing the Data Center."
5. I can't set the hosted engine storage to maintenance
What should I do ?
Yes, you cannot remove the master storage domain, so you need to create another domain and make it the master. Then you will be able to detach the original storage domain properly. Nir
Yes, you cannot remove the master storage domain, so you need to create another domain and make it the master. Then you will be able to detach the original storage domain properly.
Nir
I would love to do that...But it's not possible as long as the master data domain is in maintenance mode. And it doesn't activate... I'm now stuck with second data domain with unknown status, same for hosted_storage and master data domain still in maintenance mode. I can't activate any of the storage and can't reinitialize data center...
participants (4)
-
Alexis HAUSER -
Kevin Goldblatt -
Nir Soffer -
Simone Tiraboschi