yahoo-eng-team team mailing list archive

[OpenStack Infra <1550023@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/284973
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=8a4aa96d7c0b0902acd23160ecf917431d5d7005
Submitter: Jenkins
Branch:    master

commit 8a4aa96d7c0b0902acd23160ecf917431d5d7005
Author: David Medberry <openstack@xxxxxxxxxxxx>
Date:   Thu Feb 25 15:41:09 2016 -0700

    Don't force people to security groups after they add a FIP
    
    Horizon should not move people from the instances page to
    the security groups page after adding a FIP. It's already
    too late to prevent bad things from happening and this
    implies that it is not too late.
    
    Change-Id: I03796253fc6b6c56572c6e841f3ce3102c9c6cdd
    Closes-bug: #1550023


** Changed in: horizon
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1550023

Title:
  Really bad workflow bug in top of tree

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The associate floating ip success now takes you to a completely different web page than you started.
  This is a fundamentally flawed, broken, bad assumption.

  Ref:
  https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/access_and_security/floating_ips/workflows.py#L148

  It was probably done with the idea that you might want to change/check
  your sec group after the fact but since it's already too late now,
  don't do that....

  ALso, really breaks the stream of consciousness of working in

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1550023/+subscriptions