Actions
Issue #7263
closed
pulp_installer CI often fails to test more than 1 OS at a time
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Quarter:
Description
The problem appears to be due to the run_once in pulp_database_config.
This makes since for a clustered install, but not for 3 independent pulp servers, like our molecule CI does to test multiple OS's.
So far only source scenarios seem to be failing, but it's still incorrect.
Added by Mike DePaulo over 4 years ago
Added by Mike DePaulo over 4 years ago
Revision b38ce47b | View on GitHub
Problem: pulp_installer CI often fails to test more than 1 OS at a time
Solution: Run pulp_database_config's block of task for each OS, disabling the run_once. Via a private variable.
Updated by pulpbot over 4 years ago
- Status changed from NEW to POST
Updated by pulpbot over 4 years ago
Updated by Anonymous over 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset ansible-pulp|b38ce47b81aa06818432aaba2e914248b582a8ac.
Updated by ttereshc about 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Problem: pulp_installer CI often fails to test more than 1 OS at a time
Solution: Run pulp_database_config's block of task for each OS, disabling the run_once. Via a private variable.
fixes: #7263 https://pulp.plan.io/issues/7263