Re: Upgrade Bobcat/Caracal and python3-futurist
by Francesco Di Nucci
Thank you,
just upgraded and things seem to run smoothly
Best regards
Francesco Di Nucci
On 02/05/24 13:34, Joel Capitao wrote:
> futurist-3.0.0 is now available in CentOS CloudSIG repo
> https://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-car...
> It may take some time to be spread through the whole mirror network.
>
> On Thu, May 2, 2024 at 9:23 AM Joel Capitao <jcapitao(a)redhat.com> wrote:
>
> Hi Francesco,
>
> It looks like we had an issue in our tooling, the build of
> futurist to 3.0.0 was not proposed automatically. On a fresh
> installation of
> RDO Caracal/2024.1 it's working well with futurist 2.4.1 version,
> at least no failure was caught by our CI (i.e running different
> deployment scenarios and tempest with puppet-openstack-integration
> and packstack).
> Though, we don't test the upgrade path from previous releases,
> hence we might hit this kind of issue, and your feedback here is
> valuable for the community.
>
> Maybe the fact that it is a downgrade caused the issue? Also,
> shouldn't the CentOS repo ship the same version as RDO trunk?
>
> Right, we should ship the same version of packages in both CentOS
> CloudSIG repo and RDO Trunk repo.
> I'm going to update futurist to 3.0.0 right now and will ping you
> once it lands in repo.
>
> Cheers,
> Joel
>
> On Thu, May 2, 2024 at 8:47 AM Francesco Di Nucci
> <francesco.dinucci(a)na.infn.it> wrote:
>
> Thank you,
>
> it looks like somehow I just messed with DNF, as if I search
> the package showing duplicates and querying info about the
> specific versions, it shows that there are two alternatives:
>
> * python3-futurist-2.4.1-1 - installed from
> centos-openstack-bobcat
> * python3-futurist-2.3.0-3 - available from openstack-caracal
>
> I tried to reinstall python3-futurist and it showed an error
> about the package not being available, then I explicitly used
> dnf install python3-futurist-2.3.0 and it was correctly
> detected and run as a downgrade.
>
> Maybe the fact that it is a downgrade caused the issue? Also,
> shouldn't the CentOS repo ship the same version as RDO trunk?
>
> Best regards
>
> Francesco Di Nucci
>
> On 01/05/24 11:57, smooney(a)redhat.com wrote:
>> On Wed, 2024-05-01 at 14:20 +0900, Takashi Kajinami wrote:
>>> As far as I can tell, futurist is still used by multiple projects so
>>> it is required in Caracal.
>> its used by nova and we will be using it more going forward.
>> we have no current plans to remove our usage of futurist and are activly plannign to use it as part
>> of our strategy to reduce our use of eventlet.
>>> I checked the RDO repo and its caracal contents contains the python3-futurist
>>> package actually exists.
>>>
>>> https://trunk.rdoproject.org/centos9-caracal/component/common/26/d9/26d95...
>>> python3-futurist-3.0.0-0.20240313181506.4e14db5.el9.noarch.rpm
>>>
>>> However the SIG repo in centos provides a much older version. I suspect that
>>> there might be some problems with sync process between RDO and CentOS.
>>>
>>> https://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-car...
>>> python3-futurist-2.3.0-3.el9s.noarch.rpm
>>>
>>> I'm adding rdo user mailing list, assuming people subscribing the list may have
>>> better idea about potential causes.
>>>
>>>
>>> On 4/30/24 22:20, Francesco Di Nucci wrote:
>>>> Hi all,
>>>>
>>>> I'm upgrading from Bobcat to Caracal using RDO repositories. I noticed that the package python3-futurist.noarch was
>>>> present in centos-openstack-bobcat repo, but it is not in openstack-caracal. So it is not possible to
>>>> update/reinstall/etc. it as it is "orphaned" once the bobcat repository is disabled. Should it be removed? Is it
>>>> still a dependency?
>>>>
>>>> Best regards
>>>>
>>>> Francesco Di Nucci
>>>>
>>>>
2 weeks, 2 days
Re: Upgrade Bobcat/Caracal and python3-futurist
by Joel Capitao
Hi Francesco,
It looks like we had an issue in our tooling, the build of futurist to
3.0.0 was not proposed automatically. On a fresh installation of
RDO Caracal/2024.1 it's working well with futurist 2.4.1 version, at least
no failure was caught by our CI (i.e running different
deployment scenarios and tempest with puppet-openstack-integration and
packstack).
Though, we don't test the upgrade path from previous releases, hence we
might hit this kind of issue, and your feedback here is
valuable for the community.
Maybe the fact that it is a downgrade caused the issue? Also, shouldn't the
> CentOS repo ship the same version as RDO trunk?
Right, we should ship the same version of packages in both CentOS CloudSIG
repo and RDO Trunk repo.
I'm going to update futurist to 3.0.0 right now and will ping you once it
lands in repo.
Cheers,
Joel
On Thu, May 2, 2024 at 8:47 AM Francesco Di Nucci <
francesco.dinucci(a)na.infn.it> wrote:
> Thank you,
>
> it looks like somehow I just messed with DNF, as if I search the package
> showing duplicates and querying info about the specific versions, it shows
> that there are two alternatives:
>
> - python3-futurist-2.4.1-1 - installed from centos-openstack-bobcat
> - python3-futurist-2.3.0-3 - available from openstack-caracal
>
> I tried to reinstall python3-futurist and it showed an error about the
> package not being available, then I explicitly used dnf install
> python3-futurist-2.3.0 and it was correctly detected and run as a downgrade.
>
> Maybe the fact that it is a downgrade caused the issue? Also, shouldn't
> the CentOS repo ship the same version as RDO trunk?
>
> Best regards
>
> Francesco Di Nucci
> On 01/05/24 11:57, smooney(a)redhat.com wrote:
>
> On Wed, 2024-05-01 at 14:20 +0900, Takashi Kajinami wrote:
>
> As far as I can tell, futurist is still used by multiple projects so
> it is required in Caracal.
>
> its used by nova and we will be using it more going forward.
> we have no current plans to remove our usage of futurist and are activly plannign to use it as part
> of our strategy to reduce our use of eventlet.
>
> I checked the RDO repo and its caracal contents contains the python3-futurist
> package actually exists.
> https://trunk.rdoproject.org/centos9-caracal/component/common/26/d9/26d95...
> python3-futurist-3.0.0-0.20240313181506.4e14db5.el9.noarch.rpm
>
> However the SIG repo in centos provides a much older version. I suspect that
> there might be some problems with sync process between RDO and CentOS.
> https://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-car...
> python3-futurist-2.3.0-3.el9s.noarch.rpm
>
> I'm adding rdo user mailing list, assuming people subscribing the list may have
> better idea about potential causes.
>
>
> On 4/30/24 22:20, Francesco Di Nucci wrote:
>
> Hi all,
>
> I'm upgrading from Bobcat to Caracal using RDO repositories. I noticed that the package python3-futurist.noarch was
> present in centos-openstack-bobcat repo, but it is not in openstack-caracal. So it is not possible to
> update/reinstall/etc. it as it is "orphaned" once the bobcat repository is disabled. Should it be removed? Is it
> still a dependency?
>
> Best regards
>
> Francesco Di Nucci
>
>
>
>
2 weeks, 2 days
Re: Upgrade Bobcat/Caracal and python3-futurist
by Takashi Kajinami
As far as I can tell, futurist is still used by multiple projects so
it is required in Caracal.
I checked the RDO repo and its caracal contents contains the python3-futurist
package actually exists.
https://trunk.rdoproject.org/centos9-caracal/component/common/26/d9/26d95...
python3-futurist-3.0.0-0.20240313181506.4e14db5.el9.noarch.rpm
However the SIG repo in centos provides a much older version. I suspect that
there might be some problems with sync process between RDO and CentOS.
https://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-car...
python3-futurist-2.3.0-3.el9s.noarch.rpm
I'm adding rdo user mailing list, assuming people subscribing the list may have
better idea about potential causes.
On 4/30/24 22:20, Francesco Di Nucci wrote:
> Hi all,
>
> I'm upgrading from Bobcat to Caracal using RDO repositories. I noticed that the package python3-futurist.noarch was present in centos-openstack-bobcat repo, but it is not in openstack-caracal. So it is not possible to update/reinstall/etc. it as it is "orphaned" once the bobcat repository is disabled. Should it be removed? Is it still a dependency?
>
> Best regards
>
> Francesco Di Nucci
>
>
2 weeks, 3 days
