|
Bugzilla – Full Text Bug Listing |
| Summary: | Leap 42.2 RC2 says internal ruby error on install | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Carlos Robinson <carlos.e.r> |
| Component: | Installation | Assignee: | Josef Reidinger <jreidinger> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | astieger, dimstar, jreidinger, maint-coord, maintenance, mrmazda, sknorr |
| Version: | Leap 42.2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | |||
| Bug Blocks: | 1009123, 1009124, 1013623, 1014196, 1014233 | ||
| Attachments: |
yast logs
save_y2logs.tgz after successfully completing "partitioning" step |
||
thanks for report. I found where is problem. In general when set default mount by to label, there is a bug, which try to use disk label. I prepare fix, but as it is part of installer, I worry it is useless as maintenance update. Dominique - do we have any known issues for Leap 42.2? fix for TW is in review https://github.com/yast/yast-bootloader/pull/377 (In reply to Josef Reidinger from comment #1) > thanks for report. I found where is problem. In general when set default > mount by to label, there is a bug, which try to use disk label. I prepare > fix, but as it is part of installer, I worry it is useless as maintenance > update. > > Dominique - do we have any known issues for Leap 42.2? With GM done, all that's left that can be done us document it in the Release Notes. Please work together with sknorr on a paragraph describing the workaround As GM is already out I suggest to add paragraph to release notes like: - Installer contain problem with using default mount by set to "label". In such case installation report error and do not continue. As workaround please use other option and if needed, then change it on running system. maintenance - as this affects also running system, I think it make sense to also release maintenance update. Affected products are Leap 42.2 and SLE12 SP2. For openSUSE Leap 42.2, yast2-bootloader is a fork. Please submit into openSUSE:Maintenance. (In reply to Andreas Stieger from comment #6) > For openSUSE Leap 42.2, yast2-bootloader is a fork. Please submit into > openSUSE:Maintenance. fork from SP2? that is wrong, it should be now unified, we plan to unify versions in Leap and in SP2. Only reason why it diverge is earlier release of SP2 where we need some final fixes in Leap before GM. (In reply to Josef Reidinger from comment #7) > (In reply to Andreas Stieger from comment #6) > > For openSUSE Leap 42.2, yast2-bootloader is a fork. Please submit into > > openSUSE:Maintenance. > > fork from SP2? that is wrong See osc rdiff SUSE:SLE-12-SP2:Update/yast2-bootloader openSUSE:Leap:42.2:Update/yast2-bootloader I merely indicated what the current situation is. > it should be now unified, we plan to unify > versions in Leap and in SP2. Only reason why it diverge is earlier release > of SP2 where we need some final fixes in Leap before GM. Sure we can do that. If you want this fixed in 42.2 first, please submit into openSUSE:Maintenance. Created attachment 701750 [details]
save_y2logs.tgz after successfully completing "partitioning" step
Using the 9 Nov installation kernel and initrd and HTTP, and by partitioning and formatting 100% in advance, I was able to set default mount-by to by-label, and / mount point in fstab to by-label, and proceed all the way through create partition setup to clock and time zone without any crash. At that point I saved logs via vtty2 and exited installation by CAD.
https://github.com/openSUSE/release-notes-openSUSE/commit/3c450b8d773dc111bee7fee19d6ea4987882e805 Not sure what information is requested from me. A maintenance update for yast2-bootloader from SLE 12 SP2 can be taken into Leap 42.2 when release. Submit into openSUSE:Maintenance if you want the fix independent from SLE 12 SP2. fix for bootloader is in place. maitenance update to SP2 created and also submitted to TW Stefan - do you want to keep it open to track release notes? openSUSE release notes are done (available online, but not packaged yet). However, lets wait with closing that bug until the enterprise products have been properly noted too. Resolving fixed SUSE-RU-2016:3167-1: An update that has four recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1000629,1004229,1004921,1009493 CVE References: Sources used: SUSE Linux Enterprise Server for Raspberry Pi 12-SP2 (src): yast2-bootloader-3.1.206-28.3.1 SUSE Linux Enterprise Server 12-SP2 (src): yast2-bootloader-3.1.206-28.3.1 SUSE Linux Enterprise Desktop 12-SP2 (src): yast2-bootloader-3.1.206-28.3.1 openSUSE-RU-2016:3235-1: An update that has 7 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1009123,1009275,1009493,1010575,1014686,995062,998663 CVE References: Sources used: openSUSE Leap 42.2 (src): release-notes-openSUSE-42.2.20161212-3.1 SUSE-RU-2016:3264-1: An update that has 6 recommended fixes can now be installed. Category: recommended (low) Bug References: 1009081,1009493,1012794,1013623,1015550,995577 CVE References: Sources used: SUSE Linux Enterprise Server for Raspberry Pi 12-SP2 (src): release-notes-sles-12.2.20161221-5.5.1 SUSE Linux Enterprise Server 12-SP2 (src): release-notes-sles-12.2.20161221-5.5.1 SUSE-RU-2016:3292-1: An update that has three recommended fixes can now be installed. Category: recommended (low) Bug References: 1009493,1014233,995577 CVE References: Sources used: SUSE Linux Enterprise Workstation Extension 12-SP2 (src): release-notes-sled-12.2.20161207-18.3.1 SUSE Linux Enterprise Desktop 12-SP2 (src): release-notes-sled-12.2.20161207-18.3.1 |
Created attachment 701453 [details] yast logs I was attempting to install RC2 on my laptop test partition. I did the partition setup, advanced to next step. Phase "analyzing your system". Can't reach the point to display the proposal. Popup - I have a photo, will post on request; meanwhile, hand copied here: YaST2 Error Internal error. Please report a bug report with logs. Details: Unknown udev device /dev/disk/by-label/msdos. Caller: /usr/share/YaST2/lib/bootloader/udev_mapping.rb:33:in `to_kernel_device` Start the Ruby debugger now and debug the issue? (Experts only)!) [Yes] No Logs attached.