oar-team / oar-vagrant

Using Vagrant to test OAR's different flavors of installation
http://oar.imag.fr/dokuwiki/doku.php?id=wiki:oar-vagrant
GNU General Public License v2.0
1 stars 0 forks source link

create oar-team/centos7 vagrant image #2

Closed npf closed 9 years ago

npf commented 9 years ago

I upgraded kameleon to 2.6.0 and imported the centos7 template in oar-vagrant/kameleon. This creates the default subdirectory. How should it be merge with the existing templates ?

npf commented 9 years ago

Thanks for merging and creating oar-team/centos7 version 1.0.0.

There is a issue with the box vmid: For centos6, box.ovf has: VirtualSystem ovf:id="centos6_a7b9a5b5e668" While for centos7, it has: VirtualSystem ovf:id="2015-06-12-12-52-06_Z6m_default_1434111423796_79898"

There seems to be a bug in default/virtualbox/centos7.yaml, with: virtualbox_vmid: $${kameleon_recipename}$${kameleon_short_uuid} (not actually inherited from default/virtualbox/centos6.yaml ?)

npf commented 9 years ago

I've got errors with vagrant setup of the network interfaces. It does not fail everything though... (server was ok, below)

==> server: + touch /tmp/stamp.create_oar_resources ==> server: ## ==> server: ## start oar-server ==> server: ## ==> server: + service oar-server start ==> server: Starting OAR server: ==> server: [ OK ] ==> server: + touch /tmp/stamp.start_oar-server ==> frontend: Importing base box 'oar-team/centos7'... ==> frontend: Matching MAC address for NAT networking... ==> frontend: Checking if box 'oar-team/centos7' is up to date... ==> frontend: Setting the name of the VM: rpm_centos7_pgsql_frontend_1434121641991_80900 ==> frontend: Fixed port collision for 22 => 2222. Now on port 2200. ==> frontend: Clearing any previously set network interfaces... ==> frontend: Preparing network interfaces based on configuration... frontend: Adapter 1: nat frontend: Adapter 2: hostonly ==> frontend: Forwarding ports... frontend: 22 => 2200 (adapter 1) ==> frontend: Running 'pre-boot' VM customizations... ==> frontend: Booting VM... ==> frontend: Waiting for machine to boot. This may take a few minutes... frontend: SSH address: 127.0.0.1:2200 frontend: SSH username: vagrant frontend: SSH auth method: private key frontend: Warning: Connection timeout. Retrying... frontend: frontend: Vagrant insecure key detected. Vagrant will automatically replace frontend: this with a newly generated keypair for better security. frontend: frontend: Inserting generated public key within guest... frontend: Removing insecure key from the guest if its present... frontend: Key inserted! Disconnecting and reconnecting using new SSH key... ==> frontend: Machine booted and ready! ==> frontend: Checking for guest additions in VM... ==> frontend: Setting hostname... ==> frontend: Configuring and enabling network interfaces... The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!

cat /tmp/vagrant-ifcfg- > /etc/sysconfig/network-scripts/ifcfg-

Stdout from the command:

Stderr from the command:

cat: /tmp/vagrant-ifcfg-: No such file or directory

npf commented 9 years ago

More info: vagrant version -> 1.7.2 misc/env.sh not loaded Seems to work ok with rpm_centos6_pgsql.

npf commented 9 years ago

fixed in 1.0.1