Bug 762579 (GLUSTER-847) - Partition table doesn't update during installation
Summary: Partition table doesn't update during installation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-847
Product: GlusterSP
Classification: Retired
Component: core
Version: 3.0.3
Hardware: All
OS: Linux
low
low
Target Milestone: 3.1.2
Assignee: Harshavardhana
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-23 06:22 UTC by Raghavendra Bhat
Modified: 2015-03-23 01:03 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Raghavendra Bhat 2010-04-23 06:22:17 UTC
Suppose the /proc/partitions is not updated while the platform is being installed, then that error should be reported to the user in the UI. It just says installation is in progress and installation does not complete. One has to reboot the machine and install the platform again. That error should be reported to the user in the UI and suggest the user to reboot the machine and install again.

Comment 1 Harshavardhana 2010-06-11 01:27:24 UTC
This issue is seen when the partitions created during platform installation, where the disks are already partitioned earlier with msdos.  Since platform does mklabel with gpt, this seems to be causing the problem.

Even the partprobe and any other utility doesn't help to update partition tables. When we reboot the machine and install again it will work.

There is a work around for this kernel behaviour by doing a "udev trigger" and "udev settle"  with a "modprobe scsi_wait_scan" which is sometimes required to be done for certain disks and is part of anaconda source code.  Apart from that more testing is required for this issue.

Seen and can be reproduced on the Dell MD boxes we have in our lab.

Comment 2 Harshavardhana 2010-10-15 22:42:21 UTC
Is this issue still valid?, Raghavendra can you ask relevant people in QA to test and see if its still valid. 

Thanks

Comment 3 Rahul C S 2010-10-26 04:30:41 UTC
(In reply to comment #2)
> Is this issue still valid?, Raghavendra can you ask relevant people in QA to
> test and see if its still valid. 
> 
> Thanks

Harsha,

Do not seem to be hitting that issue, right now looks like its been fixed because i tried a few times.

Will re-open if i find it again.


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