Chronyd is stopped in Alpine after re-context (updateconf)

[xorel]

Once we switched Alpine images from installation to nocloud source Alpine images, the chronyd service is included.

In re-contextualization (onevm updateconf) we call reload_netowrk which calls stop_network + start_network, after which chronyd service remains stopped. Unlike we would call servce networking restart.

localhost:~# service networking stop && service networking start
 * Stopping chronyd ...                                                        [ ok ]
 * Stopping networking ...
 *   lo ...                                                                    [ ok ]
 *   eth0 ...                                                                  [ ok ]
 * Starting networking ...
 *   lo ...                                                                    [ ok ]
 *   eth0 ...     

vs

localhost:~# service networking restart
 * Stopping chronyd ...                                                        [ ok ]
 * Stopping networking ...
 *   lo ...                                                                    [ ok ]
 *   eth0 ...                                                                  [ ok ]
 * Starting networking ...
 *   lo ...                                                                    [ ok ]
 *   eth0 ...                                                                  [ ok ]
localhost:~#  * Starting chronyd ...

To fix that we can execute service networking restart in reload_network, but we should find different fix (or test if issue is still present) for for this commit

commit 484e43659641b4c9a5fd39b5bfea2531043757e7
Author: Vlastimil Holer <[email protected]>
Date:   Wed Sep 22 16:15:42 2021 +0200

    F #227, #86: Workaround sporadic IPv6 SLAAC privacy address on Ubuntus