Public bug reported:
There's no trunk driver supporting VIF_TYPE_HW_VEB ports [1,2,3], yet
Neutron allows trunks to be created for them. I think it should rejected
on validation.
[1]
Let me put this into invalid, I realized it was an amphora LB being hit
with constant updates and now I don't see this issue on my env.
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
I left my DevStack env for a several days to see the following:
stack@mdulko-devstack-ovnvm-0:~$ free -m
totalusedfree shared buff/cache available
Mem: 16039 15407 132 375 499 22
Swap:
Public bug reported:
Kuryr-Kubernetes tests running with ovn-octavia-provider started to fail
with "Provider 'ovn' does not support a requested option: OVN provider
does not support allowed_cidrs option" showing up in the o-api logs.
We've tracked that to check [1] getting introduced. Apparently
Public bug reported:
In kuryr-kubernetes gate runing NetworkPolicy tests from K8s itself we
started to see Neutron returns 500 on SG delete requests. This is found
in q-svc logs:
Aug 20 19:43:56.358683 ubuntu-bionic-rax-iad-0019371817 neutron-server[10089]:
ERROR neutron.api.v2.resource [None
Seems like this works on master.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1865156
Title:
If-Match header ignored for routers
Public bug reported:
According to release note [1], the If-Match conditional updates should
be supported for all resources that have revision_number. Apparently
that doesn't work for routers:
mdulko:openstacksdk/ (neutron-if-match*) $ curl -g -i -X PUT -H
"Content-Type: application/json" -H
Public bug reported:
We see this in kuryr-kubernetes and test_namespace_sg_isolation test.
More info can be found in bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1688323
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because
Public bug reported:
We're occasionally hitting a bug preventing Kuryr-Kubernetes from
attaching ports to a trunk. The result of the operation on the API is
200, but ports never gets into ACTIVE and switches device_owner to
trunk:subport. In our case Kuryr is creating those ports in bulks of 3,
Public bug reported:
If you pass binding_host_id to bulk port creation request, the property
is not saved into the DB and this results in port being unbound. This is
problematic for Kuryr where we precreate a number of ports pre-attached
to Neutron hosts.
I believe this was introduced in
Public bug reported:
We have a use case to tag all Neutron resources created by Kuryr-
Kubernetes, as Kubernetes clusters that Kuryr serves may come and go and
it should be possible to easily identify all the leftovers for garbage
collection purpose. As adding a tag is a distinct API call that
Public bug reported:
Even though "tags" field is listed in api-ref as allowed POST argument
for ports, when trying to use it we get 400: "Attribute 'tags' not
allowed in POST". I assume this is happening for other resources as well
and it's a simple documentation mistake.
** Affects: neutron
Public bug reported:
Due to code [1] Keystone produces a confusing message when:
* We're using python-openstackclient
* We're creating a trust with a role name that exists in more that one domain.
"role %s is not defined" suggests that there isn't a role like that.
What actually happens,
] section - it's named [cache].
** Affects: keystone
Importance: Undecided
Assignee: Michal Dulko (michal-dulko-f)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https
Moving this to Nova, as it looks [1] like it's caused by failures in
Nova's services.
[1] http://logs.openstack.org/49/414549/4/check/gate-tempest-dsvm-
neutron-full-ubuntu-
xenial/58aecae/logs/screen-n-cpu.txt.gz?level=TRACE#_2017-02-07_10_06_17_855
** Project changed: cinder => nova-project
Cinder does have a hacking check ensuring that [1].
[1]
https://github.com/openstack/cinder/blob/c96be71fd66aa9c2a977e6c0288c69a3d42c3b6a/cinder/hacking/checks.py#L225-L287
** No longer affects: cinder
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
I'm not 100% sure that this is the intent of this bug, but I do believe
that Cinder isn't dying when receiving SIGHUP signal [1], so I'm marking
it as invalid.
[1] https://review.openstack.org/#/c/279039/
** Changed in: cinder
Status: New => Invalid
--
You received this bug notification
** Changed in: cinder
Status: Fix Released => Confirmed
** Changed in: cinder
Milestone: 7.0.0 => None
** Changed in: cinder
Assignee: Skyler Berg (sberg-l) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
Due to bug 1386232 Nova forked get_volume_api_from_url method from
python-cinderclient. As the bug is fixed now we should switch back to
using cinderclient's version.
** Affects: nova
Importance: Undecided
Assignee: Michal Dulko (michal-dulko-f)
Status
** Also affects: glance
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1323660
Title:
Glance image properties not copied to cinder volume with
** No longer affects: glance
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1323660
Title:
Glance image properties not copied to cinder volume with glance V2 API
Status in Cinder:
** Also affects: glance
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1323660
Title:
Glance image properties not copied to cinder volume with
Cinder is also using oslo.db.
** Changed in: cinder
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1340793
Title:
DB2 deadlock error not detected
I guess this is fixed now:
nova help rescue
usage: nova rescue server
Reboots a server into rescue mode, which starts the machine from the initial
image, attaching the current boot disk as secondary.
Positional arguments:
server Name or ID of server.
** Changed in: python-novaclient
Already fixed by this commit:
https://review.openstack.org/#/c/65545/
Can we close it?
** Changed in: glance
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
Public bug reported:
There are completely no logs in v2/image_tags and v2/image_members
controllers in REST API.
** Affects: glance
Importance: Undecided
Status: New
** Description changed:
- There's completely no logs in v2/image_tags and v2/image_members
+ There are completely
Public bug reported:
This problem concerns custom scheduler filters and weighers which can be added
by user in order to specify his own scheduling algorithm.
During scheduling of a single VM, it's UUID can be retrieved from
filter_properties:
request_spec: {
block_device_mapping: [ {
27 matches
Mail list logo
