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

xFileSystemAccessRule: Fails when cluster shared disk is not present on the server #16

Closed
randomnote1 opened this issue Sep 6, 2017 · 1 comment · Fixed by #18
Closed

Comments

@randomnote1
Copy link
Contributor

@randomnote1 randomnote1 commented Sep 6, 2017

When the defined path in xFileSystemAccessRule resides on a cluster drive and the node where the configuration is applied does not own the drive, the configuration fails.

I would like to propose to make the xFileSystemAccessRule resource cluster aware. I think the logic could look something like this:

  • If the path does not exist
    • If the server is a member of a cluster
      • If the cluster node does not own the drive specified in the path
        • Exit silently
@randomnote1
Copy link
Contributor Author

@randomnote1 randomnote1 commented Oct 31, 2017

If there are no objections, I'm going to work on a fix for this. I'm going to use the same basic template that I'm using in xSQLServer and outlined in this gist.

@johlju johlju closed this in #18 May 18, 2018
johlju added a commit that referenced this issue May 18, 2018
- Changes to xFileSystemAccessRule
  - Fixed issue when cluster shared disk is not present on the server (issue #16).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

2 participants