005781fe1f
Before defining the package for the generic_service, check if it is already defined, either by $noval_title or $package_name naming. Create dependency relationship(s) with the service resource based on how the package is defined in the catalog. Otherwise, it's possible to end up with a duplicate package definition, or, more likely, the dependency from the service definition to break. This occurs most specifically with the spicehtml5proxy class on EL-based platforms. Change-Id: I215a95cac1d4b97837b67b417ff5fd7e6e9480d6 Closes-bug: 1465433
36 lines
681 B
Ruby
36 lines
681 B
Ruby
require 'spec_helper'
|
|
|
|
describe 'nova::generic_service' do
|
|
describe 'package should come before service' do
|
|
let :pre_condition do
|
|
'include nova'
|
|
end
|
|
|
|
let :params do
|
|
{
|
|
:package_name => 'foo',
|
|
:service_name => 'food',
|
|
:enabled => true
|
|
}
|
|
end
|
|
|
|
let :facts do
|
|
{ :osfamily => 'Debian' }
|
|
end
|
|
|
|
let :title do
|
|
'foo'
|
|
end
|
|
|
|
it { is_expected.to contain_service('nova-foo').with(
|
|
'name' => 'food',
|
|
'ensure' => 'running',
|
|
'enable' => true
|
|
)}
|
|
|
|
it { is_expected.to contain_service('nova-foo').that_requires(
|
|
['Package[nova-common]', 'Package[nova-foo]']
|
|
)}
|
|
end
|
|
end
|