senlin

vip of lb policy should be exposed to end user

Bug #1558930 reported by Yanyan Hu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
senlin
Fix Released
Undecided
Yanyan Hu

Bug Description

In cases user doesn't specify fix VIP address in lb policy spec, the VIP address allocated randomly is not exposed to end user.

Yanyan Hu (yanyanhu)
Changed in senlin:
assignee: nobody → Yanyan Hu (yanyanhu)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to senlin (master)

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

Changed in senlin:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to senlin (master)

Reviewed: https://review.openstack.org/294450
Committed: https://git.openstack.org/cgit/openstack/senlin/commit/?id=62ab1d31d352c10f056dcc99f66c7878e0e551f0
Submitter: Jenkins
Branch: master

commit 62ab1d31d352c10f056dcc99f66c7878e0e551f0
Author: yanyanhu <email address hidden>
Date: Fri Mar 18 03:40:41 2016 -0400

    Store random assigned VIP address to cluster data

    User is allowed to define lb policy without specifying VIP address.
    In that case, a random VIP address will be allocated during lb policy
    attaching which should be exposed to end user through cluster data.
    This patch addresses this issue.

    Closes-Bug: #1558930
    Change-Id: I9579dfa79563e9ac3868abf552687a2cdb5827b9

Changed in senlin:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/senlin 1.0.0.0rc1

This issue was fixed in the openstack/senlin 1.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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