Oh, if this was created on Monday then it was probably built during the puppetmaster swap and was dead on arrival.

Mentioned in SAL (#wikimedia-releng) [2019-09-11T14:27:12Z] <hashar> puppet cert clean integration-agent-docker-1001.integration.eqiad.wmflabs # T232619 | might unbreak puppet

I think I have created an instance based on the same name earlier but using Stretch, that was to prepare the migration of the instances to Stretch. Not a big loss though.

What I suspect is there is a cert mismatch between the client (which would use the labs puppetmaster cert) and the CI puppetmaster. That is a known issue. Potentially clearing the cert on the puppetmaster might solve the issue, else we will have to recreate the instance.

In T232619#5483743, @hashar wrote:

I think I have created an instance based on the same name earlier but using Stretch, that was to prepare the migration of the instances to Stretch. Not a big loss though.

What I suspect is there is a cert mismatch between the client (which would use the labs puppetmaster cert) and the CI puppetmaster. That is a known issue. Potentially clearing the cert on the puppetmaster might solve the issue, else we will have to recreate the instance.

You created it, but then I realized it wasn't pooled in Jenkins, so I deleted and re-created it.

In T232619#5483724, @Andrew wrote:

Oh, if this was created on Monday then it was probably built during the puppetmaster swap and was dead on arrival.

I think this was what the problem was ^ probably just need to delete the instance and re-create.

@hashar sorry for making a mess and not cleaning it up :)