Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions bin/setup-policy-routes.sh
Original file line number Diff line number Diff line change
Expand Up @@ -64,8 +64,8 @@ start)
fi
done
debug "Starting configuration for $iface"
debug /lib/systemd/systemd-networkd-wait-online -i "$iface"
/lib/systemd/systemd-networkd-wait-online -i "$iface"
debug /lib/systemd/systemd-networkd-wait-online -i "$iface" --timeout=60
/lib/systemd/systemd-networkd-wait-online -i "$iface" --timeout=60
export EC2_IF_INITIAL_SETUP=1
do_setup
;;
Expand Down
3 changes: 2 additions & 1 deletion systemd/system/policy-routes@.service
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
[Unit]
Description=Set up policy routes for %I
StartLimitIntervalSec=10
After=systemd-networkd.service

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I am still not sure how this would affect the timing between policy-routes and and cloud-init.
Currently, it seems like policy-routes@i.service runs at the same time as systemd-networkd.service.
if we further delay this to after systemd-networkd.service then it could potentially execute networkctl reload during cloud-init which would break the instance. Requires more testing on our side.

StartLimitIntervalSec=60
StartLimitBurst=5
Wants=refresh-policy-routes@%i.timer
CollectMode=inactive-or-failed
Expand Down