-
-
Notifications
You must be signed in to change notification settings - Fork 197
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
openvpn facts not generated on server #352
Comments
I did not tested yet, but the patch added can easily break the custom fact because the code does not expect to be in this situation. |
@Dan33l I've been running with a patch to make this module work in CentOS for a year now with no trouble, and only recently did I try and make changes to the user/group configuration and notice that configurations weren't deploying - so I'm not convinced that the patch caused this issue. Seems like we'll need to do some testing when we get a moment!! |
I confirm something is broken, at least with Puppet 5.5.16. On ubuntu1804 SUTs launched during acceptance i confirm i am getting all custom facts empty.
|
It looks something changed and the method used to get fact is deprecated.
|
@jameskirsop can you test |
@Dan33l, when I run
On the OpenVPN server I see similar results to yours above:
|
The code of the fact |
Yeah, right. So I guess the real question then is, why aren't exported resources being detected!! |
FWIW, 10 months later I've rebased my patch on master and I'm now seeing facts generated on the server. However, my issue where clients aren't downloading their configuration remains. |
Hi, seems that problem is on this line: puppet-openvpn/manifests/deploy/export.pp Line 20 in d5e7ad9
with:
It will work with Puppet6 on Ubuntu 18.04. I am going to fork this repo and will see if another problems pop up. If somebody is interested, you can try to merge this in meantime. Thanks |
Deployed a new VPN server today on RHEL 8 using the latest release with no patches. No facts are generated on the server - Update
From my reading of the latest code on We'll need to have a fix for #421 before I'd be happy to consider this issue able to be closed. |
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
Running
$facter openvpn
returns no resultsWhat behaviour did you expect instead
A number of openvpn facts to be returned
Output log
Any additional information you'd like to impart
I discovered this issue well after adding the
group => 'openvpn'
option to the server. I'm not sure if this is related, but I've now tried to deploy a new openvpn client node and discovered that no resources are being exported via https://github.com/voxpupuli/puppet-openvpn/blob/master/manifests/deploy/export.ppThis lead me to investigate what facts were on the openvpn server node and discovered there were none.
Client configuration export was previously working, and the only changes I made from when I last successfully deployed a node to now (I think) was adding the
management
andgroup
options.Removing the
group
option doesn't seem to have remedied the issue (it has restored permissions to default ofnobody
), so I'm a bit confused.Either way, I don't think it's ideal that this change broke the facts.
The text was updated successfully, but these errors were encountered: