VMware Cloud Community
Raducanu
Enthusiast
Enthusiast

Volume Creation not working

Hello,

i have a fresh out-of-the-box VIO 3.1 installation. I tried to create an empty volume in horizon but nothing happens in the vSphere WebClient.

Horizon shows an volume, but i can't attach it to an instance. It also shows no error message.

Any idea what's wrong or where i go on checking logfiles?

Thank you

Reply
0 Kudos
6 Replies
admin
Immortal
Immortal

Please, provide more information on this issue:

1) are all VIO services up and running trough vSphere Web client VIO Plugin?

2) any chance to get cinder logs and the volume ID currently failing?

3) which storage are you using as backend?

4) what is it shown in "Nova Storage" (VIO plugin) ?

5) what is it shown in "Glance Storage" (VIO plugin) ?

Cheers,

Domenico

Reply
0 Kudos
Raducanu
Enthusiast
Enthusiast

1) are all VIO services up and running trough vSphere Web client VIO Plugin?

     -> Yes

2) any chance to get cinder logs and the volume ID currently failing?

    -> See Video

3) which storage are you using as backend?

    -> NetApp Filer via NFS

4) what is it shown in "Nova Storage" (VIO plugin) ?

     -> See Video

5) what is it shown in "Glance Storage" (VIO plugin) ?

     -> See Video

Yesterday i installed LogInside to get a better view. I recognized that there is a nova error during creation of the volume. I remember that a "fake vm" will be created for volume. Might the creation of the fake vm fail so also the cinder volume is not created? (see nova error at the end of the video)

http://marcelmertens.de/temp/2017-09-08-08-18-56.mp4

Reply
0 Kudos
admin
Immortal
Immortal

all seems in a good shape!

Can you, please, provide the following:

1) vCenter Server version (exact build)

2) VMware VIO version.

3) Is the datastore containing Vms created only by VIO?

4) Do you think is it possible getting a text, containing the entire backtrack of req-ccfd2ad1-1251-404f-b4ab-e9d245c9552e

5) Is the datastore (Defined in Nova storage) connected to all the Esxi nodes, part of the compute cluster?

Cheers,

Domenico

Reply
0 Kudos
Raducanu
Enthusiast
Enthusiast

1) vCenter Server version (exact build)

-> 6.5.0, Build 5973321

2) VMware VIO version.

-> 3.1

3) Is the datastore containing Vms created only by VIO?

-> The datastore currently contains all VMs required for our environment (vCenter, DNS, NSX Manager, NSX Controller, VIO Manager usw). But no 3rd party workloads

4) Do you think is it possible getting a text, containing the entire backtrack of req-ccfd2ad1-1251-404f-b4ab-e9d245c9552e

-> See attachment.

5) Is the datastore (Defined in Nova storage) connected to all the Esxi nodes, part of the compute cluster?

-> Yes

Reply
0 Kudos
admin
Immortal
Immortal

As per point 3, could segregate images and volumes handling on a separate datastore?

Considering the environment is a testing one, I should:

1) add a new datastore to Nova and Glance Storage, disabling the ones already configured.

2) if the point 1 fails, I should redeploy VIO (correctly removing the one you are currently testing), deploying it back using a separate datastore for Nova and Glance.

My toughs are based on the facts that it is always recommended separating management from compute.

Please, let me know if you agree with the above and how your tests proceed.

Cheers,

Domenico

Reply
0 Kudos
Raducanu
Enthusiast
Enthusiast

Just as an Update:

There is a bug in VIO 3.x (4.x???) if your ESXi host does not have any hba (iSCSI HBA, FC HBA, SAS HBA or else).

In our case we use auto deployed Cisco UCS blades for our compute nodes booting from LAN. Storage Backend is NFS.

So there is no HBA avaiable inside the ESX host.

The VIO script for creating/attaching volumes (and else) is checking for ESXi hba (not the HBA of the instance) and run's into an error if no hba is found.

Workaround: Just activate Software-iSCSI HBA.

Domenico from VMware support helped me with this issue. He wanted to create an KB topic.

I can't find the article yet, maybe Domenico can link it here.

Reply
0 Kudos