Public bug reported:
### Scenario: ###
1) Create a new QoS policy with:
openstack network qos policy create bandwidth-control
2) Create a new rule of “minimum bandwith” type and associate this rule to
previously created policy with:
openstasck network qos rule create --type minimum-bandwidth
Public bug reported:
### Documentation enhancement bug ###
There is a sentence that says "It is also possible to combine several rules in
one policy:" and this is correct, but I think that we need to accent (inside
this sentence or by adding note bellow it) that rules' type should be
** Also affects: openstack-ansible
Importance: Undecided
Status: New
** Changed in: openstack-ansible
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Reviewed: https://review.openstack.org/577726
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=1ea3d5ec743838ddb754739a9919a2ecf4c54f9f
Submitter: Zuul
Branch:master
commit 1ea3d5ec743838ddb754739a9919a2ecf4c54f9f
Author: deepak.mourya
Date: Mon Jun 25 10:05:38 2018
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova
Importance: Undecided => Medium
** Changed in: nova/queens
Status: New => In Progress
** Changed in: nova/queens
Importance: Undecided => Medium
** Changed in: nova/queens
Assignee:
Reviewed: https://review.openstack.org/533804
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=d16d0d553b20fd45a83cf7c68bc477b97aece9a1
Submitter: Zuul
Branch:master
commit d16d0d553b20fd45a83cf7c68bc477b97aece9a1
Author: Artom Lifshitz
Date: Mon Jan 15 15:36:40 2018
*** This bug is a duplicate of bug 1645175 ***
https://bugs.launchpad.net/bugs/1645175
Reviewed: https://review.openstack.org/533805
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=abd01a757b8a83d714a6ab8b5085e7cc1b4a2c5c
Submitter: Zuul
Branch:master
commit
Public bug reported:
During policy testing using Patrole with the new multi-policy support, it
became apparent
that the Neutron policy enforcement code is using the new value of an attribute
(on a PUT
request) to validate access to that same attribute. Here are two scenarios that
expose this
tested against devstack. fix [0]
https://review.openstack.org/#/c/576163/ resolved the project creation.
Now can create project.
** Changed in: horizon
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
The Nova Compute services (os-services) API is not granular enough in
the sense that multiple APIs check the same policy action for list,
update, and delete. This does not allow operators with strict security
requirements to have different roles that can perform certain APIs
Public bug reported:
When looking up a user in a domain, one can generally do this:
openstack user show --domain testdomain testuser
Unfortunately, if testuser is a federated user, the above command will
fail. For example:
$ openstack domain list -c ID -c Name
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: New => Confirmed
** Changed in: nova/queens
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
The authentication APIs of keystone (GET|HEAD|POST|DELETE
/v3/auth/tokens) leverage the token provider API to deal with token
operations. This has traditionally been one of the most complicated
areas of keystone for multiple reasons.
First, tokens are represented in
On discussing with Dan Smith, the related denial of service condition
described in this report has been a known risk since the introduction of
the feature and generally falls below the threshold for broad
publication in an advisory. The related fixes merged back as far as
stable/pike will mitigate
Reviewed: https://review.openstack.org/575562
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=5a7c12f245fd665de5a0364059e4ad918def3e12
Submitter: Zuul
Branch:master
commit 5a7c12f245fd665de5a0364059e4ad918def3e12
Author: Swaminathan Vasudevan
Date: Thu Jun 14
Public bug reported:
There are a few places in the resource_provider.py placement API handler
module that need to be updated to return custom error codes.
Custom error codes were added in the last few months or so. They allow
the caller to determine what exact issue occurred on the server to,
At least the test test_evacuate_with_no_compute that showed this stack
trace does not produce the same trace any more. So I think the evacuate
part also OK on master.
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Gonna kills this one. We seem to have reached the consensus that
overhead that an operator may manage however they like, it is not
something we will generically manage.
In the future it might make sense for the virt drivers to handle
overhead via resereved when they are working with
Reviewed: https://review.openstack.org/578002
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=b2b42296965d8d339f06e62bd76ff81c0b746777
Submitter: Zuul
Branch:master
commit b2b42296965d8d339f06e62bd76ff81c0b746777
Author: Swaminathan Vasudevan
Date: Mon Jun 25
** Changed in: nova
Status: Confirmed => Won't Fix
--
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/1708958
Title:
disabling a compute service does not disable the
** Changed in: charm-openstack-dashboard
Status: Fix Committed => Fix Released
--
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/1777358
Title:
Charm does not
Hi, Corey!
Thank you for respond. I'd replaced local repositories with official
cloud-archive you provided, but the result is still the same...
Log is attached.
** Attachment added: "apt_install_nova-compute.log"
Public bug reported:
I've booted two instances from the same backing image (http://cloud-
images.ubuntu.com/trusty/current/trusty-server-cloudimg-
amd64-disk1.img), one using locally attached storage for the boot
volume, one using a Cinder volume. The instance booted from cinder
volume shows a
Public bug reported:
Problem description:
When doing associcate-floating-ip to an instance, we will call the following
method
https://github.com/openstack/nova/blob/master/nova/network/neutronv2/api.py#L1869
def _get_port_id_by_fixed_address(self, client,
Reviewed: https://review.openstack.org/576418
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=5ddb2a4762eac52290cd0491881ec6ca15bb9217
Submitter: Zuul
Branch:master
commit 5ddb2a4762eac52290cd0491881ec6ca15bb9217
Author: LIU Yulong
Date: Fri Jun 15 16:02:36 2018
Yea, there are lot of other place where API status code are not
consistent and as per guidelines. As jichenjc mentioned this will be API
change and need microversion bump to maintain the backward
compatibility.
And as per Nova process, every API change needs spec, so please write
spec for this
26 matches
Mail list logo
