Merge "MOS-RN6.1 Horizon known issues - edits"

This commit is contained in:
Jenkins
2015-06-23 06:13:36 +00:00
committed by Gerrit Code Review

View File

@@ -11,19 +11,21 @@ Resolved Horizon issues
Known Horizon issues
++++++++++++++++++++
* If one of two Neutron options are chosen in the :guilabel:`Network`
configuration section during the environment deployment, the
:guilabel:`Disassociate Floating IP` option disappears for an
instance with an associated floating IP in the
:menuselection:`Project > Compute > Instances` table (though it
works when :guilabel:`Nova Network` option is chosen during
deployment). You can still find (and use) this option in the
:menuselection:`Project > Access & Security > Floating IPs` table.
See `LP1325575`_.
* If one of the two Neutron options is chosen during the
:guilabel:`Network Setup` of the :guilabel:`Create a New
OpenStack environment` wizard, the :guilabel:`Disassociate Floating IP`
option disappears for an instance with an associated floating IP in
the :menuselection:`Project > Compute > Instances` table within
Horizon. This is NOT an issue if the :guilabel:`Nova Network` is chosen
during the :guilabel:`Network Setup`. You can work around this issue
by using the :guilabel:`Disassociate Floating IP` located in the
:menuselection:`Project > Access & Security > Floating IPs` table
within Horizon. See `LP1325575`_.
* In a multi-region environment, when you log into Horizon or change
a tenant, the dashboard uses only one and the same region, though
after that you may switch to a desired one. See `LP1452722`_.
* When changing tenants, the current region (Keystone service region)
may change unexpectedly. After logging in or changing tenants, a
user should select their desired region to ensure they are working
with the correct one. See `LP1452722`_.
.. Links
.. _`LP1325575`: https://bugs.launchpad.net/mos/6.1.x/+bug/1325575