Volume Group Under project panel not working

[Vishal Manchanda]

Volume Group under project panel not working properly for master branch.

Volume Group table under project panel is missing same is attached

[Akihiro Motoki (amotoki)]

I figured the root cause of this. We set permissions for the table, but it does not cover "volumev3"....

[Akihiro Motoki (amotoki)]

This happens because devstack dropped "volume" endpoint (as they consider it is for volume v1 API) [1].

I am not sure "volume" cannot be used for Volume v3 API deployments though.

[1] https://review.opendev.org/#/c/485232/

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/661960

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/661960
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=0cb5167b99d418c7ce8cbc9adda24f228fdd42d0
Submitter: Zuul
Branch: master

commit 0cb5167b99d418c7ce8cbc9adda24f228fdd42d0
Author: Akihiro Motoki <email address hidden>
Date: Wed May 29 21:22:23 2019 +0900

    Make project volume group table work even with volumev3 only env

    Previously the volume group table in the project dashboard checked if
    'volume' endpoint is available and 'volumev3' endpoint was not checked.
    'volumev3' is an endpoint name commonly used for Volume v3 API and
    it is not surprising that only volumev3 is configured in deployments,
    so we should ensure that horizon works with environments only with
    'volumev3' endpoint.

    The service endpoints are already checked in panel.py, so there is no
    need to have the permission check (i.e., service check) in the table.

    Similar patterns are found in tables in project/snapshots and
    project/vg_snapshots. They are also cleanup by this commit.

    Change-Id: I12d03745bec5d8dec10a8e2b4306c595f2f39560
    Closes-Bug: #1829461

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/stein
Review: https://review.opendev.org/663884

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/663885

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/663884
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=c3ac75edcb0808bb25977bee3c3a5691c325a708
Submitter: Zuul
Branch: stable/stein

commit c3ac75edcb0808bb25977bee3c3a5691c325a708
Author: Akihiro Motoki <email address hidden>
Date: Wed May 29 21:22:23 2019 +0900

    Make project volume group table work even with volumev3 only env

    Previously the volume group table in the project dashboard checked if
    'volume' endpoint is available and 'volumev3' endpoint was not checked.
    'volumev3' is an endpoint name commonly used for Volume v3 API and
    it is not surprising that only volumev3 is configured in deployments,
    so we should ensure that horizon works with environments only with
    'volumev3' endpoint.

    The service endpoints are already checked in panel.py, so there is no
    need to have the permission check (i.e., service check) in the table.

    Similar patterns are found in tables in project/snapshots and
    project/vg_snapshots. They are also cleanup by this commit.

    Change-Id: I12d03745bec5d8dec10a8e2b4306c595f2f39560
    Closes-Bug: #1829461
    (cherry picked from commit 0cb5167b99d418c7ce8cbc9adda24f228fdd42d0)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/663885
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=721622d182ae95320825808e2a052428e3e83d90
Submitter: Zuul
Branch: stable/rocky

commit 721622d182ae95320825808e2a052428e3e83d90
Author: Akihiro Motoki <email address hidden>
Date: Wed May 29 21:22:23 2019 +0900

    Make project volume group table work even with volumev3 only env

    Previously the volume group table in the project dashboard checked if
    'volume' endpoint is available and 'volumev3' endpoint was not checked.
    'volumev3' is an endpoint name commonly used for Volume v3 API and
    it is not surprising that only volumev3 is configured in deployments,
    so we should ensure that horizon works with environments only with
    'volumev3' endpoint.

    The service endpoints are already checked in panel.py, so there is no
    need to have the permission check (i.e., service check) in the table.

    Similar patterns are found in tables in project/snapshots and
    project/vg_snapshots. They are also cleanup by this commit.

    Change-Id: I12d03745bec5d8dec10a8e2b4306c595f2f39560
    Closes-Bug: #1829461
    (cherry picked from commit 0cb5167b99d418c7ce8cbc9adda24f228fdd42d0)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/horizon 14.0.4 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/horizon 15.1.1 release.