Re: [ovirt-users] POWER9 Support: VDSM requiring LVM2 package that's missing
by Amit Bawer
+devel <devel(a)ovirt.org>
On Fri, May 15, 2020 at 2:29 AM Amit Bawer <abawer(a)redhat.com> wrote:
> yes it correlates to the bug mentioned,
> currently the rpm for vdsm-4.30.46 is available at 4.3 pre-release repo
> https://resources.ovirt.org/pub/ovirt-4.3-pre/rpm/el7/ppc64le/
> repodata is one level up
>
> On Fri, May 15, 2020 at 2:26 AM Vinícius Ferrão <ferrao(a)versatushpc.com.br>
> wrote:
>
>> Hi Amit, I think I found the answer: It’s not available yet.
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1829348
>>
>> It's this bug right?
>>
>> Thanks,
>>
>> On 14 May 2020, at 20:14, Vinícius Ferrão <ferrao(a)versatushpc.com.br>
>> wrote:
>>
>> Hi Amit, thanks for confirming.
>>
>> Do you know in which repository VDSM 4.30.36 is available?
>>
>> It’s not available on any of both:
>> rhel-7-for-power-9-rpms/ppc64le
>> Red Hat Enterprise Linux 7 for POWER9 (RPMs)
>> 9,156
>> rhel-7-server-rhv-4-mgmt-agent-for-power-9-rpms/ppc64le Red Hat
>> Virtualization 4 Management Agents (for RHEL 7 Server for IBM POWER9 814
>>
>>
>> Thank you!
>>
>>
>> On 14 May 2020, at 20:09, Amit Bawer <abawer(a)redhat.com> wrote:
>>
>>
>> On Fri, May 15, 2020 at 12:19 AM Vinícius Ferrão via Users <
>> users(a)ovirt.org> wrote:
>>
>>> Hello,
>>>
>>> I would like to know if this is a bug or not, if yes I will submit to
>>> Red Hat.
>>>
>> Fixed on vdsm-4.30.46
>>
>>>
>>> I’m trying to add a ppc64le (POWER9) machine to the hosts pool, but
>>> there’s missing dependencies on VDSM:
>>>
>>> --> Processing Dependency: lvm2 >= 7:2.02.186-7.el7_8.1 for package:
>>> vdsm-4.30.44-1.el7ev.ppc64le
>>> --> Finished Dependency Resolution
>>> Error: Package: vdsm-4.30.44-1.el7ev.ppc64le
>>> (rhel-7-server-rhv-4-mgmt-agent-for-power-9-rpms)
>>> Requires: lvm2 >= 7:2.02.186-7.el7_8.1
>>> Available: 7:lvm2-2.02.171-8.el7.ppc64le
>>> (rhel-7-for-power-9-rpms)
>>> lvm2 = 7:2.02.171-8.el7
>>> Available: 7:lvm2-2.02.177-4.el7.ppc64le
>>> (rhel-7-for-power-9-rpms)
>>> lvm2 = 7:2.02.177-4.el7
>>> Available: 7:lvm2-2.02.180-8.el7.ppc64le
>>> (rhel-7-for-power-9-rpms)
>>> lvm2 = 7:2.02.180-8.el7
>>> Available: 7:lvm2-2.02.180-10.el7_6.1.ppc64le
>>> (rhel-7-for-power-9-rpms)
>>> lvm2 = 7:2.02.180-10.el7_6.1
>>> Available: 7:lvm2-2.02.180-10.el7_6.2.ppc64le
>>> (rhel-7-for-power-9-rpms)
>>> lvm2 = 7:2.02.180-10.el7_6.2
>>> Available: 7:lvm2-2.02.180-10.el7_6.3.ppc64le
>>> (rhel-7-for-power-9-rpms)
>>> lvm2 = 7:2.02.180-10.el7_6.3
>>> Available: 7:lvm2-2.02.180-10.el7_6.7.ppc64le
>>> (rhel-7-for-power-9-rpms)
>>> lvm2 = 7:2.02.180-10.el7_6.7
>>> Available: 7:lvm2-2.02.180-10.el7_6.8.ppc64le
>>> (rhel-7-for-power-9-rpms)
>>> lvm2 = 7:2.02.180-10.el7_6.8
>>> Installing: 7:lvm2-2.02.180-10.el7_6.9.ppc64le
>>> (rhel-7-for-power-9-rpms)
>>> lvm2 = 7:2.02.180-10.el7_6.9
>>>
>>>
>>> Thanks,
>>>
>>> _______________________________________________
>>> Users mailing list -- users(a)ovirt.org
>>> To unsubscribe send an email to users-leave(a)ovirt.org
>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/I3YDM2VN7K2...
>>>
>>
>>
>>
2 years, 6 months
OST
by Michal Skrivanek
Hi,
I’m getting " Failed to download metadata for repo \'ovirt-master-advanced-virtualization-testing\’” when using ovirt-release-master.rpm since today. Any idea?
Also, in CI the backup/restore test seem to be failing for few days now. Any idea anyone? It doesn’t fail in my local runs so could be just a dependency problem too…
Thanks,
michal
2 years, 6 months
testing uses of Injector.get with mockito
by Fedor Gavrilov
We have quite a few occasions when Injector.get(SomeClass.class) is used inside command. Given that mockito can't mock static methods and power mock is not used, I wonder what one should do when these usages have to be mocked in unit tests.
Funny enough, workarounds for this usage in my specific case include mocking constructor (unsupported by mockito) and mocking superclass method (unsupported by mockito).
Also, why not to @Inject these instances in the first place?
Thanks,
Fedor
2 years, 6 months
