[Yahoo-eng-team] [Bug 2007532] [NEW] Wrong description about minimum value of live_migration_downtime(_delay)
Public bug reported: Description === The parameter descriptions say live_migration_downtime_steps and live_migration_downtime_delay are rounded if too small values are given. However actually these parameters have minimum defined and oslo.config does not accept too small values and fail to load the config. Steps to reproduce == Configure [libvirt] live_migration_downtime = 50 [libvirt] live_migration_downtime_steps =2 Expected result === Values are rounded to the described minimum values Actual result = nova-compute fails to start because these does not meat the minimum requirement Environment === N/A Logs & Configs == N/A ** Affects: nova Importance: Undecided Assignee: Takashi Kajinami (kajinamit) Status: In Progress ** Changed in: nova Assignee: (unassigned) => Takashi Kajinami (kajinamit) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/2007532 Title: Wrong description about minimum value of live_migration_downtime(_delay) Status in OpenStack Compute (nova): In Progress Bug description: Description === The parameter descriptions say live_migration_downtime_steps and live_migration_downtime_delay are rounded if too small values are given. However actually these parameters have minimum defined and oslo.config does not accept too small values and fail to load the config. Steps to reproduce == Configure [libvirt] live_migration_downtime = 50 [libvirt] live_migration_downtime_steps =2 Expected result === Values are rounded to the described minimum values Actual result = nova-compute fails to start because these does not meat the minimum requirement Environment === N/A Logs & Configs == N/A To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/2007532/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 2007553] [NEW] [DHCP] TypeError: disable() got an unexpected keyword argument 'network_id'
Public bug reported: Snippet: https://paste.opendev.org/show/b4SBXPIlOGVWw8HJQFAP/ Error log: https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_e59/874057/1/check/neutron- tempest-plugin-openvswitch/e59aab5/controller/logs/screen-q-dhcp.txt ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2007553 Title: [DHCP] TypeError: disable() got an unexpected keyword argument 'network_id' Status in neutron: New Bug description: Snippet: https://paste.opendev.org/show/b4SBXPIlOGVWw8HJQFAP/ Error log: https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_e59/874057/1/check/neutron- tempest-plugin-openvswitch/e59aab5/controller/logs/screen-q-dhcp.txt To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2007553/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 2007565] [NEW] [tempest] "test_network_basic_ops" failing randomly
Public bug reported: Logs: https://e77ca85d21cbdb712ce7-c684a40c384a27e613f3f0e997584032.ssl.cf1.rackcdn.com/874073/1/check/neutron- ovn-tempest-ipv6-only-ovs-release/1431f0b/testr_results.html https://opensearch.logs.openstack.org/_dashboards/app/discover/#/?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-14d,to:now))&_a=(columns:!(_source),filters:!(),index:'94869730-aea8-11ec-9e6a-83741af3fdcd',interval:auto,query:(language:kuery,query:'message:%22tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops%22%20AND%20project:%22openstack%2Fneutron%22%20AND%20build_status:%22failure%22'),sort:!()) ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2007565 Title: [tempest] "test_network_basic_ops" failing randomly Status in neutron: New Bug description: Logs: https://e77ca85d21cbdb712ce7-c684a40c384a27e613f3f0e997584032.ssl.cf1.rackcdn.com/874073/1/check/neutron- ovn-tempest-ipv6-only-ovs-release/1431f0b/testr_results.html https://opensearch.logs.openstack.org/_dashboards/app/discover/#/?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-14d,to:now))&_a=(columns:!(_source),filters:!(),index:'94869730-aea8-11ec-9e6a-83741af3fdcd',interval:auto,query:(language:kuery,query:'message:%22tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops%22%20AND%20project:%22openstack%2Fneutron%22%20AND%20build_status:%22failure%22'),sort:!()) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2007565/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 2007574] [NEW] horizon does not support setuptools 67.3.1
Public bug reported: Recently setuptools 67.3.1 has been released, and it broke Kolla Horizon container builds. It seems that xstatic libraries rely on setuptools importing pkg_resources during build, which does not work in latest setuptools [1]. [1]: https://github.com/pypa/setuptools/issues/3824 ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/2007574 Title: horizon does not support setuptools 67.3.1 Status in OpenStack Dashboard (Horizon): New Bug description: Recently setuptools 67.3.1 has been released, and it broke Kolla Horizon container builds. It seems that xstatic libraries rely on setuptools importing pkg_resources during build, which does not work in latest setuptools [1]. [1]: https://github.com/pypa/setuptools/issues/3824 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/2007574/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1827120] Re: [SRU] application credentials created via Horizon with the admin project scope have project_id == None
This bug was fixed in the package horizon - 4:20.1.3-0ubuntu1~cloud1 --- horizon (4:20.1.3-0ubuntu1~cloud1) focal-xena; urgency=medium . * New stable point release for OpenStack Xena (LP: #2004032). * d/p/lp1827120.patch: Dropped. Fixed in stable point release. . horizon (4:20.1.2-0ubuntu1~cloud1) focal-xena; urgency=medium . * d/p/lp1827120.patch: Fix missing project_id in application credential create when user has both project+domain admin role (LP: #1827120). . horizon (4:20.1.2-0ubuntu1~cloud0) focal-xena; urgency=medium . * New upstream release for the Ubuntu Cloud Archive. . horizon (4:20.1.2-0ubuntu1) impish; urgency=medium . * New stable point release for OpenStack Xena (LP: #1972665). * Remove patches that have landed upstream: - d/p/0001-Fix-for-Resize-instance-button.patch . horizon (4:20.1.1-0ubuntu2) impish; urgency=medium . * d/p/0001-Fix-for-Resize-instance-button.patch: Fixes resize instance widget (LP: #1940834). . horizon (4:20.1.1-0ubuntu1) impish; urgency=medium . [ Corey Bryant ] * d/gbp.conf: Create stable/xena branch. . [ Felipe Reyes ] * New stable point release for OpenStack Xena (LP: #1962582). . horizon (4:20.1.0-0ubuntu1) impish; urgency=medium . * d/watch: Scope to 20.x series. * New upstream release for OpenStack Xena. . horizon (4:20.0.0+git2021091315.420eaa5ba-0ubuntu1) impish; urgency=medium . * New upstream snapshot for OpenStack Xena. . horizon (4:19.2.0+git2021072116.b58ac2894-0ubuntu1) impish; urgency=medium . * New upstream snapshot for OpenStack Xena. . horizon (4:19.2.0+git2021062815.310a24d05-0ubuntu1) impish; urgency=medium . * New upstream snapshot for OpenStack Xena. . horizon (4:19.2.0-0ubuntu1) hirsute; urgency=medium . * New upstream release for OpenStack Wallaby. * d/control: Align (Build-)Depends with upstream. . horizon (4:19.1.0-0ubuntu1) hirsute; urgency=medium . * d/watch: Fix tarball path. * New upstream stable point release for OpenStack Wallaby. * d/control: Align (Build-)Depends with upstream. . horizon (4:19.0.0+git2021012814.944902c5c-0ubuntu1) hirsute; urgency=medium . * New upstream snapshot for OpenStack Wallaby. . horizon (4:19.0.0-0ubuntu1) hirsute; urgency=medium . * d/watch: Scope to 19.x series. * New upstream release for OpenStack Wallaby. * d/p/fix-dashboard-django-wsgi.patch: Removed. Upstream removed deprecated file. * d/p/ubuntu_settings.patch: Refreshed. . horizon (4:18.6.1-0ubuntu2) hirsute; urgency=medium . * d/control: Ensure min version of python3-swiftclient can get capabilities when using ceph radosgw swift API (LP: #1902944). . horizon (4:18.6.1-0ubuntu1) groovy; urgency=medium . * New upstream release for OpenStack Victoria. . horizon (4:18.6.0-0ubuntu1) groovy; urgency=medium . [ Chris MacNaughton ] * d/control: Update VCS paths for move to lp:~ubuntu-openstack-dev. . [ Corey Bryant ] * New upstream release for OpenStack Victoria. . horizon (3:19.0.0~b3~git2020091105.79e505520-0ubuntu1) groovy; urgency=medium . * d/control: Remove Breaks/Replaces that are older than Focal (LP: #1878419). * New upstream snapshot for OpenStack Victoria. . horizon (3:19.0.0~b2~git2020073014.eb86389fa-0ubuntu1) groovy; urgency=medium . * New upstream snapshot for OpenStack Victoria. * d/bundle-xstatic.sh: Stop putting xstatic original tar into ../build-area. debuild needs it to be in ../ along with the horizon original tarball so that's where it should be placed. . horizon (3:19.0.0~b1~git2020071408.99ffd59a5-0ubuntu1) groovy; urgency=medium . * New upstream snapshot for OpenStack Victoria. . horizon (3:18.4.2~git2020070209.392bc2482-0ubuntu1) groovy; urgency=medium . * New upstream snapshot for OpenStack Victoria. * d/control: Align (Build-)Depends with upstream. * d/p/fix-skipped-config-files.patch: Dropped. Fixed upstream. * d/control: Update Standards-Version to 4.5.0. . horizon (3:18.3.2-0ubuntu2) groovy; urgency=medium . * d/p/fix-skipped-config-files.patch: Ensure that config files are included in the package (LP: #1872671). . horizon (3:18.3.2-0ubuntu1) groovy; urgency=medium . * New upstream release for OpenStack Ussuri (LP: #1877642). . horizon (3:18.2.1~git2020041013.754804667-0ubuntu3) focal; urgency=medium . * d/openstack-dashboard.postinst: Ensure static assets can be read by the apache user including the full path to the static directory. This changes the mode bits of /var/lib/openstack-dashboard to 755. (LP: #1871640). . horizon (3:18.2.1~git2020041013.754804667-0ubuntu2) focal; urgency=medium . * d/openstack-dashboard.postinst: Ensure static assets can be read by the apache user including the full path to the static directory (LP: #1871640). . horizon (3:18.2.1~git2020041013.754804667-0ubuntu1) focal; urgency=medium . * New upstream snapshot f
[Yahoo-eng-team] [Bug 2006496] Re: [L3-HA] "max_l3_agents_per_router" not honored when the redundancy is reduced
Reviewed: https://review.opendev.org/c/openstack/neutron/+/873107
Committed:
https://opendev.org/openstack/neutron/commit/5250598c804a38c55ff78cfb457b73d1b3cd7e07
Submitter: "Zuul (22348)"
Branch:master
commit 5250598c804a38c55ff78cfb457b73d1b3cd7e07
Author: Rodolfo Alonso Hernandez
Date: Wed Feb 8 13:14:19 2023 +0100
Improve scheduling L3/DHCP agents, missing lower binding indexes
This patch is covering an edge case that could happen when the number
of DHCP agents ("dhcp_agents_per_network") or L3 agents
("max_l3_agents_per_router") has been reduced and there are more agents
assigned than the current number. If the user removes any agent
assignation from a L3 router or a DHCP agent, it is possible to remove
first the lower binding assigned registers.
Now the method ``get_vacant_binding_index`` calculates the number of
agents bound and the number required. If a new one is needed, the
method returns first the lower binding indexes not used.
Closes-Bug: #2006496
Change-Id: I25145c088ffdca47acfcb7add02b1a4a615e4612
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2006496
Title:
[L3-HA] "max_l3_agents_per_router" not honored when the redundancy is
reduced
Status in neutron:
Fix Released
Bug description:
Related bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2166197
NOTE: Config option "router_distributed" must be False.
This issue is happening when initially we have a
"max_l3_agents_per_router" number, we create a router and then we
reduce the redundancy.
For example, if "max_l3_agents_per_router=3" and we create a HA router.
Neutron will create 3 instances of this router and will create the
corresponding "routerl3agentbindings" registers. E.g.:
MariaDB [ovs_neutron]> select * from routerl3agentbindings;
+--+--+---+
| router_id| l3_agent_id
| binding_index |
+--+--+---+
| f8d3fec5-4648-48e9-b546-94f2e135df77 | 5c54529e-1f4e-4332-9674-96a1d15a16b2
| 1 |
| f8d3fec5-4648-48e9-b546-94f2e135df77 | 8112e03e-9191-495d-aea2-d2d7cd621767
| 2 |
| f8d3fec5-4648-48e9-b546-94f2e135df77 | 850beebc-3144-4673-a4cc-142162dba436
| 3 |
+--+--+---+
Now we reduce the redundancy to "max_l3_agents_per_router=1". If we remove
the agent assignation for those registers with "binding_index" different to 1,
the next time the router is updated, the L3 scheduler will create a new
assignation with "binding_index=1". When the router is updated (a subnet is
added or removed, a FIP is assigned or removed, etc), the scheduler is called.
This method [1] will determine what is the next index that needs to be created
(that is used both for the DHCP scheduler and the L3 scheduler).
In the given example, if the agents with "binding_index" different from 1 are
removed, the vacant binding index method [1] will return 1:
open_slots = sorted(list(all_indicies - set(binding_indices)))
--> all_indicies = {1}
--> binding_indices = {3} # for example
--> open_slots = {1} # instead of an empty set(), as expected here.
[1]https://github.com/openstack/neutron/blob/7c3d6c414d3c0f085cae94b6f2186c4415a9298b/neutron/scheduler/base_scheduler.py#L102-L107
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2006496/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 2007635] [NEW] ask for large-scale deployment help
Public bug reported: hello, all, this is not a bug, I want some help. I am new for openstack, I want to find some information about official large-scale openstack deployment and pressure test indicator data, for example, how many compute nodes and vms can a sigle openstack region (not use nova cell and only three controller node) have at most, how manay vms can be created/stop/start/migrate at a same time? Is there any official data about these, or any where I can find these information, Thank you for help!! ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/2007635 Title: ask for large-scale deployment help Status in OpenStack Compute (nova): New Bug description: hello, all, this is not a bug, I want some help. I am new for openstack, I want to find some information about official large-scale openstack deployment and pressure test indicator data, for example, how many compute nodes and vms can a sigle openstack region (not use nova cell and only three controller node) have at most, how manay vms can be created/stop/start/migrate at a same time? Is there any official data about these, or any where I can find these information, Thank you for help!! To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/2007635/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
