Bug 1477606

There are two issues here. First is the customer issue, which is described in
the customer portal [1] and observed in the attachment [2]. The attachment
shows the Horizon UI displaying an error message ("Unable to retrieve the
default volume type.") on the screen where the user is trying to create a
volume from an image. The second issue is the fact that the Director does not
create a default volume type when deploying the overcloud. The premise is that
addressing the second issue will resolve the customer's issue. However, I
don't think this is true.

Cinder does not require the user define a default volume type, even when
multiple volume types have been defined. In fact, cinder doesn't require _any_
volume types be defined. In other words, the Director is not required to
define a default volume type because cinder does not require one.

Regarding the customer's issue, I was not able to reproduce the problem. I did
a fresh deployment of OSP-10, uploaded an image, and then used the Horizon UI
to create a volume from the image. The first thing I noted is "Type" widget
(which lets the user choose the volume type) offers only one option, and that
is "No volume type". I experimented by creating additional volume types, and
observed they would appear as options in the UI widget. But, compare this with
the customer's screenshot [2], where the "Type" widget appears to be blank. I
could not reproduce this behavior, nor did I ever see the "Unable to retrieve
the default volume type" error message.

I do not doubt the customer is experiencing a problem, but it seems related to
the Horizon UI rather than the underlying cinder behavior. I suggest another BZ
be opened that focuses on the customer's issue with Horizon. I think this BZ
should be closed NOTABUG. It simply is not necessary for the Director to
define a default volume type.

[1] https://access.redhat.com/support/cases/01902709
[2] https://bugzilla.redhat.com/attachment.cgi?id=1308212

Please ACK if this can be closed per my comment #2.

Update: While I was not able to reproduce the Horizon behavior, I am informed that a default cinder volume type really should be assigned.

I'll work on that issue with this BZ, but consider opening another bug if there's a separate problem related to Horizon's behavior.

*** Bug 1537471 has been marked as a duplicate of this bug. ***

*** Bug 1537471 has been marked as a duplicate of this bug. ***

*** Bug 1241442 has been marked as a duplicate of this bug. ***

I'll update the target release based on how soon the upstream patch merges.

Upstream patches have merged.

Verified on:
openstack-tripleo-heat-templates-9.0.0-0.20180831204457.17bb71e.0rc1.el7ost.noarch

Basic OSPD deployment Cinder with LVM backend, now has a default Cinder volume type:

(overcloud) [stack@undercloud-0 ~]$ cinder type-list
+--------------------------------------+---------+-------------+-----------+
| ID                                   | Name    | Description | Is_Public |
+--------------------------------------+---------+-------------+-----------+
| babdcdd7-e5f8-438b-8551-1bf9d6df8a71 | tripleo | -           | True      |
+--------------------------------------+---------+-------------+-----------+
(overcloud) [stack@undercloud-0 ~]$ cinder type-default 
+--------------------------------------+---------+-------------+-----------+
| ID                                   | Name    | Description | Is_Public |
+--------------------------------------+---------+-------------+-----------+
| babdcdd7-e5f8-438b-8551-1bf9d6df8a71 | tripleo | -           | True      |
+--------------------------------------+---------+-------------+-----------+
 
From Horizon successfully created a new image (cirros) backed volume.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:0045