28 Oct
2013
28 Oct
'13
20:00
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm testing the offline upgrade method (DVD) from 12.3 to 13.1, in a
vmplayer machine.
I've hit a strange problem: no network. Aparently there is a conflict
between the old network name, eth0, and the new, ens33.
I had a look at yast network module (yast says the name is eth0), then
rebooted. This is what the service status says now:
+++·······························
network.service - LSB: Configure network interfaces and set up routing
Loaded: loaded (/usr/lib/systemd/system/network.service; enabled)
Active: failed (Result: exit-code) since Tue 2013-10-29 00:37:31 CET; 1h 11min ago
Process: 902 ExecStart=/etc/init.d/network start (code=exited, status=7)
Oct 29 00:37:01 eleanor3 network[902]: Setting up network interfaces:
Oct 29 00:37:01 eleanor3 network[902]: lo
Oct 29 00:37:01 eleanor3 ifup[1186]: lo
Oct 29 00:37:01 eleanor3 ifup[1230]: lo
Oct 29 00:37:01 eleanor3 ifup[1233]: IP address: 127.0.0.1/8
Oct 29 00:37:01 eleanor3 network[902]: lo IP address: 127.0.0.1/8
Oct 29 00:37:01 eleanor3 ifup[1235]: Oct 29 00:37:01 eleanor3 network[902]: ..done
ens33 Startmode is 'manual' -> skipping
Oct 29 00:37:01 eleanor3 ifup[1301]: ens33 Startmode is 'manual' ->
skipping
Oct 29 00:37:01 eleanor3 network[902]: ..skippedWaiting for mandatory devices: eth0
Oct 29 00:37:31 eleanor3 network[902]: 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13
12 11 10 9 8 6 5 4 3 2 1 0
Oct 29 00:37:31 eleanor3 network[902]: eth0 No interface
found
Oct 29 00:37:31 eleanor3 network[902]: ..failedSetting up service network . . . . .
. . . . . . . ...failed
Oct 29 00:37:31 eleanor3 systemd[1]: network.service: control process exited, code=exited
status=7
Oct 29 00:37:31 eleanor3 systemd[1]: Failed to start LSB: Configure network interfaces and
set up routing.
Oct 29 00:37:31 eleanor3 systemd[1]: Unit network.service entered failed state.
·······························++-
How should this be handled?
If I try to delete the interface in YaST, and then add a new interface, it
still says the name is eth0.
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlJvCJsACgkQtTMYHG2NR9UDdQCeIehd/YSBlnAFRXZok2+1UREr
PM4An12cMm7q93fAsas1PrgqC3et14qJ
=CY5N
-----END PGP SIGNATURE-----
28 Oct
28 Oct
20:11
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday, 2013-10-29 at 02:00 +0100, Carlos E. R. wrote:
How should this be handled?
If I try to delete the interface in YaST, and then add a new interface, it
still says the name is eth0.
I found out.
YaST netowrk module displays one configure entry for eth0, and another,
unconfigured, entry for ens33.
I deleted the eth0 entry, and configured the ens33 entry, and netowrk wsa
functional.
Could YaST upgrade handle this better? Alternatively, this has to be
documented somewhere.
- --
Cheers,
Carlos E. R.
(from 12.3 x86_64 "Dartmouth" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlJvCzkACgkQtTMYHG2NR9WVsQCfR7Ddh2qW5Vr6JZaPc/6qLRUC
mboAnRAy4LHSBtQcoDCm00sw7F06P0ux
=uGle
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
6 Nov
6 Nov
18:03
New subject: [opensuse-factory] [13.1 RC1] [13.1 RC2] - upgrade test: no network device
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday, 2013-10-29 at 02:11 +0100, Carlos E. R. wrote:
On Tuesday, 2013-10-29 at 02:00 +0100, Carlos E. R.
wrote:
RC2 has the same problem.
- --
Cheers,
Carlos E. R.
(from 12.3 x86_64 "Dartmouth" at Telcontar)
How should this be handled?
If I try to delete the interface in YaST, and then add a new interface, it
still says the name is eth0.
I found out.
YaST netowrk module displays one configure entry for eth0, and another,
unconfigured, entry for ens33.
I deleted the eth0 entry, and configured the ens33 entry, and netowrk wsa
functional.
Could YaST upgrade handle this better? Alternatively, this has to be
documented somewhere. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlJ62OAACgkQtTMYHG2NR9UsyACdGXYwl190fHZboo4BTgo57A15
pAYAniidUyjUjeJpRjuZzWE0O5ArPf9f
=aV13
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
28 Oct
28 Oct
21:49
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
В Tue, 29 Oct 2013 02:00:11 +0100 (CET)
"Carlos E. R." <carlos.e.r(a)opensuse.org> пишет:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm testing the offline upgrade method (DVD) from 12.3 to 13.1, in a
vmplayer machine.
I've hit a strange problem: no network. Aparently there is a conflict
between the old network name, eth0, and the new, ens33.
I had a look at yast network module (yast says the name is eth0), then
rebooted. This is what the service status says now:
+++·······························
network.service - LSB: Configure network interfaces and set up routing
Loaded: loaded (/usr/lib/systemd/system/network.service; enabled)
Active: failed (Result: exit-code) since Tue 2013-10-29 00:37:31 CET; 1h 11min ago
Process: 902 ExecStart=/etc/init.d/network start (code=exited, status=7)
Oct 29 00:37:01 eleanor3 network[902]: Setting up network interfaces:
Oct 29 00:37:01 eleanor3 network[902]: lo
Oct 29 00:37:01 eleanor3 ifup[1186]: lo
Oct 29 00:37:01 eleanor3 ifup[1230]: lo
Oct 29 00:37:01 eleanor3 ifup[1233]: IP address: 127.0.0.1/8
Oct 29 00:37:01 eleanor3 network[902]: lo IP address: 127.0.0.1/8
Oct 29 00:37:01 eleanor3 ifup[1235]: Oct 29 00:37:01 eleanor3 network[902]: ..done
ens33 Startmode is 'manual' -> skipping
Oct 29 00:37:01 eleanor3 ifup[1301]: ens33 Startmode is 'manual' ->
skipping
Oct 29 00:37:01 eleanor3 network[902]: ..skippedWaiting for mandatory devices: eth0
Oct 29 00:37:31 eleanor3 network[902]: 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13
12 11 10 9 8 6 5 4 3 2 1 0
Oct 29 00:37:31 eleanor3 network[902]: eth0 No interface
found
Oct 29 00:37:31 eleanor3 network[902]: ..failedSetting up service network . . . . .
. . . . . . . ...failed
Oct 29 00:37:31 eleanor3 systemd[1]: network.service: control process exited, code=exited
status=7
Oct 29 00:37:31 eleanor3 systemd[1]: Failed to start LSB: Configure network interfaces
and set up routing.
Oct 29 00:37:31 eleanor3 systemd[1]: Unit network.service entered failed state.
·······························++-
How should this be handled?
If I try to delete the interface in YaST, and then add a new interface, it
still says the name is eth0.
Do you have /etc/udev/rules.d/70-persistent-net.rules? Does it match
your interfaces?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlJvIioACgkQR6LMutpd94znOACgudllqdg9Ynlvg/7Oz33YSfyq
0ZkAnivS0PJGSLs/CMJvqFlfPqANfkLr
=lIxX
-----END PGP SIGNATURE-----
N▀╖╡ФЛr╦⌡yИ ┼Z)z{.╠Гзrз+кК╖╡ФЛr╦⌡z┼^·к╛z┼ЮN┤(·ж°╤ь^ё ч╜И ┼Z)z{.╠Гзrз+кЙ0²ЙХ╔ИЛ╨г╗╝
29 Oct
29 Oct
07:22
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday, 2013-10-29 at 06:49 +0400, Andrey Borzenkov wrote:
Yes, zero bytes, dated today.
Did you see my second post? The issue was solved, but the cause is
unknown.
- --
Cheers,
Carlos E. R.
(from 12.3 x86_64 "Dartmouth" at Telcontar)
How should
this be handled?
If I try to delete the interface in YaST, and then add a new interface, it
still says the name is eth0.
Do you have /etc/udev/rules.d/70-persistent-net.rules? Does it match
your interfaces? -----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEUEARECAAYFAlJvqIYACgkQtTMYHG2NR9XIHwCghXC7fj+hRhMsINfp9kJRHxBa
OAQAl2NKVDhtbwTDBxQReI7P/ig9f2M=
=1hR5
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
11:19
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
В Tue, 29 Oct 2013 13:22:29 +0100 (CET)
"Carlos E. R." <robin.listas(a)telefonica.net> пишет:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday, 2013-10-29 at 06:49 +0400, Andrey Borzenkov wrote:
Yes, zero bytes, dated today.
Did you see my second post? The issue was solved,
If you say so ... for me the issue is that interface "lost" its name.
And it is definitely not solved :)
How
should this be handled?
If I try to delete the interface in YaST, and then add a new interface, it
still says the name is eth0.
Do you have /etc/udev/rules.d/70-persistent-net.rules? Does it match
your interfaces?
but
the cause is
unknown.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlJv3/QACgkQR6LMutpd94zmngCdE3ZxjiFnr/BJUz0jF+cP2GbY
m6IAoMYrnzKlW8NO/Pbj0dmk2RyMDVcr
=aOkn
-----END PGP SIGNATURE-----
N▀╖╡ФЛr╦⌡yИ ┼Z)z{.╠Гзrз+кК╖╡ФЛr╦⌡z┼^·к╛z┼ЮN┤(·ж°╤ь^ё ч╜И ┼Z)z{.╠Гзrз+кЙ0²ЙХ╔ИЛ╨г╗╝
18:54
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday, 2013-10-29 at 20:19 +0400, Andrey Borzenkov wrote:
If you say so ... for me the issue is that interface "lost" its name.
And it is definitely not solved :)
> but the cause is unknown.
The issue is solved for me, because I have network. If there is something
else you think I should do, please tell me.
- --
Cheers,
Carlos E. R.
(from 12.3 x86_64 "Dartmouth" at Telcontar)
Do you have /etc/udev/rules.d/70-persistent-net.rules?
Does it match
your interfaces?
Yes, zero bytes, dated today.
Did you see my second post? The issue was solved, -----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlJwStIACgkQtTMYHG2NR9XXfQCgiQ5zfZOKbIL8MrumwKu99udJ
ja4AoJSD/LSjA5XdtuqlIDHiz/FSvJjJ
=zu9n
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
28 Oct
28 Oct
22:21
On 10/28/2013 09:00 PM, Carlos E. R. pecked at the keyboard and wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm testing the offline upgrade method (DVD) from 12.3 to 13.1, in a
vmplayer machine.
I've hit a strange problem: no network. Aparently there is a conflict
between the old network name, eth0, and the new, ens33.
I had a look at yast network module (yast says the name is eth0), then
rebooted. This is what the service status says now:
+++·······························
network.service - LSB: Configure network interfaces and set up routing
Loaded: loaded (/usr/lib/systemd/system/network.service; enabled)
Active: failed (Result: exit-code) since Tue 2013-10-29 00:37:31
CET; 1h 11min ago
Process: 902 ExecStart=/etc/init.d/network start (code=exited, status=7)
Oct 29 00:37:01 eleanor3 network[902]: Setting up network interfaces:
Oct 29 00:37:01 eleanor3 network[902]: lo
Oct 29 00:37:01 eleanor3 ifup[1186]: lo
Oct 29 00:37:01 eleanor3 ifup[1230]: lo
Oct 29 00:37:01 eleanor3 ifup[1233]: IP address: 127.0.0.1/8
Oct 29 00:37:01 eleanor3 network[902]: lo IP address: 127.0.0.1/8
Oct 29 00:37:01 eleanor3 ifup[1235]: Oct 29 00:37:01 eleanor3
network[902]: ..done ens33 Startmode is 'manual' -> skipping
Oct 29 00:37:01 eleanor3 ifup[1301]: ens33 Startmode is 'manual' ->
skipping
Oct 29 00:37:01 eleanor3 network[902]: ..skippedWaiting for mandatory
devices: eth0
Oct 29 00:37:31 eleanor3 network[902]: 29 28 27 26 25 24 23 22 21 20 19
18 17 16 15 14 13 12 11 10 9 8 6 5 4 3 2 1 0
Oct 29 00:37:31 eleanor3 network[902]:
eth0 No interface found
Oct 29 00:37:31 eleanor3 network[902]: ..failedSetting up service
network . . . . . . . . . . . . ...failed
Oct 29 00:37:31 eleanor3 systemd[1]: network.service: control process
exited, code=exited status=7
Oct 29 00:37:31 eleanor3 systemd[1]: Failed to start LSB: Configure
network interfaces and set up routing.
Oct 29 00:37:31 eleanor3 systemd[1]: Unit network.service entered failed
state.
·······························++-
How should this be handled?
If I try to delete the interface in YaST, and then add a new interface,
it still says the name is eth0.
Another case of the devs not adhering to the notion that if it ain't
broke don't fix it. :-)
--
Ken Schneider
SuSe since Version 5.2, June 1998
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
29 Oct
29 Oct
11:31
El 29/10/13 00:21, Ken Schneider - openSUSE escribió:
Another case of the devs not adhering to the notion
that if it ain't
broke don't fix it. :-)
In this case, it was broken, in fact totally broken.
--
"Any real systematist (or scientist in general) has to be ready to heave
all that he or she has believed in, consider it crap, and move on, in
the face of new evidence. That is how we differ from clerics."
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
14:43
On 10/29/2013 12:31 PM, Cristian Rodríguez pecked at the keyboard and wrote:
El 29/10/13 00:21, Ken Schneider - openSUSE escribió:
So you're saying that no one could use theie ethernet cards when the
interface was called ethx. And here all this time I thought I was
connected to my network with my eth0 interface. I guess the joke was on
me. :-)
The fact is that it was /not/ broken but had issues with persistant
names when more then one interface was present.
--
Ken Schneider
SuSe since Version 5.2, June 1998
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Another case of the devs not adhering to the
notion that if it ain't
broke don't fix it. :-)
In this case, it was broken, in fact totally broken.
2874
days inactive
2883
days old
9 comments
5 participants
participants (5)
-
Andrey Borzenkov -
Carlos E. R. -
Carlos E. R. -
Cristian Rodríguez -
Ken Schneider - openSUSE