Revision history [back]

Solution which worked for me:"changing the root project directory"

First i was working by creating a root project directory named Vagrant_project in which all my puppet manifests and Vagrantfile for the project were present.When there occurred the above listed ruby gem error,i removed Vagrant_project directory and created a new project directory.This role i repeated. Also an instance(VM) on the OpenStack was actively up & running by previous root project directory,i terminated that instance before launching the next instance with new project directory.