-
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
Raise logging of files used to create answer input to UI level #137
Comments
The If you run Vagrant with logging raised to INFO:
Somewhere in the epic amount of logs that spew out there should be a line starting with For example using: $ tree
.
├── Vagrantfile
└── provision
└── pe.conf
$ cat Vagrantfile
# chdir ensures all relative paths expand relative to the Vagrantfile
# when the vagrant command is run from a subdirectory.
Dir.chdir(File.dirname(__FILE__))
Vagrant.configure('2') do |config|
config.vm.define(:master) do |master|
master.vm.hostname = 'master.testnet'
master.vm.box = 'puppetlabs/centos-7.0-64-nocm'
master.vm.provision(:pe_bootstrap) do |provisioner|
provisioner.version = '2017.2.1'
provisioner.role = :master
provisioner.answer_file = 'provision/pe.conf'
end
end
end I get:
If the default template is used, you should see a message like:
Let me know what you see when the provisioner runs. If nothing else, we should move this info up to the top-level logger so that it isn't buried down in the Vagrant log noise. |
I see the following regarding where it's getting its own pe.conf: ==> master: 2017-05-11 17:47:48,661 Running command: cp /vagrant/.pe_build/answers/master.txt /etc/puppetlabs/enterprise/conf.d/pe.conf Is this the output you were looking for? (trying to NOT copy in a crazy amount of output) |
Nope. The |
Sorry.. I'm an idiot. Ok, here's what appears to be pertinent. (you're right... this is huge) INFO answers_file: Using explicit answers file template provision/pe.conf for #<Vagrant::Machine: master (VagrantPlugins::ProviderVirtualBox::Provider)> That's what appears to be the pertinent lines. I'll attach a file of the log if you're interested. |
Looks like your configured
From the error message,
You can view the answer content that was generated by running the following from the directory containing the
|
Well, this is awesome-peachy. There is a new pe.conf that comes with the new PE. It doesn't have that setting in it at all. This is curious to say the least. Let me put that value in and then have a look. I'll update here. |
got considerably further, but added errors... still suggesting something about the answers file: /vagrant/.pe_build/puppet-enterprise-2017.2.1-el-7-x86_64/puppet-enterprise-installer -c /vagrant/.pe_build/answers/master.txt Stdout from the command: /vagrant/.pe_build/puppet-enterprise-2017.2.1-el-7-x86_64 /home/vagrant I'll pick up in the morning. |
You know what? This is likely a PE lack of full documentation on the pe.conf. I'll close this since it isn't this project's problem. Thanks so much, @Sharpie . You're a rockstar! |
Aww, thanks! For https://docs.puppet.com/pe/2017.2/install_pe_conf_param.html I'm going to re-open this just so there's a TODO hanging around for improving the logging around which input file gets used to create the answer file passed to the installer. Having that buried down in the INFO firehose isn't very useful. |
I have a project I've maintained for quite some time. I generally increment the version number, the provisioner reads the custom pe.conf and builds the appropriate machine as requested.
Today, with the release of 2017.2.1, this functionality has broken.
vagrant-pe_build (0.17.4)
Vagrantfile provisioner code:
master.vm.provision :pe_bootstrap do |provisioner|
provisioner.role = :master
provisioner.answer_file = 'provision/pe.conf'
end
master.vm.provision :shell, path: "provision/master.sh"
end
a "vagrant up" causes the provisioner to fire, but it never calls the pe.conf.
Immediately following the successful RPM installation of
pe-installer
pe-modules
puppet-agent
it goes straight to evaluating it's own master.txt rather than my specified pe.conf. I also tried moving the pe.conf out of the "provision" subdirectory to no success.
Log output:
==> master: ## We're checking if /vagrant/.pe_build/answers/master.txt contains valid HOCON syntax...
==> master:
==> master:
==> master: ## We're configuring PE using /vagrant/.pe_build/answers/master.txt.
The text was updated successfully, but these errors were encountered: