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
==> devstack: Forwarding ports...
devstack: 22 => 2222 (adapter 1)
==> devstack: Running 'pre-boot' VM customizations...
==> devstack: Booting VM...
==> devstack: Waiting for machine to boot. This may take a few minutes...
devstack: SSH address: 127.0.0.1:2222
devstack: SSH username: vagrant
devstack: SSH auth method: private key
devstack: Warning: Connection timeout. Retrying...
devstack:
devstack: Vagrant insecure key detected. Vagrant will automatically replace
devstack: this with a newly generated keypair for better security.
devstack:
devstack: Inserting generated public key within guest...
devstack: Removing insecure key from the guest if its present...
devstack: Key inserted! Disconnecting and reconnecting using new SSH key...
==> devstack: Machine booted and ready!
==> devstack: Checking for guest additions in VM...
devstack: The guest additions on this VM do not match the installed version of
devstack: VirtualBox! In most cases this is fine, but in rare cases it can
devstack: prevent things such as shared folders from working properly. If you see
devstack: shared folder errors, please make sure the guest additions within the
devstack: virtual machine match the version of VirtualBox you have installed on
devstack: your host and reload your VM.
devstack:
devstack: Guest Additions Version: 4.2.0
devstack: VirtualBox Version: 4.3
==> devstack: Setting hostname...
==> devstack: Configuring and enabling network interfaces...
==> devstack: Mounting shared folders...
devstack: /vagrant => /Users/liujiang/vagrant-devstack
devstack: /tmp/vagrant-puppet/modules-a547dc537f7ad49e035402b96ec4d1a6 => /Users/liujiang/vagrant-devstack/modules
devstack: /tmp/vagrant-puppet/manifests-a11d1078b1b1f2e3bdea27312f6ba513 => /Users/liujiang/vagrant-devstack/manifests
==> devstack: Running provisioner: puppet...
==> devstack: Running Puppet with site.pp...
==> devstack: stdin: is not a tty
==> devstack: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type vcsrepo at /tmp/vagrant-puppet/manifests-a11d1078b1b1f2e3bdea27312f6ba513/site.pp:43 on node devstack
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:
Looks like the puppet dosen't identify vcsrepo
The text was updated successfully, but these errors were encountered: