ODL Integration team tools VM debug info dump

vagrant_up_centos.out

[~/integration/test/tools/VM_Tool]$ vagrant up centos
Bringing machine 'centos' up with 'virtualbox' provider...
==> centos: Importing base box 'chef/centos-7.0'...

Progress: 20%
Progress: 50%
Progress: 70%
Progress: 90%
==> centos: Matching MAC address for NAT networking...
==> centos: Checking if box 'chef/centos-7.0' is up to date...
==> centos: Setting the name of the VM: Integration Tools: CentOS-7
==> centos: Fixed port collision for 22 => 2222. Now on port 2200.
==> centos: Clearing any previously set network interfaces...
==> centos: Preparing network interfaces based on configuration...
    centos: Adapter 1: nat
==> centos: Forwarding ports...
    centos: 22 => 2200 (adapter 1)
==> centos: Running 'pre-boot' VM customizations...
==> centos: Booting VM...
==> centos: Waiting for machine to boot. This may take a few minutes...
    centos: SSH address: 127.0.0.1:2200
    centos: SSH username: vagrant
    centos: SSH auth method: private key
    centos: Warning: Connection timeout. Retrying...
    centos: 
    centos: Vagrant insecure key detected. Vagrant will automatically replace
    centos: this with a newly generated keypair for better security.
    centos: 
    centos: Inserting generated public key within guest...
    centos: Removing insecure key from the guest if its present...
    centos: Key inserted! Disconnecting and reconnecting using new SSH key...
==> centos: Machine booted and ready!
==> centos: Checking for guest additions in VM...
==> centos: Setting hostname...
==> centos: Mounting shared folders...
    centos: /vagrant => /home/daniel/integration/test/tools/VM_Tool
    centos: /tmp/vagrant-puppet/modules-022efa1db3d7597938dfad1a3559b188 => /home/daniel/integration/test/tools/VM_Tool/modules
    centos: /tmp/vagrant-puppet/manifests-a11d1078b1b1f2e3bdea27312f6ba513 => /home/daniel/integration/test/tools/VM_Tool/manifests
==> centos: Running provisioner: shell...
    centos: Running: /tmp/vagrant-shell20150325-31221-19sulvo.sh
==> centos: Loaded plugins: fastestmirror
==> centos: Determining fastest mirrors
==> centos:  * base: centos.mirror.constant.com
==> centos:  * extras: mirror.solarvps.com
==> centos:  * updates: mirror.lug.udel.edu
==> centos: Resolving Dependencies
==> centos: --> Running transaction check
==> centos: ---> Package epel-release.noarch 0:7-5 will be installed
==> centos: --> Finished Dependency Resolution
==> centos: 
==> centos: Dependencies Resolved
==> centos: 
==> centos: ================================================================================
==> centos:  Package                Arch             Version         Repository        Size
==> centos: ================================================================================
==> centos: Installing:
==> centos:  epel-release           noarch           7-5             extras            14 k
==> centos: 
==> centos: Transaction Summary
==> centos: ================================================================================
==> centos: Install  1 Package
==> centos: Total download size: 14 k
==> centos: Installed size: 24 k
==> centos: Downloading packages:
==> centos: warning: /var/cache/yum/x86_64/7/extras/packages/epel-release-7-5.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY
==> centos: Public key for epel-release-7-5.noarch.rpm is not installed
==> centos: Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
==> centos: Importing GPG key 0xF4A80EB5:
==> centos:  Userid     : "CentOS-7 Key (CentOS 7 Official Signing Key) <[email protected]>"
==> centos:  Fingerprint: 6341 ab27 53d7 8a78 a7c2 7bb1 24c6 a8a7 f4a8 0eb5
==> centos:  Package    : centos-release-7-0.1406.el7.centos.2.3.x86_64 (@anaconda)
==> centos:  From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
==> centos: Running transaction check
==> centos: Running transaction test
==> centos: Transaction test succeeded
==> centos: Running transaction
==> centos:   Installing : epel-release-7-5.noarch                                      1/1
==> centos:  
==> centos:   Verifying  : epel-release-7-5.noarch                                      1/1
==> centos:  
==> centos: 
==> centos: Installed:
==> centos:   epel-release.noarch 0:7-5                                                     
==> centos: Complete!
==> centos: Loaded plugins: fastestmirror
==> centos: 
==> centos: 
==> centos:  One of the configured repositories failed (Unknown),
==> centos:  and yum doesn't have enough cached data to continue. At this point the only
==> centos:  safe thing yum can do is fail. There are a few ways to work "fix" this:
==> centos: 
==> centos:      1. Contact the upstream for the repository and get them to fix the problem.
==> centos: 
==> centos:      2. Reconfigure the baseurl/etc. for the repository, to point to a working
==> centos:         upstream. This is most often useful if you are using a newer
==> centos:         distribution release than is supported by the repository (and the
==> centos:         packages for the previous distribution release still work).
==> centos: 
==> centos:      3. Disable the repository, so yum won't use it by default. Yum will then
==> centos:         just ignore the repository until you permanently enable it again or use
==> centos:         --enablerepo for temporary usage:
==> centos: 
==> centos:             yum-config-manager --disable <repoid>
==> centos: 
==> centos:      4. Configure the failing repository to be skipped, if it is unavailable.
==> centos:         Note that yum will try to contact the repo. when it runs most commands,
==> centos:         so will have to try and fail each time (and thus. yum will be be much
==> centos:         slower). If it is a very temporary problem though, this is often a nice
==> centos:         compromise:
==> centos: 
==> centos:             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
==> centos: 
==> centos: Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
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.
[~/integration/test/tools/VM_Tool]$ vagrant ssh centos                  19:21:05
Last login: Tue Jul 22 03:42:16 2014 from 10.0.2.2
[vagrant@tools-centos ~]$ which puppet
/usr/bin/which: no puppet in (/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/vagrant/.local/bin:/home/vagrant/bin)
[vagrant@tools-centos ~]$ yum list installed epel-release
Loaded plugins: fastestmirror
base                                                     | 3.6 kB     00:00     


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Disable the repository, so yum won't use it by default. Yum will then
        just ignore the repository until you permanently enable it again or use
        --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>

     4. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
[vagrant@tools-centos ~]$

vagrant_up_ubuntu.out

```
[~/integration/test/tools/VM_Tool]$ vagrant up ubuntu
Bringing machine 'ubuntu' up with 'virtualbox' provider...
==> ubuntu: Box 'ubuntu/trusty64' could not be found. Attempting to find and install...
    ubuntu: Box Provider: virtualbox
    ubuntu: Box Version: >= 0
==> ubuntu: Loading metadata for box 'ubuntu/trusty64'
    ubuntu: URL: https://atlas.hashicorp.com/ubuntu/trusty64
==> ubuntu: Adding box 'ubuntu/trusty64' (v14.04) for provider: virtualbox
    ubuntu: Downloading: https://atlas.hashicorp.com/ubuntu/boxes/trusty64/versions/14.04/providers/virtualbox.box
==> ubuntu: Successfully added box 'ubuntu/trusty64' (v14.04) for 'virtualbox'!
==> ubuntu: Importing base box 'ubuntu/trusty64'...
==> ubuntu: Matching MAC address for NAT networking...
==> ubuntu: Checking if box 'ubuntu/trusty64' is up to date...
==> ubuntu: Setting the name of the VM: Integration Tools: Ubuntu-14.04
==> ubuntu: Clearing any previously set forwarded ports...
==> ubuntu: Fixed port collision for 22 => 2222. Now on port 2200.
==> ubuntu: Clearing any previously set network interfaces...
==> ubuntu: Preparing network interfaces based on configuration...
    ubuntu: Adapter 1: nat
==> ubuntu: Forwarding ports...
    ubuntu: 22 => 2200 (adapter 1)
==> ubuntu: Running 'pre-boot' VM customizations...
==> ubuntu: Booting VM...
==> ubuntu: Waiting for machine to boot. This may take a few minutes...
    ubuntu: SSH address: 127.0.0.1:2200
    ubuntu: SSH username: vagrant
    ubuntu: SSH auth method: private key
    ubuntu: Warning: Connection timeout. Retrying...
    ubuntu: 
    ubuntu: Vagrant insecure key detected. Vagrant will automatically replace
    ubuntu: this with a newly generated keypair for better security.
    ubuntu: 
    ubuntu: Inserting generated public key within guest...
    ubuntu: Removing insecure key from the guest if its present...
    ubuntu: Key inserted! Disconnecting and reconnecting using new SSH key...
==> ubuntu: Machine booted and ready!
==> ubuntu: Checking for guest additions in VM...
==> ubuntu: Setting hostname...
==> ubuntu: Mounting shared folders...
    ubuntu: /vagrant => /home/daniel/integration/test/tools/VM_Tool
==> ubuntu: Running provisioner: shell...
    ubuntu: Running: /tmp/vagrant-shell20150325-27812-az89ye.sh
==> ubuntu: stdin: is not a tty
[~/integration/test/tools/VM_Tool]$ vagrant ssh ubuntu
#snip
vagrant@tools-ubuntu:~$ which git-review
vagrant@tools-ubuntu:~$
```