Skip to content

Comments

ignition: keep network around when umounting#99

Merged
tormath1 merged 1 commit intoflatcar-masterfrom
tormath1/ignition
Sep 16, 2024
Merged

ignition: keep network around when umounting#99
tormath1 merged 1 commit intoflatcar-masterfrom
tormath1/ignition

Conversation

@tormath1
Copy link
Contributor

This keeps network in the umounting Ignition stage as Equinix Metal needs to POST a status update to Equinix Metal timeline at each stage.

This solves: flatcar/Flatcar#1536

Testing done

@tormath1 tormath1 self-assigned this Sep 12, 2024
@tormath1 tormath1 requested a review from a team September 12, 2024 13:50
Copy link
Contributor

@chewi chewi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was worried this might involve something hacky. This is beautiful!

On some providers (like Equinix Metal), there is a network dependency
for the umount stage, network must be still around when ExecStop is
executed.

Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
@tormath1
Copy link
Contributor Author

Force pushed to sync with final upstream commit - it's only a comment diff.

@tormath1 tormath1 merged commit f3c80fb into flatcar-master Sep 16, 2024
@tormath1 tormath1 deleted the tormath1/ignition branch September 16, 2024 07:36
@tormath1
Copy link
Contributor Author

cherry-picked to: flatcar-3510-backport

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants