Upgrade to Grafana v5.0.1 did not cleanly restart the service

Bug #1755315 reported by Tejeev Patel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Grafana Charm
Expired
Medium
Unassigned

Bug Description

Web page would not load and we got 404s on access:

t=2018-03-12T22:57:18+0000 lvl=info msg="Request Completed" logger=context userId=0 orgId=0 uname= method=GET path=/ status=302 remote_addr=10.101.140.6 time_ms=0 size=29 referer=
t=2018-03-12T22:57:19+0000 lvl=info msg="Request Completed" logger=context userId=0 orgId=0 uname= method=GET path=/public/build/manifest.979c370f20ff0db1a23c.js status=404 remote_addr=10.101.140.6 time_ms=2 size=8772 referer=http://10.101.140.75:3000/login
t=2018-03-12T22:57:19+0000 lvl=info msg="Request Completed" logger=context userId=0 orgId=0 uname= method=GET path=/public/build/vendor.2305a8e1d478628b1297.js status=404 remote_addr=10.101.140.6 time_ms=1 size=8772 referer=http://10.101.140.75:3000/login
t=2018-03-12T22:57:19+0000 lvl=info msg="Request Completed" logger=context userId=0 orgId=0 uname= method=GET path=/public/build/app.5331f559bd9a1bed9a93.js status=404 remote_addr=10.101.140.6 time_ms=2 size=8772 referer=http://10.101.140.75:3000/login
t=2018-03-12T22:57:19+0000 lvl=info msg="Request Completed" logger=context userId=0 orgId=0 uname= method=GET path=/public/build/app.5331f559bd9a1bed9a93.js status=404 remote_addr=10.101.140.6 time_ms=2 size=8772 referer=http://10.101.140.75:3000/login

Restart resolved

Revision history for this message
Wouter van Bommel (woutervb) wrote :

How was the upgrade performed, and how can this be reproduced. Need some more information about the process used to validate this issue.

Changed in charm-grafana:
status: New → Incomplete
Revision history for this message
Joe Guo (guoqiao) wrote :

I checked the code, while `upgrade-charm` hook is triggered, the charm just remove `grafana.installed` flag, which will trigger `install_packages`. In there, the code doesn't consider the situation of re-install and upgrade, which may need a restart. Of course the apt or snap package manager may do that, but not guaranteed. It will be better if the code can check the current service status and do a restart if necessary.

Changed in charm-grafana:
importance: Undecided → Medium
Joe Guo (guoqiao)
Changed in charm-grafana:
status: Incomplete → Triaged
assignee: nobody → Joe Guo (guoqiao)
Revision history for this message
Tejeev Patel (tejeevpatel) wrote :

Not sure.. this was filed 2 years ago and I don't even remember what customer's stack I was working on. Maybe there's a record in the bootstack salesforce tickets, but I don't have access any more.

Revision history for this message
Joe Guo (guoqiao) wrote :

Hi Tejeev,
thanks for your reply, in this case I will change the status back to Incomplte for now until we have further issue.

Changed in charm-grafana:
assignee: Joe Guo (guoqiao) → nobody
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Grafana Charm because there has been no activity for 60 days.]

Changed in charm-grafana:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.