Red Hat Bugzilla – Bug 1197869
CFME 5.3.3 Zone Level Log collection incorrectly references and uses the appliance level log depot instead of zone level specified depot
Last modified: 2016-07-12 05:19:44 EDT
Description of problem:Zone Level log collection is intended to provide a simple one-click means of collecting all logs for all appliances within a zone. When CFME Zone level log collection is requested with the 5.3.3 version, individual appliance level depot settings are examined and if empty the log collection fails, and if not empty are used to target the log collections instead of the zone-defined depot. Version-Release number of selected component (if applicable): 5.3.3.2 How reproducible: to recreate log collection failure, create zone level depot and leave appliance level depot unspecified. Request zone-level log collection from UI. UI indicates that log collection is started, but evm.log reports that log collection fails because depot is not configured. to recreate error where logs are directed to appliance level depot instead of zone-level depot, configure the zone level depot to a location other than the configuration specified for the appliance level depot, then request zone level log collection. Notice that the logs are not directed to the zone specified depot, but the appliance specified depot. In a multiple appliance zone this means that logs will be inconsistently collected or for some appliances, not collected at all. Steps to Reproduce: see above 1. 2. 3. Actual results: see above Expected results: if zone level depot is specified, and it exists, and it is contactable, logs for all appliances in the zone should be deposited into this depot. Additional info:
Joe, I wasnt able to confirm it because the log collection setup is blocked by https://github.com/ManageIQ/manageiq/issues/1506.
Josh, could you ack/nack the blocker flag based on GSS's opinion to how bad this is for you guys please.
Implemented upstream in https://github.com/ManageIQ/manageiq/pull/5864, fixing: https://github.com/ManageIQ/manageiq/issues/1962
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1348