Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Flux master isn't moving the sync tag #967

Closed
samb1729 opened this issue Feb 27, 2018 · 6 comments
Closed

Flux master isn't moving the sync tag #967

samb1729 opened this issue Feb 27, 2018 · 6 comments
Assignees

Comments

@samb1729
Copy link
Contributor

Some change in #940 broke moving the tag in the upstream repo. Track findings here, or hopefully just close with a simple fix.

@samb1729 samb1729 self-assigned this Feb 27, 2018
@squaremo
Copy link
Member

I tried a fluxd built from master, giving it an upstream of an instance on our dev env. It sent notifications fine, when I did a push-button release, and after I turned automation on :/

Worth verifying this for yourself of course. Otherwise, perhaps we could try putting the more recent fluxd back in dev and watching the logs for errors while doing push-button releases etc.

@samb1729
Copy link
Contributor Author

I'll unlock dev, let it release the latest flux, and report back. 🤓

@samb1729
Copy link
Contributor Author

Still broken for now it seems

@squaremo
Copy link
Member

Still broken for now it seems

But did you get the logs? That was the point of the exercise!

@squaremo
Copy link
Member

OK I have some logs now. The important message is this (and its ilk):

ts=2018-02-28T10:25:21.26352628Z caller=logging.go:66 component=upstream method=SyncStatus error="fatal: ambiguous argument 'k8s/dev': unknown revision or path not in the working tree."

i.e., I've got the git arguments wrong somewhere. Checking it out now, locally.

@samb1729
Copy link
Contributor Author

I grepped the logs for errors and didn't find that one. Failure on my part I suppose. Good find 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants