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

storage setting in pool.conf should not force -sd suffix #106

Open
jflorian opened this issue Oct 25, 2017 · 7 comments
Open

storage setting in pool.conf should not force -sd suffix #106

jflorian opened this issue Oct 25, 2017 · 7 comments

Comments

@jflorian
Copy link
Contributor

With the upgrade to 5.2 it became necessary for me to the storage parameter when using the bacula::director::pool resource. I set this to the FQDN of my storage host, but the director now won't start because the pool.conf file now has bacula-sd.mydomain.org-sd.

@zachfi
Copy link
Contributor

zachfi commented Oct 25, 2017

This seems like something I missed in the 5.x upgrade. I'll have to look for all instances in the template of -sd etc.

@jflorian
Copy link
Contributor Author

Bah! I made a comment on the PR rather here. I can make this work now by changing what I pass for storage to bacula::director::pool. However, I'd like to unify things so that the name in storage.conf and the storage name in pool.conf come from a single Hiera setting. Since I'm just using a default storage setup, it looks like I'd need to pass the unified value to bacula::storage::storage.

@zachfi
Copy link
Contributor

zachfi commented May 6, 2018

Hi @jflorian. Were you able to work around this issue? Does this still need to be addressed?

@jflorian
Copy link
Contributor Author

jflorian commented May 8, 2018

@xaque208 , I'm still using the same approached described above. It seems it could/should be simpler, but I haven't had time to dig deeper.

@zachfi
Copy link
Contributor

zachfi commented May 8, 2018

If you get a chance to look a little closer @jflorian, just let me know if this can be closed out.

@jflorian
Copy link
Contributor Author

jflorian commented May 8, 2018

It's unlikely to happen by me any time soon. (Blockers (other projects) before annoyances, ya know.) Feel free to close this out if you'd rather not have it clutter things.

@zachfi
Copy link
Contributor

zachfi commented May 8, 2018

Thanks @jflorian. Yeah, not trying to hassle. Mostly realizing there has been a bunch of issues that I've been neglecting. I'll have a review of the code, maybe this weekend and see what needs doing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants