© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
In response to #26, from Blake Rouse: When I say it was not working, at first the dnsresource setting was getting 500 server errors (as expected) but when it succeeded, the new IP was set in the postgres DB but the zone files on each node still reflected the old IP.
I confirmed with Dima that the md5sums of the patched files matched his.
Since this is an environment where I don't have hands on keyboard, digging into the log files is a little challenging. Also, I left the customer location on Thursday so I needed to have a solution in place. This is why I spent the remainder of my on-site time implementing roaksoax's suggestion of restarting maas-regiond when the PostgreSQL master changes.