Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1613380

Summary: TLS Everywhere: Nova VNC Proxy backend is not TLS enabled
Product: Red Hat OpenStack Reporter: Gregory Charot <gcharot>
Component: puppet-novaAssignee: Martin Schuppert <mschuppe>
Status: CLOSED DUPLICATE QA Contact: OSP DFG:Compute <osp-dfg-compute>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13.0 (Queens)CC: jjoyce, jschluet, mschuppe, nlevinki, slinaber, tvignaud
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-07 13:34:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gregory Charot 2018-08-07 13:11:03 UTC
Description of problem:

When enabling TLS everywhere, the VNC flow itself is encrypted (flow to the compute nodes) however the internal flow from HaProxy to the controllers (nova-novncproxy) is not.

Version-Release number of selected component (if applicable):

13

How reproducible:

Always

Steps to Reproduce:
1. Enable TLS everywhere as per doc
2. Check TLS configuration for nova vncproxy
3.

Actual results:

Haproxy configuration for nova_novncproxy

listen nova_novncproxy
  bind 172.17.1.150:6080 transparent ssl crt /etc/pki/tls/certs/haproxy/overcloud-haproxy-internal_api.pem
  bind 192.168.122.150:13080 transparent ssl crt /etc/pki/tls/private/overcloud_endpoint.pem
  balance source
  http-request set-header X-Forwarded-Proto https if { ssl_fc }
  http-request set-header X-Forwarded-Proto http if !{ ssl_fc }
  option tcpka
  option tcplog
  timeout tunnel 1h
  server lab-controller01.internalapi.redhat.local 172.17.1.17:6080 check fall 5 inter 2000 rise 2 verifyhost lab-controller01.internalapi.redhat.local
  server lab-controller02.internalapi.redhat.local 172.17.1.22:6080 check fall 5 inter 2000 rise 2 verifyhost lab-controller02.internalapi.redhat.local
  server lab-controller03.internalapi.redhat.local 172.17.1.16:6080 check fall 5 inter 2000 rise 2 verifyhost lab-controller03.internalapi.redhat.local


Expected results:

TLS enabled

Additional info:

Comment 1 Martin Schuppert 2018-08-07 13:34:28 UTC

*** This bug has been marked as a duplicate of bug 1613158 ***