Beaker broken for Fedora >20, Ubuntu 15.04 #63

dfarrell07 · 2015-03-02T00:38:58Z

Update: Turns out the F21 failures have nothing to do with the info in the first few posts below. Skip to this comment.

Another update: ^^That was true, but now that we have Puppet 3.7.5 and the associated patch we're seeing the tar-related error again, so we're back to the first issue described.

Third update: Fedora 21, 22 and Ubuntu 15.04 Beaker tests are failing. The Fedora ones are clearly an issue with Beaker, it attempts invalid commands. The Ubuntu may be as well, I haven't looked as closely. Fedora 20, CentOS 7 and Ubuntu 14.04 work.

Apparently the Fedora 21 Vagrant box we're using doesn't ship with tar by default (not sure if that's the case with F21 generally, likely so).

[~/puppet-opendaylight]$ BEAKER_destroy=no bundle exec rake fedora_21 &> fedora_21_1.log
[~/puppet-opendaylight]$ cd .vagrant/beaker_vagrant_files/fedora-21.yml
[~/puppet-opendaylight/.vagrant/beaker_vagrant_files/fedora-21.yml]$ vagrant ssh
Last login: Mon Mar  2 00:30:07 2015 from 10.0.2.2
[vagrant@fedora-21 ~]$ command -v tar
[vagrant@fedora-21 ~]$ which tar
/usr/bin/which: no tar in (/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/vagrant/.local/bin:/home/vagrant/bin)

It is is the repos, we just need to manually install it for Fedora 21.

[vagrant@fedora-21 ~]$ sudo yum provides tar
2:tar-1.27.1-7.fc21.x86_64 : A GNU file archiving program
Repo        : fedora

The text was updated successfully, but these errors were encountered:

* Without this, wouldn't be provisioned via RPM or tarball * Relevant to #32 and #63 Signed-off-by: Daniel Farrell <[email protected]>

dfarrell07 · 2015-03-02T20:29:43Z

Note that I'm not totally convinced that is really about tar/lack of tar. Could be something else and a cryptic (as normal) error message from Puppet.

dfarrell07 · 2015-03-02T20:31:04Z

Here's the most relevant part of F21 Beaker error message, btw:

puppet module install camptocamp-archive
Last 10 lines of output were:
        Notice: Preparing to install into /etc/puppet/modules ...
        Notice: Downloading from https://forgeapi.puppetlabs.com ...
        Error: No suitable tar implementation found
        Error: Try 'puppet help module install' for usage

dfarrell07 · 2015-03-04T19:53:29Z

Until we get this line of code via a new Puppet release, F21 Beaker tests will be broken in the same way the F20 ones are.

Note that CentOS 7 is not affected because of this line.

Marking this as blocked on a Puppet release that includes 1b8737.

dfarrell07 · 2015-03-31T16:20:06Z

The fix we need was included when the Puppet 3.7.5 release was cut.

Hasn't been packaged for Fedora yet:

[~/puppet-opendaylight]$ puppet --version
3.7.4
[~/puppet-opendaylight]$ sudo yum update -y
[sudo] password for daniel: 
Loaded plugins: langpacks, refresh-packagekit
bluejeans                                                       | 2.9 kB  00:00:00     
google-chrome                                                   |  951 B  00:00:00     
rpmfusion-free-updates                                          | 3.3 kB  00:00:00     
rpmfusion-nonfree-updates                                       | 3.3 kB  00:00:00     
updates/20/x86_64/metalink                                      |  14 kB  00:00:00     
No packages marked for update

dfarrell07 · 2015-04-06T14:35:27Z

Hasn't been packaged for Fedora yet:

Tuns out they use a different Yum repo. Once I pointed Yum at yum.puppetlabs.com I got the 3.7.5 update. Direct link to RPM.

[~]$ puppet --version                                                                                                                      10:35:12
3.7.5
[~]$ sudo yum info puppet                                                                                                                  10:35:14
Loaded plugins: langpacks, refresh-packagekit
Installed Packages
Name        : puppet
Arch        : noarch
Version     : 3.7.5
Release     : 1.fc20
Size        : 6.3 M
Repo        : installed
From repo   : puppetlabs-products
Summary     : A network tool for managing many disparate systems
URL         : http://puppetlabs.com
License     : ASL 2.0
Description : Puppet lets you centrally manage every important aspect of your system using a
            : cross-platform specification language that manages all the separate elements
            : normally aggregated in different files, like users, cron jobs, and hosts,
            : along with obviously discrete elements like packages, services, and files.

dfarrell07 · 2015-04-06T15:30:01Z

After I moved to Puppet 3.7.5 and got the associated fix I'm back to seeing tar-related errors.

fedora-21 11:05:34$ puppet module install puppetlabs-stdlib
Notice: Preparing to install into /etc/puppet/modules ...
Notice: Downloading from https://forgeapi.puppetlabs.com ...
Error: No suitable tar implementation found
Error: Try 'puppet help module install' for usage

I think that's caused by this puppetlabs/puppet code:

  def self.instance
    if Puppet::Util.which('tar') && ! Puppet::Util::Platform.windows?
      Gnu.new
    elsif Puppet.features.minitar? && Puppet.features.zlib?
      Mini.new
    else
      raise RuntimeError, 'No suitable tar implementation found'
    end
  end

Which makes sense given that which tar does in fact fail on F21:

[vagrant@fedora-21 ~]$ which tar
/usr/bin/which: no tar in (/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/vagrant/.local/bin:/home/vagrant/bin)
[vagrant@fedora-21 ~]$ echo $?
1

dfarrell07 · 2015-04-06T15:32:00Z

Manually installing tar fixes the problem:

[vagrant@fedora-21 ~]$ puppet module install puppetlabs-stdlib
Notice: Preparing to install into /home/vagrant/.puppet/modules ...
Notice: Created target directory /home/vagrant/.puppet/modules
Notice: Downloading from https://forgeapi.puppetlabs.com ...
Error: No suitable tar implementation found
Error: Try 'puppet help module install' for usage
[vagrant@fedora-21 ~]$ sudo yum install -y tar
Resolving Dependencies
--> Running transaction check
---> Package tar.x86_64 2:1.27.1-7.fc21 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

===================================================================================================================================================
 Package                       Arch                             Version                                     Repository                        Size
===================================================================================================================================================
Installing:
 tar                           x86_64                           2:1.27.1-7.fc21                             fedora                           894 k

Transaction Summary
===================================================================================================================================================
Install  1 Package

Total download size: 894 k
Installed size: 2.9 M
Downloading packages:
tar-1.27.1-7.fc21.x86_64.rpm                                                                                                | 894 kB  00:00:05     
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction (shutdown inhibited)
  Installing : 2:tar-1.27.1-7.fc21.x86_64                                                                                                      1/1 
  Verifying  : 2:tar-1.27.1-7.fc21.x86_64                                                                                                      1/1 

Installed:
  tar.x86_64 2:1.27.1-7.fc21                                                                                                                       

Complete!
[vagrant@fedora-21 ~]$ puppet module install puppetlabs-stdlib
Notice: Preparing to install into /home/vagrant/.puppet/modules ...
Notice: Downloading from https://forgeapi.puppetlabs.com ...
Notice: Installing -- do not interrupt ...
/home/vagrant/.puppet/modules
└── puppetlabs-stdlib (v4.5.1)

dfarrell07 · 2015-04-06T15:58:37Z

I don't think I'll be able to fix the tar issue by using a simple Puppet package type in the ODL mod, as this is failing way before we even puppet apply the ODL mod, during the initial module installs via Beaker in spec_helper_acceptance.rb.

  # Configure all nodes in nodeset
  c.before :suite do
    # Install opendaylight module on any/all Beaker hosts
    # TODO: Should this be done in host.each loop?
    puppet_module_install(:source => proj_root, :module_name => 'opendaylight')
    hosts.each do |host|
      # Install stdlib, a dependency of the odl mod
      # TODO: Why is 1 an acceptable exit code?
      on host, puppet('module', 'install', 'puppetlabs-stdlib'), { :acceptable_exit_codes => [0,1] }
      # Install archive, a dependency of the odl mod use for tarball-type installs
      on host, puppet('module', 'install', 'camptocamp-archive'), { :acceptable_exit_codes => [0] }
      # Install Java Puppet mod, a dependency of the tarball install method
      on host, puppet('module', 'install', 'puppetlabs-java'), { :acceptable_exit_codes => [0] }
    end
  end

First debuging plan is to attempt to find an F21 Vagant box that does have tar installed by default (relevant to #15).

dfarrell07 · 2015-04-06T17:09:37Z

The chef/fedora-21 box (which is the one I hoped to move to in #15) has tar:

[~/f21]$ vagrant destroy -f                                                                                                                13:07:40
==> fedora-21: Destroying VM and associated drives...
[~/f21]$ vagrant up                                                                                                                        13:07:46
Bringing machine 'fedora-21' up with 'virtualbox' provider...
==> fedora-21: Importing base box 'chef/fedora-21'...
==> fedora-21: Matching MAC address for NAT networking...
==> fedora-21: Checking if box 'chef/fedora-21' is up to date...
==> fedora-21: Setting the name of the VM: f21_fedora-21_1428340077792_25802
==> fedora-21: Clearing any previously set network interfaces...
==> fedora-21: Preparing network interfaces based on configuration...
    fedora-21: Adapter 1: nat
==> fedora-21: Forwarding ports...
    fedora-21: 22 => 2222 (adapter 1)
==> fedora-21: Running 'pre-boot' VM customizations...
==> fedora-21: Booting VM...
==> fedora-21: Waiting for machine to boot. This may take a few minutes...
    fedora-21: SSH address: 127.0.0.1:2222
    fedora-21: SSH username: vagrant
    fedora-21: SSH auth method: private key
    fedora-21: Warning: Connection timeout. Retrying...
    fedora-21: 
    fedora-21: Vagrant insecure key detected. Vagrant will automatically replace
    fedora-21: this with a newly generated keypair for better security.
    fedora-21: 
    fedora-21: Inserting generated public key within guest...
    fedora-21: Removing insecure key from the guest if its present...
    fedora-21: Key inserted! Disconnecting and reconnecting using new SSH key...
==> fedora-21: Machine booted and ready!
==> fedora-21: Checking for guest additions in VM...
==> fedora-21: Setting hostname...
==> fedora-21: Mounting shared folders...
    fedora-21: /vagrant => /home/daniel/f21
[~/f21]$ vagrant ssh                                                                                                                       13:08:22
Last login: Thu Dec 18 07:06:12 2014 from 10.0.2.2
[vagrant@fedora-21 ~]$ which tar
/usr/bin/tar
[vagrant@fedora-21 ~]$ logout
Connection to 127.0.0.1 closed.
[~/f21]$ cat Vagrantfile                                                                                                                   13:08:54
Vagrant.configure("2") do |c|
  c.vm.define 'fedora-21' do |v|
    v.vm.hostname = 'fedora-21'
    v.vm.box = 'chef/fedora-21'
    v.vm.box_url = 'http://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_fedora-21_chef-provisionerless.box'
    v.vm.box_check_update = 'true'
    v.vm.provider :virtualbox do |vb|
      vb.customize ['modifyvm', :id, '--memory', '1024']
    end
  end
end

dfarrell07 · 2015-04-06T18:13:28Z

After switching to the chef/fedora-21 box, I'm seeing a different error:

[~/f21]$ vagrant up                                                                                                                        13:19:02
Bringing machine 'fedora-21' up with 'virtualbox' provider...
==> fedora-21: Importing base box 'chef/fedora-21'...
==> fedora-21: Matching MAC address for NAT networking...
==> fedora-21: Checking if box 'chef/fedora-21' is up to date...
==> fedora-21: Setting the name of the VM: f21_fedora-21_1428341646241_46333
==> fedora-21: Fixed port collision for 22 => 2222. Now on port 2200.
==> fedora-21: Clearing any previously set network interfaces...
==> fedora-21: Preparing network interfaces based on configuration...
    fedora-21: Adapter 1: nat
    fedora-21: Adapter 2: hostonly
==> fedora-21: Forwarding ports...
    fedora-21: 22 => 2200 (adapter 1)
==> fedora-21: Running 'pre-boot' VM customizations...
==> fedora-21: Booting VM...
==> fedora-21: Waiting for machine to boot. This may take a few minutes...
    fedora-21: SSH address: 127.0.0.1:2200
    fedora-21: SSH username: vagrant
    fedora-21: SSH auth method: private key
    fedora-21: Warning: Connection timeout. Retrying...
    fedora-21: 
    fedora-21: Vagrant insecure key detected. Vagrant will automatically replace
    fedora-21: this with a newly generated keypair for better security.
    fedora-21: 
    fedora-21: Inserting generated public key within guest...
    fedora-21: Removing insecure key from the guest if its present...
    fedora-21: Key inserted! Disconnecting and reconnecting using new SSH key...
==> fedora-21: Machine booted and ready!
==> fedora-21: Checking for guest additions in VM...
==> fedora-21: Setting hostname...
==> fedora-21: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

ARPCHECK=no /sbin/ifup eth1 2> /dev/null

Stdout from the command:

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


Stderr from the command:

Based on this thread, the issue seems to be fairly common and unclear-if-fixed.

Ideas:

Check other F21 boxes to see if they show this behavior
Report this failure to Chef folks who built the F21 box, may be an error on their part.

dfarrell07 · 2015-04-13T16:40:19Z

Using this Beaker node config:

HOSTS:
  fedora-21:
    roles:
      - master
    platform: fedora-21-x86_64
    box: hansode/fedora-21-server-x86_64
    box_url: https://atlas.hashicorp.com/hansode/boxes/fedora-21-server-x86_64
    hypervisor: vagrant

CONFIG:
  log_level: verbose
  type: foss

So this F21 Vagrant box, using this Vagrantfile:

Vagrant.configure("2") do |c|
  c.vm.define 'fedora-21' do |v|
    v.vm.hostname = 'fedora-21'
    v.vm.box = 'hansode/fedora-21-server-x86_64'
    v.vm.box_url = 'https://atlas.hashicorp.com/hansode/boxes/fedora-21-server-x86_64'
    v.vm.box_check_update = 'true'
    v.vm.network :private_network, ip: "10.255.148.171", :netmask => "255.255.0.0", :mac => "080027DBC21B"
    v.vm.provider :virtualbox do |vb|
      vb.customize ['modifyvm', :id, '--memory', '1024']
    end
  end
end

I see this error:

 Failed to exec 'vagrant up'. Error was The guest machine e
ntered an invalid state while waiting for it (RuntimeError)
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.

dfarrell07 · 2015-04-13T17:49:32Z

Same error as described above with the box-cutter/fedora21 Vagrant box. Debugging...

dfarrell07 · 2015-04-13T17:55:45Z

Same error as described above with the box-cutter/fedora21 Vagrant box. Debugging...

Looks like it's actually an error with my VBox kernel mod version. sigh

dfarrell07 · 2015-04-13T18:12:35Z

Looks like it's actually an error with my VBox kernel mod version.

After fixing my local Vagrant setup, re-testing the box-cutter/fedora21 Vagrant box.

Beaker config:

HOSTS:
  fedora-21:
    roles:
      - master
    platform: fedora-21-x86_64
    box: box-cutter/fedora21
    box_url: https://atlas.hashicorp.com/box-cutter/boxes/fedora21
    hypervisor: vagrant

CONFIG:
  log_level: verbose
  type: foss

Resulting Vagrantfile:

Vagrant.configure("2") do |c|
  c.vm.define 'fedora-21' do |v|
    v.vm.hostname = 'fedora-21'
    v.vm.box = 'box-cutter/fedora21'
    v.vm.box_url = 'https://atlas.hashicorp.com/box-cutter/boxes/fedora21'
    v.vm.box_check_update = 'true'
    v.vm.network :private_network, ip: "10.255.244.193", :netmask => "255.255.0.0", :mac => "08002788D552"
    v.vm.provider :virtualbox do |vb|
      vb.customize ['modifyvm', :id, '--memory', '1024']
    end
  end
end

Fails with (partial)

Failed to exec 'vagrant up'. Error was The following SSH command responded with a non-zero exit status. (RuntimeError)
Vagrant assumes that this means the command failed!

ARPCHECK=no /sbin/ifup eth1 2> /dev/null

Stdout from the command:

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

dfarrell07 · 2015-04-13T18:32:04Z

Device eth1 does not seem to be present, delaying initialization.

This is a fairly helpful relevant thread.

dfarrell07 · 2015-04-13T18:36:36Z

Device eth1 does not seem to be present, delaying initialization.

Also helpful.

dfarrell07 · 2015-04-13T18:41:41Z

Building on the info provided in the two threads above, I'm able to reproduce the problem in a fairly simple setup.

[~/f21]$ vagrant --version
Vagrant 1.7.2

It doesn't seem to matter which F21 box I use.

Failing Example

Vagrantfile:

Vagrant.configure("2") do |c|
  c.vm.define 'fedora-21' do |v|
    v.vm.box = 'chef/fedora-21'
    v.vm.network :private_network, ip: "10.0.0.2"
  end
end

Output of vagrant up:

[~/f21]$ vagrant up
# snip
==> fedora-21: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

ARPCHECK=no /sbin/ifup eth1 2> /dev/null

Stdout from the command:

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


Stderr from the command:

Working example

Just removing the private network line in the Vagrantfile:

Vagrant.configure("2") do |c|
  c.vm.define 'fedora-21' do |v|
    v.vm.box = 'chef/fedora-21'
  end
end

Output of vagrant up:

[~/f21]$ vagrant destroy -f
==> fedora-21: Forcing shutdown of VM...
==> fedora-21: Destroying VM and associated drives...
[~/f21]$ vagrant up
# snip, works
[~/f21]$ echo $?
0

* Likely an issue with Vagrant image, not Puppet mod * Relevant to issue #63 Signed-off-by: Daniel Farrell <[email protected]>

As of this commit, beaker (2.14.1) is currently incompatible with vagrant/fedora 20+. See: dfarrell07/puppet-opendaylight#63 (comment)

dfarrell07 · 2015-08-07T23:23:51Z

I'm still seeing the failure from /sbin/ifup eth1 with boxcutter/fedora21, boxcutter/fedora22 and chef/fedora-21. Attempting to upgrade Beaker 2.10.0 to 2.18.3 and re-test.

dfarrell07 · 2015-08-07T23:28:03Z

Seeing the same error for Beaker 2.18.3.

ARPCHECK=no /sbin/ifup eth1 2> /dev/null

Stdout from the command:

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

[~/puppet-opendaylight]$ bundle list | grep beaker
  * beaker (2.18.3)
  * beaker-rspec (5.0.2)

Upgrade CentOS box to one that tracks the latest version (15.05 atm). Use boxcutter boxes for all Vagrantfiles. Seem higher quality. Add a Fedora 22 box. Note that Beaker 2.18.3 (current version) is incompatible with F20+, so those tests are currently failing. See #63 Signed-off-by: Daniel Farrell <[email protected]>

dfarrell07 · 2015-08-08T00:33:07Z

boxcutter/ubuntu1404 works, boxcutter/ubuntu1504 fails at

Error was The following SSH command responded with a non-zero exit status. (RuntimeError)
Vagrant assumes that this means the command failed!

service hostname start

Stdout from the command:



Stderr from the command:

stdin: is not a tty

Use (seemingly better) boxcutter Ubuntu 14.04 box. Add Ubuntu 15.04 box. Note that the 15.04 Beaker tests are currently failing (see #63). Update Rake tasks accordingly. Signed-off-by: Daniel Farrell <[email protected]>

dfarrell07 · 2015-08-08T01:30:47Z

Summery:

Fedora 21, 22 and Ubuntu 15.04 Beaker tests are failing. The Fedora ones are clearly an issue with Beaker, it attempts invalid commands. The Ubuntu may be as well, I haven't looked as closely. Fedora 20, CentOS 7 and Ubuntu 14.04 work.

Upgrade CentOS box to one that tracks the latest version (15.05 atm). Use boxcutter boxes for all Vagrantfiles. Seem higher quality. Add a Fedora 22 box. Note that Beaker 2.18.3 (current version) is incompatible with F20+, so those tests are currently failing. See #63 Signed-off-by: Daniel Farrell <[email protected]>

Use (seemingly better) boxcutter Ubuntu 14.04 box. Add Ubuntu 15.04 box. Note that the 15.04 Beaker tests are currently failing (see #63). Update Rake tasks accordingly. Signed-off-by: Daniel Farrell <[email protected]>

dfarrell07 · 2015-12-01T16:32:01Z

I'm addressing this by moving from Vagrant -> Docker as the Beaker provider. See #8.

dfarrell07 added the prio:normal label Mar 2, 2015

dfarrell07 self-assigned this Mar 2, 2015

dfarrell07 added this to the Release on Forge milestone Mar 2, 2015

dfarrell07 added type:feature info:progress-0 good-for-beginners labels Mar 2, 2015

dfarrell07 added a commit that referenced this issue Mar 2, 2015

Add rpm flag to F20/21 Beaker host YAML files

0da8105

* Without this, wouldn't be provisioned via RPM or tarball * Relevant to #32 and #63 Signed-off-by: Daniel Farrell <[email protected]>

dfarrell07 changed the title ~~Install tar on Fedora 21~~ Fedora 21 Beaker tests failing Mar 2, 2015

dfarrell07 added info:progress-25 and removed good-for-beginners info:progress-0 labels Mar 2, 2015

This was referenced Mar 2, 2015

Fedora 20 Beaker tests failing #32

Closed

Move to chef/fedora-21 Beaker node #15

Closed

dfarrell07 added the blocked label Mar 4, 2015

dfarrell07 mentioned this issue Mar 5, 2015

Beaker test coverage for ODL port param #48

Closed

dfarrell07 mentioned this issue Mar 16, 2015

rspec-puppet test coverage for ODL port #47

Closed

dfarrell07 removed this from the Release on Forge milestone Mar 31, 2015

dfarrell07 added info:progress-75 and removed info:progress-25 labels Mar 31, 2015

dfarrell07 removed the blocked label Apr 6, 2015

dfarrell07 added a commit that referenced this issue Apr 24, 2015

Add README docs on failing F21 Beaker tests

c475f01

* Likely an issue with Vagrant image, not Puppet mod * Relevant to issue #63 Signed-off-by: Daniel Farrell <[email protected]>

dfarrell07 mentioned this issue Apr 24, 2015

Final Audit Before Release #78

Closed

jhoblitt added a commit to jhoblitt/puppetlabs-ntp that referenced this issue Jun 15, 2015

add fedora 21 nodeset

fc38144

As of this commit, beaker (2.14.1) is currently incompatible with vagrant/fedora 20+. See: dfarrell07/puppet-opendaylight#63 (comment)

jhoblitt added a commit to jhoblitt/puppetlabs-ntp that referenced this issue Jun 23, 2015

add fedora 21 nodeset

5fbaa2f

As of this commit, beaker (2.14.1) is currently incompatible with vagrant/fedora 20+. See: dfarrell07/puppet-opendaylight#63 (comment)

jhoblitt added a commit to jhoblitt/puppetlabs-ntp that referenced this issue Jun 23, 2015

add fedora 21 nodeset

7291d1a

As of this commit, beaker (2.14.1) is currently incompatible with vagrant/fedora 20+. See: dfarrell07/puppet-opendaylight#63 (comment)

dfarrell07 changed the title ~~Fedora 21 Beaker tests failing~~ Beaker broken for Fedora >20, Ubuntu 15.04 Aug 8, 2015

dfarrell07 closed this as completed Dec 1, 2015

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Beaker broken for Fedora >20, Ubuntu 15.04 #63

Beaker broken for Fedora >20, Ubuntu 15.04 #63

dfarrell07 commented Mar 2, 2015

dfarrell07 commented Mar 2, 2015

dfarrell07 commented Mar 2, 2015

dfarrell07 commented Mar 4, 2015

dfarrell07 commented Mar 31, 2015

dfarrell07 commented Apr 6, 2015

dfarrell07 commented Apr 6, 2015

dfarrell07 commented Apr 6, 2015

dfarrell07 commented Apr 6, 2015

dfarrell07 commented Apr 6, 2015

dfarrell07 commented Apr 6, 2015

dfarrell07 commented Apr 13, 2015

dfarrell07 commented Apr 13, 2015

dfarrell07 commented Apr 13, 2015

dfarrell07 commented Apr 13, 2015

dfarrell07 commented Apr 13, 2015

dfarrell07 commented Apr 13, 2015

dfarrell07 commented Apr 13, 2015

dfarrell07 commented Aug 7, 2015

dfarrell07 commented Aug 7, 2015

dfarrell07 commented Aug 8, 2015

dfarrell07 commented Aug 8, 2015

dfarrell07 commented Dec 1, 2015

Beaker broken for Fedora >20, Ubuntu 15.04 #63

Beaker broken for Fedora >20, Ubuntu 15.04 #63

Comments

dfarrell07 commented Mar 2, 2015

dfarrell07 commented Mar 2, 2015

dfarrell07 commented Mar 2, 2015

dfarrell07 commented Mar 4, 2015

dfarrell07 commented Mar 31, 2015

dfarrell07 commented Apr 6, 2015

dfarrell07 commented Apr 6, 2015

dfarrell07 commented Apr 6, 2015

dfarrell07 commented Apr 6, 2015

dfarrell07 commented Apr 6, 2015

dfarrell07 commented Apr 6, 2015

dfarrell07 commented Apr 13, 2015

dfarrell07 commented Apr 13, 2015

dfarrell07 commented Apr 13, 2015

dfarrell07 commented Apr 13, 2015

dfarrell07 commented Apr 13, 2015

dfarrell07 commented Apr 13, 2015

dfarrell07 commented Apr 13, 2015

Failing Example

Working example

dfarrell07 commented Aug 7, 2015

dfarrell07 commented Aug 7, 2015

dfarrell07 commented Aug 8, 2015

dfarrell07 commented Aug 8, 2015

dfarrell07 commented Dec 1, 2015