- openstack-discuss - lists.openstack.org

[cinder] Unit test failures under Python 3.11 - mocks can no longer be provided as the specs for other Mocks
by Sofia Enriquez 10 Jan '23

10 Jan '23

Hi, Since python3.11 mocks can no longer be provided as the specs for other Mocks. As a result, an already-mocked object cannot be passed to mock.Mock(). This can uncover bugs in tests since these Mock-derived Mocks will always pass certain tests (e.g. isinstance) and built-in assert functions (e.g. assert_called_once_with) will unconditionally pass.[1] There's a bug report to track this issue in Cinder [2] but I think this may affect other projects too. I've reproduce the error and most drivers fail with: ``` unittest.mock.InvalidSpecError: Cannot spec a Mock object. [object=<Mock name='mock.client.HPE3ParClient' id='139657768087760'>] ``` Cheers, Sofia [1] https://github.com/python/cpython/issues/87644 [2] https://bugs.launchpad.net/cinder/+bug/2000436 -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

4 3

[Kolla] Transition Ussuri/Victoria to EOL
by Bartosz Bezak 09 Jan '23

09 Jan '23

Hello, As aggreed on IRC meeting, Kolla Ussuri and Victoria deliverables (Kolla, Kolla-Ansible, Kayobe) are going EOL. [1] Wallaby remains in extended maintenance. Xena, Yoga and Zed are our current stable releases. Ussuri and Victoria branches were in Extended Maintenance for a some time, Kolla community does not have resources to support those branches actively. Moreover Ussuri and Victoria were the last releases that support CentOS 8 which is also EOL. All changes to those branches have been abandoned. [1] https://review.opendev.org/c/openstack/releases/+/869569 Best regards, Bartosz Bezak

1 0

[Nova][Horizon]
by Nguyễn Hữu Khôi 09 Jan '23

09 Jan '23

Hello guys. Is there any way to assign AZ to a specified project? After searching, I cannot find any answer. Example. Sale project will only see Sale AZ to select. Tech project will only see Tech AZ to select Thank you. Regards Nguyen Huu Khoi

3 7

[all][gate][stable] Pinning tox<4 in stable branch testing
by Ghanshyam Mann 09 Jan '23

09 Jan '23

Hello Everyone, As you might know, tox4 broke almost all the projects tox.ini and so do master as well as stable branches gate. On the master, we need to fix it as we should use tox4 in testing. To fix the stable branches gate, either we need to backport all the fixes which include some more issues fixes[1] or we can pin the tox<4. We discussed it in today's TC meeting and it is better to keep testing the stable branch with the tox version that they were released with and not with the tox4. Even in future, there might be the cases where latest tox might introduce more incompatible changes. By considering all these factors, it is better to pin tox<4 for stable branches (<=stable/zed) testing. I have prepared the patch to pin it in the common job/template, feel free to comment with your feedback/opinion: - https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/867849/3 also, tested with nova/cinder stable branches: - https://review.opendev.org/q/I0ca55abf9975c5a3f9713ac5dd5be39083e04554 - https://review.opendev.org/q/I300e7804a27d08ecd239d1a7faaf2aaf3e07b9ee You can also test it in your project stable branches in case any different syntax in tox.ini causing the tox upgrade to the latest. [1] https://github.com/tox-dev/tox/issues/2712 -gmann

4 7

[Diversity] Diversity and Inclusion WG Meeting reminder
by Amy Marrich 09 Jan '23

09 Jan '23

This is a reminder that the Diversity and Inclusion WG will be meeting tomorrow at 14:00 UTC in the #openinfra-diversity channel on OFTC. We hope members of all OpenInfra projects join us as we continue working on planning for the OpenInfra Summit as well as Foundation-wide surveys. Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/diversity-wg-agenda

1 0

[blazar] Next IRC meeting cancelled
by Pierre Riteau 09 Jan '23

09 Jan '23

Hello, I am unable to run the IRC meeting on Thursday January 12. I propose to cancel it. Best wishes, Pierre Riteau (priteau)

1 0

[ci][all]tox.tox_env.python.api.NoInterpreter - gate is blocked
by Balazs Gibizer 09 Jan '23

09 Jan '23

Hi, It seems that all the tox based jobs are blocked right now on master with the following error: tox.tox_env.python.api.NoInterpreter: could not find python interpreter matching any of the specs It is due to a recent bugfix in tox that uncovered another bug[1]. There is a fix proposed in tox [2]. [1]<https://github.com/tox-dev/tox/issues/2811> [2]<https://github.com/tox-dev/tox/pull/2828>

3 2

[openstack-ansible] git clone fatal: the remote end hung up unexpectedly
by Satish Patel 09 Jan '23

09 Jan '23

Folks, Trying to deploy an openstack-ansible Zed release but noticed strange behavior with git clone. failed: [localhost] (item={'name': 'galera_server', 'scm': 'git', 'src': 'https://opendev.org/openstack/openstack-ansible-galera_server', 'version': 'master', 'trackbranch': 'master', 'shallow_since': '2022-12-12'}) => {"ansible_loop_var": "item", "attempts": 2, "changed": false, "cmd": ["/usr/bin/git", "fetch", "--depth", "20", "--force", "origin", "+refs/heads/master:refs/remotes/origin/master"], "item": {"name": "galera_server", "scm": "git", "shallow_since": "2022-12-12", "src": "https://opendev.org/openstack/openstack-ansible-galera_server", "trackbranch": "master", "version": "master"}, "msg": "Failed to download remote objects and refs: fatal: error in object: unshallow e04aeacc58c196c4fb3d49116cb93fa74f7fba31\nfatal: the remote end hung up unexpectedly\n"} Full logs: https://paste.opendev.org/show/bUjuekKPzknE5IC8zbPa/

2 2

Re: add a new service to a pre-deployed openstack private cloud
by Oliver Weinmann 08 Jan '23

08 Jan '23

You don’t need to make any changes to your inventory files. Just keep using your initial inventory and you will be fine. > On 8. Jan 2023, at 09:19, A Monster <amonster369(a)gmail.com> wrote: > > Thank you for your quick response, > do I need to change the hosts in my inventory files and keep only the nodes on which these new services will be deployed on, or is it done automatically through the roles defined ? > > On Sun, 8 Jan 2023 at 09:15, Oliver Weinmann <oliver.weinmann(a)me.com <mailto:oliver.weinmann@me.com>> wrote: >> Hi, >> >> Sure. It is doable. Just make your changes to globals.yml, add the required config files and run e.g. for MAGNUM: >> >> kolla-ansible -i <inventory> deploy --tags common,horizon,magnum >> Magnum - Container cluster service — kolla-ansible 15.1.0.dev19 documentation >> docs.openstack.org >> >> <https://docs.openstack.org/kolla-ansible/latest/reference/containers/magnum…>Magnum - Container cluster service — kolla-ansible 15.1.0.dev19 documentation <https://docs.openstack.org/kolla-ansible/latest/reference/containers/magnum…> >> docs.openstack.org <https://docs.openstack.org/kolla-ansible/latest/reference/containers/magnum…> <https://docs.openstack.org/kolla-ansible/latest/reference/containers/magnum…> >> >> In that case deploy will not re-deploy your cluster, but pull in the needed containers for magnum and configure it. >> >>> On 8. Jan 2023, at 08:48, A Monster <amonster369(a)gmail.com <mailto:amonster369@gmail.com>> wrote: >>> >>> I've done an openstack deployment using kolla ansible, and after deploying I want to add new services but without having to redo the deployment from scratch in order to keep both the configuration and the data already in use, >>> is this doable ? as I couldn't find anything in the kolla-ansible docs. >>

1 0

add a new service to a pre-deployed openstack private cloud
by A Monster 08 Jan '23

08 Jan '23

I've done an openstack deployment using kolla ansible, and after deploying I want to add new services but without having to redo the deployment from scratch in order to keep both the configuration and the data already in use, is this doable ? as I couldn't find anything in the kolla-ansible docs.

2 1