logging setup openstack-dashboard loses source IP addresses

Bug #1829796 reported by James Troup
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard Charm
In Progress
High
Unassigned
OpenStack HA Cluster Charm
Triaged
High
Unassigned

Bug Description

Out of the box, for a Juju deployed OpenStack dashboard, it's impossible to determine the source IP for a given request. For the Apache log files, the IP recorded is that of haproxy and the haproxy logging doesn't seem to actually cause logging on disk as far as I can see.

Ryan Beisner (1chb1n)
Changed in charm-openstack-dashboard:
importance: Undecided → High
milestone: none → 19.07
Changed in charm-hacluster:
importance: Undecided → High
status: New → Triaged
Changed in charm-openstack-dashboard:
status: New → Triaged
Changed in charm-hacluster:
milestone: none → 19.07
David Ames (thedac)
Changed in charm-openstack-dashboard:
milestone: 19.07 → 19.10
Changed in charm-hacluster:
milestone: 19.07 → 19.10
David Ames (thedac)
Changed in charm-openstack-dashboard:
milestone: 19.10 → 20.01
Changed in charm-hacluster:
milestone: 19.10 → 20.01
James Page (james-page)
Changed in charm-openstack-dashboard:
milestone: 20.01 → 20.05
Changed in charm-hacluster:
milestone: 20.01 → 20.05
David Ames (thedac)
Changed in charm-openstack-dashboard:
milestone: 20.05 → 20.08
Changed in charm-hacluster:
milestone: 20.05 → 20.08
James Page (james-page)
Changed in charm-openstack-dashboard:
milestone: 20.08 → none
Changed in charm-hacluster:
milestone: 20.08 → none
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-openstack-dashboard (master)
Changed in charm-openstack-dashboard:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-openstack-dashboard (master)

Change abandoned by "Mert Kırpıcı <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/charm-openstack-dashboard/+/852293

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.