Project

Profile

Help

Issue #7263

pulp_installer CI often fails to test more than 1 OS at a time

Added by mdepaulo@redhat.com about 1 year ago. Updated 10 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Category:
Installer
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.

Associated revisions

Revision b38ce47b View on GitHub
Added by Mike DePaulo about 1 year ago

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

Revision b38ce47b View on GitHub
Added by Mike DePaulo about 1 year ago

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

History

#1 Updated by pulpbot about 1 year ago

  • Status changed from NEW to POST

#3 Updated by Anonymous about 1 year ago

  • Status changed from POST to MODIFIED

#4 Updated by ttereshc 10 months ago

  • Sprint/Milestone set to 3.8.0

#5 Updated by ttereshc 10 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF