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

If configured branch didn't exist at first launch, flux won't find it later #2370

Closed
@yellowmegaman

Description

@yellowmegaman

Describe the bug
When pointing flux on non-existing (yet) branch in git, it will say branch "does not exist", even if branch is created after that. Have to manually kill flux pod.

To Reproduce
Steps to reproduce the behaviour:

  1. GKE cluster + flux + github
  2. Launch flux
  3. point it to repo A branch A
  4. it will say "does not exist"
  5. create that branch
  6. still get error until delete flux pod to restart.

Expected behavior
Flux should just work with created branch

Logs

2019-08-16 14:53:24.025 MSK
ts=2019-08-16T11:53:24.024322937Z caller=loop.go:85 component=sync-loop err="git repo not ready: configured branch 'killpinbug' does not exist"
2019-08-16 14:56:24.025 MSK
ts=2019-08-16T11:56:24.025343062Z caller=loop.go:85 component=sync-loop err="git repo not ready: configured branch 'killpinbug' does not exist"

Additional context
Add any other context about the problem here, e.g

  • Flux version: 1.13.1
  • Kubernetes version: 1.13.7-gke.8
  • Git provider: github
  • Container registry provider: gcr.io

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    blocked-needs-validationIssue is waiting to be validated before we can proceedbug

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions