Bug 1394271

Summary: Unable to auto mount per fstab due to gnome-keyring-daemon removing removable location
Product: Red Hat Enterprise Linux 6 Reporter: jigar <jraising>
Component: gnome-keyringAssignee: David King <dking>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.7CC: ayadav, cww, dking, mclasen
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-13 17:52:39 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:

Description jigar 2016-11-11 14:26:08 UTC 
Description of problem: 

There is a setup where a RHEL server constantly mounts a network drive (CIFS) provided by a window server share. The /etc/fstab is well registered on this FS mount so the server is able to auto mount the network drive upon server reboot. Issue happened at 2 locations, when sites experienced power outage. When server got back online; it no longer was able to auto mount the network share, and from the /var/log/message. We clearly see the issue was due to this "gnome-keyring-daemon" removing removable location which is this mount point:

Sep 20 10:17:27 pmmmptasp1 gnome-keyring-daemon[8439]: removing removable location: /media/aspera_cache
Sep 20 10:17:27 pmmmptasp1 gnome-keyring-daemon[8439]: no volume registered at: /media/aspera_cache

Share is mounted manually without any issues.



Version-Release number of selected component (if applicable): gnome-keyring-2.28.2-8.el6_3


How reproducible: After power outage


Actual results: gnome-keyring is removing removable locations and preventing automounting of network shares


Expected results: gnome-keyring shouldn't prevent automounting of network shares
Comment 4 Chris Williams 2017-06-13 17:52:39 UTC 
Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017.  During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
 
The official life cycle policy can be reviewed here:
 
http://redhat.com/rhel/lifecycle
 
This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification.  Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
 
https://access.redhat.com