Activity log for bug #1326034

Date Who What changed Old value New value Message
2014-06-03 16:14:11 Mathieu Gagné bug added bug
2014-06-03 17:04:41 OpenStack Infra puppet-neutron: status New In Progress
2014-06-03 17:04:41 OpenStack Infra puppet-neutron: assignee Sebastien Badia (sbadia)
2014-06-03 17:34:49 Sebastien Badia bug task added puppet-openstack
2014-06-03 17:35:41 Sebastien Badia puppet-openstack: status New In Progress
2014-06-03 17:35:45 Sebastien Badia puppet-openstack: assignee Sebastien Badia (sbadia)
2014-06-04 01:33:54 Mathieu Gagné description Our gate installs and uses rspec-puppet which installs the rspec >= 2.9. RSpec deprecated a bunch of stuff and broke rspec-puppet. Example of broken jobs: http://logs.openstack.org/53/82353/6/check/gate-puppet-neutron-puppet-unit-3.4/57a302d/console.html RSpec::Puppet::ManifestMatchers::CreateGeneric implements a legacy RSpec matcher protocol. For the current protocol you should expose the failure messages via the `failure_message` and `failure_message_when_negated` methods. The `:example_group` key in an example group's metadata hash is deprecated. Use the example group's hash directly for the computed keys and `:parent_example_group` to access the parent example group metadata instead. Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` instead. Called from /Users/mgagne/Development/Projects/StackForge/puppet-neutron/spec/unit/provider/neutron_l3_ovs_bridge/neutron_spec.rb:25:in `block (3 levels) in <top (required)>'. Related issues in rspec-puppet project: * https://github.com/rodjek/rspec-puppet/issues/198 * https://github.com/rodjek/rspec-puppet/pull/199 * https://github.com/rodjek/rspec-puppet/issues/200 * https://github.com/rodjek/rspec-puppet/pull/201 Our gate installs and uses rspec-puppet which installs the rspec >= 2.9. RSpec deprecated a bunch of stuff and broke rspec-puppet. Example of broken jobs: http://logs.openstack.org/53/82353/6/check/gate-puppet-neutron-puppet-unit-3.4/57a302d/console.html RSpec::Puppet::ManifestMatchers::CreateGeneric implements a legacy RSpec matcher protocol. For the current protocol you should expose the failure messages via the `failure_message` and `failure_message_when_negated` methods. The `:example_group` key in an example group's metadata hash is deprecated. Use the example group's hash directly for the computed keys and `:parent_example_group` to access the parent example group metadata instead. Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` instead. Called from /Users/mgagne/Development/Projects/StackForge/puppet-neutron/spec/unit/provider/neutron_l3_ovs_bridge/neutron_spec.rb:25:in `block (3 levels) in <top (required)>'. The main issue is caused by this change brought in RSpec 3.0.0 (thanks Sebastian Badia for those links): Rename be_true and be_false to be_truthy and be_falsey. (Sam Phippen) References: * https://www.relishapp.com/rspec/rspec-ex​pectations/v/2-99/docs/built-in-matchers * https://www.relishapp.com/rspec/rspe​c-expectations/v/3-0/docs/changelog Related issues in rspec-puppet project: * https://github.com/rodjek/rspec-puppet/issues/198 * https://github.com/rodjek/rspec-puppet/pull/199 * https://github.com/rodjek/rspec-puppet/issues/200 * https://github.com/rodjek/rspec-puppet/pull/201
2014-06-04 01:36:18 Mathieu Gagné description Our gate installs and uses rspec-puppet which installs the rspec >= 2.9. RSpec deprecated a bunch of stuff and broke rspec-puppet. Example of broken jobs: http://logs.openstack.org/53/82353/6/check/gate-puppet-neutron-puppet-unit-3.4/57a302d/console.html RSpec::Puppet::ManifestMatchers::CreateGeneric implements a legacy RSpec matcher protocol. For the current protocol you should expose the failure messages via the `failure_message` and `failure_message_when_negated` methods. The `:example_group` key in an example group's metadata hash is deprecated. Use the example group's hash directly for the computed keys and `:parent_example_group` to access the parent example group metadata instead. Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` instead. Called from /Users/mgagne/Development/Projects/StackForge/puppet-neutron/spec/unit/provider/neutron_l3_ovs_bridge/neutron_spec.rb:25:in `block (3 levels) in <top (required)>'. The main issue is caused by this change brought in RSpec 3.0.0 (thanks Sebastian Badia for those links): Rename be_true and be_false to be_truthy and be_falsey. (Sam Phippen) References: * https://www.relishapp.com/rspec/rspec-ex​pectations/v/2-99/docs/built-in-matchers * https://www.relishapp.com/rspec/rspe​c-expectations/v/3-0/docs/changelog Related issues in rspec-puppet project: * https://github.com/rodjek/rspec-puppet/issues/198 * https://github.com/rodjek/rspec-puppet/pull/199 * https://github.com/rodjek/rspec-puppet/issues/200 * https://github.com/rodjek/rspec-puppet/pull/201 Our gate installs and uses rspec-puppet which installs the rspec >= 2.9. RSpec deprecated a bunch of stuff and broke rspec-puppet. Example of broken jobs: http://logs.openstack.org/53/82353/6/check/gate-puppet-neutron-puppet-unit-3.4/57a302d/console.html RSpec::Puppet::ManifestMatchers::CreateGeneric implements a legacy RSpec matcher protocol. For the current protocol you should expose the failure messages via the `failure_message` and `failure_message_when_negated` methods. The `:example_group` key in an example group's metadata hash is deprecated. Use the example group's hash directly for the computed keys and `:parent_example_group` to access the parent example group metadata instead. Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` instead. Called from /Users/mgagne/Development/Projects/StackForge/puppet-neutron/spec/unit/provider/neutron_l3_ovs_bridge/neutron_spec.rb:25:in `block (3 levels) in <top (required)>'. The main issue is caused by this failure: Failure/Error: expect(provider.exists?).to be_false expected false to respond to `false?` A change was brought in RSpec 3.0.0 related to built-in matchers (thanks Sebastian Badia for those links): Rename be_true and be_false to be_truthy and be_falsey. (Sam Phippen) References: * https://www.relishapp.com/rspec/rspec-expectations/v/3-0/docs/built-in-matchers * https://www.relishapp.com/rspec/rspe​c-expectations/v/3-0/docs/changelog Related issues in rspec-puppet project: * https://github.com/rodjek/rspec-puppet/issues/198 * https://github.com/rodjek/rspec-puppet/pull/199 * https://github.com/rodjek/rspec-puppet/issues/200 * https://github.com/rodjek/rspec-puppet/pull/201
2014-06-04 15:06:40 OpenStack Infra puppet-neutron: status In Progress Fix Committed
2014-06-12 16:41:32 OpenStack Infra tags in-stable-icehouse
2014-06-18 16:06:03 OpenStack Infra tags in-stable-icehouse in-stable-havana in-stable-icehouse
2015-03-27 17:41:28 Mathieu Gagné puppet-neutron: milestone 5.0.0
2015-03-27 17:41:42 Mathieu Gagné nominated for series puppet-neutron/icehouse
2015-03-27 17:41:42 Mathieu Gagné bug task added puppet-neutron/icehouse
2015-03-27 17:41:48 Mathieu Gagné puppet-neutron/icehouse: milestone 4.1.0
2015-03-27 17:41:50 Mathieu Gagné puppet-neutron/icehouse: status New Fix Released
2015-03-27 17:41:51 Mathieu Gagné puppet-neutron: status Fix Committed Fix Released
2015-03-27 17:42:11 Mathieu Gagné nominated for series puppet-neutron/havana
2015-03-27 17:42:11 Mathieu Gagné bug task added puppet-neutron/havana
2015-03-27 17:42:46 Mathieu Gagné puppet-neutron/havana: status New Fix Committed
2015-04-16 14:57:42 OpenStack Infra puppet-openstack: assignee Sebastien Badia (sbadia) François Charlier (francois-charlier)