Vagrant, puppet and virtual box - vagrant

Getting this error when I run the command - vagrant up
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list emacs' returned 1:
Error: Cannot retrieve repository metadata (repomd.xml) for
repository: nodesource. Please verify its path and try again

Although some details around OS etc. would have helped but the error seems to be coming when trying to do an "yum update". Similar error has been answered here. So technically it is not even a Puppet error. If you need a basic sandbox for trying puppet using Vagrant then you can use the repo here

Related

gcloud crashed (NotADirectoryError): (Errno 20) Not a directory: 'xdg-settings' appeared after type: gcloud init

I got problem with command line: "gcloud init" after installed successfully the google cloud SDK in local machine. The error appeared as below:
cloud init
Welcome! This command will take you through the configuration of gcloud.
Your current configuration has been set to: [default]
You can skip diagnostics next time by using the following flag:
gcloud init --skip-diagnostics
Network diagnostic detects and fixes local network connection issues.
Checking network connection...done.
Reachability Check passed.
Network diagnostic passed (1/1 checks passed).
You must log in to continue. Would you like to log in (Y/n)? Y
ERROR: gcloud crashed (NotADirectoryError): [Errno 20] Not a directory: 'xdg-settings'
If you would like to report this issue, please run the following command:
gcloud feedback
To check gcloud for common problems, please run the following command:
gcloud info --run-diagnostics "
I tried to fix by using this link but it did not work in my environment. Please let me know if you have any idea and want me to provide anything, feel free to ask me.
Best Regards,
PNV
I solved it by doing the steps here:
brew install libxslt xmlto
export XML_CATALOG_FILES="/usr/local/etc/xml/catalog"
git clone git://anongit.freedesktop.org/xdg/xdg-utils
cd xdg-utils
./configure --prefix=/usr/local
make
make install
Note that I also had to install lynx using brew install lynx cause I was getting this issue:
Note: Writing xdg-settings.1
/usr/local/bin/xmlto txt desc/xdg-desktop-menu.xml
No way to convert HTML to text found.
Try either installing text web browser(lynx/w3m/links) or use option --with-fop
make[1]: *** [xdg-desktop-menu.txt] Error 1
make: *** [scripts] Error 2

Bundler error whilst trying to install Varying Vagrant Vagrants and Vagrant plug-ins

I am new to Vagrant, Laraval, and Varying Vagrant Vagrants. I am attempting to get this environment installed and operational. I am on Mac OS X 10.11.6.
I am following the instructions posted here.
Step 1 is install VirtualBox 5.0.x. Done that.
Step 2 is install Vagrant 1.8.5. Done that.
After installing Vagrant with the pgk file I downloaded... I created a directory at ~/vagrant. In that directory I did a vagrant init hashicorp/precise64 command. I then vagrant up.
Step 3 Install the vagrant-hostsupdater plugin with vagrant plugin install vagrant-hostsupdater
When I try to do this, I get the following error:
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:
There was an error while trying to write to
/Users/jonathan/.bundle/cache/compact_index/gems.hashicorp.com.443.68db9b3ad4be8461ccdecca2ae96d12a.
It is likely that you need to grant write permissions for that path.
Warning: this Gemfile contains multiple primary sources. Using
source more than once without a block is a security risk, and may
result in installing unexpected gems. To resolve this warning, use a
block to indicate which gems should come from the secondary source. To
upgrade this warning to an error, run bundle config
disable_multisource true.
Just to see if it made any difference, I changed the permissions on that file to 777. The same error occurs though.
I also get this error if I try to install any of the other plugins mentioned in the instructions on the VVV site.
I have no idea why this occurs, or what to do about it.
Any suggestions would be greatly appreciated.
Whilst I don't know the original cause of the issue, the came to light through my discussion (in comments) with Frédéric Henri.
For some reason the permissions on the ~/.bundle file had the owner set to root.
This was preventing the Vagrant plug-ins from installing. To correct this issue I changed the owner to my username.
From the home folder (cd ~/) use the following command, sudo chown -R <USERNAME>:staff ~/.bundle
This resolved the issue.

Vagrant -- E: Couldn't determine free space

Yesterday my vagrant box was working fine. Now it's not. When I try to provision my box again, or run this command (or any apt-get):
sudo /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install postgresql
I get this error:
E: Couldn't determine free space in /var/cache/apt/archives/ - statvfs (20: Not a directory)
I've:
done a destroy, and I still get this error.
removed all but a couple packages from my provisioner I still get this error.
created a new vagrant file, using the same box, and I do NOT get this error.
cloned my vagrant file into a new folder, and I still get this error.
What is going on here?
UPDATE: It looks like there is a lock file in /var/cache/apt/archives/
I was using the vagrant-cachier pluggin, and it had cached a bad apt-get request that put in a lock. When I disabled this pluggin and rebuild the machine there were no issues.

Vagrant Provision AWS Issue

I am following the Rails App Cookbook and am facing issue with step 6 which involves provisioning an AWS instance. I received the following errors as output.
As explained in the guide, upon observing the provisioning failure, I executed vagrant up --provider=aws and received the following errors.
Here are the outputs of the dependency file, kernel gem file and the berks file where the errors are observed.
Upon inspecting the errors and the berks file, I tried modifying line 11 to version = "3.2.0", but that didn't make any difference as I can see the same errors.
Here is the output of the Vagrantfile.
I investigated further and found the following issue being reported Berkshelf Github page. I tried the solution suggested - ensure that the Chef-DK directories are at the front of my $PATH by applying the following command $ PATH=$HOME/.chefdk/gem/ruby/2.1.0/bin:/opt/chefdk/bin:$PATH
I observed the following output at my system.
Could someone please suggest what could be the problem?
I found the solution to the problem. I was using the vagrant-berkshelf plugin. The correct plugin to be used is berkshelf alone. The issue was rectified after running the following commands:
vagrant plugin uninstall vagrant-berkshelf
vagrant plugin install berkshelf

command 'vagrant box add' fail

vagrantup.com says input vagrant box add hashicorp/precise32, But when I input it, the terminal outputs error message:
This command was not invoked properly. The help for this command is
available below.
Usage: vagrant box add <name> <url> [--provider provider] [-h]
Then, I input vagrant box add hashicorp/precise32 \ http://files.vagrantup.com/hashicorp/precise32.box,
But the download fail, with following error message.
Download failed. Will try another box URL if there is one.
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
Couldn't open file /Users/XXXX/ http:/files.vagrantup.com/precise32.box
How do I do to install vagrant box?
The syntax for the vagrant box add subcommand is changed with the version 1.5, due to the Vagrant Cloud introduction.
From the output messages it seems that you're using an older version, so current documentation is not reliable for your case.
Here you can find a snapshot of the old documentation, in any case the syntax you need to use is like the following:
vagrant box add precise32 http://files.vagrantup.com/precise32.box

Resources