systemd: Add patch to split networkd tmpfiles into a separate file #2832
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue number:
Related to #2741 and #2449
Description of changes:
It appears I missed some files when I made the
networkd
subpackage insystemd
. These tmpfiles should only be included if thenetworkd
subpackage is included. An upstream patch moves these entries into a separate file for situations such as this, so we include that patch.The offending journal entries that tipped us off to this mistake looked like:
Testing done:
aws-k8s-1.24
variant and ensure no messages referring tosystemd-network
's tmpfiles show up in the journal.aws-dev
variant with thesystemd-networkd
image-feature enabled (and add a dependency onconsole-getty.service
inpreconfigured.target
since I knew early boot services will fail). Observe thesystemd-networkd
tmpfiles being created properly and no other networkd-related issues in the journal:Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.