Phased updates can cause build regressions on Ubuntu Jammy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 55
- Forks
- 39
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 7
Description
Bug Report Track
Phased updates are available on apt since Ubuntu 21.04. This has caused build regressions events on our buildfarms at ci.ros2.org
Phased updates knowledge base:
https://wiki.ubuntu.com/PhasedUpdates
Events
June 7th, first time appearance,
Linux CI was totally broken for that day
Internal discussion: https://osrf.slack.com/archives/C5UEHBHD2/p1654626755337259
https://people.canonical.com/~ubuntu-archive/phased-updates.html
Fix for the problem: https://github.com/ros2/ci/pull/667
June 21st, second time appearance,
Linux CI was partially affected, the problem "fixed itself" and there was no CI downtime because the nodes were using the ccache.
This wasn't expected to occur because with the previously attached PR we opted out of phased updates.
https://osrf.slack.com/archives/C5UEHBHD2/p1655789723051689
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the phased-updates knowledge base and the referenced fix in ros2/ci#667, then compare it with the June 21 event described here. Done means identifying why phased updates still affected the Linux build farm and preventing recurrence without CI regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ubuntu
- Domain
- ci-cd, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100