Bug 1142396

Summary: Filesystem Options are ignored when Mount Point is empty
Product: [Fedora] Fedora Reporter: Aleš Mareček <amarecek>
Component: cockpitAssignee: Marius Vollmer <mvollmer>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: mvollmer, puiterwijk, stefw
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cockpit-0.26-1.fc21 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-16 02:09:52 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:

Description Aleš Mareček 2014-09-16 17:07:12 UTC
Description of problem:
I set up RAID5 according to https://fedoraproject.org/wiki/QA:Testcase_Cockpit_RAID and tried some magic with Mount Options.
1. I changed Mount Options to "defaults,HelloWorld=1" - When I tried to mount it I got (correct) error message: "Error mounting system-managed device /dev/md127pq:..."
2. I cleared Filesystem Options -> Mount Point and tried mount again - it succeeded in /run/media/<some hash> but without user-defined mount options.
3. I reopened Filesystem Options again and saw that Mount Point is set to "/data". Mount / Unmount didn't changed anything and partition was mounted to /run/media/...
4. Changing of Filesystem Options caused that partition was mounted again to /data properly.
5. I set Mount Options "defaults,users,uid=1001,gid=1001" and mounting of the partition was unsuccessful again.


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


How reproducible:
Always

Steps to Reproduce:
1. Set mount options that are not correct
2. Try to mount the partition
3. Clear mount point and try to mount it again
4. See the mount point in Filesystem Options, do Mount / Unmount


Actual results:
1. pass (no option check - but probably ok)
2. fail (ok)
3. it will mount to some shared place like /run/media but without any user-defined options
4. There is mount point set (what you defined, "/data" in my case) but mount will mount the partition to shared place like /run/media. Only changing the Mount Options (or Mount Point) will "reset" the mount/unmount process and new data will be given to mount.

Expected results:
1. pass
2. fail
3. fail
4. fail (+ clearing of "Mount Point" field)

Additional info:

Comment 1 Marius Vollmer 2014-10-08 08:06:41 UTC
Upstream: https://github.com/cockpit-project/cockpit/issues/1223

This has been addressed in Cockpit 0.26.  Now you can't specify mount options without also specifying a mount point.  This should reduce the confusion about what is going on.

Cockpit will still mount a filesystem in a default location when no mount point has been specified explicitly.  We might make it so that you will be asked for a mount point at the time of mounting.

See https://github.com/cockpit-project/cockpit/issues/1294

Comment 2 Fedora Update System 2014-10-08 08:48:31 UTC
cockpit-0.26-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/cockpit-0.26-1.fc21

Comment 3 Fedora Update System 2014-10-10 15:58:37 UTC
Package cockpit-0.26-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing cockpit-0.26-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-12464/cockpit-0.26-1.fc21
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2014-10-16 02:09:52 UTC
cockpit-0.26-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.