Bug 1124911

changing component to installation, but there is not much information here

That's not much to go by.

Please describe exactly what you did and what happened. If the machine hangs
during hardware probing this is in most cases a kernel driver issue.

Check the kernel messages on console 3 for anything unusual.

Created attachment 796995 [details]
screenshot where installation hangs.

I had opensuse 42.3 and wanted to update to tumbleweed.
Same is if i try new installation. 
I have hp pavilion laptop. 

Installation proceeds until Preparation-->System Analysis-->Probe Hard disc, 
where it hangs at 40%. 

ctrl alt f3 shosw nothing special 
BTRFS device fsid...
BTRFS info device : has skinny extends 
                    disk space caching enabled

ctl alt f4 seems not ok. 
Last ok is 
mv /download/file.0008 -> /license.tar.gz

but then loading file /var/adm/mount/autoinst.xml -> /download/file_0008 
error 37: Couldn't open file ... (ignored)

Then the same for certain other files... last of them driveruptdate 
and finally 

starting setsid -wc inst_steup yast 

where it hangs.

correction: of course it is setsid -wc inst_setup yast

Created attachment 799471 [details]
Tumbleweed NET install looking for nonexistent files

This error occurs on the DVD install when selecting to update online repositories and on the NET installer, period. On the DVD install it reports that it can't open the string of files in the screenshot, all at /var/adm/mount. On the NET install side it comes up with a 404 file not found. I don't know if this means that a repository is missing files on the server or not.

It's essentially impossible to install Tumbleweed from the NET installer right now and impossible on DVD if you want to update during install. The weird thing is that on rare occasion it seems to work, suggesting that something is screwy (technical term) on the server end. I've reproduced this not only on my hardware but in VirtualBox as well.

This isn't a Leap to Tumbleweed bug; this is a general, readily reproducible Tumbleweed installer bug.

I don't know how the installer mounts its files or I'd check right now to see if there are missing files on the DVD disk. Actually let me check the NET install....

OK here's the problem... it's clearly trying to access files that simply don't exist. Look at this screenshot...

It's looking for files in https://download.opensuse.org/tumbleweed/repo/oss that simply aren't there - autoinst.xml, control.xml, license.tar.gz, into.txt, part.info, README.BETA, driverupdate. It says "ignored" for all but the last. Are any of these critical problems?

OK, older install disks that work also get those missing file errors. The difference is that they don't get the setsid error. I'm back to not understanding enough to know what's going on.

>The process group ID of any process equals the PID of the calling process. Thus, 
>in particular, setsid() fails if the calling process is already a process group 
>leader.

Hot dang I found it! :-)

It's Ruby that's going crazy. There's a brief flicker before it halts the installation. Using VirtualBox and the pause key combo I managed to freeze the screen as it's reporting the error message!

I hope my new attachment is useful.

Created attachment 799472 [details]
Ruby error reported as Tumbleweed install crashes

Created attachment 799848 [details]
Yast2 log file

Removing the needinfo flag, since Joseph Mitzen managed to reproduce it and provide the missing information.

I've been told that this issue may have been related to the libcurl4 bug that was causing zypper segfaults. I've downloaded the newest ISO (March 12) with the updated libcurl and saw no signs of the installer problem through two installs in VirtualBox. 

This may have solved the problem.

(In reply to Joseph Mitzen from comment #13)
> I've been told that this issue may have been related to the libcurl4 bug
> that was causing zypper segfaults. I've downloaded the newest ISO (March 12)
> with the updated libcurl and saw no signs of the installer problem through
> two installs in VirtualBox. 
> 
> This may have solved the problem.

Good to know. Ernst, can you please also try again with the newest ISO to verify if we can close this as FIXED?

I tried the newest iso. 
Stalls at the same place probing at 40%. 
Difference is that on console 2 I observe 
the message could not create lock on 

/var/lib.rmp/.rpm.lock

I removed that file and retried. 
Still no success. Same message. 
Strange enough, now this file disappeared. 
Hm. 

I try to add an attachment...

Created attachment 800297 [details]
output on console 2

Are you installing to a system with other copies of OpenSUSE installed? Are those working correctly? Does the OpenSUSE Leap ISO give the same problem?

*** Bug 1128907 has been marked as a duplicate of this bug. ***

Adjusting priority and severity according to the current findings.

I was not able to reproduce this. I tried, 

* Latest openSUSE Tumbleweed (openSUSE-Tumbleweed-DVD-x86_64-Snapshot20190327-Media.iso) -> installation succeed.
* Latest NET installer (openSUSE-Tumbleweed-NET-x86_64-Snapshot20190327-Media.iso) -> installation succeed.
* Install openSUSE Leap 42.3 -> then -> update to openSUSE Tumbleweed using the NET installer mentioned above -> upgrade succeed.


Ernst, please, could you bring us more information. See, for example, comment#17 (quoted below)


(In reply to Joseph Mitzen from comment #17)
> Are you installing to a system with other copies of OpenSUSE installed? Are
> those working correctly? Does the OpenSUSE Leap ISO give the same problem?


Thanks in advance.

(In reply to Joseph Mitzen from comment #7)
> OK here's the problem... it's clearly trying to access files that simply
> don't exist. Look at this screenshot...
> 
> It's looking for files in https://download.opensuse.org/tumbleweed/repo/oss
> that simply aren't there - autoinst.xml, control.xml, license.tar.gz,
> into.txt, part.info, README.BETA, driverupdate. It says "ignored" for all
> but the last. Are any of these critical problems?

Just for the record - this is indeed harmless. The installer tries to download
optional files. These files do not exist, but it's not a problem at all.
If they existed, installer would just behave differently. Nothing else.

(In reply to Joseph Mitzen from comment #11)
> Created attachment 799848 [details]
> Yast2 log file

These attached logs contain this:
[zypp] MediaCurl.cc(MediaCurl):577 MediaCurl::MediaCurl(http://sfo-korg-mirror.kernel.org/opensuse/tumbleweed/repo/oss/repodata/d59f7...
[zypp++] MediaCurl.cc(setupEasy):857 Proxy: not explicitly set
[zypp++] MediaCurl.cc(setupEasy):858 Proxy: libcurl may look into the environment
[zypp] ZYppFactory.cc(sigsegvHandler):55 Error: signal 11
[zypp] ZYppFactory.cc(sigsegvHandler):55 [hd]: (-3) /usr/lib64/libzypp.so.1709 : zypp::dumpBacktrace(std::ostream&)+0x39 [0x7f2363448539]
[zypp] ZYppFactory.cc(sigsegvHandler):55 [hd]: (-2) /usr/lib64/libzypp.so.1709 : +0x393c7b [0x7f2363403c7b]
[zypp] ZYppFactory.cc(sigsegvHandler):55 [hd]: (-1) /lib64/libc.so.6 : +0x3be10 [0x7f237927be10]
[zypp] ZYppFactory.cc(sigsegvHandler):55 vvvvvvvvvv----------------------------------------
[zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (0) /usr/lib64/libcurl.so.4 : +0x3a5e1 [0x7f2362e2a5e1]

Looks like what you say in comment #13: zypp/libzypp issue with libcurl

(In reply to Ernst Reissner from comment #15)
> I tried the newest iso. 
> Stalls at the same place probing at 40%. 
> /var/lib.rmp/.rpm.lock

Looks like completely different problem, or maybe a consequent one after
libzypp/libcurl has been fixed.

Anyway, we need new logs, please.

The bug is currently being handled by David.

On the other hand, we are still waiting for info requested in comment #20.

(In reply to David Diaz from comment #20)
> I was not able to reproduce this. I tried, 
> 
> * Latest openSUSE Tumbleweed
> (openSUSE-Tumbleweed-DVD-x86_64-Snapshot20190327-Media.iso) -> installation
> succeed.
> * Latest NET installer
> (openSUSE-Tumbleweed-NET-x86_64-Snapshot20190327-Media.iso) -> installation
> succeed.
> * Install openSUSE Leap 42.3 -> then -> update to openSUSE Tumbleweed using
> the NET installer mentioned above -> upgrade succeed.
> 
> 
> Ernst, please, could you bring us more information. See, for example,
> comment#17 (quoted below)
> 
> 
> (In reply to Joseph Mitzen from comment #17)
> > Are you installing to a system with other copies of OpenSUSE installed? Are
> > those working correctly? Does the OpenSUSE Leap ISO give the same problem?
> 
> 
> Thanks in advance.

I tried again. 
I had another problem seemingly wrong label on my partitions. 
Now the failure has gone!

As regards me, we can close that bug. It disappeared. 
I suspect i had an additional problem with labels of my partitions... 
could this be? 
all were windows.