[ironic] [requirements] broken libvirt-python on yoga on stream 9

Dmitry Tantsur dtantsur at redhat.com
Wed May 18 06:24:44 UTC 2022


On Tue, May 17, 2022 at 8:24 PM Clark Boylan <cboylan at sapwetik.org> wrote:

> On Tue, May 17, 2022, at 10:56 AM, Dmitry Tantsur wrote:
> > Hi all,
> >
> > It is happening again, the Bifrost CI is broken because libvirt-python
> > cannot be built from source, this time on Stream 9.
> >
> >    Missing type converters:
> >     int *:1
> >     ERROR: failed virDomainQemuMonitorCommandWithFiles
> >
> > I created a gist with a reproducer:
> > https://gist.github.com/dtantsur/835303c6a68ed77157016f5955183115.
> >
> > I cannot count how many times we had to deal with similar errors. I
> > assume, libvirt-python has to be newer than the installed Python (8.2.0
> > in CS9, 8.0.0 in constraints). Should we stop constraining
> > libvirt-python? Any other ideas?
>
> Your libvirt-python version needs to be at least as new as your libvirt
> version. New libvirt-python versions are expected to continue to work with
> old libvirt versions as well (though it may need to be built against the
> specific libvirt?). In this case it looks like CentOS Stream 9 libvirt is
> newer than what was in constraints.
>
> Generally constraints should update quickly. Looking at master
> upper-constraints libvirt-python was updated to 8.3.0 on May 4 and
> according to pypi the package updated on May 2 which seems reasonable. The
> problem here appears to be that you want this to work on a stable branch
> (yoga) and stable branches do not update constraints.
>
> My suggestion is that we use stable platforms for testing stable releases.
> The CentOS Stream releases seem to get updates that break stable software
> expectations far more than our other platforms. When working against master
> and trying to chase the latest and greatest this is probably a feature, but
> is problematic when you want rate of change to fall to near zero. I would
> consider not using Stream on stable branches if these problems persist.
>

What would you suggest to use to test Red Hat systems then?

Dmitry


>
> >
> > Dmitry
> >
> > --
> > Red Hat GmbH <https://www.redhat.com/de/global/dach>, Registered seat:
> > Werner von Siemens Ring 14, D-85630 Grasbrunn, Germany
> > Commercial register: Amtsgericht Muenchen/Munich, HRB 153243,
> > Managing Directors: Ryan Barnhart, Charles Cachera, Michael O'Neill,
> > Amy Ross
>
>

-- 

Red Hat GmbH <https://www.redhat.com/de/global/dach>, Registered seat:
Werner von Siemens Ring 14, D-85630 Grasbrunn, Germany
Commercial register: Amtsgericht Muenchen/Munich, HRB 153243,Managing
Directors: Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220518/fde632c4/attachment.htm>


More information about the openstack-discuss mailing list