Unable to change network for VNC Proxy

Bug #1712048 reported by Juan Antonio Osorio Robles on 2017-08-21
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Medium
Juan Antonio Osorio Robles

Bug Description

The VNC Proxy seems to be configured to use the Nova API network [1] which means that configuring the VNC Proxy's network via the service map will have no effect. We should be using the ServiceNetMap to configure it.

[1] https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/nova-vnc-proxy.yaml#L74

Changed in tripleo:
importance: Undecided → Medium
milestone: none → pike-rc1
Changed in tripleo:
status: New → Triaged
assignee: nobody → Juan Antonio Osorio Robles (juan-osorio-robles)

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

Changed in tripleo:
status: Triaged → In Progress

Change abandoned by Juan Antonio Osorio Robles (<email address hidden>) on branch: master
Review: https://review.openstack.org/495848

Changed in tripleo:
milestone: pike-rc1 → pike-rc2
Changed in tripleo:
milestone: pike-rc2 → queens-1
Alex Schultz (alex-schultz) wrote :

Moving backed to triaged since the patch was abandoned. Is this still needed?

Changed in tripleo:
status: In Progress → Triaged
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Changed in tripleo:
milestone: stein-2 → stein-3
Changed in tripleo:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers