If you SSH to it what does the login banner say? What size VM did you deploy this as? Can you go to edit settings and post a screenshot? Any chance you downloaded VC on accident?
What does "rpm -qa | grep loginsight" return? Does loginsight-support exist? If so can you generate a support bundle and open a support case? If it does not can you still open a support case and upload the contents of /var/log?
I cannot repro this -- if you deploy the VM again does the same thing happen?
I've just reproduce this in my environment. Deployed 3 new 3.6 VMs, and they have all come to the VCSA start screen. No ports are listening other than RPC (111) and SMTP (localhost only).
I'll try re-deploying one and see what happens.
My other DC has 3.0 VM's upgraded to 3.3 then 3.6, so I didnt see this issue there.
Right, so I think I figured it out.
On first boot, it configures LogInsight, and brings you to the login screen. If you Alt-F2 to the holding screen, it shows VCSA.
If you do ANYTHING at this point, it appears processes stop, and the installation seems to be stuffed.
What needs to happen is just let it sit there at the login screen for some time, after which it then brings up the Log Insight holding screen.
It's still doing some configuration in the background, until it reaches this point.
So hopefully this helps someone in the future who runs into this issue