Skip to content
This repository has been archived by the owner on Apr 2, 2024. It is now read-only.

Flags now reset on upgrade-charm? #221

Closed
hloeung opened this issue Mar 7, 2020 · 4 comments
Closed

Flags now reset on upgrade-charm? #221

hloeung opened this issue Mar 7, 2020 · 4 comments

Comments

@hloeung
Copy link

hloeung commented Mar 7, 2020

Hi,

Deploying the content-cache charm. On upgrade-charm, it seems all the content_cache.* flags are removed? See:

https://pastebin.ubuntu.com/p/hjWGdtz6fC/

@hloeung
Copy link
Author

hloeung commented Mar 7, 2020

FYI, the charm clears some, but not all, in particular 'content_cache.nginx.installed'.

https://git.launchpad.net/~content-cache-charmers/content-cache-charm/tree/reactive/content_cache.py#n27

@hloeung
Copy link
Author

hloeung commented Mar 7, 2020

Even removed all the clear_flag() calls in the charm's upgrade_charm() and confirmed that those flags are gone:

https://pastebin.ubuntu.com/p/xfZfrCS3Fs/

@stub42
Copy link
Contributor

stub42 commented Mar 7, 2020

Feels like the sqlite database containing charm state got destroyed. Did it happen to get packaged in the built charm? That would do it.

@hloeung
Copy link
Author

hloeung commented Mar 8, 2020

Ah, that's exactly what it is. Didn't run 'make clean' and .unit-state.db was still around.

@hloeung hloeung closed this as completed Mar 8, 2020
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