vncproxy warnings due to class includes

[Matt Fischer]

Due to changes made earlier this year there is duplicated vncproxy settings in vncproxy.pp and vncproxy/common.pp. Compute.pp includes the latter, but not the former. Then common.pp tries to read values from vncproxy.pp causing warnings:

Warning: Scope(Class[Nova::Vncproxy::Common]): Could not look up qualified variable '::nova::vncproxy::host'; class ::nova::vncproxy has not been evaluated
Warning: Scope(Class[Nova::Vncproxy::Common]): Could not look up qualified variable '::nova::vncproxy::vncproxy_protocol'; class ::nova::vncproxy has not been evaluated
Warning: Scope(Class[Nova::Vncproxy::Common]): Could not look up qualified variable '::nova::vncproxy::port'; class ::nova::vncproxy has not been evaluated
Warning: Scope(Class[Nova::Vncproxy::Common]): Could not look up qualified variable '::nova::vncproxy::vncproxy_path'; class ::nova::vncproxy has not been evaluated

To simplify:

nova::compute includes nova::vncproxy::common which references nova::vncproxy which is unevaluated in this case.

[Emilien Macchi (emilienm)]

Matt, I've seen that: https://review.openstack.org/#/c/255529/
I think it's related :-)