-
Notifications
You must be signed in to change notification settings - Fork 302
Unpredictable fleetctl load following fleetctl destroy #1073
Comments
What version of fleet is this? It sounds like you are describing the issue in #866, but that was resolved some time ago. |
|
@phuongnd08 That is the client; can you confirm that the fleet agents in your cluster are running the same version? e.g. fleetd --version |
@phuongnd08 Hrm, actually it looks like the fix didn't make it in until 0.9.0, which is in the CoreOS alpha and should make it into the next beta release - are you able to upgrade by any chance? |
|
Btw, when will the next beta be released? Our team is a bit concerning regarding the alpha label. |
Also I'm running coreos-alpha on Digital Ocean and still see |
Weird, what does /etc/os-release say? |
|
@phuongnd08 Given that two days passed between you checking |
Okay, just checked, I got fleet 0.9.0 now. |
Awesome, I just retried and can see that fleetctl is loading the changed service file properly. Thank you! |
So I have a service file, loaded with fleet and then modified it, then reload it with:
I then cat the file from systemd perspective:
cat /run/systemd/system/redisrep.service
The content is then the old unchanged one.
If I run these commands one by one with small delay in the middle, then the content is updated.
What's going on?
The text was updated successfully, but these errors were encountered: