Bug 1218406 - FTP Log Depot validation doesn't work
Summary: FTP Log Depot validation doesn't work
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.4.0
Assignee: Martin Hradil
QA Contact: Milan Falešník
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-04 19:56 UTC by Pete Savage
Modified: 2015-06-16 13:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-16 13:01:24 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1100 0 normal SHIPPED_LIVE CFME 5.4.0 bug fixes, and enhancement update 2015-06-16 16:28:42 UTC

Description Pete Savage 2015-05-04 19:56:37 UTC
Description of problem: FTP Log Depot validation doesn't work


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


How reproducible: 100%


Steps to Reproduce:
1. Go to Configure -> Configuration -> Diagnostics
2. Choose either Zone or Server level
3. Select Collect Logs Tab
4. Choose FTP for the Depot type
5. In each of the remaining boxes, type 'set'
6. Click Validate

Actual results:
Flash messages appears saying that Validation was successful

Expected results:
Validation is not being properly checked


Additional info:

Comment 1 Pete Savage 2015-05-04 19:59:17 UTC
Obviously the Expected results are that validation is performed properly.

Comment 4 Martin Hradil 2015-05-05 13:26:03 UTC
This is indeed familiar, caused by FTP validation not throwing.. already fixed in https://github.com/ManageIQ/manageiq/pull/2332

Comment 5 Milan Falešník 2015-05-12 11:46:26 UTC
Verified working in 5.4.0.0.26

Comment 8 errata-xmlrpc 2015-06-16 13:01:24 UTC
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://rhn.redhat.com/errata/RHBA-2015-1100.html


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