Actions
Issue #7526
closedPublish is operational when the only change in config is "force_full" setting
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
2.21.4
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
To reproduce:
- Publish a repo override_config {"force_full":true}
- Then publish without override config or with {"force_full":false}.
The second publish will be operational.
Updated by ggainey almost 4 years ago
Updated by ggainey almost 4 years ago
- Status changed from NEW to POST
- Assignee set to pmoravec@redhat.com
Added by pmoravec@redhat.com almost 4 years ago
Updated by pmoravec@redhat.com almost 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulp|49a87aef4c411b94648d31ff17deee866f6d33c8.
Added by pmoravec@redhat.com almost 4 years ago
Revision 8c394e24 | View on GitHub
Ignore force_full in config override when deciding publish to be operational
Comparing config override to decide (non)operational publish can safely ignore force_full option; this option itself determines the non-operational publish independently.
closes #7526 https://pulp.plan.io/issues/7526
Signed-off-by: Pavel Moravec pmoravec@redhat.com (cherry picked from commit 49a87aef4c411b94648d31ff17deee866f6d33c8)
Updated by ggainey almost 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Ignore force_full in config override when deciding publish to be operational
Comparing config override to decide (non)operational publish can safely ignore force_full option; this option itself determines the non-operational publish independently.
closes #7526 https://pulp.plan.io/issues/7526
Signed-off-by: Pavel Moravec pmoravec@redhat.com