On 11/01/2016 01:58 AM, Ryan Harper wrote: > On Mon, Oct 31, 2016 at 11:44 PM, Robert Schweikert <[email protected]> > wrote: > >> On 10/31/2016 04:03 PM, Scott Moser wrote: >>> On Sat, 29 Oct 2016, Robert Schweikert wrote: >> I also dropped >> >> Before=basic.target >> >> in cloud-init.service as basic.target is needed by wicked.service (the >> magic to configure the network) and thus one cannot have >> >> After=wicked.service >> Before=basic.target >> >> together as that forms another loop. >> > > wicked.service has this > > [Unit] > Description=wicked managed network interfaces > Wants=network.target wickedd.service wickedd-nanny.service > After=network-pre.target wickedd.service wickedd-nanny.service > Before=network-online.target network.target > > I suspect this is the real loop; cloud-init.service wants to run before > networking is up; it > currently requires 'networking.service' on Ubuntu which is the ifupdown > target; it's not clear > to me that we're getting the equivalent target on SUSE; and likely wicked > is wanting to run > *after* basic.target which makes that loop and it gets dropped > (cloud-init.service).
Yes, wicked runs after basic.target # systemctl list-dependencies wicked.service wicked.service ● ├─system.slice ● ├─wickedd-nanny.service ● ├─wickedd.service ● ├─basic.target ● │ ├─alsa-restore.service ● │ ├─alsa-state.service ● │ ├─console-kit-log-system-start.service ● │ ├─paths.target ● │ ├─slices.target ● │ │ ├─-.slice ● │ │ └─system.slice ● │ ├─sockets.target ● │ │ ├─avahi-daemon.socket ● │ │ ├─cups.socket ● │ │ ├─dbus.socket ● │ │ ├─iscsid.socket ● │ │ ├─pcscd.socket ● │ │ ├─rpcbind.socket ● │ │ ├─systemd-initctl.socket ● │ │ ├─systemd-journald.socket ● │ │ ├─systemd-shutdownd.socket ● │ │ ├─systemd-udevd-control.socket ● │ │ └─systemd-udevd-kernel.socket ● │ ├─sysinit.target ● │ │ ├─apparmor.service ● │ │ ├─dev-hugepages.mount ● │ │ ├─dev-mqueue.mount ● │ │ ├─kmod-static-nodes.service ● │ │ ├─plymouth-read-write.service ● │ │ ├─plymouth-start.service ● │ │ ├─proc-sys-fs-binfmt_misc.automount ● │ │ ├─sys-fs-fuse-connections.mount ● │ │ ├─sys-kernel-config.mount ● │ │ ├─sys-kernel-debug.mount ● │ │ ├─systemd-ask-password-console.path ● │ │ ├─systemd-binfmt.service ● │ │ ├─systemd-firstboot.service ● │ │ ├─systemd-journal-flush.service ● │ │ ├─systemd-journald.service ● │ │ ├─systemd-modules-load.service ● │ │ ├─systemd-random-seed.service ● │ │ ├─systemd-sysctl.service ● │ │ ├─systemd-tmpfiles-setup-dev.service ● │ │ ├─systemd-tmpfiles-setup.service ● │ │ ├─systemd-udev-root-symlink.service ● │ │ ├─systemd-udev-trigger.service ● │ │ ├─systemd-udevd.service ● │ │ ├─systemd-update-utmp.service ● │ │ ├─systemd-vconsole-setup.service ● │ │ ├─cryptsetup.target ● │ │ ├─local-fs.target ● │ │ │ ├─-.mount ● │ │ │ ├─boot.mount ● │ │ │ ├─home.mount ● │ │ │ ├─opt.mount ● │ │ │ ├─systemd-fsck-root.service ● │ │ │ ├─systemd-remount-fs.service ● │ │ │ ├─var-lock.mount ● │ │ │ ├─var-run.mount ● │ │ │ ├─vm_images.mount ● │ │ │ └─work.mount ● │ │ └─swap.target ● │ │ ├─dev-disk-by\x2did-ata\x2dADATA_SP900_7D3720000812\x2dpart2.swap ● │ │ └─dev-sda2.swap ● │ └─timers.target ● │ └─systemd-tmpfiles-clean.timer ● └─network.target and for that matter wickedd.service as well as wickedd-nanny.service also run after basic.target. > > Could you send: > > systemctl list-dependencies network-online.target network-online.target ● ├─NetworkManager-wait-online.service ● └─wicked.service > systemctl list-dependencies network.target network.target Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX [email protected] IRC: robjo
signature.asc
Description: OpenPGP digital signature
-- Mailing list: https://launchpad.net/~cloud-init Post to : [email protected] Unsubscribe : https://launchpad.net/~cloud-init More help : https://help.launchpad.net/ListHelp
