action #63133

action #58184: [epic][use case] full version control awareness within openQA, e.g. user forks and branches

action #45302: [epic] smarter fetchneedles (was: fetchneedles should ensure we are always on a branch (and try to self-repair))

SLE needles git repo looses upstream branch configuration, needles are saved but fail to be pushed

Added by okurz about 1 month ago. Updated about 1 month ago.

Status:ResolvedStart date:05/02/2020
Priority:NormalDue date:
Assignee:okurz% Done:

0%

Category:Concrete Bugs
Target version:Current Sprint
Difficulty:
Duration:

Description

Observation

Unable to push Git commit: fatal: The current branch master has no upstream branch.
To push the current branch and set the remote as upstream, use

git push --set-upstream origin master

or

/var/lib/openqa/share/tests/sle/products/sle/needles> sudo -u geekotest /usr/share/openqa/script/fetchneedles
There is no tracking information for the current branch.
Please specify which branch you want to rebase against.
See git-rebase(1) for details.

    git rebase <branch>

If you wish to set tracking information for this branch you can do so with:

    git branch --set-upstream-to=origin/<branch> master

Problem

I suspect 2aadd3e56 was incomplete in the sense that we recreate the master branch but never set the upstream information.

History

#1 Updated by okurz about 1 month ago

  • Status changed from In Progress to Feedback

#2 Updated by cdywan about 1 month ago

  • Target version set to Current Sprint

#3 Updated by okurz about 1 month ago

  • Status changed from Feedback to Resolved

was deployed to osd, haven't received any negative report. Just checked again now and osd needles repos are on a proper branch and fetchneedles doesn't complain about anything.

Also available in: Atom PDF