-
Notifications
You must be signed in to change notification settings - Fork 31
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
Certificate not removed from puppet master when destroying machine #140
Comments
If the https://github.com/oscar-stack/vagrant-pe_build#pe_agent-provisioner-settings |
the master_vm is configured and during the provision the node is correclty added and autosigned. the problem is during the destroy... the node is not removed because the plugin try to use the hostname but the agent is registered with the fqdn so puppet cannot do the purge ==> pmaster.q8inttest.com: No certificate for win2012r2pmd15 on pmaster.q8inttest.com. |
Ah, this is the issue:
The cleanup action tried to purge a node named
Puppet defaults to using the output of The cleanup routine for
In this case, |
Yes vm.hostname is set and it's just the hotsname. machine.name is correct (it's the fqdn).
I'm not a vagrant expert, it seems something that could be solved by the #106 is this correct? Any idea if and when it will be merged/published as new version? Do you think i can not set config.vm.hostname or this will cause other problems? |
If At the moment I'm focused on getting existing functionality tested out against Vagrant 2.x, so I likely won't be looking to build anything new for the next .z release. Managing |
Tomorrow I’ll do some checks trying to nit define hostname in the vagrantfile, I’ll let you know how it goes. If you need to test anything particular let me know if I can help. the #106 would be nice when released :) |
Done some checks. I've removed the config.vm.hostname from the Vagrantfile...
|
The unprovision task try to remove the machine from puppet using the vmname but if the server is joined to a domain or have a domain configured this task fail because the host is registered with fqdn. Trying to redeploy a machine will result in a failure.
Not sure if this is related or can be solved by #106
This is the destroy log and the machine is not purged because it search for hostname and not fqdn
This is the cert list on puppet server, machine are configured with fqdn.
The text was updated successfully, but these errors were encountered: