search

ansible / workshops

Training Course for Ansible Automation Platform
MIT License
1.75k stars 1.14k forks source link

vagrant up fails to provision leaf and spine servers #168

Closed ffirg closed 5 years ago

ffirg commented 5 years ago
SUMMARY

$ vagrant up spine01 Bringing machine 'spine01' up with 'virtualbox' provider... ==> spine01: Importing base box 'samdoran/vyos'... ==> spine01: Matching MAC address for NAT networking... ==> spine01: Checking if box 'samdoran/vyos' is up to date... ==> spine01: Setting the name of the VM: 1_spine01 ==> spine01: Fixed port collision for 22 => 2222. Now on port 2201. ==> spine01: Clearing any previously set network interfaces... ==> spine01: Preparing network interfaces based on configuration... spine01: Adapter 1: nat spine01: Adapter 2: intnet spine01: Adapter 3: intnet spine01: Adapter 4: intnet spine01: Adapter 5: intnet spine01: Adapter 6: intnet ==> spine01: Forwarding ports... spine01: 22 (guest) => 6003 (host) (adapter 1) spine01: 22 (guest) => 2201 (host) (adapter 1) ==> spine01: Running 'pre-boot' VM customizations... ==> spine01: Booting VM... ==> spine01: Waiting for machine to boot. This may take a few minutes... spine01: SSH address: 127.0.0.1:2201 spine01: SSH username: vagrant spine01: SSH auth method: private key spine01: spine01: Vagrant insecure key detected. Vagrant will automatically replace spine01: this with a newly generated keypair for better security. spine01: spine01: Inserting generated public key within guest... spine01: Removing insecure key from the guest if it's present... spine01: Key inserted! Disconnecting and reconnecting using new SSH key... ==> spine01: Machine booted and ready! [spine01] GuestAdditions versions on your host (5.2.26) and guest (5.2.12) do not match. Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package linux-headers-3.13.11-1-amd64-vyos E: Couldn't find any package by regex 'linux-headers-3.13.11-1-amd64-vyos' Get:1 http://archive.debian.org squeeze Release.gpg [1655 B] Ign http://archive.debian.org/debian/ squeeze/contrib Translation-en Ign http://archive.debian.org/debian/ squeeze/main Translation-en Ign http://archive.debian.org/debian/ squeeze/non-free Translation-en Hit http://archive.debian.org squeeze-lts Release.gpg Ign http://archive.debian.org/debian/ squeeze-lts/contrib Translation-en Ign http://archive.debian.org/debian/ squeeze-lts/main Translation-en Ign http://archive.debian.org/debian/ squeeze-lts/non-free Translation-en Get:2 http://archive.debian.org squeeze Release [96.0 kB] Hit http://archive.debian.org squeeze-lts Release Ign http://archive.debian.org squeeze Release W: GPG error: http://archive.debian.org squeeze Release: The following signatures were invalid: KEYEXPIRED 1520281423 KEYEXPIRED 1501892461 E: Release file expired, ignoring http://archive.debian.org/debian/dists/squeeze-lts/Release (invalid since 1051d 8h 27min 31s) Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package linux-headers-3.13.11-1-amd64-vyos E: Couldn't find any package by regex 'linux-headers-3.13.11-1-amd64-vyos' /etc/bash.bash_logout: line 1: /vyatta-monitor-cleanup: No such file or directory ==> spine01: Checking for guest additions in VM... The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!

apt-get install -y linux-headers-uname -r dkms

Stdout from the command:

Reading package lists... Building dependency tree... Reading state information...

Stderr from the command:

E: Unable to locate package linux-headers-3.13.11-1-amd64-vyos E: Couldn't find any package by regex 'linux-headers-3.13.11-1-amd64-vyos'

ISSUE TYPE
OS / ENVIRONMENT

MacOS Mojave 10.14.2 Vagrant 2.2.2 Virtualbox 5.2.26 r128414

abenokraitis commented 5 years ago

I don't think linklight is supported as local install with out of band images...

ffirg commented 5 years ago

I thought it was - https://github.com/network-automation/linklight/tree/master/vagrant-demo ? The errors are related to the vagrant vyos image update. I think if that's sorted then it should still work ok?

abenokraitis commented 5 years ago

I believe this was just a POC or demo if it could be done locally but never got any community traction. Given the primary delivery method is now AWS with a robust provisioner it seems like that's where the efforts are being made to date. This could be a valid issue but not sure this is being used all that much (given last updated)...

IPvSean commented 5 years ago

@ffirg does it have to be VyOS? Have you tried the vagrant workshop for Arista. I have done that more recently and it has better directions and support... in here-> https://github.com/network-automation/linklight/tree/master/vagrant-demo/arista

ffirg commented 5 years ago

Thanks Sean. No doesn't have to be VyOS. I was just trying to use what was there. I'm using RHPDS now and linklight for demos which is cracking (great work BTW)