[Container-tools] [Devtools] Subtlety with libvirt provider that is causing quite a bit of misinformation

[Andrew Lee Rubinger]

Thanks for sending this along.

Because I'm newer to Vagrant; does "vagrant destroy" sufficiently clean up
so that the next "up" operation is a clean state?  Or in libvirt does this
have the same issue as you mention with caching in the storage pool?

S,
ALR

On Thu, Jun 2, 2016 at 10:25 AM, Dusty Mabe <dusty at dustymabe.com> wrote:

>
>
> On 06/02/2016 10:23 AM, Dusty Mabe wrote:
> >
> > There is a small subtlety with the libvirt vagrant provider that many
> > people aren't aware of.
> >
> > On the first `vagrant up` the vagrant box will be uploaded to the
> > libvirt storage pool and then used as a backing device for the vm that
> > gets started. So now you have the vagrant box file (lives in the
> > .vagrant.d directory) as well as a file in the libvirt storage pool.
> >
> > The problem comes about when you remove/re-add a box to a machine.
> > When you remove the box, it removes the box from vagrant but it does
> > not remove the box from the libvirt storage pool. If you subsequently
> > re-add the box (a newer version this time) to vagrant and perform a
> > `vagrant up` then no box gets uploaded because there is already a
> > "backing image" in libvirt with that name.
> >
> > What this leads to is people thinking they have the latest version of
> > the CDK installed, but really using something that is old as dirt.
> >
> > One example of this was the developers post [1] that came out a week
> > ago. The author was using a CDK box from January and some of the
> > information he had in the post was old.
> >
> > Another example came to me from some of my contacts in consulting.
> >
> > Basically this is dangerous because some people can "test" things and
> > "verify" they are working and not realize they are using old stuff.
> >
> > We need to somehow resolve this in the vagrant-libvirt provider or
> > come up with some other, client side way of verifying things.
> >
> > Dusty
> >
> > [1]
> http://developers.redhat.com/blog/2016/05/27/use-vagrant-landrush-to-add-dns-features-to-your-openshift-cdk-machine/
>
>
> You can workaround this now by doing something like the following:
>
> vagrant box remove cdkv2
> virsh vol-delete --pool default cdkv2_vagrant_box_image_0.img
> vagrant box add ...
>
> Dusty
>
> _______________________________________________
> Devtools mailing list
> Devtools at redhat.com
> https://www.redhat.com/mailman/listinfo/devtools
>



-- 
Red Hat Developer Programs Architecture
@ALRubinger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/container-tools/attachments/20160602/d5802419/attachment.htm>