Bug 1623977

Summary: [RFE] Log offloading from amphorae to a central system (rsyslog)
Product: Red Hat OpenStack Reporter: Bernard Cafarelli <bcafarel>
Component: openstack-tripleo-heat-templatesAssignee: Michael Johnson <michjohn>
Status: CLOSED CURRENTRELEASE QA Contact: Omer Schwartz <oschwart>
Severity: high Docs Contact:
Priority: high    
Version: 16.0 (Train)CC: afariasa, amcleod, amuller, atragler, bbonguar, cgoncalves, dcadzow, gregraka, ihrachys, jamsmith, jschluet, lpeer, ltamagno, madgupta, majopela, mburns, michjohn, njohnston, pmorey, tfreger
Target Milestone: z2Keywords: FutureFeature, TestOnly, Triaged
Target Release: 16.1 (Train on RHEL 8.2)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-octavia-15.4.1-0.20200414073424.8bae62d.el8ost openstack-tripleo-common-11.3.3-0.20200611110653.f7715be.el8ost openstack-tripleo-heat-templates-11.3.2-0.20200616123428.abf6c28.el8ost tripleo-ansible-0.5.1-0.20200611183519.ccd7be7.el8ost Doc Type: Known Issue
Doc Text:
When you enable Load-balancing service instance (amphora) log offloading, both the administrative logs and the tenant logs are written to the same file (`octavia-amphora.log`). This is a known issue caused by an incorrect default value for the Orchestration service (heat) parameter, `OctaviaTenantLogFacility`. As a workaround, perform the following steps: + Set `OctaviaTenantLogFacility` to zero (0) in a custom environment file and run the `openstack overcloud deploy` command: + ---- parameter_defaults: OctaviaLogOffload: true OctaviaTenantLogFacility: 0 ... ---- + For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/director_installation_and_usage/performing-basic-overcloud-administration-tasks#modifying-the-overcloud-environment[Modifying the overcloud environment]
Story Points: ---
Clone Of:
: 1795708 (view as bug list) Environment:
Last Closed: 2020-10-21 10:53:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1856835, 1860658, 1877689, 1883536    
Bug Blocks: 1766770, 1795708    

Description Bernard Cafarelli 2018-08-30 15:11:36 UTC
To help debugging, operators should not have to login a suspect amphora to check logs. Also if an amphora rotation happens, logs will be lost.

So logs should be collected in a centralized system, and the amphorae configured to send logs there

From Octavia roadmap:
https://wiki.openstack.org/wiki/Octavia/Roadmap

Comment 4 Andre 2019-04-02 14:46:32 UTC
I'd like to reinforce this bugzilla, I have a ticket that's waiting for this resolution.
In the meantime, do we have any workaround on this issue?

Comment 7 Carlos Goncalves 2019-05-13 07:59:09 UTC
Andre, currently there's no work-around supported by Engineering. One possible way to work-around is by editing the amphora image to set a target rsyslog server. GSS may be able to assist the customer should they run into a problem. For support exception of this workaround or another viable way, please open a support exception request.

Comment 8 Carlos Goncalves 2019-06-14 15:47:18 UTC
Work progresses well upstream and is close to being approved. Next steps include adding support in puppet-octavia and tripleo-heat-templates, and official documentation.

Comment 14 Andre 2019-11-20 11:46:59 UTC
Hi, can we have a backport for OSP13? Is it doable?

Comment 15 Michael Johnson 2019-11-20 14:28:03 UTC
Andre,

That may be possible, we will need to raise the request with the PM.

Comment 32 Lon Hohberger 2020-07-29 10:49:41 UTC
According to our records, this should be resolved by puppet-octavia-15.4.1-0.20200414073424.8bae62d.el8ost.  This build is available now.

Comment 33 Lon Hohberger 2020-07-29 10:49:45 UTC
According to our records, this should be resolved by openstack-tripleo-common-11.3.3-0.20200611110656.f7715be.el8ost.  This build is available now.

Comment 36 Omer Schwartz 2020-10-21 08:57:14 UTC
Manual verification succeeded, moving this RFE to VERIFIED.