Skip to content

leap local doesn't always map to the actual vagrant box

I got irritated that our platform builds were much faster in the last days/weeks, and looking into the deploy logs reveal that they don't need to actually install packages, i.e. https://0xacab.org/varac/platform/builds/1741

I logged into greyhound, went to the provider dir that was used for the build, and logged into the 'singlebuild1741' VM.

gitlab-runner@greyhound:~/builds/e6c33500/0/varac/platform/tests/platform-ci/provider$ bundle exec leap list

              SERVICES  NODES                       
               couchdb  catalogtest, singlebuild1741
               monitor  catalogtest, singlebuild1741
                    mx  catalogtest, singlebuild1741
             obfsproxy  catalogtest, singlebuild1741
               openvpn  catalogtest, singlebuild1741
               soledad  catalogtest, singlebuild1741
                static  catalogtest                 
                   tor  catalogtest, singlebuild1741
                webapp  catalogtest, singlebuild1741

                  TAGS  NODES          
             build1741  singlebuild1741
           catalogtest  catalogtest    
           development  catalogtest    
                 local  singlebuild1741

                 NODES  SERVICES                                                                TAGS                    
           catalogtest  couchdb, monitor, mx, obfsproxy, openvpn, soledad, static, tor, webapp  catalogtest, development
       singlebuild1741  couchdb, monitor, mx, obfsproxy, openvpn, soledad, tor, webapp          build1741, local        

gitlab-runner@greyhound:~/builds/e6c33500/0/varac/platform/tests/platform-ci/provider$ bundle exec leap ssh singlebuild1741
Warning: Permanently added '10.5.5.101' (ECDSA) to the list of known hosts.
Development Environment
Last login: Mon Sep  5 12:01:17 2016 from 10.5.5.1
root@singlebuild1755:~#

Wait what, the VM is called 'singlebuild1741' but the hostname is 'singlebuild1755' ? Looks like the same machine gets re-used multiple times, possibly explaining why no packages need to get installed.

Using vagrant I end up on a different node:



gitlab-runner@greyhound:~/builds/e6c33500/0/varac/platform/tests/platform-ci/provider$ cd test/
gitlab-runner@greyhound:~/builds/e6c33500/0/varac/platform/tests/platform-ci/provider/test$ vagrant status
Current machine states:

singlebuild1741           running (libvirt)

The Libvirt domain is running. To stop this machine, you can run
`vagrant halt`. To destroy the machine, you can run `vagrant destroy`.
gitlab-runner@greyhound:~/builds/e6c33500/0/varac/platform/tests/platform-ci/provider/test$ vagrant ssh singlebuild1741
hostname -fDevelopment Environmenthostname -f
Last login: Mon Sep  5 12:05:18 2016 from 192.168.121.1
vagrant@leap-jessie:~$ hostname -f
leap-jessie.local
vagrant@leap-jessie:~$

(from redmine: created on 2016-09-05)