On Thu, Aug 11, 2016 at 5:44 PM, Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
On Thu, Aug 11, 2016 at 4:40 PM, Amit Aviram
<aaviram(a)redhat.com> wrote:
>
> On Thu, Aug 11, 2016 at 5:39 PM, Amit Aviram <aaviram(a)redhat.com> wrote:
>
>> Due to bug:
>>
https://bugzilla.redhat.com/show_bug.cgi?id=1365451
>>
>> There will need to be special configurations to do, in order to run
>> ovirt-imageio-proxy after upgrade. we are making best efforts to publish
>> this fix asap
>>
>
> (patch is merged in master, will be available in the next build)
>
>
>>
>>
Ok, I read the bug. for the missing pki. In fact in conf file I see
reference to missing
# Key file for SSL connections
ssl_key_file = /etc/pki/ovirt-engine/keys/imageio-proxy.key.nopass
# Certificate file for SSL connections
ssl_cert_file = /etc/pki/ovirt-engine/certs/imageio-proxy.cer
In the mean time I see that if I change the default in
/etc/ovirt-imageio-proxy/ovirt-imageio-proxy.conf
from
# Wrap incoming connections with SSL
use_ssl = true
to
# Wrap incoming connections with SSL
use_ssl = false
The service starts and it seems it listens to tcp port 54323.
Could it be a workaround (wit the limitations of not secure trasnport) or
is it anyway designed to only work through SSL?
Yes, supposed to work. if not for HTTPS connection to ovirt, probably for
HTTP.