Deploy oVirt Engine fail behind proxy
Hi, I am trying to deploy the ovirt engine following self-hosted engine installation procedure on documentation. Deployment servers are behind a proxy and I have set it in environment and in yum.conf before run deploy. Deploy fails because ovirt engine vm cannot resolve AppStream repository url: [ INFO ] TASK [ovirt.engine-setup : Install oVirt Engine package] [ ERROR ] fatal: [localhost -> ovirt-manager.mydomain]: FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'AppStream': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=AppStream&infra=stock [Could not resolve host: mirrorlist.centos.org]", "rc": 1, "results": []} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources [ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch logs from the engine VM] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Set destination directory path] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Create destination directory] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Find the local appliance image] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Set local_vm_disk_path] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Copy engine logs] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Remove local vm dir] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Remove temporary entry in /etc/hosts for the local VM] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Clean local storage pools] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Destroy local storage-pool {{ he_local_vm_dir | basename }}] [ INFO ] TASK [ovirt.hosted_engine_setup : Undefine local storage-pool {{ he_local_vm_dir | basename }}] [ INFO ] TASK [ovirt.hosted_engine_setup : Destroy local storage-pool {{ local_vm_disk_path.split('/')[5] }}] [ INFO ] TASK [ovirt.hosted_engine_setup : Undefine local storage-pool {{ local_vm_disk_path.split('/')[5] }}] [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20201109165237.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20201109164244-b3e8sd.log How I can set proxy for the engine vm? Ovirt version: [root@myhost ~]# rpm -qa | grep ovirt-engine-appliance ovirt-engine-appliance-4.4-20200916125954.1.el8.x86_64 [root@myhost ~]# rpm -qa | grep ovirt-hosted-engine-setup ovirt-hosted-engine-setup-2.4.6-1.el8.noarch OS version: [root@myhost ~]# cat /etc/centos-release CentOS Linux release 8.2.2004 (Core) [root@myhost ~]# uname -a Linux myhost.mydomain 4.18.0-193.28.1.el8_2.x86_64 #1 SMP Thu Oct 22 00:20:22 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Thanks for the help. Regards, Matteo
On Tue, Nov 10, 2020 at 9:14 AM Matteo Bonardi <mbona92@gmail.com> wrote:
Hi,
I am trying to deploy the ovirt engine following self-hosted engine installation procedure on documentation. Deployment servers are behind a proxy and I have set it in environment and in yum.conf before run deploy.
Someone recently reported on this list that setting both environment variables http_proxy and https_proxy worked for them. I didn't try this myself recently. Best regards, -- Didi
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.
Hi Didi, Thanks for reply. My proxy settings are the following: [root@myhost ~]# env | grep proxy https_proxy=http://10.248.2.50:3128/ http_proxy=http://10.248.2.50:3128/ ftp_proxy=http://10.248.2.50:3128/ [root@myhost ~]# cat /etc/yum.conf [main] gpgcheck=1 installonly_limit=3 clean_requirements_on_remove=True best=True skip_if_unavailable=False proxy=http://10.248.2.50:3128 Regards, Matteo
I didn't try this myself recently.
Best regards,
On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi <mbona92@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/D5WQSM7OZNKJQK... 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
On Tue, Nov 10, 2020 at 12:18 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi <mbona92@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/D5WQSM7OZNKJQK...
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
Thanks for the update :-) Not sure if this is already expected to work (and was broken at some point) or not. Can one of you please file a bug about this? I am not aware of another workaround, sorry. Best regards, -- Didi
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@gmail.com> написа: On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi <mbona92@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/D5WQSM7OZNKJQK... 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@ovirt.org To unsubscribe send an email to users-leave@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/RJ4MQDQDJUNE67...
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@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@gmail.com> написа:
On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi <mbona92@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/D5WQSM7OZNKJQK...
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@ovirt.org To unsubscribe send an email to users-leave@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/RJ4MQDQDJUNE67...
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 <mbona92@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@yahoo.com <mailto:hunter86_bg@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://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 <gianluca.cecchi@gmail.com <mailto:gianluca.cecchi@gmail.com>> написа:
On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi <mbona92@gmail.com <mailto:mbona92@gmail.com>> 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$>>; 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/D5WQSM7OZNKJQK... <https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@ovirt.org/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 -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> 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/users@ovirt.org/message/RJ4MQDQDJUNE67... <https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@ovirt.org/message/RJ4MQDQDJUNE67FHXI5C5SP62FO6RTLY/__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhOGhJ0KY$>
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!Gq... oVirt Code of Conduct: https://urldefense.com/v3/__https://www.ovirt.org/community/about/community-... List Archives: https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@ovir...
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@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: http://myproxy:3128 Hope this helps. Simon
On Nov 10, 2020, at 4:45 PM, Matteo Bonardi <mbona92@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@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@gmail.com> написа:
On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi <mbona92@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/D5WQSM7OZNKJQK...
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@ovirt.org To unsubscribe send an email to users-leave@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/RJ4MQDQDJUNE67...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!Gq... oVirt Code of Conduct: https://urldefense.com/v3/__https://www.ovirt.org/community/about/community-... List Archives: https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@ovir...
the delegate_to stanza should use the variable for the HostedEngine, but I think this one from the code should work: delegate_to: "{{ groups.engine[0] }}" @Sandro Bonazzola , Maybe we should open a feature request for allowing the installer to deploy a proxy ? I think it's quite common in Enterprise environments . Best Regards, Strahil Nikolov В вторник, 10 ноември 2020 г., 18:57:03 Гринуич+2, Strahil Nikolov <hunter86_bg@yahoo.com> написа: 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@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: http://myproxy:3128 Hope this helps. Simon
On Nov 10, 2020, at 4:45 PM, Matteo Bonardi <mbona92@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@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@gmail.com> написа:
On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi <mbona92@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/D5WQSM7OZNKJQK...
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@ovirt.org To unsubscribe send an email to users-leave@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/RJ4MQDQDJUNE67...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!Gq... oVirt Code of Conduct: https://urldefense.com/v3/__https://www.ovirt.org/community/about/community-... List Archives: https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@ovir...
On Tue, Nov 10, 2020 at 7:18 PM Strahil Nikolov via Users <users@ovirt.org> wrote:
the delegate_to stanza should use the variable for the HostedEngine, but I think this one from the code should work:
delegate_to: "{{ groups.engine[0] }}"
@Sandro Bonazzola , Maybe we should open a feature request for allowing the installer to deploy a proxy ?
I already suggested to open a bug for this earlier in this thread.
I think it's quite common in Enterprise environments .
I am not sure. I talked with Sandro about this, and we agreed that a common enterprise requirement is being able to use a local _mirror_ (e.g. Foreman), mainly for disconnected use (without an Internet connection). A proxy is technically quite different, even if in principle can be used for the same need. Best regards,
Best Regards, Strahil Nikolov
В вторник, 10 ноември 2020 г., 18:57:03 Гринуич+2, Strahil Nikolov <hunter86_bg@yahoo.com> написа:
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@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: http://myproxy:3128
Hope this helps.
Simon
On Nov 10, 2020, at 4:45 PM, Matteo Bonardi <mbona92@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@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@gmail.com> написа:
On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi <mbona92@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/D5WQSM7OZNKJQK...
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@ovirt.org To unsubscribe send an email to users-leave@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/RJ4MQDQDJUNE67...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!Gq... oVirt Code of Conduct: https://urldefense.com/v3/__https://www.ovirt.org/community/about/community-... List Archives: https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@ovir...
Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/L6FM4VPEEBEPDB...
-- Didi
Hi Didi,
On Tue, Nov 10, 2020 at 7:18 PM Strahil Nikolov via Users <users(a)ovirt.org> wrote:
I already suggested to open a bug for this earlier in this thread.
I will open a bug for that.
I am not sure. I talked with Sandro about this, and we agreed that a common enterprise requirement is being able to use a local _mirror_ (e.g. Foreman), mainly for disconnected use (without an Internet connection). A proxy is technically quite different, even if in principle can be used for the same need.
I can understand your point, but since the deploy script already checks that the proxy is set, I don't see why it can't pass this information to the engine.
Best regards,
Regards, Matteo
On Wed, Nov 11, 2020 at 11:49 AM Matteo Bonardi <mbona92@gmail.com> wrote:
Hi Didi,
On Tue, Nov 10, 2020 at 7:18 PM Strahil Nikolov via Users <users(a)ovirt.org> wrote:
I already suggested to open a bug for this earlier in this thread.
I will open a bug for that.
Thanks.
I am not sure. I talked with Sandro about this, and we agreed that a common enterprise requirement is being able to use a local _mirror_ (e.g. Foreman), mainly for disconnected use (without an Internet connection). A proxy is technically quite different, even if in principle can be used for the same need.
I can understand your point, but since the deploy script already checks that the proxy is set, I don't see why it can't pass this information to the engine.
Sorry, where? Also: On Wed, Nov 11, 2020 at 11:39 AM Matteo Bonardi <mbona92@gmail.com> wrote:
Thanks to all yours suggestions I, finally, complete the deploy with success. The solution is been to edit the file /usr/share/ansible/roles/ovirt.engine-setup/tasks/install_packages.yml adding the proxy variable:
Which version? Perhaps you had 4.4.2 and then updated to 4.4.3 before retrying, or something similar?
- name: Install oVirt Engine package package: name: "ovirt-engine" state: present environment: https_proxy: "http://<proxy_host>:<proxy_port>" http_proxy: "http://<proxy_host>:<proxy_port>" ftp_proxy: "http://<proxy_host>:<proxy_port>" when: ovirt_engine_setup_product_type | lower == 'ovirt' [..]
One suggestion for who will have the same problem: This file was created by the first failed run of the deploy. Without run the deploy, this file does not exists. So you have to run the deploy one time, let it fail and then edit the file. I know that it seems a stupid suggestion but i think could help someone.
It's not stupid! :-). I think you unknowingly ran into something caused by the move to ovirt-ansible-roles in 4.4.3 [1]. Until 4.4.2, this file was in the package ovirt-ansible-engine-setup , in: /usr/share/ansible/roles/ovirt.engine-setup/tasks/install_packages.yml In 4.4.3, this file, along with many others (including hosted-engine ansible code), is in ovirt-ansible-collection, in: /usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/install_packages.yml Can't guess, though, your exact flow - if you suspect a bug, please check/share relevant logs (including dnf, but perhaps also ansible), perhaps in a separate bug. Sorry if this is confusing/messy. Feel free to comment on [1] if you have something specific to add (it's a RHV bug, though, so if unsure, perhaps file another bug. RHV's and oVirt's documentation are not as aligned as their source code). [1] https://bugzilla.redhat.com/show_bug.cgi?id=1891749 Thanks and best regards, -- Didi
On Wed, Nov 11, 2020 at 11:05 AM Yedidyah Bar David <didi@redhat.com> wrote: [snip]
One suggestion for who will have the same problem:
This file was created by the first failed run of the deploy. Without run the deploy, this file does not exists. So you have to run the deploy one time, let it fail and then edit the file. I know that it seems a stupid suggestion but i think could help someone.
It's not stupid! :-). I think you unknowingly ran into something caused by the move to ovirt-ansible-roles in 4.4.3 [1].
Until 4.4.2, this file was in the package ovirt-ansible-engine-setup , in:
/usr/share/ansible/roles/ovirt.engine-setup/tasks/install_packages.yml
In 4.4.3, this file, along with many others (including hosted-engine ansible code), is in ovirt-ansible-collection, in:
/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/install_packages.yml
Uhm... Can this be related in any way with my dependency problems updating engine from 4.4.2 to 4.4.3, as described in the thread just opened here: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/JEZZ5CMFM4EFKT3... ? Gianluca
On Wed, Nov 11, 2020 at 12:14 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Wed, Nov 11, 2020 at 11:05 AM Yedidyah Bar David <didi@redhat.com> wrote:
[snip]
One suggestion for who will have the same problem: This file was created by the first failed run of the deploy. Without run the deploy, this file does not exists. So you have to run the deploy one time, let it fail and then edit the file. I know that it seems a stupid suggestion but i think could help someone.
It's not stupid! :-). I think you unknowingly ran into something caused by the move to ovirt-ansible-roles in 4.4.3 [1].
Until 4.4.2, this file was in the package ovirt-ansible-engine-setup , in:
/usr/share/ansible/roles/ovirt.engine-setup/tasks/install_packages.yml
In 4.4.3, this file, along with many others (including hosted-engine ansible code), is in ovirt-ansible-collection, in:
/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/install_packages.yml
Uhm... Can this be related in any way with my dependency problems updating engine from 4.4.2 to 4.4.3, as described in the thread just opened here: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/JEZZ5CMFM4EFKT3...
I am aware of your other thread, might reply later (or I hope someone else will do the investigation...). I do not think it's strictly related, but not sure yet. Yours was on the engine machine, whereas current is about a host (hosted-engine) machine. Thanks anyway :-), -- Didi
Il giorno mer 11 nov 2020 alle ore 11:01 Yedidyah Bar David <didi@redhat.com> ha scritto:
On Wed, Nov 11, 2020 at 11:49 AM Matteo Bonardi <mbona92@gmail.com> wrote:
Hi Didi,
On Tue, Nov 10, 2020 at 7:18 PM Strahil Nikolov via Users <users(a)ovirt.org> wrote:
I already suggested to open a bug for this earlier in this thread.
I will open a bug for that.
Thanks.
I am not sure. I talked with Sandro about this, and we agreed that a common enterprise requirement is being able to use a local _mirror_ (e.g. Foreman), mainly for disconnected use (without an Internet connection). A proxy is technically quite different, even if in principle can be used for the same need.
I can understand your point, but since the deploy script already checks
that the proxy is set, I don't see why it can't pass this information to the engine.
Sorry, where?
Sincerely I didn't read the code, but reading the log there are more than one reference to proxy. For example: 2020-11-10 18:15:48,518+0100 WARNING otopi.plugins.gr_he_common.network.gateway gateway._setup:88 It seems that this host is configured to use a *proxy*, please ensure that this host will be able to reach the engine VM trough that proxy or add a specific exception. 2020-11-10 18:15:49,637+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:197 ansible-playbook: env: {'LS_COLORS': [..], 'USER': 'root', 'PWD': '', 'HOME': '', 'SSH_CLIENT': '', *'https_proxy': 'http://10.248.2.50:3128/ <http://10.248.2.50:3128/>', 'http_proxy': 'http://10.248.2.50:3128/ <http://10.248.2.50:3128/>', 'no_proxy': '<my_engine>.<my_domain>'*, 'SSH_TTY': '/dev/pts/0', 'MAIL': '/var/spool/mail/root', 'SHELL': '/bin/bash', 'TERM': 'xterm', 'SHLVL': '1', 'PYTHONPATH': '/usr/share/ovirt-hosted-engine-setup/scripts/..:',[..], 'HE_ANSIBLE_LOG_PATH': '/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-ansible-get_network_interfaces-20201110181549-tppuv6.log'} 2020-11-10 18:17:11,505+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:111 TASK [ovirt.ovirt.hosted_engine_setup : *Check http/https proxy*] I'm not sure at all, but the log makes me think the proxy is being checked more than once. Of course I can be wrong.
Also:
On Wed, Nov 11, 2020 at 11:39 AM Matteo Bonardi <mbona92@gmail.com> wrote:
Thanks to all yours suggestions I, finally, complete the deploy with
success.
The solution is been to edit the file /usr/share/ansible/roles/ovirt.engine-setup/tasks/install_packages.yml adding the proxy variable:
Which version?
Perhaps you had 4.4.2 and then updated to 4.4.3 before retrying, or something similar?
Before retry the deploy, I have completely cleanup the installation with: [root@<my-host> ~]# ovirt-hosted-engine-cleanup [root@<my-host> ~]# yum remove ovirt-* And then reinstall all: [root@<my-host> ~]# yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm [root@<my-host> ~]# yum install ovirt-engine-appliance [root@<my-host> ~]# yum install ovirt-hosted-engine-setup I am a bit confused on how to check the version (it is embarrassing, but I am new on ovirt and ansible). There is a mismatch between the version in deployment server and in engine vm. I have attached the rpm version of both. The manager web console shows 4.4.2 as version.
- name: Install oVirt Engine package package: name: "ovirt-engine" state: present environment: https_proxy: "http://<proxy_host>:<proxy_port>" http_proxy: "http://<proxy_host>:<proxy_port>" ftp_proxy: "http://<proxy_host>:<proxy_port>" when: ovirt_engine_setup_product_type | lower == 'ovirt' [..]
One suggestion for who will have the same problem: This file was created by the first failed run of the deploy. Without run the deploy, this file does not exists. So you have to run the deploy one time, let it fail and then edit the
file.
I know that it seems a stupid suggestion but i think could help someone.
It's not stupid! :-). I think you unknowingly ran into something caused by the move to ovirt-ansible-roles in 4.4.3 [1].
Until 4.4.2, this file was in the package ovirt-ansible-engine-setup , in:
/usr/share/ansible/roles/ovirt.engine-setup/tasks/install_packages.yml
In 4.4.3, this file, along with many others (including hosted-engine ansible code), is in ovirt-ansible-collection, in:
/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/install_packages.yml
Can't guess, though, your exact flow - if you suspect a bug, please check/share relevant logs (including dnf, but perhaps also ansible), perhaps in a separate bug.
Sorry if this is confusing/messy. Feel free to comment on [1] if you have something specific to add (it's a RHV bug, though, so if unsure, perhaps file another bug. RHV's and oVirt's documentation are not as aligned as their source code).
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1891749
Thanks and best regards, -- Didi
Regards, Matteo
On Thu, Nov 12, 2020 at 9:32 AM Matteo Bonardi <mbona92@gmail.com> wrote:
Il giorno mer 11 nov 2020 alle ore 11:01 Yedidyah Bar David <didi@redhat.com> ha scritto:
On Wed, Nov 11, 2020 at 11:49 AM Matteo Bonardi <mbona92@gmail.com> wrote:
Hi Didi,
On Tue, Nov 10, 2020 at 7:18 PM Strahil Nikolov via Users <users(a)ovirt.org> wrote:
I already suggested to open a bug for this earlier in this thread.
I will open a bug for that.
Thanks.
I am not sure. I talked with Sandro about this, and we agreed that a common enterprise requirement is being able to use a local _mirror_ (e.g. Foreman), mainly for disconnected use (without an Internet connection). A proxy is technically quite different, even if in principle can be used for the same need.
I can understand your point, but since the deploy script already checks that the proxy is set, I don't see why it can't pass this information to the engine.
Sorry, where?
Sincerely I didn't read the code, but reading the log there are more than one reference to proxy. For example:
2020-11-10 18:15:48,518+0100 WARNING otopi.plugins.gr_he_common.network.gateway gateway._setup:88 It seems that this host is configured to use a proxy, please ensure that this host will be able to reach the engine VM trough that proxy or add a specific exception.
You are right. This was added for: https://bugzilla.redhat.com/show_bug.cgi?id=1387146 The request there wasn't for full proxy support, just a warning.
2020-11-10 18:15:49,637+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:197 ansible-playbook: env: {'LS_COLORS': [..], 'USER': 'root', 'PWD': '', 'HOME': '', 'SSH_CLIENT': '', 'https_proxy': 'http://10.248.2.50:3128/', 'http_proxy': 'http://10.248.2.50:3128/', 'no_proxy': '<my_engine>.<my_domain>', 'SSH_TTY': '/dev/pts/0', 'MAIL': '/var/spool/mail/root', 'SHELL': '/bin/bash', 'TERM': 'xterm', 'SHLVL': '1', 'PYTHONPATH': '/usr/share/ovirt-hosted-engine-setup/scripts/..:',[..], 'HE_ANSIBLE_LOG_PATH': '/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-ansible-get_network_interfaces-20201110181549-tppuv6.log'}
This just logs all env vars when running ansible.
2020-11-10 18:17:11,505+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:111 TASK [ovirt.ovirt.hosted_engine_setup : Check http/https proxy]
Similarly. Was added for: https://bugzilla.redhat.com/1588720 And to further clarify. Adding full proxy support requires: 1. Some design and development work 2. Routinely testing deployment with a proxy 3. Fix new bugs as they are found It's not clear this is worth it. That said, patches are welcome :-). To consider including it, it should obviously be written so that it also seamlessly works without a proxy. Thanks and best regards,
I'm not sure at all, but the log makes me think the proxy is being checked more than once. Of course I can be wrong.
Also:
On Wed, Nov 11, 2020 at 11:39 AM Matteo Bonardi <mbona92@gmail.com> wrote:
Thanks to all yours suggestions I, finally, complete the deploy with success. The solution is been to edit the file /usr/share/ansible/roles/ovirt.engine-setup/tasks/install_packages.yml adding the proxy variable:
Which version?
Perhaps you had 4.4.2 and then updated to 4.4.3 before retrying, or something similar?
Before retry the deploy, I have completely cleanup the installation with:
[root@<my-host> ~]# ovirt-hosted-engine-cleanup [root@<my-host> ~]# yum remove ovirt-*
And then reinstall all:
[root@<my-host> ~]# yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm [root@<my-host> ~]# yum install ovirt-engine-appliance [root@<my-host> ~]# yum install ovirt-hosted-engine-setup
I am a bit confused on how to check the version (it is embarrassing, but I am new on ovirt and ansible). There is a mismatch between the version in deployment server and in engine vm. I have attached the rpm version of both. The manager web console shows 4.4.2 as version.
- name: Install oVirt Engine package package: name: "ovirt-engine" state: present environment: https_proxy: "http://<proxy_host>:<proxy_port>" http_proxy: "http://<proxy_host>:<proxy_port>" ftp_proxy: "http://<proxy_host>:<proxy_port>" when: ovirt_engine_setup_product_type | lower == 'ovirt' [..]
One suggestion for who will have the same problem: This file was created by the first failed run of the deploy. Without run the deploy, this file does not exists. So you have to run the deploy one time, let it fail and then edit the file. I know that it seems a stupid suggestion but i think could help someone.
It's not stupid! :-). I think you unknowingly ran into something caused by the move to ovirt-ansible-roles in 4.4.3 [1].
Until 4.4.2, this file was in the package ovirt-ansible-engine-setup , in:
/usr/share/ansible/roles/ovirt.engine-setup/tasks/install_packages.yml
In 4.4.3, this file, along with many others (including hosted-engine ansible code), is in ovirt-ansible-collection, in:
/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/install_packages.yml
Can't guess, though, your exact flow - if you suspect a bug, please check/share relevant logs (including dnf, but perhaps also ansible), perhaps in a separate bug.
Sorry if this is confusing/messy. Feel free to comment on [1] if you have something specific to add (it's a RHV bug, though, so if unsure, perhaps file another bug. RHV's and oVirt's documentation are not as aligned as their source code).
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1891749
Thanks and best regards, -- Didi
Regards, Matteo
-- Didi
Define ‘proxy’ with /etc/yum.conf. From: Simon Coter <simon.coter@oracle.com> Sent: Tuesday, November 10, 2020 9:59 AM To: Matteo Bonardi <mbona92@gmail.com> Cc: Strahil Nikolov <hunter86_bg@yahoo.com>; users <users@ovirt.org> Subject: [ovirt-users] Re: Deploy oVirt Engine fail behind proxy 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 Hope this helps. Simon On Nov 10, 2020, at 4:45 PM, Matteo Bonardi <mbona92@gmail.com<mailto:mbona92@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@yahoo.com<mailto:hunter86_bg@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://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 <gianluca.cecchi@gmail.com<mailto:gianluca.cecchi@gmail.com>> написа: On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi <mbona92@gmail.com<mailto:mbona92@gmail.com>> 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$>>; 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/D5WQSM7OZNKJQK3L5CN367W2TRVZZVHZ/<https://urldefense.com/v3/__https:/lists.ovirt.org/archives/list/users@ovirt.org/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 -- users@ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org<mailto:users-leave@ovirt.org> 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/users@ovirt.org/message/RJ4MQDQDJUNE67FHXI5C5SP62FO6RTLY/<https://urldefense.com/v3/__https:/lists.ovirt.org/archives/list/users@ovirt.org/message/RJ4MQDQDJUNE67FHXI5C5SP62FO6RTLY/__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhOGhJ0KY$> _______________________________________________ Users mailing list -- users@ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhD-SJE5g$<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$<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/users@ovirt.org/message/X6DEOI4SGSQ2GWMFPB76NQL6E5U7SETN/__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhPkJL46A$<https://urldefense.com/v3/__https:/lists.ovirt.org/archives/list/users@ovirt.org/message/X6DEOI4SGSQ2GWMFPB76NQL6E5U7SETN/__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhPkJL46A$>
Usually when you deploy via cockpit, the last step allows you to edit the playbook (I'm not sure if it was only for gluster or overall). Otherwise, you have to find the ansible playbooks on the host where the deployment is going on . On my 4.3 host there is a directory named: /usr/share/ansible/roles/ovirt.hosted_engine_setup I guess you can run a grep in that dir (use -R for recursive) to find the task name that failed /it's in your previous e-mail/ and then I guess you can put it somewhere before that. Best Regards, Strahil Nikolov В вторник, 10 ноември 2020 г., 17:45:48 Гринуич+2, Matteo Bonardi <mbona92@gmail.com> написа: 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@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@gmail.com> написа:
On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi <mbona92@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/D5WQSM7OZNKJQK...
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@ovirt.org To unsubscribe send an email to users-leave@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/RJ4MQDQDJUNE67...
Thanks to all yours suggestions I, finally, complete the deploy with success. The solution is been to edit the file /usr/share/ansible/roles/ovirt.engine-setup/tasks/install_packages.yml adding the proxy variable: - name: Install oVirt Engine package package: name: "ovirt-engine" state: present environment: https_proxy: "http://<proxy_host>:<proxy_port>" http_proxy: "http://<proxy_host>:<proxy_port>" ftp_proxy: "http://<proxy_host>:<proxy_port>" when: ovirt_engine_setup_product_type | lower == 'ovirt' [..] One suggestion for who will have the same problem: This file was created by the first failed run of the deploy. Without run the deploy, this file does not exists. So you have to run the deploy one time, let it fail and then edit the file. I know that it seems a stupid suggestion but i think could help someone. Thank you all for the help! Best regards, Matteo
Thank you for all the information provided. For OLVM (i dont know if only for them) this helped me: # touch /etc/profile.d/proxy.sh # chown root:root /etc/profile.d/proxy.sh # chmod 644 /etc/profile.d/proxy.sh # vi /etc/profile.d/proxy.sh --- ###########proxy export http_proxy=http://<PROXY_FQDN/IP>:<port> export HTTPS_PROXY=http://<PROXY_FQDN/IP>:<port> export https_proxy=http://<PROXY_FQDN/IP>:<port> export HTTP_PROXY=http://<PROXY_FQDN/IP>:<port> export no_proxy=localhost,127.0.0.1,<Self_Hosted_Engine_FQDN> --- # source /etc/profile.d/proxy.sh (Load configuration for current session) Make sure you have set proxy in /etc/yum.conf and/or /etc/dnf/dnf.conf Add extra vars to the deployment command: # touch /root/extra-vars.yml # vi /root/extra-vars.yml --- he_pause_host: true he_proxy: http://<PROXY_FQDN/IP>:<port> --- # hosted-engine --deploy --restore-from-file=backup_file --ansible-extra-vars="@/root/extra-vars.yml" Best regards, Rok
participants (7)
-
Gianluca Cecchi -
Matteo Bonardi -
Matthew.Stier＠fujitsu.com -
rokxer＠gmail.com -
Simon Coter -
Strahil Nikolov -
Yedidyah Bar David