Project

General

Profile

Actions

Bug #44182

closed

ceph-backport.sh: Can't set backport environment up

Added by Tatjana Dehler about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Community (dev)
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

I tried to set up a backport environment by using "ceph-backport.sh --setup". It asked me for my Github token. I provided the correct token but it failed:

ceph-backport.sh --setup
ceph-backport.sh: WARNING: /path/to/.github_token not populated: initiating interactive setup routine
ceph-backport.sh: WARNING: /path/to/.redmine_key not populated: initiating interactive setup routine
ceph-backport.sh: ERROR: Cannot auto-determine fork remote
ceph-backport.sh: (Could not find GitHub user 's fork of ceph/ceph in "git remote -v")

=============================================
        ceph-backport.sh setup report
=============================================
variable name    value
---------------------------------------------
redmine_endpoint https://tracker.ceph.com
redmine_user_id  !!! NOT SET !!!
redmine_key      !!! NOT SET !!!
github_endpoint  https://github.com/ceph/ceph
github_user      !!! NOT SET !!!
github_token     !!! NOT SET !!!
upstream_remote  origin
fork_remote      !!! NOT SET !!!
---------------------------------------------
ceph-backport.sh: setup is NOT OK
==============================================

Run the interactive setup routine now? (default: y) y

Welcome to the ceph-backport.sh interactive setup routine!

---------------------------------------------------------------------
Setup step 1 of 4 - GitHub token
---------------------------------------------------------------------
For information on how to generate a GitHub personal access token
to use with this script, go to https://github.com/settings/tokens
then click on "Generate new token" and make sure the token has
"Full control of private repositories" scope.

For more details, see:
https://help.github.com/en/articles/creating-a-personal-access-token-for-the-command-line

What is your GitHub token? my-secret-github-token
ceph-backport.sh: You must provide a valid GitHub personal access token
ceph-backport.sh: ERROR: problem detected in your setup
ceph-backport.sh: Run "ceph-backport.sh --setup" to fix

Could it possibly be related to https://github.com/ceph/ceph/commit/3de3797bba995308e1c8d6baf38324d38d031510#diff-3ef57d65f9ba2ac8e625e4a27c342e9aL603 ?

Actions #1

Updated by Nathan Cutler about 4 years ago

  • Status changed from New to In Progress
  • Assignee set to Nathan Cutler
Actions #2

Updated by Nathan Cutler about 4 years ago

Thanks, Tatjana, your analysis was "right on the mark". This is a regression I introduced with 3de3797bba995308e1c8d6baf38324d38d031510

Actions #3

Updated by Nathan Cutler about 4 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 33456
Actions #4

Updated by Tatjana Dehler about 4 years ago

  • Status changed from Fix Under Review to Resolved
Actions

Also available in: Atom PDF