Problem solved.The cause of the problem was really in the fact that there was no global proxy settings in yum.confThank you all! 14.09.2016, 13:24, "aleksey.maksi...@it-kb.ru" :Hmm..I'll try.How can I call the forced update checking process for oVirt, as well as it
Hmm..I'll try.How can I call the forced update checking process for oVirt, as well as it happens every night ? 14.09.2016, 13:05, "Gianluca Cecchi" :On Wed, Sep 14, 2016 at 10:40 AM, wrote:Yesterday I installed the all updates to hosts and
On Wed, Sep 14, 2016 at 10:40 AM, wrote:
> Yesterday I installed the all updates to hosts and Hosted Engine (and now
> I have oVirt Engine Version: 4.0.3-1.el7.centos)
> But the problem still persists.
>
> ==>>> Is this happening consistently or randomly?
>
>
Yesterday I installed the all updates to hosts and Hosted Engine (and now I
have oVirt Engine Version: 4.0.3-1.el7.centos)
But the problem still persists.
==>>> Is this happening consistently or randomly?
Consistently. every night.
==>>> Do you have any proxy server defined?
Yes. I add to end
On Wed, Sep 14, 2016 at 8:21 AM, wrote:
> Hi oVirt guru`s!
>
> # getent ahosts mirrorlist.centos.org
>
> 216.176.179.218 STREAM mirrorlist.centos.org
> 216.176.179.218 DGRAM
> 216.176.179.218 RAW
> 67.219.148.138 STREAM
> 67.219.148.138 DGRAM
> 67.219.148.138 RAW
>
IPv6 disabled in my ifcfg files # cat /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt | grep IPV6 IPV6INIT=no And running the command "yum update" manually operates successfully. 13.09.2016, 22:25, "Gianluca Cecchi" :On Tue, Sep 13, 2016 at 10:59 AM,
Hi oVirt guru`s! # getent ahosts mirrorlist.centos.org 216.176.179.218 STREAM mirrorlist.centos.org216.176.179.218 DGRAM216.176.179.218 RAW67.219.148.138 STREAM67.219.148.138 DGRAM67.219.148.138 RAW85.236.43.108 STREAM85.236.43.108 DGRAM85.236.43.108 RAW212.69.166.138
On Tue, Sep 13, 2016 at 10:59 AM, wrote:
> nslookup resolves names on the engine and hosts without ipv6 address:
>
> # nslookup mirrorlist.centos.org
>
> Server: 10.1.0.10
> Address:10.1.0.10#53
>
> Non-authoritative answer:
> Name:
On Tue, Sep 13, 2016 at 8:26 AM, wrote:
> 2604:1580:fe02:2::10
Probably yum/DNF not explicitly asking for IPv4 (and perhaps happy
eyeballs[1] is used on the stack?)
Y.
[1] https://en.wikipedia.org/wiki/Happy_Eyeballs
___
On Tue, Sep 13, 2016 at 12:55 PM, Martin Perina wrote:
>
>
> On Tue, Sep 13, 2016 at 10:59 AM, wrote:
>
>> nslookup resolves names on the engine and hosts without ipv6 address:
>>
>> # nslookup mirrorlist.centos.org
>>
>> Server: 10.1.0.10
On Tue, Sep 13, 2016 at 10:59 AM, wrote:
> nslookup resolves names on the engine and hosts without ipv6 address:
>
> # nslookup mirrorlist.centos.org
>
> Server: 10.1.0.10
> Address:10.1.0.10#53
>
> Non-authoritative answer:
> Name:
nslookup resolves names on the engine and hosts without ipv6 address:
# nslookup mirrorlist.centos.org
Server: 10.1.0.10
Address:10.1.0.10#53
Non-authoritative answer:
Name: mirrorlist.centos.org
Address: 67.219.148.138
Name: mirrorlist.centos.org
Address: 85.236.43.108
Yesterday I changed the settings the host to: net.ipv6.conf.all.disable_ipv6 = 1net.ipv6.conf.default.disable_ipv6 = 1 I deleted the last two lines in /etc/sysctl.conf and rebooted host. Tonight - problem repeated: 2016-09-13 01:11:13 ERROR otopi.context context._executeMethod:151 Failed to
On Mon, Sep 12, 2016 at 3:34 PM, wrote:
> My /etc/sysctl.conf is:
>
> net.ipv6.conf.all.disable_ipv6 = 1
> net.ipv6.conf.default.disable_ipv6 = 1
> net.ipv6.conf.lo.disable_ipv6 = 0
> net.ipv6.conf.ovirtmgmt.disable_ipv6 = 0
>
I'm not networking expert, but last two
My /etc/sysctl.conf is: net.ipv6.conf.all.disable_ipv6 = 1net.ipv6.conf.default.disable_ipv6 = 1net.ipv6.conf.lo.disable_ipv6 = 0net.ipv6.conf.ovirtmgmt.disable_ipv6 = 0 Last two lines was added for http://lists.ovirt.org/pipermail/users/2016-July/041443.html My configuration file is bad ??
On Mon, Sep 12, 2016 at 2:49 PM, wrote:
> Ok. I found log-file /var/log/ovirt-engine/host-deploy/ovirt-host-mgmt-
> 20160912020013-kom-ad01-vm31.holding.com-null.log with this:
>
> ...
> 2016-09-12 02:00:13 ERROR otopi.plugins.otopi.packagers.yumpackager
>
Ok. I found log-file
/var/log/ovirt-engine/host-deploy/ovirt-host-mgmt-20160912020013-kom-ad01-vm31.holding.com-null.log
with this:
...
2016-09-12 02:00:13 ERROR otopi.plugins.otopi.packagers.yumpackager
yumpackager.error:85 Yum Cannot queue package iproute: Cannot find a valid
baseurl for
> 2016-09-12 02:00:13,388 INFO
> [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase]
(VdsDeploy) [] Retrieving installation logs to: '/var/log/ovirt-engine/host-
deploy/ovirt-host-mgmt-20160912020013-kom-ad01-vm31.holding.com-null.l$
This is most probably the log file where details of the
On Mon, Sep 12, 2016 at 3:08 PM, wrote:
>
> Excuse me. I do not understand. What I should do?
> The directory /var/log/ovirt-engine/host-deploy many different log files
Please check the one from a time where you see this error.
Every run of host-deploy creates its
Excuse me. I do not understand. What I should do?
The directory /var/log/ovirt-engine/host-deploy many different log files
12.09.2016, 14:59, "Yedidyah Bar David" :
> On Mon, Sep 12, 2016 at 11:17 AM, wrote:
>> # yum install iproute
>>
>> Loaded
On Mon, Sep 12, 2016 at 11:17 AM, wrote:
> # yum install iproute
>
> Loaded plugins: fastestmirror
> Loading mirror speeds from cached hostfile
> * base: mirror.awanti.com
> * elrepo: dfw.mirror.rackspace.com
> * epel: epel.besthosting.ua
> * extras:
# yum install iproute
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.awanti.com
* elrepo: dfw.mirror.rackspace.com
* epel: epel.besthosting.ua
* extras: centos-mirror.rbc.ru
* ovirt-4.0: ftp.nluug.nl
* ovirt-4.0-epel: epel.besthosting.ua
* updates:
On Mon, Sep 12, 2016 at 10:59 AM, wrote:
> Hi, Martin.
>
> The command is executed successfully:
>
> Updated:
> vdsm.x86_64 0:4.18.12-1.el7
> vdsm-cli.noarch 0:4.18.12-1.el7
> Dependency Updated:
> vdsm-api.noarch 0:4.18.12-1.el7
Hi, Martin.
The command is executed successfully:
Updated:
vdsm.x86_64 0:4.18.12-1.el7
vdsm-cli.noarch 0:4.18.12-1.el7
Dependency Updated:
vdsm-api.noarch 0:4.18.12-1.el7 vdsm-hook-vmfex-dev.noarch
0:4.18.12-1.el7 vdsm-infra.noarch
Hi Aleksey,
the error message is raised by Host upgrade manager (more info at [1])
which checks for available package upgrades on the host.
It seems that you have somehow corrupted repository configuration of the
host 'kom-ad01-vm31.holding.com':
2016-09-12 02:00:13,300 ERROR
Hello oVirt guru`s!
oVirt Engine Version: 4.0.1.1-1.el7.centos
Every day there is a message in web UI for one of my two hosts:
"Failed to check for available updates on host KOM-AD01-VM31 with message
'Command returned failure code 1 during SSH session
'r...@kom-ad01-vm31.holding.com''.
In
26 matches
Mail list logo