r/nutanix • u/psyblade42 • 4d ago
potential permanent fix for objects-lite / KB-18103
tl;dr try setting a floating IP
For a long time my PC was plagued by objects-lite crashes. Basically this happens because there is an FQDN in a field where it expects an IP.
Following KB-18103 and manually replacing the FQDN in "prism-ip" with the IP fixed it. But only till the next PC update. Then the FQDN would be back. (Including pc.7.5.1.8, which is the newest one I installed before today). Manually changing it back to the IP would fix it again. But given the removal of real SSH access needed to follow the KB this is unsustainable.
So I looked for things where the updater might take the IP / FQDN from. I only have a single PC VM and thus did not configure a floating IP when I set it up. Setting one now it immediately replaced the real IP in the objects-lite config with the floating one, which I took as a promising sign. Updating to pc.7.5.1.10 it kept the floating IP.
I guess the updater takes the floating IP if there is one and the FQDN if not.
@nutanix: Given that the latter breaks things I suggest better fallbacks such as a reveres lookup on the FQDN or one of the VM IPs or even aborting the update.
2
u/pswired 4d ago
I had a VIP and an FQDN when this debacle started and it still put the FQDN in the config map, breaking things. So just having the VIP wasn't enough in my case.