Hi again
My friend told me that this issue solved after (unintensionally) a reboot.
According to logs on spacewalk server, the system had couple of failures
because of the disk and rebooted itself twice. Thanks for your help.
2018-06-07 23:53 GMT+03:00 jin :
> Thanks Avi
> I'll raise a service
Thanks Avi
I'll raise a service request for this
On Thu, 7 Jun 2018, 23:40 Avi Miller, wrote:
> Hi
>
>
> > On 7 Jun 2018, at 11:30 pm, jin
> wrote:
> >
> > Here is the name differences between errata and error sections
> >
> > in error :
> > lvm2-libs-7:2.02.177-4.0.2.el7.x86_64
>
> This is
Hi
> On 7 Jun 2018, at 11:30 pm, jin wrote:
>
> Here is the name differences between errata and error sections
>
> in error :
> lvm2-libs-7:2.02.177-4.0.2.el7.x86_64
This is showing the epoch of the RPM (7:) at the beginning.
> in errata
> lvm2-libs-2.02.177.4.0.2.el7:7-x86_64
This has the
Here is the name differences between errata and error sections
in error :
lvm2-libs-7:2.02.177-4.0.2.el7.x86_64
in errata
lvm2-libs-2.02.177.4.0.2.el7:7-x86_64
I do not want to believe this naming differences cause this errors but the
errroe messages have this detail as a common point.
Hi
Trying to deploy errata files. Not all of them but some erratas. For
example ELBA-2018-4118. I confirmed that the rpm packages listing in this
errata are already downloaded and I can locate under /var/satellite
directories. Also verifying them with their sha256 summaries against in
errata
