Use service anchor to ensure API is up
... instead of the individual service resource which can be named
differently according to service_name.
Closes-Bug: #1949658
Change-Id: I847b88710578818f6c792d1603e02759072a9d25
(cherry picked from commit 614d16329a
)
This commit is contained in:
parent
eb2c462cbc
commit
3241ff122a
|
@ -264,7 +264,7 @@ running as a standalone service, or httpd for being run by a httpd server")
|
|||
# lint:endignore
|
||||
}
|
||||
}
|
||||
create_resources('openstacklib::service_validation', $validation_cmd, {'subscribe' => 'Service[cinder-api]'})
|
||||
create_resources('openstacklib::service_validation', $validation_cmd, {'subscribe' => 'Anchor[cinder::service::end]'})
|
||||
}
|
||||
|
||||
}
|
||||
|
|
|
@ -126,7 +126,7 @@ describe 'cinder::api' do
|
|||
end
|
||||
it { is_expected.to contain_openstacklib__service_validation('cinder-api').with(
|
||||
:command => 'cinder --os-auth-url http://localhost:5000 --os-project-name services --os-username cinder --os-password foo list',
|
||||
:subscribe => 'Service[cinder-api]',
|
||||
:subscribe => 'Anchor[cinder::service::end]',
|
||||
)}
|
||||
end
|
||||
|
||||
|
|
Loading…
Reference in New Issue