Systest_katello not destroying VMs

Development
1

Could somebody look at the systest_katello job on Jenkins please? It
doesn't appear to be destroying VMs once the job completes.

The job script has a trap set up to call vagrant destroy, but this
appears to error:

  • exit 0
  • vagrant destroy
    There are errors in the configuration of this machine. Please fix
    the following errors and try again:

vm:

  • The 'main' provisioner could not be found.

++ vagrant destroy
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:

  • The 'main' provisioner could not be found.
··· -- Dominic Cleal dominic@cleal.org
2

What version of vagrant is running on the slaves currently?

··· On Aug 12, 2016 3:26 AM, "Dominic Cleal" wrote:

Could somebody look at the systest_katello job on Jenkins please? It
doesn’t appear to be destroying VMs once the job completes.

The job script has a trap set up to call vagrant destroy, but this
appears to error:

  • exit 0
  • vagrant destroy
    There are errors in the configuration of this machine. Please fix
    the following errors and try again:

vm:

  • The ‘main’ provisioner could not be found.

++ vagrant destroy
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:

  • The ‘main’ provisioner could not be found.

–
Dominic Cleal
dominic@cleal.org

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

3

Vagrant 1.4.2 with vagrant-rackspace 0.1.6
(https://github.com/theforeman/foreman-infra/blob/da45a3fd9652f387dc6a110afbf5f35f07e2d126/puppet/modules/slave/manifests/vagrant.pp).

··· On 12/08/16 12:29, Eric D Helms wrote: > What version of vagrant is running on the slaves currently?

–
Dominic Cleal
dominic@cleal.org

4

Looks like named provisioners were added in 1.7 which makes me surprised
they spin up. We'll have to add a version check or consider upgrading
vagrant.

··· On Aug 12, 2016 7:30 AM, "Dominic Cleal" wrote:

On 12/08/16 12:29, Eric D Helms wrote:

What version of vagrant is running on the slaves currently?

Vagrant 1.4.2 with vagrant-rackspace 0.1.6
(https://github.com/theforeman/foreman-infra/blob/
da45a3fd9652f387dc6a110afbf5f35f07e2d126/puppet/modules/
slave/manifests/vagrant.pp).

–
Dominic Cleal
dominic@cleal.org

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

5

This doesn't seem to be fixed, I logged in today to find another load of
VMs running. Can you please turn this off unless fixed? I'm worried that
it'll exceed the account budget at the current rate.

··· On 12/08/16 12:48, Eric D Helms wrote: > Looks like named provisioners were added in 1.7 which makes me surprised > they spin up. We'll have to add a version check or consider upgrading > vagrant.

–
Dominic Cleal
dominic@cleal.org

6

The PR [1] with the fix did not get merged until today and a test run with
that code in place seems to successfully delete [2] the spun up VM.

[1] https://github.com/Katello/forklift/pull/274
[2] http://ci.theforeman.org/job/systest_katello/1953/consoleFull

··· On Fri, Aug 19, 2016 at 3:26 AM, Dominic Cleal wrote:

On 12/08/16 12:48, Eric D Helms wrote:

Looks like named provisioners were added in 1.7 which makes me surprised
they spin up. We’ll have to add a version check or consider upgrading
vagrant.

This doesn’t seem to be fixed, I logged in today to find another load of
VMs running. Can you please turn this off unless fixed? I’m worried that
it’ll exceed the account budget at the current rate.

–
Dominic Cleal
dominic@cleal.org

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University