seems nova don't have function 'interface_list' ?
** No longer affects: nova
--
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/1471041
Title:
interface_list() function
Public bug reported:
If we use http proxy ip like a glance endpoint and add metadata for image in
bug: https://bugs.launchpad.net/horizon/+bug/1449260
then http response have wrong HTTP type.
reproduced on branch: stable/juno
Steps to reproduce:
Precondition steps:
httpproxy glance endpoint:
Public bug reported:
nova service-delete 11-3
ERROR (ClientException): The server has either erred or is incapable of
performing the requested operation. (HTTP 500) (Request-ID:
req-931741d5-4013-477e-93cc-c0c90b302ffe)
the logs shows we need to handle DBError Exception
2015-07-03
Public bug reported:
When starting/restarting/rebuilding instances, it may happen that a
volume detach request comes right in the middle of attaching a volume in
the driver. In this case the hypervisor (e.g. libvirt) will throw
DiskNotFound exception in driver.detach_volume() call, but still the
Public bug reported:
When I create a new user and enter the password but not the confirmation
password, and then click Create User. I only get one error message,
stating that This is field is required for Confirm Password but not
for Password(with cleared field).
I would prefer that either:
-
Public bug reported:
Due to the fact that rebuild detaches block devices when instance is
still powered on, data written to attached volumes can possibly be lost,
if it hasn't been fsynced yet.
We can prevent this by allowing instance to shut down gracefully before
detaching block devices during
Public bug reported:
The check job gate-glance-python27 failed on my patch
https://review.openstack.org/#/c/197916/
I added debug traces and it looks like the OpenStack infra uses a ext4
partition mounted with noatime, whereas the xattr image cache driver
explicitly requires atime.
Debug trace:
Public bug reported:
When keystone is configured to use fernet tokens and also configured to
be a SP for an external IDP then the token data received by nova and
other services appear to not contain the right information, resulting in
errors from nova-api-os-compute such as:
Returning 400 to
Public bug reported:
1.
ii nova-common 1:2014.2-fuel6.0~mira19
OpenStack Compute - common files
ii nova-compute 1:2014.2-fuel6.0~mira19
OpenStack Compute - compute node base
ii nova-compute-kvm
Public bug reported:
The create_subnet flow was recently re-factored as part of the ongoing
neutron-ipam work, and has broken the process for requesting a specific
subnet. Before the refactor, a user could request a subnet from the
implicit (None) pool by supplying a cidr and not a subnetpool_id
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1419175
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1415669
Public bug reported:
Neutron third-party external repos (and also the *aaS repos) have their
own independent alembic branches. Then autogenerate command of neutron-
db-manage shall support these external branches.
Documentation shall be provided on how to use it.
** Affects: neutron
Public bug reported:
Some random IPV6 seems to be selected for the DHCP port when the port is
created.
It's not really a bug for say but this makes the behaviour less
predictable ...
For instance, in devstack, by default, it will create a random 40 bit
IPV6 global ID (to comply with RFC 4193)
Hi George,
Since this bug is caused by invalid configuration, I'm closing this bug.
According to your comment #4, I think if few networks was attached in
this way, and one network is removed, address is written in wrong
network filed is a defect, please open a new bug against this defect.
**
** Tags added: api novaclient
** Also affects: python-novaclient
Importance: Undecided
Status: New
--
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/1470219
** Also affects: python-novaclient
Importance: Undecided
Status: New
** Tags added: novaclient
--
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/1471041
Title:
Public bug reported:
In oslo.config StrOpt provide parameter choices, that means the
option's value must be in the choices, otherewise an exception will be
raised. The current exception is NoSuchOptError[1], a more meaningful
exception should be raised [2].
In other word, if an exception
** Changed in: nova
Status: In Progress = Invalid
** Changed in: nova
Assignee: wangxiyuan (wangxiyuan) = (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
Reproducing method as following:
1、create one instance
[root@opencosf0ccfb2525a94ffa814d647f08e4d6a4 ~(keystone_admin)]# nova list
+--+-+++-+---+
| ID
Public bug reported:
Our functional tests (test_scrubber.py) contains a lot of extra code
which can be replaced.
** Affects: glance
Importance: Undecided
Assignee: Alexey Galkin (agalkin)
Status: In Progress
** Tags: glance tests
** Changed in: glance
Assignee:
Public bug reported:
Consider a flavour with 4 vcpus, and image property hw:cpu_threads==2.
Now the NUMA topology may prefer a thread count of 4, but best of the
thread preference set, the guest will end up with 2 sockets, 1 core and
2 threads.
Now consider a flavour with 4 vcpus, and image
Public bug reported:
The followings are needed to confirm the resource update history.
*Latest value
*Updated value(point)
*Default value
Latest value is got by GET API.
**GET API**
$ curl -X GET -H X-Auth-Token: $TOKEN
23 matches
Mail list logo
