Closed danikam closed 4 years ago
thanks @danikam do you know if something changed on the CERN GitLab to trigger this?
Hi @lukasheinrich, not sure. It looks like the monosbb ci jobs first started failing the recast auth
command with that error message 5 months ago: https://gitlab.cern.ch/recast-monosbb/workflow/-/jobs/4801397. Before that, the auth login was succeeding (eg. https://gitlab.cern.ch/recast-monosbb/workflow/-/jobs/4658329). The tag of the recast/recastatlas
image (v0.0.16
) is the same for the two pipelines.
I'm not sure how the docker registry login using registry_pass==token
was succeeding in the past without setting the RECAST_TOKEN the same as the RECAST_PASS (that's my current workaround), but it obviously was working, so I don't know what changed to make it start failing.
Issue resolved. Was due to misunderstanding on my end regarding the use of gitlab access tokens.
The command
eval "$(recast auth setup -a $RECAST_USER -a $RECAST_PASS -a $RECAST_TOKEN -a default)"
was failing with the following error:This authorization error seems to be resolved by assigning the user-input
$RECAST_PASS
password - rather than the user-input$RECAST_TOKEN
- to the variableregistry_pass
inauth.py
.The
eval
command above now succeeds with: