-
Notifications
You must be signed in to change notification settings - Fork 15
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
Move to chef/fedora-21 Beaker node #15
Comments
This Beaker nodespec config file:
Run with
With this output/failure:
Copied into a fresh dir and
Editing the Vagrantfile to remove the network config line fixes things:
|
The F21 Vagrant box (without the network line, to make it work) shows this networking info:
Note that the ether interface is called
|
I had a same issue with a CentOS 7 box, updating Vagrant it self fixed the issue for me. |
Thanks for the data point! I upgraded from 1.6.5 to 1.7.2. Unfortunately, I'm seeing the same issue.
Again, remove the network-related line (created by Beaker) lets the box work:
It looks like I need to figure out why Beaker is adding that network-related line, and potentially prevent it from doing so. Alternatively/additionally, need to check why Vagrant is using eth1 instead of an actual interface. |
That's weird because i use beaker as well and worked fine when booting up my CentOS 7 box.. must admit i haven't tried F21. |
Yeah, CentOS 7 is working fine (also using Beaker). Also strange, the TFDuesing/Fedora-21 box doesn't show this issue. |
Note that |
Going to re-visit this as an attempt at fixing #63. |
This is blocked. We can't get feedback about the success/failure of base-box change until #63 is unblocked and the F21 tests work. |
I've update all the Vagrant boxes in the last few commits. This is now irrelevant. |
I'm currently using a very un-official F21 Vagrant box for my F21 Beaker node. Eventually it'd be much better to move to an official-ish one, like
chef/fedora-21
. There are complicating factors, like the Chef box not being on Vagrantcloud yet. See details on #10.The text was updated successfully, but these errors were encountered: