Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1358826

Summary: vsftpd configuration file checked for uncompatible directives
Product: Red Hat Enterprise Linux 6 Reporter: Jakub Mazanek <jmazanek>
Component: preupgrade-assistant-el6toel7Assignee: Jakub Mazanek <jmazanek>
Status: CLOSED ERRATA QA Contact: Alois Mahdal <amahdal>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.9CC: jmazanek, ovasik, pstodulk
Target Milestone: rcKeywords: 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
Description of problem:

Module of preupgrade-assistant-el6toel7 checks if there are not mutually conflicting directives listen and listen_ipv6 defined in /etc/vsftpd/vsftpd.conf.

If the chroot_list_enabled=YES directive exists it informs the user how to allow writeable chrooted environment on upgraded system

If the variable chroot_list_file is set, the list of chrooted users is backed up

Main configuration file is also backed up

Additional info:

Comment 2 Alois Mahdal 2016-07-22 03:45:40 UTC
Acking, although i's a bit unclear: are you aware that vsftpd module existed before? is the old behavior preserved plus this one?

Comment 3 Jakub Mazanek 2016-07-22 05:53:25 UTC
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

Comment 6 Alois Mahdal 2016-10-20 16:19:55 UTC
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.

Comment 8 errata-xmlrpc 2016-11-04 09: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/RHEA-2016-2618.html