Simeon's proposal will be valid only for the deployment of the package - and it should
allow the deployment to pass.
The example from the previous won't work as yum/dns is not using system proxy -> my
bad I didn't realize it earlier.
I guess the task for the engine to use the proxy when installing software would look like
( I haven't tested it,though):
- name: Deploy_proxy
lineinfile:
line: "proxy=http://myproxy.localdomain:3399"
state: "present"
path: "/etc/dnf/dnf.conf"
delegate_to: localhost
Best Regards,
Strahil Nikolov
В вторник, 10 ноември 2020 г., 17:59:29 Гринуич+2, Simon Coter
<simon.coter(a)oracle.com> написа:
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:
On Nov 10, 2020, at 4:45 PM, Matteo Bonardi <mbona92(a)gmail.com>
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 <hunter86_bg(a)yahoo.com> 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_proxy=https://myproxy.localdomain:3340
> 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
> [root@engine ~]# echo $https_proxy
>
https://myproxy.localdomain:3340
> [root@engine ~]# echo $no_proxy
> localhost
>
>
> Best Regards,
> Strahil Nikolov
>
>
>
>
>
>
>
> В вторник, 10 ноември 2020 г., 12:17:52 Гринуич+2, Gianluca Cecchi
<gianluca.cecchi(a)gmail.com> написа:
>
>
>
>
>
> On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi <mbona92(a)gmail.com> wrote:
>>> On Tue, Nov 10, 2020 at 9:14 AM Matteo Bonardi
<mbona92(a)gmail.com> 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/users@ovirt.org/message/D5WQSM7OZNK...
>
> 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 -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> 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/users@ovirt.org/message/RJ4MQDQDJUN...
>
>
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement:
https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!...
oVirt Code of Conduct:
https://urldefense.com/v3/__https://www.ovirt.org/community/about/communi...
List Archives:
https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@o...