I have a 'test-cirros' script (see below) that provides 'nocloud' data that runs ping.
By the time /etc/rc3.d/S98-cirros-status executes, the ipv4 network is not up, and cirros-status will show the debug information.
Networking should block, so that user-data or rc.local can assume if everything is functioning correctly, network will be up. In the past this was guaranteed, if networking was not up at that point, then something was wrong. As it is now trying again in a second or two would work.
I have a 'test-cirros' script (see below) that provides 'nocloud' data that runs ping. By the time /etc/rc3.d/S98-cirros-status executes, the ipv4 network is not up, and cirros-status will show the debug information.
Networking should block, so that user-data or rc.local can assume if everything is functioning correctly, network will be up. In the past this was guaranteed, if networking was not up at that point, then something was wrong. As it is now trying again in a second or two would work.
Script is
test-cirros
below and log file attached (cirros-0.6.0-test.log).