Openstack plugin not displayed with VIO 3.1

[chewy85500]

Hello,

I have deployed the VIO 3.1 appliance on a vCenter 6.0 Update 3 but the plugin does not appear in the vCenter after restart the session.

I tried to restart the vCenter and the VIO appliance but this is the same.

I cannot access to the VIO interface (https://IP:8443/VIO). On the VIO appliance, oms and osvmw were not started and there is no log for these services. I started them and they appear as running but still no plugin in the vCenter.

If someone has any clue about this issue, it will be greatly appreciated.

[admin]

did you start both the VM and the template part of the vApp?

If so, please, follow:

1) Shutdown the vApp

2) Power on the vApp

3) Log out from vSphere Web client

4) Log in back.

How many times did you try to deploy VIO? multiple times?

If the previous steps don't fix VIO plugin installation, please, let me know and I'll try to help you into the manual uninstall.

Cheers,

Domenico

[chewy85500]

I didn't start the template, only the VM.

I tried to stop and start the vApp but only the VM was started, not the template. I forced the template poweron but after logging out and back, the plugin was still not there.

I deployed the VIO two times on the same vCenter (did a snapshot before).

[admin]

Template should not be powered on, only the VM should be on, after powering on the vApp.

Please, follow KB 2146541, in order to manually remove VIO and proceed to deploy it again.

Once deployed, power on the vApp, logout from vSphere Web client and login back; then you should find the plugin.

Any question, let me know.

Cheers,

Domenico

[chewy85500]

I followed KB 2146541 but the extensions were not registered.

I deployed and power on the vApp but no plugin after logout/log back.

I got the same results as before, with no oms service started and no log.

[admin]

In order to understand better the issue, could you please provide the following:

1) what is the OMS hostname? did you set correctly DNS server during deployment?

2) what do you mean with "no oms service started and no log) ?

3) did you try to power off and power on agaiin the vApp?

4) did you try restarting vcenter server ?

5) checking into https:// vcenter_server_ip/FQDN /mob/?moid=ExtensionManager, which extensions are registered?

6)which package has been placed into /vsphere-client-serenity folder?

Thanks

[chewy85500]

My answers:

1) The hostname is cloud-vio-z01r-stg and the DNS server is correct and reachable. During the OVA deploymenent, I have provided the IP addresse and and hostname was set on the VM with reverse DNS I suppose

2) The services oms and osvmw were not started. I have to start them manually. In the directories "/var/log/oms/" and "/var/log/osvmw/", there is no file

3) Yes, tried

4) Yes

5) https://10.36.70.107/mob/?moid=ExtensionManager :

extensionList["com.vmware.vim.inventoryservice"]    Extension
extensionList["com.vmware.vim.sms"]    Extension
extensionList["com.vmware.vim.vsm"]    Extension
extensionList["VirtualCenter"]    Extension
extensionList["com.vmware.vim.stats.report"]    Extension
extensionList["com.vmware.vim.sps"]    Extension
extensionList["hostdiag"]    Extension
extensionList["com.vmware.vim.ls"]    Extension
extensionList["com.vmware.vim.eam"]    Extension
extensionList["com.vmware.rbd"]    Extension
extensionList["com.vmware.vsan.health"]    Extension
extensionList["com.vmware.cl"]    Extension
extensionList["com.vmware.vdc"]    Extension
extensionList["com.vmware.vShieldManager"]    Extension

6) in /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/

com.vmware.vShieldManager-6.2.2.3604087

[chewy85500]

I tried to redeploy but with using the DHCP server and this time, it worked.

Previously, I was using static IP address but on the same network where this DHCP server is present.

Is it possible that DHCP server interfere ?

During my previous deployments with static IPs, the VM was getting an IP address by DHCP before the static configuration was applied.

[admin]

this a fantastic news!

I'll try to replicate the issue as soon as I can, enabling a DHCP server during the deployment process.

Honestly I did not hear about this behavior before.

Cheers,

Domenico

[chewy85500]

I will try with disabling the DHCP server, to see if static adress is working for me.

Thanks for your help !

[admin]

honestly that was my idea too! I did not know if you could stop dhcp services.

Please, let me know if it works!

Cheers,

Domenico

[chewy85500 · Accepted solution]

With the DHCP disabled, it worked so it seems that the cause of my issue !

[admin]

that's perfect!

great to hear that!

Cheers,

Domenico

[admin]

Hi chewy85500,

I just tried to reproduce the issue, in order to identify if a DHCP service can stop a correct VIO deployment.

With an installed  DHCP server (in the same network where it is supposed to deploy VIO) and correctly configured, Vio deployment works fine, installing correctly the plugin.

Cheers,

Domenico