December 2022 - openstack-discuss

Help overriding Nova policies (Ussuri)
by Jérôme BECOT 26 Dec '22

26 Dec '22

Hello, I should miss something, and I need some help. I've updated some rules that I placed in the /etc/nova/policy.yaml file. I use all defaults for the olso policies (ie scope is not enabled). When I generate the fulle policy with oslopolicy-policy-generator, the rules are applied in the generated output. If I test the policy with oslopolicy-checker under the user's token, the results matches the permissions, but Nova API continue to refuse the operation Policy check for os_compute_api:os-flavor-manage:create failed with credentials I'm using the openstack cli to make the request (openstack flavor create) Thanks for your help J

2 2

[tacker] Cancelling next irc meetings
by Yasufumi Ogawa 25 Dec '22

25 Dec '22

Hi team, Due to the holidays, we are cancelling next two meetings on 27th Dec and 3rd Jun. Cheers, Yasufumi

1 0

[kolla-ansible] telemetry data
by Satish Patel 25 Dec '22

25 Dec '22

Folks, I am deployed kolla-ansible and trying to set up telemetry for billing etc. But not able to get it working may be broken or something. In global.yml I turned on the following options and deployed kolla and it did install all the components but I am not seeing it deploy a ceilometer agent on compute nodes. How does it collect data from compute nodes if the ceilometer agent is not running on compute nodes? Did I miss something here? enable_ceilometer: "yes" enable_gnocchi: "yes" enable_cloudkitty: "yes"

2 2

The CFP for the OpenInfra Summit 2023 is open!
by Erin Disney 25 Dec '22

25 Dec '22

Hi Everyone! The CFP for the 2023 OpenInfra Summit (June 13-15, 2023) is NOW LIVE [1]! Check out the full list of tracks and submit a talk on your topic of expertise [2]. The CFP closes January 10, 2023, at 11:59 p.m. PT We are also now accepting submissions for Forum sessions [3]! What should you submit to the forum vs. the traditional CFP? For the Forum, submit discussion-oriented sessions, including challenges around different software components, working group progress or best practices to tackle common issues. Looking for other resources? Registration [4], sponsorships [5], travel support [6] and visa requests [7] are also all open! Find all the information on the OpenInfra Summit 2023 in one place [8]! Cheers, Erin [1] https://cfp.openinfra.dev/app/vancouver-2023/19/presentations <https://cfp.openinfra.dev/app/vancouver-2023/19/presentationshttps://cfp.op…> [2] https://openinfra.dev/summit/vancouver-2023/summit-tracks/ <https://openinfra.dev/summit/vancouver-2023/summit-tracks/> [3] https://cfp.openinfra.dev/app/vancouver-2023/20/ <https://cfp.openinfra.dev/app/vancouver-2023/20/> [4] http://openinfra.dev/summit/registration <http://openinfra.dev/summit/registration> [5] http://openinfra.dev/summit/vancouver-2023/summit-sponsor/ <http://openinfra.dev/summit/vancouver-2023/summit-sponsor/> [6] https://openinfrafoundation.formstack.com/forms/openinfra_tsp <https://openinfrafoundation.formstack.com/forms/openinfra_tsp> [7] https://openinfrafoundation.formstack.com/forms/visa_yvrsummit2023 <https://openinfrafoundation.formstack.com/forms/visa_yvrsummit2023> [8] https://openinfra.dev/summit/vancouver-2023 <https://openinfra.dev/summit/vancouver-2023>

2 1

the zun service run is OK , but at dashboard web no view zun serivce!
by 无数的星球 24 Dec '22

24 Dec '22

After I successfully installed the zun service, I logged in to the dashboard, but I could not see the zun entry I've rebooted all the machines，but invalid. thanks you !

2 1

Container access mounted device
by vincent lee 24 Dec '22

24 Dec '22

Hi, I have deployed a working OpenStack and would like to know if there are any possible options I can enable so that when creating a new container, files can be mounted to it, and a user from the container can access it. For instance, having a mounted device from the compute host and allowing the /dev/(mounted device name) file to be accessible in the container. Best regards, Vincent

2 1

the zun server (zun-api) in controller host error(s)
by 无数的星球 24 Dec '22

24 Dec '22

iAfter I followed the official documentation and fixed a 'pip3' error, it still failed to run successfully. This is an error reported by the zun api. Other components work normally. If you need my profile, it is attached root@controller:~# systemctl status zun-api ● zun-api.service - OpenStack Container Service API      Loaded: loaded (/etc/systemd/system/zun-api.service; enabled; vendor preset: enabled)      Active: failed (Result: exit-code) since Sun 2022-12-11 11:43:04 CST; 1min 38s ago     Process: 1017 ExecStart=/usr/local/bin/zun-api (code=exited, status=1/FAILURE)    Main PID: 1017 (code=exited, status=1/FAILURE) Dec 11 11:43:04 controller zun-api[1017]:     from zun import objects Dec 11 11:43:04 controller zun-api[1017]:   File "/usr/local/lib/python3.8/dist-packages/zun/objects/__init__.py", line 13, in <module> Dec 11 11:43:04 controller zun-api[1017]:     from zun.objects import compute_node Dec 11 11:43:04 controller zun-api[1017]:   File "/usr/local/lib/python3.8/dist-packages/zun/objects/compute_node.py", line 16, in <module> Dec 11 11:43:04 controller zun-api[1017]:     from zun.db import api as dbapi Dec 11 11:43:04 controller zun-api[1017]:   File "/usr/local/lib/python3.8/dist-packages/zun/db/api.py", line 32, in <module> Dec 11 11:43:04 controller zun-api[1017]:     (a)profiler.trace("db") Dec 11 11:43:04 controller zun-api[1017]: AttributeError: partially initialized module 'zun.common.profiler' has no attribute 'trace' (most likely due to a circular import) Dec 11 11:43:04 controller systemd[1]: zun-api.service: Main process exited, code=exited, status=1/FAILURE Dec 11 11:43:04 controller systemd[1]: zun-api.service: Failed with result 'exit-code'.

2 1

[all][tc] What's happening in Technical Committee: summary 2022 Dec 23: Reading: 5 min
by Ghanshyam Mann 23 Dec '22

23 Dec '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Dec 21. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-12-21-16.00.log.html * The TC meeting on Dec 28 is cancelled [1]. The next TC weekly meeting will be on Jan 4 Wed at 16:00 UTC, Feel free to add the topic to the agenda[2] by Jan 3. 2. What we completed this week: ========================= * Made inactive projects timeline as release milestone-2 of the cycle[3] 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[4]. Open Reviews ----------------- * Three open reviews for ongoing activities[5]. IMPORTANT: Tox 4 failure and time to fix them -------------------------------------------------------- tox is uncapped in ensure-tox [6]. With that tox4 is used in unit/functional tests job (or any job using ensure-role. If you are seeing failure in your project's jobs, please fix those on priority and if it needs time then you can cap tox it in your project zuul.yaml or for the particular job via 'ensure_tox_version' var. Mistral release and more maintainers ------------------------------------------- avanzagh who is the new maintainer of Mistral is in discussion with the release team for the required work for the Mistral release. We will keep monitoring the situation until the proposal for Mistral release deprecation is closed[7]. Project updates ------------------- * Add Cinder Huawei charm[8] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[9]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [10] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-December/03156… [2] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggesti… [3] https://review.opendev.org/c/openstack/governance/+/867062 [4] https://etherpad.opendev.org/p/tc-2023.1-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://review.opendev.org/c/zuul/zuul-jobs/+/866943 [7] https://review.opendev.org/c/openstack/governance/+/866562 [8] https://review.opendev.org/c/openstack/governance/+/867588 [9] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [10] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[manila] Cancelling Dec 29th weekly meeting
by Carlos Silva 23 Dec '22

23 Dec '22

Hello, Zorillas! As discussed in yesterday's weekly meeting, next week's IRC meeting (Dec 29th) is cancelled due to most of us being offline. The next weekly meeting is on January 5th. Happy holidays to those celebrating! Cheers, carloss

1 0

[neutron] bug deputy report December 19th -23th
by Miguel Lavalle 23 Dec '22

23 Dec '22

Hi, Here's this week's bugs deputy report: Under investigation at the moment of this report ==================================== https://bugs.launchpad.net/neutron/+bug/2000378 [OVN] orphaned virtual parent ports break new ports. Under investigation by ralonsoh Medium ====== https://bugs.launchpad.net/neutron/+bug/2000163 [FT] Error in "test_get_datapath_id". Proposed fix: https://review.opendev.org/c/openstack/neutron/+/868311 https://bugs.launchpad.net/neutron/+bug/2000164 [FT] Error in "test_dvr_update_gateway_port_with_no_gw_port_in_namespace". Needs owner https://bugs.launchpad.net/neutron/+bug/2000252 [OVN] "DBInconsistenciesPeriodics.check_for_inconsistencies" failing during port deletion. Needs owner https://bugs.launchpad.net/neutron/+bug/2000314 [OVS] Call to "driver.unregister" failing. Needs owner Low === https://bugs.launchpad.net/neutron/+bug/2000238 [FT] Remove the "Running command:" messages in the logs. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/868304

1 0