[Yahoo-eng-team] [Bug 1267362] Re: The meaning of "Disk GB Hours" is not really clear
As per comment #8, this isn't something that should be fixed in documentation - removing the reference to manuals. ** No longer affects: openstack-manuals -- 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/1267362 Title: The meaning of "Disk GB Hours" is not really clear Status in OpenStack Dashboard (Horizon): Fix Committed Bug description: when visiting the admin overview page, http://localhost:8000/admin/ the usage summary lists Disk GB Hours The same term "This Period's GB-Hours: 0.00" can be found e.g here: https://github.com/openstack/horizon/blob/master/horizon/templates/horizon/common/_usage_summary.html To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1267362/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1306835] Re: V3 list users filter by email address throws exception
** Changed in: openstack-manuals Status: In Progress => Fix Released ** Changed in: openstack-manuals Milestone: None => juno ** Changed in: openstack-manuals Importance: Undecided => Medium -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1306835 Title: V3 list users filter by email address throws exception Status in OpenStack Identity (Keystone): Fix Released Status in Keystone icehouse series: Fix Released Status in OpenStack Manuals: Fix Released Bug description: V3 list_user filter by email throws excpetion. There is no such attribute email. keystone.common.wsgi): 2014-04-11 23:09:00,422 ERROR type object 'User' has no attribute 'email' Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/keystone/common/wsgi.py", line 206, in __call__ result = method(context, **params) File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line 183, in wrapper return f(self, context, filters, **kwargs) File "/usr/lib/python2.7/dist-packages/keystone/identity/controllers.py", line 284, in list_users hints=hints) File "/usr/lib/python2.7/dist-packages/keystone/common/manager.py", line 52, in wrapper return f(self, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/keystone/identity/core.py", line 189, in wrapper return f(self, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/keystone/identity/core.py", line 328, in list_users ref_list = driver.list_users(hints or driver_hints.Hints()) File "/usr/lib/python2.7/dist-packages/keystone/common/sql/core.py", line 227, in wrapper return f(self, hints, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/keystone/identity/backends/sql.py", line 132, in list_users user_refs = sql.filter_limit_query(User, query, hints) File "/usr/lib/python2.7/dist-packages/keystone/common/sql/core.py", line 374, in filter_limit_query query = _filter(model, query, hints) File "/usr/lib/python2.7/dist-packages/keystone/common/sql/core.py", line 326, in _filter filter_dict = exact_filter(model, filter_, filter_dict, hints) File "/usr/lib/python2.7/dist-packages/keystone/common/sql/core.py", line 312, in exact_filter if isinstance(getattr(model, key).property.columns[0].type, AttributeError: type object 'User' has no attribute 'email' To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1306835/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1301519] Re: nova.conf.sample missing from the 2014.1.rc1 tarball
This is being brought up on the mailing list, returning to 'new'. ** Changed in: nova Status: Won't Fix => 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/1301519 Title: nova.conf.sample missing from the 2014.1.rc1 tarball Status in OpenStack Compute (Nova): New Bug description: This patch [1] removed the nova.conf.sample because it's not gated but now we are left without the sample config file in the tarball. We could generate the nova.conf.sample in setup.py (based on this comment [2]) and include it in the tarball for rc2. [1] https://review.openstack.org/#/c/81588/ [2] https://bugs.launchpad.net/nova/+bug/1294774/comments/4 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1301519/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1370934] Re: Add details on dhcp_agents_per_network option for DHCP agent HA
** No longer affects: openstack-manuals -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1370934 Title: Add details on dhcp_agents_per_network option for DHCP agent HA Status in OpenStack Neutron (virtual network service): Confirmed Bug description: The current documentation does not specify any information about the "dhcp_agents_per_network" configuration option in /etc/neutron/neutron.conf. Using this option, it is possible to have the scheduler automatically assign multiple DHCP agents to a tenant network, which provides high availability. If that option is not set, you have to manually assign multiple DHCP agents to each network, which does not scale in terms of management. Would it be possible to document this option here? --- Built: 2014-04-17T10:27:55 00:00 git SHA: 1842612f99f1fe87149db9a3cb0bd43e7892e22b URL: http://docs.openstack.org/trunk/config-reference/content/multi_agent_demo_configuration.html source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/config-reference/networking/section_networking-multi-dhcp-agents.xml xml:id: multi_agent_demo_configuration To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1370934/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1329884] Re: Conflicting documention on V3 Identity roles route
** Project changed: openstack-manuals => openstack-api-site
** Also affects: keystone
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1329884
Title:
Conflicting documention on V3 Identity roles route
Status in OpenStack Identity (Keystone):
New
Status in OpenStack API documentation site:
New
Bug description:
http://developer.openstack.org/api-ref-identity-v3.html documents a
/v3/users/{user_id}/roles route but https://github.com/openstack
/identity-api/blob/master/v3/src/markdown/identity-api-v3.md has no
mention of such a route.
When I've tried to access the /v3/users/{user_id}/roles route using
V3 Identity I get a 404, although I can access domain and project role
routes ok. I'm not certain if I'm doing something wrong or if this
route doesn't actually exist.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1329884/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1329884] Re: Conflicting documention on V3 Identity roles route
** No longer affects: keystone
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1329884
Title:
Conflicting documention on V3 Identity roles route
Status in OpenStack API documentation site:
Confirmed
Bug description:
http://developer.openstack.org/api-ref-identity-v3.html documents a
/v3/users/{user_id}/roles route but https://github.com/openstack
/identity-api/blob/master/v3/src/markdown/identity-api-v3.md has no
mention of such a route.
When I've tried to access the /v3/users/{user_id}/roles route using
V3 Identity I get a 404, although I can access domain and project role
routes ok. I'm not certain if I'm doing something wrong or if this
route doesn't actually exist.
To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-api-site/+bug/1329884/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1274005] Re: .tx/config in havana needs to catch up with Transifex resource renaming
** Changed in: openstack-i18n 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/1274005 Title: .tx/config in havana needs to catch up with Transifex resource renaming Status in OpenStack Dashboard (Horizon): Invalid Status in OpenStack Dashboard (Horizon) havana series: Fix Released Status in OpenStack I18n & L10n: Fix Released Bug description: I18N team decided to maintain Horizon translations for Havana stable branch and Transifex resource names is renamed to *-havana. Horizon repository has .tx/config and .tx/config in stable/havana needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1274005/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1266620] Re: bad english in string: "Disabled reason contains invalid characters or is too long"
** Changed in: openstack-i18n Status: In Progress => Fix Released -- 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/1266620 Title: bad english in string: "Disabled reason contains invalid characters or is too long" Status in OpenStack Compute (Nova): Fix Released Status in OpenStack I18n & L10n: Fix Released Bug description: This string: "Disabled reason contains invalid characters or is too long" found in nova/api/openstack/compute/contrib/services.py:177, nova/api/openstack/compute/plugins/v3/services.py:159 should be fixed. From the spanish translation team: Se recomienda que esta cadena sea reestructurada en su versión original, particularmente "Disabled reason". Essentially, the string isn't the best English and should be re-written so it can be translated properly - particularly the use of "Disabled reason". To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1266620/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1224329] Re: I18n: strings in some table columns (e.g., Status, Task, Powerstate) are not translated
** Changed in: openstack-i18n 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/1224329 Title: I18n: strings in some table columns (e.g., Status, Task, Powerstate) are not translated Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack I18n & L10n: Fix Released Bug description: There are many tables in Horizon. I noticed some columns are untranslated. For example, in the table of instances, strings in the column of "Status", "Task", and "Power State" are not translated. In the table of volumes, strings in the column of "Status" are not translated. In the table of images, strings in the column of "Type", "Status", "Public", and "Protected" are not translated. Some of these strings are getting from database as code, for example "Type" and "Status". Some of these strings are "Yes" and "No". I think they should also be enabled i18n too. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1224329/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1292589] Re: Can't set any default quota values in Horizon
this was updated in the manuals by the autotools ** Changed in: openstack-manuals Status: Triaged => Fix Released ** Changed in: openstack-manuals Assignee: (unassigned) => Tom Fifield (fifieldt) -- 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/1292589 Title: Can't set any default quota values in Horizon Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Manuals: Fix Released Bug description: To re-create, log in as admin. Navigate to Admin/System Panel/Defaults. Click Update Defaults. Change any quota to a reasonable value (or don't change any at all) and click Update Defaults. There will be both a success and error message (there is a separate bug about that). But no changes from the UI will be applied. Inside the log there is the following trace info: [Fri Mar 14 14:20:30 2014] [error] NotFound: Not found (HTTP 404) [Fri Mar 14 14:27:04 2014] [error] Not Found: Not found (HTTP 404) [Fri Mar 14 14:27:04 2014] [error] Traceback (most recent call last): [Fri Mar 14 14:27:04 2014] [error] File "/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/admin/defaults/workflows.py", line 93, in handle [Fri Mar 14 14:27:04 2014] [error] nova.default_quota_update(request, **nova_data) [Fri Mar 14 14:27:04 2014] [error] File "/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/nova.py", line 626, in default_quota_update [Fri Mar 14 14:27:04 2014] [error] novaclient(request).quota_classes.update(DEFAULT_QUOTA_NAME, **kwargs) [Fri Mar 14 14:27:04 2014] [error] File "/usr/lib/python2.6/site-packages/novaclient/v1_1/quota_classes.py", line 44, in update [Fri Mar 14 14:27:04 2014] [error] 'quota_class_set') [Fri Mar 14 14:27:04 2014] [error] File "/usr/lib/python2.6/site-packages/novaclient/base.py", line 165, in _update [Fri Mar 14 14:27:04 2014] [error] _resp, body = self.api.client.put(url, body=body) [Fri Mar 14 14:27:04 2014] [error] File "/usr/lib/python2.6/site-packages/novaclient/client.py", line 289, in put [Fri Mar 14 14:27:04 2014] [error] return self._cs_request(url, 'PUT', **kwargs) [Fri Mar 14 14:27:04 2014] [error] File "/usr/lib/python2.6/site-packages/novaclient/client.py", line 260, in _cs_request [Fri Mar 14 14:27:04 2014] [error] **kwargs) [Fri Mar 14 14:27:04 2014] [error] File "/usr/lib/python2.6/site-packages/novaclient/client.py", line 242, in _time_request [Fri Mar 14 14:27:04 2014] [error] resp, body = self.request(url, method, **kwargs) [Fri Mar 14 14:27:04 2014] [error] File "/usr/lib/python2.6/site-packages/novaclient/client.py", line 236, in request [Fri Mar 14 14:27:04 2014] [error] raise exceptions.from_response(resp, body, url, method) [Fri Mar 14 14:27:04 2014] [error] NotFound: Not found (HTTP 404) I'm concerned that this has been caused by a change in nova that we haven't reflected in horizon http://lists.openstack.org/pipermail/openstack-dev/2014-February/027560.html To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1292589/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1208286] Re: V3 Identity API: expired tokens are not documented as invalid
** Changed in: openstack-api-site Status: Fix Committed => Fix Released ** Changed in: openstack-manuals Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1208286 Title: V3 Identity API: expired tokens are not documented as invalid Status in OpenStack Identity (Keystone): Confirmed Status in OpenStack API documentation site: Fix Released Status in OpenStack Manuals: Fix Released Bug description: The response codes from GET /auth/tokens are not documented, but they are non-obvious (at least to me). The 'happy case' is easy. But what happens if the auth token has expired? What happens if the subject token has expired? How can I differentiate? If an expired subject token is returned as a 200 response, how can I tell it is expired (assuming I don't have an accurate source of time, e.g. in the browser)? For how long are expired tokens stored? To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1208286/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1106423] Re: grizzly: ability to specify the libvirt cache mode for disk devices
now mentioned in config-reference
** Changed in: openstack-manuals
Status: Confirmed => Fix Released
** Changed in: openstack-manuals
Assignee: (unassigned) => Tom Fifield (fifieldt)
--
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/1106423
Title:
grizzly: ability to specify the libvirt cache mode for disk devices
Status in OpenStack Compute (Nova):
Fix Committed
Status in OpenStack Manuals:
Fix Released
Bug description:
If https://review.openstack.org/#/c/18042/ is merged, a new
configuration option/feature will be added to nova. The manuals should
be updated to reflect this - configuration references and sample files
In past versions of Nova it was possible to explicitly configure
the cache mode of disks via the libvirt XML template. The curent approach
makes this a derived setting of either “none” or “writethrough” based
on the support of O_DIRECT. Whilst this provides a good set of default
settings it removes the ability of the cloud provider to use other
modes such as “writeback” and “unsafe” which are valuable in certain
configurations.
This change allows the cache mode to be specified on a per-disk type
basis. Leaving the specify_cachemode option set to False retains the
current behaviour.
189 cfg.ListOpt('disk_cachemodes',
190 default=[],
191help='Specific cachemodes to use for different
disk types '
192 'e.g: ["file=directsync","block=none"]'),
189 ] 193 ]
317 self.valid_cachemodes = ["default",
318 "none",
319 "writethrough",
320 "writeback",
321 "directsync",
322 "writethrough",
323 "unsafe",
324 ]
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1106423/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1161988] Re: Flavor naming shouldn't include "m1"
** Changed in: nova Status: In Progress => Won't Fix ** Changed in: tempest Status: In Progress => Won't Fix ** Changed in: python-novaclient Status: In Progress => Won't Fix ** Changed in: devstack Status: In Progress => Confirmed ** Changed in: horizon Status: In Progress => Confirmed ** Changed in: python-heatclient Status: In Progress => Confirmed -- 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/1161988 Title: Flavor naming shouldn't include "m1" Status in devstack - openstack dev environments: Confirmed Status in OpenStack Dashboard (Horizon): Confirmed Status in OpenStack Compute (Nova): Won't Fix Status in Python client library for heat: Confirmed Status in Python client library for Nova: Won't Fix Status in Tempest: Won't Fix Bug description: Flavor naming shouldn't include "m1" ENV: devstack trunk / nova 814e109845b3b2546f60e3f537dcfe32893906a3 (grizzly) The default flavors are now: m1.nano m1.micro m1.tiny m1.small m1.medium m1.large m1.xlarge We are propagating AWS "m1" designation. This is not useful information to the OpenStack administrator or user, and it's actually possible misinformation as the "m1" on AWS suggests a specific generation of hardware. POSSIBLE SOLUTION: Drop the "m1": nano micro tiny small medium large xlarge To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1161988/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1253482] Re: Keystone default port in linux local ephemeral port range. Devstack should shift range.
In openstack-manuals, this will now be dealt holistically across all services by this bug : https://bugs.launchpad.net/openstack- manuals/+bug/1261617 " Provide information and instructions on default ports and firewall rules " ** No longer affects: openstack-manuals -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1253482 Title: Keystone default port in linux local ephemeral port range. Devstack should shift range. Status in devstack - openstack dev environments: In Progress Status in OpenStack Identity (Keystone): In Progress Bug description: The linux ip port local range is 32768 to 61000 as reported by sysctl: $ sysctl -a | grep ip_local_port_range net.ipv4.ip_local_port_range = 32768 61000 Keystone's default port as assigned by IANA is 35357. It is therefore possible that keystone will fail to start because some application has a socket open on port 35357. We believe this is the case logged at http://logs.openstack.org/09/57509/2/gate/gate-tempest-devstack-vm- large-ops/1171354/logs/screen-key.txt.gz?level=TRACE. To fix this devstack should shift the ephemeral port range to 49152 to 61000 to avoid IANA port allocations and to avoid linux private port ranges. Additionally keystone should document this fact so that deployers are aware of this and know to work around the funny linux default range. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1253482/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1239894] Re: insecure=True not documented outside of keystoneclient.middleware.auth_token
** No longer affects: nova
** Tags added: sec-guide
--
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/1239894
Title:
insecure=True not documented outside of
keystoneclient.middleware.auth_token
Status in OpenStack Identity (Keystone):
Triaged
Status in OpenStack Manuals:
Triaged
Status in Python client library for Keystone:
Invalid
Bug description:
We use self signed certificate with all openstack services. It all
worked so far, but break once keystoneclient v0.4.0 was released last
week.
As per this commit, keystoneclient by default use insecure=False.
https://github.com/openstack/python-keystoneclient/commit/20e166fd8a943ee3f91ba362a47e9c14c7cc5f4c
This break self-signed instances. The openstack components {nova,
glance, neutron} are unable to communicate with keystone. We don't use
horion or swift. I presume they are broken as well. The keystone
client is happy though if we use --insecure flag, while using it
directly.
Ideally, we should introduce new config parameter
keystone_api_insecure. The insecure flag in keystoneclient should be
defined based on this parameter. This should be fixed in all openstack
services, nova, glance & neutron.
[barumugam@build tempest]$ keystone --insecure tenant-list
+++-+
| id |name| enabled |
+++-+
| csi-tenant-tempest | csi-tenant-tempest | True |
+++-+
[barumugam@build tempest]$ nova --insecure list
ERROR: Unauthorized (HTTP 401)
Nova log:
2013-10-13 00:01:56,680 (keystoneclient.middleware.auth_token): ERROR
auth_token _http_request HTTP connection exception: [Errno 1] _ssl.c:490:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify
failed
2013-10-13 00:01:56,682 (keystoneclient.middleware.auth_token): DEBUG
auth_token _validate_user_token Token validation failure.
Traceback (most recent call last):
File
"/usr/local/csi/share/csi-nova.venv/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py",
line 808, in _validate_user_token
verified = self.verify_signed_token(user_token)
File
"/usr/local/csi/share/csi-nova.venv/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py",
line 1165, in verify_signed_token
if self.is_signed_token_revoked(signed_text):
File
"/usr/local/csi/share/csi-nova.venv/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py",
line 1127, in is_signed_token_revoked
revocation_list = self.token_revocation_list
File
"/usr/local/csi/share/csi-nova.venv/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py",
line 1217, in token_revocation_list
self.token_revocation_list = self.fetch_revocation_list()
File
"/usr/local/csi/share/csi-nova.venv/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py",
line 1235, in fetch_revocation_list
additional_headers=headers)
File
"/usr/local/csi/share/csi-nova.venv/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py",
line 739, in _json_request
response = self._http_request(method, path, **kwargs)
File
"/usr/local/csi/share/csi-nova.venv/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py",
line 704, in _http_request
raise NetworkError('Unable to communicate with keystone')
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1239894/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1233303] Re: Incorrect documentation on protected properties
** No longer affects: openstack-manuals -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1233303 Title: Incorrect documentation on protected properties Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: The documentation patch does not mention that the service does not restart if config value for property protection file is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1233303/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1266620] [NEW] bad english in string: "Disabled reason contains invalid characters or is too long"
Public bug reported: This string: "Disabled reason contains invalid characters or is too long" found in nova/api/openstack/compute/contrib/services.py:177, nova/api/openstack/compute/plugins/v3/services.py:159 should be fixed. >From the spanish translation team: Se recomienda que esta cadena sea reestructurada en su versión original, particularmente "Disabled reason". Essentially, the string isn't the best English and should be re-written so it can be translated properly - particularly the use of "Disabled reason". ** Affects: nova Importance: Undecided Status: New ** Affects: openstack-i18n Importance: Undecided Status: Confirmed ** Tags: i18n ** Also affects: nova Importance: Undecided Status: New ** Summary changed: - translation problem in nova: "Disabled reason" + bad english in string: "Disabled reason" ** Summary changed: - bad english in string: "Disabled reason" + bad english in string: "Disabled reason contains invalid characters or is too long" ** Changed in: openstack-i18n Status: New => Confirmed ** Tags added: i18n -- 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/1266620 Title: bad english in string: "Disabled reason contains invalid characters or is too long" Status in OpenStack Compute (Nova): New Status in OpenStack I18n & L10n: Confirmed Bug description: This string: "Disabled reason contains invalid characters or is too long" found in nova/api/openstack/compute/contrib/services.py:177, nova/api/openstack/compute/plugins/v3/services.py:159 should be fixed. From the spanish translation team: Se recomienda que esta cadena sea reestructurada en su versión original, particularmente "Disabled reason". Essentially, the string isn't the best English and should be re-written so it can be translated properly - particularly the use of "Disabled reason". To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1266620/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1285617] [NEW] sample configuration needs to be updated for database config
Public bug reported: As reported on the mailing list, sample configuration files are out of date with respect to database configuration. http://lists.openstack.org/pipermail/openstack- dev/2014-February/028394.html they lack the [database] stanza and still have sql_connection. ** Affects: glance Importance: Undecided Status: Confirmed ** Changed in: glance Status: New => Confirmed ** Summary changed: - sample configuration needs to be update for database config + sample configuration needs to be updated for database config -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1285617 Title: sample configuration needs to be updated for database config Status in OpenStack Image Registry and Delivery Service (Glance): Confirmed Bug description: As reported on the mailing list, sample configuration files are out of date with respect to database configuration. http://lists.openstack.org/pipermail/openstack- dev/2014-February/028394.html they lack the [database] stanza and still have sql_connection. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1285617/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1430365] Re: config drive table force_config_drive parameter values do not match Impl
** Also affects: nova Importance: Undecided Status: New ** Changed in: openstack-manuals Milestone: kilo => liberty ** Tags added: doc-tools -- 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/1430365 Title: config drive table force_config_drive parameter values do not match Impl Status in OpenStack Compute (Nova): New Status in OpenStack Manuals: Confirmed Bug description: The config drive table [1] describes for the force_config_drive parameter the following options: Default: None Other Options: always But looking at the code [2], only the following values are allowed: always, True, False What does the current default 'None' mean? Is it really a value? Or desribes it the abscense of the parameter? I could not configure it for the force_config_drive option. The abscense of the parameter is the same as 'False', so I guess that's the correct default, isn't it? The docs should be updated accordingly. [1] https://github.com/openstack/openstack-manuals/blob/master/doc/common/tables/nova-configdrive.xml [2] https://github.com/openstack/nova/blob/master/nova/virt/configdrive.py To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1430365/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1416496] Re: nova.conf - configuration options icehouse compat flag is not right
** Changed in: openstack-manuals Status: In Progress => Fix Released -- 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/1416496 Title: nova.conf - configuration options icehouse compat flag is not right Status in OpenStack Compute (Nova): Fix Committed Status in OpenStack Manuals: Fix Released Bug description: Table 2.57. Description of upgrade levels configuration options has the wrong information for setting icehouse/juno compat flags during upgrades. Specifically this section: compute = None (StrOpt) Set a version cap for messages sent to compute services. If you plan to do a live upgrade from havana to icehouse, you should set this option to "icehouse-compat" before beginning the live upgrade procedure This should be compute = , for example compute = icehouse when doing an upgrade from I to J. --- Built: 2015-01-29T19:27:05 00:00 git SHA: 3e80c2419cfe03f86057f3229044cd0d495e0295 URL: http://docs.openstack.org/juno/config-reference/content/list-of-compute-config-options.html source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/config-reference/compute/section_compute-options-reference.xml xml:id: list-of-compute-config-options To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1416496/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1435386] Re: Specific config setting may result in VMs being taken over through VNC
** Changed in: openstack-manuals Milestone: kilo => liberty ** 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/1435386 Title: Specific config setting may result in VMs being taken over through VNC Status in OpenStack Manuals: Triaged Status in OpenStack Security Advisories: Won't Fix Bug description: Jonathan Hogg from Chargebox reports (edited): On a single-machine cloud running OpenStack Icehouse and over the last week we have seen compromises of all of the Ubuntu 14.04 VMs running on the machine. Scenario shows the attacker gaining access through VNC (via controlled reboot to reset root password). QEMU instances are running with -vnc 0.0.0.0:1, which may or may not be the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1435386/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1028684] Re: Missing body parameters in volume create function
** Changed in: python-cinderclient Status: Fix Committed => Fix Released -- 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/1028684 Title: Missing body parameters in volume create function Status in OpenStack Compute (Nova): Fix Released Status in Python client library for Cinder: Fix Released Bug description: When trying to run tempest against cinder, discovered that provided metadata was not being used in volume creation. Along with this some other parameters should be there as well including; user_id, project_id, availability_zone and type_id. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1028684/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1287542] Re: Error importing module nova.openstack.common.sslutils: duplicate option: ca_file
** Changed in: blazar Status: Fix Committed => Fix Released -- 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/1287542 Title: Error importing module nova.openstack.common.sslutils: duplicate option: ca_file Status in Blazar: Fix Released Status in OpenStack Telemetry (Ceilometer): Fix Released Status in OpenStack Compute (Nova): Fix Released Status in Messaging API for OpenStack: Fix Released Bug description: Error importing module nova.openstack.common.sslutils: duplicate option: ca_file This is seen in the nova gate - for unrelated patches - it might be a bad slave I guess, or it might be happening to all subsequent patches, or it might be a WTF. http://logstash.openstack.org/#eyJzZWFyY2giOiJcIkVycm9yIGltcG9ydGluZyBtb2R1bGUgbm92YS5vcGVuc3RhY2suY29tbW9uLnNzbHV0aWxzOiBkdXBsaWNhdGUgb3B0aW9uOiBjYV9maWxlXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjkwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjEzOTM5MTUyNTE4ODl9 suggest it has only happened once so far. commit 5188052937219badaa692f67d9f98623c15d1de2 Merge: af626d0 88b7380 Author: Jenkins Date: Tue Mar 4 02:47:02 2014 + Merge "Sync latest config file generator from oslo-incubator" Was the latest merge prior to this, but it may be coincidental. To manage notifications about this bug go to: https://bugs.launchpad.net/blazar/+bug/1287542/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1278028] Re: VMware: update the default 'task_poll_interval' time
** Changed in: openstack-manuals Status: Confirmed => Fix Released ** Changed in: openstack-manuals Assignee: (unassigned) => Tom Fifield (fifieldt) ** Changed in: openstack-manuals Milestone: None => liberty -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1278028 Title: VMware: update the default 'task_poll_interval' time Status in Cinder: Fix Released Status in OpenStack Image Registry and Delivery Service (Glance): New Status in OpenStack Manuals: Fix Released Bug description: https://review.openstack.org/70079 Dear documentation bug triager. This bug was created here because we did not know how to map the project name "openstack/nova" to a launchpad project name. This indicates that the notify_impact config needs tweaks. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit 73c87a280e77e03d228d34ab4781ca2e3b02e40e Author: Gary Kotton Date: Thu Jan 30 01:44:10 2014 -0800 VMware: update the default 'task_poll_interval' time The original means that each operation against the backend takes at least 5 seconds. The default is updated to 0.5 seconds. DocImpact Updated default value for task_poll_interval from 5 seconds to 0.5 seconds Change-Id: I867b913f52b67fa9d655f58a2e316b8fd1624426 Closes-bug: #1274439 To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1278028/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1266391] Re: Install the dashboard in OpenStack Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora - havana
** Changed in: openstack-manuals 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/1266391 Title: Install the dashboard in OpenStack Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora - havana Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Manuals: Fix Released Bug description: OPENSTACK_KEYSTONE_DEFAULT_ROLE = "Member" in the config file should be set to OPENSTACK_KEYSTONE_DEFAULT_ROLE = "admin" --- Built: 2014-01-03T13:40:41 00:00 git SHA: 9ad96c1083e1bed1a0582d54c7bc99dc84208fa4 URL: http://docs.openstack.org/havana/install-guide/install/yum/content/install_dashboard.html source File: file:/home/jenkins/workspace/openstack-install-deploy-guide-fedora/doc/install-guide/section_dashboard-install.xml xml:id: install_dashboard To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1266391/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1299349] Re: upstream-translation-update Jenkins job failing
** Also affects: openstack-manuals Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1299349 Title: upstream-translation-update Jenkins job failing Status in OpenStack Telemetry (Ceilometer): In Progress Status in Cinder: In Progress Status in OpenStack Image Registry and Delivery Service (Glance): New Status in Orchestration API (Heat): In Progress Status in OpenStack Identity (Keystone): Fix Committed Status in OpenStack Neutron (virtual network service): In Progress Status in OpenStack Compute (Nova): In Progress Status in OpenStack Manuals: New Bug description: Various upstream-translation-update succeed apparently but looking into the file errors get ignored - and there are errors uploading the files to the translation site like: Error uploading file: There is a syntax error in your file. Line 1936: duplicate message definition... Line 7: ...this is the location of the first definition For keystone, see: http://logs.openstack.org/78/7882359da114079e8411bd3f97c5628f2cd1c098/post/keystone-upstream-translation-update/27cbb22/ This has been fixed on ironic with: https://review.openstack.org/#/c/83935 See also: http://lists.openstack.org/pipermail/openstack-i18n/2014-March/000479.html To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1299349/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1306342] Re: Icehouse on CentOS - launch instance failed with nova
Boon,
This is very likely a bug either in packaging or in the code, rather
than a problem in the manuals. I'm going to send this to the nova
project.
** Also affects: nova
Importance: Undecided
Status: New
** No longer affects: openstack-manuals
--
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/1306342
Title:
Icehouse on CentOS - launch instance failed with nova
Status in OpenStack Compute (Nova):
New
Bug description:
Hi there,
I am unable to launch any instance after recent yum upgrade(10 April).
I have installed icehouse on CentOS-6.5.
Dashboard:
Message: Virtual Interface creation failed
Code: 500
Details
File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 296, in
decorated_function return function(self, context, *args, **kwargs) File
"/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 2073, in
run_instance do_run_instance() File
"/usr/lib/python2.6/site-packages/nova/openstack/common/lockutils.py", line
249, in inner return f(*args, **kwargs) File
"/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 2072, in
do_run_instance legacy_bdm_in_spec) File
"/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1205, in
_run_instance notify("error", fault=e) # notify that build failed File
"/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py", line 68,
in __exit__ six.reraise(self.type_, self.value, self.tb) File
"/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1189, in
_run_instance instance, image_meta, legacy_bdm_in_spec) File
"/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1333, in _buil
d_instance network_info.wait(do_raise=False) File
"/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py", line 68,
in __exit__ six.reraise(self.type_, self.value, self.tb) File
"/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1309, in
_build_instance set_access_ip=set_access_ip) File
"/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 399, in
decorated_function return function(self, context, *args, **kwargs) File
"/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1721, in
_spawn LOG.exception(_('Instance failed to spawn'), instance=instance) File
"/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py", line 68,
in __exit__ six.reraise(self.type_, self.value, self.tb) File
"/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1718, in
_spawn block_device_info) File
"/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 2251, in
spawn block_device_info) File "/usr/lib/python2.6/site-packages
/nova/virt/libvirt/driver.py", line 3654, in _create_domain_and_network raise
exception.VirtualInterfaceCreateException()
api.log:
2014-04-11 10:38:36.383 6386 ERROR nova.api.openstack.wsgi [-] Exception
handling resource: multi() got an unexpected keyword argument 'body'
2014-04-11 10:38:36.383 6386 TRACE nova.api.openstack.wsgi Traceback (most
recent call last):
2014-04-11 10:38:36.383 6386 TRACE nova.api.openstack.wsgi File
"/usr/lib/python2.6/site-packages/nova/api/openstack/wsgi.py", line 983, in
_process_stack
2014-04-11 10:38:36.383 6386 TRACE nova.api.openstack.wsgi action_result
= self.dispatch(meth, request, action_args)
2014-04-11 10:38:36.383 6386 TRACE nova.api.openstack.wsgi File
"/usr/lib/python2.6/site-packages/nova/api/openstack/wsgi.py", line 1070, in
dispatch
2014-04-11 10:38:36.383 6386 TRACE nova.api.openstack.wsgi return
method(req=request, **action_args)
2014-04-11 10:38:36.383 6386 TRACE nova.api.openstack.wsgi TypeError: multi()
got an unexpected keyword argument 'body'
compute.log:
2014-04-11 10:38:32.869 17049 ERROR nova.compute.manager
[req-7c8f2ee8-f957-4f1e-b188-2f136fcb7cdb 1cfbc71fddb848668295a2bb1895dfda
9f03371fd9fb4ef8ba5760a3ae1021ba] [instance:
45a6f90d-3c76-4740-bacb-f3ea73c1b78c] Instance failed to spawn
2014-04-11 10:38:32.869 17049 TRACE nova.compute.manager [instance:
45a6f90d-3c76-4740-bacb-f3ea73c1b78c] Traceback (most recent call last):
2014-04-11 10:38:32.869 17049 TRACE nova.compute.manager [instance:
45a6f90d-3c76-4740-bacb-f3ea73c1b78c] File
"/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1718, in _spawn
2014-04-11 10:38:32.869 17049 TRACE nova.compute.manager [instance:
45a6f90d-3c76-4740-bacb-f3ea73c1b78c] block_device_info)
2014-04-11 10:38:32.869 17049 TRACE nova.compute.manager [instance:
45a6f90d-3c76-4740-bacb-f3ea73c1b78c] File
"/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 2251, in
spawn
2014-04-11 10:38:32.869 17049 TRACE nova.compute.manager [instance:
45a6f90d-3c76-4740-bacb-f3ea73c1b78c] block_device_info)
2014-04-11 10:38:32.869 17049 TRACE nova.compute.manager [instance:
4
[Yahoo-eng-team] [Bug 1241395] Re: heat "Stack creation failed" error messages need improvement
This is still an issue in icehouse release candidates. ** Also affects: heat Importance: Undecided Status: New -- 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/1241395 Title: heat "Stack creation failed" error messages need improvement Status in Orchestration API (Heat): New Status in OpenStack Dashboard (Horizon): Confirmed Bug description: When trying to launch a stack, there are several scenarios that results in a "Stack creation failed" error message quick examples include: 2013-10-18 18:40:17.931 11283 TRACE heat.openstack.common.rpc.amqp ValueError: db_password Password must start with an uppercase character 2013-10-18 18:40:17.931 11283 TRACE heat.openstack.common.rpc.amqp 2013-10-18 18:40:17.938 11283 ERROR heat.openstack.common.rpc.common [-] Returning exception db_password Password must start with an uppercase character to caller 2013-10-18 18:40:52.899 10922 TRACE root ValueError: db_password Password length must be between 6 and 8 characters These should ideally be shown to the user in some way. Note - this could be a heat problem, rather than one in horizon. I'll leave that to triage. This is running Havana release from the ubuntu cloud archive. To manage notifications about this bug go to: https://bugs.launchpad.net/heat/+bug/1241395/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1283930] Re: Make metaplugin be used with a router service plugin
Hi, Oda san, Thank you for your comment. In my opinion, this text is good: """ If you use a router service plugin, set 'l3_plugin_list' blank. If 'l3_plugin_list' is not blank, must not specify a router service plugin in 'service_plugins' of neutron.conf. """ However, I feel that perhaps it could be added to the help text of the l3_plugin_list option in the code. At the moment, "(StrOpt) List of L3 plugins to load" is fairly basic, and maybe not so informative for the user :) ** Also affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1283930 Title: Make metaplugin be used with a router service plugin Status in OpenStack Neutron (virtual network service): New Status in OpenStack Manuals: Confirmed Bug description: https://review.openstack.org/65034 commit c04785e0ced18ebab6bada1d3961c1394c541a69 Author: Itsuro Oda Date: Mon Jan 6 15:03:14 2014 +0900 Make metaplugin be used with a router service plugin "l3_plugin_list" configuration parameter of the metaplugin is permitted blank now. If "l3_plugin_list" is blank, router extension and extensions which extend the router extension don't be included in "supported-extension-aliases" of the metaplugin. This makes the metaplugin be able to be used with a router service plugin. Note that if "l3_plugin_list" is not blank, a router service plugin must not be specified, otherwise the error of the bug report still occurs. This patch removes some router extension related meaningless codes also. (e.g. external-net extension belongs to L2 functionality and be handled by core plugins properly.) Closes-bug: 1266347 DocImpact Change-Id: I0454bc0a4bd7eda5dad18b0538fb7baebe0b9f91 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1283930/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1308313] [NEW] bad error message on trove database initialisation failure
Public bug reported: When there is a DatastoreDefaultDatastoreNotFound or DatastoreDefaultVersionNotFound exception raised on trove database creation attempt through horizon, only this is shown to the user: """ Error: There was an error submitting the form. Please try again. """ This is not useful in terms of fixing the problem, and should provide more information. Example debug log: File "/opt/stack/trove/trove/common/wsgi.py", line 251, in execute_action **action_args) File "/opt/stack/trove/trove/openstack/common/wsgi.py", line 395, in execute_action return self.dispatch(self.controller, action, request, **action_args) File "/opt/stack/trove/trove/openstack/common/wsgi.py", line 404, in dispatch return method(*args, **kwargs) File "/opt/stack/trove/trove/instance/service.py", line 186, in create datastore_models.get_datastore_version(**datastore_args)) File "/opt/stack/trove/trove/datastore/models.py", line 179, in get_datastore_version datastore.name) DatastoreDefaultVersionNotFound: Default version for datastore 'Legacy MySQL' not found. Steps to reproduce. 1. Install devstack with all services enabled, using milestone-proposed branch 2. try to create a new database through horizon ** Affects: horizon Importance: Undecided Status: New ** Affects: trove Importance: Undecided Status: New ** Also affects: trove Importance: Undecided Status: New -- 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/1308313 Title: bad error message on trove database initialisation failure Status in OpenStack Dashboard (Horizon): New Status in Trove - Database as a Service: New Bug description: When there is a DatastoreDefaultDatastoreNotFound or DatastoreDefaultVersionNotFound exception raised on trove database creation attempt through horizon, only this is shown to the user: """ Error: There was an error submitting the form. Please try again. """ This is not useful in terms of fixing the problem, and should provide more information. Example debug log: File "/opt/stack/trove/trove/common/wsgi.py", line 251, in execute_action **action_args) File "/opt/stack/trove/trove/openstack/common/wsgi.py", line 395, in execute_action return self.dispatch(self.controller, action, request, **action_args) File "/opt/stack/trove/trove/openstack/common/wsgi.py", line 404, in dispatch return method(*args, **kwargs) File "/opt/stack/trove/trove/instance/service.py", line 186, in create datastore_models.get_datastore_version(**datastore_args)) File "/opt/stack/trove/trove/datastore/models.py", line 179, in get_datastore_version datastore.name) DatastoreDefaultVersionNotFound: Default version for datastore 'Legacy MySQL' not found. Steps to reproduce. 1. Install devstack with all services enabled, using milestone-proposed branch 2. try to create a new database through horizon To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1308313/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1310815] Re: bad django conf example
Also affects horizon. openstack/horizon doc/source/topics/deployment.rst ** Also affects: horizon Importance: Undecided Status: New -- 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/1310815 Title: bad django conf example Status in OpenStack Dashboard (Horizon): New Status in OpenStack Manuals: Triaged Bug description: With Django 1.6, the setting is wrong. You need to use SESSION_ENGINE = 'django.contrib.sessions.backends.db' as described on: https://docs.djangoproject.com/en/1.6/ref/settings/#std:setting- SESSION_ENGINE If i use the one described on this page (SESSION_ENGINE = 'django.core.cache.backends.db.DatabaseCache'), i got a 500 error and i have this in logs: File ".../django-1.6/django/core/handlers/base.py", line 90, in get_response response = middleware_method(request) File ".../django-1.6/django/contrib/sessions/middleware.py", line 10, in process_request engine = import_module(settings.SESSION_ENGINE) File ".../django-1.6/django/utils/importlib.py", line 40, in import_module __import__(name) ImportError: No module named DatabaseCache greetings, Thomas --- Built: 2014-04-07T07:45:00 00:00 git SHA: b7557a0bb682410c86f8022eb07980840d82c8cf URL: http://docs.openstack.org/havana/install-guide/install/apt/content/dashboard-session-database.html source File: file:/home/jenkins/workspace/openstack-install-deploy-guide-ubuntu/doc/common/section_dashboard_sessions.xml xml:id: dashboard-session-database To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1310815/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1308984] Re: Floating IP addresses ordered in a weird way
** Also affects: openstack-community
Importance: Undecided
Status: New
--
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/1308984
Title:
Floating IP addresses ordered in a weird way
Status in OpenStack Dashboard (Horizon):
New
Status in OpenStack Community Project:
New
Bug description:
The floating ip:s are ordered according to UUID instead of IP, more
information in the patch.
---
commit 83a10bf02a5079513741039860208e277e1d12e4
Author: Ian Kumlien
Date: Thu Apr 17 13:49:32 2014 +0200
Sorting floating IP:s according to IP.
While using alot of manually allocated floating ip:s we wondered why
the IP list wasn't sorted. While looking at it we found that the UI
actually does sort the IP but according to the UUID instead of the
actual IP address.
This change fixes this so that it's sorted according to IP.
Found-By: Marko Bocevski
diff --git
a/openstack_dashboard/dashboards/project/access_and_security/floating_ips/workflows.py
b/openstack_dashboard/dashboards/project/access_and_security/floating_ips/workflows.py
index c4ebbd1..d884dee 100644
---
a/openstack_dashboard/dashboards/project/access_and_security/floating_ips/workflows.py
+++
b/openstack_dashboard/dashboards/project/access_and_security/floating_ips/workflows.py
@@ -69,7 +69,7 @@ class AssociateIPAction(workflows.Action):
exceptions.handle(self.request,
_('Unable to retrieve floating IP addresses.'),
redirect=redirect)
-options = sorted([(ip.id, ip.ip) for ip in ips if not ip.port_id])
+options = sorted([(ip.ip, ip.ip) for ip in ips if not ip.port_id])
if options:
options.insert(0, ("", _("Select an IP address")))
else:
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1308984/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1283930] Re: Make metaplugin be used with a router service plugin
** Changed in: openstack-manuals Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1283930 Title: Make metaplugin be used with a router service plugin Status in OpenStack Neutron (virtual network service): Fix Committed Status in OpenStack Manuals: Fix Released Bug description: https://review.openstack.org/65034 commit c04785e0ced18ebab6bada1d3961c1394c541a69 Author: Itsuro Oda Date: Mon Jan 6 15:03:14 2014 +0900 Make metaplugin be used with a router service plugin "l3_plugin_list" configuration parameter of the metaplugin is permitted blank now. If "l3_plugin_list" is blank, router extension and extensions which extend the router extension don't be included in "supported-extension-aliases" of the metaplugin. This makes the metaplugin be able to be used with a router service plugin. Note that if "l3_plugin_list" is not blank, a router service plugin must not be specified, otherwise the error of the bug report still occurs. This patch removes some router extension related meaningless codes also. (e.g. external-net extension belongs to L2 functionality and be handled by core plugins properly.) Closes-bug: 1266347 DocImpact Change-Id: I0454bc0a4bd7eda5dad18b0538fb7baebe0b9f91 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1283930/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1116440] Re: Quantum Documentation misses the output examples
This was substantially improved in Icehouse. Marking fixed - feel free to reopen,. ** Changed in: openstack-manuals Status: Confirmed => Fix Released ** Changed in: openstack-manuals Milestone: None => icehouse -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1116440 Title: Quantum Documentation misses the output examples Status in OpenStack Neutron (virtual network service): Confirmed Status in OpenStack Manuals: Fix Released Bug description: While documentation have several examples of configurations, including all step of how to reproduce, it lacks utilities output examples. So it's really hard to determine whether things goes right or wrong and you'll end up with all commands executed, but nothing really works. This should include not only output of quantum commands themselves, but also output of some diagnostic commands ovs-vsctl with at least simple explanation. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1116440/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1179424] Re: SET syslog_log_facility = LOG_LOCAL1 in nova.conf, but rsyslog can not get the logs
Since this bug is not in OpenStack, and has not been commented in for more than 6 months, I will mark it invalid. If this was done in error, please feel free to reopen. ** Changed in: nova Status: Confirmed => Invalid -- 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/1179424 Title: SET syslog_log_facility = LOG_LOCAL1 in nova.conf, but rsyslog can not get the logs Status in OpenStack Compute (Nova): Invalid Bug description: I add two configuration as follows in /etc/nova/nova.conf: use_syslog = True syslog_log_facility = LOG_LOCAL1 Rsyslog cannot get the nova logs in local1.*, BUT Rsyslog can get them in *.* THis is my rsyslog.conf: local1.* /var/log/openstack_logs By the way, I can get the logs in grizzly, cann not get then in havana To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1179424/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1161165] Re: Move keystone auth to nova.conf.sample
The appropriate settings are now in nova.conf's keystone_authtoken section. ** Changed in: nova Status: In Progress => Fix Released -- 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/1161165 Title: Move keystone auth to nova.conf.sample Status in devstack - openstack dev environments: Invalid Status in OpenStack Compute (Nova): Fix Released Bug description: For a while, nova has supported specifying the keystone authentication info in a [keystone_authtoken] section in nova.conf, instead of a [filter:authtoken] section of api-paste.ini. However, in the nova repository, the example keystone authentication info is still in api- paste.ini instead of nova.conf.sample. It is easier on operators if only the nova.conf file needs to be edited, and seeing the content in etc/nova/api-paste.ini can be confusing. I recommend moving the content from api-paste.ini to nova.conf.sample. Note that this requires modifying devstack since removing these lines from api-paste.ini will cause devstack to fail, and it's used to gate nova. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1161165/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1183259] Re: deleted (then replaced) flavors keep the old name in nova show
Looks like this was fixed in icehouse, or havana. I'm marking this bug as fix released. If you are able to reproduce it in a supported version, please reopen. ** Changed in: nova Status: Incomplete => Fix Released -- 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/1183259 Title: deleted (then replaced) flavors keep the old name in nova show Status in OpenStack Compute (Nova): Fix Released Bug description: If I create a flavor and then delete it and create it anew, the original name comes out in nova show and elsewhere. I suspect that the DB query is lacking a "(deleted=0)" To reproduce: OS_TENANT_NAME=admin nova flavor-create foo 1010 1024 10 1 OS_TENANT_NAME=admin nova flavor-delete foo OS_TENANT_NAME=admin nova flavor-create bar 1010 2048 10 1 nova boot --flavor=bar --image=$WHATEVER baz #See how the output says that the flavor is "foo (1010)" nova show baz <-- also says foo This is using: 1:2013.1-0ubuntu2.1~cloud0 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1183259/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 877046] Re: Misleading error message --bridge interface is required
Unable to confirm the bug, marking as invalid. If this was done in error and it can be reproduced in a supported version, please reopen. ** Changed in: nova Status: Confirmed => Invalid -- 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/877046 Title: Misleading error message --bridge interface is required Status in OpenStack Compute (Nova): Invalid Bug description: When I had in these settings in nova.conf: --network_manage=nova.network.manager.VlanManager --flat_network_bridge=br100 I see this error in the nova_manage.log Fail --bridge_interface is required to create a network interface. While the settings below are incorrect, the error message is even more incorrect. BUG: There is no --bridge_interface parameter Outcome: This OpenStack beginner was confused and frustrated. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/877046/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 872522] Re: NetworkNotFound should be raised when a network is not found in network manager
Believe this 3 year old bug is long-fixed. If the bug recurs, please reopen. ** Summary changed: - NetworkNotFound should be raised when a network is not fould in network manager + NetworkNotFound should be raised when a network is not found in network manager ** Changed in: nova Status: Confirmed => Fix Released -- 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/872522 Title: NetworkNotFound should be raised when a network is not found in network manager Status in OpenStack Compute (Nova): Fix Released Status in OpenStack QA: Won't Fix Bug description: db.network_get_by_cidr() can return None. In that case some method in network manager such as delete_network raises AttriuteError. But this is not informative. In this case, Network manager should throw exception. Following methods have same problem. - FloatingIP.associate_floating_ip() - NetworkManager._get_dhcp_ip() - NetworkManager.allocate_fixed_ip() - NetworkManager.deallocate_fixed_ip() - NetworkManager.lease_fixed_ip() - NetworkManager.release_fixed_ip() - NetworkManager.validate_networks() - VlanManager.allocate_fixed_ip() To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/872522/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 885165] Re: Add option to do remote host SSL cert verification in nova-objectstore
This is now solved with CONF.s3_use_ssl ** Changed in: nova Status: Triaged => Fix Released -- 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/885165 Title: Add option to do remote host SSL cert verification in nova-objectstore Status in OpenStack Compute (Nova): Fix Released Bug description: This bug is related to another bug which I am about to report. In nova/image/s3.py the _conn static method of the S3ImageService class passes in is_secure=False, when creating a new boto.s3.connection.S3Connection. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/885165/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 873686] Re: nova.network.lease_fixed_ip doesn't raise correct exceptions
** No longer affects: openstack-qa -- 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/873686 Title: nova.network.lease_fixed_ip doesn't raise correct exceptions Status in OpenStack Compute (Nova): Invalid Bug description: nova.network.lease_fixed_ip throws exceptions .Error. This should be exception.instanceNotFound To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/873686/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 884825] Re: utils.runthis has unused argument and unused valiables
** No longer affects: openstack-qa -- 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/884825 Title: utils.runthis has unused argument and unused valiables Status in OpenStack Compute (Nova): Fix Released Bug description: prompt is not used. https://github.com/openstack/nova/blob/stable/diablo/nova/utils.py#L274 rv, err are not used. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/884825/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 872450] Re: utils.xhtml_escape should escape apostrophe, U+0027
** No longer affects: openstack-qa -- 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/872450 Title: utils.xhtml_escape should escape apostrophe, U+0027 Status in OpenStack Compute (Nova): Fix Released Bug description: utils.xhtml_escape should escape apostrophe, U+0027 to ' nova/utils.py 514 xhtml_escape(value) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/872450/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 883337] Re: config_drive_id is not in instance model
** No longer affects: openstack-qa -- 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/883337 Title: config_drive_id is not in instance model Status in OpenStack Compute (Nova): Fix Released Bug description: config_drive_id is used in nova.compute.api ,but it is not exist in the model of Instance. https://github.com/openstack/nova/blob/stable/diablo/nova/compute/api.py#L263 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/883337/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 883322] Re: nova.network.manager should handle exceptions and rollback.
** No longer affects: openstack-qa -- 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/883322 Title: nova.network.manager should handle exceptions and rollback. Status in OpenStack Compute (Nova): Confirmed Bug description: nova.network.manager should handle exceptions and rollback. Example associate_floating_ip didn't handle driver.bind_floating_ip(). The method should handle exceptions and cleanup. https://github.com/openstack/nova/blob/master/nova/network/manager.py#L341 This also affects. - FloatingIP.init_host_floating_ips() - FloatingIP.disassociate_floating_ip() - NetworkManager.deallocate_fixed_ip() - FlatDHCPManager.init_host() - FlatDHCPManager._setup_network() - VlanManager.init_host() - VlanManager._setup_network() To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/883322/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 883328] Re: get_glance_client throws UnboundLocalError
** No longer affects: openstack-qa -- 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/883328 Title: get_glance_client throws UnboundLocalError Status in OpenStack Compute (Nova): Fix Released Status in OpenStack Compute (nova) essex series: Fix Released Bug description: get_glance_client throws UnboundLocalError when image_href is refs. UnboundLocalError: local variable 'glance_host' referenced before assignment https://github.com/openstack/nova/blob/stable/diablo/nova/image/glance.py#L90 In this line, the variables is host, port https://github.com/openstack/nova/blob/stable/diablo/nova/image/glance.py#L110 but glance_host, glance_port variable is used https://github.com/openstack/nova/blob/stable/diablo/nova/image/glance.py#L113 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/883328/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 883320] Re: nova.crypto. revoke_certs_by_user should handle ProcessExecutionError
** No longer affects: openstack-qa -- 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/883320 Title: nova.crypto. revoke_certs_by_user should handle ProcessExecutionError Status in OpenStack Compute (Nova): Confirmed Bug description: revoke_cert may throw ProcessExecutionError. https://github.com/openstack/nova/blob/master/nova/crypto.py#L164 This is bad pattern. (See Policy of Exception Handling https://blueprints.launchpad.net/openstack-qa/+spec/nova-exception-policy) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/883320/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 877305] Re: /nova/notifier/list_notifier.py
** Project changed: openstack-qa => nova ** Changed in: nova Status: Confirmed => Invalid -- 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/877305 Title: /nova/notifier/list_notifier.py Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0Ah4SRFAhJkHXdFg3RTFDanBoRktFcDJ0YmV5ZHZwYUE&hl=en_US -Traceability_Matrix: https://docs.google.com/spreadsheet/ccc?key=0Ah4SRFAhJkHXdE1uc2FxcEpWemdFajBWcmlRX01GNkE&hl=en_US -Github branch https://github.com/ntt-pf-lab/nova/tree/openstack-qa-nova-877305 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/877305/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 879315] Re: /nova/notifier/rabbit_notifier.py
** Project changed: openstack-qa => nova ** Changed in: nova Status: New => Invalid -- 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/879315 Title: /nova/notifier/rabbit_notifier.py Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdFA3eElza181Ymx5Z0ZwMWcwX05nQmc&hl=en_US -Tracability-matrix https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdDgweXhHcHNpcHBIbU5mNGpCRWtQNVE&hl=en_US -Github branch https://github.com/ntt-pf-lab/nova/tree/openstack-qa-nova-879315 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/879315/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 880617] Re: nova.network.api
** Project changed: openstack-qa => nova ** Changed in: nova Status: New => Invalid -- 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/880617 Title: nova.network.api Status in OpenStack Compute (Nova): Invalid Bug description: Checklist: https://docs.google.com/spreadsheet/ccc?key=0As5cC18HZlbndEdtdUN3QU9vZHFVNXhWbDJlVjY3ZkE&hl=en_US Traceability_Matrix: https://docs.google.com/spreadsheet/ccc?key=0As5cC18HZlbndGEycWFyaUsxWEZwNEdBTE9ubE9wd3c&hl=en_US github: https://github.com/ntt-pf-lab/nova/tree/openstack-qa-nova-880617 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/880617/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 878680] Re: nova.scheduler.base_scheduler
** Project changed: openstack-qa => nova ** Changed in: nova Status: Confirmed => Invalid -- 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/878680 Title: nova.scheduler.base_scheduler Status in OpenStack Compute (Nova): Invalid Bug description: Checklist: https://docs.google.com/spreadsheet/ccc?key=0As5cC18HZlbndDJsMWM1a1RHNGd0Q2NLVEh1VGpHVmc&hl=en_US Traceability_Matrix: https://docs.google.com/spreadsheet/ccc?key=0As5cC18HZlbndGVxUkdnWDlJazVqdjNCUFY5UEpvT1E&hl=en_US github https://github.com/ntt-pf-lab/nova/tree/openstack-qa-nova-878680 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/878680/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 877121] Re: nova.quota
** Project changed: openstack-qa => nova ** Changed in: nova Status: Confirmed => Invalid -- 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/877121 Title: nova.quota Status in OpenStack Compute (Nova): Invalid Bug description: Checklist: https://docs.google.com/spreadsheet/ccc?key=0As5cC18HZlbndGc4UGdmTzBIM2dZVlNkTXNzN2h0UHc&hl=en_US Traceability_Matrix: https://docs.google.com/spreadsheet/ccc?key=0As5cC18HZlbndDBTQ29FRmJIdlJvQ2xEY0QwQnVwYmc&hl=en_US github: https://github.com/ntt-pf-lab/nova/tree/openstack-qa-nova-877121 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/877121/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 878673] Re: /nova/image/glance.py
** Project changed: openstack-qa => nova ** Changed in: nova Status: In Progress => Invalid -- 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/878673 Title: /nova/image/glance.py Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdHk0QmFvbVhUZVB5SF9QVDNlbWVZRXc&hl=en_US -Tracability-matrix https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdGFtZ3pObW1zRWR2dUlkb3RlWFJTa0E&hl=en_US To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/878673/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 877291] Re: /nova/notifier/log_notifier.py
** Project changed: openstack-qa => nova ** Changed in: nova Status: Confirmed => Invalid -- 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/877291 Title: /nova/notifier/log_notifier.py Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0Ah4SRFAhJkHXdG0xZi1iYXRFemlYWEVDeGgxVUlHRXc&hl=en_US -Traceability_Matrix: https://docs.google.com/spreadsheet/ccc?key=0Ah4SRFAhJkHXdFF6Ukx5UmlqaHltYm83WlR5aVVveXc&hl=en_US -Gibhub branch https://github.com/ntt-pf-lab/nova/tree/openstack-qa-nova-877291 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/877291/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 883308] Re: nova.crypto has unused method
** No longer affects: openstack-qa -- 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/883308 Title: nova.crypto has unused method Status in OpenStack Compute (Nova): Fix Released Bug description: mkreq and mkcacert is not used nova@nova-VirtualBox:/opt/stack/nova$ grep -R mkreq nova Binary file nova/crypto.pyc matches nova/crypto.py:def mkreq(bits, subject='foo', ca=0): nova/crypto.py:req, pk = mkreq(2048, subject, ca=1) <- this is in mkcacert nova/crypto.py:# FIXME subject is not set in mkreq yet nova@nova-VirtualBox:/opt/stack/nova$ grep -R mkcacert nova Binary file nova/crypto.pyc matches nova/crypto.py:def mkcacert(subject='nova', years=1): To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/883308/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 881239] Re: nova.db.api
** Project changed: openstack-qa => nova ** Changed in: nova Status: In Progress => Invalid -- 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/881239 Title: nova.db.api Status in OpenStack Compute (Nova): Invalid Bug description: Checklist: https://docs.google.com/spreadsheet/ccc?key=0As5cC18HZlbndGt2MVBYdHpqQ09mZ2l1R0tzaGxtOUE&hl=en_US Traceability_Matrix: github: https://github.com/ntt-pf-lab/nova/tree/openstack-qa-nova-881239 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/881239/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 877091] Re: /nova/notifier/api.py
** Project changed: openstack-qa => nova ** Changed in: nova Status: Confirmed => Invalid -- 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/877091 Title: /nova/notifier/api.py Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0AhaCUzjDteQYdFozek1OVHM4MVFwNkFoRUYwUTRxOWc&hl=en_US#gid=0 -Traceability_Matrix: https://docs.google.com/spreadsheet/ccc?key=0AhaCUzjDteQYdEpzR3BrOGlQQ1QycFJnb3VfekppVXc&hl=en_US To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/877091/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 877115] Re: /nova/notifier/no_op_notifier.py
** Project changed: openstack-qa => nova ** Changed in: nova Status: Confirmed => Invalid -- 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/877115 Title: /nova/notifier/no_op_notifier.py Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0AhaCUzjDteQYdGpVYVNSeDd4UzlUSHhwRDVkVXJXZnc&hl=en_US -Traceability_Matrix: https://docs.google.com/spreadsheet/ccc?key=0AhaCUzjDteQYdEY3T09VMUV5ekhrbmd1VG1IV3VCUXc&hl=en_US -Github branch https://github.com/ntt-pf-lab/nova/tree/openstack-qa-nova-877115 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/877115/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 856034] Re: nova.compute.manager
** Project changed: openstack-qa => nova ** Changed in: nova Status: In Progress => Invalid -- 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/856034 Title: nova.compute.manager Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0AsUHVTZg__ridEcwNlU4VktxU1ZqVlZ1ZDJhOWlyNXc&hl=en_US -Tracability-matrix https://docs.google.com/spreadsheet/ccc?key=0Ato6uknaqvE8dE0zVzFmdU14OXRWaXcyM3hvUm9McXc&hl=en_US -github https://github.com/ntt-pf-lab/nova/tree/openstack-qa-nova-856034 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/856034/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 884616] Re: /nova/virt/libvirt/netutils.py
** Project changed: openstack-qa => nova ** Changed in: nova Status: New => Invalid -- 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/884616 Title: /nova/virt/libvirt/netutils.py Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdHJndVhFc2NESlNWSjNPTVB4VDVuNWc -Tracability-matrix https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdHljcTBvZGdyU2VrN184ZWNmd2thYnc To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/884616/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 883002] Re: /nova/scheduler/driver.py
** Project changed: openstack-qa => nova ** Changed in: nova Status: In Progress => Invalid -- 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/883002 Title: /nova/scheduler/driver.py Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdFF3OVVkcHJ0Qjk2R042XzBkbjByQkE&hl=en_US -Tracability-matrix https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdHpOdUtFVXNuN0ZkYWVuOTRpUk84Q0E To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/883002/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 880652] Re: nova.manager
** Project changed: openstack-qa => nova ** Changed in: nova Status: New => Invalid -- 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/880652 Title: nova.manager Status in OpenStack Compute (Nova): Invalid Bug description: Checklist: https://docs.google.com/spreadsheet/ccc?key=0As5cC18HZlbndFNsZUNRNHhjU1JyYW1iaFJvNVNPdlE&hl=en_US Traceability_Matrix: https://docs.google.com/spreadsheet/ccc?key=0As5cC18HZlbndFRYUWxBd0hNWnNRU1FYc3dUdE56NkE&hl=en_US github: https://github.com/ntt-pf-lab/nova/tree/openstack-qa-nova-880652 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/880652/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 885104] Re: /nova/scheduler/api.py
** Project changed: openstack-qa => nova ** Changed in: nova Status: New => Invalid -- 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/885104 Title: /nova/scheduler/api.py Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0AhaCUzjDteQYdHktUThSRnRiSjhVNlU5Z2QwSzQ4MlE&hl=en_US#gid=0 -Tracability-matrix https://docs.google.com/spreadsheet/ccc?key=0AhaCUzjDteQYdHg4Wl81QmdXN2M2ZWFHTmJNRGQ2d3c&hl=en_US#gid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/885104/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 884147] Re: nova/scheduler/abstract_scheduler.py
** Project changed: openstack-qa => nova ** Changed in: nova Status: New => Invalid -- 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/884147 Title: nova/scheduler/abstract_scheduler.py Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0Ah4SRFAhJkHXdHBDSWZvSmE1OVFQenVZdG1lcTZuU3c&hl=en_US -Tracability-matrix https://docs.google.com/spreadsheet/ccc?key=0Ah4SRFAhJkHXdHJhYzlHNnNBNUpBakNBb2FVaHdTdkE To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/884147/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 884601] Re: nova.virt.disk
** Project changed: openstack-qa => nova ** Changed in: nova Status: In Progress => Invalid -- 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/884601 Title: nova.virt.disk Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0As5cC18HZlbndHlYckFCRFBQWWdrcy02dUtCSTdzTEE -Tracability-matrix https://docs.google.com/spreadsheet/ccc?key=0As5cC18HZlbndEZTTW5MUXlGTWhqaGJJM0lyb0w0anc -github To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/884601/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 881182] Re: nova.scheduler.zone_manager
** Project changed: openstack-qa => nova ** Changed in: nova Status: New => Invalid -- 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/881182 Title: nova.scheduler.zone_manager Status in OpenStack Compute (Nova): Invalid Bug description: Checklist: https://docs.google.com/spreadsheet/ccc?key=0As5cC18HZlbndDZacklRRjZxNUZPV2kwQzhvT0pzbXc&hl=en_US Traceability_Matrix: https://docs.google.com/spreadsheet/ccc?key=0As5cC18HZlbndFNZVl9tM0hqUTN5aFNHWG1jRGtGRnc&hl=en_US github: To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/881182/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 900298] Re: /nova/network/quantum/melange_connection.py
** Project changed: openstack-qa => nova ** Changed in: nova Status: New => Invalid -- 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/900298 Title: /nova/network/quantum/melange_connection.py Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdHZuMWY3eHI3RGxuSjNMUVNVZnhlS0E -Tracability-matrix https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdFlzb2JpR0ZCc2FkNFU2ajg5OVJ1X0E To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/900298/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 900939] Re: Instance quota exceeded with many self.driver.spawn errors
** No longer affects: openstack-qa -- 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/900939 Title: Instance quota exceeded with many self.driver.spawn errors Status in OpenStack Compute (Nova): Confirmed Bug description: When we do the long running test, we got instance quota exceeded with many self.driver.spawn errors. Because nova didn't cleanup db record when nova get self.driver.spawn error, then the number of instance reaches to the Quota value with no actual instance. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/900939/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 900745] Re: /nova/network/quantum/client.py
** Project changed: openstack-qa => nova ** Changed in: nova Status: New => Invalid -- 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/900745 Title: /nova/network/quantum/client.py Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdExMMzVjRU1pZ2o1UVVNSnJIWUgxTVE -Tracability-matrix https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdEJlcGpTN2NudUxqNGQ3VDRPQjd3UlE To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/900745/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 900264] Re: /nova/network/quantum/quantum_connection.py
** Project changed: openstack-qa => nova ** Changed in: nova Status: New => Invalid -- 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/900264 Title: /nova/network/quantum/quantum_connection.py Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdEpEcWNoSnN4c0o3TF9UV1hpeXVwdGc -Tracability-matrix https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdGJ6MlBOOUdtc1hFNC1fZ3dTSUp1Smc To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/900264/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 894172] Re: nova.compute.manager has unreachable path
** No longer affects: openstack-qa -- 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/894172 Title: nova.compute.manager has unreachable path Status in OpenStack Compute (Nova): Fix Released Bug description: nova.compute.manager has unreachable path https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L306 if not ((bdm['snapshot_id'] is None) or (bdm['volume_id'] is not None)): is equivalent to this: if ((bdm['snapshot_id'] is not None) and (bdm['volume_id'] is None)): bdm['volume_id'] is always set L304 if bdm['snapshot_id'] is not None and bdm['volume_id'] is None https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L304 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/894172/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 900229] Re: /nova/network/quantum/manager.py
** Project changed: openstack-qa => nova ** Changed in: nova Status: New => Invalid -- 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/900229 Title: /nova/network/quantum/manager.py Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdFlDMEVDTnE1VURVSmszV25yZkRUX2c -Tracability-matrix https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdG10Mk9abjZfNmxHZm82ZWZXM05SdWc To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/900229/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 891435] Re: Invalid availability_zone didn't return HTTP/1.1 400 Bad Request
** No longer affects: openstack-qa
--
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/891435
Title:
Invalid availability_zone didn't return HTTP/1.1 400 Bad Request
Status in OpenStack Compute (Nova):
Invalid
Bug description:
Invalid availability_zone didn't return HTTP/1.1 400 Bad Request
This should be return invalid availability_zone error message.
Test
nova@freecloud-a-2:~/devstack4/devstack$ curl -i -H "x-auth-token:
$AUTHTOKEN" -H "content-type: application/json" -d
'{"server":{"name":"fuga","imageRef":2,"flavorRef":3,"availability_zone":"badzone"}}'
$APIURL/v1.1/2/servers
HTTP/1.1 202 Accepted
Content-Type: application/json
Content-Length: 718
Date: Wed, 16 Nov 2011 23:54:17 GMT
{"server": {"status": "BUILD", "updated": "2011-11-16T23:54:17Z",
"hostId": "", "user_id": "demo", "name": "fuga", "links": [{"href":
"http://127.00.1:8774/v1.1/2/servers/7";, "rel": "self"}, {"href":
"http://127.00.1:8774/2/servers/7";, "rel": "bookmark"}], "addresses":
{}, "tenant_id": "2", "image": {"id": "2", "links": [{"href":
"http://127.00.1:8774/2/images/2";, "rel": "bookmark"}]}, "created":
"2011-11-16T23:54:17Z", "uuid": "1a79a930-b1fa-42e3-a68b-
cff655cbdb5e", "accessIPv4": "", "accessIPv6": "", "key_name": null,
"adminPass": "y6LU47nRJasskwCK", "progress": 0, "flavor": {"id": "3",
"links": [{"href": "http://127.00.1:8774/2/flavors/3";, "rel":
"bookmark"}]}, "config_drive": "", "id": 7, "metadata": {}}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/891435/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 890099] Re: Wrong parameter name gateway6 in nova.virt.libvirt.connection
** No longer affects: openstack-qa -- 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/890099 Title: Wrong parameter name gateway6 in nova.virt.libvirt.connection Status in OpenStack Compute (Nova): Fix Released Bug description: This should be gateway_v6 https://github.com/openstack/nova/blob/stable/diablo/nova/virt/libvirt/connection.py#L971 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/890099/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 888073] Re: /nova/virt/libvirt/connection.py
** Project changed: openstack-qa => nova ** Changed in: nova Status: New => Invalid -- 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/888073 Title: /nova/virt/libvirt/connection.py Status in OpenStack Compute (Nova): Invalid Bug description: -Test Specification https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdDFJaUFleUFyRW1EY3owbEhhRjUyUWc -Tracability-matrix https://docs.google.com/spreadsheet/ccc?key=0AulGiQepLutkdFlpTU5BeVozSjQ5bk1na3hfTC1TTkE To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/888073/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 886284] Re: NetworkManager should check instance is exist or not
** No longer affects: openstack-qa -- 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/886284 Title: NetworkManager should check instance is exist or not Status in OpenStack Compute (Nova): Incomplete Bug description: NetworkManager.allocate_for_instance should check instance is exist or not, then if the instance is not exists, throw NotFound exception. https://github.com/openstack/nova/blob/master/nova/network/manager.py#L206 FloatingIP.allocate_for_instance() FloatingIP.deallocate_for_instance() NetworkManager.set_network_host() NetworkManager.deallocate_for_instance() NetworkManager.get_instance_nw_info() NetworkManager.add_virtual_interface() NetworkManager.add_fixed_ip_to_instance() NetworkManager.remove_fixed_ip_from_instance() NetworkManager.allocate_fixed_ip() VlanManager.allocate_fixed_ip() To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/886284/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 881590] Re: Concurrent instance create/delete leads to unpredictable results
** Project changed: openstack-qa => nova ** Changed in: nova Status: New => Invalid -- 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/881590 Title: Concurrent instance create/delete leads to unpredictable results Status in OpenStack Compute (Nova): Invalid Bug description: Hitting this bug in several environments with automatic tests. The instance creation followed by instance deletion (with relatively short interval) sometimes leaves VM running, but marked as deleted in the DB. Have seen some cases when it was left in a pending state, etc. Need a mechanism to synchronize operations performed on same instances/objects (at least for some operations). To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/881590/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1370934] Re: Add details on dhcp_agents_per_network option for DHCP agent HA
This option is currently listed in: http://docs.openstack.org/trunk/config-reference/content /section_networking-options-reference.html however, the help text isn't very good: dhcp_agents_per_network = 1 (IntOpt) Number of DHCP agents scheduled to host a network. To fix this bug, I think we need two patches 1. a patch to neutron to fix the help text to better explain why/when you would alter this option 2. ensure the new networking guide provides detailed information in the agent configuration area ** Also affects: neutron Importance: Undecided Status: New ** Changed in: openstack-manuals Status: New => Confirmed ** Changed in: openstack-manuals Status: Confirmed => Triaged ** Changed in: openstack-manuals Importance: Undecided => Low ** Changed in: openstack-manuals Milestone: None => juno ** Tags added: neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1370934 Title: Add details on dhcp_agents_per_network option for DHCP agent HA Status in OpenStack Neutron (virtual network service): New Status in OpenStack Manuals: Triaged Bug description: The current documentation does not specify any information about the "dhcp_agents_per_network" configuration option in /etc/neutron/neutron.conf. Using this option, it is possible to have the scheduler automatically assign multiple DHCP agents to a tenant network, which provides high availability. If that option is not set, you have to manually assign multiple DHCP agents to each network, which does not scale in terms of management. Would it be possible to document this option here? --- Built: 2014-04-17T10:27:55 00:00 git SHA: 1842612f99f1fe87149db9a3cb0bd43e7892e22b URL: http://docs.openstack.org/trunk/config-reference/content/multi_agent_demo_configuration.html source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/config-reference/networking/section_networking-multi-dhcp-agents.xml xml:id: multi_agent_demo_configuration To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1370934/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 753280] Re: We should use policy routing for VM's.
** Changed in: neutron Status: Incomplete => 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/753280 Title: We should use policy routing for VM's. Status in OpenStack Neutron (virtual network service): Invalid Status in OpenStack Compute (Nova): Invalid Bug description: We currently modify the host's default routing table. We should leave that alone and apply a different routing table for VM's. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/753280/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1233259] Re: Midonet plugin clean up dhcp correctly
** Changed in: neutron Status: In Progress => Confirmed ** Changed in: neutron Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1233259 Title: Midonet plugin clean up dhcp correctly Status in OpenStack Neutron (virtual network service): Fix Released Bug description: Midonet plugin. When a subnet is deleted clean the proper dhcp entry, not always the first one. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1233259/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 884479] Re: Ability to display just a single enlarged table...
Based on the comment from 2012, and the complete lack of activity, I'm going to mark this up as "Opinion". ** Changed in: horizon Status: Triaged => Opinion -- 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/884479 Title: Ability to display just a single enlarged table... Status in OpenStack Dashboard (Horizon): Opinion Bug description: Related to blueprint: improve-user-experience. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/884479/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1378705] Re: Neutron do not pick up existing physical device bridge
** Also affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1378705 Title: Neutron do not pick up existing physical device bridge Status in OpenStack Neutron (virtual network service): New Status in OpenStack Manuals: New Bug description: Hello Maybe this is normal user story, but it is very inconvenient, when I have server with already configured bridge and I have to turn off network interface, so Neutron can create new one. For example I have configured br0 with eth0 port for libvirtd, which has ten virtual machines. If I decide to switch to Neutron, I will have to bring all of them down, delete bridge, start neutron, specify new bridge in libvirt network configuration XML. Such process implies big downtime, which is inconvenient. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1378705/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1297290] Re: keystone-manage db_sync might fail
My hope is that this was just a bug in Havana or before and all is fixed in Icehouse/Juno now ** Changed in: openstack-manuals Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1297290 Title: keystone-manage db_sync might fail Status in OpenStack Identity (Keystone): Expired Status in OpenStack Manuals: Invalid Bug description: Change to step 5. Create the database tables for the Identity Service Add an additional note after the db_sync command that this command may return a critical error and fail to fully migrate an empty repository. This is probably due to the fact that the upgrade scripts do not guard against transaction failures returned from the SQL server. You need to run this command multiple times and check "keystone-manage db_version". If it does not reach version 34, the upgrade scripts have not completed for Havana builds. --- Built: 2014-03-18T18:59:18 00:00 git SHA: b4f5cdc33b9248aa9c9768e2deccbc3a1a04cc3f URL: http://docs.openstack.org/havana/install-guide/install/apt/content/keystone-install.html source File: file:/home/jenkins/workspace/openstack-install-deploy-guide-ubuntu/doc/install-guide/section_keystone-install.xml xml:id: keystone-install To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1297290/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1388494] Re: Install and configure in OpenStack Installation Guide for Ubuntu 14.04 - juno
Hi Tom, Thank you very much for your report, and sorry you got an error. I just wanted to drop a quick line to say most of the OpenStack community is at our 6-monthly conference this week, so replies may be slower than normal. In the meantime, can I confirm 1) the ubuntu version you are running and 2) how you added the ubuntu cloud archive ** Also affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1388494 Title: Install and configure in OpenStack Installation Guide for Ubuntu 14.04 - juno Status in OpenStack Identity (Keystone): New Status in OpenStack Manuals: New Bug description: This is my first time going through the openstack install, so grain of salt, please. When following the guide to the letter on installing keystone I get the following in syslog: Nov 1 23:19:17 i5 kernel: [474361.925239] init: keystone main process (11278) terminated with status 1 Nov 1 23:19:17 i5 kernel: [474361.925245] init: keystone respawning too fast, stopped On the command line, starting keystone-all, I see the following on console: -- root@i5:/var/lib/keystone# /usr/bin/keystone-all 2014-11-01 23:30:26.918 12581 INFO keystone.common.environment [-] Environment configured as: eventlet 2014-11-01 23:30:26.967 12581 CRITICAL keystone [-] ImportError: No module named persistence.backends.sql 2014-11-01 23:30:26.967 12581 TRACE keystone Traceback (most recent call last): 2014-11-01 23:30:26.967 12581 TRACE keystone File "/usr/bin/keystone-all", line 134, in 2014-11-01 23:30:26.967 12581 TRACE keystone service.load_backends() 2014-11-01 23:30:26.967 12581 TRACE keystone File "/usr/lib/python2.7/dist-packages/keystone/service.py", line 58, in load_backends 2014-11-01 23:30:26.967 12581 TRACE keystone token_api=token.Manager(), 2014-11-01 23:30:26.967 12581 TRACE keystone File "/usr/lib/python2.7/dist-packages/keystone/common/dependency.py", line 166, in wrapper 2014-11-01 23:30:26.967 12581 TRACE keystone self.__wrapped_init__(*args, **kwargs) 2014-11-01 23:30:26.967 12581 TRACE keystone File "/usr/lib/python2.7/dist-packages/keystone/common/dependency.py", line 106, in __wrapped_init__ 2014-11-01 23:30:26.967 12581 TRACE keystone init(self, *args, **kwargs) 2014-11-01 23:30:26.967 12581 TRACE keystone File "/usr/lib/python2.7/dist-packages/keystone/token/core.py", line 113, in __init__ 2014-11-01 23:30:26.967 12581 TRACE keystone super(Manager, self).__init__(CONF.token.driver) 2014-11-01 23:30:26.967 12581 TRACE keystone File "/usr/lib/python2.7/dist-packages/keystone/common/manager.py", line 70, in __init__ 2014-11-01 23:30:26.967 12581 TRACE keystone self.driver = importutils.import_object(driver_name) 2014-11-01 23:30:26.967 12581 TRACE keystone File "/usr/lib/python2.7/dist-packages/keystone/openstack/common/importutils.py", line 38, in import_object 2014-11-01 23:30:26.967 12581 TRACE keystone return import_class(import_str)(*args, **kwargs) 2014-11-01 23:30:26.967 12581 TRACE keystone File "/usr/lib/python2.7/dist-packages/keystone/openstack/common/importutils.py", line 28, in import_class 2014-11-01 23:30:26.967 12581 TRACE keystone __import__(mod_str) 2014-11-01 23:30:26.967 12581 TRACE keystone ImportError: No module named persistence.backends.sql 2014-11-01 23:30:26.967 12581 TRACE keystone - Removing the following line from the /etc/keystone/keystone.conf: driver = keystone.token.persistence.backends.sql.Token appears to fix the problem starting keystone-all. I'm not sure what affect that has later on in the installation, but right now it looks like a problem in python-keystoneclient not having the right libs, or not apt-get installing something that is needed, and is not mentioned thus far in the install guide. --- Built: 2014-11-01T18:04:04 00:00 git SHA: 0b43451156b70284686b99d7964cdb179cb9d24c URL: http://docs.openstack.org/juno/install-guide/install/apt/content/keystone-install.html source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_keystone-install.xml xml:id: keystone-install To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1388494/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1388494] Re: Install and configure in OpenStack Installation Guide for Ubuntu 14.04 - juno
Glad to hear it Tom! Do let us know if you find any other way we can make the docs better - we rely on reports like yours :) ** No longer affects: keystone ** Changed in: openstack-manuals Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1388494 Title: Install and configure in OpenStack Installation Guide for Ubuntu 14.04 - juno Status in OpenStack Manuals: Invalid Bug description: This is my first time going through the openstack install, so grain of salt, please. When following the guide to the letter on installing keystone I get the following in syslog: Nov 1 23:19:17 i5 kernel: [474361.925239] init: keystone main process (11278) terminated with status 1 Nov 1 23:19:17 i5 kernel: [474361.925245] init: keystone respawning too fast, stopped On the command line, starting keystone-all, I see the following on console: -- root@i5:/var/lib/keystone# /usr/bin/keystone-all 2014-11-01 23:30:26.918 12581 INFO keystone.common.environment [-] Environment configured as: eventlet 2014-11-01 23:30:26.967 12581 CRITICAL keystone [-] ImportError: No module named persistence.backends.sql 2014-11-01 23:30:26.967 12581 TRACE keystone Traceback (most recent call last): 2014-11-01 23:30:26.967 12581 TRACE keystone File "/usr/bin/keystone-all", line 134, in 2014-11-01 23:30:26.967 12581 TRACE keystone service.load_backends() 2014-11-01 23:30:26.967 12581 TRACE keystone File "/usr/lib/python2.7/dist-packages/keystone/service.py", line 58, in load_backends 2014-11-01 23:30:26.967 12581 TRACE keystone token_api=token.Manager(), 2014-11-01 23:30:26.967 12581 TRACE keystone File "/usr/lib/python2.7/dist-packages/keystone/common/dependency.py", line 166, in wrapper 2014-11-01 23:30:26.967 12581 TRACE keystone self.__wrapped_init__(*args, **kwargs) 2014-11-01 23:30:26.967 12581 TRACE keystone File "/usr/lib/python2.7/dist-packages/keystone/common/dependency.py", line 106, in __wrapped_init__ 2014-11-01 23:30:26.967 12581 TRACE keystone init(self, *args, **kwargs) 2014-11-01 23:30:26.967 12581 TRACE keystone File "/usr/lib/python2.7/dist-packages/keystone/token/core.py", line 113, in __init__ 2014-11-01 23:30:26.967 12581 TRACE keystone super(Manager, self).__init__(CONF.token.driver) 2014-11-01 23:30:26.967 12581 TRACE keystone File "/usr/lib/python2.7/dist-packages/keystone/common/manager.py", line 70, in __init__ 2014-11-01 23:30:26.967 12581 TRACE keystone self.driver = importutils.import_object(driver_name) 2014-11-01 23:30:26.967 12581 TRACE keystone File "/usr/lib/python2.7/dist-packages/keystone/openstack/common/importutils.py", line 38, in import_object 2014-11-01 23:30:26.967 12581 TRACE keystone return import_class(import_str)(*args, **kwargs) 2014-11-01 23:30:26.967 12581 TRACE keystone File "/usr/lib/python2.7/dist-packages/keystone/openstack/common/importutils.py", line 28, in import_class 2014-11-01 23:30:26.967 12581 TRACE keystone __import__(mod_str) 2014-11-01 23:30:26.967 12581 TRACE keystone ImportError: No module named persistence.backends.sql 2014-11-01 23:30:26.967 12581 TRACE keystone - Removing the following line from the /etc/keystone/keystone.conf: driver = keystone.token.persistence.backends.sql.Token appears to fix the problem starting keystone-all. I'm not sure what affect that has later on in the installation, but right now it looks like a problem in python-keystoneclient not having the right libs, or not apt-get installing something that is needed, and is not mentioned thus far in the install guide. --- Built: 2014-11-01T18:04:04 00:00 git SHA: 0b43451156b70284686b99d7964cdb179cb9d24c URL: http://docs.openstack.org/juno/install-guide/install/apt/content/keystone-install.html source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_keystone-install.xml xml:id: keystone-install To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1388494/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1300800] Re: Nova boot fails if sbin not in path
Thanks Thomas, marking as invalid for manuals. ** Changed in: openstack-manuals Status: Triaged => Invalid ** Changed in: openstack-manuals Milestone: juno => None -- 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/1300800 Title: Nova boot fails if sbin not in path Status in devstack - openstack dev environments: Fix Released Status in OpenStack Compute (Nova): Invalid Status in OpenStack Manuals: Invalid Bug description: In a fresh install of devstack I see an error in the nova-compute log when I try to start an instance. I tracked this down to coming from nova/linux_net.py where sysctl is called in _enable_ipv4_forwarding(). If I add /sbin to my path the error goes away. However some distros, e.g.: debian, don't include sbin in the standard path rather they restrict it to root users only. I think the call to sysctl (and possibly other similar calls) should be moved to use rootwrap, along with preventing issues like this it would have the added benifit of making the code slightly more OS agnostic. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1300800/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 900934] Re: Create Image should be accepted only for ACTIVE, PAUSED, SUSPENDED, RESCUED, STOPPED
** Changed in: openstack-qa Status: New => Invalid -- 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/900934 Title: Create Image should be accepted only for ACTIVE,PAUSED,SUSPENDED,RESCUED,STOPPED Status in OpenStack Compute (Nova): Invalid Status in OpenStack QA: Invalid Bug description: Create Image should be accepted only for active instance VM_STATE == ACTIVE,PAUSED,SUSPENDED,RESCUED,STOPPED TASK_STATE == None To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/900934/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1049570] Re: Cannot import name timezone
As Ubuntu 11.04 is marked as 'end of life', making this bug invalid
** Changed in: devstack
Status: New => Invalid
--
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/1049570
Title:
Cannot import name timezone
Status in devstack - openstack dev environments:
Invalid
Status in OpenStack Dashboard (Horizon):
Invalid
Bug description:
With latest code installation with devstack, you will get " internal server
error 500" when accessing dashboard login page. The horizon log tell that an
error "importing middleware horizon.middleware: cannot import name timezone".
I verified the timezone module in django.utils exists there.
Horizon Log
...
[Wed Sep 12 10:43:54 2012] [error] Warning: Could not import Horizon
dependencies. This is normal during installation.
[Wed Sep 12 10:43:54 2012] [error] Warning: Could not import Horizon
dependencies. This is normal during installation.
[Wed Sep 12 10:43:54 2012] [error] [client 192.168.156.156] mod_wsgi
(pid=32481): Exception occurred processing WSGI script
'/opt/stack/horizon/openstack_dashboard/wsgi/django.wsgi'.
[Wed Sep 12 10:43:54 2012] [error] [client 192.168.156.156] mod_wsgi
(pid=32482): Exception occurred processing WSGI script
'/opt/stack/horizon/openstack_dashboard/wsgi/django.wsgi'.
[Wed Sep 12 10:43:54 2012] [error] [client 192.168.156.156] Traceback (most
recent call last):
[Wed Sep 12 10:43:54 2012] [error] [client 192.168.156.156] File
"/usr/lib/pymodules/python2.7/django/core/handlers/wsgi.py", line 250, in
__call__
[Wed Sep 12 10:43:54 2012] [error] [client 192.168.156.156] Traceback (most
recent call last):
[Wed Sep 12 10:43:54 2012] [error] [client 192.168.156.156] File
"/usr/lib/pymodules/python2.7/django/core/handlers/wsgi.py", line 250, in
__call__
[Wed Sep 12 10:43:54 2012] [error] [client 192.168.156.156]
self.load_middleware()
[Wed Sep 12 10:43:54 2012] [error] [client 192.168.156.156]
self.load_middleware()
[Wed Sep 12 10:43:54 2012] [error] [client 192.168.156.156] File
"/usr/lib/pymodules/python2.7/django/core/handlers/base.py", line 47, in
load_middleware
[Wed Sep 12 10:43:54 2012] [error] [client 192.168.156.156] File
"/usr/lib/pymodules/python2.7/django/core/handlers/base.py", line 47, in
load_middleware
[Wed Sep 12 10:43:54 2012] [error] [client 192.168.156.156] raise
exceptions.ImproperlyConfigured('Error importing middleware %s: "%s"' %
(mw_module, e))
[Wed Sep 12 10:43:54 2012] [error] [client 192.168.156.156] raise
exceptions.ImproperlyConfigured('Error importing middleware %s: "%s"' %
(mw_module, e))
[Wed Sep 12 10:43:54 2012] [error] [client 192.168.156.156]
ImproperlyConfigured: Error importing middleware horizon.middleware: "cannot
import name timezone"
[Wed Sep 12 10:43:54 2012] [error] [client 192.168.156.156]
ImproperlyConfigured: Error importing middleware horizon.middleware: "cannot
import name timezone"
=
To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1049570/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 961761] Re: If nova-network is down, Access and Security panel hangs
** Changed in: nova Status: Confirmed => Fix Released ** Changed in: horizon Status: Confirmed => Fix Released -- 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/961761 Title: If nova-network is down, Access and Security panel hangs Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Compute (Nova): Fix Released Bug description: If no nova-network service is available, the Access and Security page never loads and just hangs forever. This is primarily an issue with nova hanging forever when attempting to fetch information about floating ip addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/961761/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 954536] Re: Document how to install on Mac OS X
This wishlist bug has been open a year without any activity. I'm going to move it to "Opinion / Wishlist", which is an easily-obtainable queue of older requests that have come on. This bug can be reopened (set back to "New") if someone decides to work on this. https://wiki.openstack.org/wiki/BugTriage ** Changed in: glance Status: Triaged => Opinion ** Changed in: openstack-manuals Status: Triaged => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/954536 Title: Document how to install on Mac OS X Status in OpenStack Image Registry and Delivery Service (Glance): Opinion Status in OpenStack Manuals: Opinion Bug description: We're missing docs on how to install glance on OS X. Fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/954536/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1858091] Re: Nova compute api v2.1/servers in train
Since this appears to be an issue with Rancher or an application rather than Kolla Ansible, marking as invalid,. ** Changed in: kolla-ansible Status: New => Invalid -- 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/1858091 Title: Nova compute api v2.1/servers in train Status in kolla-ansible: Invalid Status in OpenStack Compute (nova): Invalid Bug description: **Environment**: * OS (e.g. from /etc/os-release): Ubuntu * Kernel (e.g. `uname -a`): Linux host 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux * Docker version if applicable (e.g. `docker version`): 19.03.2 * Kolla-Ansible version (e.g. `git head or tag or stable branch` or pip package version if using release): 9.0.0 * Docker image Install type (source/binary): source * Docker image distribution: train * Are you using official images from Docker Hub or self built? official * If self built - Kolla version and environment used to build: * Share your inventory file, globals.yml and other configuration files if relevant - I have updated kolla-ansible(to 9.0.0) and openstack images(to train) recently. Thus, I was using Rancher node driver to provision openstack instances and use it to deploy k8s cluster. With Stein everything was working smoothly. However, after I updated to Train version, Rancher started getting 400-403 error codes: ``` Error creating machine: Error in driver during machine creation: Expected HTTP response code [200] when accessing [POST http://10.0.225.254:8774/v2.1/os-keypairs], but got 403 instead or Error creating machine: Error in driver during machine creation: Expected HTTP response code [200] when accessing [POST http://10.0.225.254:8774/v2.1/servers], but got 400 instead ``` Thus, I am wondering if anything was changed to nova compute api's in Train version and what action can be done in order to fix that issue? I have reported that bug on Rancher github as well: https://github.com/rancher/rancher/issues/24813 cause I am not sure if its fully openstack-version related issue. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/kolla-ansible/+bug/1858091/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1648643] Re: nova-api-metadata ignores firewall driver
Confirmed by Jens Rosenboom on the ML: I agree with Sam on this. Looking a bit into the code, the mangling part of the iptables rules is only called in nova/network/l3.py, which seems to happen only when nova-network is being used. The installation of the global nova-iptables setup however happens unconditionally in nova/api/manager.py as soon as the nova-api-metadata service is started, which doesn't make much sense in a Neutron environment. So I would propose to either make this setup happen only when nova-network is used or at least allow an deployer to turn it off via a config option. ** Changed in: nova Status: Won't Fix => New ** Changed in: nova Status: New => Confirmed -- 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/1648643 Title: nova-api-metadata ignores firewall driver Status in OpenStack Compute (nova): Confirmed Bug description: In my nova.conf I have firewall_driver = nova.virt.firewall.NoopFirewallDriver When I start nova-api-metadata it installs some iptables rules (and blows away what is already there) I want to make it not manage any iptables rules by using the noop driver however it has no affect on nova-api-metadata. I'm using stable/mitaka although a look at the code in master would indicate this affects master too. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1648643/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1687401] Re: Horizon 403 Forbidden
** No longer affects: openstack-community -- 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/1687401 Title: Horizon 403 Forbidden Status in OpenStack Dashboard (Horizon): New Bug description: Hello there, I have been struggling a bit with moving the horizon page from domain.com/horizon to domain.com/ + setting up HTTPS, here's what I have tied: - [General 403 debugging](https://askubuntu.com/questions/292968/apache2-forbidden-you-dont-have-permission-to-access-dir-on-this-server) - [General 403 debugging](https://unix.stackexchange.com/questions/169513/403-forbidden-you-dont-have-permission-to-access-on-this-server-apache2) - [403 fix for Horizon](https://fosshelp.blogspot.co.uk/2014/02/openstack-horizon-you-dont-have.html) - [General 403 debugging](https://stackoverflow.com/questions/10873295/error-message-forbidden-you-dont-have-permission-to-access-on-this-server) - [Launchpad 403 knwon (and fixed) bug ](https://bugs.launchpad.net/devstack/+bug/1243075) - [HTTPS config guide (from Juno)](https://docs.openstack.org/juno/config-reference/content/configure-dashboard.html#after-example) ### Environment - Followed the latest installation guide (Ocata) - Apache2 version: Apache/2.4.18 (Ubuntu) - Ubuntu 16.04.2 LTS AMD64 ### Configuration **local_settings.py** https://paste.debian.net/930199/ **openstack-dashboard.conf** https://paste.debian.net/930200/ **error.log** https://paste.debian.net/930201/ This leaves me with some funny results, the login page loads but is missing CSS, only plain HTML. When I log in, everything else gives me a `403`. Any help would be appreciated. Thank you, Tiago Ferreira m...@tiferrei.com To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1687401/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1613199] Re: nova should accept pre-pended comments in public keys
** Changed in: nova Status: Invalid => New ** Tags added: ops -- 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/1613199 Title: nova should accept pre-pended comments in public keys Status in OpenStack Compute (nova): New Bug description: Prior to commit 3f3f9bf22efd2fb209d2a2fe0246f4857cd2d21a nova/crypto.py generate_fingerprint used ssh-keygen -q -l -f to generate finger prints. ssh-keygen -qlf is quite happy to process public key matter of the form cert-authority ssh-rsa B3NzaC1yc2EDAQABAAABAQCfHlWGrnpirvqvUTySnoQK6ze5oIXz7cYIT+XCBeBCahlK05O38g0erBGrNWFozZwbIXnysVCibaUJqtH0JrYqmcr2NnYA0PoiTeranvaJI7pQsga1gBxfK/D4UItw5yI6V7w9efMT0zpIP8WEubQz6GFtkyiNVgFCHj3+VhLs3RslvYzb35SFcLXEDsGVQM5NdWBUgRaNRqpTPvuMcxTyPvy32wW72kwaYRQioDJFcE2WJ240M2oSsx+dhTWvI8sW1sEUI1qIDfyBPsOgsLofuSpt4ZNgJqBUTp/hW85wVpNzud6A4YJWHpZXSDMtUMYE9QL+x2fw/b26yck9ZPE/ hines@tun The issue is the string cert-authority at the beginning of the public key matter. This form can appear in authorized_keys to enable multiple users on a project to have individual keys certified by a central certifying authority providing access to a single administrative account. The use of ssh certificates is documented here: https://www.digitalocean.com/community/tutorials/how-to-create-an-ssh- ca-to-validate-hosts-and-clients-with-ubuntu Steps to reproduce: 1) Place the string """ cert-authority ssh-rsa B3NzaC1yc2EDAQABAAABAQCfHlWGrnpirvqvUTySnoQK6ze5oIXz7cYIT+XCBeBCahlK05O38g0erBGrNWFozZwbIXnysVCibaUJqtH0JrYqmcr2NnYA0PoiTeranvaJI7pQsga1gBxfK/D4UItw5yI6V7w9efMT0zpIP8WEubQz6GFtkyiNVgFCHj3+VhLs3RslvYzb35SFcLXEDsGVQM5NdWBUgRaNRqpTPvuMcxTyPvy32wW72kwaYRQioDJFcE2WJ240M2oSsx+dhTWvI8sW1sEUI1qIDfyBPsOgsLofuSpt4ZNgJqBUTp/hW85wVpNzud6A4YJWHpZXSDMtUMYE9QL+x2fw/b26yck9ZPE/ hines@tun """ in a file 2) run nova keypair-add --pub-key Expected result: They nova keypair-list should now list the key Actual result: ERROR (BadRequest): Keypair data is invalid: failed to generate fingerprint (HTTP 400) Environment: Openstack liberty release (bug is not present on kilo) Logs: Sorry, not available (I'm only a user not an admin) Suggest fix: either: 1) revert generate_fingerprint to using exec ssh-keygen 2) generate_fingerprint should strip the string cert-authority from the begining of the public key matter (if present) before attempting to generate the fingerprint. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1613199/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1606056] Re: nova-api did not start
** Project changed: openstack-community => 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/1606056 Title: nova-api did not start Status in OpenStack Compute (nova): New Bug description: Im doing a cloud-init install of a fresh ubuntu 14.04 image, straight from the 'all in one VM' instructions and keep getting : [ERROR] /home/stack/devstack/lib/nova:800 nova-api did not start Error on exit 2016-07-24 19:28:12,017 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/runcmd [1] 2016-07-24 19:28:12,023 - cc_scripts_user.py[WARNING]: Failed to run module scripts-user (scripts in /var/lib/cloud/instance/scripts) 2016-07-24 19:28:12,023 - util.py[WARNING]: Running scripts-user () failed ci-info: no authorized ssh keys fingerprints found for user stack. What keys is it wanting? Ive tried adding various ssh keys to the stack user, but nothing changes. I would be asking on the forum, but the spam filter is not allowing any questions at all. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1606056/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1507826] Re: Error - "Unable to find authentication token in headers" when run "nova image-list on a new install env
** Project changed: openstack-community => 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/1507826
Title:
Error - "Unable to find authentication token in headers" when run
"nova image-list on a new install env
Status in Glance:
New
Bug description:
I just tried to set up a minimum environment with a control node, a
network node and a compute node by following the document "openstack-
install-guide-kilo.pdf". I went through setting up keystone, glance
and compute. At the end of Adding Compute Node section, it verifies
the install. The commands "nova service-list", "nova endpoints" had
good results.
But "nova image-list" has following error:
$ nova image-list
ERROR (ClientException): The server has either erred or is incapable of
performing the requested operation. (HTTP 500) (Request-ID:
req-2c4cd3c7-da8d-480d-949d-1a54f51ec994)
The error "HTTP 500" is kind of general error from http server.
From glance-registry.log, it has following error msg:
2015-10-19 20:08:14.976 32745 WARNING keystonemiddleware.auth_token [-]
Identity response: {"error": {"message": "The request you have made requires
authentication.", "code": 401, "title": "Unauthorized"}}
2015-10-19 20:08:14.997 32745 WARNING keystonemiddleware.auth_token [-]
Identity response: {"error": {"message": "The request you have made requires
authentication.", "code": 401, "title": "Unauthorized"}}
2015-10-19 20:08:14.997 32745 WARNING keystonemiddleware.auth_token [-]
Authorization failed for token
2015-10-19 20:08:14.998 32745 INFO eventlet.wsgi.server [-] 127.0.0.1 - -
[19/Oct/2015 20:08:14] "GET /images/detail?is_public=none&limit=20 HTTP/1.1"
401 187 0.063297
2015-10-19 20:08:15.000 32745 WARNING keystonemiddleware.auth_token [-]
Unable to find authentication token in headers
2015-10-19 20:08:15.001 32745 INFO eventlet.wsgi.server [-] 127.0.0.1 - -
[19/Oct/2015 20:08:15] "GET /images/detail?is_public=none&limit=20 HTTP/1.1"
401 187 0.000781
I searched the forum, I knew there is a post "nova image-list returns
500 error", I tried the steps listed in that post but it didn't fix my
issue. I have double, triple checked the configuration in nova.conf,
glance-api.conf, glance-registry.conf. restarted all nova, glance
services, but the error is still there.
Can anyone tell what I could do to investigate it?
Some other info is as below.
Thanks,
Allen
nova.conf on control node:
# cat /etc/nova/nova.conf
[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/bin/nova-dhcpbridge
log_dir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
force_dhcp_release=True
libvirt_use_virtio_for_bridges=True
verbose=True
ec2_private_dns_show_ip=True
api_paste_config=/etc/nova/api-paste.ini
enabled_apis=ec2,osapi_compute,metadata
rpc_backend = rabbit
auth_strategy = keystone
my_ip = 10.6.117.173
vncserver_listen = 10.6.117.173
vncserver_proxyclient_address = 10.6.117.173
[oslo_messaging_rabbit]
rabbit_host=fbdl4
rabbit_userid=openstack
rabbit_password=abc123
[database]
connection = mysql://nova:abc123@fbdl4/nova
[keystone_authtoken]
auth_uri = http://fbdl4:5000
auth_url = http://fbdl4:35357
auth_plugin = password
project_domain_id = default
user_domain_id = default
project_name = service
username = nova
password = abc123
[glance]
host = fbdl4
[oslo_concurrency]
lock_path = /var/lib/nova/tmp
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1507826/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1515528] Re: openstack-nova-novncproxy-2014.1.5-1.el6.noarch
** Project changed: openstack-community => 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/1515528 Title: openstack-nova-novncproxy-2014.1.5-1.el6.noarch Status in OpenStack Compute (nova): New Bug description: #/usr/bin/nova-novncproxy --web /usr/share/novnc/ WARNING: no 'numpy' module, HyBi protocol will be slower Traceback (most recent call last): File "/usr/bin/nova-novncproxy", line 10, in sys.exit(main()) File "/usr/lib/python2.6/site-packages/nova/cmd/novncproxy.py", line 87, in main wrap_cmd=None) File "/usr/lib/python2.6/site-packages/nova/console/websocketproxy.py", line 47, in __init__ ssl_target=None, *args, **kwargs) File "/usr/lib/python2.6/site-packages/websockify/websocketproxy.py", line 231, in __init__ websocket.WebSocketServer.__init__(self, RequestHandlerClass, *args, **kwargs) TypeError: __init__() got an unexpected keyword argument 'no_parent' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1515528/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1101187] Re: in case ow two networks on the same bridge nova overwrites dnsmasq config
Hi, nova-network was designed for relatively simple networking use cases, so it struggles to support things like this. However, for what you're trying to achieve the neutron project should work very well! Check out the networking guide at : http://docs.openstack.org/networking-guide/ and see about moving to neutron for this. Given that this bug is a few years old now, I think it's time to close it with our apologies. ** Changed in: nova Status: Confirmed => Won't Fix ** Changed in: nova (Ubuntu) Status: Confirmed => Invalid -- 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/1101187 Title: in case ow two networks on the same bridge nova overwrites dnsmasq config Status in OpenStack Compute (nova): Won't Fix Status in nova package in Ubuntu: Invalid Bug description: Some background: I run a private cloud environment (folsom/stable, FlatDhcp) in the 172.17.11.XXX/24 range. The private range for instances is 192.168.100.XX/24 . Basically if I add a floating IP it get's assigned from the 172.17.11.XX/24 range. Recently, I needed to assign 172.17.11.XX fixed addresses for local usage. nova-manage network list 1 192.168.100.0/24None192.168.100.2 8.8.4.4 NoneNone 3 172.17.11.224/28None172.17.11.226 8.8.8.8 NoneNone This should happen on the same bridge (br100). Now when activating an instance with a fixed ip, /var/lib/nova/networks/nova-br100.conf gets overwitten. So I end up with only the 172.17.11.XXX fixed ip in that list. While i would expect 192.168 addresses and 172.17.11 addresses. It seems that nova is not able to handle multiple ipranges/dnsmasq on one bridge? As a workaround I activated the network on a new bridge. I needed to activate proxy_arp and change some iptables to make sure traffic gets to the instance. Not something really maintainable :). To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1101187/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
