Bug 1708996 - systemd-mount fails with commandline-specified cifs path ("non-normalized")
Summary: systemd-mount fails with commandline-specified cifs path ("non-normalized")
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 29
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-12 11:06 UTC by Trevor Cordes
Modified: 2019-08-07 01:55 UTC (History)
6 users (show)

Fixed In Version: systemd-241-9.gitb67ecf2.fc30 systemd-239-13.gitf4afb95.fc29
Clone Of:
Environment:
Last Closed: 2019-07-23 01:07:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Trevor Cordes 2019-05-12 11:06:50 UTC
Description of problem:
I can't mount a remote cifs share with systemd-mount when the entire mount is specified on the command line (i.e. not in a unit file).  No, I don't want to make unit files, these are transient and always-changing mounts.

Plain mount works fine with the same options.


Version-Release number of selected component (if applicable):
systemd-239-12.git8bca462.fc29.x86_64


How reproducible: always


Steps to Reproduce:
1.
systemd-mount -t cifs -o 'ro,credentials=/home/foo/.creds,uid=foo,file_mode=0644,dir_mode=0755,sec=ntlmv2,vers=2.1' '//192.168.100.102/Fooshare' '/mnt/foo'

Actual results:
Path contains non-normalized components: //192.168.100.102/Fooshare

Expected results:
mount should succeed

Additional info:
This works fine (just changing systemd-mount to mount):
mount -t cifs -o 'ro,credentials=/home/foo/.creds,uid=foo,file_mode=0644,dir_mode=0755,sec=ntlmv2,vers=2.1' '//192.168.100.102/Fooshare' '/mnt/foo'

Yes, I could use mount, but systemd somehow intercepts mount's call and if I botch the creds file even plain old mount will start messing around with password agents and wall messages instead of just silently failing like it used to.  (Argh!)  So I need to use systemd-mount so I can access --no-ask-password.  Either that, or have some way to tell mount not to start messing with password agents.

Obviously specifying the // style cifs path works in unit files, so why doesn't it work at the command line?

Comment 1 Karel Zak 2019-06-10 13:27:20 UTC
I have created upstream pull request with bugfix for this issue:

https://github.com/systemd/systemd/pull/12765

Comment 2 Fedora Update System 2019-07-21 09:21:22 UTC
FEDORA-2019-5feaad3f65 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-5feaad3f65

Comment 3 Fedora Update System 2019-07-22 01:10:25 UTC
systemd-241-9.gitb67ecf2.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-5feaad3f65

Comment 4 Fedora Update System 2019-07-22 09:53:32 UTC
FEDORA-2019-8016b5dca7 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-8016b5dca7

Comment 5 Fedora Update System 2019-07-23 01:07:52 UTC
systemd-241-9.gitb67ecf2.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2019-07-23 01:39:52 UTC
systemd-239-13.gitf4afb95.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-8016b5dca7

Comment 7 Fedora Update System 2019-08-07 01:55:17 UTC
systemd-239-13.gitf4afb95.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.


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