Vastool status is reporting "724 System is not defined as in a site" yet "vastool info site" shows the site. (4265996)

Vasd picks a site to be in when AD doesn't assign it one. That's why "vastool info site" is showing the site.

To check if the joined Linux/Unix system is in a site run the following:

#vastool info servers

From the resulting list choose a DC and run the following where dc.domain.com is the fqdn of the DC:

#vastool info cldap dc.domain.com

Look for the following in the output:

Server Site:             Actual site name

Client Site:             (NULL)

This shows that the joined system (Client Site: (NULL),  is not in site.

Vasd picks a site to be in when AD doesn't assign it one. That's why "vastool info site" is showing the site.

A possible issue is that it picks that site based on DC response speed. And it checks every 24 hours.
And if it changes site, because say another DC in a different site was faster that time, it does a flush.
Which can interrupt requests during the flush. This is why the new check was added.

The best way forward is to eventually add the joined systems to a site.

Alternately another fix if you are seeing outages every 24 hours is to add a site-name-override. This will not stop the INFO message, but will stop vasd from possibly triggering a flush when it picks a new site to be in.

Please see the following KB on how to set a site-name-override:

Knowledge Article 241954