vCenter 7.0 wrong build version

[mariss35]

So i have build playground with 7.0 versions before actually moving prod to new version. Yesterday i encountered weird thing.

1. web client notification popped up , that there is new update for vCenter (thats really nice thing!)

2. since from default repos for vCenter nothing is being picked up i downloaded iso manually and patched appliance that way.

3. appliance patched without any issues and shows build version - 7.0.0.10300 build 16189094

4. web client still keep popping alert that patch is available and showing that build version is 16189207

what confuses hell out of me why the patched version 7.0.0.10300 (16189094) shows build number lesser than unpatched version 7.0.0.10100 (16189207)

p.s. initially it was installed from iso available in VMUG Adv repo (VMware-VCSA-all-7.0.0-15952498)

suggestions , how to fix that versioning missmatch ?

M.

[Raudi]

Short info:

The missing infos in the Summary tab was a rights issue, when logged in with the administrator@vsphere.local user this infos are shown:

[depping]

Correct srodenburg​

[Leica]

Any update to this issue?

[kmnalbone]

Glad I found this thread as I am experiencing the same issue in my lab today. Will keep an eye on this one.

[Raudi]

I'm wondering that there is no KB regarding this problem... Or do i missed something...

[mariss35]

silence , still no patches , checking regularly

[maxyardley]

For anyone still looking into this, the patch appears to have gone live yesterday. I updated today through the appliance management interface and am no longer experiencing the issues noted in this post

[Vijay2027 · Accepted solution]

VMware vCenter Server 7.0.0b Release Notes

You can still see Updates Available in the Summary tab of the vSphere Client after updating your vCenter Server system

When you log in to the vSphere Client for the first time after updating your vCenter Server system to vCenter Server 7.0.0a, you might still see Updates Available in the Summary tab.

This issue is resolved in this release.

[pawelq4]

It looks like the upgrade to version 7.0.0b has fixed the bug

[srodenburg]

Can confirm that VCSA version 7.0.0b fixes the issue.