Skip to content

core: refresh unit cache when building a transaction if UNIT_NOT_FOUND#16371

Merged
keszybz merged 1 commit intosystemd:masterfrom
bluca:unit_cache_transaction_refresh
Jul 7, 2020
Merged

core: refresh unit cache when building a transaction if UNIT_NOT_FOUND#16371
keszybz merged 1 commit intosystemd:masterfrom
bluca:unit_cache_transaction_refresh

Conversation

@bluca
Copy link
Member

@bluca bluca commented Jul 6, 2020

When a command asks to load a unit directly and it is in state
UNIT_NOT_FOUND, and the cache is outdated, we refresh it and
attempto to load again.
Use the same logic when building up a transaction and a dependency in
UNIT_NOT_FOUND state is encountered.
Update the unit test to exercise this code path.

When a command asks to load a unit directly and it is in state
UNIT_NOT_FOUND, and the cache is outdated, we refresh it and
attempto to load again.
Use the same logic when building up a transaction and a dependency in
UNIT_NOT_FOUND state is encountered.
Update the unit test to exercise this code path.
@keszybz
Copy link
Member

keszybz commented Jul 7, 2020

bionic-i386 timed out in su ..., unrelated.

@keszybz keszybz merged commit cda6677 into systemd:master Jul 7, 2020
@bluca bluca deleted the unit_cache_transaction_refresh branch July 30, 2020 18:39
slyon added a commit to canonical/netplan that referenced this pull request Aug 4, 2020
This way it can be started on first boot by cloud-init via 'systemctl start netplan.target'

This partly fixes (LP: #1870346), but needs fixed to cloud-init and
systemd v246 (systemd/systemd#16371) as well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants