Public bug reported:
to reproduce the bug:
1) boot a windows machine and specify a public key where the private key is
protected with a passphrase.
2) try to retrieve the machine password.
3) An error will accur: could not decrypt password
** Affects: horizon
Importance: Undecided
** Changed in: python-openstackclient
Status: Fix Released => Triaged
--
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/1460492
Title:
List credentials by type
Reviewed: https://review.openstack.org/355597
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=8ddf174a3081b0a60964fa196c46c97e8a475fff
Submitter: Jenkins
Branch:master
commit 8ddf174a3081b0a60964fa196c46c97e8a475fff
Author: Maciej Szankin
Date:
Reviewed: https://review.openstack.org/352866
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=87530b6e674750ab0d55b70cce4d96bf26d1f49a
Submitter: Jenkins
Branch:master
commit 87530b6e674750ab0d55b70cce4d96bf26d1f49a
Author: Markus Zoeller
Date:
solution considerations
option one has the advantage of confining the change change to os-vif.
option two is the correct approach long term as it dose not require any config
change on upgrade.
option three is a compromise as while we do not need to make any change on
upgrade we cannot hanel
the
Public bug reported:
This is an all new install on CentOS 7.
The error message is:
"The current Horizon settings indicate no valid image creation methods
are available. Providing an image location and/or uploading from the
local file system must be allowed to support image creation."
This link
** Changed in: keystone/mitaka
Status: Fix Committed => Fix Released
--
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/1592169
Title:
cached tokens break
I think this could be marked as Fix Released for openstackclient. The
implementation [0] landed several months ago but it was never tagged
against this bug.
[0]
https://github.com/openstack/python-openstackclient/commit/15d3717e733aec9e8b6526a1abffd62f2da1e32b
** Changed in:
Public bug reported:
Logstash started seeing this failure October 3rd. Not seeing any
occurrences before that. It's very intermittent:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22RuntimeError%3A%20Metadata%20proxy%20didn't%20spawn%5C%22
** Affects: neutron
Reviewed: https://review.openstack.org/378716
Committed:
https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=6584de1523cc87d04a75c29b6c0841192ac4d4ac
Submitter: Jenkins
Branch:master
commit 6584de1523cc87d04a75c29b6c0841192ac4d4ac
Author: Darla Ahlert
Date:
Reviewed: https://review.openstack.org/384469
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=1d13a052468ef1b66d1c75f98f52cc356ba81365
Submitter: Jenkins
Branch:master
commit 1d13a052468ef1b66d1c75f98f52cc356ba81365
Author: Paul Karikh
Date:
Confirmed locally that reverting the above patch fixes this. I'm not
sure why it's only affecting Mitaka, so going to add keystone to the bug
and see if they have any thoughts.
** Also affects: keystone
Importance: Undecided
Status: New
--
You received this bug notification because
Public bug reported:
Hi,
we have our swift proxy configured with account_autocreate = false
(which is the default), i.e. a new project does not automatically have a
swift account, but it needs to be created via PUT on the swift auth url.
In combination with multi-tenant swift backend use in
Since nova-network is gonna be deprecated in near future, I don't feel
the real need of making this change. I see most of the commands in
OpenStack client seems to be case sensitive. Hence I am changing the bug
status to 'won't fix'. If this needs to be fixed, please feel free to
reopen the bug.
I tried to reproduce the bugs using following commands
1) neutron port-create
2) nova boot --image cirros-0.3.4-x86_64-uec --flavor m1.small --nic
port-id= test1
3) nova interface-list
4) neutron port-delete
5) nova interface-list
I wasn't able to reproduce the scenario described above.
Reviewed: https://review.openstack.org/334844
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=4eb89c206e68a7172ebad897ad24769036c7bdd6
Submitter: Jenkins
Branch:master
commit 4eb89c206e68a7172ebad897ad24769036c7bdd6
Author: Takashi NATSUME
** Changed in: neutron
Status: New => Fix Released
** Changed in: networking-bagpipe
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
* This is with:
- SUSE SLE 12 SP2
- Nova Mitaka (version 13.1.2.dev68 from the stable-mitaka from
tarballs.openstack.org)
- neutron+linuxbridge
- nova libvirt+KVM
When running the tempest scenario tests (ostestr -r '^tempest.scenario') I get:
Traceback (most recent
Reviewed: https://review.openstack.org/352317
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=36a0ba9c8141b445f2c6bfc093fde4cc98d229b2
Submitter: Jenkins
Branch:master
commit 36a0ba9c8141b445f2c6bfc093fde4cc98d229b2
Author: jichenjc
Date: Sat Jul
I am also seeing this issue on Ubuntu Xenial (16.04.1) using the
stable/Newton branch.
** Also affects: glance
Importance: Undecided
Status: New
** Changed in: openstack-manuals
Status: Opinion => Confirmed
--
You received this bug notification because you are a member of
Reviewed: https://review.openstack.org/343799
Committed:
https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=abeb5c4de0f50bba23cbc9750a095b9423dd33d5
Submitter: Jenkins
Branch:master
commit abeb5c4de0f50bba23cbc9750a095b9423dd33d5
Author: Pablo Iranzo Gómez
Public bug reported:
Currently, the functional tests can't be run with python 3.x and fail
with a trace like this:
Failed to import test module:
nova.tests.functional.api_sample_tests.test_volumes
Traceback (most recent call last):
File
Reviewed: https://review.openstack.org/385134
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=abe6157e5a1cdfba74b1d775630424eff08cbb34
Submitter: Jenkins
Branch:master
commit abe6157e5a1cdfba74b1d775630424eff08cbb34
Author: Steve Martinelli
After the latest finding, I think it's evident that there's nothing we
can do to fix this from the Neutron side.
** No longer affects: neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
Using pdb breakpoints with testr fails with BdbQuit exception rather
than stopping at the breakpoint.
The oslotest package also distributes a shell file that may be used to assist
in debugging python code. The shell file uses testtools, and supports debugging
with pdb.
Based on your config, your devstack is using Neutron for networking.
Nova-network commands won't work.
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
You have been subscribed to a public bug:
After spending a few hours trying to work with the API documentation
(http://developer.openstack.org/api-ref-compute-v2.1.html#createServer),
I discovered the "networks" and "security_groups" parameters are not
accurate enough. They are both described as
** Changed in: openstack-api-site
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/1630134
Title:
Networking API v2.0 (CURRENT): Update Network Request
Public bug reported:
We need a way for mechanism driver to pass user-defined
(driver-specific) data or changed states from precommit to postcommit.
The simplest way is to add a dict as object property in the context.
** Affects: neutron
Importance: Undecided
Assignee: Li Ma
** Project changed: nova => ironic-inspector
** Project changed: ironic-inspector => ironic
--
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/1632539
Title:
Multiple nova
[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard
You have been subscribed to a public bug:
I am unable to find any official documentation on project name
restrictions. The only two that can be found are 1. It must be uniqe
within the domain and 2. No more than 64 characters.
** Project changed: openstack-api-site => keystone
--
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/1631517
Title:
No formal statement of project name restrictions
** Project changed: openstack-api-site => 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/1616134
Title:
api-ref-compute-v2.1 - inaccurate description for
You have been subscribed to a public bug:
When Ironic and nova work in one region。we should deploy multiple nova-
scheduler process,some for Ironic node scheduling and others for virtual
machines scheduling。 Then we call rest API to boot an ironic node, nova-
conductor polls the message to
Public bug reported:
2016-10-12 10:04:38.587 25667 ERROR neutron.agent.l3.agent
[req-5d499217-05b6-4a56-a3b7-5681adb53d6c - d2b95803757641b6bc55f6309c12c6e9 -
- -] Failed to process compatible router 'da82aeb4-07a4-45ca-ae7a-570aec69df29'
2016-10-12 10:04:38.587 25667 ERROR
** Project changed: tempest => 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/1632539
Title:
Multiple nova schedulers for Ironic and nova conflict when they work
Bug reporter was not able to repro behavior in the nova console; this
only happens when using Horizon. marking as invalid for Nova and adding
Horizon to the bug report.
** Also affects: horizon
Importance: Undecided
Status: New
** Changed in: nova
Status: Incomplete => Invalid
Public bug reported:
We tried to add some negative test case to Tempest for the other bug.
However, Nova still returns HTTP500 error if attaching the already attached
volume like:
http://logs.openstack.org/83/382083/12/check/gate-tempest-dsvm-neutron-
full-ubuntu-
** Also affects: nova/mitaka
Importance: Undecided
Status: New
** Changed in: nova/mitaka
Assignee: (unassigned) => Dan Smith (danms)
** Changed in: nova/mitaka
Status: New => In Progress
** Changed in: nova/mitaka
Importance: Undecided => High
--
You received this
Public bug reported:
Description
===
There are 15 instances. I excute the command: nova --debug list --all-tenants,
But it took more than 40 seconds. I read the nova api code, it sends a Get
request
and read the instance_faults table for detail information. The instance_faults
table has
41 matches
Mail list logo