On Tue, Feb 27, 2018 at 2:49 PM, Junaid Jadoon <junaid8756(a)gmail.com> wrote:
please guide which repo should i add on node server in order to
resolve this
issue???? can u please send repo list.
What's the output of each of these commands:
rpm -qa | grep ovirt-release
grep ovirt-4.2-epel /etc/yum.repos.d/*
cat /etc/yum.repos.d/ovirt-*dependencies.repo
yum install dmidecode
Thanks,
On Tue, Feb 27, 2018 at 5:46 PM, Yedidyah Bar David <didi(a)redhat.com> wrote:
>
> On Tue, Feb 27, 2018 at 2:38 PM, Junaid Jadoon <junaid8756(a)gmail.com>
> wrote:
> > Thanks Yedidyah David for reply.
> >
> > Please confirm where check should the repo file either host engine or
> > node
> > server???
>
> On the node, please.
>
> >
> >
> >
> > On Tue, Feb 27, 2018 at 5:31 PM, Yedidyah Bar David <didi(a)redhat.com>
> > wrote:
> >>
> >> On Tue, Feb 27, 2018 at 2:17 PM, Junaid Jadoon <junaid8756(a)gmail.com>
> >> wrote:
> >> > Dear All,
> >> > I have Ovirt engine 4.2 and node version is 4.2.
> >> >
> >> > After installing node in in ovirt engine when i try to install node
> >> > it
> >> > gives
> >> > following error
> >> > 14:25:37,410+05 ERROR
> >> > [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
> >> > (EE-ManagedThreadFactory-engine-Thread-19) [52669850] Host
> >> > installation
> >> > failed for host 'bd8d007a-be92-4075-bba9-6cbeb890a1e5',
'node_2':
> >> > Command
> >> > returned failure code 1 during SSH session
'root(a)192.168.20.20'
> >> > 2018-02-27 14:25:37,416+05 INFO
> >> > [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> >> > (EE-ManagedThreadFactory-engine-Thread-19) [52669850] START,
> >> > SetVdsStatusVDSCommand(HostName = node_2,
> >> >
> >> >
> >> >
SetVdsStatusVDSCommandParameters:{hostId='bd8d007a-be92-4075-bba9-6cbeb890a1e5',
> >> > status='InstallFailed', nonOperationalReason='NONE',
> >> > stopSpmFailureLogged='false',
maintenanceReason='null'}), log id:
> >> > 2b138e87
> >> > 2018-02-27 14:25:37,423+05 INFO
> >> > [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> >> > (EE-ManagedThreadFactory-engine-Thread-19) [52669850] FINISH,
> >> > SetVdsStatusVDSCommand, log id: 2b138e87
> >> > 2018-02-27 14:25:37,429+05 ERROR
> >> >
> >> > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> >> > (EE-ManagedThreadFactory-engine-Thread-19) [52669850] EVENT_ID:
> >> > VDS_INSTALL_FAILED(505), Host node_2 installation failed. Command
> >> > returned
> >> > failure code 1 during SSH session 'root(a)192.168.20.20'.
> >> > 2018-02-27 14:25:37,433+05 INFO
> >> > [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
> >> > (EE-ManagedThreadFactory-engine-Thread-19) [52669850] Lock freed to
> >> > object
> >> >
> >> >
> >> >
'EngineLock:{exclusiveLocks='[bd8d007a-be92-4075-bba9-6cbeb890a1e5=VDS]',
> >> > sharedLocks=''}'
> >> >
> >> >
> >> > I have attached log file for your reference
> >>
> >> The relevant part is:
> >>
> >> 2018-02-27 12:54:56,909+05 ERROR
> >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> >> (VdsDeploy) [719d5f5d] EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511),
> >> An error has occurred during installation of Host uoi_node2: Yum
> >> Cannot queue package dmidecode: Cannot retrieve metalink for
> >> repository: ovirt-4.2-epel/x86_64. Please verify its path and try
> >> again.
> >>
> >> Please check/share yum repos on the host. What happens if you run
> >> there 'yum install dmidecode'?
> >> It might be a specific bad mirror, or a bad proxy etc. You can edit
> >> the repo file to point at
> >> another specific mirror instead of using mirrorlist.
> >>
> >> Best regards,
> >> --
> >> Didi
> >
> >
>
>
>
> --
> Didi
--
Didi