Umount /target before creating other partitions

[Vladimir Kozhukalov]

In Ubuntu, there are some raid cards that will not update partition or file systems properly if any partition of the device is already mounted. In these cases, it is necessary to umount all mount points which are connected to a particular disk before creating other partitions on that disk.

This is usually found on HP hardware

This may cause the OS to boot after provisioning, leaving you at the just after the PXE loader reports "Booting..."

This may cause "The disk drive for /var/lib/nova is not ready yet or present."

This may cause "The disk drive for /var/lib/glance is not ready yet or present."

[Andrew Woodward (xarses)]

https://review.openstack.org/#/c/83032/

[Openstack Gerrit (openstack-gerrit)]

Reviewed: https://review.openstack.org/83032
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=349e3b5756af2030bf6f8fe1965cc745846baf9f
Submitter: Jenkins
Branch: master

commit 349e3b5756af2030bf6f8fe1965cc745846baf9f
Author: Vladimir Kozhukalov <email address hidden>
Date: Wed Mar 26 14:12:26 2014 +0400

    Added mounting and umounting /target

    It turned out that in some cases it is necessary to umount
    all mount points which are connected to a particular disk
    before creating other partitions on that disk.

    Change-Id: I43a2de132415d026a6dc096e2b25ce0ab4cce915
    Closes-Bug: #1297792

[Openstack Gerrit (openstack-gerrit)]

Fix proposed to branch: stable/4.1
Review: https://review.openstack.org/89980

[Openstack Gerrit (openstack-gerrit)]

Reviewed: https://review.openstack.org/89980
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=a77e9e6179936c184abddbf07c52d68564f4853f
Submitter: Jenkins
Branch: stable/4.1

commit a77e9e6179936c184abddbf07c52d68564f4853f
Author: Vladimir Kozhukalov <email address hidden>
Date: Wed Mar 26 14:12:26 2014 +0400

    Added mounting and umounting /target

    It turned out that in some cases it is necessary to umount
    all mount points which are connected to a particular disk
    before creating other partitions on that disk.

    Change-Id: I43a2de132415d026a6dc096e2b25ce0ab4cce915
    Closes-Bug: #1297792

[Miroslav Anashkin (manashkin)]

Last change request actually failed to fix this issue.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/92621
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=9d8a83446b314122523b41f1db40b013ebbd32ca
Submitter: Jenkins
Branch: master

commit 9d8a83446b314122523b41f1db40b013ebbd32ca
Author: Vladimir Kozhukalov <email address hidden>
Date: Wed May 7 20:09:02 2014 +0400

    Fixed some ubuntu points in pmanager.py

    Added umounting /dev/sda3 apart from unmounting /target.
    Added additional lvm cleaning right after creating
    physical volume partitions. If a new physical volume
    partition matches the boundaries of the previous one, we can
    not reread partition table then. Additional lvm cleaning
    allows to avoid this such a kind of undesirable behaviour.

    Closes-Bug: #1297792
    Change-Id: Ibce615837b7d08806cf7b551d40f8dbc4b03b8b1

[Meg McRoberts (dreidellhasa)]

Added to "Fixed Issues" in 5.0 Release Notes.

[Miroslav Anashkin (manashkin)]

Bug was changed to Fixed by Gerrit.

Actually, fix does not work for old HP Smart Array P200/P400/P800 and older controllers, for which Ubuntu loads CCISS driver.

[Dmitry Borodaenko (angdraug)]

Miroslav, please confirm if this is still a problem in 5.0 and 5.1, or is it only 4.1 that still need to have the same fix backported?

[Evgeny Kozhemyakin (ekozhemyakin)]

The issue doesn't appear on 5.0.
5.1 (fuel-master-265-2014-06-23_00-31-14.iso) is OK too.