[PUP-8106] "mount" type should autorequire its mountpoint Created: 2017/10/30 Updated: 2019/10/21 Resolved: 2018/02/06
|Component/s:||Types and Providers|
|Affects Version/s:||PUP 5.3.2|
|Reporter:||Johnson Earls||Assignee:||Kris Bosland|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Epic Link:||Mount Type/Provider Improvements|
|Sprint:||Platform Core KANBAN|
|Release Notes:||New Feature|
|Release Notes Summary:||The mount resource now auto requires the file resource that is its mountpoint.|
|QA Risk Assessment:||No Action|
The mount type should autorequire a File resource for its mountpoint.
This will try to mount /usr/local/foo before creating it.
I've got a mountpoint being created in one component and the nfs share being mounted from another component. So my profile has to know the details of the components to know that it has to create the ordering relationship. This should be automatic.
|Comment by Johnson Earls [ 2017/10/30 ]|
I'm attempting a PR for this. Given how little I know about the autorequires stuff, I hope it ends up correct.
|Comment by Johnson Earls [ 2017/10/31 ]|
Submitted PR#6325 for this.
|Comment by Kris Bosland [ 2017/12/18 ]|
|Comment by Melissa Stone [ 2018/02/06 ]|
I've opened https://github.com/puppetlabs/puppet/pull/6607 to revert this change. It seems it reintroduces a bug fixed by https://tickets.puppetlabs.com/browse/PUP-6397 where the auorequire in mount will cause dependency loops.