You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run setup/setup.rb and specify the parameters shown in parameters.json
Run "vagrant up"
Expected results:
4. The AEM and Dispatcher instances are up and running on Vagrant/VirtualBox
Actual results:
4. "vagrant up" terminates with 'Could not find declared class..." message. See 'vagrant up' failure.txt or below...
default: Installed:
default: puppet-agent.x86_64 0:1.10.14-1.el7
default: Complete!
default: Successfully installed thor-0.20.3
default: Successfully installed librarianp-0.6.4
default: Successfully installed rsync-1.0.9
default: Successfully installed multipart-post-2.0.0
default: Successfully installed faraday-0.13.1
default: Successfully installed faraday_middleware-0.12.2
default: Successfully installed semantic_puppet-1.0.2
default: The `minitar` executable is no longer bundled with `minitar`. If you are
default: expecting this executable, make sure you also install `minitar-cli`.
default: Successfully installed minitar-0.8
default: Successfully installed locale-2.1.2
default: Successfully installed text-1.3.1
default: Successfully installed gettext-3.2.9
default: Successfully installed fast_gettext-1.1.2
default: Successfully installed gettext-setup-0.30
default: Successfully installed puppet_forge-2.2.9
default: Successfully installed librarian-puppet-3.0.0
default: 15 gems installed
default: Puppet VM Provisioning: Installing puppet modules.
default: Error executing puppet module install. Check that this command succeeds:
default: puppet module install --version 5.2.0 --target-dir /vagrant/puppet/.tmp/librarian/cache/source/puppet/forge/forgeapi_puppetlabs_com/puppetlabs-stdlib/5.2.0 --module_repository https://forgeapi.puppetlabs.com --modulepath /vagrant/puppet/.tmp/librarian/cache/source/puppet/forge/forgeapi_puppetlabs_com/puppetlabs-stdlib/5.2.0 --module_working_dir /vagrant/puppet/.tmp/librarian/cache/source/puppet/forge/forgeapi_puppetlabs_com/puppetlabs-stdlib/5.2.0 --ignore-dependencies puppetlabs-stdlib
default: Error:
default: Error: Operation not permitted @ dir_initialize - /vagrant/puppet/.tmp/librarian/cache/source/puppet/forge/forgeapi_puppetlabs_com/puppetlabs-stdlib/5.2.0/cache/puppetlabs-stdlib20190502-16312-2bhxry/types
default: Error: Try 'puppet help module install' for usage
default: Finished basic VM Provisioning.
==> default: Running provisioner: puppet...
==> default: Running Puppet with environment local...
==> default: Error: Evaluation Error: Error while evaluating a Resource Statement, Could not find declared class apache at /tmp/vagrant-puppet/environments/local/manifests/site.pp:33:1 on node vagrant.aem
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
The text was updated successfully, but these errors were encountered:
To recreate the problem:=
Expected results:
4. The AEM and Dispatcher instances are up and running on Vagrant/VirtualBox
Actual results:
4. "vagrant up" terminates with 'Could not find declared class..." message. See 'vagrant up' failure.txt or below...
==> default: Running provisioner: puppet...
==> default: Running Puppet with environment local...
==> default: Error: Evaluation Error: Error while evaluating a Resource Statement, Could not find declared class apache at /tmp/vagrant-puppet/environments/local/manifests/site.pp:33:1 on node vagrant.aem
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
The text was updated successfully, but these errors were encountered: