Actions
Task #4326
closed
Test source install with Molecule
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:
Sprint 47
Quarter:
Description
We will need to create a new scenario to test source installs so we can also test the pulp3-devel role.
molecule tests run with its own playbook `molecule/default/playbook.yml`
Add pulp3-devel to this list, and fix any errors that come up.
Updated by amacdona@redhat.com over 5 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to amacdona@redhat.com
- Sprint set to Sprint 47
Updated by amacdona@redhat.com over 5 years ago
- Subject changed from Add pulp3-devel to molecule playbook so it is tested. to Test source install with Molecule
- Description updated (diff)
Updated by CodeHeeler about 5 years ago
- Tracker changed from Issue to Task
- % Done set to 0
Added by amacdona@redhat.com about 5 years ago
Added by amacdona@redhat.com about 5 years ago
Revision 7a29983d | View on GitHub
Create source install molecule test scenario
Strange idempotence issue with postgresql role when screen or redhat-lsb-core is installed in pulp3-devel. I've removed these packages, but it is not clear why they would cause idempotence problems with the creation of the postgres socket at /var/run/posgresql.
fixes #4326
Updated by amacdona@redhat.com about 5 years ago
- Status changed from ASSIGNED to MODIFIED
- % Done changed from 0 to 100
Applied in changeset ansible-pulp3|7a29983d0679a8c96cb711812a80300778f3f903.
Updated by bmbouter over 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Updated by bmbouter almost 4 years ago
- Category set to Installer - Moved to GitHub issues
- Tags deleted (
Pulp 3 installer)
Actions
.
Create source install molecule test scenario
Strange idempotence issue with postgresql role when screen or redhat-lsb-core is installed in pulp3-devel. I've removed these packages, but it is not clear why they would cause idempotence problems with the creation of the postgres socket at /var/run/posgresql.
fixes #4326