Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Forced unmount because devices don't match" every run for curlftpfs #53561

Open
uhriap opened this issue Jun 21, 2019 · 2 comments
Open

"Forced unmount because devices don't match" every run for curlftpfs #53561

uhriap opened this issue Jun 21, 2019 · 2 comments
Labels
Bug broken, incorrect, or confusing behavior Confirmed Salt engineer has confirmed bug/feature - often including a MCVE Linux severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around
Milestone

Comments

@uhriap
Copy link

uhriap commented Jun 21, 2019

Description of Issue

mount.mounted state always force remount for curlftpfs mount with Forced unmount because devices don't match.
I believe this

# then we remove the prefaced string so that the device in state matches
assumptions is false and mount.active actually returns string with curlftpfs#

Workaround device_name_regex: ftp://xxx:xxx@example.com/ helps

[INFO    ] {u'mount': True, u'umount': u"Forced unmount because devices don't match. Wanted: curlftpfs#ftp://xxx:xxx@example.com/ (ftp://xxx:xxx@example.com/), current: curlftpfs#ftp://xxx:xxx@example.com/, /root/curlftpfs#ftp:/xxx:xxx@example.com"}

Setup

# cat test.sls
curlftpfs:
  pkg:
    - installed

curlftpfs mount xxx:
  mount.mounted:
    - name: /opt/xxx
    - device: curlftpfs#ftp://xxx:xxx@example.com/
    - fstype: fuse
    - mount: True
    - mkmnt: True
    - persist: False
    - require:
      - pkg: curlftpfs

Versions Report

(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)

# salt-call --versions-report
Salt Version:
           Salt: 2018.3.0

Dependency Versions:
           cffi: Not Installed
       cherrypy: Not Installed
       dateutil: 2.4.2
      docker-py: Not Installed
          gitdb: Not Installed
      gitpython: Not Installed
          ioflo: Not Installed
         Jinja2: 2.8
        libgit2: Not Installed
        libnacl: Not Installed
       M2Crypto: Not Installed
           Mako: Not Installed
   msgpack-pure: Not Installed
 msgpack-python: 0.4.6
   mysql-python: Not Installed
      pycparser: Not Installed
       pycrypto: 2.6.1
   pycryptodome: Not Installed
         pygit2: Not Installed
         Python: 2.7.12 (default, Dec  4 2017, 14:50:18)
   python-gnupg: Not Installed
         PyYAML: 3.11
          PyZMQ: 15.2.0
           RAET: Not Installed
          smmap: Not Installed
        timelib: Not Installed
        Tornado: 4.3
            ZMQ: 4.1.4

System Versions:
           dist: Ubuntu 16.04 xenial
         locale: UTF-8
        machine: x86_64
        release: 4.4.88-42
         system: Linux
        version: Ubuntu 16.04 xenial
@Akm0d Akm0d added Bug broken, incorrect, or confusing behavior Linux P4 Priority 4 labels Jul 2, 2019
@Akm0d Akm0d added this to the Approved milestone Jul 2, 2019
@stale
Copy link

stale bot commented Jan 8, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

@stale stale bot added the stale label Jan 8, 2020
@waynew waynew added the Confirmed Salt engineer has confirmed bug/feature - often including a MCVE label Jan 8, 2020
@stale
Copy link

stale bot commented Jan 8, 2020

Thank you for updating this issue. It is no longer marked as stale.

@stale stale bot removed the stale label Jan 8, 2020
@sagetherage sagetherage removed the P4 Priority 4 label Jun 3, 2020
@sagetherage sagetherage added severity-high 2nd top severity, seen by most users, causes major problems severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around and removed severity-high 2nd top severity, seen by most users, causes major problems labels Jun 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior Confirmed Salt engineer has confirmed bug/feature - often including a MCVE Linux severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around
Projects
None yet
Development

No branches or pull requests

4 participants