Wrong value of free space after set default node volume

[Oleksandr Minakov]

Steps to reproduce:
1) Create cluster
2) Add one node to the cluster
3) Check volumes in postgresql
    $su postgres
    $psql nailgun
    #select * from volume_manager_node_volumes;

We should see 0 in "free_space" after set default node volumes

Expected: "free_space": 0

Actual: "free_space": 50572 (equal to all disk space without boot volume and lvm_meta).

And if we will do some changes in disc configuration in Fuel UI and than push apply free_space will be recalculated to right value.

{
    "release": "9.0",
    "auth_required": true,
    "api": "1",
    "openstack_version": "liberty-9.0",
    "feature_groups": []
}

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/292415

[Vladimir Kuklin (vkuklin)]

Oleksandr, could you please elaborate which particular functionality is broken? Volume allocation happens when we do actual deployment. Before that it is ok to have free space set to almost all space - we have not allocated anything yet.

[Oleksiy Molchanov (omolchanov)]

Marking as Invalid, because of no update for more than a month.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/292415
Reason: This repo is retired now, no further work will get merged.