Duplicated to the bug:
https://bugs.launchpad.net/neutron/+bug/1777598
Please backport this:
https://review.openstack.org/#/c/576418/
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
could you please help approve the changes to add one option to send the
events into the kvp pool.
** Affects: cloud-init
Importance: Undecided
Status: New
** Merge proposal linked:
Public bug reported:
Neutron API provides [0] GET and DELETE functions for
auto_allocated_topology, but policy.json contains only GET rule [1].
We need to update policy.json to include delete RBAC rule.
[0]
On second thought, I think we should add a note to the documentation
stating that subnets inherit their networks RBAC policies
** Summary changed:
- Subnets accessible when project_id != my project id with multiple subnets in
single RBAC access_as_shared network
+ Networking guide doesn't
Hi loonatic,
What you refer as "UNEXPECTED" three times above is actually the
expected behavior, per the subnets data model:
https://github.com/openstack/neutron/blob/master/neutron/db/models_v2.py#L201-L206.
Once you give other projects access to the network through RBAC
policies, its subnets
This has been broken since newton:
https://github.com/openstack/nova/commit/74ab427d4796d8a386f84a15cc49188c2a60f8f1
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/pike
Public bug reported:
When we resize a server, we update the RequestSpec.flavor because for
later move operations of the server, the RequestSpec is what gets passed
to the scheduler, so naturally we need the RequestSpec.flavor to match
the instance.flavor after the instance is resized. That
Public bug reported:
This is a simple performance optimization bug. When creating multiple
servers, if they are in an affinity group they are going to be on the
same host. Or if simply the scheduler configuration is such that
instances are packed onto as few hosts as possible rather than spread,
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/ocata
Status: New => Triaged
** Changed in:
Public bug reported:
I found this in the starlingx diff for nova:
https://github.com/starlingx-staging/stx-
nova/commit/71acfeae0d1c59fdc77704527d763bd85a276f9a#diff-
afb9c0c0ca5276c7eacd987bbf51d8e6R447
For volume-backed instances, the instance image_meta comes from the
volume_image_metadata
See https://review.openstack.org/#/c/565601/5 for more context - that
was changed because it failed the ceph job, because apparently with rbd
volumes you can't delete the volume snapshots until the original volume
is deleted, which in the cinder API you normally can't do that if there
are
Public bug reported:
cloud-init pre-networking fails when grub is configured to use a static
IP with the 'autoconf' field set to 'none'
(https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt).
Cloud provider: vsphere
Static IP is configured here (/etc/default/grub).
---
#
Public bug reported:
Confirmation of a resize is an RPC operation. If a compute node fails
after a migration has been put into the "confirming" status there is no
way to confirm it again, causing the state of the instance to get
"stuck".
In the case of confirm_resize(), I don't see any problem
** Also affects: devstack
Importance: Undecided
Status: New
** No longer affects: nova
** Changed in: devstack
Status: New => Fix Released
** Changed in: devstack
Importance: Undecided => Medium
** Changed in: devstack
Assignee: (unassigned) => Pawel Koniszewski
Public bug reported:
The user and group members of a project are not displayed directly in
the project details view for an admin user.
It could be interesting for administrator to display (by example as
tabs) the list of users with their roles on the project and the list of
group with their
Public bug reported:
The pause:
https://developer.openstack.org/api-ref/compute/#pause-server-pause-
action
And suspend:
https://developer.openstack.org/api-ref/compute/#suspend-server-suspend-
action
APIs just say they pause and suspend the server, which does not really
tell the user
Public bug reported:
I found it hard to understand what configuration was needed when
reading:
"The Neutron metadata API proxy should be global across all cells, and
thus be configured as an API-level service with access to the
[api_database]/connection information."
Which service is it
Public bug reported:
Description
===
The nova-api-metadata service fails to provide metadata to guests
when it is providing metadata for multiple cells.
Steps to reproduce
==
Deploy a a environment with multiple cells and a single
nova-api-metadata service. Requests by
Public bug reported:
Hi colleagues,
I'm using Heat to provision Neutron and faced the bug which is rather
Neutron's than Heat's, since Neutron receives all information,
provisions control plane ('openstack port/router show' gives updated
config), but do nothing in dataplane.
My config, which
Public bug reported:
1. The following stanzas in /etc/cloud/cloud.cfg:
```
cloud_final_modules:
# always update+upgrade on boot
- [package-update-upgrade-install, always]
packages: # will run apt-update
- git
package_update: true
package_upgrade: true
package_reboot_if_required: true
```
Public bug reported:
Use Case:
User wants to use provider network with some external dhcp server.
Now he need to add proper security group rule to allow incoming dhcp traffic to
his instances.
Proposed solution:
Add new attribute to network, something like "external-dhcp".
Ports connected to
Public bug reported:
Description
===
Changing a node's cell through nova.conf and then restarting nova-compute will
result in duplicate hypervisor records for that node.
Steps to reproduce
==
1. edit nova.conf on a compute node, to update [database].connection and
Reviewed: https://review.openstack.org/583967
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=7a92d44bfa6aeb96f61b95a96b4248a80b5d4544
Submitter: Zuul
Branch:master
commit 7a92d44bfa6aeb96f61b95a96b4248a80b5d4544
Author: Slawek Kaplonski
Date: Thu Jul 19 16:00:04
Public bug reported:
The generic group type named "default_cgsnapshot_type" is reserved for the
consistency group and we cannot use a generic group using
"default_cgsnapshot_type".
"default_cgsnapshot_type" should not be listed in "Group Type" selection in
"Create Group" form.
In addition, it
24 matches
Mail list logo
