> Am 28.06.2019 um 11:59 schrieb Markus Falb :
>
>
>
>> On 28.06.2019, at 11:41, Oliver Riesener
>> wrote:
>>
>>
>> On 27.06.19 12:05, markus.f...@mafalb.at wrote:
>>> ...
>>>
>>> btw, on my engine I see a few versionlocks too.
>>>
>>> ...snip
>>> # yum versionlock list
>>> Loaded plugins
> On 28.06.2019, at 11:41, Oliver Riesener wrote:
>
>
> On 27.06.19 12:05, markus.f...@mafalb.at wrote:
>> ...
>>
>> btw, on my engine I see a few versionlocks too.
>>
>> ...snip
>> # yum versionlock list
>> Loaded plugins: fastestmirror, versionlock
>> ovirt-engine-webadmin-portal-4.3.4.3-1
On 27.06.19 12:05, markus.f...@mafalb.at wrote:
...
The next command makes the possible to see the locked but potential upgradable
packages
(up to 128).
# yum --enablerepo=base --enablerepo=updates --enablerep=extras
--enablerepo=epel
versionlock status
Upgrade, or not upgrade? This is the
> On Wed, Jun 26, 2019 at 11:59 AM
> You should wait for next node release and upgrade to that.
How is that handled when installed on top of CentOS, not ovirt node?
Best Regards, Markus
___
Users mailing list -- users@ovirt.org
To unsubscribe send an
...
> The next command makes the possible to see the locked but potential
> upgradable packages
> (up to 128).
>
> # yum --enablerepo=base --enablerepo=updates --enablerep=extras
> --enablerepo=epel
> versionlock status
>
> Upgrade, or not upgrade? This is the question, Didi says wait for nex
On Thu, Jun 27, 2019 at 10:49 AM Oliver Riesener
wrote:
>
> >
> > Most installed packaged are version locked.
> >
> Ok i see. It was new for me. Thank you.
>
>
> > # yum versionlock list
> >
> > Maybe the CentOS repos are disabled by default, then versionlock status
> > would be empty.
> >
>
> Ok
>
> Most installed packaged are version locked.
>
Ok i see. It was new for me. Thank you.
> # yum versionlock list
>
> Maybe the CentOS repos are disabled by default, then versionlock status would
> be empty.
>
Ok, the packages and versionlocks are not shown, because the were disabled by
> On 26.06.19 13:02, markus.falb(a)mafalb.at wrote:
>
>
> I never saw version locked packages on a node before. I went from 4.2.x
> over previous
> 4.3.x versions to 4.3.4 and didn't have or see any versionlocks. What
> packages are locked ?
Most installed packaged are version locked.
...snip
On 26.06.19 13:02, markus.f...@mafalb.at wrote:
Thanks Oliver,
a Node installation is image based and this should not happen ...
What should not happen? That it is manually updated via yum? Hmm, always done
that with previous versions.
I never saw version locked packages on a node before. I
Thanks Oliver,
> a Node installation is image based and this should not happen ...
What should not happen? That it is manually updated via yum? Hmm, always done
that with previous versions.
>
> On an Engine system you have to call engine-setup again (don't worry)
> which updates installation fi
On Wed, Jun 26, 2019 at 11:59 AM wrote:
>
> Hi,
> I just upgraded some ovirt node 4.2.8 to ovirt node 4.3.4
> After a
>
> ...snip
> # yum update ovirt-node-ng-image-update
> snap...
>
> I rebooted, and afterwards I wanted to run a yum update like I was doing it
> with the previous versions, but
>
Hi Markus,
a Node installation is image based and this should not happen ...
On an Engine system you have to call engine-setup again (don't worry)
which updates installation files and then installs the versionlock'ed
packages.
Best regards, Oliver
On 26.06.19 10:57, markus.f...@mafalb.at wro
12 matches
Mail list logo
