Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to provision a fedora-19 machine with private-network #196

Closed
outofjungle opened this issue Mar 21, 2014 · 1 comment
Closed

Unable to provision a fedora-19 machine with private-network #196

outofjungle opened this issue Mar 21, 2014 · 1 comment

Comments

@outofjungle
Copy link

I'm using test-kitchen to bring up a fedora-19 node. My .kitchen.yml looks like this

---
driver:
  name: vagrant

provisioner:
  name: chef_solo

platforms:
  - name: fedora
    driver_config:
      require_chef_omnibus: true
      box: fedora-19
      box_url: http://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_fedora-19_chef-provisionerless.box
      customize:
        memory: 20484
        cpus: 2

suites:
  - name: default
    driver_config:
      network:
        - ["private_network", {ip: "33.33.33.10"}]
    run_list:
      - recipe[openshift::default]
    attributes:

and i get this error:

>>>>>> ------Exception-------                                                                                                           [6/993]
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: Failed to complete #create action: [Expected process to exit with [0], but received '1'
---- Begin output of vagrant up --no-provision --provider=virtualbox ----
STDOUT: Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'fedora-19'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: default-fedora_default_1395436395353_5309
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Error: Connection timout. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
STDERR: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

/sbin/ifup p7p1 2> /dev/null

Stdout from the command:

ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device p7p1 does not seem to be present, delaying initialization.


Stderr from the command:
---- End output of vagrant up --no-provision --provider=virtualbox ----
Ran vagrant up --no-provision --provider=virtualbox returned 1]
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration

If i remove this block from the .kitchen.yml

    driver_config:
      network:
        - ["private_network", {ip: "33.33.33.10"}]

everything works fine.

@juliandunn
Copy link
Contributor

Sounds like this Vagrant bug: hashicorp/vagrant#1997

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants