OBS runner creates conflicts in the origin repo, then waits forever for them
Affected images versions
- not relevant (explain why) infrastructure bug
The tests on tests/dash seem to periodically fail with errors that there is a source conflict. This should...not actually be possible, because when the runner adds a new commit, it doesn't set keeplink, so the links should be broken in the first place. There is a chance it may be tied to #114, as the branched package has a whopping 196 revisions. Either way, the runner also shouldn't hang forever when a conflict occurs.
Reproducibility
- always
-
✅ often, but not always -
✅ rarely
Impact of bug
How severe is the bug? Does it render an image unbootable? Is it a security issue? Does it prevent specific applications from working? What is the impact? Does this bug affect a critical component? Does it cause something else to not work? How often is the bug likely to be found by a user? For example, every boot or once per year?
Attachments
Add further information about the environment in the form of attachments here. Attach plain text files from log output (from
journalctl,systemctl, …) or long backtraces as attached files. If adding comments on the log is required create a new snippet and add the link to it here.
Screenshots and videos are usually useful for graphic issues.
Root cause
describe in one line what caused the issue to give a hint to product teams whether they may be impacted or not
Outcomes
TBD
Management data
This section is for management only, it should be the last one in the description.
/cc @andrunko @em @Balasubramanian @sudarshan @wlozano
Phabricator link: https://phabricator.apertis.org/T10335