There's no obvious error in the initial comment. Directory /var/log/YaST2/ (or even /mnt/var/log/YaST2/) must have existed (the initial report contains part of it).

We appreciate you have reported this bug but we can't do anything without the requested logs files. However, the initial comment neither contains any error nor any piece of information that would say what happened.

Can you provide more logs, and/or is the issue reproducible?

Hello,

I checked /var/log/YaST2/ folder when I was reporting this bug.
There was no log file.

I was installing OpenSuSE in virtual machine (Virtual Box 2.0.6) on x86 arch.
RAM: 512MB, Video: 32MB, CD-ROM connected to ISO image.
As installation has not been completed - I can't load OpenSuSE from that virtual machine (VDI disk)

My impression is that during install process disk space on VDI disk exhausted, and as /var/log/ is located on the same disk, installer could not write log file - and halted.
I am question here if installed should check for available disk space when initiates installation?
And when it is finalizing installation?

I was also surprised that "Install to hard disk" didn't have option to select which packages should be installed (and which - not installed to hdd, like additional localization options, drivers for not present hardware, etc.) 
This could potentially fill all the disk space on vdi disk.
But correct behavior in this case should be inform user that not enough disk space is available, and then giv eoption of removing some not necessary packages.

Best regards,
Vadim Plessky

P.S. I can reproiduce this issue if necessary.
Installing OpenSuSE once more to the same virtual machine would reproduce this bug. I can also provide screenshot if needed.

Yes, please, try to reproduce that bug and check what you've written above (such as not enough disk space).

Directory /var/log/YaST2/ is not located on the disk, it's in memory (Ctrl+Alt+F2 takes you to console).

Directory /mnt/var/log/YaST2/ is on the disk and the file existed while running the test. See, === Checking YaST log file /mnt//var/log/YaST2//y2log... === is in the initial comment.

Could you, please, also describe your virtual machine configuration more precisely? For instance disk sizes, Desktop selected for installation... Just how to reproduce the bug.

Thanks

Created attachment 261370 [details]
/var/log/YaST2   log file for failed OpenSuSE 11.1 install

/var/log/YaST2   log file for failed OpenSuSE 11.1 install

ok, here is additional info.

Virtual machine:
VirtualBox OSE (virtualbox-2.0.6-1mdv2009.0)
Host system: Mandriva Linux 2009.0 x86, KDE 4.1.3
Physical RAM: 1GB
VM RAM: 512MB
VM Videocard: 32MB
VM Disk: 2GB
OpenSuSE ISO mounted to Virtual CD-ROM drive

I just tried to restart that virtual machine rebooting again from OpenSuSE ISO
disk - but start of the system hanged.
Than I connected that VM to Fedora 10 ISO image, and restarted system with
Fedora 10 (KDE).
Here is complete system (Fedora 10 running in the same VirtualBox 2.0.6):
http://www.smolts.org/client/show/pub_9983f8b1-4384-4933-a50d-0ab62e8f91b6
Thanks to Smolt for great possibility to share system details online! :-)

So, "hardware" is the same as for OpenSuSE 11.1 install.

Than I connected to formatted partition and opened /media/disk/var/log/YaST2 on
disk formatted by OpenSuSE installer.
It is attached to this message.

Here is relevant info from /var/log/YaST2/y2lg:
...
2008-12-19 03:16:33 <1> linux(3915) [YCP] Progress.ycp:380 Progress::New(Copying the Live Image to Hard Disk, 100, ["Evaluate filesystems to copy", "Copy root filesystem", "Copy additional filesystems"])
2008-12-19 03:16:33 <1> linux(3915) [YCP] Progress.ycp:469 No progress icons defined
2008-12-19 03:16:34 <1> linux(3915) [YCP] clients/inst_live_doit.ycp:25 Executing 
	for LINK in `find /mnt -xdev -type l` ; do
	    stat -c "%N" $LINK |grep livecd >/dev/null 2>/dev/null && echo $LINK;
	done; exit 0
2008-12-19 03:16:34 <1> linux(3915) [YCP] clients/inst_live_doit.ycp:27 Result: $["exit":0, "stderr":"", "stdout":""]
2008-12-19 03:16:34 <1> linux(3915) [YCP] clients/inst_live_doit.ycp:36 Symlinks to resolve: []
2008-12-19 03:16:34 <1> linux(3915) [YCP] clients/inst_live_doit.ycp:55 Resolved symlinks: $[]
2008-12-19 03:16:34 <1> linux(3915) [YCP] ImageInstallation.ycp:865 Executing du -x -B 1048576 -s /
2008-12-19 03:17:28 <1> linux(3915) [YCP] ImageInstallation.ycp:867 Output: $["exit":0, "stderr":"", "stdout":"1657\t/\n"]
2008-12-19 03:17:28 <1> linux(3915) [YCP] ImageInstallation.ycp:884 Executing mkfifo /tmp/YaST2-03915-mQPDUa/system_clone_fifo_1 ;
	 mkfifo /tmp/YaST2-03915-mQPDUa/system_clone_fifo_2 ;
	 tar -C / --numeric-owner -cSf /tmp/YaST2-03915-mQPDUa/system_clone_fifo_1 --one-file-system . &
	 dd bs=1048576 if=/tmp/YaST2-03915-mQPDUa/system_clone_fifo_1 of=/tmp/YaST2-03915-mQPDUa/system_clone_fifo_2 >&2 &
	 jobs -l >&2;
	 tar -C /mnt --numeric-owner -xSf /tmp/YaST2-03915-mQPDUa/system_clone_fifo_2
2008-12-19 03:17:28 <1> linux(3915) [liby2util++] ExternalProgram.cc(start_program):160 Executing '/bin/sh' '-c' 'mkfifo /tmp/YaST2-03915-mQPDUa/system_clone_fifo_1 ;
2008-12-19 03:17:28 <1> linux(3915) [liby2util++] ExternalProgram.cc(start_program):160 	 mkfifo /tmp/YaST2-03915-mQPDUa/system_clone_fifo_2 ;
2008-12-19 03:17:28 <1> linux(3915) [liby2util++] ExternalProgram.cc(start_program):160 	 tar -C / --numeric-owner -cSf /tmp/YaST2-03915-mQPDUa/system_clone_fifo_1 --one-file-system . &
2008-12-19 03:17:28 <1> linux(3915) [liby2util++] ExternalProgram.cc(start_program):160 	 dd bs=1048576 if=/tmp/YaST2-03915-mQPDUa/system_clone_fifo_1 of=/tmp/YaST2-03915-mQPDUa/system_clone_fifo_2 >&2 &
2008-12-19 03:17:28 <1> linux(3915) [liby2util++] ExternalProgram.cc(start_program):160 	 jobs -l >&2;
2008-12-19 03:17:28 <1> linux(3915) [liby2util++] ExternalProgram.cc(start_program):163 	 tar -C /mnt --numeric-owner -xSf /tmp/YaST2-03915-mQPDUa/system_clone_fifo_2'
2008-12-19 03:17:28 <1> linux(3915) [YCP] ImageInstallation.ycp:901 DD's pid: 4671
2008-12-19 03:40:50 <1> linux(11229) [liby2] genericfrontend.cc(main):608 Launched YaST2 component 'scr' 'stdio' 'scr'
2008-12-19 03:40:50 <1> linux(11229) [ui-component] YUIComponentCreator.cc(createInternal):113 Creating UI component for ""
2008-12-19 03:40:50 <1> linux(11229) [liby2] genericfrontend.cc(main):762 YAST_IS_RUNNING is yes
2008-12-19 03:40:51 <3> linux(11229) [agent-system] SystemAgent.cc(SystemAgent):122 Cannot create temporary directory /tmp/YaST2-11229-xNxm3I:No space left on device
2008-12-19 03:40:51 <3> linux(11229) [liby2] genericfrontend.cc(signal_handler):196 got signal 6 at YCP file :2
2008-12-19 03:40:51 <3> linux(11229) [liby2] genericfrontend.cc(log_stored_debug):120 Liberating suppressed debugging messages:
2008-12-19 03:40:51 <3> linux(11229) [liby2] genericfrontend.cc(log_stored_debug):122 End of suppressed debugging messages
2008-12-19 03:40:51 <3> linux(11229) [liby2] genericfrontend.cc(log_backtrace):144 Back trace:

   Frame  0: /usr/lib/liby2.so.2  log_backtrace()
   Frame  1: /usr/lib/liby2.so.2  signal_handler(int)
   Frame  2: [0xffffe400]
   Frame  3: [0xffffe422]
   Frame  4: /lib/libc.so.6(gsignal+0x50) [0xb79b9990]
   Frame  5: /lib/libc.so.6(abort+0x188) [0xb79bb2c8]
   Frame  6: /usr/lib/libstdc++.so.6  __gnu_cxx::__verbose_terminate_handler()
   Frame  7: /usr/lib/libstdc++.so.6 [0xb7bde445]
   Frame  8: /usr/lib/libstdc++.so.6 [0xb7bde482]
   Frame  9: /usr/lib/libstdc++.so.6 [0xb7bde5ba]
   Frame 10: /usr/lib/YaST2/plugin/libpy2ag_system.so.2  SystemAgent::SystemAgent()
   Frame 11: /usr/lib/YaST2/plugin/libpy2ag_system.so.2  Y2AgentComp<SystemAgent>::getSCRAgent()
   Frame 12: /usr/lib/liby2.so.2  Y2PluginComponent::getSCRAgent()
   Frame 13: /usr/lib/YaST2/plugin/libpy2scr.so.2  SCRSubAgent::mount(SCRAgent*)
   Frame 14: /usr/lib/YaST2/plugin/libpy2scr.so.2  ScriptingAgent::executeSubagentCommand(char const*, YCPPath const&, YCPValue const&, YCPValue const&)
   Frame 15: /usr/lib/YaST2/plugin/libpy2scr.so.2  ScriptingAgent::Read(YCPPath const&, YCPValue const&, YCPValue const&)
   Frame 16: /usr/lib/YaST2/plugin/libpy2scr.so.2  Y2AgentComp<ScriptingAgent>::evaluate(YCPValue const&)
   Frame 17: /usr/lib/liby2.so.2  Y2StdioComponent::doActualWork(YCPList const&, Y2Component*)
   Frame 18: /usr/lib/liby2.so.2(main+0x11e5) [0xb7eda2c5]
   Frame 19: /lib/libc.so.6(__libc_start_main+0xe5) [0xb79a5705]
   Frame 20: scr [0x8048841]

== End of back trace ===
2008-12-19 04:11:03 <1> linux(11841) [liby2] genericfrontend.cc(main):608 Launched YaST2 component 'scr' 'stdio' 'scr'
2008-12-19 04:11:04 <1> linux(11841) [ui-component] YUIComponentCreator.cc(createInternal):113 Creating UI component for ""
2008-12-19 04:11:04 <1> linux(11841) [liby2] genericfrontend.cc(main):762 YAST_IS_RUNNING is yes
2008-12-19 04:11:04 <3> linux(11841) [agent-system] SystemAgent.cc(SystemAgent):122 Cannot create temporary directory /tmp/YaST2-11841-rwcjru:No space left on device
2008-12-19 04:11:04 <3> linux(11841) [liby2] genericfrontend.cc(signal_handler):196 got signal 6 at YCP file :1
2008-12-19 04:11:04 <3> linux(11841) [liby2] genericfrontend.cc(log_stored_debug):120 Liberating suppressed debugging messages:
2008-12-19 04:11:04 <3> linux(11841) [liby2] genericfrontend.cc(log_stored_debug):122 End of suppressed debugging messages
2008-12-19 04:11:04 <3> linux(11841) [liby2] genericfrontend.cc(log_backtrace):14

One more file from /media/disk/var/log/YaST2

[root@localhost YaST2]# cat disk_sda
Device: /dev/sda
Major: 8
Minor: 0
Range: 16
Cylinder: 261
Head: 255
Sector: 63
Label: msdos
MaxPrimary: 4
ExtPossible: 1
MaxLogical: 15
SizeK: 2097152

I managed to install OpenSuSE 11.1 in VirtualBox (2.0.6) with virtual hard disk of 2.6GB

To maximize disk space for Root partition (in default/recommended setup), I used LVM-based disk partitioning

linux-tgl3:/home/vadim # fdisk -l

Disk /dev/sda: 2791 MB, 2791309312 bytes
255 heads, 63 sectors/track, 339 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0004830d

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1           9       72261   83  Linux
/dev/sda2              10         339     2650725   8e  Linux LVM

Disk /dev/dm-0: 2650 MB, 2650800128 bytes
255 heads, 63 sectors/track, 322 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 62 MB, 62914560 bytes
255 heads, 63 sectors/track, 7 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-1 doesn't contain a valid partition table

Created attachment 262305 [details]
Successfull install with 2.6GB virtual disk (LVM) - in VirtualBox


I repeated installation with a bigger disk - and succeeded installation with 2.6GB disk and default disk partition for LVM (swap file 60MB, /boot 70MB, the rest is Root & Home)

There was no problem as reported in my bug report with such disk size.
Install was again in VirtualBox on x86 arch.
Therefor, I suggest bug described above was caused by insufficient disk space.
YAST should warn user that disk space is exhausted, and make necessary steps to avoid system installation failure.

From comment #6: 

SystemAgent.cc(SystemAgent):122 Cannot create temporary directory
/tmp/YaST2-11841-rwcjru:No space left on device


This does not sound good. Please make sure there is sufficient disk space and try again.

Comment #9 indicates it really is about no space.

Lukas, we might want to check in the switch debug also free space on devices.

- Added test for checking free space when SCR switch fails
  (bnc #460477).
- yast2-installation-2.18.3

Jirko, maybe we could check for available disk space better in the
installation proposal. This is a live_CD_install.

Feel free to close as FIXED or reassign back.

I considered it several times, will close it as FIXED for now, because of following reasons:

- the default partitioning proposal suggests more disk space than is necessary, thus default installation should work well

- there is no suitable component of the proposal (no package manager)

- there is no information about size of individual directories (consider e.g. separate /usr partition)

In the future, it would be nice to enhance the live installer with possibility to install additional packages - then such check will be (nearly) for free.