And my livepatch client ('canonical-livepatch enable <MYAPIKEY>') just registered fine.
Before this change, it was just sitting there for ~10 minutes, retrying to connect (as per syslog, no info on this was printed on my tty), then ultimately failed (no notice on that in syslog, just on the tty i was running the command on) with the error message by Keenen.
It would be great to have more robust testing in place to prevent such issues. I know this is often easier said than done, especially with web applications - but if it's a web application which only one application - which is maintained by Canonical - is supposed to access anyways, then... I would think this should be manageable. ;-)
Thanks for your efforts (and the free tier on this service).
And my livepatch client ('canonical- livepatch enable <MYAPIKEY>') just registered fine.
Before this change, it was just sitting there for ~10 minutes, retrying to connect (as per syslog, no info on this was printed on my tty), then ultimately failed (no notice on that in syslog, just on the tty i was running the command on) with the error message by Keenen.
It would be great to have more robust testing in place to prevent such issues. I know this is often easier said than done, especially with web applications - but if it's a web application which only one application - which is maintained by Canonical - is supposed to access anyways, then... I would think this should be manageable. ;-)
Thanks for your efforts (and the free tier on this service).