Failure in browser_ui/3_create/repository/push_over_ssh_spec.rb | Create SSH key support pushes multiple branches and tags together

Full description

Create SSH key support pushes multiple branches and tags together

File path

./qa/specs/features/browser_ui/3_create/repository/push_over_ssh_spec.rb

Stack trace

Failure/Error: repository.push_tags_and_branches(branches)

QA::Support::Run::CommandError:
  The command HOME="/tmp/qa-netrc-credentials/27" GIT_SSH_COMMAND="ssh -i /tmp/id_3d4cd3a0900ca6b020230414-27-ei7aig -o UserKnownHostsFile=/tmp/known_hosts_ce83c8f004a8fced20230414-27-rt8cdm -o IdentitiesOnly=yes" git push --tags origin branch1 branch2 branch3 2>&1 failed (1) with the following output:
  remote: 
  remote: INFO: Your SSH key is expiring soon. Please generate a new key.
  remote: 
  remote: GitLab: Internal API error (404)
  To ssh://staging.gitlab.com/gitlab-qa-sandbox-group-6/qa-test-2023-04-14-17-44-05-eb2dc52737c1b3d5/ssh-tests-6811f405aade389c.git
   ! [remote rejected] branch1 -> branch1 (pre-receive hook declined)
   ! [remote rejected] branch2 -> branch2 (pre-receive hook declined)
   ! [remote rejected] branch3 -> branch3 (pre-receive hook declined)
   ! [remote rejected] tag1 -> tag1 (pre-receive hook declined)
   ! [remote rejected] tag2 -> tag2 (pre-receive hook declined)
   ! [remote rejected] tag3 -> tag3 (pre-receive hook declined)
  error: failed to push some refs to 'ssh://staging.gitlab.com/gitlab-qa-sandbox-group-6/qa-test-2023-04-14-17-44-05-eb2dc52737c1b3d5/ssh-tests-6811f405aade389c.git'

First happened in https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/9783878.

Related test case: https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/347826.

Screenshot:

added QA Quality failurenew found:staging.gitlab.com priority2 test labels

Failed most recently in staging pipeline: https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/9784158

changed due date to May 14, 2023

assigned to @jay_mccure

mentioned in issue gitlab-org/quality/testcase-sessions#68901 (closed)

This issue was automatically tagged with the label groupsource code by TanukiStan, a machine learning classification model, with a probability of 1.

If this label is incorrect, please tag this issue with the correct group label as well as automation:ml wrong to help TanukiStan learn from its mistakes.

If you are unsure about the correct group, please do not leave the issue without a group label. Please refer to GitLab's shared responsibility functionality guidelines for more information on how to triage this kind of issues.

Authors who do not have permission to update labels can leave the issue to be triaged by group leaders initially assigned by TanukiStan

This message was generated automatically. You're welcome to improve it.

added automation:ml groupsource code labels

added devopscreate sectiondev labels

Setting label(s) Category:Source Code Management based on groupsource code.

added Category:Source Code Management label

mentioned in issue gitlab-org/quality/pipeline-triage#193 (closed)

mentioned in issue gitlab-org/quality/pipeline-triage#194 (closed)

mentioned in merge request gitlab-org/quality/triage-ops!2179 (merged)

added failuretest-environment label and removed failurenew label

closed