Bug 1188359 - CFME 5.3.2.6 log collection to FTP stopped working due to removal of behavior of CFME to create directory structure required by log collection.
Summary: CFME 5.3.2.6 log collection to FTP stopped working due to removal of behavior...
Keywords:
Status: CLOSED DUPLICATE of bug 1184465
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.3.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: GA
: 5.4.0
Assignee: Joe Rafaniello
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-02 16:53 UTC by Thomas Hennessy
Modified: 2015-02-02 23:15 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-02 23:15:57 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Thomas Hennessy 2015-02-02 16:53:45 UTC
Description of problem:in previous releases of CFME, collecting current or archive logs to FTP depot worked because CFME code would recognize absense of a directory structure required and create it.  This level of CFME now fails for all FTP log collections reporting cause as missing directory structure.


Version-Release number of selected component (if applicable): 5.3.2.6


How reproducible:


Steps to Reproduce:
1. From UI of running CFME 5.3.2.6 appliance, specify a valid FTP depot with valid credentials and save.
2. Initiate any appliance level log collection to that depot
3.

Actual results: evm.log indicates that required directory is not found and fails log collection to FTP depot.


Expected results: creation of necessary directories required by CFME to store the logs it has just created.


Additional info:

Comment 2 Dave Johnson 2015-02-02 17:45:28 UTC
Bumping the sev as this is blocking support

Comment 3 Joe Rafaniello 2015-02-02 23:15:57 UTC
This looks to be a duplicate of 1184465.  Please re-open with differences if it's not.

*** This bug has been marked as a duplicate of bug 1184465 ***


Note You need to log in before you can comment on or make changes to this bug.