-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
States mount.* fail on OpenBSD's tmpfs #34012
Comments
@viq I am able to verify this behavior that it is working in 2015.8.10 but broken 2016.3.0. My git bisect is showing:
Which doesn't seem right but I did that git bisect multiple times. |
I believe this should fix it: |
mount(8) output is a little bit different on OpenBSD between local and special or remote filesystems (e.g. tmpfs or nfs). These do not use a UUID nor a device. #34012
When executing
and result of
but it works. |
That's an unrelated issue. I'll have a look at fixing it on the OpenBSD side. |
Thank you @ajacoutot :) |
@viq ok so I looked at modifying mount(8) -v output on OpenBSD but there's just too much discrepancy. |
I had to add a bit more to
So now it's just to get this backported to 2016.3. |
@viq yes, I was just providing an example; if you are using more opts, then you will end up hiding a few more. |
mount(8) output is a little bit different on OpenBSD between local and special or remote filesystems (e.g. tmpfs or nfs). These do not use a UUID nor a device. saltstack#34012
@viq I have backported this fix to 2016.3 in #34133. Thank you for testing and confirming. @ajacoutot Thanks again for the fix and for following up on this issue. |
States mount.* fail to take into consideration
mount
output on OpenBSDSetup
Latest OpenBSD snapshot (doesn't matter, should behave the same on any). Following state:
Which results in following
fstab
entry:and following
mount -v
output:Steps to Reproduce Issue
Versions Report
Currently the master is:
but I've demonstrated above this happens as well with --local.
Interestingly enough, it works on
The text was updated successfully, but these errors were encountered: