On Tue, Oct 6, 2020 at 11:33 AM Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
Hello,
I'm testing upgrade from 4.3.10 to 4.4.2 for a standalone manager with
local database environment.
I configured the new engine system as a CentOS 8.2 with a proxy in
/etc/yum.conf (that is a link to /etc/dnf/dnf.com) and that worked for
all the steps until engine-setup.
Now I get this
[root@ovmgr1 ~]# engine-setup
[ INFO ] Stage: Initializing
[ INFO ] Stage: Environment setup
Configuration files:
/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf,
/etc/ovirt-engine-setup.conf.d/10-packaging.conf,
/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf
Log file:
/var/log/ovirt-engine/setup/ovirt-engine-setup-20201006112458-p84x9i.log
Version: otopi-1.9.2 (otopi-1.9.2-1.el8)
[ INFO ] DNF Downloading 1 files, 0.00KB
[ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB
[ INFO ] DNF Downloaded CentOS-8 - AppStream
[ INFO ] DNF Errors during downloading metadata for repository
'AppStream':
....
[ ERROR ] Execution of setup failed
and I see in netstat during the phase
tcp 0 1 10.4.192.43:33418 18.225.36.18:80
SYN_SENT
so it seems it is not using the proxy.
Do I have to put proxy info into any other file?
Thanks,
Gianluca
It was necessary and sufficient to set both:
[root@ovmgr1 ~]# export http_proxy=my.proxy.host:proxy_port
[root@ovmgr1 ~]# export https_proxy=my.proxy.host:proxy_port
It seems some repos are using http and other https.
A smarter way would be to leverage the already systemwide dnf proxy config.
Anyway the upgrade of the engine from 4.3.10 to 4.4.2 went smooth and ok
and I was able to move VMs from a host to start upgrading it.
Let's see how it goes.
HIH others,
Gianluca