0.13: [Bug]: sync status not correct

[jalper]

Garden Bonsai (0.13) Bug

Current Behavior

The new sync status command doesn't seem to be working as expected. When running it in a project with a whole bunch of syncs configured, after starting the syncs, they all show as "not-active". But if I run garden plugins kubernetes sync-status they all show as status: watching

Your environment

• OS: macOS
• How I'm running Kubernetes: GKE

% garden version
0.13.0

[Orzelius]

@jalper Thank you for reporting this. As there's a workaround we might prioritize a few other issues before this but we'll have a look in a couple of weeks.

[vvagaytsev]

@jalper I wasn't able to reproduce this. Tried the vote project in the following way:

1. Deployed it in sync mode gdev deploy --sync (gdev is the local alias. that points to the latest build of the main branch)
2. Got to the dev console, tried sync status and got active
3. Executed gdev plugins local-kubernetes sync-status from another terminal inside the vote example directory and got active syncs
4. Exited the dev console with exit command -> syncs got stopped
5. Executed gdev sync status and got non-active status as expected (because the syncs were stopped on exit form the dev console)
6. Executed gdev plugins local-kubernetes sync-status from another terminal again and got no syncs.

Is it still reproducible? If it is, could you share a repro example, please?

[jalper]

@vvagaytsev definitely still an issue. When I try on our platform repo I get a mix of active and not-active when they should all be showing as active. I can try to put together a simpler repro next week if I have time.

[eysi09]

Yes, I can confirm I'm seeing the same.

To repro:

1. In platform repo, run: garden deploy --sync
2. Once it finishes deploying, run garden sync status and notice that it's not correct.

Also: The not-active status is logged with a the color green, it should be yellow.

And the text that says something like: The api Deploy has 5 sync(s) configured should instead be The api Deploy action has 5 sync(s) configured (that is, adding action).

Perhaps we can fix that while we're at it.

[eysi09]

I'm setting the priority to high on this one since the same information is displayed on the live page.