Bug 1358826
| Summary: | vsftpd configuration file checked for uncompatible directives | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jakub Mazanek <jmazanek> |
| Component: | preupgrade-assistant-el6toel7 | Assignee: | Jakub Mazanek <jmazanek> |
| Status: | CLOSED ERRATA | QA Contact: | Alois Mahdal <amahdal> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.9 | CC: | jmazanek, ovasik, pstodulk |
| Target Milestone: | rc | Keywords: | Extras |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | preupgrade-assistant-el6toel7-0.6.52-1.el6 | Doc Type: | No Doc Update |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-04 09:01:24 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: | |||
| Bug Blocks: | 1335038 | ||
|
Description
Jakub Mazanek
2016-07-21 14:42:03 UTC
Acking, although i's a bit unclear: are you aware that vsftpd module existed before? is the old behavior preserved plus this one? Yes, the previous functionality has been preserved. This is an enhancement. New features were added first to preupgrade-assistant-el5toel7, based on input from the testers and I would like to include them in preupgrade-assistant-el6toel7. For relevant discussion please see : https://bugzilla.redhat.com/show_bug.cgi?id=1346803 Verified with preupgrade-assistant-el6toel7-0.6.59-4.el6: Original behavior is not tested thoroughly but it is assumed that in any case, SLIGHT risk is logged regarding different behavior of listen* directives. If both listen and listen_ipv6 are enabled, an extra MEDIUM risk (plus solution text) is logged to warn user that vsftpd would not start properly after upgrade. When chroot_list_file directive is set to a path, the file at this path is properly backed up in dirtyconf. 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/RHEA-2016-2618.html |