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

2024-03-27 Thread rokxer
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://:
export HTTPS_PROXY=http://:
export https_proxy=http://:
export HTTP_PROXY=http://:
export no_proxy=localhost,127.0.0.1,
---
# 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://:
---

# hosted-engine --deploy --restore-from-file=backup_file 
--ansible-extra-vars="@/root/extra-vars.yml"

Best regards,
Rok
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/YY42NF5XCHO7I3PBXIEZ6O7C3LRT6XDA/


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

2020-11-17 Thread Yedidyah Bar David
On Thu, Nov 12, 2020 at 9:32 AM Matteo Bonardi  wrote:
>
>
>
> Il giorno mer 11 nov 2020 alle ore 11:01 Yedidyah Bar David  
> ha scritto:
>>
>> On Wed, Nov 11, 2020 at 11:49 AM Matteo Bonardi  wrote:
>> >
>> > Hi Didi,
>> >
>> > > On Tue, Nov 10, 2020 at 7:18 PM Strahil Nikolov via Users
>> > > > > >
>> > > 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': 
> '.', '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  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@ ~]# ovirt-hosted-engine-cleanup
> [root@ ~]# yum remove ovirt-*
>
> And then reinstall all:
>
> [root@ ~]# yum install 
> https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
> [root@ ~]# yum install ovirt-engine-appliance
> [root@ ~]# 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://:"
>> > http_proxy: "http://:"
>> > ftp_proxy: "http://:"
>> >   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:
>>
>> 

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

2020-11-11 Thread Matteo Bonardi
Il giorno mer 11 nov 2020 alle ore 11:01 Yedidyah Bar David 
ha scritto:

> On Wed, Nov 11, 2020 at 11:49 AM Matteo Bonardi  wrote:
> >
> > Hi Didi,
> >
> > > On Tue, Nov 10, 2020 at 7:18 PM Strahil Nikolov via Users
> > >  > >
> > > 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_proxy': 'http://10.248.2.50:3128/
', 'no_proxy': '.'*,
'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  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@ ~]# ovirt-hosted-engine-cleanup
[root@ ~]# yum remove ovirt-*

And then reinstall all:

[root@ ~]# yum install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
[root@ ~]# yum install ovirt-engine-appliance
[root@ ~]# 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://:"
> > http_proxy: "http://:"
> > ftp_proxy: "http://:"
> >   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

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

2020-11-11 Thread Yedidyah Bar David
On Wed, Nov 11, 2020 at 12:14 PM Gianluca Cecchi
 wrote:
>
> On Wed, Nov 11, 2020 at 11:05 AM Yedidyah Bar David  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/JEZZ5CMFM4EFKT3637BZZDBRJCQYVFRH/

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
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/M7HL4RBE3LEMZ5X5DUKSURI72UEMVHYW/


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

2020-11-11 Thread Gianluca Cecchi
On Wed, Nov 11, 2020 at 11:05 AM Yedidyah Bar David  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/JEZZ5CMFM4EFKT3637BZZDBRJCQYVFRH/

?

Gianluca
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/WHNSXCR33AL6VSQQNX3N6CRFOMM5JJR5/


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

2020-11-11 Thread Yedidyah Bar David
On Wed, Nov 11, 2020 at 11:49 AM Matteo Bonardi  wrote:
>
> Hi Didi,
>
> > On Tue, Nov 10, 2020 at 7:18 PM Strahil Nikolov via Users
> >  >
> > 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  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://:"
> http_proxy: "http://:"
> ftp_proxy: "http://:"
>   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
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/55HJDO63UT6XQPEIPPPB2GLUVMDTJXT7/


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

2020-11-11 Thread Matteo Bonardi
Hi Didi,

> On Tue, Nov 10, 2020 at 7:18 PM Strahil Nikolov via Users
>  
> 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
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/47RCLJWNUXFCALQ5ZYISEE2CYDT3AY4Q/


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

2020-11-11 Thread Matteo Bonardi
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://:"
http_proxy: "http://:"
ftp_proxy: "http://:"
  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
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/IMHIBGCFIED32NIOBZCUXIPVAGFNSDJZ/


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

2020-11-11 Thread Yedidyah Bar David
On Tue, Nov 10, 2020 at 7:18 PM Strahil Nikolov via Users
 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 
>  написа:
>
>
>
>
>
> 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 
>  написа:
>
>
>
>
>
> 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: 
>  http_proxy: 
> when: ovirt_engine_setup_product_type | lower == 'ovirt'
>
> In place of  add your own proxy; example: http://myproxy:3128
>
> Hope this helps.
>
> Simon
>
> > On Nov 10, 2020, at 4:45 PM, Matteo Bonardi  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  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 
> >>  написа:
> >>
> >>
> >>
> >>
> >>
> >> On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi  wrote:
>  On Tue, Nov 10, 2020 at 9:14 AM Matteo Bonardi   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/
> >>
> >> 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-le...@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/RJ4MQDQDJUNE67FHXI5C5SP62FO6RTLY/
> >>
> >>
> > ___
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to 

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

2020-11-10 Thread matthew.st...@fujitsu.com
Define ‘proxy’ with /etc/yum.conf.

From: Simon Coter 
Sent: Tuesday, November 10, 2020 9:59 AM
To: Matteo Bonardi 
Cc: Strahil Nikolov ; users 
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: 
 http_proxy: 
when: ovirt_engine_setup_product_type | lower == 'ovirt'

In place of  add your own proxy; example: http://myproxy:3128

Hope this helps.

Simon


On Nov 10, 2020, at 4:45 PM, Matteo Bonardi 
mailto:mbon...@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 
mailto:hunter86...@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 
mailto:gianluca.cec...@gmail.com>> написа:





On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi 
mailto:mbon...@gmail.com>> wrote:
>> On Tue, Nov 10, 2020 at 9:14 AM Matteo Bonardi 
>> 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-le...@ovirt.org<mailto:users-le...@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-le...@

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

2020-11-10 Thread Simon Coter
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: 
 http_proxy: 
when: ovirt_engine_setup_product_type | lower == 'ovirt'
 
In place of  add your own proxy; example: http://myproxy:3128 


Hope this helps.

Simon

> On Nov 10, 2020, at 4:45 PM, Matteo Bonardi  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  > 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 
> mailto:gianluca.cec...@gmail.com>> написа: 
> 
> 
> 
> 
> 
> On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi  > wrote:
> >> On Tue, Nov 10, 2020 at 9:14 AM Matteo Bonardi  >> 
> >>  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/
>  
> 
> 
> 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-le...@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/RJ4MQDQDJUNE67FHXI5C5SP62FO6RTLY/
>  
> 
> 
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: 
> https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhD-SJE5g$
>  
> oVirt Code of Conduct: 
> 

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

2020-11-10 Thread Strahil Nikolov via Users
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 
 написа: 





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 
 написа: 





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: 
         http_proxy: 
when: ovirt_engine_setup_product_type | lower == 'ovirt'
 
In place of  add your own proxy; example: http://myproxy:3128

Hope this helps.

Simon

> On Nov 10, 2020, at 4:45 PM, Matteo Bonardi  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  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 
>>  написа: 
>> 
>> 
>> 
>> 
>> 
>> On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi  wrote:
 On Tue, Nov 10, 2020 at 9:14 AM Matteo Bonardi >>> 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/
>> 
>> 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-le...@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/RJ4MQDQDJUNE67FHXI5C5SP62FO6RTLY/
>> 
>> 
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> 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/users@ovirt.org/message/X6DEOI4SGSQ2GWMFPB76NQL6E5U7SETN/__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhPkJL46A$
>  
___
Users mailing list -- users@ovirt.org
To unsubscribe send an 

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

2020-11-10 Thread Strahil Nikolov via Users
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 
 написа: 





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: 
         http_proxy: 
when: ovirt_engine_setup_product_type | lower == 'ovirt'
 
In place of  add your own proxy; example: http://myproxy:3128

Hope this helps.

Simon

> On Nov 10, 2020, at 4:45 PM, Matteo Bonardi  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  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 
>>  написа: 
>> 
>> 
>> 
>> 
>> 
>> On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi  wrote:
 On Tue, Nov 10, 2020 at 9:14 AM Matteo Bonardi >>> 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/
>> 
>> 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-le...@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/RJ4MQDQDJUNE67FHXI5C5SP62FO6RTLY/
>> 
>> 
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> 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/users@ovirt.org/message/X6DEOI4SGSQ2GWMFPB76NQL6E5U7SETN/__;!!GqivPVa7Brio!JHkvRkiLdGTkZ9bIiVhZDaA8jR8Qfb_WIHV3oQYAfjyTMX_L4QpqMnmlhPkJL46A$
>  
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/2UMZK2JA5L4OUFHWNEXI3WLH5ZD6XRHJ/


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

2020-11-10 Thread Strahil Nikolov via Users
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 
 написа: 





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  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 
>  написа: 
> 
> 
> 
> 
> 
> On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi  wrote:
>>> On Tue, Nov 10, 2020 at 9:14 AM Matteo Bonardi >> 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/
> 
> 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-le...@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/RJ4MQDQDJUNE67FHXI5C5SP62FO6RTLY/
> 
> 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/6BA7XRPZAXV3F6ND2FSXSAQFJZXJD5EW/


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

2020-11-10 Thread Matteo Bonardi
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  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.cec...@gmail.com> написа:
>
>
>
>
>
> On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi  wrote:
> >> On Tue, Nov 10, 2020 at 9:14 AM Matteo Bonardi  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/
>
> 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-le...@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/RJ4MQDQDJUNE67FHXI5C5SP62FO6RTLY/
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/X6DEOI4SGSQ2GWMFPB76NQL6E5U7SETN/


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

2020-11-10 Thread Strahil Nikolov via Users
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 
 написа: 





On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi  wrote:
>> On Tue, Nov 10, 2020 at 9:14 AM Matteo Bonardi > 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/

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-le...@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/RJ4MQDQDJUNE67FHXI5C5SP62FO6RTLY/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/WIZVGUDVQQFZWFQQGGQ3ETT7CZSF5H7S/


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

2020-11-10 Thread Yedidyah Bar David
On Tue, Nov 10, 2020 at 12:18 PM Gianluca Cecchi
 wrote:
>
> On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi  wrote:
>>
>> > On Tue, Nov 10, 2020 at 9:14 AM Matteo Bonardi > > 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/
>
> 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
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/D736NGNASY2RHU2KJDAQQV5HP6BUAH3W/


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

2020-11-10 Thread Gianluca Cecchi
On Tue, Nov 10, 2020 at 8:55 AM Matteo Bonardi  wrote:

> > On Tue, Nov 10, 2020 at 9:14 AM Matteo Bonardi  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/

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-le...@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/RJ4MQDQDJUNE67FHXI5C5SP62FO6RTLY/


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

2020-11-09 Thread Matteo Bonardi
> On Tue, Nov 10, 2020 at 9:14 AM Matteo Bonardi  
> 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,
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/DJI7IFUQ6FPDYIVDHAPDXVLY4BGOIZI4/


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

2020-11-09 Thread Yedidyah Bar David
On Tue, Nov 10, 2020 at 9:14 AM Matteo Bonardi  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
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/FQ6WXIHDUM3GFT2UQH4BTDG2FXHEBZYB/