[Yahoo-eng-team] [Bug 1518864] [NEW] Reproducibility: remove timestamps in generated files.

[Charles Plessy]

Public bug reported:

Hi Scott,

in , it was suggested to avoid
timestamps in generated files such as `/etc/sudoers.d/90-cloud-init-
users`, in order to enhance reproducibility in installed systems.  Would
you consider doing so ?

Have a nice day,

-- 
Charles

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1518864

Title:
  Reproducibility: remove timestamps in generated files.

Status in cloud-init:
  New

Bug description:
  Hi Scott,

  in , it was suggested to avoid
  timestamps in generated files such as `/etc/sudoers.d/90-cloud-init-
  users`, in order to enhance reproducibility in installed systems.
  Would you consider doing so ?

  Have a nice day,

  -- 
  Charles

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1518864/+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 1518893] [NEW] Instance flavor column does not sort the proper way

[Itxaka]

Public bug reported:

Latest horizon from master branch.

When displaying the instance list of a project in the Horizon dashboard
(/project/instances/) and sorting the instances by the "size" column, it
won't be sorted the right way.


How to reproduce:

Create 3 instances, 2 with flavor m1.tiny and 1 with flavor m1.small.
Click on the "size" header several times to order them.

Expected result:
m1.tiny
m1.tiny
m1.small

Actual result:
m1.tiny
m1.small
m1.tiny


One would expect them to be sorted by name but instead the "size" filter is 
used which produces the unordered results.
https://github.com/openstack/horizon/blob/master/horizon%2Fstatic%2Fhorizon%2Fjs%2Fhorizon.tables.js#L258-L285

** Affects: horizon
 Importance: Undecided
 Assignee: Itxaka (itxakaserrano)
 Status: New


** Tags: ux

** Changed in: horizon
 Assignee: (unassigned) => Itxaka (itxakaserrano)

-- 
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/1518893

Title:
  Instance flavor column does not sort the proper way

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Latest horizon from master branch.

  When displaying the instance list of a project in the Horizon
  dashboard (/project/instances/) and sorting the instances by the
  "size" column, it won't be sorted the right way.

  
  How to reproduce:

  Create 3 instances, 2 with flavor m1.tiny and 1 with flavor m1.small.
  Click on the "size" header several times to order them.

  Expected result:
  m1.tiny
  m1.tiny
  m1.small

  Actual result:
  m1.tiny
  m1.small
  m1.tiny

  
  One would expect them to be sorted by name but instead the "size" filter is 
used which produces the unordered results.
  
https://github.com/openstack/horizon/blob/master/horizon%2Fstatic%2Fhorizon%2Fjs%2Fhorizon.tables.js#L258-L285

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1518893/+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 1518902] [NEW] revokation list queried twice on token query

[Attila Fazekas]

Public bug reported:

curl -H 'Host: 127.0.0.1:35357' -H 'Accept-Encoding: gzip, deflate' -H
'X-Subject-Token: ' -H 'Accept: application/json' -H 'X
-Auth-Token: ' -H 'Connection: keep-alive' -H 'User-Agent:
python-keystoneclient' http://localhost:35357/v3/auth/tokens


Keystone on behalf of the same HTTP request queries the full revocation_event 
table twice.

SELECT revocation_event.id AS revocation_event_id, revocation_event.domain_id 
AS revocation_event_domain_id, revocation_event.project_id AS 
revocation_event_project_id, revocation_event.user_id AS 
revocation_event_user_id, revocation_event.role_id AS revocation_event_role_id, 
revocation_event.trust_id AS revocation_event_trust_id, 
revocation_event.consumer_id AS revocation_event_consumer_id, 
revocation_event.access_token_id AS revocation_event_access_token_id, 
revocation_event.issued_before AS revocation_event_issued_before, 
revocation_event.expires_at AS revocation_event_expires_at, 
revocation_event.revoked_at AS revocation_event_revoked_at, 
revocation_event.audit_id AS revocation_event_audit_id, 
revocation_event.audit_chain_id AS revocation_event_audit_chain_id 
FROM revocation_event ORDER BY revocation_event.revoked_at

The full revocation_event table must not be queried multiple times on behalf of 
the same HTTP request,
it is a  waste of resources.

PS.: It happens also when X-Subject-Token = X-Auth-Token.

** Affects: keystone
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1518902

Title:
  revokation list queried twice on token query

Status in OpenStack Identity (keystone):
  New

Bug description:
  curl -H 'Host: 127.0.0.1:35357' -H 'Accept-Encoding: gzip, deflate' -H
  'X-Subject-Token: ' -H 'Accept: application/json' -H 'X
  -Auth-Token: ' -H 'Connection: keep-alive' -H 'User-Agent:
  python-keystoneclient' http://localhost:35357/v3/auth/tokens

  
  Keystone on behalf of the same HTTP request queries the full revocation_event 
table twice.

  SELECT revocation_event.id AS revocation_event_id, revocation_event.domain_id 
AS revocation_event_domain_id, revocation_event.project_id AS 
revocation_event_project_id, revocation_event.user_id AS 
revocation_event_user_id, revocation_event.role_id AS revocation_event_role_id, 
revocation_event.trust_id AS revocation_event_trust_id, 
revocation_event.consumer_id AS revocation_event_consumer_id, 
revocation_event.access_token_id AS revocation_event_access_token_id, 
revocation_event.issued_before AS revocation_event_issued_before, 
revocation_event.expires_at AS revocation_event_expires_at, 
revocation_event.revoked_at AS revocation_event_revoked_at, 
revocation_event.audit_id AS revocation_event_audit_id, 
revocation_event.audit_chain_id AS revocation_event_audit_chain_id 
  FROM revocation_event ORDER BY revocation_event.revoked_at

  The full revocation_event table must not be queried multiple times on behalf 
of the same HTTP request,
  it is a  waste of resources.

  PS.: It happens also when X-Subject-Token = X-Auth-Token.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1518902/+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 1509349] Re: [docs] Update the glance_store swift section with Keystone v3 support

[ologvinova]

** Changed in: glance
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1509349

Title:
  [docs] Update the glance_store swift section with Keystone v3 support

Status in Glance:
  Fix Released

Bug description:
  Keystone v3 (along with v2 - default) is now supported in the Swift
  storage backend configuration according to the patch
  https://review.openstack.org/#/c/193422/3

  The appropriate section of the guide should reflect this change
  ( 
http://docs.openstack.org/developer/glance/configuring.html#configuring-the-swift-storage-backend
 ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1509349/+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 1426813] Re: configuration docs need to be updated for the deprecated swift options

[ologvinova]

** Changed in: glance
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1426813

Title:
  configuration docs need to be updated for the deprecated swift options

Status in Glance:
  Fix Released

Bug description:
  The sample conf shows that a bunch of the swift options in glance-
  store are deprecated. We set some of these with puppet so I'd like to
  know where they're moving to or if they're just going away so that I
  can update the puppet-glance module.

  The configuring.rst doc needs to be updated to account for these.
  Since that's part of the main repo I'm filing here and not in docs,
  please move if needed.

  Some examples:

  # Version of the authentication service to use. Valid versions are 2
  # for keystone and 1 for swauth and rackspace. (deprecated) (string
  # value)
  #swift_store_auth_version = 2

  # The address where the Swift authentication service is
  # listening.(deprecated) (string value)
  #swift_store_auth_address = 

  # The user to authenticate against the Swift authentication service
  # (deprecated) (string value)
  #swift_store_user = 

  # Auth key for the user authenticating against the Swift
  # authentication service. (deprecated) (string value)
  #swift_store_key = 

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1426813/+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 1518917] [NEW] add missing package in doc

[Daniele Pizzolli]

Public bug reported:

In the development.environment.rst the installation of
python-virtualenv  is not explict.

I will propose a patch soon.

** Affects: keystone
 Importance: Undecided
 Assignee: Daniele Pizzolli (daniele-pizzolli)
 Status: In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1518917

Title:
  add missing package in doc

Status in OpenStack Identity (keystone):
  In Progress

Bug description:
  In the development.environment.rst the installation of
  python-virtualenv  is not explict.

  I will propose a patch soon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1518917/+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 1518921] [NEW] Functional tests failing inside _test_restart_service_on_sighup with "Timed out waiting for file /tmp/XXX/YYY/test_server.tmp to be created and its size become equ

[Ihar Hrachyshka]

Public bug reported:

Example: http://logs.openstack.org/89/244089/4/check/gate-neutron-dsvm-
functional/1ebb083/testr_results.html.gz

Example log:

ft1.123: 
neutron.tests.functional.agent.test_l3_agent.TestL3AgentRestart.test_restart_l3_agent_on_sighup_StringException:
 Empty attachments:
  pythonlogging:''
  pythonlogging:'neutron.api.extensions'
  stderr
  stdout

Traceback (most recent call last):
  File "neutron/tests/functional/agent/test_l3_agent.py", line 943, in 
test_restart_l3_agent_on_sighup
workers=1)
  File "neutron/tests/functional/test_server.py", line 158, in 
_test_restart_service_on_sighup
'size': expected_size}))
  File "neutron/agent/linux/utils.py", line 324, in wait_until_true
eventlet.sleep(sleep)
  File 
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/eventlet/greenthread.py",
 line 34, in sleep
hub.switch()
  File 
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/eventlet/hubs/hub.py",
 line 294, in switch
return self.greenlet.switch()
RuntimeError: Timed out waiting for file 
/tmp/tmpsoYARR/tmpzLkipc/test_server.tmp to be created and its size become 
equal to 10.

Kibana:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message:%5C%22to%20be%20created%20and%20its%20size%20become%20equal%20%5C%22

243 hits in 7 days.

** Affects: neutron
 Importance: High
 Status: New

** Changed in: neutron
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1518921

Title:
  Functional tests failing inside _test_restart_service_on_sighup with
  "Timed out waiting for file /tmp/XXX/YYY/test_server.tmp to be created
  and its size become equal to ZZZ"

Status in neutron:
  New

Bug description:
  Example: http://logs.openstack.org/89/244089/4/check/gate-neutron-
  dsvm-functional/1ebb083/testr_results.html.gz

  Example log:

  ft1.123: 
neutron.tests.functional.agent.test_l3_agent.TestL3AgentRestart.test_restart_l3_agent_on_sighup_StringException:
 Empty attachments:
pythonlogging:''
pythonlogging:'neutron.api.extensions'
stderr
stdout

  Traceback (most recent call last):
File "neutron/tests/functional/agent/test_l3_agent.py", line 943, in 
test_restart_l3_agent_on_sighup
  workers=1)
File "neutron/tests/functional/test_server.py", line 158, in 
_test_restart_service_on_sighup
  'size': expected_size}))
File "neutron/agent/linux/utils.py", line 324, in wait_until_true
  eventlet.sleep(sleep)
File 
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/eventlet/greenthread.py",
 line 34, in sleep
  hub.switch()
File 
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/eventlet/hubs/hub.py",
 line 294, in switch
  return self.greenlet.switch()
  RuntimeError: Timed out waiting for file 
/tmp/tmpsoYARR/tmpzLkipc/test_server.tmp to be created and its size become 
equal to 10.

  Kibana:
  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message:%5C%22to%20be%20created%20and%20its%20size%20become%20equal%20%5C%22

  243 hits in 7 days.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1518921/+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 1518141] Re: Some special characters used in display_name cause issues.

[jichenjc]

I tried this ,so I think it's a bug in novaclient

jichen@devstack1:~$ nova rename t1 及
jichen@devstack1:~$ nova list
ERROR (UnicodeEncodeError): 'ascii' codec can't encode character u'\u53ca' in 
position 0: ordinal not in range(128)


DEBUG (connectionpool:387) "GET 
/v2.1/d1c5aa58af6c426492c642eb649017be/servers/detail HTTP/1.1" 200 2045
DEBUG (session:216) RESP: [200] Content-Length: 2045 X-Compute-Request-Id: 
req-fbf5ad5c-72e7-4c56-afea-28b1f313d605 Vary: X-OpenStack-Nova-API-Version 
Connection: keep-alive X-Openstack-Nova-Api-Version: 2.6 Date: Mon, 23 Nov 2015 
10:48:51 GMT Content-Type: application/json
RESP BODY: {"servers": [{"status": "ACTIVE", "OS-EXT-SRV-ATTR:ramdisk_id": 
"960df433-efe0-4744-a4fb-828059170e4a", "updated": "2015-11-23T10:48:08Z", 
"hostId": "c6756a173c3668e5edfc570e437e01695989d1992bcfd920d8653918", 
"OS-EXT-SRV-ATTR:host": "devstack1", "addresses": {"private": 
[{"OS-EXT-IPS-MAC:mac_addr": "fa:16:3e:31:e8:bd", "version": 4, "addr": 
"10.0.0.2", "OS-EXT-IPS:type": "fixed"}]}, "links": [{"href": 
"http://192.168.122.239:8774/v2.1/d1c5aa58af6c426492c642eb649017be/servers/e5d86f12-0ab2-4d3c-95a1-9951845f644e";,
 "rel": "self"}, {"href": 
"http://192.168.122.239:8774/d1c5aa58af6c426492c642eb649017be/servers/e5d86f12-0ab2-4d3c-95a1-9951845f644e";,
 "rel": "bookmark"}], "key_name": null, "image": {"id": 
"9eee793a-25e5-4f42-bd9e-b869e60d3dbd", "links": [{"href": 
"http://192.168.122.239:8774/d1c5aa58af6c426492c642eb649017be/images/9eee793a-25e5-4f42-bd9e-b869e60d3dbd";,
 "rel": "bookmark"}]}, "OS-EXT-SRV-ATTR:user_data": null, 
"OS-EXT-STS:task_state": null, "OS-EXT-STS:vm_state": "active", 
"OS-EXT-SRV-ATTR:instance_name": "instance-0001", 
"OS-EXT-SRV-ATTR:root_device_name": "/dev/vda", "OS-SRV-USG:launched_at": 
"2015-11-12T12:24:17.00", "OS-EXT-SRV-ATTR:hypervisor_hostname": 
"devstack1", "flavor": {"id": "84", "links": [{"href": 
"http://192.168.122.239:8774/d1c5aa58af6c426492c642eb649017be/flavors/84";, 
"rel": "bookmark"}]}, "id": "e5d86f12-0ab2-4d3c-95a1-9951845f644e", 
"security_groups": [{"name": "default"}], "OS-SRV-USG:terminated_at": null, 
"OS-EXT-SRV-ATTR:kernel_id": "638edb53-e796-4f8c-b2a6-435e06b2", 
"OS-EXT-AZ:availability_zone": "nova", "user_id": 
"eb66e3bddd1046b8ac12ca3187eb2a5d", "name": "\u53ca", 
"OS-EXT-SRV-ATTR:launch_index": 0, "created": "2015-11-12T12:23:56Z", 
"tenant_id": "d1c5aa58af6c426492c642eb649017be", "OS-DCF:diskConfig": "MANUAL", 
"os-extended-volumes:volumes_attached": [], "accessIPv4": "", "accessIPv6": "", 
"OS-EXT-SRV-ATTR:reservation_id": "r-crtbvkzw", "OS-EXT-SRV-ATTR:hostname": 
"t1", "progress": 0, "OS-EXT-STS:power_state": 1, "config_drive": "True", 
"metadata": {"a": "e"}}]}

DEBUG (shell:909) 'ascii' codec can't encode character u'\u53ca' in position 0: 
ordinal not in range(128)
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/novaclient/shell.py", line 907, 
in main
OpenStackComputeShell().main(argv)
  File "/usr/local/lib/python2.7/dist-packages/novaclient/shell.py", line 834, 
in main
args.func(self.cs, args)
  File "/usr/local/lib/python2.7/dist-packages/novaclient/v2/shell.py", line 
1451, in do_list
formatters, sortby_index=sortby_index)
  File "/usr/local/lib/python2.7/dist-packages/novaclient/utils.py", line 101, 
in print_list
data = str(data).replace("\r", "")
UnicodeEncodeError: 'ascii' codec can't encode character u'\u53ca' in position 
0: ordinal not in range(128)
ERROR (UnicodeEncodeError): 'ascii' codec can't encode character u'\u53ca' in 
position 0: ordinal not in range(128)


** Project changed: nova => python-novaclient

** Changed in: python-novaclient
   Importance: Undecided => Low

** Changed in: python-novaclient
   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/1518141

Title:
  Some special characters used in display_name cause issues.

Status in Cinder:
  New
Status in python-novaclient:
  Confirmed

Bug description:
  One of our Asian users created new instance with roman numeral 2 in its name. 
Looks similar to "II" but it is one character.
  This has caused us issues with CLI trying to list instances "nova list" etc.. 
did not work. Just a small one nothing major, renamed the instance and all 
working fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1518141/+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 1518927] [NEW] nova service state stops updating after SQL connection lost

[György Szombathelyi]

Public bug reported:

After nova-conductor loses mysql connection, it stops to update the service 
'Updated_at' status. 
After logging the error:
ERROR oslo.service.loopingcall [-] Fixed interval looping call 
'nova.servicegroup.drivers.db.DbDriver._report_state' failed
.
.
.
DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to 
MySQL server on '10.97.36.127' ((2013, 'Lost connection to MySQL server during 
query'))") [SQL: u'SELECT 1']

After some tracing, it seems nova.servicegroup.drivers.db _report state
is never called again. Restarting the service correctly restarts
reporting, too. Probably the reporting thread got stuck?

Using Liberty from Ubuntu Cloud Archive: 2:12.0.0-0ubuntu2~cloud0

** Affects: nova
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1518927

Title:
  nova service state stops updating after SQL connection lost

Status in OpenStack Compute (nova):
  New

Bug description:
  After nova-conductor loses mysql connection, it stops to update the service 
'Updated_at' status. 
  After logging the error:
  ERROR oslo.service.loopingcall [-] Fixed interval looping call 
'nova.servicegroup.drivers.db.DbDriver._report_state' failed
  .
  .
  .
  DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to 
MySQL server on '10.97.36.127' ((2013, 'Lost connection to MySQL server during 
query'))") [SQL: u'SELECT 1']

  After some tracing, it seems nova.servicegroup.drivers.db _report
  state is never called again. Restarting the service correctly restarts
  reporting, too. Probably the reporting thread got stuck?

  Using Liberty from Ubuntu Cloud Archive: 2:12.0.0-0ubuntu2~cloud0

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1518927/+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 1518431] Re: Glance failed to upload image to swift storage via RadosGW

[Flavio Percoco]

The swift driver is meant to be used to talk to Swift. If there's a
problem in RadosGW swift API, we should notify the RadosGW maintainers.

** Changed in: glance
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1518431

Title:
  Glance failed to upload image to swift storage via RadosGW

Status in Glance:
  Invalid

Bug description:
  When glance configured with swift backend, and swift API provides via
  RadosGW is unable to upload image.

  Command:
  glance --debug image-create --name trusty_ext4 --disk-format raw 
--container-format bare --file trusty-server-cloudimg-amd64.img --visibility 
public --progress
  Logs:
  http://paste.openstack.org/show/479621/

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1518431/+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 1433435] Re: Change http_keepalive default value from Ture to False

[Rajesh Tailor]

** Changed in: glance
   Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1433435

Title:
  Change http_keepalive default value from Ture to False

Status in Glance:
  Invalid

Bug description:
  In order to close the client socket connection explicitly after the
  response is sent and read successfully by the client, you simply have
  to set keepalive to False when you create a wsgi server.

  Right now it is set to True for backward compatibility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1433435/+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 1507564] Re: os.path.remove doesn't exist. Conver task fails

[Flavio Percoco]

** Also affects: glance/liberty
   Importance: Undecided
   Status: New

** Tags removed: liberty-backport-potential

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1507564

Title:
  os.path.remove doesn't exist. Conver task fails

Status in Glance:
  In Progress
Status in Glance liberty series:
  New

Bug description:
File 
"/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", 
line 96, in run
  for _state in self.run_iter():
File 
"/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", 
line 146, in run_iter
  self._change_state(states.FAILURE)
File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, 
in __exit__
  six.reraise(self.type_, self.value, self.tb)
File 
"/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", 
line 130, in run_iter
  failure.Failure.reraise_if_any(failures)
File "/usr/lib/python2.7/site-packages/taskflow/types/failure.py", line 
244, in reraise_if_any
  failures[0].reraise()
File "/usr/lib/python2.7/site-packages/taskflow/types/failure.py", line 
251, in reraise
  six.reraise(*self._exc_info)
File 
"/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/executor.py", 
line 86, in _revert_task
  result = task.revert(**arguments)
File "/usr/lib/python2.7/site-packages/glance/async/flows/convert.py", line 
99, in revert
  os.path.remove(fs_path)
  AttributeError: 'module' object has no attribute 'remove'
  2015-07-11 11:40:00.817 6663 INFO eventlet.wsgi.server 
[req-c4c286ec-2248-4d93-b631-a2270de43ec8 7a6bd2901f0642b18be91d82782ed1ca 
3954f0a8635249eba2eda9a489e233a7 - - -] 10.12.27.41 - - [11/Jul/2015 11:40:00] 
"POST /v2/tasks HTTP/1.1" 500 139

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1507564/+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 1498416] Re: NOVA-DOCKER-Glance: Docker image can't registe to glance with broken pipe.

[Erno Kuvaja]

No response for month to the additional info request. Closing as
invalid, please reopen if the issue is still persistent.

** Changed in: glance
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1498416

Title:
  NOVA-DOCKER-Glance: Docker image can't registe to glance with broken
  pipe.

Status in Glance:
  Invalid

Bug description:
  OS:Ubuntu 14.04
  openstack KILO with nova-docker
  NOVA-DOCKER-Glance: Docker image can't registe to glance with broken pipe.
  steps:
  ===
  1. deploy kilo setup with 10 docker compute node, 2 network node , 1 
controller. all node are ubuntu 14.04 trusty build.
  2. Register docker image to glance, an "broken pipe" error will be observed 
and image is always in "SAVING" state:

  root@quasarucn3:~# nova image-list
  +--+--+++
  | ID   | Name | Status | Server |
  +--+--+++
  | 23579e1a-d9cc-498a-ac1a-6b4ec11edb9f | cirros   | SAVING ||
  | cdccdaca-6b66-4102-a3c5-255bef33916f | cirros   | ACTIVE ||
  | 2e25e8c4-cf03-4ae2-af47-cb2788a47b18 | ewindisch/cirros | SAVING ||
  | dfea4ce1-6b8b-4905-9d7a-dac6434b5ccd | ewindisch/cirros | SAVING ||
  | 9365acd8-d912-4e6c-acf2-2f8e52da1949 | leo_ubuntu   | SAVING || 
 <
  +--+--+++
  root@quasarucn3:~#
  root@quasarucn3:~#

  
  root@quasarucn3:~# docker images
  REPOSITORY  TAG IMAGE IDCREATED   
  VIRTUAL SIZE
  leo_ubuntu  latest  18e310c9cafc5 weeks ago   
  274.7 MB
  hello-world latest  af340544ed626 weeks ago   
  960 B
  ewindisch/cirroslatest  0a37b1702dd77 months ago  
  7.698 MB
  root@quasarucn3:~#

  root@quasarucn3:~# docker save  leo_ubuntu | glance image-create  
--container-format=docker --visibility public --disk-format=raw --name 
leo_ubuntu
  +--+--+
  | Property | Value|
  +--+--+
  | checksum | None |
  | container_format | docker   |
  | created_at   | 2015-09-18T07:33:49Z |
  | disk_format  | raw  |
  | id   | 9365acd8-d912-4e6c-acf2-2f8e52da1949 |
  | min_disk | 0|
  | min_ram  | 0|
  | name | leo_ubuntu   |
  | owner| 066c321d33c24ea4acaf2e1a0451e85c |
  | protected| False|
  | size | None |
  | status   | queued   |
  | tags | []   |
  | updated_at   | 2015-09-18T07:33:49Z |
  | virtual_size | None |
  | visibility   | public   |
  +--+--+
  write /dev/stdout: broken pipe--bugs
  root@quasarucn3:~# ^C

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1498416/+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 1517060] Re: User (without admin privileges) can change size your own image with 'deactivated' status.

[Flavio Percoco]

** Tags removed: liberty-backport-potential

** Also affects: glance/liberty
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1517060

Title:
  User (without admin privileges) can change size your own image with
  'deactivated' status.

Status in Glance:
  In Progress
Status in Glance liberty series:
  New

Bug description:
  Steps to reproduce:

  1. Create a new image with 'active' status.
  2. Deactivate this image from admin. (image should have a 'deactivated' 
status)
  3. Use this curl request:
  curl -X PUT http://localhost:9292/v1/images/ -H 'X-Auth-Token: 
' -H 'x-image-meta-size: 1234567'
  4. Verify that created image have a '1234567' size.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1517060/+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 1445487] Re: Attempting to deactivate a queued image returns a 403

[Abhishek Kekane]

similar to https://bugs.launchpad.net/glance/+bug/1447322
please refer glance meeting [1] for reason behind marking this as invalid

[1]
http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-11-19-14.01.log.html

** Changed in: glance
   Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1445487

Title:
  Attempting to deactivate a queued image returns a 403

Status in Glance:
  Invalid

Bug description:
  Overview:
  When attempting to deactivate a queued image (one without an image file) 
returns a "'403 Forbidden - Not allowed to deactivate image in status 'queued'".

  Steps to reproduce:
  1) Register a new image as user
  2) Without uploading an image file, deactivate the image as admin via:
  POST /images//actions/deactivate
  3) Notice that a "'403 Forbidden - Not allowed to deactivate image in status 
'queued'" is returned

  Expected:
  A 400 response should be returned with the same message

  Actual:
  A 403 response is returned

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1445487/+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 1505474] Re: Glance raise 500 error when delete images with unallowed status change

[Flavio Percoco]

** Also affects: glance/kilo
   Importance: Undecided
   Status: New

** Also affects: glance/liberty
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1505474

Title:
  Glance raise 500 error when delete images with unallowed status change

Status in Glance:
  Fix Committed
Status in Glance kilo series:
  New
Status in Glance liberty series:
  New

Bug description:
  When user try to change the image's status to unallowed status, such
  as deactivated --> pending-delete, it will rasie a 500 error.

  It's not clear to user. So we should catch this error and return to
  user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1505474/+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 1412802] Re: copy-from broken for large files and swift

[Flavio Percoco]

** No longer affects: glance/icehouse

** No longer affects: glance/juno

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1412802

Title:
  copy-from broken for large files and swift

Status in Glance:
  Fix Released
Status in glance_store:
  In Progress

Bug description:
  Glance may loose some image data while transferring it to the backing
  store thus corrupting the image when ALL the following conditions are
  met:

  - Image is being created by copying data from remote source (--copy-from CLI 
parameter or appropriate API call)
  - Backing store is Swift
  - Image size is larger then configured "swift_store_large_object_size"

  In such scenarios the last chunk stored in Swift will have the size
  significantly less then expected. An attempt to download the image
  will result in a checksum verification error, however the checksum
  stored in Glance (with image metadata) is correct, and so is the size.

  This is easily reproducible even on devstack (if the devstack is
  configured to run Swift as Glance backend). Just decrease
  'swift_store_large_object_size' to some reasonably low value (i.e. 200
  Mb) and try to copy-from any image which is larger then that value.
  After the upload is successful, check the object size in swift (by
  either summing the sizes of all the chunks or by looking to the size
  of virtual large object) - they will be lower then expected:

  
  glance image-create --name tst --disk-format qcow2 --container-format bare 
--copy-from http://192.168.56.1:8000/F18-x86_64-cfntools.qcow2

  ...

  glance image-list
  
+--+-+-+--+---++
  | ID   | Name| 
Disk Format | Container Format | Size  | Status |
  
+--+-+-+--+---++
  | fc34ec49-4bd3-40dd-918f-44d3254f2ac9 | tst | 
qcow2   | bare | 536412160 | active |
  
+--+-+-+--+---++

  ...

  swift stat glance fc34ec49-4bd3-40dd-918f-44d3254f2ac9 --os-tenant-name 
service --os-username admin
 Account: AUTH_cce6e9c12fa34c63b64ef29e84861554
   Container: glance
  Object: fc34ec49-4bd3-40dd-918f-44d3254f2ac9
Content Type: application/octet-stream
  Content Length: 509804544 < see, the size is 
different!
   Last Modified: Mon, 19 Jan 2015 15:52:18 GMT
ETag: "6d0612f82db9a531b34d25823a45073d"
Manifest: glance/fc34ec49-4bd3-40dd-918f-44d3254f2ac9-
   Accept-Ranges: bytes
 X-Timestamp: 1421682737.01148
  X-Trans-Id: tx01a19f7476a541808c9a1-0054bd28e1

  

  glance image-download tst --file out.qcow2
  [Errno 32] Corrupt image download. Checksum was 
0eeddae1007f01b0029136d28518f538 expected 3ecddfe0787a392960d230c87a421c6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1412802/+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 1517060] Re: User (without admin privileges) can change size your own image with 'deactivated' status.

[Flavio Percoco]

** Also affects: glance/kilo
   Importance: Undecided
   Status: New

** Changed in: glance/kilo
   Importance: Undecided => High

** Changed in: glance/liberty
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1517060

Title:
  User (without admin privileges) can change size your own image with
  'deactivated' status.

Status in Glance:
  In Progress
Status in Glance kilo series:
  New
Status in Glance liberty series:
  New

Bug description:
  Steps to reproduce:

  1. Create a new image with 'active' status.
  2. Deactivate this image from admin. (image should have a 'deactivated' 
status)
  3. Use this curl request:
  curl -X PUT http://localhost:9292/v1/images/ -H 'X-Auth-Token: 
' -H 'x-image-meta-size: 1234567'
  4. Verify that created image have a '1234567' size.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1517060/+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 1481320] Re: Creating glance image size 4.5GB trigers to an error 500

[Erno Kuvaja]

Closing as invalid due no response for 2 months after Incomplete.

** Changed in: glance
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1481320

Title:
  Creating glance image size 4.5GB trigers to an error 500

Status in Glance:
  Invalid

Bug description:
  Preconditions:
  Download Windows server 2008 iso to controller node
  
9600.17050.WINBLUE_REFRESH.140317-1640_X64FRE_SERVER_EVAL_EN-US-IR3_SSS_X64FREE_EN-US_DV9.ISO

  Steps to reproduce:
  Navigate to controller node using ssh
  Execute: glance image-create --file 
9600.17050.WINBLUE_REFRESH.140317-1640_X64FRE_SERVER_EVAL_EN-US-IR3_SSS_X64FREE_EN-US_DV9.ISO
 --name "win" --container-format bare --disk-format iso

  Actual result:
  HTTPInternalServerError: HTTPInternalServerError (HTTP 500)
  http://paste.openstack.org/show/406771/

  https://bugs.launchpad.net/mos/+bug/1481321

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1481320/+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 1321545] Re: creating image with only "--file" parameter will raise error but will create a queued image

[Abhishek Kekane]

Now its not creating queued image as --file without --container-format,
--disk-format is not allowed

** Changed in: glance
   Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1321545

Title:
  creating image with only "--file" parameter will raise error but will
  create a queued image

Status in Glance:
  Invalid

Bug description:
  When I use following command to create an image:

  glance image-create --file
  /devstack/files/cirros-0.3.0-x86_64-disk.img

  it returns:

  400 Bad Request
  Invalid disk format 'None' for image.
  (HTTP 400)

  and I use "glance image-list", a queued image has been created.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1321545/+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 1515531] Re: weather applet crashes on logout

[Jeremy Stanley]

** Changed in: nova
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1515531

Title:
  weather applet crashes on logout

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  We are trying our best

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1515531/+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 1505295] Re: Tox tests failing with AttributeError

[Jesse Pretorius]

** Changed in: openstack-ansible
   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/1505295

Title:
  Tox tests failing with AttributeError

Status in Cinder:
  Fix Committed
Status in Designate:
  Fix Committed
Status in neutron:
  Fix Committed
Status in OpenStack Compute (nova):
  In Progress
Status in openstack-ansible:
  Fix Released

Bug description:
  Currently all tests run in Jenkins python27 and python34 are failing
  with an AttributeError, saying that "'str' has no attribute 'DEALER'",
  as well as an AssertionError on assert TRANSPORT is not None in
  cinder/rpc.py.

  An example of the full traceback of the failure can be found here:

   http://paste.openstack.org/show/476040/

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1505295/+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 1517461] Re: Create a 'stable/liberty' branch for networking-vsphere subproject of neutron

[Kyle Mestery]

I've created the stable/liberty branch, so marking this bug as "Fix
Released".

** Changed in: neutron
Milestone: None => mitaka-1

** 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/1517461

Title:
  Create a 'stable/liberty' branch for networking-vsphere subproject of
  neutron

Status in networking-vsphere:
  Confirmed
Status in neutron:
  Fix Released

Bug description:
  As per the guidelines for subprojects in neutron here:
  
https://review.openstack.org/#/c/240800/1/doc/source/stadium/sub_project_guidelines.rst

  We are requesting the neutron release team to create 'stable/liberty'
  branch for networking-vsphere.

  In addition, since we are not part of the release-team, we request you to 
push the tag on 
  that stable/liberty branch of networking-vsphere.

  The SHA to use is HEAD, which is enclosed here:

  396e4de19a81c5b33ed09462f4dfc7c5f4d02ac2

  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-vsphere/+bug/1517461/+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 1518997] [NEW] No unit test for duplicate project creation.

[Ajaya Agrawal]

Public bug reported:

There is no unit test which tests for exception while creating a
duplicate project.

** Affects: keystone
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1518997

Title:
  No unit test for duplicate project creation.

Status in OpenStack Identity (keystone):
  New

Bug description:
  There is no unit test which tests for exception while creating a
  duplicate project.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1518997/+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 1518995] [NEW] l3-agent router sync unbinds port on down ovs-agent

[Miguel Angel Ajo]

Public bug reported:

Using ha-routers, we've found that getting network node agents down for
T>agent_down time, and then bringing them up fires a race condition
during ovs-agent and l3-agent boot.

Even if you set a constraint on ovs-agent being up before l3-agent, that
won't work, because still the l3-agent will start and sync routers
before the ovs-agent is able to report himself active back to neutron
server.

A possible solution:

   Using systemd notify from the openvswitch-agent, so it won't notify
system-d about readiness until the first heartbeat has been sent to
neutron-server.

Other solutions could be detecting the unbound state ("Device x not
defined on plugin") from the ovs-agent and trying to rebind it if the
port is present.


How does it reproduce:

1) neutron-servers and agents are down by being set to standby

some time, T>agent_down_time

2) cluster is took out of standby, neutron-servers and agents are
started again, first neutron-server, then agents

3) neutron servers consider the agents to be down (last heartbeat >
agent_down_time), when checking ports in the database, reset them as
binding failed...

4) agents start, try to fetch info from the ports, as those are in
status binding failed... they get no info from the server (or the
interpretation is wrong "Device xxx not defined on plugin")

5) agents mark ports as dead vlan (4095), as the port "does not exist"
on the server


Analysis over the logs:
  

-- SRV2 tryies to bind port on dead agent (: same happening for SRV1 and
3 that's omitted---

2015-08-25 09:37:11.687000 [SRV2] 16522 DEBUG
neutron.plugins.ml2.managers [req-fd4c17c2-0acc-4bb6-a652-91359eda496b
None] Attempting to bind port 6adcffbf-09d5-4a85-9339-9d6beb2bf82c on
host neutron-n-0 for vnic_type normal with profile  bind_port
/usr/lib/python2.7/site-packages/neutron/plugins/ml2/managers.py:574

2015-08-25 09:37:11.687000 [SRV2] 16522 DEBUG
neutron.plugins.ml2.drivers.mech_agent [req-fd4c17c2-0acc-
4bb6-a652-91359eda496b None] Attempting to bind port 6adcffbf-
09d5-4a85-9339-9d6beb2bf82c on network 2c52ca73-b11f-426f-
9b78-185ef15809e3 bind_port /usr/lib/python2.7/site-
packages/neutron/plugins/ml2/drivers/mech_agent.py:57

2015-08-25 09:37:11.689000 [SRV2] 16522 DEBUG
neutron.plugins.ml2.drivers.mech_agent [req-fd4c17c2-0acc-
4bb6-a652-91359eda496b None] Checking agent: {'binary': u'neutron-
openvswitch-agent', 'description': None, 'admin_state_up': True,
'heartbeat_timestamp': datetime.datetime(2015, 8, 25, 1, 35, 5),
'alive': False, 'id': u'196101f4-9680-43bb-8310-9fca49cd4930', 'topic':
u'N/A', 'host': u'neutron-n-0', 'agent_type': u'Open vSwitch agent',
'started_at': datetime.datetime(2015, 8, 22, 6, 55, 59), 'created_at':
datetime.datetime(2015, 8, 12, 10, 23, 16), 'configurations':
{u'arp_responder_enabled': False, u'tunneling_ip': u'', u'devices': 28,
u'l2_population': False, u'tunnel_types': [],
u'enable_distributed_routing': False, u'bridge_mappings': {u'physnet-
external': u'br-ex', u'physnet-tenants': u'br-enp7s0'}}} bind_port
/usr/lib/python2.7/site-
packages/neutron/plugins/ml2/drivers/mech_agent.py:65

2015-08-25 09:37:11.69 [SRV2] 16522 WARNING
neutron.plugins.ml2.drivers.mech_agent [req-fd4c17c2-0acc-
4bb6-a652-91359eda496b None] Attempting to bind with dead agent:
{'binary': u'neutron-openvswitch-agent', 'description': None,
'admin_state_up': True, 'heartbeat_timestamp': datetime.datetime(2015,
8, 25, 1, 35, 5), 'alive': False, 'id':
u'196101f4-9680-43bb-8310-9fca49cd4930', 'topic': u'N/A', 'host':
u'neutron-n-0', 'agent_type': u'Open vSwitch agent', 'started_at':
datetime.datetime(2015, 8, 22, 6, 55, 59), 'created_at':
datetime.datetime(2015, 8, 12, 10, 23,16), 'configurations':
{u'arp_responder_enabled': False, u'tunneling_ip': u'', u'devices': 28,
u'l2_population': False, u'tunnel_types': [],
u'enable_distributed_routing': False, u'bridge_mappings': {u'physnet-
external': u'br-ex', u'physnet-tenants': u'br-enp7s0'}}}

2015-08-25 09:37:11.69 [SRV2] 16522 WARNING
neutron.plugins.ml2.managers [req-fd4c17c2-0acc-4bb6-a652-91359eda496b
None] Failed to bind port 6adcffbf-09d5-4a85-9339-9d6beb2bf82c on host
neutron-n-0

2015-08-25 09:37:11.719000 [SRV2] 16522 WARNING
neutron.plugins.ml2.plugin [req-fd4c17c2-0acc-4bb6-a652-91359eda496b
None] In _notify_port_updated(), no bound segment for port 6adcffbf-
09d5-4a85-9339-9d6beb2bf82c on network 2c52ca73-b11f-426f-
9b78-185ef15809e3


-- OVS agent 1 requests info for ports, including 
6adcffbf-09d5-4a85-9339-9d6beb2bf82c --


2015-08-25 09:37:16.043000 [OVS1] 12613 DEBUG neutron.common.rpc 
[req-588c942a-6526-464f-a447-782a5e2d436a None] 
neutron.plugins.openvswitch.agent.ovs_neutron_agent.OVSPluginApi method call 
called with arguments (, 
{'args': {'host': 'neutron-n-2', 'agent_id': 'ovs-agent-neutron-n-2', 
'devices': set([u'6adcffbf-09d5-4a85-9339-9d6beb2bf82c', 
u'2cdba01d-e48a-46a6-82c0-bbbfd8e2b490', 
u'fa58d644-8162-410b-8b45-747ae8813a61', 
u'5d5ea109-4807-4df3-bef4-b5d89c3ffebc', 
u'743cc

[Yahoo-eng-team] [Bug 1519001] [NEW] Resource tracker double counts vcpus_used

[Paul Murray]

Public bug reported:

The resource tracker is double counting the number of vcpu used.

It is believe this behavior was introduce in:
https://review.openstack.org/#/c/240159/

That patch moved the vcpu accounting from the extensible resource
tracker plugin into the main resource tracker code.

This behavior is at present openstack/nova master commit
4fb0da175d62084900e68c710f3cc0f916db64e0

To reproduce:

* Set up devstack (e.g. simple single machine setup)
* boot an instance
* initially 'nova hypervisor-show devstack' will show the correct vcpu used 
count
* wait for compute manager periodic task to run, updating the available 
resources
* now 'nova hypervisor-show devstack' will show double the number of used vcpu 
count

** Affects: nova
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1519001

Title:
  Resource tracker double counts vcpus_used

Status in OpenStack Compute (nova):
  New

Bug description:
  The resource tracker is double counting the number of vcpu used.

  It is believe this behavior was introduce in:
  https://review.openstack.org/#/c/240159/

  That patch moved the vcpu accounting from the extensible resource
  tracker plugin into the main resource tracker code.

  This behavior is at present openstack/nova master commit
  4fb0da175d62084900e68c710f3cc0f916db64e0

  To reproduce:

  * Set up devstack (e.g. simple single machine setup)
  * boot an instance
  * initially 'nova hypervisor-show devstack' will show the correct vcpu used 
count
  * wait for compute manager periodic task to run, updating the available 
resources
  * now 'nova hypervisor-show devstack' will show double the number of used 
vcpu count

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1519001/+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 1229324] Re: extraneous vim editor configuration comments

[Sean McGinnis]

** Changed in: python-cinderclient
   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/1229324

Title:
  extraneous vim editor configuration comments

Status in Ceilometer:
  Fix Released
Status in Cinder:
  Fix Released
Status in Glance:
  Fix Released
Status in heat:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in Manila:
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo-incubator:
  Fix Released
Status in python-ceilometerclient:
  Fix Released
Status in python-cinderclient:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-neutronclient:
  In Progress
Status in python-swiftclient:
  In Progress
Status in python-troveclient:
  In Progress
Status in storyboard:
  New
Status in OpenStack Object Storage (swift):
  In Progress
Status in taskflow:
  Fix Released
Status in tempest:
  Fix Released
Status in tuskar:
  Fix Released

Bug description:
  Many of the source code files have a beginning line

  # vim: tabstop=4 shiftwidth=4 softtabstop=4

  This should be deleted.

  Many of these lines are in the ceilometer/openstack/common directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1229324/+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 1519006] [NEW] How to set the supported image formats doesn't seem to be documented

[Stuart McLaren]

Public bug reported:

In glance/common/config.py default supported disk_formats are defined:

 image_format_opts = [
cfg.ListOpt('container_formats',
default=['ami', 'ari', 'aki', 'bare', 'ovf', 'ova'],
help=_("Supported values for the 'container_format' "
   "image attribute"),
deprecated_opts=[cfg.DeprecatedOpt('container_formats',
   group='DEFAULT')]),
cfg.ListOpt('disk_formats',
default=['ami', 'ari', 'aki', 'vhd', 'vmdk', 'raw', 'qcow2',
 'vdi', 'iso'],
help=_("Supported values for the 'disk_format' "
   "image attribute"),
deprecated_opts=[cfg.DeprecatedOpt('disk_formats',
   group='DEFAULT')]),
 ]

But I can't see where we explain to users how to configure them.

** Affects: glance
 Importance: Undecided
 Assignee: Stuart McLaren (stuart-mclaren)
 Status: In Progress

** Changed in: glance
 Assignee: (unassigned) => Stuart McLaren (stuart-mclaren)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1519006

Title:
  How to set the supported image formats doesn't seem to be documented

Status in Glance:
  In Progress

Bug description:
  In glance/common/config.py default supported disk_formats are defined:

   image_format_opts = [
  cfg.ListOpt('container_formats',
  default=['ami', 'ari', 'aki', 'bare', 'ovf', 'ova'],
  help=_("Supported values for the 'container_format' "
 "image attribute"),
  deprecated_opts=[cfg.DeprecatedOpt('container_formats',
 group='DEFAULT')]),
  cfg.ListOpt('disk_formats',
  default=['ami', 'ari', 'aki', 'vhd', 'vmdk', 'raw', 'qcow2',
   'vdi', 'iso'],
  help=_("Supported values for the 'disk_format' "
 "image attribute"),
  deprecated_opts=[cfg.DeprecatedOpt('disk_formats',
 group='DEFAULT')]),
   ]

  But I can't see where we explain to users how to configure them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1519006/+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 1518997] Re: No unit test for duplicate project creation.

[Steve Martinelli]

Bugs should be reserved for issues that end users are hitting with the
current code base. If there is a missing test, just add it to the code
base.

Unless adding a test is showing a bug in the code, then there is no need
to create a bug.

I'm going to mark the bug as invalid, but I'd be more than happy to
review your patch.

** Changed in: keystone
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1518997

Title:
  No unit test for duplicate project creation.

Status in OpenStack Identity (keystone):
  Invalid

Bug description:
  There is no unit test which tests for exception while creating a
  duplicate project.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1518997/+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 1517461] Re: Create a 'stable/liberty' branch for networking-vsphere subproject of neutron

[Kyle Mestery]

** Changed in: neutron
   Status: Fix Released => In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1517461

Title:
  Create a 'stable/liberty' branch for networking-vsphere subproject of
  neutron

Status in networking-vsphere:
  Confirmed
Status in neutron:
  In Progress

Bug description:
  As per the guidelines for subprojects in neutron here:
  
https://review.openstack.org/#/c/240800/1/doc/source/stadium/sub_project_guidelines.rst

  We are requesting the neutron release team to create 'stable/liberty'
  branch for networking-vsphere.

  In addition, since we are not part of the release-team, we request you to 
push the tag on 
  that stable/liberty branch of networking-vsphere.

  The SHA to use is HEAD, which is enclosed here:

  396e4de19a81c5b33ed09462f4dfc7c5f4d02ac2

  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-vsphere/+bug/1517461/+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 1513733] Re: nova api wsgi request lost, system messages show 'ValueError: I/O operation on closed file'

[Markus Zoeller (markus_z)]

@Rong Han:
The Icehouse release has reached its end of life [1], which means there will be 
no upstream fixes for that anymore. That's why I switch the bug status to 
"won't fix". If you've seen this behavior in Juno and newer releases, please 
open a new bug report. 

[1] https://wiki.openstack.org/wiki/Releases

** Changed in: nova
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1513733

Title:
  nova api wsgi request lost, system messages show 'ValueError: I/O
  operation on closed file'

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  1. Exact version of Nova/OpenStack you are running:
  icehouse

  2. Relevant log files:
  the log in /var/log/messages

  Oct 28 17:30:32 controller1 nova-api[4206]: Traceback (most recent call last):
  Oct 28 17:30:32 controller1 nova-api[4206]: File 
"/usr/lib/python2.7/site-packages/eventlet/greenpool.py", line 80, in 
_spawn_n_impl
  Oct 28 17:30:32 controller1 nova-api[4206]: func(*args, **kwargs)
  Oct 28 17:30:32 controller1 nova-api[4206]: File 
"/usr/lib/python2.7/site-packages/eventlet/wsgi.py", line 594, in 
process_request
  Oct 28 17:30:32 controller1 nova-api[4206]: proto.__init__(sock, address, 
self)
  Oct 28 17:30:32 controller1 nova-api[4206]: File 
"/usr/lib64/python2.7/SocketServer.py", line 649, in __init__
  Oct 28 17:30:32 controller1 nova-api[4206]: self.handle()
  Oct 28 17:30:32 controller1 nova-api[4206]: File 
"/usr/lib64/python2.7/BaseHTTPServer.py", line 340, in handle
  Oct 28 17:30:32 controller1 nova-api[4206]: self.handle_one_request()
  Oct 28 17:30:32 controller1 nova-api[4206]: File 
"/usr/lib/python2.7/site-packages/eventlet/wsgi.py", line 285, in 
handle_one_request
  Oct 28 17:30:32 controller1 nova-api[4206]: self.handle_one_response()
  Oct 28 17:30:32 controller1 nova-api[4206]: File 
"/usr/lib/python2.7/site-packages/eventlet/wsgi.py", line 453, in 
handle_one_response
  Oct 28 17:30:32 controller1 nova-api[4206]: 'wall_seconds': finish - start,
  Oct 28 17:30:32 controller1 nova-api[4206]: File 
"/usr/lib/python2.7/site-packages/eventlet/wsgi.py", line 603, in log_message
  Oct 28 17:30:32 controller1 nova-api[4206]: self.log.write(message + '\n')
  Oct 28 17:30:32 controller1 nova-api[4206]: File 
"/usr/lib/python2.7/site-packages/nova/openstack/common/log.py", line 575, in 
write
  Oct 28 17:30:32 controller1 nova-api[4206]: self.logger.log(self.level, 
msg.rstrip())
  Oct 28 17:30:32 controller1 nova-api[4206]: File 
"/usr/lib64/python2.7/logging/__init__.py", line 1471, in log
  Oct 28 17:30:32 controller1 nova-api[4206]: self.logger.log(level, msg, 
*args, **kwargs)
  Oct 28 17:30:32 controller1 nova-api[4206]: File 
"/usr/lib64/python2.7/logging/__init__.py", line 1213, in log
  Oct 28 17:30:32 controller1 nova-api[4206]: self._log(level, msg, args, 
**kwargs)
  Oct 28 17:30:32 controller1 nova-api[4206]: File 
"/usr/lib64/python2.7/logging/__init__.py", line 1268, in _log
  Oct 28 17:30:32 controller1 nova-api[4206]: self.handle(record)
  Oct 28 17:30:32 controller1 nova-api[4206]: File 
"/usr/lib64/python2.7/logging/__init__.py", line 1278, in handle
  Oct 28 17:30:32 controller1 nova-api[4206]: self.callHandlers(record)
  Oct 28 17:30:32 controller1 nova-api[4206]: File 
"/usr/lib64/python2.7/logging/__init__.py", line 1318, in callHandlers
  Oct 28 17:30:32 controller1 nova-api[4206]: hdlr.handle(record)
  Oct 28 17:30:32 controller1 nova-api[4206]: File 
"/usr/lib64/python2.7/logging/__init__.py", line 749, in handle
  Oct 28 17:30:32 controller1 nova-api[4206]: self.emit(record)
  Oct 28 17:30:32 controller1 nova-api[4206]: File 
"/usr/lib64/python2.7/logging/handlers.py", line 425, in emit
  Oct 28 17:30:32 controller1 nova-api[4206]: self.stream.flush()
  Oct 28 17:30:32 controller1 nova-api[4206]: ValueError: I/O operation on 
closed file

  
  3. Reproduce steps:
  build many instances.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1513733/+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 1517461] Re: Create a 'stable/liberty' branch for networking-vsphere subproject of neutron

[Kyle Mestery]

1.0.0 is on PyPI now:

https://pypi.python.org/pypi/networking-vsphere/1.0.0

** Changed in: neutron
   Status: In Progress => 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/1517461

Title:
  Create a 'stable/liberty' branch for networking-vsphere subproject of
  neutron

Status in networking-vsphere:
  Confirmed
Status in neutron:
  Fix Released

Bug description:
  As per the guidelines for subprojects in neutron here:
  
https://review.openstack.org/#/c/240800/1/doc/source/stadium/sub_project_guidelines.rst

  We are requesting the neutron release team to create 'stable/liberty'
  branch for networking-vsphere.

  In addition, since we are not part of the release-team, we request you to 
push the tag on 
  that stable/liberty branch of networking-vsphere.

  The SHA to use is HEAD, which is enclosed here:

  396e4de19a81c5b33ed09462f4dfc7c5f4d02ac2

  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-vsphere/+bug/1517461/+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 1519017] [NEW] nova keypair-list generates ERROR (ClientException): Unexpected API Error.

[Serguei Bezverkhi]

Public bug reported:

On executing nova keypair-list, the following error gets generated:

nova keypair-list
ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
 (HTTP 500) (Request-ID: 
req-5ff60d4d-67e3-4f2d-9912-fd4dcb833165)

** Affects: nova
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1519017

Title:
  nova keypair-list generates ERROR (ClientException): Unexpected API
  Error.

Status in OpenStack Compute (nova):
  New

Bug description:
  On executing nova keypair-list, the following error gets generated:

  nova keypair-list
  ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
   (HTTP 500) (Request-ID: 
req-5ff60d4d-67e3-4f2d-9912-fd4dcb833165)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1519017/+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 1179009] Re: Use testtools for base test class

[Sean McGinnis]

** Changed in: cinder
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1179009

Title:
  Use testtools for base test class

Status in Ceilometer:
  Fix Released
Status in Cinder:
  Fix Released
Status in git-review:
  Fix Committed
Status in Glance:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in oslo-incubator:
  Fix Released
Status in python-ceilometerclient:
  Fix Released
Status in python-heatclient:
  Fix Released
Status in Sahara:
  Fix Released
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  Fix Released
Status in Trove:
  In Progress
Status in Zuul:
  New

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1

  The testtools library has been chosen as the project-wide testing base
  class. It works across 2.6 and 2.7 and is a library that aims to develop
  new testing features before inclusion in the standard library. It
  enforces a few elements of correctness, such as always upcalling
  standard methods, as well as providing hooks for features such as detail
  collection and fixtures with cleanup.

   affects ceilometer
   affects cinder
   affects git-review
   affects glance
   affects horizon
   affects keystone
   affects openstack-ci
   affects oslo
   affects python-ceilometerclient
   affects python-heatclient
   affects reddwarf
   affects swift
   affects tempest
   affects zuul
  -BEGIN PGP SIGNATURE-
  Version: GnuPG v1.4.12 (GNU/Linux)
  Comment: Using GnuPG with undefined - http://www.enigmail.net/

  iEYEARECAAYFAlGObtcACgkQ2Jv7/VK1RgH0AgCg8uEx2Za2rXscfse508hhog7p
  OrMAoK2LacTVUNhbe6R6AxO8XXXB1PWv
  =QEI2
  -END PGP SIGNATURE-

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1179009/+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 1188189] Re: Some server-side 'SSL' communication fails to check certificates (use of HTTPSConnection)

[Sean McGinnis]

No longer any instances of this in cinder.

** Changed in: cinder
   Status: In Progress => 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/1188189

Title:
  Some server-side 'SSL' communication fails to check certificates (use
  of HTTPSConnection)

Status in Cinder:
  Invalid
Status in OpenStack Identity (keystone):
  Fix Released
Status in neutron:
  In Progress
Status in oslo.vmware:
  Fix Released
Status in OpenStack Security Advisory:
  Won't Fix
Status in OpenStack Security Notes:
  Fix Released
Status in python-keystoneclient:
  Fix Released
Status in OpenStack Object Storage (swift):
  Invalid

Bug description:
  Grant Murphy from Red Hat reported usage of httplib.HTTPSConnection
  objects. In Python 2.x those do not perform CA checks so client
  connections are vulnerable to MiM attacks.

  """
  The following files use httplib.HTTPSConnection :
  keystone/middleware/s3_token.py
  keystone/middleware/ec2_token.py
  keystone/common/bufferedhttp.py
  vendor/python-keystoneclient-master/keystoneclient/middleware/auth_token.py

  AFAICT HTTPSConnection does not validate server certificates and
  should be avoided. This is fixed in Python 3, however in 2.X no
  validation occurs. I suspect this is also applicable to most OpenStack
  modules that make HTTPS client calls.

  Similar problems were found in ovirt:
  https://bugzilla.redhat.com/show_bug.cgi?id=851672 (CVE-2012-3533)

  With solutions for ovirt:
  http://gerrit.ovirt.org/#/c/7209/
  http://gerrit.ovirt.org/#/c/7249/
  """

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1188189/+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 1489744] Re: Swapping volume will not result in correct status

[Ryan McNair]

Should be fixed by change in Cinder -
https://review.openstack.org/#/c/247767/

** Also affects: cinder
   Importance: Undecided
   Status: New

** Changed in: cinder
 Assignee: (unassigned) => Ryan McNair (rdmcnair)

** Changed in: cinder
   Status: New => Fix Committed

-- 
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/1489744

Title:
  Swapping volume will not result in correct status

Status in Cinder:
  Fix Committed
Status in OpenStack Compute (nova):
  New

Bug description:
  Swap volume API can swap a in-use volume with available volume.
  Therefore in-use volume should be available and available will be in-use.
  In face, volumes will stay in detaching and attaching respectively after send 
swap volume request to nova.
  But those volumes had been swapped.
  Following are commands flow.

  > cinder list
  
+--+---+--+--+-+--+-+--+
  |  ID  |   Status  | Name | Size | Volume 
Type | Bootable | Multiattach | Attached to  |
  
+--+---+--+--+-+--+-+--+
  | 8a3440f7-afbf-4581-95fb-14730fbd98c1 |   in-use  |  -   |  1   | 
lvmdriver-1 |  false   |False| 6d316dab-426e-48f9-956f-e2f0df1aabcd |
  | cafc833a-8645-47db-b464-999142afa7be | available |  -   |  1   | 
lvmdriver-1 |  false   |False|  |
  
+--+---+--+--+-+--+-+--+

  > sudo iscsiadm -m node 
  10.0.2.15:3260,-1 
iqn.2010-10.org.openstack:volume-8a3440f7-afbf-4581-95fb-14730fbd98c1

  * Ready to send swap volume request *
  > curl -H "Content-Type: application/json" -H "X-Auth-Token: $TOKEN" 
127.0.0.1:8774/v3/servers/6d316dab-426e-48f9-956f-e2f0df1aabcd/os-volume_attachments/8a3440f7-afbf-4581-95fb-14730fbd98c1
 -X 'PUT' -d '{"volumeAttachment": 
{"volumeId":"cafc833a-8645-47db-b464-999142afa7be"}}'

  > cinder list
  
+--+---+--+--+-+--+-+--+
  |  ID  |   Status  | Name | Size | Volume 
Type | Bootable | Multiattach | Attached to  |
  
+--+---+--+--+-+--+-+--+
  | 8a3440f7-afbf-4581-95fb-14730fbd98c1 | detaching |  -   |  1   | 
lvmdriver-1 |  false   |False| 6d316dab-426e-48f9-956f-e2f0df1aabcd |
  | cafc833a-8645-47db-b464-999142afa7be | attaching |  -   |  1   | 
lvmdriver-1 |  false   |False|  |
  
+--+---+--+--+-+--+-+--+

  > sudo iscsiadm -m node 
  10.0.2.15:3260,-1 
iqn.2010-10.org.openstack:volume-cafc833a-8645-47db-b464-999142afa7be

  My devstack environments:
  nova (12.0.0.0b3.dev508, /opt/stack/nova)
  python-novaclient (2.26.0)
  cinder (7.0.0.0b3.dev296, /opt/stack/cinder)
  python-cinderclient (1.3.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1489744/+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 1507564] Re: os.path.remove doesn't exist. Conver task fails

[Flavio Percoco]

** Also affects: glance/kilo
   Importance: Undecided
   Status: New

** Changed in: glance/kilo
   Importance: Undecided => Medium

** Changed in: glance/liberty
   Importance: Undecided => Medium

** Changed in: glance/kilo
 Assignee: (unassigned) => Flavio Percoco (flaper87)

** Changed in: glance/liberty
 Assignee: (unassigned) => Flavio Percoco (flaper87)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1507564

Title:
  os.path.remove doesn't exist. Conver task fails

Status in Glance:
  In Progress
Status in Glance kilo series:
  In Progress
Status in Glance liberty series:
  New

Bug description:
File 
"/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", 
line 96, in run
  for _state in self.run_iter():
File 
"/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", 
line 146, in run_iter
  self._change_state(states.FAILURE)
File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, 
in __exit__
  six.reraise(self.type_, self.value, self.tb)
File 
"/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", 
line 130, in run_iter
  failure.Failure.reraise_if_any(failures)
File "/usr/lib/python2.7/site-packages/taskflow/types/failure.py", line 
244, in reraise_if_any
  failures[0].reraise()
File "/usr/lib/python2.7/site-packages/taskflow/types/failure.py", line 
251, in reraise
  six.reraise(*self._exc_info)
File 
"/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/executor.py", 
line 86, in _revert_task
  result = task.revert(**arguments)
File "/usr/lib/python2.7/site-packages/glance/async/flows/convert.py", line 
99, in revert
  os.path.remove(fs_path)
  AttributeError: 'module' object has no attribute 'remove'
  2015-07-11 11:40:00.817 6663 INFO eventlet.wsgi.server 
[req-c4c286ec-2248-4d93-b631-a2270de43ec8 7a6bd2901f0642b18be91d82782ed1ca 
3954f0a8635249eba2eda9a489e233a7 - - -] 10.12.27.41 - - [11/Jul/2015 11:40:00] 
"POST /v2/tasks HTTP/1.1" 500 139

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1507564/+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 1485940] Re: non-admin user get error code "500" if he tries to deactivate the image hosted by admin which have visibility "public"

[Flavio Percoco]

Kilo: https://review.openstack.org/248856
Liberty: https://review.openstack.org/248855

** Also affects: glance/kilo
   Importance: Undecided
   Status: New

** Also affects: glance/liberty
   Importance: Undecided
   Status: New

** Changed in: glance/kilo
   Importance: Undecided => High

** Changed in: glance/liberty
   Importance: Undecided => High

** Changed in: glance/kilo
 Assignee: (unassigned) => Flavio Percoco (flaper87)

** Changed in: glance/liberty
 Assignee: (unassigned) => Flavio Percoco (flaper87)

** Changed in: glance/kilo
   Status: New => In Progress

** Changed in: glance/liberty
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1485940

Title:
  non-admin user  get error code "500"  if he  tries to deactivate the
  image hosted by admin which have visibility "public"

Status in Glance:
  Fix Committed
Status in Glance kilo series:
  In Progress
Status in Glance liberty series:
  In Progress

Bug description:
  Description:
  non-admin user  get error code "500"  if he  tries to deactivate the image 
hosted by admin which have visibility "public" which is not user friendly it 
should raise response 403 forbidden.

  Steps:
  scenario was tested using tempest.
  1. image was uploaded by admin user with visibility "public" using api.
  2. deactivate request was generated by non-admin user using api.
  3. In response header "500" was received.

  Expected:
  1. even if non-admin user is not allowed to deactivate image uploaded by 
admin user having visibility "public", response should contain "403 forbidden" 
to give meaning full information to user that he is not authorized to perform 
this act.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1485940/+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 1350892] Re: Nova VMWare provisioning errors

[Flavio Percoco]

quite old and no feedback

** Changed in: glance-store
   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/1350892

Title:
  Nova VMWare provisioning errors

Status in glance_store:
  Invalid
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  I am trying to provision a RHEL VMWare image (custom vmdk created
  through template)

  Openstack dashboard shows provisioning status for a long time, however
  no activity on vCenter. PS- CirrOS VMDK (Conveterted from qemu-img
  gets deployed with out errors)

  Request help here

  2014-07-31 16:48:44.017 2931 WARNING nova.openstack.common.loopingcall [-] 
task run outlasted interval by 11.98221 sec
  2014-07-31 16:50:27.015 2931 WARNING nova.openstack.common.loopingcall [-] 
task run outlasted interval by 12.987183 sec
  2014-07-31 16:51:57.715 2931 WARNING nova.openstack.common.loopingcall [-] 
task run outlasted interval by 0.696367 sec
  2014-07-31 16:58:32.860 2931 ERROR suds.client [-] 
  http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";>
 

   SessionManager
   5216dd75-609c-3c5a-b7e6-9708bd7dc786
   Administrator

 
  
  2014-07-31 16:58:32.863 2931 WARNING nova.virt.vmwareapi.driver 
[req-e6f5ba33-a37a-476b-a6b6-801ccd80bac6 6b875fcfe8344addb87382298c1a75be 
dad97a29e60849a2a6ad9d0ffb353161] Unable to validate session 
5216dd75-609c-3c5a-b7e6-9708bd7dc786!
  2014-07-31 16:58:32.863 2931 WARNING nova.virt.vmwareapi.driver 
[req-e6f5ba33-a37a-476b-a6b6-801ccd80bac6 6b875fcfe8344addb87382298c1a75be 
dad97a29e60849a2a6ad9d0ffb353161] Session 5216dd75-609c-3c5a-b7e6-9708bd7dc786 
is inactive!
  2014-07-31 16:58:48.406 2931 ERROR suds.client [-] 
  http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";>
 

   SessionManager
   5216dd75-609c-3c5a-b7e6-9708bd7dc786

 
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance-store/+bug/1350892/+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 1519017] Re: nova keypair-list generates ERROR (ClientException): Unexpected API Error.

[Hans Lindgren]

** 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/1519017

Title:
  nova keypair-list generates ERROR (ClientException): Unexpected API
  Error.

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  On executing nova keypair-list, the following error gets generated:

  nova keypair-list
  ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
   (HTTP 500) (Request-ID: 
req-5ff60d4d-67e3-4f2d-9912-fd4dcb833165)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1519017/+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 1519078] [NEW] Freescale vendor code still present in neutron tree

[Henry Gessau]

Public bug reported:

The Freescale service plugin and ML2 mechanism driver should be
completely removed from the neutron tree. All Freescale code and
artifacts should be contained in an external freescale repository.

See http://docs.openstack.org/developer/neutron/devref/contribute.html

** Affects: neutron
 Importance: Medium
 Status: New

** Changed in: neutron
   Importance: Undecided => Medium

** Changed in: neutron
Milestone: None => mitaka-2

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1519078

Title:
  Freescale vendor code still present in neutron tree

Status in neutron:
  New

Bug description:
  The Freescale service plugin and ML2 mechanism driver should be
  completely removed from the neutron tree. All Freescale code and
  artifacts should be contained in an external freescale repository.

  See http://docs.openstack.org/developer/neutron/devref/contribute.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1519078/+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 1516031] Re: Use of MD5 in OpenStack Glance image signature (CVE-2015-8234)

[Tristan Cacqueray]

Since this does not qualify for an OpenStack Security Advisory (OSSA),
I've added an OSSN task to assess if a Security Note would work better
here.

** Also affects: ossn
   Importance: Undecided
   Status: New

** Changed in: ossa
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1516031

Title:
  Use of MD5 in OpenStack Glance image signature (CVE-2015-8234)

Status in Glance:
  Triaged
Status in OpenStack Security Advisory:
  Won't Fix
Status in OpenStack Security Notes:
  New

Bug description:
  This have been reported by Daniel P. Berrange:
  "
  In the OpenStack Liberty release, the Glance project added support for image 
signature verification.

  http://specs.openstack.org/openstack/glance-specs/specs/liberty/image-
  signing-and-verification-support.html

  The verification code was added in the following git commit

  
https://github.com/openstack/glance/commit/484ef1b40b738c87adb203bba6107ddb4b04ff6e

  
  Unfortunately the design of this signature verification method is flawed by 
design.

  The generalized approach to creating signatures of content is to apply
  a hash to the content and then encrypt it in some manner. Consider
  that the signature is defined to use hash=sha256 and cipher=rsa we can
  describe the signature computation as

  signature = rsa(sha256(content))

  In the case of verifying a disk image, the content we care about
  verifying is the complete disk image file. Unfortunately, the glance
  specification chose *not* to compute the signature against the disk
  image file. Glance already had an MD5 checksum calculated for the disk
  image file, so they instead chose to compute the signature against the
  MD5 checksum instead. ie glance is running

  signature = rsa(sha256(md5(disk-image-content)))

  This degrades the security of the system to that of the weakest hash,
  which is obviously MD5 here.

  The code where glance verifies the signature is in the
  glance/locations.py, the 'set_data' method where is does

   result = signature_utils.verify_signature(
   self.context, checksum, self.image.extra_properties)
   if result:
   LOG.info(_LI("Successfully verified signature for image %s"),
   self.image.image_id)

  The 'checksum' variable is populate by the glance_store driver, but it
  is hardcoded to always be md5 in all current glance storage backends:

   $ git grep hashlib glance_store/_drivers/ | grep checksum
   glance_store/_drivers/filesystem.py: checksum = hashlib.md5()
   glance_store/_drivers/rbd.py: checksum = hashlib.md5()
   glance_store/_drivers/s3.py: checksum = hashlib.md5()
   glance_store/_drivers/s3.py: checksum = hashlib.md5()
   glance_store/_drivers/sheepdog.py: checksum = hashlib.md5()
   glance_store/_drivers/swift/store.py: checksum =
   hashlib.md5()
   glance_store/_drivers/vmware_datastore.py: self.checksum =
   hashlib.md5()

  
  Since we will soon be shipping OpenStack Liberty release, we need to at least 
give a security notice to alert our customers to the fact that the signature 
verification is cryptographically weak/broken. IMHO, it quite likely deserves a 
CVE though

  NB, this is public knowledge as I first became aware of this flawed
  design in comments / discussion on a public specification proposed to
  implement the same approach in the Nova project.

  My suggested way to fix this is to simply abandon the current impl and
  re-do it such that it directly computes the signature against  the
  disk image, and does not use the existing md5 checksum in any way.

  Regards,
  Daniel
  "

  Mailing list thread for Nova impl: 
http://lists.openstack.org/pipermail/openstack-dev/2015-November/079348.html
  Nova Spec: https://review.openstack.org/#/c/188874/

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1516031/+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 1480951] Re: List LDAP users returns 500 error code when one of the users' local_id only consists of numbers

[aginwala]

** Changed in: keystone
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1480951

Title:
  List LDAP users returns 500 error code when one of the users' local_id
  only consists of numbers

Status in OpenStack Identity (keystone):
  Invalid

Bug description:
  Listing LDAP users when one of the users' local_id only consists of numbers 
will return an Internal Server Error. 
  Here is the error log:
  {"error": {"message": "An unexpected error prevented the server from 
fulfilling your request: (DataError) invalid input syntax for type numeric: 
\"Administrator\"\n 'SELECT id_mapping.public_id AS id_mapping_public_id 
\\nFROM id_mapping \\nWHERE id_mapping.domain_id = %(domain_id_1)s AND 
id_mapping.local_id = %(local_id_1)s AND id_mapping.entity_type = 
%(entity_type_1)s' {'local_id_1': 123456, 'domain_id_1': 
u'1e5f790eabfc4b84a4a37734aa0602e4', 'entity_type_1': 'user'} (Disable debug 
mode to suppress these details.)", "code": 500, "title": "Internal Server 
Error"}}
  The Exception is thrown in _set_domain_id_and_mapping_for_single_ref() method
  I'm using postgres as the SQL backend

  Steps to reproduce:
  1. configure keystone to enable domain specific drivers and configure one of 
the domains to use LDAP backend.

  2. create an user under the configured user_tree_dn and set the user's
  corresponding user_id_attrbite to consists only of numbers, like
  123456, for example.

  3. list users of this domain using /v3/users?domain_id=$domain_id,
  keystone will return an Internal Server Error with the above error
  message.

  This error occurs when keystone is trying to add an id_mapping entry
  for this user, and it needs to check if it already exists before
  creating it.

  Also, changing an existing user's user_id_attrbite to pure numbers
  triggers this bug.

  The error says that keystone is trying to query an id_mapping record
  where the value of local_id column is a number, and in fact this field
  is VCHAR type.

  I think it may have something to do with data type conversions.

  And as a principle, one bad record should not affect the whole list to
  be unreadable, isn't it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1480951/+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 1489921] Re: Nova connects to rabbitmq successfully but has invalid credentials

[Davanum Srinivas (DIMS)]

** Changed in: oslo.messaging
   Status: Fix Committed => Fix Released

** Changed in: oslo.messaging
Milestone: None => 3.0.0

-- 
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/1489921

Title:
  Nova connects to rabbitmq successfully but has invalid credentials

Status in OpenStack Compute (nova):
  Invalid
Status in oslo.messaging:
  Fix Released

Bug description:
  From rabbitmq log:

  =INFO REPORT 28-Aug-2015::10:54:20 ===
  accepting AMQP connection <0.15664.0> (10.0.2.26:55772 -> 10.0.2.8:5672)

  =INFO REPORT 28-Aug-2015::10:54:20 ===
  Mirrored queue 
'q-agent-notifier-security_group-update_fanout_c8d714e02b944c7f91dad2530a34ff01'
 in vhost '/': Adding mirror on node 'rabbit@os-controller-1003': <7448.19519.0>

  =INFO REPORT 28-Aug-2015::10:54:20 ===
  Mirrored queue 
'q-agent-notifier-dvr-update_fanout_87fb0fc8e8224ffb88ea91ee20ad8e29' in vhost 
'/': Adding mirror on node 'rabbit@os-controller-1002': <7447.3416.0>

  =INFO REPORT 28-Aug-2015::10:54:20 ===
  Mirrored queue 
'q-agent-notifier-dvr-update_fanout_87fb0fc8e8224ffb88ea91ee20ad8e29' in vhost 
'/': Adding mirror on node 'rabbit@os-controller-1003': <7448.19521.0>

  =ERROR REPORT 28-Aug-2015::10:54:20 ===
  closing AMQP connection <0.15305.0> (10.0.2.26:55758 -> 10.0.2.8:5672):
  {handshake_error,starting,0,
   {amqp_error,access_refused,
   "AMQPLAIN login refused: user 'openstack' - 
invalid credentials",
   'connection.start_ok'}}

  =INFO REPORT 28-Aug-2015::10:54:21 ===
  accepting AMQP connection <0.15747.0> (10.0.2.26:55773 -> 10.0.2.8:5672)

  From Nova Log:

  2015-08-28 10:54:19.524 14743 DEBUG oslo_concurrency.lockutils 
[req-91919deb-c6be-42a8-91f6-557f078f7d19 - - - - -] Lock "compute_resources" 
acquired by "_update_available_resource" :: waited 0.000s inner 
/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:444
  2015-08-28 10:54:19.827 14743 INFO nova.compute.resource_tracker 
[req-91919deb-c6be-42a8-91f6-557f078f7d19 - - - - -] Total usable vcpus: 48, 
total allocated vcpus: 1
  2015-08-28 10:54:19.827 14743 INFO nova.compute.resource_tracker 
[req-91919deb-c6be-42a8-91f6-557f078f7d19 - - - - -] Final resource view: 
name=osc-1001.prd.cin1.corp.hosting.net phys_ram=257524MB used_ram=2560MB 
phys_disk=5GB used_disk=20GB total_vcpus=48 used_vcpus=1 
pci_stats=
  2015-08-28 10:54:19.886 14743 INFO nova.scheduler.client.report 
[req-91919deb-c6be-42a8-91f6-557f078f7d19 - - - - -] Compute_service record 
updated for ('osc-1001.prd.cin1.corp.hosting.net', 
'osc-1001.prd.cin1.corp.hosting.net')
  2015-08-28 10:54:19.886 14743 INFO nova.compute.resource_tracker 
[req-91919deb-c6be-42a8-91f6-557f078f7d19 - - - - -] Compute_service record 
updated for 
osc-1001.prd.cin1.corp.hosting.net:osc-1001.prd.cin1.corp.hosting.net
  2015-08-28 10:54:19.887 14743 DEBUG oslo_concurrency.lockutils 
[req-91919deb-c6be-42a8-91f6-557f078f7d19 - - - - -] Lock "compute_resources" 
released by "_update_available_resource" :: held 0.363s inner 
/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:456
  2015-08-28 10:54:19.922 14743 DEBUG nova.service 
[req-91919deb-c6be-42a8-91f6-557f078f7d19 - - - - -] Creating RPC server for 
service compute start /usr/lib/python2.7/site-packages/nova/service.py:188
  2015-08-28 10:54:19.925 14743 INFO oslo_messaging._drivers.impl_rabbit 
[req-91919deb-c6be-42a8-91f6-557f078f7d19 - - - - -] Connecting to AMQP server 
on 10.0.2.8:5672
  2015-08-28 10:54:19.943 14743 INFO oslo_messaging._drivers.impl_rabbit 
[req-91919deb-c6be-42a8-91f6-557f078f7d19 - - - - -] Connected to AMQP server 
on 10.0.2.8:5672
  2015-08-28 10:54:19.969 14743 DEBUG nova.service 
[req-91919deb-c6be-42a8-91f6-557f078f7d19 - - - - -] Join ServiceGroup 
membership for this service compute start 
/usr/lib/python2.7/site-packages/nova/service.py:206
  2015-08-28 10:54:19.969 14743 DEBUG nova.servicegroup.drivers.db 
[req-91919deb-c6be-42a8-91f6-557f078f7d19 - - - - -] DB_Driver: join new 
ServiceGroup member osc-1001.prd.cin1.corp.hosting.net to the compute group, 
service =  join 
/usr/lib/python2.7/site-packages/nova/servicegroup/drivers/db.py:59

  Rabbit configuration in nova.conf
  [oslo_messaging_rabbit]
  rabbit_hosts=10.0.2.8:5672,10.0.2.7:5672,10.0.2.6:5672
  rabbit_userid=openstack
  rabbit_password=placeholderpassword

  Functionality seems fine and nothing shows up in the nova log but
  rabbitmq references this hypervisor and with only the nova openstack
  service running i get the message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1489921/+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/

[Yahoo-eng-team] [Bug 1513630] Re: notifications are not being recevied since mitaka

[Davanum Srinivas (DIMS)]

** Changed in: oslo.messaging
   Status: Fix Committed => Fix Released

** Changed in: oslo.messaging
Milestone: None => 3.0.0

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1513630

Title:
  notifications are not being recevied since mitaka

Status in Astara:
  Invalid
Status in neutron:
  Fix Committed
Status in neutron liberty series:
  In Progress
Status in oslo.messaging:
  Fix Released

Bug description:
  our liberty release was 1 week behind neutron. in that week, we had to
  pin our gate jobs to stable/liberty for other projects because at some
  point since mitaka opened, something changed in neutron that prevents
  events from hitting astara.

  have not yet been able to track down the change but am in the process
  of bisecting now.

  will update this bug with details once i find more

To manage notifications about this bug go to:
https://bugs.launchpad.net/astara/+bug/1513630/+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 1210436] Re: hypervisor status does not update immediately after 'nova delete'

[Stephen Finucane]

I could be wrong, but this seems to be "by design". The Nova API is
asynchronous by design, and requests aren't guaranteed to be handled
immediately.  IRC log from conversation with dansmith included below.

http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-
nova.2015-11-23.log.html#t2015-11-23T20:47:54

 Does Nova have any concept of interrupt- or notification-driven 
tasks?
 I see `periodic_task` used extensively and I'm also aware of the 
'notify_about_instance_usage' and related functions. The latter is 
polling-based though, while the former only seems to issue user-focused messages
 s/latter/former/ s/former/latter/
 sfinucan: confusing
 Sorry
 sfinucan: the notify there is to send a notification about a 
change, which happens when a thing happens, to notify someone like the deployer 
about a change
 periodic tasks happen on a timer to poll for cleanups, etc
 dansmith: OK. So for something like VM creation/deletion, we 
seem to use periodic tasks
 sfinucan: use more words
 OK :)
 sfinucan: vm create/destroy happens because you asked for it via 
the api
 Why do we use periodic tasks to check if VM creation/deletion is 
done?
 sfinucan: in case it fails in the middle and we need to clean it 
up
 dansmith: But this means there's a period of time between when a 
VM is finished being created/deleted and when the user is told it's finished, 
correct?
 Which causes bugs like this 
https://bugs.launchpad.net/nova/+bug/1210436
 sfinucan: no
 dansmith: Oh?
 sfinucan: there is a delay between you asking for it to be 
deleted and it being deleted, but that is not because of a periodic
 sfinucan: that's because most API requests are async.. they 
return immediately and put something on the message queue to be processed
 sfinucan: which is a very fundamental design point of nova 
(since I can feel "why" coming)
 dansmith: Hmm OK that's interesting. So we can say that as soon 
as the VM deletion request is received and completed by Nova, the DB should 
reflect the deletion?
 sfinucan: as soon as it's completed by nova, yeah
 sfinucan: which is not equal to "received"
 dansmith: OK, that's interesting :)
 I think the linked bug can be marked as invalid for this reason 
so I'll do just that. Thanks for the help, dansmith
 sfinucan: yep, probably (having read only the title)


** 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/1210436

Title:
  hypervisor status does not update immediately after 'nova delete'

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Hypervisor status does not update immediately after 'nova delete', after 
about 1min the status is correct. But if we boot instance or live migrate on 
this hyperviosr, it make mistake. 
  Also, I notice that when running command 'nova boot --image 
cirros-0.3.1-x86_64-uec --flavor 1 vm1' every one second, the vm will be on one 
host mostly, because the same reason. Furthermore, after many times 'boot' and 
'delete' the hypervisor status becomes muddled.
  Actually, after 'nova delete' the table compute_nodes will not be updated 
immediately, it also lasts until periodic task. 

  BUT, those should be updated immediately.

  Test steps:
  1. environment, there is a 'vm1' on hypervisor 'ubuntu'
  zhgaoxa@ubuntu:~/src$ nova list
  
+--+--+++-+--+
  | ID   | Name | Status | Task State | Power 
State | Networks |
  
+--+--+++-+--+
  | a439e64e-0d1c-4c23-8cfd-6ab12dc9a209 | vm1  | ACTIVE | None   | Running 
| private=10.0.0.2 |
  
+--+--+++-+--+
  zhgaoxa@ubuntu:~/src$ nova show vm1
  
+--++
  | Property | Value
  |
  
+--++
  | status   | ACTIVE   
  |
  | updated  | 2013-07-18T07:05:29Z 
  |
  | OS-EXT-STS:task_state| None 
  |
  | OS-EXT-SRV-ATTR:host | ubuntu   
  |
  | key_name | None 
  |
  | image  

[Yahoo-eng-team] [Bug 1519112] [NEW] Enabling port_security extension in ML2 won't work for networks created *before* enabling it

[Antonio Messina]

Public bug reported:

Assume you installed neutron without "port_security" extension, and you
already created some network. If you then enable the extension and run:

neutron port-update --port-security-enabled=False 

it will NOT update the port-security-enabled property of the port (but
will not print any error message either), and on the neutron log the
following message is printed:

2015-11-19 11:47:32.148 61810 INFO neutron.plugins.ml2.managers 
[req-cd918215-5740-4087-b4b5-fbd62888af2a ] Extended port dict for driver 'p
ort_security'
2015-11-19 11:47:32.155 61810 INFO neutron.plugins.ml2.managers 
[req-cd918215-5740-4087-b4b5-fbd62888af2a ] Extended port dict for driver 'p
ort_security'
2015-11-19 11:47:32.156 61810 ERROR neutron.plugins.ml2.managers 
[req-cd918215-5740-4087-b4b5-fbd62888af2a ] Extension driver 'port_security' 
failed in process_update_port
2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers Traceback 
(most recent call last):
2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers   File 
"/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/managers.py", line 742, 
in _call_on_ext_drivers
2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers 
getattr(driver.obj, method_name)(plugin_context, data, result)
2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers   File 
"/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/extensions/port_security.py",
 line 59, in process_update_port
2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers context, 
data, result)
2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers   File 
"/usr/lib/python2.7/dist-packages/neutron/db/portsecurity_db_common.py", line 
112, in _process_port_port_security_update
2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers raise 
psec.PortSecurityBindingNotFound()
2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers 
PortSecurityBindingNotFound: Port does not have port security binding.
2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers 
2015-11-19 11:47:32.164 61810 INFO neutron.plugins.ml2.managers 
[req-cd918215-5740-4087-b4b5-fbd62888af2a ] Extended network dict for driver 
'port_security'


My interpretation is that the table neutron.portsecuritybindings does not 
contain rows corresponding to ports created *before* enabling the extesion, and 
the code from 
https://github.com/openstack/neutron/blob/master/neutron/db/portsecurity_db_common.py#L104
 will fail because of this.

Tested on Ubuntu 14.04/Kilo only

** 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/1519112

Title:
  Enabling port_security extension in ML2 won't work for networks
  created *before* enabling it

Status in neutron:
  New

Bug description:
  Assume you installed neutron without "port_security" extension, and
  you already created some network. If you then enable the extension and
  run:

  neutron port-update --port-security-enabled=False 

  it will NOT update the port-security-enabled property of the port (but
  will not print any error message either), and on the neutron log the
  following message is printed:

  2015-11-19 11:47:32.148 61810 INFO neutron.plugins.ml2.managers 
[req-cd918215-5740-4087-b4b5-fbd62888af2a ] Extended port dict for driver 'p
  ort_security'
  2015-11-19 11:47:32.155 61810 INFO neutron.plugins.ml2.managers 
[req-cd918215-5740-4087-b4b5-fbd62888af2a ] Extended port dict for driver 'p
  ort_security'
  2015-11-19 11:47:32.156 61810 ERROR neutron.plugins.ml2.managers 
[req-cd918215-5740-4087-b4b5-fbd62888af2a ] Extension driver 'port_security' 
failed in process_update_port
  2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers Traceback 
(most recent call last):
  2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers   File 
"/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/managers.py", line 742, 
in _call_on_ext_drivers
  2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers 
getattr(driver.obj, method_name)(plugin_context, data, result)
  2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers   File 
"/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/extensions/port_security.py",
 line 59, in process_update_port
  2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers context, 
data, result)
  2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers   File 
"/usr/lib/python2.7/dist-packages/neutron/db/portsecurity_db_common.py", line 
112, in _process_port_port_security_update
  2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers raise 
psec.PortSecurityBindingNotFound()
  2015-11-19 11:47:32.156 61810 TRACE neutron.plugins.ml2.managers 
PortSecurityBindingNotFound: Port does not have port security binding.
  2015-11-19 11

[Yahoo-eng-team] [Bug 1488261] Re: update code so data-selenium is consistently available

[Doug Fish]

On review I'm going to disagree with myself. Not sure this was a good
idea at all - a lot of overhead for a limited number of cases.

** Changed in: horizon
   Status: Confirmed => 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/1488261

Title:
  update code so data-selenium is consistently available

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  while reviewing https://review.openstack.org/#/c/214671/ in patch set
  6, Timur proposed a patch that consistently added the data-selenium
  attribute to table values. I believe this is the right approach and it
  would be nice if all of our integration tests could rely on this value
  being present. However, several unit tests fail after this attribute
  is added.

  This bug is to update the data-selenium -updating code in
  horizon/tables/base.py Cell.__init__ to always add this attribute as
  well as update the related unit tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1488261/+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 1519115] [NEW] [RFE] Add get_subnets in MetadataPluginAPI

[Shih-Hao Li]

Public bug reported:

Add get_subnets function in MetadataPluginAPI so that it can
be used by MetadataProxyHandler or its derived classes to
search subnets.

** Affects: neutron
 Importance: Undecided
 Assignee: Shih-Hao Li (shihli)
 Status: New


** Tags: rfe

** Changed in: neutron
 Assignee: (unassigned) => Shih-Hao Li (shihli)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1519115

Title:
  [RFE] Add get_subnets in MetadataPluginAPI

Status in neutron:
  New

Bug description:
  Add get_subnets function in MetadataPluginAPI so that it can
  be used by MetadataProxyHandler or its derived classes to
  search subnets.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1519115/+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 1519118] [NEW] No way to determine whether contract migrations are pending

[Ihar Hrachyshka]

Public bug reported:

It's needed because depending on that fact operators may need to proceed
with full shutdown of their API services, or may skip such high impact
step in upgrade procedures.

Ansible playbooks for neutron already rely on some hacky way to
determine that: https://github.com/openstack/openstack-
ansible/blob/aa9230b5a5cdf0e7baf57b5fb8fc6e149912b0fa/playbooks/roles/os_neutron/library/neutron_migrations_facts#L162

We should accommodate those users that want to utilize the benefits of
split branches in production with a simple CLI command.

** Affects: neutron
 Importance: Undecided
 Assignee: Ihar Hrachyshka (ihar-hrachyshka)
 Status: In Progress


** Tags: db

** Changed in: neutron
 Assignee: (unassigned) => Ihar Hrachyshka (ihar-hrachyshka)

** Tags added: db

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1519118

Title:
  No way to determine whether contract migrations are pending

Status in neutron:
  In Progress

Bug description:
  It's needed because depending on that fact operators may need to
  proceed with full shutdown of their API services, or may skip such
  high impact step in upgrade procedures.

  Ansible playbooks for neutron already rely on some hacky way to
  determine that: https://github.com/openstack/openstack-
  
ansible/blob/aa9230b5a5cdf0e7baf57b5fb8fc6e149912b0fa/playbooks/roles/os_neutron/library/neutron_migrations_facts#L162

  We should accommodate those users that want to utilize the benefits of
  split branches in production with a simple CLI command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1519118/+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 1513574] Re: firewall rules on DVR FIP fails to work for ingress traffic

[Carl Baldwin]

At this point, given that fwaas is totally up in the air, I don't think
we're going to take on anymore DVR / FWaaS bugs.

** Changed in: neutron
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1513574

Title:
  firewall rules on DVR FIP fails to work for ingress traffic

Status in neutron:
  Won't Fix

Bug description:
  =
  my env
  =
  controller +network node(dvr_snat) + 2 compute nodes(dvr)
  DVR: enable DVR when using devstack to deploy this env
  FWaaS: manually git clone neutron-fwaas and to configure, using iptables as 
driver

  
  
  steps
  
  1) create net, subnet, boot VM-1 on CN-1, VM-2 on CN-2, create router, and 
attach subnet onto router.
  2) create external network, set as router gateway net, create 2 floating IPs 
and associate to two VMs.
  3) confirm DVR FIP works: fip ns created, iptable rules updated in qrouter 
ns, two VMs are pingable by floating IP.
  floating IP like: 192.168.0.4 and 192.168.0.5
  4) create firewall rules, firewall policy and create firewall on router. 
  firewall rule like: 
  fw-r1: ICMP, source: 192.168.0.184/29(none), dest: 192.168.0.0/28(none), 
allow
  fw-r2: ICMP, source: 192.168.0.0/28(none), dest: 192.168.0.184/29(none), 
allow
  5) confirm firewall rules updated in qrouter ns.
  6) on host who has IP like 192.168.0.190, try to ping floating IPs mentioned 
in step 3.
  expected: floating IPs should be pingable (for IP 192.168.0.190 is in 
192.168.0.184/29, and two firewall rules allows)
  observed: no response, "100% packet loss" from ping command. floating IP fail 
to ping.

  
  
  more details
  
  
  firewall iptable rules:
  
  -A INPUT -j neutron-l3-agent-INPUT
  -A FORWARD -j neutron-filter-top
  -A FORWARD -j neutron-l3-agent-FORWARD
  -A OUTPUT -j neutron-filter-top
  -A OUTPUT -j neutron-l3-agent-OUTPUT
  -A neutron-filter-top -j neutron-l3-agent-local
  -A neutron-l3-agent-FORWARD -o rfp-+ -j neutron-l3-agent-iv4322a9b15
  -A neutron-l3-agent-FORWARD -i rfp-+ -j neutron-l3-agent-ov4322a9b15
  -A neutron-l3-agent-FORWARD -o rfp-+ -j neutron-l3-agent-fwaas-defau
  -A neutron-l3-agent-FORWARD -i rfp-+ -j neutron-l3-agent-fwaas-defau
  -A neutron-l3-agent-INPUT -m mark --mark 0x1/0x -j ACCEPT
  -A neutron-l3-agent-INPUT -p tcp -m tcp --dport 9697 -j DROP
  -A neutron-l3-agent-fwaas-defau -j DROP
  -A neutron-l3-agent-iv4322a9b15 -m state --state INVALID -j DROP
  -A neutron-l3-agent-iv4322a9b15 -m state --state RELATED,ESTABLISHED -j ACCEPT
  -A neutron-l3-agent-iv4322a9b15 -s 192.168.0.0/28 -d 192.168.0.184/29 -p icmp 
-j ACCEPT
  -A neutron-l3-agent-iv4322a9b15 -s 192.168.0.184/29 -d 192.168.0.0/28 -p icmp 
-j ACCEPT
  -A neutron-l3-agent-ov4322a9b15 -m state --state INVALID -j DROP
  -A neutron-l3-agent-ov4322a9b15 -m state --state RELATED,ESTABLISHED -j ACCEPT
  -A neutron-l3-agent-ov4322a9b15 -s 192.168.0.0/28 -d 192.168.0.184/29 -p icmp 
-j ACCEPT
  -A neutron-l3-agent-ov4322a9b15 -s 192.168.0.184/29 -d 192.168.0.0/28 -p icmp 
-j ACCEPT

  ---
  DVR FIP nat iptable rules:
  ---
  1) for 192.168.0.4:
  -A PREROUTING -j neutron-l3-agent-PREROUTING
  -A OUTPUT -j neutron-l3-agent-OUTPUT
  -A POSTROUTING -j neutron-l3-agent-POSTROUTING
  -A POSTROUTING -j neutron-postrouting-bottom
  -A neutron-l3-agent-OUTPUT -d 192.168.0.4/32 -j DNAT --to-destination 20.0.1.7
  -A neutron-l3-agent-POSTROUTING ! -i rfp-4bf3186c-d ! -o rfp-4bf3186c-d -m 
conntrack ! --ctstate DNAT -j ACCEPT
  -A neutron-l3-agent-PREROUTING -d 169.254.169.254/32 -i qr-+ -p tcp -m tcp 
--dport 80 -j REDIRECT --to-ports 9697
  -A neutron-l3-agent-PREROUTING -d 192.168.0.4/32 -j DNAT --to-destination 
20.0.1.7
  -A neutron-l3-agent-float-snat -s 20.0.1.7/32 -j SNAT --to-source 192.168.0.4
  -A neutron-l3-agent-snat -j neutron-l3-agent-float-snat
  -A neutron-postrouting-bottom -m comment --comment "Perform source NAT on 
outgoing traffic." -j neutron-l3-agent-snat

  2) for 192.168.0.5:
  -A PREROUTING -j neutron-l3-agent-PREROUTING
  -A OUTPUT -j neutron-l3-agent-OUTPUT
  -A POSTROUTING -j neutron-l3-agent-POSTROUTING
  -A POSTROUTING -j neutron-postrouting-bottom
  -A neutron-l3-agent-OUTPUT -d 192.168.0.5/32 -j DNAT --to-destination 20.0.1.6
  -A neutron-l3-agent-PREROUTING -d 169.254.169.254/32 -i qr-+ -p tcp -m tcp 
--dport 80 -j REDIRECT --to-ports 9697
  -A neutron-l3-agent-PREROUTING -d 192.168.0.5/32 ! -i qr-+ -j DNAT 
--to-destination 20.0.1.6
  -A neutron-l3-agent-float-snat -s 20.0.1.6/32 -j SNAT --to-source 192.168.0.5
  -A neutron-l3-agent-snat -j neutron-l3-agent-float-snat
  -A neutron-postrouting-bottom -m comment --comment "Perform source NAT on 
outgoing traffic." -j neutron-l3-agent-snat

  ---

[Yahoo-eng-team] [Bug 1372141] Re: StaleDataError while updating ml2_dvr_port_bindings

[Armando Migliaccio]

We never merged anything to fix the issue, the issue did come and go; as
of now it's not there...so I'd rather mark it invalid.

** Changed in: neutron
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1372141

Title:
  StaleDataError while updating ml2_dvr_port_bindings

Status in neutron:
  Invalid

Bug description:
  This stacktrace has been observed for a while:

  http://logs.openstack.org/17/120917/5/experimental/check-tempest-dsvm-
  neutron-
  dvr/960bdbb/logs/screen-q-svc.txt.gz?level=TRACE#_2014-09-16_19_06_14_290

  The logstash query is here:

  
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiU3RhbGVEYXRhRXJyb3IgVVBEQVRFIHN0YXRlbWVudCBvbiB0YWJsZSAnbWwyX2R2cl9wb3J0X2JpbmRpbmdzJ1wiIEFORCBtZXNzYWdlOlwiaW4gdXBkYXRlX2R2cl9wb3J0X2JpbmRpbmdcIiBBTkQgZmlsZW5hbWU6XCJsb2dzL3NjcmVlbi1xLXN2Yy50eHRcIiBBTkQgYnVpbGRfYnJhbmNoOlwibWFzdGVyXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJmcm9tIjoiMjAxNC0wOS0xNlQxOTowMzozMSswMDowMCIsInRvIjoiMjAxNC0wOS0xNlQxOTowNzoyMSswMDowMCIsInVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQxMTU4OTY1OTE2NywibW9kZSI6IiIsImFuYWx5emVfZmllbGQiOiIifQ==

  However, we need to establish if fix for bug #1371696 struck two birds
  with one stone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1372141/+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 1515360] Re: Add more verbose to Tempest Test Errors that causes "SSHTimeout" seen in CVR and DVR

[Armando Migliaccio]

I think the objective here is to add probes with the intention of
removing them, not sure if it's worthwhile tracking this a bug, the
patch will have to be reverted later on.

** Changed in: neutron
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1515360

Title:
  Add more verbose to Tempest Test Errors that causes "SSHTimeout" seen
  in CVR and DVR

Status in neutron:
  Invalid

Bug description:
  Today "SSHTimeout" Errors are seen both in CVR ( Centralized Virtual Routers) 
and DVR ( Distributed Virtual Routers).
  The frequency of occurence is more on DVR than the CVR.

  But the problem here, is the error statement that is returned and the data 
that is dumped.
  SSHTimeout may have occured due to several reasons, since in all our tempest 
test we are trying to ssh to the VM using the public IP ( FloatingIP) 
  1. VM did not come up
  2. VM does not have a private IP address
  3. Security rules in the VM was not applied properly
  4. Setting up of Floating IP
  5. DNAT rules in the Router Namespace.
  6. Scheduling.
  7. Namespace Errors etc.,

  
  We need a way to identify through the tempest test exactly were and what went 
wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1515360/+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 1519160] [NEW] unit test intermittent failure

[Armando Migliaccio]

Public bug reported:

An example:

http://logs.openstack.org/98/248498/3/gate/gate-neutron-
python27/e2b5fd2/testr_results.html.gz

The logstash query:

http://logstash.openstack.org/#dashboard/file/logstash.json?query=message:%5C%22test_failing_async_process_handle_error_once%5C%22

** Affects: neutron
 Importance: Undecided
 Status: Confirmed


** Tags: gate-failure unittest

** Changed in: neutron
   Status: New => Confirmed

** Tags added: gate-failure

** Tags added: unittest

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1519160

Title:
  unit test intermittent failure

Status in neutron:
  Confirmed

Bug description:
  An example:

  http://logs.openstack.org/98/248498/3/gate/gate-neutron-
  python27/e2b5fd2/testr_results.html.gz

  The logstash query:

  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message:%5C%22test_failing_async_process_handle_error_once%5C%22

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1519160/+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 1519164] [NEW] numa_topology does not get populated for compute_nodes table

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I am running Liberty on RHEL 7.2. When I request via flavor any numa
related attributes, instance fails to launch as NUMA filter cannot find
host with requested resources available.

When I checked nova database, compute_nodes table, I noticed numa_topoly
has no information.

use nova;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
MariaDB [nova]> SELECT numa_topology FROM compute_nodes;
+---+
| numa_topology |
+---+
| NULL  |
+---+
1 row in set (0.01 sec)

It supposed to return numa related information.

Here is the version of nova rpms I am running on this server:

openstack-nova-conductor-12.0.0-1.el7.noarch
python-novaclient-2.30.1-1.el7.noarch
openstack-nova-console-12.0.0-1.el7.noarch
openstack-nova-common-12.0.0-1.el7.noarch
openstack-nova-scheduler-12.0.0-1.el7.noarch
openstack-nova-compute-12.0.0-1.el7.noarch
python-nova-12.0.0-1.el7.noarch
openstack-nova-novncproxy-12.0.0-1.el7.noarch
openstack-nova-api-12.0.0-1.el7.noarch
openstack-nova-cert-12.0.0-1.el7.noarch

Please let me know what additional information required.

Thank you

Serguei

** Affects: nova
 Importance: Undecided
 Status: New

-- 
numa_topology does not get populated for compute_nodes table
https://bugs.launchpad.net/bugs/1519164
You received this bug notification because you are a member of Yahoo! 
Engineering Team, which is subscribed to OpenStack Compute (nova).

-- 
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 1519164] [NEW] numa_topology does not get populated for compute_nodes table

[Serguei Bezverkhi]

Public bug reported:

I am running Liberty on RHEL 7.2. When I request via flavor any numa
related attributes, instance fails to launch as NUMA filter cannot find
host with requested resources available.

When I checked nova database, compute_nodes table, I noticed numa_topoly
has no information.

use nova;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
MariaDB [nova]> SELECT numa_topology FROM compute_nodes;
+---+
| numa_topology |
+---+
| NULL  |
+---+
1 row in set (0.01 sec)

It supposed to return numa related information.

Here is the version of nova rpms I am running on this server:

openstack-nova-conductor-12.0.0-1.el7.noarch
python-novaclient-2.30.1-1.el7.noarch
openstack-nova-console-12.0.0-1.el7.noarch
openstack-nova-common-12.0.0-1.el7.noarch
openstack-nova-scheduler-12.0.0-1.el7.noarch
openstack-nova-compute-12.0.0-1.el7.noarch
python-nova-12.0.0-1.el7.noarch
openstack-nova-novncproxy-12.0.0-1.el7.noarch
openstack-nova-api-12.0.0-1.el7.noarch
openstack-nova-cert-12.0.0-1.el7.noarch

Please let me know what additional information required.

Thank you

Serguei

** Affects: nova
 Importance: Undecided
 Status: New

** Project changed: tripleo => 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/1519164

Title:
  numa_topology does not get populated for compute_nodes table

Status in OpenStack Compute (nova):
  New

Bug description:
  I am running Liberty on RHEL 7.2. When I request via flavor any numa
  related attributes, instance fails to launch as NUMA filter cannot
  find host with requested resources available.

  When I checked nova database, compute_nodes table, I noticed
  numa_topoly has no information.

  use nova;
  Reading table information for completion of table and column names
  You can turn off this feature to get a quicker startup with -A

  Database changed
  MariaDB [nova]> SELECT numa_topology FROM compute_nodes;
  +---+
  | numa_topology |
  +---+
  | NULL  |
  +---+
  1 row in set (0.01 sec)

  It supposed to return numa related information.

  Here is the version of nova rpms I am running on this server:

  openstack-nova-conductor-12.0.0-1.el7.noarch
  python-novaclient-2.30.1-1.el7.noarch
  openstack-nova-console-12.0.0-1.el7.noarch
  openstack-nova-common-12.0.0-1.el7.noarch
  openstack-nova-scheduler-12.0.0-1.el7.noarch
  openstack-nova-compute-12.0.0-1.el7.noarch
  python-nova-12.0.0-1.el7.noarch
  openstack-nova-novncproxy-12.0.0-1.el7.noarch
  openstack-nova-api-12.0.0-1.el7.noarch
  openstack-nova-cert-12.0.0-1.el7.noarch

  Please let me know what additional information required.

  Thank you

  Serguei

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1519164/+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 1519171] [NEW] model-migration check fails to detect integer-biginteger mismatch

[Henry Gessau]

Public bug reported:

See
https://review.openstack.org/#/c/222079/15/neutron/db/migration/alembic_migrations/versions/mitaka/expand/32e5974ada25_add_neutron_resources_table.py

Kevin had Integer in the model and BigInteger in the migration.
This should be detected by _TestModelsMigrations().

** Affects: neutron
 Importance: Medium
 Status: New


** Tags: db functional-tests

** Changed in: neutron
   Importance: Undecided => Medium

** Tags added: db

** Tags added: functional-tests

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1519171

Title:
  model-migration check fails to detect integer-biginteger mismatch

Status in neutron:
  New

Bug description:
  See
  
https://review.openstack.org/#/c/222079/15/neutron/db/migration/alembic_migrations/versions/mitaka/expand/32e5974ada25_add_neutron_resources_table.py

  Kevin had Integer in the model and BigInteger in the migration.
  This should be detected by _TestModelsMigrations().

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1519171/+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 1416179] Re: Missing API to get list of provider network types

[Armando Migliaccio]

Unless we provide a mechanism to dynamically modify the list of provider
networks, returning them does not make much sense, as it's hard-coded.

** Changed in: neutron
   Status: Confirmed => Incomplete

** Changed in: neutron
 Assignee: Sreekumar S (sreesiv) => (unassigned)

** Changed in: python-neutronclient
   Status: Invalid => Incomplete

** Changed in: python-neutronclient
 Assignee: Sreekumar S (sreesiv) => (unassigned)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1416179

Title:
  Missing API to get list of provider network types

Status in neutron:
  Incomplete
Status in python-neutronclient:
  Incomplete

Bug description:
  There is currently no way to get the list of available provider
  network types from Neutron. The list may vary based on which plugin is
  used. Allowing clients to query for this list will remove having to
  hardcode the types in clients such as Horizon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1416179/+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 1369854] Re: min_disk and size information wrong when creating an instance image

[wangxiyuan]

** Changed in: glance
 Assignee: wangxiyuan (wangxiyuan) => (unassigned)

** Changed in: glance
   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/1369854

Title:
  min_disk and size information wrong when creating an instance image

Status in Glance:
  Invalid
Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  If I launch an instance from an image that has min_disk set to 2GB,
  then create an image from the instance, the min_disk attribute is not
  set correctly on the image (it's set to 0). Instead of being set as an
  attribute, it exists as a property instead. This can cause issues when
  other services rely on min_disk to make decisions about size (e.g. bug
  1368600 for Horizon, not sure if Cinder is affected too).

  This doesn't seem to happen when creating a basic instance from an
  instance, only when there is also a volume involved.

  I'm not sure if this is a nova or glance issue so I'm opening a task
  on both for now.

  Steps to reproduce
  
  (done on a recent devstack)

  1. Create a new image with e.g. min_disk 2GB
  $ glance image-create --name mindisk2gb --disk-format qcow2 
--container-format bare --location 
https://launchpad.net/cirros/trunk/0.3.0/+download/cirros-0.3.0-i386-disk.img 
--min-disk 2
  +--+--+
  | Property | Value|
  +--+--+
  | checksum | None |
  | container_format | bare |
  | created_at   | 2014-09-16T12:35:33  |
  | deleted  | False|
  | deleted_at   | None |
  | disk_format  | qcow2|
  | id   | 9bbed3a5-00bf-4901-855e-556ca02e7fb7 |
  | is_public| False|
  | min_disk | 2|  <-- min_disk 
set as expected
  | min_ram  | 0|
  | name | mindisk2gb   |
  | owner| eb6acc49df4b4390a99c722ded526284 |
  | protected| False|
  | size | 9159168  |  <-- size 
looks ok
  | status   | active   |
  | updated_at   | 2014-09-16T12:35:37  |
  | virtual_size | None |
  +--+--+

  2. Boot an instance from this image, backed by a volume (I believe this 
matches what happens when launching with "Image (creates a new volume)" in 
Horizon)
  $ nova boot --flavor 4115a835-04f0-4457-b93c-1817bc44812c --block-device 
device='/dev/vda',source='image',dest='volume',id='9bbed3a5-00bf-4901-855e-556ca02e7fb7',size=2,bootindex=0
 my_instance 
  
+--+--+
  | Property | Value
|
  
+--+--+
  | OS-DCF:diskConfig| MANUAL   
|
  | OS-EXT-AZ:availability_zone  | nova 
|
  | OS-EXT-STS:power_state   | 0
|
  | OS-EXT-STS:task_state| -
|
  | OS-EXT-STS:vm_state  | building 
|
  | OS-SRV-USG:launched_at   | -
|
  | OS-SRV-USG:terminated_at | -
|
  | accessIPv4   |  
|
  | accessIPv6   |  
|
  | adminPass| Uo2DL64GaY74 
|
  | config_drive |  
|
  | created  | 2014-09-16T12:55:30Z 
|
  | flavor   | m1.lowmem 
(4115a835-04f0-4457-b93c-1817bc44812c) |
  | hostId   |  
|
  | id   | 3e70fd2e-1dc6-4001-941e-9496a9514882 
|
  | image| Attempt to boot from volume - no 
image supplied  |
  | key_name 

[Yahoo-eng-team] [Bug 1492274] Re: nova evacuate does not update instance's neutron port location in the DB

[Launchpad Bug Tracker]

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
   Status: Incomplete => Expired

-- 
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/1492274

Title:
  nova evacuate does not update instance's neutron port location in the
  DB

Status in OpenStack Compute (nova):
  Expired

Bug description:

  nova evacuate and nova host-evacuate doesn't update the database with
  the new neutron port location after the instance has successfully
  evacuate.

  The instance's neutron port is created on the right compute node and
  the neutron port is created correctly using openvswitch. The instance
  doesn't lose connectivity.

  Everything is fine with migrate/live-migration/host-live-migration


  To reproduce:
  shutdown a compute node and execute a nova evacuate or a nova host-evacuate.

  
  Expected Result:
  neutron port-show  show the neutron port are updated with the new 
neutron port location 

  
  Actual Result:
  neutron port-show  still show the previous compute node

  
  Version used :
  ii  nova-api 1:2015.1.0-0ubuntu1.1~cloud0 
 all  OpenStack Compute - API frontend
  ii  nova-cert1:2015.1.0-0ubuntu1.1~cloud0 
 all  OpenStack Compute - certificate management
  ii  nova-common  1:2015.1.0-0ubuntu1.1~cloud0 
 all  OpenStack Compute - common files
  ii  nova-conductor   1:2015.1.0-0ubuntu1.1~cloud0 
 all  OpenStack Compute - conductor service
  ii  nova-novncproxy  1:2015.1.0-0ubuntu1.1~cloud0 
 all  OpenStack Compute - NoVNC proxy
  ii  nova-scheduler   1:2015.1.0-0ubuntu1.1~cloud0 
 all  OpenStack Compute - virtual machine scheduler
  ii  python-nova  1:2015.1.0-0ubuntu1.1~cloud0 
 all  OpenStack Compute Python libraries
  ii  python-novaclient1:2.22.0-0ubuntu1~cloud0 
 all  client library for OpenStack Compute API

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1492274/+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 1519210] [NEW] opt-out of certain notifications

[Steve Martinelli]

Public bug reported:

keystone currently support a lot of event notifications, just see
http://docs.openstack.org/developer/keystone/event_notifications.html

It would be nice if there was a configuration option to allow users to
opt-out of notifications they didn't care about.

This could be as simple as:

[notifications]
listen_group_create = True
listen_group_delete = True
listen_group_update = True
...
listen_authenticate_success = True

Or something more advanced.

Either way, each would have to be set to True by default.

** Affects: keystone
 Importance: Wishlist
 Status: New

** Changed in: keystone
   Importance: Undecided => Wishlist

** Summary changed:

- opt-out of notifications
+ opt-out of certain notifications

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1519210

Title:
  opt-out of certain notifications

Status in OpenStack Identity (keystone):
  New

Bug description:
  keystone currently support a lot of event notifications, just see
  http://docs.openstack.org/developer/keystone/event_notifications.html

  It would be nice if there was a configuration option to allow users to
  opt-out of notifications they didn't care about.

  This could be as simple as:

  [notifications]
  listen_group_create = True
  listen_group_delete = True
  listen_group_update = True
  ...
  listen_authenticate_success = True

  Or something more advanced.

  Either way, each would have to be set to True by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1519210/+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 1420104] Re: quota set failed

[Steve Martinelli]

*** This bug is a duplicate of bug 1475831 ***
https://bugs.launchpad.net/bugs/1475831

** This bug has been marked a duplicate of bug 1475831
   Some compute quotas are not being set

-- 
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/1420104

Title:
  quota set failed

Status in OpenStack Identity (keystone):
  Invalid
Status in OpenStack Compute (nova):
  Invalid
Status in python-openstackclient:
  In Progress

Bug description:
  1: source file:
  export NOVA_VERSION=1.1
  export no_proxy=$no_proxy, [overcloud_ip]
  export OS_PASSWORD=redhat
  export OS_TENANT_ID=86c0d2458dbb4adc990bab70ef3546f5
  export OS_PROJECT_ID=86c0d2458dbb4adc990bab70ef3546f5
  export OS_AUTH_URL=https://[overcloud_ip]:5000/v3
  export OS_USER_DOMAIN_ID=9a03881b62ca449f87f8d5a1ceaad845
  export OS_USERNAME=testuser_dx_px
  export COMPUTE_API_VERSION=1.1
  export OS_NO_CACHE=True
  export OS_IDENTITY_API_VERSION=3
  export OS_CACERT=/usr/local/share/ca-certificates/ephemeralca-cacert.crt
  PS2=$PS1
  export PS1=($OS_USERNAME)$PS1
  export OS_PS1=$PS2

  2: testuser_dx_px  was created via v3 keystone API as below:
  (admin)cetest@cer106n*:~/lily$ openstack domain create test_domain
  +-+--+
  | Field   | Value|
  +-+--+
  | enabled | True |
  | id  | 9a03881b62ca449f87f8d5a1ceaad845 |
  | name| test_domain  |
  +-+--+
  (admin)cetest@cer106n*:~/lily$ openstack project create --domain test_domain 
--description "test project" --enable te   stproject_dx
  +-+--+
  | Field   | Value|
  +-+--+
  | description | test project |
  | domain_id   | 9a03881b62ca449f87f8d5a1ceaad845 |
  | enabled | True |
  | id  | 86c0d2458dbb4adc990bab70ef3546f5 |
  | name| testproject_dx   |
  +-+--+
  (admin)cetest@cer106n*:~/lily$ openstack user create --password redhat 
--email testuser_dx...@hp.com --project testproject_dx --domai   n test_domain 
--description "user in test_domain and testproject_dx." --enable testuser_dx_px
  ++-+
  | Field  | Value   |
  ++-+
  | default_project_id | 86c0d2458dbb4adc990bab70ef3546f5|
  | description| user in test_domain and testproject_dx. |
  | domain_id  | 9a03881b62ca449f87f8d5a1ceaad845|
  | email  | testuser_dx...@hp.com   |
  | enabled| True|
  | id | ddf3e092104b4f47bbf25dc39342159c|
  | name   | testuser_dx_px  |
  ++-+

  
  3: project quota set failed[openstackclient cmd]
  
(testuser_dx_px)(testuser_dx_px)root@overcloud-ce-controller-controller1-gcf3ewgvxb4l:~#
 openstack --version
  openstack 0.4.1
  
(testuser_dx_px)(testuser_dx_px)root@overcloud-ce-controller-controller1-gcf3ewgvxb4l:~#
 openstack quota show testproject_dx
  +--++
  | Field| Value  |
  +--++
  | backup_gigabytes | 1000   |
  | backups  | 10 |
  | cores| -1 |
  | fixed-ips| -1 |
  | floating-ips | 10 |
  | gigabytes| 1000   |
  | injected-file-size   | 10240  |
  | injected-files   | 5  |
  | injected-path-size   | 255|
  | instances| 40 |
  | key-pairs| 100|
  | project  | testproject_dx |
  | properties   | 50 |
  | ram  | 16000  |
  | secgroup-rules   | 20 |
  | secgroups| 10 |
  | server_group_members | 10 |
  | server_groups| 10 |
  | snapshots| 10 |
  | volumes  | 10 |
  +--++
  
(testuser_dx_px)(testuser_dx_px)root@overcloud-ce-controller-controller1-gcf3ewgvxb4l:~#
 openstack quota set --ram 15360 testproject_dx
  ERROR: openstack Bad Request (HTTP 400) (Request-ID: 
req-29f562c4-8cf0-4e2f-97f0-d4a11bf16ebf)
  
(testuser_dx_px)(testuser_dx_px)root@overcloud-ce-controller-controller1-gcf3ewgvxb4l:~#
 openstack quota show testproject_dx
  +--+--

[Yahoo-eng-team] [Bug 1519223] [NEW] Freescale FWaaS Plugin code decomposition

[Trinath Somanchi]

Public bug reported:

The Freescale FwaaS service plugin should be completely removed from the
neutron-fwaas tree.

All Freescale code and artifacts should be contained in an external
freescale repository.

See http://docs.openstack.org/developer/neutron/devref/contribute.html

** Affects: neutron
 Importance: Undecided
 Assignee: Trinath Somanchi (trinath-somanchi)
 Status: In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1519223

Title:
  Freescale FWaaS Plugin code decomposition

Status in neutron:
  In Progress

Bug description:
  The Freescale FwaaS service plugin should be completely removed from
  the neutron-fwaas tree.

  All Freescale code and artifacts should be contained in an external
  freescale repository.

  See http://docs.openstack.org/developer/neutron/devref/contribute.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1519223/+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 1368661] Re: Unit tests sometimes fail because of stale pyc files

[Adrian Otto]

** Changed in: python-magnumclient
   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/1368661

Title:
  Unit tests sometimes fail because of stale pyc files

Status in Ironic:
  Fix Released
Status in Magnum:
  Fix Committed
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) icehouse series:
  Fix Released
Status in python-magnumclient:
  Fix Released
Status in python-troveclient:
  Fix Committed
Status in Trove:
  Fix Committed

Bug description:
  Because python creates pyc files during tox runs, certain changes in
  the tree, like deletes of files, or switching branches, can create
  spurious errors. This can be suppressed by PYTHONDONTWRITEBYTECODE=1
  in the tox.ini.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ironic/+bug/1368661/+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