clustering.properties no longer read on each boot of Jamf Pro about jamfpro HOT 4 CLOSED

In my (albeit brief) testing on 10.42.1, the file still works as intended and does indeed automate the setting of the primary node on startup and moves of the primary. Depending on how your environment is setup in Kubernetes however you may need to update which ip is being passed as the POD_IP. This ip needs to be the ip from the perspective of the mysql server, so if deploying in cluster the pod ip would work whereas if deployed outside of the cluster, the actual external node ip would have to be passed into the deployment/pod config.

from jamfpro.

I pass hostIP as POD_IP. I’ve been running this for well over a year with a variety of versions, and they all worked till this attempt to upgrade.

The setup where I experienced it is my pre-prod environment. I haven’t attempted reproducing with fewer variables but I’ll see what I can do.

Here are the steps I plan on doing to attempt to reproduce

1. Deploy docker image, and memcached. Make sure the proper ENV variables are set so that it enables memcached, and clustering.
2. Complete setup of Jamf Pro, confirm clustering is enabled, shows correct IP, and shows memcached.
3. Shutdown docker image.
4. Redeploy docker image ensuring that the IP that DB sees it from is different, and check if it boots properly. In my env memcached failed to be configured because new pod wasn’t the “primary” even though clustering.properties said it was.

from jamfpro.

Just wanting to check in and see if you were able to reproduce the issue?

from jamfpro.

Hey there, it's been awhile since this issue was opened and responded to so I am going to close it, but please do feel free to open a new case if you are able to reproduce the issue.

from jamfpro.