Actions
Story #7259
closedStory #5762: [Epic] CI Improvements
Story #6584: As a pulp_installer CI user, I see verification that pulp functions and was installed correctly at the end
As a user, the pulp_installer will verify that the Pulp Services are up & listening
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
The installer sub-team agreed that we will port these tests (meant for molecule and written in ruby inspec) to ansible tasks: https://github.com/pulp/pulp_installer/blob/master/molecule/scenario_resources/tests/test_default.rb
Presumably, there will be a new verification role at the end of the installer.
Upon further investigation:
- The ansible URI and assert modules should probably be used.
- Counting the redirects may not be possible with the ansible URI module.
- This should be run on the webserver node, and querying against it.
- Some tests like checking the services won't make since on the webserver node, since services pulpcore-api wouldn't run on a separate webserver.
- We're going to need to add variables, at least for a complete and thorough check (beyond what the current ruby ones do.) The checking role will need to be aware of how many workers there are for example.
Actions
Verify if Pulp Services are up & listening
https://pulp.plan.io/issues/7259 closes #7259