action #80594
closed
Needles are not pushed from o3 to github repo
Added by ggardet_arm about 4 years ago.
Updated about 4 years ago.
Description
Quite often, new needles are created on o3 from webui, but the update is not pushed to github repo and we need to push them manually whereas there is no conflict.
This is a problem, mainly on remote workers which just update from github repo and do not use the NFS share.
- Project changed from openQA Project (public) to openQA Infrastructure (public)
- Priority changed from Normal to Urgent
- Target version set to Ready
The new needle is saved on o3 disk, with a commit message (seen with git log), but the changes are not pushed to github repo, so local repo is ahead, compared to github repo.
- Status changed from New to Feedback
[11:23] Martchus: as an example, this morning, the latest needles omn github were three days old; There was no issue to 'git push' though as geekotest (10 commits pushed); but it should happen automatically
[11:24] Martchus: DimStar was faster than me ;)
[11:24] When one creates a needle via the web UI it is supposed to be pushed automatically (unless configured otherwise).
[11:25] that's our expectation too - yet, the needles were in the master branch on the git clone on ariel, but it was never pushed to github
[11:26] Oh, seems like the config is screwed up, the [scm git] section header was commented out. Likely I screwed that up when updating to Leap 15.2. (I actually cared about migrating configuration changes.)
[11:27] I enabled it again and restarted gru. That should do it.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF