[Yahoo-eng-team] [Bug 2025497] Re: Unable to delete image from glance cinder store
Incorrect glance-api conf file.
Once the correct information was in there it works fine
** Changed in: glance
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/2025497
Title:
Unable to delete image from glance cinder store
Status in Glance:
Invalid
Bug description:
OpenStack master branch built using Devstack 6/30/23
Configuring glance to use cinder backends as multistores.
Configuration works as documented and images can be created in the
cinder backend, however when trying to delete any image from glance
that is located in a cinder store this will fail with the following:
stack@multi1:~$ glance image-delete 7934ed5e-9958-47e2-9a6a-5aab9a33dfca
'HTTP 500 Internal Server Error: The server has either erred or is incapable
of performing the requested operation.': Unable to delete image
'7934ed5e-9958-47e2-9a6a-5aab9a33dfca'
The image in question is:
stack@multi1:~$ glance image-show 7934ed5e-9958-47e2-9a6a-5aab9a33dfca
+--+--+
| Property | Value
|
+--+--+
| checksum | a3bf59112e4930ef32397be81c761a80
|
| container_format | bare
|
| created_at | 2023-06-30T16:32:14Z
|
| disk_format | raw
|
| id | 7934ed5e-9958-47e2-9a6a-5aab9a33dfca
|
| locations| [{"url":
"cinder://pure2/7f299476-9245-4648-9e2e-a9cca62f9354", "metadata": |
| | {"store": "pure2"}}]
|
| min_disk | 0
|
| min_ram | 0
|
| name | Ubuntu 22.04
|
| os_hash_algo | sha512
|
| os_hash_value|
0bbfdb7382c8767f60d8bb6da703819dc6fdaef36e6e544740eb5fffcb677d11ba23c3eed9e885b8
|
| |
b82d8444a7adcfd8712c2dc4dcb8f9589f5a9787a6879aa1
|
| os_hidden| False
|
| owner| 6f9ddcf4d9f148789b03a20447a39f8c
|
| owner_specified.openstack.md5|
|
| owner_specified.openstack.object | images/Ubuntu 22.04
|
| owner_specified.openstack.sha256 |
|
| protected| False
|
| size | 2361393152
|
| status | active
|
| stores | pure2
|
| tags | []
|
| updated_at | 2023-06-30T16:33:00Z
|
| virtual_size | 2361393152
|
| visibility | public
|
+--+--+
The error in the glance-api log file is:
Jun 30 17:54:45 multi1 devstack@g-api.service[1052009]: ERROR
glance.common.wsgi [None req-2e0ef496-2877-431c-af02-fe439fe33af2 admin admin]
Caught error: De
[Yahoo-eng-team] [Bug 2024903] Re: [neutron-lib] FT "test_negative_update_floatingip_port_forwarding" failing randomly very often
** Changed in: neutron Status: Fix Committed => 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/2024903 Title: [neutron-lib] FT "test_negative_update_floatingip_port_forwarding" failing randomly very often Status in neutron: Fix Released Bug description: Checking the zuul builds [1], the first time this test started to fail was on 2023-05-31 11:32:02 [2]. This issue is also affecting "neutron-functional-with-sqlalchemy- master" because it is using neutron-lib master branch. [1]https://zuul.opendev.org/t/openstack/builds?job_name=neutron-functional-with-uwsgi&project=openstack%2Fneutron-lib&result=FAILURE&skip=0 [2]https://zuul.opendev.org/t/openstack/build/794b34cbece9491a950ed7c920760cd2 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2024903/+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 2025653] Re: glance image-import failure with all-stores
My bad - failed to configure the staging area for multistore glance
Please ignore
** Changed in: glance
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/2025653
Title:
glance image-import failure with all-stores
Status in Glance:
Invalid
Bug description:
devstack build of master from 6/30/23
Glance is configured with 3 cinder stores and an image has been
uploaded to one of these stores.
When trying to copy the image to all the stores image-import fails
with logged error of:
glance_store.exceptions.StoreAddDisabled: Configuration for store
failed. Adding images to this store is disabled.
Command issued was:
glance image-import 7934ed5e-9958-47e2-9a6a-5aab9a33dfca --all-
stores true --import-method copy-image
Image information:
stack@multi1:~$ glance image-show 7934ed5e-9958-47e2-9a6a-5aab9a33dfca
+--+--+
| Property | Value
|
+--+--+
| checksum | a3bf59112e4930ef32397be81c761a80
|
| container_format | bare
|
| created_at | 2023-06-30T16:32:14Z
|
| disk_format | raw
|
| id | 7934ed5e-9958-47e2-9a6a-5aab9a33dfca
|
| locations| [{"url":
"cinder://pure2/7f299476-9245-4648-9e2e-a9cca62f9354", "metadata": |
| | {"store": "pure2"}}]
|
| min_disk | 0
|
| min_ram | 0
|
| name | Ubuntu 22.04 (on pure2)
|
| os_glance_failed_import |
|
| os_glance_importing_to_stores| pure1,pure3
|
| os_hash_algo | sha512
|
| os_hash_value|
0bbfdb7382c8767f60d8bb6da703819dc6fdaef36e6e544740eb5fffcb677d11ba23c3eed9e885b8
|
| |
b82d8444a7adcfd8712c2dc4dcb8f9589f5a9787a6879aa1
|
| os_hidden| False
|
| owner| 6f9ddcf4d9f148789b03a20447a39f8c
|
| owner_specified.openstack.md5|
|
| owner_specified.openstack.object | images/Ubuntu 22.04
|
| owner_specified.openstack.sha256 |
|
| protected| False
|
| size | 2361393152
|
| status | active
|
| stores | pure2
|
| tags | []
|
| updated_at | 2023-07-03T13:46:25Z
|
| virtual_size | 2361393152
|
| visibility | public
|
+--+--+
Glance stores information:
stack@multi1:~$ glance stores-info
+
[Yahoo-eng-team] [Bug 2025653] [NEW] glance image-import failure with all-stores
Public bug reported:
devstack build of master from 6/30/23
Glance is configured with 3 cinder stores and an image has been uploaded
to one of these stores.
When trying to copy the image to all the stores image-import fails with
logged error of:
glance_store.exceptions.StoreAddDisabled: Configuration for store
failed. Adding images to this store is disabled.
Command issued was:
glance image-import 7934ed5e-9958-47e2-9a6a-5aab9a33dfca --all-stores
true --import-method copy-image
Image information:
stack@multi1:~$ glance image-show 7934ed5e-9958-47e2-9a6a-5aab9a33dfca
+--+--+
| Property | Value
|
+--+--+
| checksum | a3bf59112e4930ef32397be81c761a80
|
| container_format | bare
|
| created_at | 2023-06-30T16:32:14Z
|
| disk_format | raw
|
| id | 7934ed5e-9958-47e2-9a6a-5aab9a33dfca
|
| locations| [{"url":
"cinder://pure2/7f299476-9245-4648-9e2e-a9cca62f9354", "metadata": |
| | {"store": "pure2"}}]
|
| min_disk | 0
|
| min_ram | 0
|
| name | Ubuntu 22.04 (on pure2)
|
| os_glance_failed_import |
|
| os_glance_importing_to_stores| pure1,pure3
|
| os_hash_algo | sha512
|
| os_hash_value|
0bbfdb7382c8767f60d8bb6da703819dc6fdaef36e6e544740eb5fffcb677d11ba23c3eed9e885b8
|
| |
b82d8444a7adcfd8712c2dc4dcb8f9589f5a9787a6879aa1
|
| os_hidden| False
|
| owner| 6f9ddcf4d9f148789b03a20447a39f8c
|
| owner_specified.openstack.md5|
|
| owner_specified.openstack.object | images/Ubuntu 22.04
|
| owner_specified.openstack.sha256 |
|
| protected| False
|
| size | 2361393152
|
| status | active
|
| stores | pure2
|
| tags | []
|
| updated_at | 2023-07-03T13:46:25Z
|
| virtual_size | 2361393152
|
| visibility | public
|
+--+--+
Glance stores information:
stack@multi1:~$ glance stores-info
+--+--+
| Property | Value
|
+--+--+
| stores | [{"id": "pure1", "description": "Pure Array 1"}, {"id": "pure2",
"description": |
| | "Pure Array 2", "default": "true"}, {"id": "pure3", "description":
"Pure"}] |
[Yahoo-eng-team] [Bug 2025055] Re: [rfe][ml2] Add a new API that supports cloning a specified security group
** Changed in: neutron
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2025055
Title:
[rfe][ml2] Add a new API that supports cloning a specified security
group
Status in neutron:
Won't Fix
Bug description:
Hi everyone：
We want to define a new api that supports cloning a specified
security_group.
Consider the following case:
If the user wants to create a new security_group with the same rules as a
created security_group, he should do some duplicate actions to create rules.
It looks expensive, so that we want to define a new API that
supports create a new security_group and automatically copy the rules
from the specified security_group.
API likes:
PUT /v2.0/security-groups/{security_group_id}/clone
{
"security_group": {
"name": "newsecgroup",
"description": "cloning security group from test",
"stateful": true
}
}
Does anyone have other ideas?
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2025055/+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 2025129] Re: DvrLocalRouter init references namespace before it is created
** Changed in: neutron Status: Confirmed => 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/2025129 Title: DvrLocalRouter init references namespace before it is created Status in neutron: Fix Released Bug description: Description --- When the DvrLocalRouter object is instantiated, it calls the the _load_used_fip_information() function. In some cases this function will try to add ip rules in a specific network namespace however that namespace may not exist at the time. This results in neutron.privileged.agent.linux.ip_lib.NetworkNamespaceNotFound being thrown. Pre-conditions -- - DVR is in use and the created router is distributed and HA - The state file 'fip-priorities' is missing some entires which results in https://opendev.org/openstack/neutron/src/commit/0c5d4b872899497437d1399c845be756103a46d3/neutron/agent/l3/dvr_local_router.py#L76 being skipped - The qrouter network namespace does not exist (possibly due to a reboot of the host or something similar) Step-by-step reproduction steps --- - Setup OpenStack with DVR enabled - Create a HA router with an external subnet attached so we can use the IPs as FIPs - Create a VM with a FIP attached from the aforementioned router - SSH to the host running the aforementioned VM and: - Delete the qrouter namespace associated with this router - Remove the entry for the FIP from the fip-priorities state file in the Neutron state directory - Restart the Neutron L3 agent Expected output --- Neutron L3 agent should restart without any errors. Actual output - Neutron L3 agent throws a NetworkNamespaceNotFound exception for each missing FIP in the fip-priorities state file, fails to setup the router and then retries. Note that if there are more than 5 missing FIP entires in the fip-priorities file then the router setup fails completely as it hits the retry limit specified in https://opendev.org/openstack/neutron/src/commit/0c5d4b872899497437d1399c845be756103a46d3/neutron/agent/l3/agent.py#L730-L733. This leaves the router completely broken and not setup on the node resulting in broken networking for all VMs using that router on a particular host. Version --- - OpenStack version - master/zed - Linux distro - AlmaLinux9 - Deployed via Kolla Ansible To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2025129/+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 2025368] Re: [sRBAC] Subnets permissions now inherit from the parent resource Network
** 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/2025368 Title: [sRBAC] Subnets permissions now inherit from the parent resource Network Status in neutron: Fix Released Bug description: Since [1], Subnets use the same policy rules as the parent resource Network. With neutron-lib 3.7.0 that releases this patch [1], a unit test is failing [2][3] [1]https://review.opendev.org/c/openstack/neutron-lib/+/886746 [2]https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_ef9/887270/1/check/cross-neutron-py310/ef93cf7/testr_results.html [3]https://paste.opendev.org/show/bmgNmJC6XsaUGERjurRR/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2025368/+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 2025486] Re: [stable/wallaby] neutron-tempest-plugin-scenario-ovn-wallaby fails on ovn git clone
** Changed in: neutron Status: Confirmed => Invalid ** Also affects: devstack Importance: Undecided Status: New ** Changed in: devstack Status: New => In Progress ** Changed in: devstack Assignee: (unassigned) => yatin (yatinkarel) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2025486 Title: [stable/wallaby] neutron-tempest-plugin-scenario-ovn-wallaby fails on ovn git clone Status in devstack: In Progress Status in neutron: Invalid Bug description: Since 2023-06-30, the neutron-tempest-plugin-scenario-ovn-wallaby started to fail 100% in stable/wallaby backports: https://zuul.opendev.org/t/openstack/builds?job_name=neutron-tempest-plugin-scenario-ovn-wallaby&project=openstack/neutron Sample failure grabbed from https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_288/887253/2/check/neutron-tempest-plugin-scenario-ovn-wallaby/288071d/job-output.txt 2023-06-30 11:00:07.584319 | controller | + functions-common:git_timed:644 : timeout -s SIGINT 0 git clone https://github.com/ovn-org/ovn.git /opt/stack/ovn --branch 36e3ab9b47e93af0599a818e9d6b2930e49473f0 2023-06-30 11:00:07.587213 | controller | Cloning into '/opt/stack/ovn'... 2023-06-30 11:00:07.828809 | controller | fatal: Remote branch 36e3ab9b47e93af0599a818e9d6b2930e49473f0 not found in upstream origin I think I recall some recent fixes (to devstack maybe) to change git clone/checkout, is it related and just a missing backport to wallaby? Newer branches are fine To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/2025486/+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 2025637] [NEW] [ovn-octavia-provider] FIP traffic not distributed for members' FIP after lb cascade deletion
Public bug reported: When a member of a loadbalancer has a FIP, it gets centralized (mac info removed from NAT table) due to requirements on OVN side. When a member gets deleted from a loadbalancer, the mac information gets updated in the NAT table and the traffic to the FIP gets distributed again. However, if the whole loadbalancer gets deleted with the cascade option, the traffic to the member FIP is left centralized (without the NAT table being updated with the MAC again) ** Affects: neutron Importance: Undecided Assignee: Luis Tomas (luis5tb) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Luis Tomas (luis5tb) ** Changed in: neutron Status: New => In Progress ** Summary changed: - [ovn-octavia-provider] DVR traffic not reenabled for members' FIP upon cascade deletion + [ovn-octavia-provider] FIP traffic not distributed for members' FIP after lb cascade deletion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2025637 Title: [ovn-octavia-provider] FIP traffic not distributed for members' FIP after lb cascade deletion Status in neutron: In Progress Bug description: When a member of a loadbalancer has a FIP, it gets centralized (mac info removed from NAT table) due to requirements on OVN side. When a member gets deleted from a loadbalancer, the mac information gets updated in the NAT table and the traffic to the FIP gets distributed again. However, if the whole loadbalancer gets deleted with the cascade option, the traffic to the member FIP is left centralized (without the NAT table being updated with the MAC again) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2025637/+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 2025618] [NEW] [UT] "test_negative_update_floatingip_port_forwarding" does not create the ports in the correct subnet
Public bug reported: The ``NeutronDbPluginV2TestCase.port`` method input parameters are misleading. The "subnet" parameter won't create a port in the subnet selected; the method will extract the network and will enforce only the creation of the port on this network. In order to create a port on the required subnet, the parameter "fixed_ips" should be provided instead. The test ``test_negative_update_floatingip_port_forwarding`` is failing in [1]. [1]https://438434f768f3cb6b0f33-325b4a96905c9937625b58a50d186e45.ssl.cf2.rackcdn.com/887270/1/gate/cross- neutron-py310/e22eb16/testr_results.html ** Affects: neutron Importance: High Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez) ** Changed in: neutron Importance: Undecided => High ** Description changed: The ``NeutronDbPluginV2TestCase.port`` method input parameters are misleading. The "subnet" parameter won't create a port in the subnet selected; the method will extract the network and will enforce only the creation of the port on this network. In order to create a port on the required subnet, the parameter "fixed_ips" should be provided instead. + + The test ``test_negative_update_floatingip_port_forwarding`` is failing + in [1]. + + [1]https://438434f768f3cb6b0f33-325b4a96905c9937625b58a50d186e45.ssl.cf2.rackcdn.com/887270/1/gate/cross- + neutron-py310/e22eb16/testr_results.html -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2025618 Title: [UT] "test_negative_update_floatingip_port_forwarding" does not create the ports in the correct subnet Status in neutron: In Progress Bug description: The ``NeutronDbPluginV2TestCase.port`` method input parameters are misleading. The "subnet" parameter won't create a port in the subnet selected; the method will extract the network and will enforce only the creation of the port on this network. In order to create a port on the required subnet, the parameter "fixed_ips" should be provided instead. The test ``test_negative_update_floatingip_port_forwarding`` is failing in [1]. [1]https://438434f768f3cb6b0f33-325b4a96905c9937625b58a50d186e45.ssl.cf2.rackcdn.com/887270/1/gate/cross- neutron-py310/e22eb16/testr_results.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2025618/+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 2025466] Re: [OVN] OVN agent should register the correct config options
** Changed in: neutron Status: New => 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/2025466 Title: [OVN] OVN agent should register the correct config options Status in neutron: Fix Released Bug description: Commit [1] reduced the number of loaded config options when the OVN agent is started. However this patch removed the load of the core common options, as seen in the puppet CI [2]: """ Jun 29 23:45:47 np0003949382.novalocal neutron-ovn-agent[95988]: sys.exit(main()) Jun 29 23:45:47 np0003949382.novalocal neutron-ovn-agent[95988]: File "/usr/lib/python3.9/site-packages/neutron/cmd/eventlet/agents/ovn_neutron_agent.py", line 26, in main Jun 29 23:45:47 np0003949382.novalocal neutron-ovn-agent[95988]: ovn_neutron_agent.main() Jun 29 23:45:47 np0003949382.novalocal neutron-ovn-agent[95988]: File "/usr/lib/python3.9/site-packages/neutron/agent/ovn/ovn_neutron_agent.py", line 37, in main Jun 29 23:45:47 np0003949382.novalocal neutron-ovn-agent[95988]: config.init(sys.argv[1:]) Jun 29 23:45:47 np0003949382.novalocal neutron-ovn-agent[95988]: File "/usr/lib/python3.9/site-packages/neutron/common/config.py", line 105, in init Jun 29 23:45:47 np0003949382.novalocal neutron-ovn-agent[95988]: msg = validators.validate_regex(cfg.CONF.base_mac, validators.MAC_PATTERN) Jun 29 23:45:47 np0003949382.novalocal neutron-ovn-agent[95988]: File "/usr/lib/python3.9/site-packages/oslo_config/cfg.py", line 2223, in __getattr__ Jun 29 23:45:47 np0003949382.novalocal neutron-ovn-agent[95988]: raise NoSuchOptError(name) Jun 29 23:45:47 np0003949382.novalocal neutron-ovn-agent[95988]: oslo_config.cfg.NoSuchOptError: no such option base_mac in group [DEFAULT] """ [1]https://review.opendev.org/c/openstack/neutron/+/878565 [2]https://logserver.rdoproject.org/openstack-periodic-daily/review.rdoproject.org/rdoinfo/master/weirdo-bobcat-promote-puppet-scenario005-centos-stream-9/9f93f3b/logs/weirdo-project/logs/systemctl.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2025466/+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 2025598] [NEW] I can't launch instances on OpenStack
Public bug reported: I can't launch instances on OpenStack Hi all, I manually installed all OpenStack services and components on Ubuntu 22.04, the installation of the services seems to have been successful, everything works except the instances, which as soon as I try to create one I get this error: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-46aedbe5-4081-4988-a1e2-4c2da4f83996). I tried adding port 5000 via iptables but it didn't work much and neither did adding "/v3" before the auth_uri directive from nova.conf from [keystone_authtoken] what am i doing wrong?, where could be the problem? I'm on OpenStack Yoga post my nova-api.log Is the problem due to some misconfiguration or missing package? ** Affects: nova Importance: Undecided Status: New ** Attachment added: "nova-api log" https://bugs.launchpad.net/bugs/2025598/+attachment/5683489/+files/nova-api.log -- 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/2025598 Title: I can't launch instances on OpenStack Status in OpenStack Compute (nova): New Bug description: I can't launch instances on OpenStack Hi all, I manually installed all OpenStack services and components on Ubuntu 22.04, the installation of the services seems to have been successful, everything works except the instances, which as soon as I try to create one I get this error: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-46aedbe5-4081-4988-a1e2-4c2da4f83996). I tried adding port 5000 via iptables but it didn't work much and neither did adding "/v3" before the auth_uri directive from nova.conf from [keystone_authtoken] what am i doing wrong?, where could be the problem? I'm on OpenStack Yoga post my nova-api.log Is the problem due to some misconfiguration or missing package? To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/2025598/+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
