Actions
Bug #23111
closedXenial repos created by chacra not being recreated when using --force option for same url
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When debian repos are updated by chacra using the --force flag, and the url is the same as an existing repo the binaries will not be updated.
For example consider the following repo:
If a jenkins build is triggered and you are using FORCE and the same sha1 under V2.5-stable then the binaries will not be updated.
The only directory that will be updated is the db directory.
Updated by David Galloway over 2 years ago
This could be accomplished by adding an if statement to each job that uses chacractl and run chacractl repo recreate if FORCE is used.
Updated by David Galloway over 2 years ago
Err wait. Ali, why would the binaries change if you're pushing the same package based on the same sha1?
Updated by David Galloway over 2 years ago
- Status changed from New to Won't Fix
- Assignee set to David Galloway
<amaredia> dgalloway: I saw you bumped this: https://tracker.ceph.com/issues/23111#change-200486 <amaredia> since it was 3 years ago I can't recall the exact circumstances why this issue was raised <amaredia> your second point makes sense <amaredia> and since it hasn't been an issue since it was opened, I say close it <dgalloway> Thank you for following up amaredia
Actions