#7648 Certificates use to push containers to the candidate-registry seems to have expired
Closed: Fixed 5 years ago by kevin. Opened 5 years ago by cverna.

  • Describe what you need us to do:

While trying to release containers @mohanboddu faced a authentication error since we authenticate against the candidate repository using certificates I assume these have expired or something else is wrong.

  • When do you need this? (YYYY/MM/DD)

  • When is this no longer needed or useful? (YYYY/MM/DD)

  • If we cannot complete your request, what is the impact?


Metadata Update from @bowlofeggs:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: authentication

5 years ago

We don't use certs for the candidate ones... thats via docker login?

What process/user/thing is runing thats hitting the unauth thing?

We don't use certs for the candidate ones... thats via docker login?
What process/user/thing is runing thats hitting the unauth thing?

Ha I am always confused on which registry uses which auth :-), the error happened while running the releng container release script see releng ticket.

This was all sorted on the releng ticket I think. Feel free to re-open if there is further to do here.

:passport_control:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata