Bug 15938 - Attempting a upgrade, M4.1 to M5, using Live-media is destructive
Summary: Attempting a upgrade, M4.1 to M5, using Live-media is destructive
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: High major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: m5final
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-14 19:09 CEST by William Kenney
Modified: 2015-05-14 21:19 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description William Kenney 2015-05-14 19:09:54 CEST
Description of problem:

In VirtualBox, M4.1 -> M5final Upgrade, KDE, 32-bit

Using an up to date x86_64 M4.1 Vbox client then booting from:

Mageia-5-LiveDVD-KDE4-x86_64-DVD.iso
Wed May  6 12:00:00 CEST 2015
md5sum: 7b06a39d3af2167e07a017acfa1eac91

Live media system ignores installed M4.1 then goes into endless
looping processes none of which results in an installed system.
Process does involve reformatting "drives" which results in a
complete loss of the previously installed M4.1 x86_64 system.

Bummer.

Test platform:
Intel Core i7-2600K Sandy Bridge 3.4GHz
GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo
GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB
RTL8111/8168B PCI Express 1Gbit Ethernet
DRAM 16GB (4 x 4GB)
Mageia 4 64-bit, Nvidia driver
virtualbox-4.3.26-1.mga4.x86_64
virtualbox-guest-additions-4.3.26-1.mga4.x86_64

Reproducible: 

Steps to Reproduce:
William Kenney 2015-05-14 19:10:53 CEST

Whiteboard: (none) => m5final

Comment 1 William Kenney 2015-05-14 19:22:31 CEST
Correction to Description Line #1 s/b:

In VirtualBox, M4.1 -> M5final Upgrade, KDE, 64-bit
Comment 2 William Kenney 2015-05-14 19:25:01 CEST
In VirtualBox, M4.1 -> M5final Upgrade, KDE, 32-bit

Using an up to date i586 M4.1 Vbox client then booting from:

Mageia-5-LiveDVD-KDE4-i586-DVD.iso
Wed May  6 12:00:00 CEST 2015
md5sum: b2b0c5c4b8490d9f6c365fdcfec9fb95

Live media system ignores installed M4.1 then goes into endless
looping processes none of which results in an installed system.
Process does involve reformatting "drives" which results in a
complete loss of the previously installed M4.1 x86_64 system.

Test platform:
Intel Core i7-2600K Sandy Bridge 3.4GHz
GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo
GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB
RTL8111/8168B PCI Express 1Gbit Ethernet
DRAM 16GB (4 x 4GB)
Mageia 4 64-bit, Nvidia driver
virtualbox-4.3.26-1.mga4.x86_64
virtualbox-guest-additions-4.3.26-1.mga4.x86_64
Comment 3 Rémi Verschelde 2015-05-14 19:41:57 CEST
Upgrade using Live media is not supported at all Bill.

On the other hand, if it proposes to upgrade and fails, it should probably be looked into to disable the possibility to upgrade with Live ISOs.
Comment 4 William Kenney 2015-05-14 20:04:07 CEST
(In reply to Rémi Verschelde from comment #3)

> Upgrade using Live media is not supported at all Bill.
> 
> On the other hand, if it proposes to upgrade and fails, it should probably
> be looked into to disable the possibility to upgrade with Live ISOs.

Ya, a user can execute the process and doing so blows up the
already installed M4.1. Not a good thing.
Comment 5 William Kenney 2015-05-14 20:18:03 CEST
Lets rename this then.

Summary: Upgrading M4.1 with M5 Live-media puts process into loops and a lost system => Attempting a upgrade, M4.1 with M5, using Live-media is destructive

William Kenney 2015-05-14 20:18:25 CEST

Priority: Normal => High

William Kenney 2015-05-14 20:20:06 CEST

Summary: Attempting a upgrade, M4.1 with M5, using Live-media is destructive => Attempting a upgrade, M4.1 to M5, using Live-media is destructive

Comment 6 Thomas Backlund 2015-05-14 21:19:53 CEST
We have not _ever_ supported ugrades with live medias.

We even warn about it on download pages.

If endusers still wants to break their systems, we cant stop them..

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.