Public bug reported:
If an Azure VM is rebooted after being moved to a different host (e.g.
after a deallocate operation or after a service-heal to remove a bad
host from service), the ephemeral drive exposed to the VM is reset to
the default state (NTFS format). The Azure data source detects
** Also affects: keystone (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1825214
Title:
Install and configure
I suspect this is a packaging issue and not an issue with the keystone
documentation or source code, so tagging the Ubuntu team.
** Also affects: keystone (Ubuntu)
Importance: Undecided
Status: New
** Changed in: keystone
Status: Confirmed => Incomplete
--
You received this
Public bug reported:
Stein nova-api running under uWSGI presents an AMQP issue. The first API
call that requires RPC creates an AMQP connection and successfully
completes. Normally regular heartbeats would be sent from this point on,
to maintain the connection. This is not happening. After a few
Public bug reported:
When you configure a region_name for Ironic, an endpoint isn't properly
passed on to the ironic client. This means that the region_name won't be
respected.
The current workaround is to provide an api_endpoint (or
endpoint_override) for Ironic.
** Affects: nova
Gerrit is down but I've written a functional regression test to recreate
the bug and attached it as a patch for now.
** Description changed:
- This is purely based on code inspection right now, I need to write a
- functional test to recreate the issue.
-
While triaging bug 1821594 it got me
I think this possibly introduced a regression bug 1825537 so I've marked
Ocata as won't fix for this bug.
** Changed in: nova/ocata
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
Public bug reported:
This is purely based on code inspection right now, I need to write a
functional test to recreate the issue.
While triaging bug 1821594 it got me thinking about handling placement
allocations during resize when something fails, which got me thinking
about an older fix:
Public bug reported:
By doing this:
tox -e py36 -- nova.tests.unit.test_rpc --until-failure
I'm able to trigger this setup failure:
nova.tests.unit.test_rpc.TestRPC.test_add_extra_exmods
--
Captured traceback:
~~~
Public bug reported:
When bulk creating auto address IPv6 subnets, port update happens within
a transaction:
2019-03-28 15:48:50.894 2377 ERROR neutron.pecan_wsgi.hooks.translation
[req-e84aba73-3fc5-4b3f-bf41-a7e762af4bdf
166b7ed45cd6404e884ba63f89e88bf9 2ce6b2792eee4dc88639a3575f1ac7f0 -
Public bug reported:
After creating security_groups the name of security_groups does not
appear automatically. We need to refresh it manually:
After Creation of security_group, we directly jump to the manage Rules page it
shows rules of the created security group that is okay but when we come
Public bug reported:
Success Message should appear after volume creation and deletion:
This is just suggetsion for the UI Side.
As all the services like network topology, image, flavor, etc show
success when it is created and deleted.
The same thing should happen in volume as well. Volume only
My bad, seems the last version will raise an error if VM reboot too
quick, the code will enter into 2 loops ,the first loop we get events
both include added and updated, but the second loop will handle the
port, and add it back to sg_port_map
** Changed in: neutron
Status: In Progress =>
13 matches
Mail list logo
