[ovirt-users] Re: Deploy oVirt Engine fail behind proxy

Simon Coter Tue, 10 Nov 2020 09:25:19 -0800

Hi Matteo,

this one is the solution we’ve applied on OLVM that should also work for oVirt:


Before Deploying Self Hosted Engine(SHE) update the below lines in 
/usr/share/ansible/roles/ovirt.hosted-engine-setup/hooks/enginevm_before_engine_setup/install_pre_setup_packages.yml

From

- name:Install oVirt Engine packages for restoring backup
package:
name: "ovirt-engine"
state: present
when: ovirt_engine_setup_product_type | lower == 'ovirt'
 To

-name: Install oVirt Engine packages for restoring backup
package:
     name: "ovirt-engine"
     state: present
environment:
         https_proxy: <proxy>
         http_proxy: <proxy>
when: ovirt_engine_setup_product_type | lower == 'ovirt'
 
In place of <proxy> add your own proxy; example: http://myproxy:3128 
<http://myproxy:3128/>

Hope this helps.

Simon

> On Nov 10, 2020, at 4:45 PM, Matteo Bonardi <[email protected]> wrote:
> 
> Hi Strahil,
> 
> How can I define that task and pass it to the deploy?
> 
> Thanks,
> Matteo
> 
> Il mar 10 nov 2020, 16:33 Strahil Nikolov <[email protected] 
> <mailto:[email protected]>> ha scritto:
> Did anyone try to define a task to deploy the variables in the HostedEngine 
> before the task?
> 
> For example (take only the task):
> ---
> - name: Deploy proxy
>  hosts: localhost
>  tasks:
>  - name: Deploy_proxy
>    blockinfile:
>      block:
>        http_proxy=http://myproxy.localdomain:3399 
> <https://urldefense.com/v3/__http://myproxy.localdomain:3399__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhPGweMje$>
>        https_proxy=https://myproxy.localdomain:3340 
> <https://urldefense.com/v3/__https://myproxy.localdomain:3340__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhMsw9Zdf$>
>        no_proxy=localhost
>      create: True
>      mode: "0444"
>      owner: "root"
>      selevel: "s0"
>      serole: "object_r"
>      setype: "bin_t"
>      seuser: "system_u"
>      state: "present"
>      path: "/etc/profile.d/proxy.sh"
>    delegate_to: localhost
> 
> And the result is:
> [root@engine ~]# echo $http_proxy
> http://myproxy.localdomain:3399 
> <https://urldefense.com/v3/__http://myproxy.localdomain:3399__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhPGweMje$>
> [root@engine ~]# echo $https_proxy
> https://myproxy.localdomain:3340 
> <https://urldefense.com/v3/__https://myproxy.localdomain:3340__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhMsw9Zdf$>
> [root@engine ~]# echo $no_proxy    
> localhost
> 
> 
> Best Regards,
> Strahil Nikolov
> 
> 
> 
> 
> 
> 
> 
> В вторник, 10 ноември 2020 г., 12:17:52 Гринуич+2, Gianluca Cecchi 
> <[email protected] <mailto:[email protected]>> написа: 
> 
> 
> 
> 
> 
> On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi <[email protected] 
> <mailto:[email protected]>> wrote:
> >> On Tue, Nov 10, 2020 at 9:14 AM Matteo Bonardi <mbona92(a)gmail.com 
> >> <https://urldefense.com/v3/__http://gmail.com__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhA4tE7wC$>&gt;
> >>  wrote:
> >> 
> >> Someone recently reported on this list that setting both environment
> >> variables http_proxy and https_proxy worked for them.
> > 
> > 
> 
> yes it was me here:
> https://lists.ovirt.org/archives/list/[email protected]/message/D5WQSM7OZNKJQK3L5CN367W2TRVZZVHZ/
>  
> <https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/[email protected]/message/D5WQSM7OZNKJQK3L5CN367W2TRVZZVHZ/__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhA-KoBa4$>
> 
> But in my case it was simpler because the engine was external.
> With hosted engine it is indeed a problem that should be addressed I think
> 
> Gianluca
> 
> 
> _______________________________________________
> Users mailing list -- [email protected] <mailto:[email protected]>
> To unsubscribe send an email to [email protected] 
> <mailto:[email protected]>
> Privacy Statement: https://www.ovirt.org/privacy-policy.html 
> <https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhD-SJE5g$>
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/ 
> <https://urldefense.com/v3/__https://www.ovirt.org/community/about/community-guidelines/__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhMOe5kNF$>
> List Archives: 
> https://lists.ovirt.org/archives/list/[email protected]/message/RJ4MQDQDJUNE67FHXI5C5SP62FO6RTLY/
>  
> <https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/[email protected]/message/RJ4MQDQDJUNE67FHXI5C5SP62FO6RTLY/__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhOGhJ0KY$>
> 
> _______________________________________________
> Users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Privacy Statement: 
> https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhD-SJE5g$
>  
> oVirt Code of Conduct: 
> https://urldefense.com/v3/__https://www.ovirt.org/community/about/community-guidelines/__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhMOe5kNF$
>  
> List Archives: 
> https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/[email protected]/message/X6DEOI4SGSQ2GWMFPB76NQL6E5U7SETN/__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhPkJL46A$
>

_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/565SCOWFFQ3Z3VVV56KMF3JMS4E2T7BU/

[ovirt-users] Re: Deploy oVirt Engine fail behind proxy

Reply via email to