Consider delaying fetches until NetworkManager is connected
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
Feature Request
Environment
Any
Desired Feature
If networking is provided by NetworkManager, we could use NM's dbus API to wait for connectivity before attempting to fetch. This shouldn't change the ultimate outcome, but would address a recurring source of confusion for users: Ignition trying to fetch things before the network is up.
If we don't trust NetworkManager's connectivity logic, we could time out after ~60 seconds and fetch anyway.
On platforms that don't have NetworkManager, we could skip this check after the dbus request fails, or disable it via a compile-time option.
Contributor guide
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
No files or tests are named. Start by locating the fetch path and investigating how NetworkManager connectivity could be queried through its D-Bus API, including behavior when NetworkManager is unavailable. Done means fetches wait for connectivity when supported, fall back after about 60 seconds, and preserve the existing outcome on other platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100