On Wed, 6 May 2015 21:18, Hendrik Woltersdorf wrote:
Am 06.05.2015 um 21:08 schrieb Yamaban:
On Wed, 6 May 2015 20:26, Olaf Hering wrote:
On Tue, May 05, Ludwig Nussel wrote:
Changed packages: ...
For me network is broken, tested only booting a dom0. 'systemctl start wicked.service' started the network as expected. My guess: there are wrong Before=/After= lines in various .services:
root@optiplex:~ # journalctl -b | grep delete [snip error-list]
I think the subject should read 20150505, thats why me /etc/issue has. But perhaps I run the to-be-released snapshot?!
[snip repo-list]
A few hints to solve that.
As you have included your repo-list, and seeing "/network:/wicked:/master/" there, this rises the question, where are your "wicked" packages from?
either with "rpm -qi {package}", see "Vendor" field, or with zypper se -s wicked
Please check for these packages: libwicked wicked wicked-service sysconfig sysconfig-netconfig
Either with "rpm -qi {package}", see "Vendor" field, or with "zypper se -s wicked sysconfig", see "repo" field.
For these Packages it should be either "factory-oss" or "obs-network_wicked_master" but not mixed in the installation.
Next question: where points "network.service" to? systemctl status network.service5~
If you want to use wicked, please disable NetworkManager, and enable wicked after that.
systemctl disable NetworkManager.service systemctl enable wicked.service systemctl daemon-reload
After that wicked should work as expected again after the next reboot.
Hi,
I've got the same problem with NetworkManager:
Mai 06 21:10:29 linux-yb52 systemd[1]: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start
and less repositories:
# | Alias | Name | Enabled | Refresh --+--------------------+-----------------------------+---------+-------- 1 | Packman | Packman | Yes | Yes 2 | http-....-55ced6b4 | X11:RemoteDesktop | No | No 3 | openSUSE-20150225-0| openSUSE-20150225-0 | No | No 4 | ownclowd-Desktop | ownclowd-Desktop | Yes | Yes 5 | repo-debug | openSUSE-Tumbleweed-Debug | No | Yes 6 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | Yes | Yes 7 | repo-oss | openSUSE-Tumbleweed-Oss | Yes | Yes 8 | repo-source | openSUSE-Tumbleweed-Source | No | Yes 9 | repo-update | openSUSE-Tumbleweed-Update | Yes | Yes
Well, the main question is likely the same as above, it boils down to: What network.service do you REALLY want to use? If the answer is wicked, either uninstall NetworkManager, or disable it. === systemctl disable NetworkManager.service systemctl enable wicked.service systemctl daemon-reload If the answer is NetworkManager, either uninstall wicked, or disable it. === systemctl disable wicked.service systemctl enable NetworkManager.service systemctl daemon-reload Something did go wrong during the "zypper dup" for both of you. BUT something already did go wrong before that. Just WHY install BOTH, NetworkManager AND wicked ?? Yes, I know, the choice of Cholera and Black Death, both have their problems, but those that have both installed should be knowlegde able enough to handle the needed "systemctl" steps to switch back and forth, the same you would have to do switching between two http-daemons for port 80. There is ONE resource, the network interface. One OR the other handler can be active. NEVER both. - Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org