http://bugzilla.opensuse.org/show_bug.cgi?id=1182227 http://bugzilla.opensuse.org/show_bug.cgi?id=1182227#c2 --- Comment #2 from syuta hashimoto --- Created attachment 846103 --> http://bugzilla.opensuse.org/attachment.cgi?id=846103&action=edit rdsosreport -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182227 Anthony Rabbito changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hello@anthonyrabbito.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182227 http://bugzilla.opensuse.org/show_bug.cgi?id=1182227#c7 John Voudouris changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jvoudouris@pm.me --- Comment #7 from John Voudouris --- I'm also experiencing this bug exactly as described here. I would love to add useful information if anyone has any request or way for me to be helpful. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182227 http://bugzilla.opensuse.org/show_bug.cgi?id=1182227#c10 Enrico Belleri changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |idesmi@protonmail.com --- Comment #10 from Enrico Belleri --- I can reproduce this bug, network as a dependency in Combustion fails to be satisfied. There is no problem in activating a network interface from the emergency mode instead. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182227 http://bugzilla.opensuse.org/show_bug.cgi?id=1182227#c12 --- Comment #12 from Enrico Belleri --- (In reply to Anthony Rabbito from comment #11)

omit the [# combustion: network] and 'manually' up the interface via combustion script? That would be an interesting workaround.

Tried. The interface does get `up` during the Combustion process, but commands after `ip link set [���] up` that make use on an internet connection still fail. I'm not knowledgeable in the boot sequence (at all), so doing this might have been pointless from the start. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182227 http://bugzilla.opensuse.org/show_bug.cgi?id=1182227#c22 Andrei Borzenkov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com --- Comment #22 from Andrei Borzenkov --- (In reply to Thomas Blume from comment #21)

With ip=dhcp it still fails, I'm trying to find a workaround from within dracut.

wicked client (equivalent of ifup) requires per-interface configuration. That is how wicked is designed. Wicked dracut parser is simply wrong. The dracut legacy module basically implements hotplug - it runs ifup script from within udev rule; ifup parses command line and picks up either interface-specific config or generic one. It also waits for at least one interface to come up. In addition its ifup can be called directly, is using the same parser and works whether called from within udev rule or manually. To add feature parity to wicked module there are two possibilities 1. Command line parser should generate policy instead of configuration; this policy will be directly loaded into backend. This will move hotplug handling into wicked. It won't allow running "wicked ifup" manually if needed. 2. Implement same wrapper for wicked ifup as legacy module does - generate wicked configuration for specific interface and call wicked with it. It need not really be xml, could be good ole ifcfg file. And add udev rules to call this wrapper. And of cause name it ifup so it could be called explicitly. And add same waiting for network being up. Considering that a) there is exactly zero documentation for wicked policies and b) running ifup/down manually still requires explicit configuration - I'd say 1 is pretty much unrealistic. For 2 one could actually simply copy legacy scripts and only add ifcfg generation. But then it begs the question - why wicked at all? What exactly wicked module does that legacy module does not that justifies all those efforts? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182227 http://bugzilla.opensuse.org/show_bug.cgi?id=1182227#c38 --- Comment #38 from OBSbugzilla Bot --- This is an autogenerated message for OBS integration: This bug (1182227) was mentioned in https://build.opensuse.org/request/show/929130 Factory / wicked -- You are receiving this mail because: You are on the CC list for the bug.