[yast-devel] Question to SLE12-SP1 mode=installation stage=continue
Hi, I know in SLE12 there is no installation in stage=continue. But for the product SLE12-SP1-SAP we need to start a yast2 client immediately after reboot the system. For this reason I've inserted the following lines into the control.xml: <workflow> <defaults> <archs>all</archs> </defaults> <label>Preparation</label> <mode>installation</mode> <stage>continue</stage> <modules config:type="list"> <module> <label>SAP Setup</label> <name>sap</name> </module> </modules> </workflow> It works fine and the inst_sap.rb will be executed. But the network was not started the network cards where not activated. When I insert netprobe into the workflow befor sap the network cards will be activated but not confiugred. When I check the network status by "systemctl status network" the result is: wicked.service - wicked managed network interfaces Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled) Active: failed (Result: exit-code) since Fri 2015-08-07 09:47:43 CEST; 5min ago Process: 3173 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=1/FAILURE) Main PID: 3173 (code=exited, status=1/FAILURE) Aug 07 09:47:43 linux wicked[3173]: /org/opensuse/Network/Interface.getManagedObjects failed. Server responds: Aug 07 09:47:43 linux wicked[3173]: org.freedesktop.DBus.Error.ServiceUnknown: The name org.opensuse.Network was not provided by any .service files Aug 07 09:47:43 linux wicked[3173]: Couldn't refresh list of active network interfaces In both cases when I try to start the network on a console by "systemctl start network" this has no effect. Do you have any hint for me? -- Peter Varkoly Sr. Developer SUSE Linux Enterprise Applications SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 7.8.2015 v 10:10 Peter Varkoly napsal(a):
Um, why do you need to run it _after_ reboot? Could you integrate it directly into the installation workflow to the first stage? (Note: you will need a DUD on the SLE12-SP1-SAP medium for adding a new YaST client...)
It works fine and the inst_sap.rb will be executed. But the network was not started the network cards where not activated.
The problem is that the YaST framework still allows running the second stage (it is needed for AutoYaST) but it should not be used in the old way because the clients were modified to run in the first stage. That's probably why the network setup does not work as expected...
Do you have any hint for me?
Use yast2-firstboot, that's been designed for setting up the system after boot. Or alternatively move your client to the first stage if possible. HTH -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 7.8.2015 v 10:10 Peter Varkoly napsal(a):
Um, why do you need to run it _after_ reboot? Could you integrate it directly into the installation workflow to the first stage? (Note: you will need a DUD on the SLE12-SP1-SAP medium for adding a new YaST client...)
It works fine and the inst_sap.rb will be executed. But the network was not started the network cards where not activated.
The problem is that the YaST framework still allows running the second stage (it is needed for AutoYaST) but it should not be used in the old way because the clients were modified to run in the first stage. That's probably why the network setup does not work as expected...
Do you have any hint for me?
Use yast2-firstboot, that's been designed for setting up the system after boot. Or alternatively move your client to the first stage if possible. HTH -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (2)
-
Ladislav Slezak -
Peter Varkoly