July 2021 - openstack-discuss - lists.openstack.org

Redhat RHEV Virtualisation and logical data volumes
by KK CHN 31 Jul '21

31 Jul '21

Is it practically or theoretically possible to export image/Disk as single image /Disk from RHEV/Virtualization Manager where VMs have logical volumes attached to it ? Any other data/information do I need to provide for the above question let know. Problem scenario is this: We have hosted VMs on RHEV virtualization environment. Each VM has associated Logical Volumes attached to the VM. We are planning to migrate our VMs to OpenStack (Ussuri, qemu KVM and Glance) Right now Our System Integrator who maintains these VMs on their RHEV virtualization environment exporting each VM as Three separate images. One for OS image, other for boot and third one for data volume disk image ( they use logical volumes for data storage, might be added disks when data storage was insufficient at any point of time. ) But I want to get each VM with data volumes as a single disk image . IS THIS THEORETICALLY or PRACTICALLY POSSIBLE using RHEV Virtualization tools ? if so how ? ( OR any other methods do this ?) OR am I asking a STUPID QUESTION ? If so WHY ? Kindly enlighten me !!! I am at the end of the rope with this issue. Thanks in advance, Kris

1 0

[sahara][stable] periodic-stable errors
by Előd Illés 31 Jul '21

31 Jul '21

Hi Sahara Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've seen that Sahara's stable branches started to fail as well so collected the recent failures with examples. Please take a look at them and try to fix them. The errors seem to be related to cinder's v2 removal ("No module named 'cinderclient.v2'"): sahara: stein - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/77f0f18b297240fa92eb5b22c8200598 sahara: train - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/23c860b5af74449bbed561d5853963ea sahara: ussuri - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/6e8ec09a4cc54eadaeaa9fe88eb249d9 sahara: victoria - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/db254fea259e482ab3ff3b404feeed28 sahara: wallaby - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/1e50a52edefe4f8191f0f0d529db7a63 [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

2 2

[cinder][qa][devstack][ci] need help running centos-8/opensuse-15 on stable/victoria
by Brian Rosmaita 31 Jul '21

31 Jul '21

Does anyone have any zuul jobs running in stable/victoria that use either of these nodesets: - devstack-single-node-centos-8 - devstack-single-node-opensuse-15 I can't get devstack to complete building on either (missing package, though different for each distro). I figure that someone in openstack must have this working, given that Python 3.6 and Centos-8 and OpenSUSE-15 are listed in the Tested Runtimes for Victoria [0]. Here's the failing patch if anyone would be kind enough to point out what I'm mis-configuring: https://review.opendev.org/c/openstack/python-cinderclient/+/800635/ thanks! brian [0] https://governance.openstack.org/tc/reference/runtimes/victoria.html

6 7

[nova][wallaby] Nova policy rule project_member_api not effective
by Taltavull Jean-Francois 31 Jul '21

31 Jul '21

Hi All, Despite the fact that oslopolicy-policy-generator --namespace nova shows the rules "project_member_api": "role:member and project_id:%(project_id)s" and "os_compute_api:servers:create": "rule:project_member_api", it is still possible to create a server even if you only have the role "member" on the project. Is this behavior normal or not ? Must we consider that we are in a phase of transition about nova default policies ? Thanks, Jean-Francois

2 3

[trove][stable] periodic-stable errors
by Előd Illés 31 Jul '21

31 Jul '21

Hi Trove Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've collected the recent failures with examples that are failing constantly. Please take a look at them and try to fix them wherever it is possible. Since the old branches seem quite abandoned in some cases, they might need maintainers to step up to keep those gates healthy, or in case there are no maintainers, then it might worth to think of transitioning those broken old branches to End of Life. :/ And the list (with possible root causes): * bandit should be constrained: trove: pike - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/c8da125f4a7f4dafaa5f3b337a0d14c2 trove: pike - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/9973f556913e439a912455712ecbd54a trove: queens - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/6ed08e9f7d25414e8ee04db14a753649 trove: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/0a3b1f6668a740c69f888c7272e24d58 trove: rocky - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/208c02dfcbc9487bbaca1eccc53e8a67 trove: rocky - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/f13cc87c4f104727ab4f4696ad7ed160 trove: stein - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/9aff516680074e11b52ea07fac389fa0 trove: train - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/db3b97cec2604318a7bd129fa8cd3bc2 * version conflict revealed with the new pip resolver: trove: stein - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/30f8f8a99fea4a93bab55b694c9e79e9 trove: train - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/00b400d2485a45fc997ebd35d48a506d trove: train - openstack-tox-py36 -- https://zuul.opendev.org/t/openstack/build/5e6a8f14ea93456ba70f5e1e3ee689a9 trove: train - openstack-tox-py37 -- https://zuul.opendev.org/t/openstack/build/e3c9201c92874e3fa25357171741cad2 [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

1 0

[neutron][stable] periodic-stable errors
by Előd Illés 31 Jul '21

31 Jul '21

Hi Neutron Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've collected the recent failures with examples that are failing constantly. Please take a look at them and try to fix them wherever it is possible. Since the old branches seem quite abandoned in some cases, they might need maintainers to step up to keep those gates healthy, or in case there are no maintainers, then it might worth to think of transitioning those broken old branches to End of Life. :/ And the list (with possible root causes): * horizon's pike + queens were deprecated: networking-bgpvpn: pike - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/553d4923eeca421c9ac56d193781b487 networking-bgpvpn: pike - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/0fe12998347c4fa19ce3e04450bd914d networking-bgpvpn: queens - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/d804b266bfdc408dbd1dd517b5901914 networking-bgpvpn: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/9151ba1cb74e4f569d863b7a90a8b702 * some dependency issues + unit tests are broken: neutron-vpnaas: queens - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/64d92abffe7d48b1bcc3d3f42f8a1a24 neutron-vpnaas: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/743f561a2bb34875b86917cfe8861a53 neutron-vpnaas: rocky - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/e700494509934ba995f8c4b0e69f4627 neutron-vpnaas: stein - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/4339034bc4014a0292310fd013d46caa neutron-vpnaas: victoria - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/83d8251153b64de488bae3972968256f neutron-vpnaas: victoria - openstack-tox-py36 -- https://zuul.opendev.org/t/openstack/build/02e214a1483a4778986697ba6c85cbf9 neutron-vpnaas: victoria - openstack-tox-py38 -- https://zuul.opendev.org/t/openstack/build/a746a0bc5a1c4caeb6b813a7dd83878c [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

1 0

[murano][stable] periodic-stable errors
by Előd Illés 31 Jul '21

31 Jul '21

Hi Murano Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've collected the recent failures with examples that are failing constantly. Please take a look at them and try to fix them wherever it is possible. Since the old branches seem quite abandoned in some cases, they might need maintainers to step up to keep those gates healthy, or in case there are no maintainers, then it might worth to think of transitioning those broken old branches to End of Life. :/ And the list (with possible root causes): * bandit should be constrained: murano: pike - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/6ee6c9548d6b47e79361151964992ddf murano: pike - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/fbfe0f67b90f4b3189a13e02a5b7f274 murano: queens - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/c254a7f764f547e4a5bf8467cbcbe24b murano: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/b9646137d45c49ab8f10c2031135d21e murano: rocky - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/63f53b3df8a940f6b86c450617882cfc murano: stein - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/be63abe6be9a4d1f90c8d74fd9c4a407 * broken unittest: murano: victoria - openstack-tox-py36 -- https://zuul.opendev.org/t/openstack/build/b403e1a7431a484e90b23738a56669c7 murano: victoria - openstack-tox-py38 -- https://zuul.opendev.org/t/openstack/build/7f886d7e21864f4d941ad0a03d61ec4d murano: wallaby - openstack-tox-py36 -- https://zuul.opendev.org/t/openstack/build/dc61998732ff4d13a6e8c9d1f82ccd8d murano: wallaby - openstack-tox-py38 -- https://zuul.opendev.org/t/openstack/build/cc2fa00e650d4cd1973fd76dc1649624 * and also master is broken. [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

1 0

[designate][stable] periodic-stable errors
by Előd Illés 31 Jul '21

31 Jul '21

Hi Designate Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've collected the recent failures with examples that are failing constantly. Please take a look at them and try to fix them wherever it is possible. Since the old branches seem quite abandoned in some cases, they might need maintainers to step up to keep those gates healthy, or in case there are no maintainers, then it might worth to think of transitioning those broken old branches to End of Life. :/ And the list (with possible root cause): * bandit should be constrained: designate: pike - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/810cf80432dc4b90a7367b5f2107147e designate: pike - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/11d042ab2e82478db75d877f3c62cd62 designate: queens - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/4cd73558ffb3402e8f25f602d85aec94 designate: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/6c0b8dd6cee24b7eab9153bfc0e1dd61 designate: rocky - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/8d4d56e05ec94870823d3e057ee8ea4a [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

1 0

[powervmstackers][multi-arch-sig][stable] periodic-stable errors
by Előd Illés 31 Jul '21

31 Jul '21

Hi PowerVMStackers and Multi-Arch SIG members, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've collected the recent failures with examples that are failing constantly. Please take a look at them and try to fix them wherever it is possible. Since the old branches seem quite abandoned in some cases, they might need maintainers to step up to keep those gates healthy, or in case there are no maintainers, then it might worth to think of transitioning those broken old branches to End of Life. :/ And the list: * ocata is mostly End of Life -- (also there is a patch to EOL ocata of the *-powervm: https://review.opendev.org/c/openstack/releases/+/801123 ) ceilometer-powervm: ocata - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/151e90c3c3eb48779759f469d76f02d7 nova-powervm: ocata - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/535ffa6750c74ab7a886f6fb3838ff4f * unit tests are broken: nova-powervm: pike - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/27bd093f615341e7a5563e3b9ea86f31 * dependency version conflict: nova-powervm: train - openstack-tox-py36 -- https://zuul.opendev.org/t/openstack/build/f9afc55de6dc452cbc88d98c837ab58f nova-powervm: train - openstack-tox-py37 -- https://zuul.opendev.org/t/openstack/build/0ea69ad9be8c4a269613573fa5014fe4 [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

1 0

[telemetry][stable] periodic-stable errors
by Előd Illés 31 Jul '21

31 Jul '21

Hi Telemetry Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've collected the recent failures with examples that are failing constantly. Please take a look at them and try to fix them wherever it is possible. Since the old branches seem quite abandoned in some cases, they might need maintainers to step up to keep those gates healthy, or in case there are no maintainers, then it might worth to think of transitioning those broken old branches to End of Life. :/ And the list (with possible root causes): * tenacity should be constrained for py27: ceilometer: pike - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/4bcb7e71d507465ea799cd289e6cc920 ceilometer: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/583d52b6096745ddbb18da23cf79fa75 ceilometer: rocky - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/03279061fddd4d14819c04feda3a1806 * kombu version should be constrained for py27: ceilometer: stein - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/219139b1814b4fd591ee7dc199f2e3da [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

1 0