- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Skyline "Could not execute Online health checks." after 7.0 U3d update
After updating to 7.0U3d, I have several custromers who are experiencing Skyline Health "Online health checks execution" error showing "Could not execute Online health checks." I tried a "RETEST" and Guest OS reset on the vCenter Server VM and a full Power Reset and came back up to the same result.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have the same issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Does anyone have any suggestions yet?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
same issue here
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same here. I just updated to 7.0 U3d and have the same result. I'll be firing up VSAN in 2 weeks... this isn't giving me a warm fuzzy.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same issue since upgrading to 7.0.3.00500.
No VSAN setup at all but that's the error I'm getting in the logs, just like everyone else.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yeah, I don't think it's a vSan issue although I do have that. The VCSA update is what broke it. It was listed as a critical update so I decided not to roll it back hoping they would have a fix soon.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same issue for me on 7.0U3d.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
same
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ditto. At least I know to stop beating my head against a (virtual) wall and wait.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A VMware reassurance of a fix or acknowledge of the issue at least wouldn’t go a miss.
There might be one and I haven’t look hard enough to be honest.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After filing a support request. I got the follwing answer:
Listed as a known issue for 7.0 U3d, fix is planned come for release 7.0 P5 [scheduled for late Q2, early Q3 2022]
So I guess we have to wait a "little" longer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The Oracle (Sun) JRE package is updated to version 1.8.0_311 in 7.0 U3d and in /var/log/vmware/analytics/analytics.log you are getting this when you running Skyline:
pool-14-thread-1 [operationID=5e25e847-8fd1-4086-b242-2cf2f0b194a6] WARN cloud.dataapp.internal.collector.DefaultCollectorDataAppAgent Data app collection failed java.lang.IllegalArgumentException: Unsupported type class java.util.ArrayList
I think this is the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nothing in the official release notes says this is a known issue. Cmon VMware, do better.
https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3d-release-notes.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same issue after updating from 7.0u3c > 7.0u3d. VMware support has not provided any resolution and just wants to use our production system as a bug fix sandbox.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When it comes to something as unimportant as the health of our production VMWare environments, we can wait for a fix... ![]()
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I checked VMware vCenter Server 7.0 Update 3d Release Notes as well and all I could find regarding Skyline Health is:
- Skyline Health page displays garbage characters
In the vSphere Client, when you navigate to vCenter Server or select an ESXi host in the vSphere Client navigator and click Monitor > Skyline Health, the page displays garbage characters in the following locales: Korean, Japanese, German and French.
Workaround: Switch to English locale.
Can someone post the URL that contains this (Skyline "Could not execute Online health checks") as a known issue?
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think that is part of the issue. VMware has not posted it as a known issue although people who have opened tickets say support is aware of it.