I don't see it listed in the Known Issues with this update or with prior updates. Can you please post a link where you found it?

We also have this issue. Like OP, retesting and restarting the VCSA don't help.

Same issue here.  Skyline Health works fine for all the vSAN Clusters, but not on vCenter or the Hosts. Opened a SR with VMware, and after two days working with them trying different things, I finally got this back from them today.

Issue: Skyline "Could not execute Online health checks." after 7.0 U3d update 

Action Taken:

• Review the logs and checked the PRs raised, this is a known issue with latest version of vCenter server i.e., 7.0 U3d.
• Confirmed with Internal team, as of now there is no work around for this issue.
• This is likely to be resolved in the upcoming release.
• As of now there is not ETA for the next release.

Found the following KB: https://kb.vmware.com/s/article/88254

But nothing new at the moment.

vSphere 7.0 Update 3e was released yesterday with a fix for the problem.

https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3e-release-notes.html

Regards,

Bjoern

I can verify U3e (00600) corrected the Skyline issue in my environment.   

Don't think this is the first time it's happened tbh - they should probably review the release procedure / pipeline to make sure release notes are available *before* displaying banners. It'd be a brave soul who'd blindly update.

This seems to be broken again in G VMware vCenter Server 7.0 Update 3g Release Notes

Please confirm if anyone else is having this issue?

I am using build 20150588 which is update 3g and is connecting to skyline fine. I just did a skyline health retest and it showed fine.

Same build here, but having same issues as this thread.

• Version:7.0.3
• Build:20150588

I also updated my collector to 3.2 last week and still appears to be working fine. Wonder what is different from others still having issues?

Not sure of the cause, but it is working now post reboot.

Hello there,

We have the issue on vcsa 8.0, in the logs :

2023-01-05T10:33:55.180Z pool-10-thread-17  WARN  vmware.ph.upload.rest.PhRestClientImpl Failed to execute request: https://vcsa.vmware.com:443/ph/api/v1/manifest?collectorId=vSphere.vapi.6_7&instanceId=REMOVED&v=3.2.2
2023-01-05T10:33:55.182Z pool-10-thread-17  INFO  org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi Initializing with trust store at path: /usr/java/jre-vmware/lib/security/cacerts
2023-01-05T10:33:55.191Z pool-10-thread-17  WARN  vmware.ph.upload.rest.ProxyAwareHttpExecutor Failed 3 of 3 attempts to get manifest from VMware server. The reason for the last failure was (enable 'debug' level logging to see the error of every failed attempt): com.vmware.ph.exceptions.resource.ResourceNotFoundException: Request failed: 404 Not Found; Reason:
-------->{"timestamp":1672914835094,"status":404,"error":"Not Found","message":"A manifest could not be found. Contact the PH team to create a manifest.","path":"/api/v1/manifest"}.

Requesting url by hand give same result : https://vcsa.vmware.com/ph-stg/api/v1/manifest?collectorId=vcenter-all.vpxd.drs.7_0u1&instanceId=rem...or https://vcsa.vmware.com:443/ph/api/v1/manifest?collectorId=vSphere.vapi.6_7&instanceId=REMOVED&v=3.2... 

Side note : vcsa 8.0 request uri contains 7.0u1 (DRS) or 6.7 (vapi) see on both url above

Internet connectivity is good, CEIP enabled and working.

Any news on this topic? Same problem on vCenter 8 after upgrade

I successfully solved the problem using the magic  button