Description of problem: I wanted to post this as a BUG so that people get a chance to look at it. Reproducible: Steps to Reproduce:
In VirtualBox, M4.1, KDE, 32-bit Start with an updated install of M4.1 Set: Wed Jan 14 16:52:57 CET 2015 Mageia-5-beta2-i586-DVD.iso 5d52b2614967c68e3b4b1d6c66520e2f as the first bootable device. Goes through the upgrade process but reports one error: Error: "Script" failed for libgrilo-gir0.2-0.2.11-4.mga5.i586 Continuing on it went to a working desktop. I changed the repo to the M5 repo, updated, rebooted and it came back to a working desktop. Only wrinkle is that it was not able to connect to an NFS share during boot. I was able to make the connect manually: [root@shermanm4 wilcal]# mount -a All installed apps seemed to work properly. 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.10-1.1.mga4.x86_64 virtualbox-guest-additions-4.3.10-1.1.mga4.x86_64
In VirtualBox, M4.1, KDE, 64-bit Start with an updated install of M4.1 Set: Wed Jan 14 20:18:39 CET 2015 Mageia-5-beta2-x86_64-DVD.iso b74d62bf415da953917d50536c1a4419 as the first bootable device. Goes through the upgrade process but reports one error: Error: "Script" failed for lib64grilo-gir0.2-0.2.11-4.mga5.i586 Continuing on it came back to a terminal. I logged in as wilcal then startx started KDE. Only wrinkle after that was that it was not able to connect to an NFS share during boot. I was able to make the connect manually: [root@shermanm4 wilcal]# mount -a All installed apps seemed to work properly. 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.10-1.1.mga4.x86_64 virtualbox-guest-additions-4.3.10-1.1.mga4.x86_64
For next one, one bug/issue, will be much better ;)
Blocks: (none) => 15013Summary: M4.1 -> M5B2 upgrade results => M4.1 -> M5B2 upgrade results (libgrilo-gir0.2 ; NFS)
This is old
Status: NEW => RESOLVEDResolution: (none) => FIXED
I'm going to reopen this with M5RC
Status: RESOLVED => REOPENEDResolution: FIXED => (none)Summary: M4.1 -> M5B2 upgrade results (libgrilo-gir0.2 ; NFS) => M4.1 -> M5RC upgrade results (preload-0.6.4-7 ; NFS)
In VirtualBox, M4.1, KDE, 32-bit Start with an up to date install of M4.1 Set: Wed Feb 25 20:41:46 CET 2015 Mageia-5-rc-i586-DVD.iso md5sum: 13e98ac12db9f3cd7562f7bda36ada53 as the first bootable device. Goes through the upgrade process but reports one error: Error: "Script" failed for preload-0.6.4-7.mga5.i586 Continuing on it went to a working desktop. I changed the repo to the M5 repo, updated, rebooted and it came back to a working desktop. Only wrinkle is that it still is not able to connect to an NFS share during boot. I was able to make the connect manually using: [root@shermanm4 wilcal]# mount -a All installed apps seemed to work properly. 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.10-1.1.mga4.x86_64 virtualbox-guest-additions-4.3.10-1.1.mga4.x86_64
can you attach /root/drakx/install.log Bill please
Created attachment 5958 [details] install.log from commnet #7
Created attachment 5959 [details] install.log from comment #7
Opps uploaded it twice. x86-64 soon.
In VirtualBox, M4.1, KDE, 64-bit Start with an up to date install of M4.1 Set: Wed Feb 25 21:32:45 CET 2015 Mageia-5-rc-x86_64-DVD.iso md5sum: 0e3ae4c152e16cd366b2110a0e4b2353 as the first bootable device. Goes through the upgrade process but reports one error: Error: "Script" failed for preload-0.6.4-7.mga5.x86_64 It booted to a terminal. I logged in as user then started x and it was fine. Continuing on it went to a working desktop. I changed the repo to the M5 repo, updated, rebooted and it came back to a working desktop. The NFS share works fine here. Reboots still require that I log in and start x. Common installed apps seemed to work properly. 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.10-1.1.mga4.x86_64 virtualbox-guest-additions-4.3.10-1.1.mga4.x86_64
Created attachment 5960 [details] install.log from comment #12
CC: (none) => remiBlocks: (none) => 14069
Blocks: 14069 => (none)
Blocks: (none) => 15637
Is this still valid? If yes it's a blocker isn't it?
Keywords: (none) => NEEDINFOPriority: Normal => release_blockerSummary: M4.1 -> M5RC upgrade results (preload-0.6.4-7 ; NFS) => M4.1 -> M5RC upgrade script error (preload-0.6.4-7 ; NFS)Source RPM: (none) => preload-0.6.4-7.mga5.x86_64
CC: (none) => thierry.vignaud Attachment 5958 is obsolete: 0 => 1
Attachment 5959 is obsolete: 0 => 1
Attachment 5960 is obsolete: 0 => 1
There's no errors in those logs. Please attach your /root/drakx/report.bug.xz instead. And a single package issue cannot be a release blocker...
Priority: release_blocker => Normal
In VirtualBox, M4.1 -> M5, KDE, 32-bit Start with an up to date install of M4.1 Set: Tue May 19 00:30:02 CEST 2015 Mageia-5-i586-DVD.iso md5sum: b4044bf961a10196ada679b8f90ec608 as the first bootable device. Execute upgrade. Only continuing wrinkle is that it still is not able to connect to an NFS share during boot. I was able to make the connect manually using: [root@shermanm4 wilcal]# mount -a All installed apps seemed to work properly. Switched to M5 repo, updates installed cleanly. Rebooted to a working desktop. Removed all orphans then successfully rebooted back to a working desktop. 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
In other words, the preload script issue is fixed?
(In reply to Samuel VERSCHELDE from comment #17) > In other words, the preload script issue is fixed? Gimme a day or so on this Samuel. I wanna go through the upgrades all over again both in Vbox and on real hardware. At this point in Vbox i586 M4.1 -> M5 upgrade looks clean.
Well, we usually don't like carryall bugs. This report mixes successful upgrades, script errors, NFS issues. Developers can't follow that so your reports here will probably remain without impact. You need to create one bug report per specific issue, then close it once the issue in question is fixed. This was asked by Manuel 3 month ago already.
Only script for preload is %_post_service, which shouldn't have errors. Closing this. Reopen if problem reappears.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
I disagree. "it shouldn't have errors" conflicts with the fact this bug did happen.
CC: (none) => mageia