tripleo

VIP and nodes are not generated for nova vncproxy

Bug #1621368 reported by Juan Antonio Osorio Robles
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Juan Antonio Osorio Robles
tripleo newton-rc1 "newton-rc1"

Bug Description

Recently, t-h-t is able to set which nodes are running what services and the according VIPs for those. This is not the case for nova vncproxy. this is because the service_name doesn't match the servicenetmap entry.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (master)

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

Changed in tripleo:
assignee: nobody → Juan Antonio Osorio Robles (juan-osorio-robles)
status: New → In Progress
Steven Hardy (shardy)
Changed in tripleo:
milestone: none → newton-rc1
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (master)

Reviewed: https://review.openstack.org/367200
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=b1c32247a2d724294e1d9a5e4df6c48c525ed300
Submitter: Jenkins
Branch: master

commit b1c32247a2d724294e1d9a5e4df6c48c525ed300
Author: Juan Antonio Osorio Robles <email address hidden>
Date: Thu Sep 8 11:21:16 2016 +0300

    Make Nova VNC Proxy service name match service net map

    If these names don't match then we cannot set the service's nodes,
    VIP and network.

    Change-Id: I8f1c0eaf62eee2704a5f2556a553032106db606b
    Closes-Bug: #1621368

Changed in tripleo:
status: In Progress → Fix Released
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.