Why cannot show the 3rd plugin in vSphere Flex Client?

[Flying_Cat]

Hi laurentsd​,

We recently encountered a tricky customer case, there are three linked multiple vCenters in customer's environment. The problem is our plugin cannot show in one vCenter, but it is normal in other two vCenters. So we collected the logs in that problematic vCenter, then analyzed them and found many same clues like below:

[2017-11-21T07:36:58.681-07:00] [INFO ] http-bio-9090-exec-10        70000110 100006 200002 com.vmware.vise.extensionfw.ExtensionManager                      Package is filtered out - com.emc.vsi.plugin:6.9.2.31

We are curious that why our plugin is filtered out in that vCenter and no other more valuable messages in logs, but we found some SRM issues and we are not sure whether SRM issue is the root cause or the Center itself has some problems.

Could you help to check the log for giving your any ideas or suggestions? Thanks in advance.

[laurentsd]

Make sure to mention the vSphere Client version in all your messages, and the SDK version used to be build your plugin.

The log "Package is filtered out" means that the plugin is marked disabled.  Do you see that in the Admin > Client plugins view?

Is it registered with all VCs?

[Flying_Cat]

Customer has 3 vCenters that are 6.0 U2, not in our development environment. And we checked that all the vCenters have registered our plugin in "Client Plugin" view like this:

but there is still one vCenter which cannot see our plugin UI in vSphere Web Client, so we provided the log before to hope you check it whether the vCenter has some issues or not.

Any other messages do you want? We are willing to provide them.

[laurentsd]

I don't see anything special in the logs you sent regarding this plugin, there was no deployment error.

- Do other registered plugins have the same behavior for that VC linked to the 2 other ones?

- Does it make a difference if you login to another VC first?

- Does it make a difference if you disable and enable the plugin again?

- Does the plugin show up if that VC is not linked anymore?

[Flying_Cat]

- Do other registered plugins have the same behavior for that VC linked to the 2 other ones?

No, the 2 other vCenters have the registered plugin, customer can use our plugin normally.

- Does it make a difference if you login to another VC first?

When we login to another VC first, our plugin UI shows normally, but if we login the problematic VC, it cannot show our plugin UI...

- Does it make a difference if you disable and enable the plugin again?

No different, we checked that the VC mob has registered our plugin extension normally and the plugin has been downloaded in VC virtual machine.

- Does the plugin show up if that VC is not linked anymore?

The customer's environment I think we cannot change anything, but I'm confused is it related to VC not linked anymore?

We checked the log again, and found a clue that there were some information of missing session by invoking VMware method getUserSession when deploying our plugin in that problematic VC:

[2017-11-21T07:34:14.883-07:00] [INFO ] region-dm-11                  c.vmware.vsphere.client.usersession.impl.UserSessionServiceImpl   getUserSession called on a missing session.

Do you have any idea?

Thanks

[_vladi_]

Hi,

I have seen this twice in the past and believe this is a very rare race condition in the vSphere Web Client. Please try the following on the failing vCenter:

 - Check your /storage/vsphere-client/SerenityDB/serenity folder and its subfolders for a file called “client.package.states”.

 - If it exists back it up, remove it and restart the Web Client.

The plugin should be back.

If not - please try cleaning up your plugin instance from the vc-packages folder and restarting the Web Client.

Cheers,

Vladi

/storage/vsphere-client/SerenityDB/serenity folder and its subfolders for a file called “client.package.states”?

If it exists ask them to back it up, send it to us, remove it and restart the Web Client.

[Flying_Cat]

Hi _vladi_,

Sorry for that I forgot to tell you the failing vCenter was installed in Windows OS, not Linux OS. So the folder path /storage/vsphere-client/SerenityDB/serenity I think is not correct, right?

Could you give me the right path in Windows OS? Thanks very much.

[_vladi_]

Hi,

On Windows it should be:

C:\ProgramData\VMware\vSphere Web Client\SerenityDB\serenity

Please let me know if that works.

Cheers,

Vladi

[Flying_Cat]

Sure, no problem, will let you know if it works

[Flying_Cat]

Hi _vladi_​,

I provided the solution you mentioned last time to our customer, they said it worked, and our plugin is now visible in their environment. Thank you very much for your support.

Cheers,

Plocen

[fchouBMRN]

Thanks I had the same issue and performing the steps to remove the client.package states resolved the isue

Backed up and removed file, which was in this folder: \ProgramData\VMware\vCenterServer\data\vSphere Web Client\SerenityDB\serenity\ALL\client.package.states

External Appliance PSC Build Number 5326079)

3 vCenters (Windows vCenter 6.0 Build 5318200)

ELM