Giters

adamcooke / staytus

đź’ˇ An open source solution for publishing the status of your services

Home Page:http://staytus.co

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Status won't update with issue

alexandredpy opened this issue · comments

commented

Hello,
I installed twice Staytus by following atech's tutorial, and by replacing mysql with mariadb.

When I declare an issue, even when I set the status to an outage, the impacted devices won't update their status and will remain Operational. It means that on the public homepage, the devices are still "Operational".

I tried also to change the status by doing an update on the issue, but it won't change the status.

Best regards

image
image
image

commented

I observed this issue as well and can reproduce. It seems like updating a status to include other services does not properly update those service statuses to match the status post: it only seems to care about the initial "services" that were logged with the creation of the status update itself. Bit frustrating because you may find other services going down after making the status post (even if they worked before, or you need to reboot everything), meaning proper logging of the issue isn't as streamlined as it should be.

commented

We have the same problem. Please indicate where to check and how to fix this (if it is an installation issue).
We run still on MySQL. Thanks.

commented

Hello, any update from the dev team ?
Thanks ;)

commented

@adamcooke tagging in case this has been missed (and as per readme) :)

commented

I'm seeing the same thing. At first I thought it was something I messed up in the version I compile into a docker container, but I guess not.

commented

Same problem here too, any updates/fixes for this? Status updates fine if you edit it via the services creation page which works as a work around currently but is a pain if multiple services are affected.

commented

Hey @naft-a how can I deploy this patch to my local installation? I switched to your branch and did this:

sudo -u staytus bundle install --deployment --without development:test
sudo -u staytus bundle exec rake staytus:build
sudo -u staytus bundle exec rake staytus:install

But the issue is still existing. In the git log history I see that your branch is active:

commit 6ed2120 (HEAD -> fix-issue-services-status-updates, origin/fix-issue-services-status-updates)
Author: Georgi Ganchev googs.bs@gmail.com
Date: Wed Mar 10 11:41:51 2021 +0000

tweak: changes attr_changed? to saved_change_to_attr?

Do you have a hint for me to deploy this patch to my installation?

commented

Hello @naft-a
I applied your change to the file issue.rb, but nothing changes for me.

Made a new issue, declared a status change (major outage for example), but after saving the issue it doesn't change the device's status.

Stopped the server (procodile stop), made the change, and started the server (procodile start).

Any help?
thanks

commented

Hi,
Are there any updates on resolving this, even if manually changing a file?

Thanks

commented

Hi,
I just installed Staytus from the master branch, I'm not 100% sure that it's the same issue than the original post, but it looks like.

When I create an issue, no matter the status I choose : the status is always "Operational"
Then, if I change the status of the previously created issue, to the first status that I chose : the status still remains "Operational"
And if I change the status of the previously created issue, to another status that the one I chose : the status correctly updates

Am I the only one to still have this problem ?

Thanks for you help