[sles-beta] Changing lan adapter names, get stuck rebooting

[Joe Doupnik]

Fredric,
     Good, let's see how matters develop in beta 3.
     Btw, I have read that citation you mentioned, and even repeated a 
clipping on this list as evidence of how wacko the new scheme has 
become. I cut through the excessive and defensive verbage of the systemd 
docs to get a solution done here, using YaST. Thus kudos once again to 
the YAST developers; none to the s-d folks.
     Throughout the systemd learning experience my goal has been to seek 
the clear and quickly used methods. The situation often is a server is 
ill, it must be fixed right now, services need to be restarted or 
revised by hand right now, and we need the big picture fully in mind to 
do this effectively, again right now. Similarly, building a server ought 
not be a half day or more exercise (without autoyast). There may be new 
ways of expressing things, but if we have to seriously fight the system 
to survive (which is the case at present) one suspects those systems 
will be replaced by more compliant ones, simply as a matter of site 
survival. Thus assistance from SUSE on decoding and domesticating what 
seems to be a real muddle in important places would be most appreciated.
     In its way this rough beginning has its benefits because we 
identify and clarify the nasty spots early enough for them to be 
smoothed out.
     Thanks and we do look forward to beta 3.
     Joe D.

On 19/03/2014 17:46, Frederic Crozat wrote:
> Le mercredi 19 mars 2014 à 17:37 +0000, Joe Doupnik a écrit :
>>       Likely probably many other people, I have no use for the current
>> opaquely generated lan adapter names. There is no obvious tie to the
>> hardware such as MAC address, in a readily visible fashion. Thus I used
>> YaST (text mode) to modify the name to eth0. Yes, it can be done. The
>> result was a conventional (at last) 70-persistent-net.rules item in
>> /etc/udev/rules.d. My IPtables filter thanked me for that.
>>       However, there is a dark side. Restarting the machine from power
>> off causes the boot process to get stuck in a wait loop for wicked,
>> saying "A start job is running for wicked managed network".
>>       Seven and a half minutes later... the system went beyond that point
>> and finished booting.
>>       There is no wireless or similar arrangement here. No Network
>> Manager. Just one Ethernet adapter in this ESXi virtual machine.
>>
>>       Problem two is to re-ask a question. Where are the systemd lan
>> adapter names defined? Those ems32 style things. I have not been able to
>> locate them. If found then perhaps reason could be brought to bear to
>> return to usable eth0 etc. Having ifcfg-eth0 with real values would be a
>> definite plus. The points at hand are clarity, easily located
>> configurations, flexibility in operations, but so far in my learning
>> process the systemd approach lacks each of these.
> Network renaming (allowing you to have eth0 instead of en0s3..) was
> broken in Beta2, this might explains why you were stuked.
>
> This will be fixed in Beta3 and for Beta4, we will probably ship a
> script to ease the creation of 70-persistent-net.rules based on MAC
> address or bus address of the adapter.
>
> For the documentation on the network precitable names, you can have a
> look at
> http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ as a initial step.
>