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

Error: Could not parse application options: invalid option: --manifestdir #13

Closed
ms82119 opened this issue Aug 20, 2015 · 6 comments
Closed

Comments

@ms82119
Copy link

ms82119 commented Aug 20, 2015

I tried downloading both v1 and v2 demo's, but when I install the NYC traffic demo i get the error:

Error: Could not parse application options: invalid option: --manifestdir

at the point where puppet is doing the provisioning. Looking around it seems this was deprecated in the 4.x puppet versions. hashicorp/vagrant#3740

Not really clear where to take it from here though. Any help to get the demo working would be appreciated.

@trevor
Copy link

trevor commented Aug 26, 2015

The new config looks something like this:

./Vagrantfile:

  config.vm.provision :puppet, :options => ["--debug --trace --verbose"] do |puppet|
    puppet.environment = "dev"
    puppet.environment_path = [:host, "foo"]
  end

Where you might have files at:

  • ./Vagrantfile
  • ./foo/dev/manifests/site.pp

@ms82119
Copy link
Author

ms82119 commented Aug 27, 2015

Thanks for taking a shot at this. I had been trying a similar approach but setting the envionment_path was something I had missed. Your suggested changes got me up to the point where it now fails with:

Error: Evaluation Error: Error while evaluating a Function Call, Could not find class ::elasticsearch-demo_nyc for localhost.hsd1.nj.comcast.net at /tmp/vagrant-puppet/environments/test/manifests/site.pp:2:1 on node localhost.hsd1.nj.comcast.net

I did some more searching online and found that there may be some question about the correctness of using "-" character in the class name, so i changed it to an underscore "_" in the two directory names:

./modules/elasticsearch-demo_nyc
./modules/elasticsearch-demo_vagrant_env

and in the following files where it is referenced:

./modules/elasticsearch-demo_nyc/manifests/init.pp
./modules/elasticsearch-demo_nyc/metadata.json
./modules/elasticsearch-demo_vagrant_env/manifests/init.pp
./modules/elasticsearch-demo_vagrant_env/metadata.json
./manifests/site.pp

Now it runs much further, but still not quite there yet 😞
I now get down to the point:

==> default: Debug: template[/tmp/vagrant-puppet/environments/test/modules/nginx/templates/vhost/vhost_footer.erb]: Interpolated template /tmp/vagrant-puppet/environments/test/modules/nginx/templates/vhost/vhost_footer.erb in 0.00 seconds
==> default: Error: Evaluation Error: Error while evaluating a Function Call, too short escape sequence: /\/ at /tmp/vagrant-puppet/environments/test/modules/nginx/manifests/resource/location.pp:234:25 on node localhost.hsd1.nj.comcast.net

I'm stuck again at this point, but am wondering if what i did initially with the site.pp file was correct. The demo didn't have this file, so i just renamed the default.pp to be site.pp. It only has one line

include elasticsearch_demo_nyc

I've tried to help myself as best I can, but again am stuck, as always, any help is appreciated.

@peterskim12
Copy link

Sorry I obviously haven't looked at this in a while and it looks like the vagrantbox has been updated to use Puppet 4.2.1. I'll try to get this fixed soon.

@asawariS
Copy link
Contributor

@ms82119 We have updated the existing examples (and added some new ones too). The updates include a simplified workflow to replicate and run the example on your machine. Give it a try and let us know how it goes.

@ms82119
Copy link
Author

ms82119 commented Sep 27, 2015

I see you ditched the vagrant box approach, but these new steps work just fine. Thanks a lot.

@ms82119 ms82119 closed this as completed Sep 27, 2015
@asawariS
Copy link
Contributor

@ms82119 That's awesome!

Yes, we decided to simplify the getting started experience by reducing the need to download and configure additional products during the trial phase. We might bring back something like docker / vagrant alternatives to running the examples if the community request it.

Also, as we mentioned in the ReadMe, comments, suggestions, and feedback are welcome!

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

No branches or pull requests

4 participants