Error while deleting a VIP

Bug #1439180 reported by Kobi Samoray
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Low
Tatiana Ovchinnikova

Bug Description

While deleting a VIP from Horizon load balancer dashboard, the following error is shown:
'You are not allowed to delete vip: <pool name associated with VIP>'

This error is shown although there was no attempt to delete the pool, but only a VIP.
The VIP is deleted successfully and the error above is shown in addition to the 'vip deleted successfully' message.

The error was observed with different lbaas drivers.
CLI is able to delete VIPs with no errors displayed.

Kobi Samoray (ksamoray)
description: updated
Liyingjun (liyingjun)
Changed in horizon:
status: New → Confirmed
Revision history for this message
Sungjin Yook (sungyook) wrote :

I also observed same error while deleting vip on kilo dashboard.

Revision history for this message
Sungjin Yook (sungyook) wrote :

Is there any workaround to this problem ?

Revision history for this message
Sungjin Yook (sungyook) wrote :

When deleting vip from dashboard:
==> Error: You are not allowed to delete vip: testpool

In the /var/log/httpd/error_log :
[root@qdev-network-tor01-jr httpd]# tail -f error_log
...
[Mon May 11 20:08:38.112326 2015] [:error] [pid 10665] Permission denied to scheduled deletion of vip: "testpool"

But lb-vip-list showed that vip was deleted :
[root@qdev-network-tor01-j1 httpd]# (keystone_admin)] neutron lb-vip-list

[root@qdev-network-tor01-j1 httpd]# (keystone_admin)]

This is user impacting issue since most users will use dashboard, not CLI.
Please take this seriously. Thank you.

Changed in horizon:
assignee: nobody → Tatiana Ovchinnikova (tmazur)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

Fix proposed to branch: master
Review: https://review.openstack.org/184776

Changed in horizon:
status: Confirmed → In Progress
Revision history for this message
Doug Fish (drfish) wrote :

Some extra re-create info for reviewers who may not be familiar with LBaaS:

This is seen on
Project->Network->Load Balancers

To set up the test:
* Create a pool
* on that pool choose the Add VIP action.

To create the failure:
* choose Delete VIP on the pool

Notice that both success and failure messages are shown although the operation is successful.

Your Openstack environment needs to include lbaas in order for Horizon to show this. In devstack you can get this by incluing enable_service q-lbaas in your localrc file.

tags: added: kilo-rc-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/184776
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=05a5ae38774b78ee8ed76b3d347c1ca89dd2fa07
Submitter: Jenkins
Branch: master

commit 05a5ae38774b78ee8ed76b3d347c1ca89dd2fa07
Author: Tatiana Ovchinnikova <email address hidden>
Date: Wed Aug 12 11:46:26 2015 +0300

    Delete VIP action refactoring

    "Delete VIP" is not a batch action so it makes sense to use
    tables.Action instead of tables.DeleteAction to prevent extra
    success message which is in fact incorrect. "Delete VIP" is
    a specific action: there is no separate tab for VIPs. That's
    why pool's id is used for this message. Moreover, a default
    confirmation message is quite confusing too: "You have selected
    <pool name associated with VIP>". This patch adds a custom help
    text with VIP id to this message.

    Closes-Bug: #1439180

    Change-Id: I74c13bcbee56e22d8814e8a4118c906c23e2405e

Changed in horizon:
status: In Progress → Fix Committed
Changed in horizon:
milestone: none → liberty-3
importance: Undecided → Low
Thierry Carrez (ttx)
Changed in horizon:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in horizon:
milestone: liberty-3 → 8.0.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.