Nope, it's in the appstream (CentOS Stream), but I never tested it.
Best Regards,Strahil Nikolov
On Wed, Feb 23, 2022 at 12:42, Gilboa Davara wrote:
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
P
On Mon, Feb 21, 2022 at 12:07 PM Strahil Nikolov
wrote:
> You can blacklist packages in dnf with specific version, and thus you
> don't need to blacklist from repo.
>
> Best Regards,
> Strahil Nikolov
>
>
Hello,
Understood.
Perr your qemu 6.2 question, how can I test it? Is it packaged in some
t
You can blacklist packages in dnf with specific version, and thus you don't
need to blacklist from repo.
Best Regards,Strahil Nikolov
On Mon, Feb 21, 2022 at 10:33, Gilboa Davara wrote:
___
Users mailing list -- users@ovirt.org
To unsubscribe se
Hello,
I somehow missed your reply (and was AFK nearly two weeks).
How can I test qemu 6.2? Is it available in some repo?
- Gilboa
On Thu, Feb 10, 2022 at 4:31 PM Strahil Nikolov
wrote:
> I ment blacklisting only the broken qemu packages .
> Something like:
> exclude=qemu*6.1.0-4.module_el8.6.
I ment blacklisting only the broken qemu packages .Something
like:exclude=qemu*6.1.0-4.module_el8.6.0+983+a7505f3f.x86_64
or even more explicit -> full package names qith version & arch
New packages would not match the filter.
By the way, did anyone check qemu 6.2.0 ?
Best Regards,Strahil Nikolo
On Wed, Feb 9, 2022, 21:33 Nir Soffer wrote:
> On Wed, Feb 9, 2022 at 5:06 PM Gilboa Davara wrote:
> >
> >
> > On Wed, Feb 9, 2022 at 3:35 PM Nir Soffer wrote:
> >>
> >> On Wed, Feb 9, 2022 at 12:47 PM Gilboa Davara
> wrote:
> >> >
> >> > On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov
> wrote
On Wed, Feb 9, 2022 at 5:06 PM Gilboa Davara wrote:
>
>
> On Wed, Feb 9, 2022 at 3:35 PM Nir Soffer wrote:
>>
>> On Wed, Feb 9, 2022 at 12:47 PM Gilboa Davara wrote:
>> >
>> > On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov
>> > wrote:
>> >>
>> >> Or just add an exclude in /etc/dnf/dnf.conf
>>
On Wed, Feb 9, 2022 at 3:35 PM Nir Soffer wrote:
> On Wed, Feb 9, 2022 at 12:47 PM Gilboa Davara wrote:
> >
> > On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov
> wrote:
> >>
> >> Or just add an exclude in /etc/dnf/dnf.conf
> >
> >
> > I personally added and exclusion to
> /etc/yum.repos.d/CentOS
On Wed, Feb 9, 2022 at 12:47 PM Gilboa Davara wrote:
>
> On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov wrote:
>>
>> Or just add an exclude in /etc/dnf/dnf.conf
>
>
> I personally added and exclusion to
> /etc/yum.repos.d/CentOS-Stream-AppStream.repo
> exclude=qemu*
> It allows ovirt-4.4* repos
On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov
wrote:
> Or just add an exclude in /etc/dnf/dnf.conf
I personally added and exclusion to
/etc/yum.repos.d/CentOS-Stream-AppStream.repo
exclude=qemu*
It allows ovirt-4.4* repos to push a new qemu release, without letting
CentOS stream break things..
Or just add an exclude in /etc/dnf/dnf.conf
On Tue, Feb 8, 2022 at 18:32, Gilboa Davara wrote:
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy
>
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fail if Engine IP is
> different from engine's he_fqdn resolved IP]
> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg":
> "Engine VM IP address is while the engine's he_fqdn
> ovirt-engine.mgmt.pss.local resolves to 10.210.1.101.
While I have not answered your question directly, I would strongly advise
you just use ovirt-node
I went through similar build issues all the time. Ansible (well, whoever
wrote the playbook) can be finicky sometimes and I found when I deployed
ovirt-node I was done in under an hour with absolutely
On Tue, Feb 8, 2022 at 4:05 PM Charles Stellen wrote:
>
> Dear Ovirt Hackers,
>
> sorry: incidently send to de...@ovitr.org
>
> we are dealing with hosted engine deployment issue on a fresh AMD EPYC
> servers:
>
> and we are ready to donate hardware to Ovirt community after we pass
> this issue (
14 matches
Mail list logo
