[Bug 704344] New: An KDE X64 Installation of 11.3 will accept and start to upgrade an 11.4 I586 Version
https://bugzilla.novell.com/show_bug.cgi?id=704344 https://bugzilla.novell.com/show_bug.cgi?id=704344#c0 Summary: An KDE X64 Installation of 11.3 will accept and start to upgrade an 11.4 I586 Version Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: scott@aphofis.com QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.17) Gecko/20110420 SUSE/3.6.17-0.2.1 Firefox/3.6.17 Architecture is X_64 - Prior installation wax 11.3. Boot PC fro I586 11.4> Select upgrade and NO warning is given to the new version being the wrong architecture...The install will eventually fail as the 'process of evaluating the root partition' Finds NO Root EXT3 existing partition, indead it finds NO partition available. When the Option is put to 'display all partitions, in my case only 1 HD with a actual mount of root Ext3, is found and a swap area..However both SDA1 ad SdA2 shows format unknown. The other 3 x HD are not listed. Reproducible: Always Steps to Reproduce: 1.100% Reproducible - Do not ask me for logs please - Its reproducible 2. 3. Expected Results: I would expect that an I586 Full DVD should error out when 'Installation' is selected from the menu. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=704344 https://bugzilla.novell.com/show_bug.cgi?id=704344#c2 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scott@aphofis.com --- Comment #2 from Scott Couston <scott@aphofis.com> 2011-07-09 03:26:54 UTC --- There are other consequences of allowing the above an not issuing an error. The above mixture of an existing X_64 O/S being upgraded with I586 cause massive issued with the packet manager solver. In the above example the package manager find a conflict in wanting to downgrade hundreds of O/S and application files with "lower performance" version of I586 files -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=704344 https://bugzilla.novell.com/show_bug.cgi?id=704344#c3 Jiří Suchomel <jsuchome@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |scott@aphofis.com --- Comment #3 from Jiří Suchomel <jsuchome@novell.com> 2011-07-20 09:53:41 UTC --- 1. I installed 11.3 x86-64. 2. On the same machine, I booted 11.4 i586 medium. Selected "Update". No partition for update can be seen. If I click "Show all partition", it shows my original 11.3 system (of x86-64 architecture). 3. When I select 11.3 partition to upgrade, I get the warning "The architecture of the system installed in the selected partition is different than the one of this product. Sounds like completely solution. So, what have you done differently that you met the wrong behavior? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=704344 https://bugzilla.novell.com/show_bug.cgi?id=704344#c4 --- Comment #4 from Scott Couston <scott@aphofis.com> 2011-07-23 01:26:13 UTC --- Jiri you would need to start with X64 CPU and architecture for the first complete install the upgrade to 11.3 I586 to see the horror -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=704344 https://bugzilla.novell.com/show_bug.cgi?id=704344#c5 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|scott@aphofis.com | --- Comment #5 from Scott Couston <scott@aphofis.com> 2011-07-23 01:26:26 UTC --- OOOPs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=704344 https://bugzilla.novell.com/show_bug.cgi?id=704344#c6 Jiří Suchomel <jsuchome@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |scott@aphofis.com --- Comment #6 from Jiří Suchomel <jsuchome@novell.com> 2011-07-25 06:29:39 UTC --- (In reply to comment #4)
Jiri you would need to start with X64 CPU and architecture for the first complete install the upgrade to 11.3 I586 to see the horror
Look at comment 3, that's what I did. I did full install of x86-64 11.3 and than tried to upgrade it to 11.4 i586. Seen the warnings, as expected. So what have you done differently? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=704344 https://bugzilla.novell.com/show_bug.cgi?id=704344#c7 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|scott@aphofis.com | --- Comment #7 from Scott Couston <scott@aphofis.com> 2011-07-30 23:09:18 UTC --- Jiri - Sorry about being vague in not specifying what update version I used for testing. I had an existing X_64 11.3 installation - all o.k I then performed an update using 11.3 I586 to illistrate the potential error. I see the major issue of not restricting the same version from X_64 to update to I586 as huge. The Package manager works well in the huge list of conflicts of libray files being downgraded to I586 as part of the update. BUT if the same version of an existing X_64 installation being updated to the same version I586 the net end result would see the PC unable to boot as the I586 Kernel would be installed and replaced once the PC boots from its harddrive rather than any DVD. Whilst I am no infavour of inhibiting most any user action, I think the Package Manager solver should terminate the installation rather than present hundereds of conflicts to downgrage X_64 library files to I586 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=704344 https://bugzilla.novell.com/show_bug.cgi?id=704344#c8 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Installation AssignedTo|jsuchome@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com Product|openSUSE 11.4 |openSUSE 11.3 --- Comment #8 from Scott Couston <scott@aphofis.com> 2011-07-30 23:25:13 UTC --- Re-correct Title Again. Suggest the best solution to any conflicting installation OR upgrade being of the same version or othwise; lies in the Packet Manager Solver. Any instance of conflicks that require X_64 Library file to changed to I586 and vica versa would create a Error and terminate the update. The change of downgraging mass X_64 library files to I586 and terminating the update process should hold us in good stead no matter the future versions etc. There is also the other related issues of trying to upgrade to other OpenSuse Hardware varients by a termination issued from the Package Manager Solver -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=704344 https://bugzilla.novell.com/show_bug.cgi?id=704344#c Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|An KDE X64 Installation of |An KDE X64 Installation of |11.3 will accept and start |11.3 will accept and start |to upgrade an 11.4 I586 |to upgrade an 11.3 I586 |Version |Version -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=704344 https://bugzilla.novell.com/show_bug.cgi?id=704344#c9 Jiří Suchomel <jsuchome@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jsuchome@novell.com InfoProvider| |scott@aphofis.com --- Comment #9 from Jiří Suchomel <jsuchome@novell.com> 2011-08-01 08:14:46 UTC --- (In reply to comment #7)
I then performed an update using 11.3 I586 to illistrate the potential error.
So how have you done that update? Did you boot new (11.3 I586) media and selected Update in the workflow? Or did you just add new DVD to installed (X_64 11.3) system and ran package manager? I wrote earlier, that I myself tested the first scenario (boot new media, select Update) and was warned by YaST about different architecture. Have you done it the same way, but did not see a warning? Than it would be YaST bug that you were not warned. Or, have you seen the warning, entered package manager and it came up with tons of conflicts? If this is the case, do you consider as bug that you were allowed to enter package manager? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=704344 https://bugzilla.novell.com/show_bug.cgi?id=704344#c10 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|scott@aphofis.com | --- Comment #10 from Scott Couston <scott@aphofis.com> 2011-08-05 22:31:57 UTC ---
wrote earlier, that I myself tested the first scenario (boot new media, select Update) and was warned by YaST about different architecture.
Have you done it the same way, but did not see a warning? Than it would be YaST bug that you were not warned.
Or, have you seen the warning, entered package manager and it came up with tons of conflicts? If this is the case, do you consider as bug that you were allowed to enter package manager? Yes, you observed the same test condition as I and got the same result! I am the first to ack that this may be a Yast issue and/or Installation. In this test the packet manager displays a huge amount of X_64 library files to be replaced with I586. If we permit the packet manager conflicts to be accepted to I586 and the installation proceed further; ultimately the Kernel and/or Video specific files will be I586 and the X_64 PC will not boot. The user sees the same issue we see if we try to boot from a the wrong Kernel specific discord with the CPU architecture - The total I584 version would replace the X64 producing either inability to boot and/or completely stuff up Video and perhaps old X_64 repositories. The PC would be totally useless. I dont think there would ever be a deliberate reason to do this! I think at the same time we halt such an installation, we do so by refinement to the packet manager, not offering ANY solution to change software architecture related Library, Kernel and Video files. At the same time we should also make sure an existing PC-MAC installation cannot be upgraded to an I586 and X_64 based PC and vice-a-versa (sp) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=704344 https://bugzilla.novell.com/show_bug.cgi?id=704344#c11 Jiří Suchomel <jsuchome@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #11 from Jiří Suchomel <jsuchome@novell.com> 2011-08-08 06:46:40 UTC --- If I understand it correctly, you were warned twice (in a different way) not do do what you've tried: 1. You've checked "Show all partition" which is unchecked by default. This already means entering into expert mode. 2. You've seen the warning "The architecture of the system installed in the selected partition is different than the one of this product" (see comment 3) but still continued with upgrade. Now, you are saying that it should not be allowed to continue after the mentioned warning? Well, I think there is a reason to leave it there, because sometimes YaST may not detect installed systems correctly and than such 'manual override' is required: user should be able to continue upgrade even if YaST does not recommend it. Yes, it is a corned case. But I think current solution does not bring much danger to users, as it correctly warns them about possible problems when they choose the non-default way to go. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=704344 https://bugzilla.novell.com/show_bug.cgi?id=704344#c12 --- Comment #12 from Scott Couston <scott@aphofis.com> 2011-08-09 05:07:07 UTC --- Jiri, Yes I can see the advanced search for partitions. Part of development often involves not taking action, even if it ends up hurting the user. All I can do is log the instance - Yours is the hardest call in deciding the risk does not outweigh the cost of making things 100% - This is perfectly acceptable - The biggest wrong thing is to not take action either way - Yours is the far harder job :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=704344 https://bugzilla.novell.com/show_bug.cgi?id=704344#c13 --- Comment #13 from Scott Couston <scott@aphofis.com> 2011-08-26 20:53:31 UTC --- Jiri There is off-course, NO Kernel warning in trying to install I586 on X_64 Hardware - The warning is only present when installing X_64 on I586 Hardware -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=704344 https://bugzilla.novell.com/show_bug.cgi?id=704344#c14 --- Comment #14 from Jiří Suchomel <jsuchome@suse.com> 2011-09-01 10:13:34 UTC --- (In reply to comment #13)
Jiri There is off-course, NO Kernel warning in trying to install I586 on X_64 Hardware - The warning is only present when installing X_64 on I586 Hardware
Yes, of course. Because installing I586 on X_64 is actually possible. We were talking about update of existing installation, and there, warning is appropriate when the architecture is different. And the warning is shown in your case (by YaST). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com