https://bugzilla.suse.com/show_bug.cgi?id=1226204
https://bugzilla.suse.com/show_bug.cgi?id=1226204#c1
Knut Alejandro Anderssen González changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kanderssen@suse.com
--- Comment #1 from Knut Alejandro Anderssen González ---
The main problem we have in the installation is that there is no a full
differentiation of the running network config and the target system network
config, that is, if you modify the network configuration during the
installation it will change your current one copying it to the target system or
translating it to Network manager at the end of the installation unless you
select "None" backend as you asked for in the past.
If there is no changes in the network configuration it should work fine, but if
you mess the network configuration during the installation it will be hard to
fix, so, the recommendation is to configure it by cmdline or with the interface
and then just select a "Non"e backend. That should be enough.
Will try to taboo that packages and reproduce the problem but It should be
enough selecting none as the backend to be used.
--
You are receiving this mail because:
You are on the CC list for the bug.
