Bug 15686

Summary:	no nfs share mount after upgrade M4.1 -> M5RC i586 (in virtualbox only)
Product:	Mageia	Reporter:	William Kenney <wilcal.int>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	minor
Priority:	Low	CC:	guillomovitch, thierry.vignaud
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	Mageia 6
Hardware:	i586
OS:	Linux
Whiteboard:	5rc
Source RPM:	nfs-utils	CVE:
Status comment:
Attachments:	drakx files journalctl -b output upgrade on real hardware

Description William Kenney 2015-04-12 16:42:40 CEST

Description of problem:

wilcal in Vbox: M4.1 -> M5RC KDE upgrade using

ISO Name: Mageia-5-RC-i586-DVD.iso
DATE.txt: Thu Apr  9 23:04:38 CEST 2015  
md5sum:  51537a09099b0be5fb5bf01b861030e7

Starting with M4.1 i586 that has a working NFS share mount
with a M4.1 server on the LAN. After upgrade NFS share no
longer works. Even removing nfs-utils and deleting share
comment from /etc/fstab rebooting, then reinstalling nfs-utils
and setting that up all over again does not cure the problem.
I believe this problem has been around for a long time.
This does not occur in:

ISO Name: Mageia-5-RC-x86_64-DVD.iso
DATE.txt: Thu Apr  9 22:56:24 CEST 2015
md5sum:  98cbb4e2366dd2218896b71e1801b441

Reproducible: 

Steps to Reproduce:

Comment 1 William Kenney 2015-04-12 16:51:01 CEST

Created attachment 6246 [details]
drakx files

Comment 2 William Kenney 2015-04-27 16:19:37 CEST

In VirtualBox, M4, KDE, 32-bit

Bug continues:

wilcal in Vbox: M4.1 -> M5RC KDE upgrade using

ISO Name: Mageia-5-RC-i586-DVD.iso
DATE.txt: Mon Apr 20 23:43:56 CEST 2015 
md5sum:  1c92e633ffbcbaf49446aa418d92ae46

Starting with M4.1 i586 that has a working NFS share mount
with a M4.1 server on the LAN. After upgrade NFS share no
longer works. Even removing nfs-utils and deleting share
comment from /etc/fstab rebooting, then reinstalling nfs-utils
and setting that up all over again does not cure the problem.
I believe this problem has been around for a long time.
This does not occur in:

ISO Name: Mageia-5-RC-x86_64-DVD.iso
DATE.txt: Mon Apr 20 23:54:12 CEST 2015
md5sum:  f29f810208def3fb3e360d64bb11072d

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

William Kenney 2015-04-27 16:21:03 CEST

Whiteboard: (none) => 5rc

Comment 3 Thierry Vignaud 2015-04-28 07:19:57 CEST

This is not an installer bug.
We would need you to attach "journalctl -b" output.

Keywords: (none) => NEEDINFO
CC: (none) => guillomovitch, thierry.vignaud
Component: Installer => RPM Packages
Source RPM: (none) => nfs-utils

Comment 4 William Kenney 2015-04-28 18:26:35 CEST

Created attachment 6392 [details]
journalctl -b output

Comment 5 William Kenney 2015-05-02 19:23:33 CEST

Created attachment 6429 [details]
upgrade on real hardware

Ok so I did this on real hardware and the NFS connection was fine.
I've created a ZIP file of the drakx logs and attached it.
This is before any updates.

Comment 6 William Kenney 2015-05-02 21:00:03 CEST

So on real hardware even after a full update of all the M4 -> M5 files
and sweeping out the orphans then reboot the NFS connection remains fine.
So this looks to be a Vbox only thing. I suspect very few people
will encounter this bug so I'm gonna reduce the Priority to Low and
the Severity to minor.

Priority: Normal => Low
Severity: normal => minor

Samuel Verschelde 2015-05-19 14:28:38 CEST

Keywords: NEEDINFO => (none)

Samuel Verschelde 2015-05-19 14:28:48 CEST

Summary: no nfs share mount after upgrade M4.1 -> M5RC i586 => no nfs share mount after upgrade M4.1 -> M5RC i586 (in virtualbox only)

Samuel Verschelde 2015-05-19 14:29:23 CEST

Assignee: bugsquad => guillomovitch

Comment 7 Samuel Verschelde 2015-06-06 16:12:13 CEST

Since we can't fix it anymore and the original reporter thinks it's a minor bug, I suggest to close this bug report. Unless you want to keep it to address it for the mga5 -> mga6 migration William?

Keywords: (none) => NEEDINFO

Comment 8 William Kenney 2015-06-06 17:05:19 CEST

(In reply to Samuel VERSCHELDE from comment #7)

> Unless you want to keep it to address it
> for the mga5 -> mga6 migration William?

Lets keep it open and minor as a bookmark for action in M6.
As I usually think when we identify the cause it could have
an effect on other things. Thanks

Samuel Verschelde 2015-06-06 17:07:04 CEST

Target Milestone: --- => Mageia 6

Samuel Verschelde 2015-06-06 17:07:10 CEST

Keywords: NEEDINFO => (none)

Comment 9 Guillaume Rousse 2015-07-09 19:18:55 CEST

I won't perform any investigation myself about such kind of issue. Feel free to reassign the bug to yourself if you're really interested.

Assignee: guillomovitch => bugsquad

Comment 10 Samuel Verschelde 2016-10-10 23:01:07 CEST

(In reply to William Kenney from comment #8)
> (In reply to Samuel VERSCHELDE from comment #7)
> 
> > Unless you want to keep it to address it
> > for the mga5 -> mga6 migration William?
> 
> Lets keep it open and minor as a bookmark for action in M6.
> As I usually think when we identify the cause it could have
> an effect on other things. Thanks

More than one year later, we haven't investigated it :)

Are you willing to do so, William?

Samuel Verschelde 2016-10-10 23:28:07 CEST

Keywords: (none) => NEEDINFO

Comment 11 William Kenney 2016-10-10 23:51:15 CEST

I'm willing to put this to bed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED