| 1 |
--- |
| 2 |
upgrade: |
| 3 |
- | |
| 4 |
Due to the fix for `Bug #1740950 |
| 5 |
<https://bugs.launchpad.net/cinder/+bug/1740950>`_, the |
| 6 |
``host_name`` field in any object in the ``attachments`` |
| 7 |
array of the volume detail response is populated only when |
| 8 |
the call is made in an administrative context. Otherwise, |
| 9 |
its value is the JSON ``null`` value. This is consistent with |
| 10 |
prior API behavior, as it has always been possible for the |
| 11 |
value of that field to be ``null``. |
| 12 |
security: |
| 13 |
- | |
| 14 |
It was possible under certain circumstances for the host name |
| 15 |
of an instance to be leaked in the volume detail response. This |
| 16 |
has been fixed in the current release. The ``host_name`` field |
| 17 |
in any object in the ``attachments`` array of the volume |
| 18 |
detail response is populated only when the call is made in an |
| 19 |
administrative context. Otherwise, its value is the JSON ``null`` |
| 20 |
value. |
| 21 |
fixes: |
| 22 |
- | |
| 23 |
`Bug #1740950 <https://bugs.launchpad.net/cinder/+bug/1740950>`_: |
| 24 |
the ``host_name`` field in any object in the ``attachments`` array |
| 25 |
of the volume detail response is populated only when the call is |
| 26 |
made in an administrative context. Otherwise, its value is the |
| 27 |
JSON ``null`` value. |