incorrect partition size in UI

Bug #1370533 reported by Gleb
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
New
Medium
Fuel Python (Deprecated)

Bug Description

{
    "build_id": "2014-07-28_10-30-48",
    "ostf_sha": "8c328521b1444f22c50463b9432193e20ed33813",
    "build_number": "367",
    "auth_required": true,
    "api": "1.0",
    "nailgun_sha": "83cc9ed44ebc8dd97248483b6d414ebbc4cff3c0",
    "production": "docker",
    "fuelmain_sha": "9adfbf5a52cedbdd16ec1a74f6c44c5b3419b87c",
    "astute_sha": "aa5aed61035a8dc4035ab1619a8bb540a7430a95",
    "feature_groups": [
        "mirantis"
    ],
    "release": "5.1",
    "fuellib_sha": "d1c7f67b3cf51978d3178c8666ea398f2477dcb5"
}

I tryied to emulate Ceph Journals on SSD and created 0.3Gb disks on test VMs.
Fuel sees all 0.3Gb but when I click on "USE ALL ALLOWED SPACE" it allocate only 7Mb.

Screenshot is atached.

Revision history for this message
Gleb (gleb-q) wrote :
Revision history for this message
Nastya Urlapova (aurlapova) wrote :

Gleb, please try to reproduce on 5.1-9(RC3)

Changed in fuel:
status: New → Incomplete
Revision history for this message
Gleb (gleb-q) wrote :

It reproduced on small volumes (1Gb or less)

{
    "build_id": "2014-09-17_21-40-34",
    "ostf_sha": "64cb59c681658a7a55cc2c09d079072a41beb346",
    "build_number": "11",
    "auth_required": true,
    "api": "1.0",
    "nailgun_sha": "eb8f2b358ea4bb7eb0b2a0075e7ad3d3a905db0d",
    "production": "docker",
    "fuelmain_sha": "8ef433e939425eabd1034c0b70e90bdf888b69fd",
    "astute_sha": "f5fbd89d1e0e1f22ef9ab2af26da5ffbfbf24b13",
    "feature_groups": [
        "mirantis"
    ],
    "release": "5.1",
    "release_versions": {
        "2014.1.1-5.1": {
            "VERSION": {
                "build_id": "2014-09-17_21-40-34",
                "ostf_sha": "64cb59c681658a7a55cc2c09d079072a41beb346",
                "build_number": "11",
                "api": "1.0",
                "nailgun_sha": "eb8f2b358ea4bb7eb0b2a0075e7ad3d3a905db0d",
                "production": "docker",
                "fuelmain_sha": "8ef433e939425eabd1034c0b70e90bdf888b69fd",
                "astute_sha": "f5fbd89d1e0e1f22ef9ab2af26da5ffbfbf24b13",
                "feature_groups": [
                    "mirantis"
                ],
                "release": "5.1",
                "fuellib_sha": "d9b16846e54f76c8ebe7764d2b5b8231d6b25079"
            }
        }
    },
    "fuellib_sha": "d9b16846e54f76c8ebe7764d2b5b8231d6b25079"
}

Changed in fuel:
assignee: nobody → Fuel Python Team (fuel-python)
milestone: none → 6.0
importance: Undecided → Medium
status: Incomplete → New
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

It happens because we lock 200Mb on each disk for boot image. It was done in order to avoid issues with incorrect boot settings in bios. We are going to get rid of it in future. There is a bug https://bugs.launchpad.net/fuel/+bug/1258347 and a blueprint https://blueprints.launchpad.net/fuel/+spec/volume-manager-refactoring for that.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.