Re: [vagrant-up] Private IP Assigned to Wrong NIC

2018-03-08 Thread Jamie Jackson 
I've copied the contents to https://github.com/hashicorp/vagrant/issues/9546,
so go ahead and delete my comments. I'll try to get a repro case together.

On Thu, Mar 8, 2018 at 1:03 PM, Alvaro Miranda Aguilera 
wrote:

> not sure if the same
>
> please open a new issue, include a repro case and instructions how to repro
>
> please @kikitux so i can get the notification to look into
>
> if happens to you and more people, should happen to us
>
>
> if you are ok, i would like to the delete the comment in that issue in
> 9510 since we will handle it in a new one, with a repro case
>
> thanks
>
>
> On Thu, Mar 8, 2018 at 6:41 PM, Jamie Jackson 
> wrote:
>
>> I'm having big problems with Vagrant lately:
>>
>>
>>- My private network's IP gets properly assigned (to eth1) on the
>>first vagrant up
>>- On the first vagrant reload, the IP is inappropriately assigned to
>>eth0 (the regular NAT network nic), and the IP now shows on both eth0 and
>>eth1
>>- On third vagrant reload, eth1 is disabled
>>
>>
>> Upon the third vagrant reload, my project is trashed because I can't use
>> the private network anymore. My project has a rather long initial vagrant
>> up so it is very painful for my team to have to destroy frequently.
>>
>> I see lots of networking issues reported on GitHub, so I don't have much
>> hope that this one will get fixed anytime soon, so I'm looking for any
>> workarounds you might have.
>>
>> Here's a detail of my problem: https://github.com/ha
>> shicorp/vagrant/issues/9510#issuecomment-371560182
>>
>> Thanks,
>> Jamie
>>
>> --
>> This mailing list is governed under the HashiCorp Community Guidelines -
>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>> violation of those guidelines may result in your removal from this mailing
>> list.
>>
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Vagrant" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to vagrant-up+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/vagrant-up/CA%2BonWPf5SUJ_AM0LS2wQv__%2B5W29uzHV_%3Die%
>> 2BqKrW-0WeKGiuQ%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Alvaro
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/CAHqq0eztCZRWJvSDdKGQ2QwjaBkhB
> YLKXhoMJ0G8mayJt7FPbA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CA%2BonWPcVivVVDZLgaBXUGMUJBvvMOXTDDBpEH8204KvthdbWhg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Private IP Assigned to Wrong NIC

2018-03-08 Thread Alvaro Miranda Aguilera 
not sure if the same

please open a new issue, include a repro case and instructions how to repro

please @kikitux so i can get the notification to look into

if happens to you and more people, should happen to us


if you are ok, i would like to the delete the comment in that issue in 9510
since we will handle it in a new one, with a repro case

thanks


On Thu, Mar 8, 2018 at 6:41 PM, Jamie Jackson  wrote:

> I'm having big problems with Vagrant lately:
>
>
>- My private network's IP gets properly assigned (to eth1) on the
>first vagrant up
>- On the first vagrant reload, the IP is inappropriately assigned to
>eth0 (the regular NAT network nic), and the IP now shows on both eth0 and
>eth1
>- On third vagrant reload, eth1 is disabled
>
>
> Upon the third vagrant reload, my project is trashed because I can't use
> the private network anymore. My project has a rather long initial vagrant
> up so it is very painful for my team to have to destroy frequently.
>
> I see lots of networking issues reported on GitHub, so I don't have much
> hope that this one will get fixed anytime soon, so I'm looking for any
> workarounds you might have.
>
> Here's a detail of my problem: https://github.com/
> hashicorp/vagrant/issues/9510#issuecomment-371560182
>
> Thanks,
> Jamie
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/CA%2BonWPf5SUJ_AM0LS2wQv__%2B5W29uzHV_%3Die%2BqKrW-
> 0WeKGiuQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0eztCZRWJvSDdKGQ2QwjaBkhBYLKXhoMJ0G8mayJt7FPbA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Private IP Assigned to Wrong NIC

2018-03-08 Thread Jamie Jackson 
I'm having big problems with Vagrant lately:


   - My private network's IP gets properly assigned (to eth1) on the first
   vagrant up
   - On the first vagrant reload, the IP is inappropriately assigned to
   eth0 (the regular NAT network nic), and the IP now shows on both eth0 and
   eth1
   - On third vagrant reload, eth1 is disabled


Upon the third vagrant reload, my project is trashed because I can't use
the private network anymore. My project has a rather long initial vagrant
up so it is very painful for my team to have to destroy frequently.

I see lots of networking issues reported on GitHub, so I don't have much
hope that this one will get fixed anytime soon, so I'm looking for any
workarounds you might have.

Here's a detail of my problem:
https://github.com/hashicorp/vagrant/issues/9510#issuecomment-371560182

Thanks,
Jamie

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CA%2BonWPf5SUJ_AM0LS2wQv__%2B5W29uzHV_%3Die%2BqKrW-0WeKGiuQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Enabling/Disabling plugins

2018-03-08 Thread Alvaro Miranda Aguilera 
hello

it seems packer is a better tool for this, you can use virtualbox-ovf to
start from an existing box

have a look here:
https://github.com/kikitux/virtualbox-ovf

however, if you really want to use vagrant, you can use a shell provisioner
to do the virtualbox part, so you keep all under control

the vbox guest is an iso, you can mount it as part of the script and do the
install





On Thu, Mar 8, 2018 at 1:59 PM, Michael  wrote:

> Hi all,
>
> I'm looking at creating a Vagrant VM using a CI server with no internet
> connection. Or rather, the CI only has a connection to the internet via
> Artifactory, which is acting as a proxy for Yum packages and Vagrant boxes,
> including caching those files for reproducibility.
>
> I'm trying to build a VM with centos/7 (v1801.02, Virtualbox) as a base
> image. I would also like to install VirtualBox Guest Additions, using the
> Vagrant plugin vagrant-vbguest.
>
> I will include a sanitised Vagrantfile and build script as attachments for
> this process.
>
>
> What I am trying to do is the following:
>  - Disable vagrant-vbguest
>  - Provision the VM
>  - Enable vagrant-vbguest
>  - Vagrant up again (to install Guest Additions)
>  - Export the VM
>
> However, it seems that after provisioning the machine with the plugin
> disabled, re-enabling the plugin has no effect. How can I cause the above
> set of steps to occur?
>
> Michael
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/06daea1a-c111-48e0-87ab-205cf0f28bbe%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ez5X7nGeiE_z1XFXO-1mscs0LXzns%3D4BJ0gf1R7CTsO%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Enabling/Disabling plugins

2018-03-08 Thread Michael 
Hi all,

I'm looking at creating a Vagrant VM using a CI server with no internet 
connection. Or rather, the CI only has a connection to the internet via 
Artifactory, which is acting as a proxy for Yum packages and Vagrant boxes, 
including caching those files for reproducibility.

I'm trying to build a VM with centos/7 (v1801.02, Virtualbox) as a base 
image. I would also like to install VirtualBox Guest Additions, using the 
Vagrant plugin vagrant-vbguest. 

I will include a sanitised Vagrantfile and build script as attachments for 
this process.


What I am trying to do is the following:
 - Disable vagrant-vbguest
 - Provision the VM
 - Enable vagrant-vbguest
 - Vagrant up again (to install Guest Additions)
 - Export the VM

However, it seems that after provisioning the machine with the plugin 
disabled, re-enabling the plugin has no effect. How can I cause the above 
set of steps to occur?

Michael

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/06daea1a-c111-48e0-87ab-205cf0f28bbe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Vagrantfile
Description: Binary data
#!/bin/bash
set -e

# Ensure that the box is added from Artifactory
vagrant box add "https://my/artifactor/url/centos7;

# Disable the guest additions plugin
export VAGRANT_NO_PLUGINS=1

# First build of VM
vagrant up

# Enable guest additions plugin to install Guest Additions
unset VAGRANT_NO_PLUGINS

# For some reason, running the script a few times is needed for the guest additions
vagrant halt && vagrant up
vagrant halt && vagrant up
vagrant halt

# Package the output into a box file
vagrant package --output my-centos7.box

# Upload the box file to Artifactory - command not included here