the source secret is not updated when re-bootstraping to new repo

[zxkane]

trafficstars

Describe the bug

Following the doc to re-bootstrap to another github repo.

The bootstrap failed with below output.

$ flux bootstrap github --owner=zxkane --repository=eks-gitops4 --path=clusters/gitops-cluster --personal
► connecting to github.com
✔ repository "https://github.com/zxkane/eks-gitops4" created
► cloning branch "main" from Git repository "https://github.com/zxkane/eks-gitops4.git"
✔ cloned repository
► generating component manifests
✔ generated component manifests
✔ committed sync manifests to "main" ("9e7b384216333d7ef8863e4320975a80a63daa59")
► pushing component manifests to "https://github.com/zxkane/eks-gitops4.git"
✔ reconciled components
► determining if source secret "flux-system/flux-system" exists
✔ source secret up to date
► generating sync manifests
✔ generated sync manifests
✔ committed sync manifests to "main" ("cde961145c99a8cb7de206fdf75c575bde0073bd")
► pushing sync manifests to "https://github.com/zxkane/eks-gitops4.git"
► applying sync manifests
✔ reconciled sync configuration
◎ waiting for Kustomization "flux-system/flux-system" to be reconciled
✗ context deadline exceeded
► confirming components are healthy
✔ helm-controller: deployment ready
✔ kustomize-controller: deployment ready
✔ notification-controller: deployment ready
✔ source-controller: deployment ready
✔ all components are healthy
✗ bootstrap failed with 1 health check failure(s)

Steps to reproduce

1. export GITHUB_TOKEN=
2. bootstrap flux flux bootstrap github --owner=zxkane --repository=eks-gitops --path=clusters/gitops-cluster --personal
3. rebootstrap to another repo flux bootstrap github --owner=zxkane --repository=eks-gitops4 --path=clusters/gitops-cluster --personal

Expected behavior

The bootstrap command runs successfully.

Screenshots and recordings

No response

OS / Distro

ubuntu 18.04

Flux version

v0.26.2

Flux check

► checking prerequisites ✔ Kubernetes 1.21.5-eks-bc4871b >=1.20.6-0 ► checking controllers ✔ helm-controller: deployment ready ► ghcr.io/fluxcd/helm-controller:v0.16.0 ✔ kustomize-controller: deployment ready ► ghcr.io/fluxcd/kustomize-controller:v0.20.1 ✔ notification-controller: deployment ready ► ghcr.io/fluxcd/notification-controller:v0.21.0 ✔ source-controller: deployment ready ► ghcr.io/fluxcd/source-controller:v0.21.2 ✔ all checks passed

Git provider

No response

Container Registry provider

No response

Additional context

remove existing secrets from namespace flux-system then rebootstrap works

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[stefanprodan]

This is by design, changing the bootstrap target or auth method is not supported. You need to do flux uninstall or delete the flux-system secret with kubectl.

[zxkane]

The UX is not friendly. As a user I see the new repo was created and the configuration of flux was pushed. If it's not supported, the clear message would be helpful a lot.

Stefan Prodan @.***> 于 2022年2月10日周四 下午4:49写道：

This is by design, changing the bootstrap target or auth method is not supported. You need to do flux uninstall or delete the flux-system secret with kubectl.

— Reply to this email directly, view it on GitHub https://github.com/fluxcd/flux2/issues/2414#issuecomment-1034648776, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGN4J2YDPRJLMOLQPKWHDDU2N3Z3ANCNFSM5N77RNPA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>