On Fri, Sep 15, 2017 at 1:18 PM, Josef Reidinger <jreidinger@suse.cz> wrote:

V Fri, 15 Sep 2017 12:36:39 +0200 Roger Oberholtzer <roger.oberholtzer@gmail.com> napsáno:

...

Hi,

(I'm new here. I have looked for answers to the following, but seem not to know where to find them. Please be gentle...)

I am building an openSUSE Leap 42.3 OEM image that, when installed, runs YaST firstboot stuff. I have done this for quite a few openSUSE releases without a problem. But I am having difficulty with doing so in Leap 42.3. I have discussed my issues with the KIWI folk, and they are of the opinion the the issue is YaST. Or, my use of it.

These are the kind of issues I am encountering (not in order of importance):

1. It insists on being in character mode. I think I have all the X11/QT stuff installed. So I do not know why this happens.

2. It starts out by saying that /etc/ntp.conf cannot be written. Initially I did not have ntp installed. But then it failed immediately. Why it is trying to do anything with NTP before, say, I have configured the network, is a mystery.

3. It fails to run inst_hostname. I get an error and it says to let the YaST folk know. Then it dies.

4. At one point it shows a screen (so fast that I almost do not see what it says) that says Analyzing System. Then it immediately shuts down the system. Not a crash. But a proper shutdown.

So I am not sure if the problem is my firstboot script, or some missing packages.

Where to start? I can provide my firstboot script. Or information on installed packages.

I think it make sense to start with providing y2logs from that firstboot run, so we can check what happens. Also opening bug report can simplify communication and make it more persistent.

I'm not sure these are bugs. Probably something I am doing incorrectly. If I encounter a bug I will of course report it. I've never tried reporting myself as a bug. :) I have finally been able to access the disk after all this. I see this in y2log: The very first line is: 2017-09-15 10:55:29 <1> linux(19818) [Ruby] bin/y2start:16 y2base called with ["firstboot", "--arg", "firstboot", "ncurses"] I do not know where the ncurses is coming from. Later on I see: 2017-09-15 11:05:01 <1> linux(19818) [Ruby] modules/Misc.rb:188 .sysconfig.firstboot.LICENSE_REFUSAL_ACTION: 'halt' 2017-09-15 11:05:01 <1> linux(19818) [Ruby] clients/firstboot.rb:95 Firstboot aborted, LICENSE_REFUSAL_ACTION: halt 2017-09-15 11:05:01 <1> linux(19818) [Ruby] clients/firstboot.rb:101 Halting the system... I have no idea why. The only thing the firstboot has related to a license is: <module> <enabled config:type="boolean">false</enabled> <label>License Agreement</label> <name>firstboot_license</name> </module> So it is not enabled. Perhaps that is not the way to do this? Where is there documentation on firstboot.xml? I mean the possible contents. I just have an old one I have been using. But I do not know if things have changed. -- Roger Oberholtzer -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org

...

The very first line is:

2017-09-15 10:55:29 <1> linux(19818) [Ruby] bin/y2start:16 y2base called with ["firstboot", "--arg", "firstboot", "ncurses"]

check y2start log, it should print why it pick ncurses as UI

I see this in y2start.log: |-- Starting X11/VNC based session... Stage [call]: Starting prequalification checks... Stage [call]: =================================== |-- No testX binary installed -> Medium Qt disabled |-- No SSH daemon running -> Medium SSH disabled |-- No testX binary installed -> Medium VNC disabled Stage [call]: Evaluate medium selection... Stage [call]: ============================ Stage [call]: Check selected medium... Stage [call]: ======================== |-- Wished medium is: QT |-- Medium Qt not available, falling back to ncurses |-- Selected medium is: NCURSES testX? What's that? X11 and Qt are installed. As is yast2-control-center-qt. I have no idea what might be missing.

...

2017-09-15 11:05:01 <1> linux(19818) [Ruby] modules/Misc.rb:188 .sysconfig.firstboot.LICENSE_REFUSAL_ACTION: 'halt' 2017-09-15 11:05:01 <1> linux(19818) [Ruby] clients/firstboot.rb:95 Firstboot aborted, LICENSE_REFUSAL_ACTION: halt 2017-09-15 11:05:01 <1> linux(19818) [Ruby] clients/firstboot.rb:101 Halting the system...

I have no idea why. The only thing the firstboot has related to a license is:

<module> <enabled config:type="boolean">false</enabled> <label>License Agreement</label> <name>firstboot_license</name> </module>

So it is not enabled. Perhaps that is not the way to do this?

Well, so what happen here? sysconfig for first boot is set to halt if license is not approved and license dialog is disabled, so you cannot approve it. So it halt.

I will change that. This is different behavior than before (i.e., 13.1.... I know...) . I had this clause when it worked. I am happy to make changes as needed. But I don't know where to find documentation. I see lots on making my own YaST modules and all. But not on using existing ones in firstboot. Like I say, I do not think there are bugs in YaST. Just in my attempted use... -- Roger Oberholtzer -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org

...

This is different behavior than before (i.e., 13.1.... I know...) . I had this clause when it worked. I am happy to make changes as needed. But I don't know where to find documentation. I see lots on making my own YaST modules and all. But not on using existing ones in firstboot.

I just took the /etc/YaST2/firstboot.xml from a standard Leap 42.3 install and made modifications in that. It is what I was looking for. I do see some differences. -- Roger Oberholtzer -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org