[ocata][17.02] a restart of all apache2 services was required to avoid incorrect horizon page rendering after charm upgrade to add lbaasv2

Bug #1711195 reported by Dmitrii Shcherbakov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard Charm
Fix Released
Undecided
Unassigned

Bug Description

This needs to be reproduced again to be certain but after a charm upgrade to fix https://bugs.launchpad.net/charm-openstack-dashboard/+bug/1658105 I had incorrect page rendering in multiple browsers until I ran this:

ubuntu@maas:~/bundles⟫ juju run --application openstack-dashboard 'sudo systemctl restart apache2'
- Stdout: ""
  UnitId: openstack-dashboard/0
- Stdout: ""
  UnitId: openstack-dashboard/1
- Stdout: ""
  UnitId: openstack-dashboard/2

Although the following code is present:

https://github.com/openstack/charm-openstack-dashboard/blob/stable/17.02/hooks/horizon_hooks.py#L110

https://github.com/openstack/charm-openstack-dashboard/blob/stable/17.02/hooks/horizon_utils.py#L233-L248

https://github.com/openstack/charm-openstack-dashboard/blob/stable/17.02/hooks/horizon_utils.py#L127-L182

A screenshot is attached.

Revision history for this message
Dmitrii Shcherbakov (dmitriis) wrote :
description: updated
David Ames (thedac)
Changed in charm-openstack-dashboard:
status: New → Triaged
importance: Undecided → High
milestone: none → 17.11
David Ames (thedac)
Changed in charm-openstack-dashboard:
assignee: nobody → David Ames (thedac)
Revision history for this message
David Ames (thedac) wrote :

Dmitrii,

I have run this test a few times and I have been unable to re-create the problem.

Workflow:
Deploy with charm before https://github.com/openstack/charm-openstack-dashboard/commit/65d500392488d1dc987a021760e01f89a6235b0a
Enable neutron-network-lb
Load horizon (load balancer page missing due to missing plugin)
Upgrade charm to current master
Load horizon at load balancer page

I also confirmed that apache2 is has been restarted after the charm upgrade.

Can you think of any other circumstances for re-creating the bug? Marking this incomplete for now.

Changed in charm-openstack-dashboard:
status: Triaged → Incomplete
James Page (james-page)
Changed in charm-openstack-dashboard:
milestone: 17.11 → 18.02
Ryan Beisner (1chb1n)
Changed in charm-openstack-dashboard:
milestone: 18.02 → 18.05
David Ames (thedac)
Changed in charm-openstack-dashboard:
milestone: 18.05 → 18.08
James Page (james-page)
Changed in charm-openstack-dashboard:
milestone: 18.08 → 18.11
David Ames (thedac)
Changed in charm-openstack-dashboard:
milestone: 18.11 → 19.04
David Ames (thedac)
Changed in charm-openstack-dashboard:
milestone: 19.04 → 19.07
David Ames (thedac)
Changed in charm-openstack-dashboard:
milestone: 19.07 → 19.10
David Ames (thedac)
Changed in charm-openstack-dashboard:
milestone: 19.10 → 20.01
tags: added: charm-upgrade
Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

It's down to undecided, and likely will be made invalid as there's been no activity for 2 years.

Changed in charm-openstack-dashboard:
importance: High → Undecided
James Page (james-page)
Changed in charm-openstack-dashboard:
milestone: 20.01 → 20.05
David Ames (thedac)
Changed in charm-openstack-dashboard:
milestone: 20.05 → 20.08
James Page (james-page)
Changed in charm-openstack-dashboard:
milestone: 20.08 → none
Revision history for this message
David Ames (thedac) wrote :

Aging this one out per Alex's comment #3

Changed in charm-openstack-dashboard:
status: Incomplete → Fix Released
assignee: David Ames (thedac) → nobody
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.