Bug 2017112

Summary: lftp: MLSD parsing issue with Cerberus FTP Server with the "mirror" command.
Product: Red Hat Enterprise Linux 8 Reporter: Stepan Broz <sbroz>
Component: lftpAssignee: Michal Ruprich <mruprich>
Status: CLOSED MIGRATED QA Contact: rhel-cs-infra-services-qe <rhel-cs-infra-services-qe>
Severity: medium Docs Contact:
Priority: low    
Version: 8.4Keywords: MigratedToJIRA, Reproducer, Triaged
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-28 14:07:38 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:

Comment 3 Michal Ruprich 2021-11-01 11:22:13 UTC
One more thing, would it be possible to run the command with -d to see the debug output of lftp?

Comment 8 Michal Ruprich 2021-11-10 12:57:47 UTC
Once again, thanks for the great reproducer. It helped me narrow it down to a particular function in lftp but at this point I had to ask the upstream, hopefully Alex will be able to help because I cannot figure out the final logic in selecting the correct parser for the list of files.

The upstream bug is here: https://github.com/lavv17/lftp/issues/652

Comment 12 RHEL Program Management 2023-08-28 14:07:03 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 13 RHEL Program Management 2023-08-28 14:07:38 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.