[Jenkins-infra] So that was a funny ci.jenkins.io outage

R. Tyler Croy tyler at monkeypox.org
Thu Dec 7 22:17:23 UTC 2017

abayer gets a golden rubber chicken for today

    03:58 @<abayer> rtyler: something is awry with creds on ci.jenkins.io for Azure - see https://gist.github.com/abayer/88b3d5344ed95ad64bb5e83eb6b48cb1 e.g.
    03:58 @<abayer> So instances aren't getting deleted. Not sure what else is borked by that, but I'm guessing it's probably causing other errors.
    04:00 @<abayer> Yup, errors validating VM images, timeouts creating instances...

As a bunch of smashing around on my part, I discovered the real issue (in the
last place I looked!) was that Azure AD Application credentials are created
with a 365 day expiry.

As it turns out, I originally provisioned our Azure integration in
ci.jenkins.io on December 7th 2016.

I have created a key without an expiry for the AAD service principal for now. I
need to discuss with olblak how we should handle some of these grants we have
running around for Terrorform.

- R. Tyler Croy

     Code: <https://github.com/rtyler>
  Chatter: <https://twitter.com/agentdero>
     xmpp: rtyler at jabber.org

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20171207/f540c9d3/attachment.asc>

More information about the Jenkins-infra mailing list