[opensuse-factory] wicked problem on fresh 13.2 install - bugzilla not helpful because corresponding bug is locked
Hello everyone, I have a (proplably known and fixed) problem with a fresh install of openSUSE 13.2 and wicked. After boot, I have no network and # systemctl status wicked wicked: /org/opensuse/Network/Interface.getManagedObjects failed. Server responds: wicked: org.freedesktop.DBus.Error.ServiceUnknown: The name org.opensuse.Network was not provided by any .service files wicked: Couldn't refresh list of active network interfaces Googling this gives me BNC#904776 at https://bugzilla.opensuse.org/show_bug.cgi?id=904776 which I do not get access to. So what to do? How is a user supposed to fix a problem, if the only source of information (i.e. the "open"SUSE bugzilla) is locked down? Is there a public source of help for this bug? Or could someone unlock it? Thanks and best regards, JB -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 19 May 2015 16:56:18 +0200 Joschi Brauchle <joschibrauchle@gmx.de> wrote:
Hello everyone,
I have a (proplably known and fixed) problem with a fresh install of openSUSE 13.2 and wicked. After boot, I have no network and
# systemctl status wicked wicked: /org/opensuse/Network/Interface.getManagedObjects failed. Server responds: wicked: org.freedesktop.DBus.Error.ServiceUnknown: The name org.opensuse.Network was not provided by any .service files wicked: Couldn't refresh list of active network interfaces
Googling this gives me BNC#904776 at https://bugzilla.opensuse.org/show_bug.cgi?id=904776 which I do not get access to.
So what to do? How is a user supposed to fix a problem, if the only source of information (i.e. the "open"SUSE bugzilla) is locked down?
Is there a public source of help for this bug? Or could someone unlock it?
Thanks and best regards, JB
Hi Joschi, I see you have two choices here: 1) open a new bug (according to the instructions from: https://en.opensuse.org/openSUSE:Bugreport_wicked) and provide logs from your case. If it's the same bug we will comment it there. (Recommended) 2) try to restart wickedd service with: systemctl restart wickedd and afterwards call systemctl restart network or call ifup all This should bring your network up and then you could perform an update via zypper up. The wicked version which contains a fix for bsc#904776 is 0.6.14. But I recommend you go for the latest one 0.6.18. You can get it with 13.2 update or from: https://build.opensuse.org/package/show/network:wicked:factory/wicked HTH -- Best Regards, Pawel Wieczorkiewicz <pwieczorkiewicz@suse.de>, Linux System Developer SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 / 90409 Nürnberg / Germany / Phone: +49-911-740 53 - 613 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 05/19/2015 06:09 PM, Pawel Wieczorkiewicz wrote:
On Tue, 19 May 2015 16:56:18 +0200 Joschi Brauchle <joschibrauchle@gmx.de> wrote:
Hello everyone,
I have a (proplably known and fixed) problem with a fresh install of openSUSE 13.2 and wicked. After boot, I have no network and
# systemctl status wicked wicked: /org/opensuse/Network/Interface.getManagedObjects failed. Server responds: wicked: org.freedesktop.DBus.Error.ServiceUnknown: The name org.opensuse.Network was not provided by any .service files wicked: Couldn't refresh list of active network interfaces
Googling this gives me BNC#904776 at https://bugzilla.opensuse.org/show_bug.cgi?id=904776 which I do not get access to.
So what to do? How is a user supposed to fix a problem, if the only source of information (i.e. the "open"SUSE bugzilla) is locked down?
Is there a public source of help for this bug? Or could someone unlock it?
Thanks and best regards, JB Hi Joschi,
I see you have two choices here: 1) open a new bug (according to the instructions from: https://en.opensuse.org/openSUSE:Bugreport_wicked) and provide logs from your case. If it's the same bug we will comment it there. (Recommended)
2) try to restart wickedd service with: systemctl restart wickedd and afterwards call systemctl restart network or call ifup all This should bring your network up and then you could perform an update via zypper up.
The wicked version which contains a fix for bsc#904776 is 0.6.14. But I recommend you go for the latest one 0.6.18. You can get it with 13.2 update or from: https://build.opensuse.org/package/show/network:wicked:factory/wicked
HTH
Hi Pavel, the problem with wicked appears in stage2 of an fairly minimal autoyast installation. Stage1 completed successfully with all update repos added, hence wicked is the latest version 0.6.18 available for openSUSE 13.2. See my bugreport here https://bugzilla.opensuse.org/show_bug.cgi?id=931710 Thanks for your help. Best regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 20 May 2015 17:40:31 +0200 Joschi Brauchle <joschibrauchle@gmx.de> wrote:
Hi Pavel,
the problem with wicked appears in stage2 of an fairly minimal autoyast installation. Stage1 completed successfully with all update repos added, hence wicked is the latest version 0.6.18 available for openSUSE 13.2.
See my bugreport here https://bugzilla.opensuse.org/show_bug.cgi?id=931710
It looks like a dup of already existing one (marked already) and also systemd dependencies are involved. Thanks, we will take a look. -- Best Regards, Pawel Wieczorkiewicz <pwieczorkiewicz@suse.de>, Linux System Developer SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 / 90409 Nürnberg / Germany / Phone: +49-911-740 53 - 613 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Joschi Brauchle -
Pawel Wieczorkiewicz