Project

General

Profile

action #67213

pushing needles on osd to gitlab.suse.de fails

Added by okurz over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
2020-05-25
Due date:
% Done:

0%

Estimated time:

Description

Observation

the account "openqa-pusher" is not able anymore to push needles to gitlab.suse.de . Seems like with the switch of the authentication system on the side of SUSE we need to migrate the account.


Related issues

Related to openQA Infrastructure - action #75067: save_needle minion task fails because "Your account has been blocked"Resolved2020-10-22

Related to openQA Infrastructure - action #89047: Failed to commit needles, gitlab account blocked 2021-02-24Resolved2021-02-24

Copied to openQA Infrastructure - action #67804: use non-personal account and key for pushing needles on osd to gitlab.suse.deResolved2020-05-252020-11-05

History

#1 Updated by okurz over 1 year ago

I migrated the account, have logged in over web UI and ssh gitlab.suse.de works as geekotest but git push is still denied with "remote: GitLab: Your account has been blocked.".

#2 Updated by okurz over 1 year ago

GIT_SSH_COMMAND="ssh -v" git push ssh://gitlab.suse.de/openqa/os-autoinst-needles-sles.git HEAD:master yields

debug1: Offering public key: /var/lib/openqa/.ssh/id_rsa.gitlab RSA SHA256:walE7SywGmiOeD2NAn0Jg5YNc7Hqwks0slyvYDLcnJI explicit
debug1: Server accepts key: /var/lib/openqa/.ssh/id_rsa.gitlab RSA SHA256:walE7SywGmiOeD2NAn0Jg5YNc7Hqwks0slyvYDLcnJI explicit
debug1: Authentication succeeded (publickey).
Authenticated to gitlab.suse.de ([149.44.176.5]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug1: Remote: /srv/gitlab/.ssh/authorized_keys:1430: key options: command user-rc
debug1: Remote: /srv/gitlab/.ssh/authorized_keys:1430: key options: command user-rc
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug1: Sending env LC_CTYPE = en_US.UTF-8
debug1: Sending env LC_TIME = en_DK.utf8
debug1: Sending command: git-receive-pack '/openqa/os-autoinst-needles-sles.git'
Enumerating objects: 34, done.
Counting objects: 100% (34/34), done.
Delta compression using up to 10 threads
Compressing objects: 100% (33/33), done.
Writing objects: 100% (33/33), 321.62 KiB | 11.91 MiB/s, done.
Total 33 (delta 10), reused 0 (delta 0), pack-reused 0
remote: GitLab: Your account has been blocked.
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
Transferred: sent 334008, received 1192064 bytes, in 2.3 seconds
Bytes per second: sent 144390.1, received 515323.6
debug1: Exit status 0
To ssh://gitlab.suse.de/openqa/os-autoinst-needles-sles.git
 ! [remote rejected]       HEAD -> master (pre-receive hook declined)
error: failed to push some refs to 'ssh://gitlab.suse.de/openqa/os-autoinst-needles-sles.git'

and the same for "origin" directly resolving to gitlab.suse.de:openqa/os-autoinst-needles-sles.git.

so key is accepted but still the pre-receive hook declined.

Created https://infra.nue.suse.com/SelfService/Display.html?id=171345 asking SUSE IT to additionally check if the key on gitlab is blocked and can not be unblocked by ourselves. so git push of SLE needles from osd to gitlab.suse.de does not work but saving needles in commits is fine. I created a ticket for SUSE IT to check. There is no problems to save needles on osd though. I have synced the pending needles manually now andI will ensure all pending commits are synced as soon as that is possible automatically again.

hm, according to https://docs.gitlab.com/ee/user/project/deploy_keys/index.html the page https://gitlab.suse.de/openqa/os-autoinst-needles-sles/-/settings/repository should have a section "Deploy Keys" but I can't find it. There is https://gitlab.suse.de/openqa/os-autoinst-needles-sles/-/settings/ci_cd#js-deploy-keys-settings though and there is one active which is active and when I try to add the ssh key there then it tells me it's already in.

#3 Updated by okurz over 1 year ago

  • Priority changed from High to Normal

First part of the problem solved. Apparently we did not use a key from openqa-pusher but nicksinger and his account was blocked. So after he logged in over the webui we could push again. This still leaves the original problem though to avoid a blocked account to not being able to push though. Probably still we should start with using the key from openqa-pusher first.

#4 Updated by okurz over 1 year ago

  • Status changed from In Progress to Workable
  • Assignee deleted (okurz)

#5 Updated by okurz over 1 year ago

  • Copied to action #67804: use non-personal account and key for pushing needles on osd to gitlab.suse.de added

#6 Updated by okurz over 1 year ago

  • Status changed from Workable to Resolved
  • Assignee set to okurz
  • Priority changed from Normal to High

Clearer to have a specific workable ticket for the followup, see #67804

#7 Updated by okurz 11 months ago

  • Related to action #75067: save_needle minion task fails because "Your account has been blocked" added

#8 Updated by okurz 7 months ago

  • Related to action #89047: Failed to commit needles, gitlab account blocked 2021-02-24 added

Also available in: Atom PDF