[Yahoo-eng-team] [Bug 1711038] [NEW] Fail to add subnet to router if this subnet already add to a router

2017-08-15 Thread wei.ying 
Public bug reported:

Env: devstack master branch

If a subnet is connected by a router, the subnet can not be connected by
other routers, and if it is connected to other routers, the following
error will be prompted.

Error: Failed to add interface: IP address 10.0.0.193 already allocated
in subnet 719ca9f3-00e3-4c1a-bf74-3e7a67c4c319 Neutron server returns
request_ids: ['req-ed305303-4330-49e0-9ccf-e7fca4b36210']

** Affects: horizon
 Importance: Undecided
 Assignee: wei.ying (wei.yy)
 Status: New

** Changed in: horizon
 Assignee: (unassigned) => wei.ying (wei.yy)

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

Title:
  Fail to add subnet to router if this subnet already add to a router

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Env: devstack master branch

  If a subnet is connected by a router, the subnet can not be connected
  by other routers, and if it is connected to other routers, the
  following error will be prompted.

  Error: Failed to add interface: IP address 10.0.0.193 already
  allocated in subnet 719ca9f3-00e3-4c1a-bf74-3e7a67c4c319 Neutron
  server returns request_ids: ['req-ed305303-4330-49e0-9ccf-
  e7fca4b36210']

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1711038/+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 1573479] Re: Users email can not delete by updating user

2017-08-15 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/492286
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=a9517ff6151be22a4aa5dccd8389b358f591a92b
Submitter: Jenkins
Branch:master

commit a9517ff6151be22a4aa5dccd8389b358f591a92b
Author: Lucas H. Xu 
Date:   Wed Aug 9 16:30:46 2017 -0400

Fix cannot delete user's email addresses in the identity/user panel

How to reproduce the bug:

P.S. Using the horizon master(pike) codebase

1) Login as an admin user
2) Click Identity and go to the Users panel
3) Create a user and put an email address with that user
4) Then edit this user to clear the email address.
5) Update the user and even though we have a green  banner(successful)
show up, the email address still viewable and do not disappear.

Closes Bug: #1573479

Change-Id: I0273d0c6d885c77f1f74bdc2ae6674d1e6539ac0


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

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

Title:
  Users email can not delete by updating user

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Environment:  Kilo build

  Steps:
  1) Login using admin
  2) Click Identity -> Users
  3)  Create a user with email address input.
  4) Then edit this user to let the email para as empty which want to remove 
original email .
  5) But after this update, the email address still exist. 

  Expected Result: Email address should be removed by this update action

  Also tried with the keystone command, it can successfully remove the
  email:

  1. Create user with an email using Identity API v2: 
  # keystone --os-identity-api-version 2.0 user-create --name testv2 --email 
tes...@ibm.com
  /usr/lib/python2.7/site-packages/keystoneclient/shell.py:65: 
DeprecationWarning: The keystone CLI is deprecated in favor of 
python-openstackclient. For a Python library, continue using 
python-keystoneclient.
'python-keystoneclient.', DeprecationWarning)
  +--+--+
  | Property |  Value   |
  +--+--+
  |  email   |  tes...@ibm.com  |
  | enabled  |   True   |
  |id| 6cde253f2e4c474993d78a70e21886ab |
  |   name   |  testv2  |
  | username |  testv2  |
  +--+--+

  2. Update user to remove the email using Identity API v2: 
  # keystone --os-identity-api-version 2.0 user-update --name testv2new --email 
"" testv2
  /usr/lib/python2.7/site-packages/keystoneclient/shell.py:65: 
DeprecationWarning: The keystone CLI is deprecated in favor of 
python-openstackclient. For a Python library, continue using 
python-keystoneclient.
'python-keystoneclient.', DeprecationWarning)
  User has been updated.

  Then run command to verify, the email address has been removed.
  # keystone --os-identity-api-version 2.0 user-get testv2new
  /usr/lib/python2.7/site-packages/keystoneclient/shell.py:65: 
DeprecationWarning: The keystone CLI is deprecated in favor of 
python-openstackclient. For a Python library, continue using 
python-keystoneclient.
'python-keystoneclient.', DeprecationWarning)
  +--+--+
  | Property |  Value   |
  +--+--+
  |  email   |  |
  | enabled  |   True   |
  |id| 6cde253f2e4c474993d78a70e21886ab |
  |   name   |testv2new |
  | username |testv2new |
  +--+--+

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1573479/+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 1702211] Re: test_password_history_not_enforced_in_admin_reset failed in tempest test

2017-08-15 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/493259
Committed: 
https://git.openstack.org/cgit/openstack/keystone/commit/?id=38974af24c47a6c26bb627250657a4d9ed5aa881
Submitter: Jenkins
Branch:master

commit 38974af24c47a6c26bb627250657a4d9ed5aa881
Author: Morgan Fainberg 
Date:   Fri Aug 11 14:56:30 2017 -0700

Add int storage of datetime for password created/expires

Due to MySQL (in some versions) not storing datetime resolution below
one second, keystone occasionally ends up with weird behavior such as
a New password not being valid. The password created at and expires at
columns now store both datetime (for rolling upgrades) and integers.

Keystone from Pike and beyond leans on the new created_at_int column
and expires_at_int column.

Change-Id: I2c219b4b9b353f1e2cce6088849a773196f0e443
Closes-Bug: #1702211


** Changed in: keystone
   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/1702211

Title:
  test_password_history_not_enforced_in_admin_reset failed in tempest
  test

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  http://logs.openstack.org/95/479995/1/check/gate-tempest-dsvm-neutron-
  full-ubuntu-xenial/181701f/logs/testr_results.html.gz

  ft1.3: 
tempest.api.identity.admin.v3.test_users.UsersV3TestJSON.test_password_history_not_enforced_in_admin_reset[id-568cd46c-ee6c-4ab4-a33a-d3791931979e]_StringException:
 pythonlogging:'': {{{
  2017-07-04 02:14:33,998 23518 INFO [tempest.lib.common.rest_client] 
Request (UsersV3TestJSON:test_password_history_not_enforced_in_admin_reset): 
200 PATCH https://10.0.1.201/identity/v3/users/e70a98d099b145f4bd39637a6ebc5ff0 
0.092s
  2017-07-04 02:14:33,998 23518 DEBUG[tempest.lib.common.rest_client] 
Request - Headers: {'Content-Type': 'application/json', 'Accept': 
'application/json', 'X-Auth-Token': ''}
  Body: {"user": {"password": "A1^PtkD~Pd1e@3P", "id": 
"e70a98d099b145f4bd39637a6ebc5ff0"}}
  Response - Headers: {u'x-openstack-request-id': 
'req-c629cb49-12f9-4970-9cb7-00f749f1d67d', u'content-type': 
'application/json', u'vary': 'X-Auth-Token', u'content-length': '502', 
u'server': 'Apache/2.4.18 (Ubuntu)', u'date': 'Tue, 04 Jul 2017 02:14:33 GMT', 
u'connection': 'close', 'content-location': 
'https://10.0.1.201/identity/v3/users/e70a98d099b145f4bd39637a6ebc5ff0', 
'status': '200'}
  Body: {"user": {"name": "tempest-UsersV3TestJSON-46658028", "links": 
{"self": 
"https://10.0.1.201/identity/v3/users/e70a98d099b145f4bd39637a6ebc5ff0"}, 
"extra": {"project_id": "48606d02759440688de7759ffe09cf86", "email": 
"tempest-usersv3testjson-1943043...@example.com"}, "domain_id": "default", 
"enabled": true, "options": {}, "id": "e70a98d099b145f4bd39637a6ebc5ff0", 
"project_id": "48606d02759440688de7759ffe09cf86", "email": 
"tempest-usersv3testjson-1943043...@example.com", "password_expires_at": null}}
  2017-07-04 02:14:34,099 23518 INFO [tempest.lib.common.rest_client] 
Request (UsersV3TestJSON:test_password_history_not_enforced_in_admin_reset): 
201 POST https://10.0.1.201/identity/v3/auth/tokens
  2017-07-04 02:14:34,099 23518 DEBUG[tempest.lib.common.rest_client] 
Request - Headers: {'Content-Type': 'application/json', 'Accept': 
'application/json'}
  Body: 
  Response - Headers: {u'x-openstack-request-id': 
'req-93ea6008-f665-463d-bdb0-49ea225dad42', u'content-type': 
'application/json', u'vary': 'X-Auth-Token', u'content-length': '339', 
u'server': 'Apache/2.4.18 (Ubuntu)', u'date': 'Tue, 04 Jul 2017 02:14:34 GMT', 
u'x-subject-token': '', u'connection': 'close', 'content-location': 
'https://10.0.1.201/identity/v3/auth/tokens', 'status': '201'}
  Body: {"token": {"issued_at": "2017-07-04T02:14:34.00Z", 
"audit_ids": ["PZ9Yvi0CRaOVnaiAnBlEbg"], "methods": ["password"], "expires_at": 
"2017-07-04T03:14:34.00Z", "user": {"password_expires_at": null, "domain": 
{"id": "default", "name": "Default"}, "id": "e70a98d099b145f4bd39637a6ebc5ff0", 
"name": "tempest-UsersV3TestJSON-46658028"}}}
  2017-07-04 02:14:34,240 23518 INFO [tempest.lib.common.rest_client] 
Request (UsersV3TestJSON:test_password_history_not_enforced_in_admin_reset): 
200 PATCH https://10.0.1.201/identity/v3/users/e70a98d099b145f4bd39637a6ebc5ff0 
0.140s
  2017-07-04 02:14:34,241 23518 DEBUG[tempest.lib.common.rest_client] 
Request - Headers: {'Content-Type': 'application/json', 'Accept': 
'application/json', 'X-Auth-Token': ''}
  Body: {"user": {"password": "A1^PtkD~Pd1e@3P", "id": 
"e70a98d099b145f4bd39637a6ebc5ff0"}}
  Response - Headers: {u'x-openstack-request-id': 
'req-f48d7c79-c625-4fc9-94fd-7e448a5c5e61', u'content-type': 
'application/json', u'vary': 'X-Auth-Token', u'content-length': '502', 
u'server': 'Apache/2.4.18 (Ubuntu)',

[Yahoo-eng-team] [Bug 1392035] Re: case sensitivity inconsistency when doing user get and user create

2017-08-15 Thread Launchpad Bug Tracker 
[Expired for tripleo because there has been no activity for 60 days.]

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

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

Title:
  case sensitivity inconsistency when doing user get and user create

Status in OpenStack Identity (keystone):
  Won't Fix
Status in tripleo:
  Expired

Bug description:
  (openstack) user show stevenk
  ERROR: openstack No user with a name or ID of 'stevenk' exists.
  (openstack) 
  (openstack) 
  (openstack) user create stevenk
  ERROR: openstack Conflict occurred attempting to store user - Duplicate Entry 
(HTTP 409)

  create failed because there is a user called StevenK
  user list
  | cab307b5740a414cb43017536454cbb5 | StevenK|

  
  I think there should be consistency in handling get and create. either case 
sensitive or case insensitive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1392035/+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 1479172] Re: Add unit tests for libvirt fibrechannel/iser/iscsi/aoe volume drivers after os-brick

2017-08-15 Thread 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/1479172

Title:
  Add unit tests for libvirt fibrechannel/iser/iscsi/aoe volume drivers
  after os-brick

Status in OpenStack Compute (nova):
  Expired

Bug description:
  With change https://review.openstack.org/#/c/175569/ we lost some unit
  test coverage of connect_volume/disconnect_volume/get_config methods
  in the libvirt iscsi/fibrechannel/iser/aoe volume drivers, since the
  actual low-level parts of those are now handled in os-brick but we
  still need to unit test the calls to os-brick in nova.

  I've made comments in https://review.openstack.org/#/c/175569/ where
  there were things that didn't have test coverage after the change.
  Some of the other comments are handled in the refactor series here:

  
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp
  /consolidate-libvirt-fs-volume-drivers,n,z

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1479172/+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 1698046] Re: Add support for ingress bandwidth limit rules in ovs agent

2017-08-15 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/492035
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=1908829ace1867c5df9f56ba6302aa56ac09e136
Submitter: Jenkins
Branch:master

commit 1908829ace1867c5df9f56ba6302aa56ac09e136
Author: Rodolfo Alonso Hernandez 
Date:   Wed Aug 9 09:33:35 2017 +0100

Add documentation for Linux Bridge and OVS ingress QoS

Added documentation reference for ingress bandwith limit QoS rule
for Open vSwitch and Linux Bridge backends.

Change-Id: I605b941efe661621298e703ee9f8ea0c1938135f
Closes-Bug: #1699802
Closes-Bug: #1698046


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

Title:
  Add support for ingress bandwidth limit rules in ovs agent

Status in neutron:
  Fix Released

Bug description:
  https://review.openstack.org/457816
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit 2d0d1a2d76c3383bd1e2d14e8860824d843f5047
  Author: Sławek Kapłoński 
  Date:   Wed Apr 19 00:40:38 2017 +0200

  Add support for ingress bandwidth limit rules in ovs agent
  
  Add support for QoS ingress bandwidth limiting in
  openvswitch agent.
  It uses default ovs QoS policies on bandwidth limiting
  mechanism.
  
  DocImpact: Ingress bandwidth limit in QoS supported by
 Openvswitch agent
  
  Change-Id: I9d94e27db5d574b61061689dc99f12f095625ca0
  Partial-Bug: #1560961

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1698046/+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 1699802] Re: Ingress bandwidth limit rule in Linuxbridge agent

2017-08-15 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/492035
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=1908829ace1867c5df9f56ba6302aa56ac09e136
Submitter: Jenkins
Branch:master

commit 1908829ace1867c5df9f56ba6302aa56ac09e136
Author: Rodolfo Alonso Hernandez 
Date:   Wed Aug 9 09:33:35 2017 +0100

Add documentation for Linux Bridge and OVS ingress QoS

Added documentation reference for ingress bandwith limit QoS rule
for Open vSwitch and Linux Bridge backends.

Change-Id: I605b941efe661621298e703ee9f8ea0c1938135f
Closes-Bug: #1699802
Closes-Bug: #1698046


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

Title:
  Ingress bandwidth limit rule in Linuxbridge agent

Status in neutron:
  Fix Released

Bug description:
  https://review.openstack.org/475584
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit da646496e3a48d78c13a015b56c187ce9ac9b5ef
  Author: Sławek Kapłoński 
  Date:   Mon Jun 19 22:13:37 2017 +

  Ingress bandwidth limit rule in Linuxbridge agent
  
  Add support for QoS ingress bandwidth limiting in
  linuxbridge agent.
  It uses traffic shaping done by tc with tbf qdisc.
  
  DocImpact: Ingress bandwidth limit in QoS supported by
 Linuxbridge agent
  
  Change-Id: Id495b302d31f5527db3e45b51517bc53153e7fc2
  Partial-Bug: #1560961

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1699802/+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 1711018] [NEW] glanceclient chokes on task-list, task schema needs update

2017-08-15 Thread Brian Rosmaita 
Public bug reported:

$ glance task-list
u'api_image_import' is not one of [u'import']

Failed validating u'enum' in schema[u'properties'][u'type']:
{u'description': u'The type of task represented by this content',
 u'enum': [u'import'],
 u'type': u'string'}

On instance[u'type']:
u'api_image_import'


The GET /v2/tasks call works via the API.  The problem is that the glanceclient 
is using the tasks schema to validate the response, so this does need to be 
fixed on the API side.

** Affects: glance
 Importance: High
 Assignee: Brian Rosmaita (brian-rosmaita)
 Status: Triaged

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

Title:
  glanceclient chokes on task-list, task schema needs update

Status in Glance:
  Triaged

Bug description:
  $ glance task-list
  u'api_image_import' is not one of [u'import']

  Failed validating u'enum' in schema[u'properties'][u'type']:
  {u'description': u'The type of task represented by this content',
   u'enum': [u'import'],
   u'type': u'string'}

  On instance[u'type']:
  u'api_image_import'

  
  The GET /v2/tasks call works via the API.  The problem is that the 
glanceclient is using the tasks schema to validate the response, so this does 
need to be fixed on the API side.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1711018/+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 1710994] [NEW] arm64 - cannot convert image to raw

2017-08-15 Thread Andrew McLeod 
Public bug reported:

Deploying xenial-ocata on arm64 - during instance creation nova reports
the following error:

fault| {"message": "Build of instance 
3460a1bc-72ac-4d43-a232-d150161c2447 aborted: Image 
b81b08c8-2487-4fea-b39a-d9b07b75b2f0 is unacceptable: Unable to convert image 
to raw: Image 
/var/lib/nova/instances/_base/43dbc7beed2459ae424c6b889caf7854f26321e5.part is 
unacceptable: ", "code": 500, "details": "  File 
\"/usr/lib/python2.7/dist-packages/nova/compute/manager.py\", line 1785, in 
_do_build_and_run_instance |
|  | filter_properties) 




   |
|  |   File 
\"/usr/lib/python2.7/dist-packages/nova/compute/manager.py\", line 2007, in 
_build_and_run_instance 



   |

Further investigation of nova-compute logs reveals:

Unable to convert image to raw: Unexpected error while running command.
Command: qemu-img convert -t none -O raw -f qcow2 
/var/lib/nova/instances/_base/f8488b6e96eb7e752a6d2aa046a8de693c06a5fd.part 
/var/lib/nova/instances/_base/f8488b6e96eb7e752a6d2aa046a8de693c06a5fd.converted
Exit code: 1
Stdout: u''
Stderr: u"qemu-img: file system may not support O_DIRECT\nqemu-img: Could not 
open 
'/var/lib/nova/instances/_base/f8488b6e96eb7e752a6d2aa046a8de693c06a5fd.converted':
 Could not open 
'/var/lib/nova/instances/_base/f8488b6e96eb7e752a6d2aa046a8de693c06a5fd.converted':
 Invalid argument\n"

Full log:

https://pastebin.canonical.com/195965/

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: aarch64 nova ocata osci xenial

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

Title:
  arm64 - cannot convert image to raw

Status in OpenStack Compute (nova):
  New

Bug description:
  Deploying xenial-ocata on arm64 - during instance creation nova
  reports the following error:

  fault| {"message": "Build of instance 
3460a1bc-72ac-4d43-a232-d150161c2447 aborted: Image 
b81b08c8-2487-4fea-b39a-d9b07b75b2f0 is unacceptable: Unable to convert image 
to raw: Image 
/var/lib/nova/instances/_base/43dbc7beed2459ae424c6b889caf7854f26321e5.part is 
unacceptable: ", "code": 500, "details": "  File 
\"/usr/lib/python2.7/dist-packages/nova/compute/manager.py\", line 1785, in 
_do_build_and_run_instance |
  |  | filter_properties)   




 |
  |  |   File 
\"/usr/lib/python2.7/dist-packages/nova/compute/manager.py\", line 2007, in 
_build_and_run_instance 



   |

  Further investigation of nova-compute logs reveals:

  Unable to convert image to raw: Unexpected error while running command.
  Command: qemu-img convert -t none -O raw -f qcow2 
/var/lib/nova/instances/_base/f8488b6e96eb7e752a6d2aa046a8de693c06a5fd.part 
/var/lib/nova/instances/_base/f8488b6e96eb7e752a6d2aa046a8de693c06a5fd.converted
  Exit code: 1
  Stdout: u''
  Stderr: u"qemu-img: file system may not support O_DIRECT\nqemu-img: Could not 
open 
'/var/lib/nova/instances/_base/f8488b6e96eb7e752a6d2aa046a8de693c06a5fd.converted':
 Could not open 
'/var/lib/nova/instances/_base/f8488b6e96eb7e752a6d2aa046a8de693c06a5fd.converted':
 Invalid argument\n"

  Full log:

  https://pastebin.canonical.com/195965/

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1710994/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe :

[Yahoo-eng-team] [Bug 1709869] Re: test_convert_default_subnetpool_to_non_default fails: Subnet pool could not be found

2017-08-15 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/492522
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=34ad023ea3b00ed876e9c5b1a4f19ee56f7f89b7
Submitter: Jenkins
Branch:master

commit 34ad023ea3b00ed876e9c5b1a4f19ee56f7f89b7
Author: Itzik Brown 
Date:   Thu Aug 10 15:44:18 2017 +0300

Fixing test_convert_default_subnetpool_to_non_default

Susbnetpool is created by admin but the show command
is using non-admin client.

Change-Id: I4cac1b87c03053255ed298d4423ea672e60b410d
Closes-bug: #1709869


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

Title:
  test_convert_default_subnetpool_to_non_default fails: Subnet pool
  could not be found

Status in neutron:
  Fix Released

Bug description:
  Running test_convert_default_subnetpool_to_non_default it fails with
  the following error:

  Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/tempest/test.py", line 122, in 
wrapper
  return func(*func_args, **func_kwargs)
File 
"/usr/lib/python2.7/site-packages/neutron/tests/tempest/api/test_subnetpools.py",
 line 392, in test_convert_default_subnetpool_to_non_default
  show_body = self.client.show_subnetpool(subnetpool_id)
File 
"/usr/lib/python2.7/site-packages/neutron/tests/tempest/services/network/json/network_client.py",
 line 136, in _show
  resp, body = self.get(uri)
File "/usr/lib/python2.7/site-packages/tempest/lib/common/rest_client.py", 
line 285, in get
  return self.request('GET', url, extra_headers, headers)
File "/usr/lib/python2.7/site-packages/tempest/lib/common/rest_client.py", 
line 659, in request
  self._error_checker(resp, resp_body)
File "/usr/lib/python2.7/site-packages/tempest/lib/common/rest_client.py", 
line 765, in _error_checker
  raise exceptions.NotFound(resp_body, resp=resp)
  tempest.lib.exceptions.NotFound: Object not found
  Details: {u'message': u'Subnet pool 428fbe89-0282-4587-a59b-be3957d5c701 
could not be found.', u'type': u'SubnetPoolNotFound', u'detail': u''}

  Version
  ===
  Pike
  python-neutron-tests-11.0.0-0.20170804190459.el7ost.noarch

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1709869/+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 1710064] Re: agent logs filled with log noise after sinkhole patch

2017-08-15 Thread OpenStack Infra 
*** This bug is a duplicate of bug 1709625 ***
https://bugs.launchpad.net/bugs/1709625

Reviewed:  https://review.openstack.org/492801
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=e0a26029043401e80fbbcc603c01371866ef28d2
Submitter: Jenkins
Branch:master

commit e0a26029043401e80fbbcc603c01371866ef28d2
Author: Kevin Benton 
Date:   Thu Aug 10 21:58:22 2017 -0700

Add a target to Sinkhole so it's compatible

This prevents oslo messaging dispatch from trying
to treat the receiver function as a target. When it
thought it was a target it was referencing attributes
it didn't have.

Closes-Bug: #1710064
Change-Id: I1832a05f23cd76c1732d3b98539988bc9519d79e


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

Title:
  agent logs filled with log noise after sinkhole patch

Status in neutron:
  Fix Released

Bug description:
  Aug 11 03:23:30.735163 ubuntu-xenial-rax-ord-10386499 
neutron-openvswitch-agent[19463]: ERROR oslo_messaging.rpc.server Traceback 
(most recent call last):
  Aug 11 03:23:30.735305 ubuntu-xenial-rax-ord-10386499 
neutron-openvswitch-agent[19463]: ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/rpc/server.py", line 
160, in _process_incoming
  Aug 11 03:23:30.735418 ubuntu-xenial-rax-ord-10386499 
neutron-openvswitch-agent[19463]: ERROR oslo_messaging.rpc.server res = 
self.dispatcher.dispatch(message)
  Aug 11 03:23:30.735525 ubuntu-xenial-rax-ord-10386499 
neutron-openvswitch-agent[19463]: ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
207, in dispatch
  Aug 11 03:23:30.735632 ubuntu-xenial-rax-ord-10386499 
neutron-openvswitch-agent[19463]: ERROR oslo_messaging.rpc.server if not 
(self._is_namespace(target, namespace) and
  Aug 11 03:23:30.735739 ubuntu-xenial-rax-ord-10386499 
neutron-openvswitch-agent[19463]: ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
170, in _is_namespace
  Aug 11 03:23:30.735853 ubuntu-xenial-rax-ord-10386499 
neutron-openvswitch-agent[19463]: ERROR oslo_messaging.rpc.server return 
namespace in target.accepted_namespaces
  Aug 11 03:23:30.735960 ubuntu-xenial-rax-ord-10386499 
neutron-openvswitch-agent[19463]: ERROR oslo_messaging.rpc.server 
AttributeError: 'function' object has no attribute

  
  
http://logs.openstack.org/55/491555/5/check/gate-tempest-dsvm-py35-ubuntu-xenial/72551bb/logs/screen-q-agt.txt.gz?level=TRACE#_Aug_11_03_18_16_310607

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1710064/+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 1710984] [NEW] Wrong nova.server_list handling for several tabs

2017-08-15 Thread Oleksii 
Public bug reported:

Tabs /projects/volumes, /project/floating_ips/ and some other have wrong 
handling for api.nova.server_list, e.g.
/usr/share/openstack-dashboard/openstack_dashboard/dashboards/project/volumes/tabs.py:
instances, has_more = 
api.nova.server_list(self.request,search_opts=search_opts,detailed=False)
meanwhile it returns 3 values:
ValueError: 'too many values to unpack'
(Pdb) api.nova.server_list(self.request,search_opts=search_opts,detailed=False)
([http://10.101.0.46:8774/v2.1/09ded4150fb84f96a44cbf91e203d4e1/servers/26c2173c-322d-4944-a286-5cb7078cd411',
 u'rel': u'self'}, {u'href': 
u'http://10.101.0.46:8774/09ded4150fb84f96a44cbf91e203d4e1/servers/26c2173c-322d-4944-a286-5cb7078cd411',
 u'rel': u'bookmark'}], 'name': u'test2'}>, http://10.101.0.46:8774/v2.1/09ded4150fb84f96a44cbf91e203d4e1/servers/99d5e094-e1a8-4657-9c63-b689347b7366',
 u'rel': u'self'}, {u'href': 
u'http://10.101.0.46:8774/09ded4150fb84f96a44cbf91e203d4e1/servers/99d5e094-e1a8-4657-9c63-b689347b7366',
 u'rel': u'bookmark'}], 'name': u'test'}>], False, False)

Error in horizon for /projects/volumes doesn't give any idea about the
problem ("Error: Unable to retrieve volume/instance attachment
information").

Please note, that other tabs has correct handling:
/usr/share/openstack-dashboard/openstack_dashboard/dashboards/project/network_topology/views.py:
servers, more, __ = api.nova.server_list(request)

** Affects: horizon
 Importance: Undecided
 Status: New

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

Title:
  Wrong nova.server_list handling for several tabs

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Tabs /projects/volumes, /project/floating_ips/ and some other have wrong 
handling for api.nova.server_list, e.g.
  
/usr/share/openstack-dashboard/openstack_dashboard/dashboards/project/volumes/tabs.py:
instances, has_more = 
api.nova.server_list(self.request,search_opts=search_opts,detailed=False)
  meanwhile it returns 3 values:
  ValueError: 'too many values to unpack'
  (Pdb) 
api.nova.server_list(self.request,search_opts=search_opts,detailed=False)
  ([http://10.101.0.46:8774/v2.1/09ded4150fb84f96a44cbf91e203d4e1/servers/26c2173c-322d-4944-a286-5cb7078cd411',
 u'rel': u'self'}, {u'href': 
u'http://10.101.0.46:8774/09ded4150fb84f96a44cbf91e203d4e1/servers/26c2173c-322d-4944-a286-5cb7078cd411',
 u'rel': u'bookmark'}], 'name': u'test2'}>, http://10.101.0.46:8774/v2.1/09ded4150fb84f96a44cbf91e203d4e1/servers/99d5e094-e1a8-4657-9c63-b689347b7366',
 u'rel': u'self'}, {u'href': 
u'http://10.101.0.46:8774/09ded4150fb84f96a44cbf91e203d4e1/servers/99d5e094-e1a8-4657-9c63-b689347b7366',
 u'rel': u'bookmark'}], 'name': u'test'}>], False, False)

  Error in horizon for /projects/volumes doesn't give any idea about the
  problem ("Error: Unable to retrieve volume/instance attachment
  information").

  Please note, that other tabs has correct handling:
  
/usr/share/openstack-dashboard/openstack_dashboard/dashboards/project/network_topology/views.py:
servers, more, __ = api.nova.server_list(request)

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1710984/+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 1709788] Re: AllocationCandidates return duplicated allocation requests when no sharing rp

2017-08-15 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/492395
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=2e5f293f13e8f38e8cb6b4b58bd69d04eb808b9e
Submitter: Jenkins
Branch:master

commit 2e5f293f13e8f38e8cb6b4b58bd69d04eb808b9e
Author: He Jie Xu 
Date:   Thu Aug 10 14:49:29 2017 +0800

placement: avoid returning duplicated alloc_reqs when no sharing rp

This patch returns from the loop early where there are no sharing
rps, avoiding generating duplicated requests.

Change-Id: I7c73b720f09bb2371770b1c6de537bb5527785a9
Closes-Bug: #1709788


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

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

Title:
  AllocationCandidates return duplicated allocation requests when no
  sharing rp

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  The case is: computenode1 and comptuenode3 share the storage from
  sharedstrorage1, computenode3 has local disk. The expected result from
  AllocationCandidates is (computenode1, sharedstorage1), (computenode2,
  sharedstorage1) and (computenode3). But the current return is
  (computenode1, sharedstorage1), (computenode2, sharedstorage1),
  (computenode3) and (computenode3), a duplicated (computenodes)
  returned.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1709788/+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 1710509] Re: ServerMovingTests.test_evacuate sometimes fails but not always

2017-08-15 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/493448
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=548e93c4b45df05bb0352cc3ef6554d0f65870bd
Submitter: Jenkins
Branch:master

commit 548e93c4b45df05bb0352cc3ef6554d0f65870bd
Author: jichenjc 
Date:   Tue Aug 15 01:16:16 2017 +0800

Avoid race in test_evacuate

We want the host to be the destination and the status to be active so
use _wait_for_server_parameter to wait on both of those, rather than
waiting only for the server to change to ACTIVE.

Without this, we sometimes see the server go ACTIVE but the host has
not yet changed.

Co-Authored-By: Balazs Gibizer 
Co-Authored-By: Chris Dent 
Change-Id: I273998ebc03f3a832cc44787a5c2396da58e5e25
Closes-Bug: 1710509


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

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

Title:
  ServerMovingTests.test_evacuate sometimes fails but not always

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  The newly added test_evacuate test in ServerMovingTests is lightly
  racey. It seems to fail about 1 in 10 times. A recent failure is at
  http://logs.openstack.org/72/489772/2/gate/gate-nova-tox-functional-
  py35-ubuntu-xenial/07f4a29/console.html#_2017-08-12_12_51_52_867765

  Will look into this more closely tomorrow when I've got time, and add
  elastic recheck entry etc, but wanted to get it written down.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1710509/+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 1710958] [NEW] glance image stage fails with 500

2017-08-15 Thread Brian Rosmaita 
Public bug reported:

Returns a 500 when enable_image_import=False.  Should probably return a
404.

** Affects: glance
 Importance: High
 Assignee: Brian Rosmaita (brian-rosmaita)
 Status: Triaged

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

Title:
  glance image stage fails with 500

Status in Glance:
  Triaged

Bug description:
  Returns a 500 when enable_image_import=False.  Should probably return
  a 404.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1710958/+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 1710932] Re: Doesn't configure landscape client on py3

2017-08-15 Thread Chad Smith 
Updated decription and re-opened. Rharper found that it's a py3 issue. I
manually validated this works in py2.7.

http://paste.ubuntu.com/25320461/

** Summary changed:

- Doesn't configure landscape client
+ Doesn't configure landscape client on py3

** Description changed:

- ubuntu@withkvm:/var/log$ cat cloud-init.log | grep landscape
- 2017-08-15 17:17:28,660 - stages.py[DEBUG]: Running module landscape () with 
frequency once-per-instance
- 2017-08-15 17:17:28,660 - handlers.py[DEBUG]: start: 
modules-final/config-landscape: running config-landscape with frequency 
once-per-instance
- 2017-08-15 17:17:28,664 - util.py[DEBUG]: Writing to 
/var/lib/cloud/instances/yar6cr/sem/config_landscape - wb: [420] 25 bytes
- 2017-08-15 17:17:28,665 - helpers.py[DEBUG]: Running config-landscape using 
lock ()
- 2017-08-15 17:17:28,665 - handlers.py[DEBUG]: finish: 
modules-final/config-landscape: SUCCESS: config-landscape ran successfully
+ Attempting to configure landscape-client on a py3 system falls over due
+ to string/byte-string conversion issues
  
- ubuntu@withkvm:/var/log$ cat /etc/cloud/cloud.cfg.d/99_landscape_client 
+ Here's a sample run from MAAS:
+ 
+ 2017-08-15 17:58:11,883 - util.py[DEBUG]: Running module landscape () failed
+ Traceback (most recent call last):
+   File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 793, in 
_run_modules
+ freq=freq)
+   File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
+ return self._runners.run(name, functor, args, freq, clear_on_fail)
+   File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
+ results = functor(*args)
+   File "/usr/lib/python3/dist-packages/cloudinit/config/cc_landscape.py", 
line 113, in handle
+ merged.write(contents)
+   File "/usr/lib/python3/dist-packages/configobj.py", line 2126, in write
+ outfile.write(output_bytes)
+ TypeError: string argument expected, got 'bytes'
+ 
+ 
+ ubuntu@withkvm:/etc/landscape$ cat 
/etc/cloud/cloud.cfg.d/99_landscape_client.cfg 
  landscape:
client:
  url: "https://192.168.122.1/message-system;
  ping_url: "http://192.168.122.1/ping;
  data_path: "/var/lib/landscape/client"
  #http_proxy: "http://my.proxy.com/foobar;
  tags: "maas"
  computer_title: withkvm
  #https_proxy: fooproxy
  registration_key: test
  account_name: standalone
  
- ubuntu@withkvm:/var/log$ dpkg -l | grep landscape-client
- ubuntu@withkvm:/var/log$ cat /etc/landscape/client.conf
- cat: /etc/landscape/client.conf: No such file or directory
+ 
+ Ryan validated py3 falling over just on basic ConfigObj.write() attempts:
+ (foudres) ~ % python3
+ Python 3.5.2 (default, Nov 17 2016, 17:05:23) 
+ [GCC 5.4.0 20160609] on linux
+ Type "help", "copyright", "credits" or "license" for more information.
+ >>> import confi
+ KeyboardInterrupt
+ >>> from configobj import ConfigObj
+ >>> from six import StringIO
+ >>> contents = StringIO()
+ >>> merged = cfg = ConfigObj({})
+ >>> merged
+ ConfigObj({})
+ >>> cfg.merge({'a': 1})
+ >>> cfg
+ ConfigObj({'a': 1})
+ >>> type(contents)
+ 
+ >>> merged.write(contents)
+ Traceback (most recent call last):
+   File "", line 1, in 
+   File "/usr/lib/python3/dist-packages/configobj.py", line 2126, in write
+ outfile.write(output_bytes)
+ TypeError: string argument expected, got 'bytes'

** Description changed:

  Attempting to configure landscape-client on a py3 system falls over due
  to string/byte-string conversion issues
  
  Here's a sample run from MAAS:
  
  2017-08-15 17:58:11,883 - util.py[DEBUG]: Running module landscape () failed
  Traceback (most recent call last):
-   File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 793, in 
_run_modules
- freq=freq)
-   File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
- return self._runners.run(name, functor, args, freq, clear_on_fail)
-   File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
- results = functor(*args)
-   File "/usr/lib/python3/dist-packages/cloudinit/config/cc_landscape.py", 
line 113, in handle
- merged.write(contents)
-   File "/usr/lib/python3/dist-packages/configobj.py", line 2126, in write
- outfile.write(output_bytes)
+   File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 793, in 
_run_modules
+ freq=freq)
+   File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
+ return self._runners.run(name, functor, args, freq, clear_on_fail)
+   File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
+ results = functor(*args)
+   File "/usr/lib/python3/dist-packages/cloudinit/config/cc_landscape.py", 
line 113, in handle
+ merged.write(contents)
+   File "/usr/lib/python3/dist-packages/configobj.py", line 2126, in write
+ outfile.write(output_bytes)
  TypeError: string argument expected, got 'bytes'
  
- 
- ubuntu@withkvm:/etc/landscape$ cat

[Yahoo-eng-team] [Bug 1710932] Re: Doesn't configure landscape client

2017-08-15 Thread Ryan Harper 
You've an error in your cloud-config file

ubuntu@withkvm:/var/log$ cat /etc/cloud/cloud.cfg.d/99_landscape_client

cloud-config files need a .cfg extension to be read.

If I use your landscape config this way, I see landscape-client
installed and file written.

% cat landscape.yaml 
#cloud-config
landscape:
  client:
url: "https://192.168.122.1/message-system;
ping_url: "http://192.168.122.1/ping;
data_path: "/var/lib/landscape/client"
#http_proxy: "http://my.proxy.com/foobar;
tags: "maas"
computer_title: withkvm
#https_proxy: fooproxy
registration_key: test
account_name: standalone

% lxc launch ubuntu-daily:artful --config=user.user-data="$(cat
landscape.yaml)"

# wait a bit for install to complete

% lxc exec measured-hyena -- dpkg --list | grep landscape
ii  landscape-client   16.03-0ubuntu3   
 amd64The Landscape administration system client
ii  landscape-common   16.03-0ubuntu3   
 amd64The Landscape administration system client - Common files

it appears to be working fine.  If you feel there's still a bug, please
re-open.


** Changed in: cloud-init
   Status: New => Invalid

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

Title:
  Doesn't configure landscape client

Status in cloud-init:
  Invalid

Bug description:
  ubuntu@withkvm:/var/log$ cat cloud-init.log | grep landscape
  2017-08-15 17:17:28,660 - stages.py[DEBUG]: Running module landscape () with 
frequency once-per-instance
  2017-08-15 17:17:28,660 - handlers.py[DEBUG]: start: 
modules-final/config-landscape: running config-landscape with frequency 
once-per-instance
  2017-08-15 17:17:28,664 - util.py[DEBUG]: Writing to 
/var/lib/cloud/instances/yar6cr/sem/config_landscape - wb: [420] 25 bytes
  2017-08-15 17:17:28,665 - helpers.py[DEBUG]: Running config-landscape using 
lock ()
  2017-08-15 17:17:28,665 - handlers.py[DEBUG]: finish: 
modules-final/config-landscape: SUCCESS: config-landscape ran successfully

  ubuntu@withkvm:/var/log$ cat /etc/cloud/cloud.cfg.d/99_landscape_client 
  landscape:
client:
  url: "https://192.168.122.1/message-system;
  ping_url: "http://192.168.122.1/ping;
  data_path: "/var/lib/landscape/client"
  #http_proxy: "http://my.proxy.com/foobar;
  tags: "maas"
  computer_title: withkvm
  #https_proxy: fooproxy
  registration_key: test
  account_name: standalone

  ubuntu@withkvm:/var/log$ dpkg -l | grep landscape-client
  ubuntu@withkvm:/var/log$ cat /etc/landscape/client.conf
  cat: /etc/landscape/client.conf: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1710932/+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 1710932] [NEW] Doesn't configure landscape client

2017-08-15 Thread Andres Rodriguez 
Public bug reported:

ubuntu@withkvm:/var/log$ cat cloud-init.log | grep landscape
2017-08-15 17:17:28,660 - stages.py[DEBUG]: Running module landscape () with 
frequency once-per-instance
2017-08-15 17:17:28,660 - handlers.py[DEBUG]: start: 
modules-final/config-landscape: running config-landscape with frequency 
once-per-instance
2017-08-15 17:17:28,664 - util.py[DEBUG]: Writing to 
/var/lib/cloud/instances/yar6cr/sem/config_landscape - wb: [420] 25 bytes
2017-08-15 17:17:28,665 - helpers.py[DEBUG]: Running config-landscape using 
lock ()
2017-08-15 17:17:28,665 - handlers.py[DEBUG]: finish: 
modules-final/config-landscape: SUCCESS: config-landscape ran successfully

ubuntu@withkvm:/var/log$ cat /etc/cloud/cloud.cfg.d/99_landscape_client 
landscape:
  client:
url: "https://192.168.122.1/message-system;
ping_url: "http://192.168.122.1/ping;
data_path: "/var/lib/landscape/client"
#http_proxy: "http://my.proxy.com/foobar;
tags: "maas"
computer_title: withkvm
#https_proxy: fooproxy
registration_key: test
account_name: standalone

ubuntu@withkvm:/var/log$ dpkg -l | grep landscape-client
ubuntu@withkvm:/var/log$ cat /etc/landscape/client.conf
cat: /etc/landscape/client.conf: No such file or directory

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

Title:
  Doesn't configure landscape client

Status in cloud-init:
  New

Bug description:
  ubuntu@withkvm:/var/log$ cat cloud-init.log | grep landscape
  2017-08-15 17:17:28,660 - stages.py[DEBUG]: Running module landscape () with 
frequency once-per-instance
  2017-08-15 17:17:28,660 - handlers.py[DEBUG]: start: 
modules-final/config-landscape: running config-landscape with frequency 
once-per-instance
  2017-08-15 17:17:28,664 - util.py[DEBUG]: Writing to 
/var/lib/cloud/instances/yar6cr/sem/config_landscape - wb: [420] 25 bytes
  2017-08-15 17:17:28,665 - helpers.py[DEBUG]: Running config-landscape using 
lock ()
  2017-08-15 17:17:28,665 - handlers.py[DEBUG]: finish: 
modules-final/config-landscape: SUCCESS: config-landscape ran successfully

  ubuntu@withkvm:/var/log$ cat /etc/cloud/cloud.cfg.d/99_landscape_client 
  landscape:
client:
  url: "https://192.168.122.1/message-system;
  ping_url: "http://192.168.122.1/ping;
  data_path: "/var/lib/landscape/client"
  #http_proxy: "http://my.proxy.com/foobar;
  tags: "maas"
  computer_title: withkvm
  #https_proxy: fooproxy
  registration_key: test
  account_name: standalone

  ubuntu@withkvm:/var/log$ dpkg -l | grep landscape-client
  ubuntu@withkvm:/var/log$ cat /etc/landscape/client.conf
  cat: /etc/landscape/client.conf: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1710932/+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 1710908] [NEW] scheduler.utils.merge_resources allows zero value resources

2017-08-15 Thread Chris Dent 
Public bug reported:

(master as of 2017-08-15)

If the merge of two resources of the same class can result in a sum of
zero, or one of the provided keys has a value of zero in the first place
and it is only in one of the provided resource dicts, the result dict of
resources will have a zero value entry. If this is then used directly to
produce an allocations entry, the allocation will fail.

I discovered this while manually testing resizes of servers using
flavors with no disk.

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: resource-tracker scheduler

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

Title:
  scheduler.utils.merge_resources allows zero value resources

Status in OpenStack Compute (nova):
  New

Bug description:
  (master as of 2017-08-15)

  If the merge of two resources of the same class can result in a sum of
  zero, or one of the provided keys has a value of zero in the first
  place and it is only in one of the provided resource dicts, the result
  dict of resources will have a zero value entry. If this is then used
  directly to produce an allocations entry, the allocation will fail.

  I discovered this while manually testing resizes of servers using
  flavors with no disk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1710908/+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 1708676] Re: juju doesn't surface cloud-init failures

2017-08-15 Thread Nicholas Skaggs 
** Also 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/1708676

Title:
  juju doesn't surface cloud-init failures

Status in cloud-init:
  New
Status in juju:
  Triaged

Bug description:
  This bug is similar to bug 1644566, though the underlying reason
  doesn't seem to be the same. On a fresh artful (this seems to affect
  at least zesty also) instance, I am unable to bootstrap a new lxd
  container. I have tried purging config and reinstalling lxd and juju
  from deb and snaps to various degress with no luck. The end result is
  juju stuck waiting at Attempting to connect to 10.249.132.39:22. See
  attached log. This is with lxd 2.16 and juju 2.2.2 or 2.3-alpah1.

  
  $ lxc list
  
+---+-+--+--++---+
  | NAME  |  STATE  | IPV4 | IPV6 |TYPE| 
SNAPSHOTS |
  
+---+-+--+--++---+
  | juju-759e30-0 | RUNNING | 10.249.132.39 (eth0) |  | PERSISTENT | 0  
   |
  
+---+-+--+--++---+
  $ lxc network list
  ++--+-+-+-+
  |  NAME  |   TYPE   | MANAGED | DESCRIPTION | USED BY |
  ++--+-+-+-+
  | eno1   | physical | NO  | | 0   |
  ++--+-+-+-+
  | lxdbr0 | bridge   | YES | | 1   |
  ++--+-+-+-+
  $ ssh ubuntu@10.249.132.39
  Warning: Permanently added '10.249.132.39' (ECDSA) to the list of known hosts.
  Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.11.0-10-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

Get cloud support with Ubuntu Advantage Cloud Guest:
  http://www.ubuntu.com/business/services/cloud

  0 packages can be updated.
  0 updates are security updates.

  
  ubuntu@juju-759e30-0:~$ exit
  logout
  Connection to 10.249.132.39 closed.
  $ lxc file pull juju-759e30-0/var/lib/cloud/seed/nocloud-net/meta-data -
  #cloud-config
  instance-id: juju-759e30-0
  local-hostname: juju-759e30-0

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1708676/+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 1699549] Re: metadefs release note for pike

2017-08-15 Thread Brian Rosmaita 
This made it into RC-1, I forgot to put closes-bug on the patch.
Change-Id: I466463e1f921d1d07227b987b7d80274fcdd5f42

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

** Changed in: glance
 Assignee: Brian Rosmaita (brian-rosmaita) => (unassigned)

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

Title:
  metadefs release note for pike

Status in Glance:
  Fix Released

Bug description:
  Instead of requiring separate release notes for each metadefs change,
  we'll gather them into a single yaml file in releasenotes/notes.

  Start with a releasenote for Change-Id:
  I825c5c2a8ba3b9f5eccd9800870b6307d201614c

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1699549/+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 1710890] [NEW] Image is not available when launch instance

2017-08-15 Thread Kairat Kushaev 
Public bug reported:

it was reproduced against master.
Steps to reproduce:
1. Go to Horizon-> Images under admin
2. Create public image of any type
3. push [Launch] button on created image.
4. go to source tab.
5. Choose Boot source= Image
6. Try to find image created in "Select one" table  
AR: created image is not listed in the table
ER: created image is available in the table.

** Affects: horizon
 Importance: Undecided
 Status: New

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

Title:
  Image is not available when launch instance

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  it was reproduced against master.
  Steps to reproduce:
  1. Go to Horizon-> Images under admin
  2. Create public image of any type
  3. push [Launch] button on created image.
  4. go to source tab.
  5. Choose Boot source= Image
  6. Try to find image created in "Select one" table  
  AR: created image is not listed in the table
  ER: created image is available in the table.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1710890/+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 1710396] Re: tox -e manage -- extract_messages mixes horizon and openstack_dashboard catalogs

2017-08-15 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/493320
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=19a4012b9119643a612cf5d61be5c7d8ed128a65
Submitter: Jenkins
Branch:master

commit 19a4012b9119643a612cf5d61be5c7d8ed128a65
Author: Akihiro Motoki 
Date:   Sat Aug 12 17:52:31 2017 +

extract_messages: Specify input directory

Currently horizon/locale/{django,djangojs}.js contain strings from
openstack_dashboard and vice versa. To avoid this, --input-dirs
option needs to be passed to python setup.py extract_messages.

Change-Id: Iee874616f4c037cc68bc3b0c7d8586d86f7153f4
Closes-Bug: #1710396


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

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

Title:
  tox -e manage -- extract_messages mixes horizon and
  openstack_dashboard catalogs

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  when we run tox -e manage -- extract_messages, we will get message catalogs 
both for horizon and openstack_dashboard but each message catalogs contains 
strings from both horizon and openstack_dashboard.
  horizon message catalogs should contains only horizon strings and same for 
openstack_dashboard.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1710396/+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 1535571] Re: The stack recovery display error

2017-08-15 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/492426
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=08fd18c03b254eb7ba1cc3e999231fb29f36da93
Submitter: Jenkins
Branch:master

commit 08fd18c03b254eb7ba1cc3e999231fb29f36da93
Author: yaraat 
Date:   Thu Aug 10 11:05:37 2017 +0300

Add exceptions for action

In ResumeStack.action use try/except for action resume, delete, suspend

Closes-Bug: #1535571

Change-Id: I5f1ed830e16ca60cd11c78dcaaef3596b338b4ce


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

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

Title:
  The stack recovery display error

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
When I click "Resume Stacks",the message is "Success: Resumed Stack:
  k8sbay-yo52f6o3i75f".But the stack's status is "Resume Failed",I think
  it needs to be corrected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1535571/+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 1709801] Re: Domain scope auth fails when use endpoint filter

2017-08-15 Thread OpenStack Infra 
** Changed in: keystone/newton
   Status: Invalid => In Progress

** Changed in: keystone/newton
 Assignee: (unassigned) => Martins Jakubovics (martins-k)

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

Title:
  Domain scope auth fails when use endpoint filter

Status in OpenStack Identity (keystone):
  Invalid
Status in OpenStack Identity (keystone) newton series:
  In Progress
Status in OpenStack Identity (keystone) ocata series:
  New

Bug description:
  When use endpoint_filter.sql catalog driver in Newton and authenticate
  with domain scope, we fail to receive endpoints. Should be all
  endpoints instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1709801/+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 1710794] [NEW] The requested URL /horizon was not found on this server.

2017-08-15 Thread prakash 
Public bug reported:

Ubuntu 16.04.3 LTS
Openstack Release - Ocata

I'm not getting dashboard in chrome

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

Title:
  The requested URL /horizon was not found on this server.

Status in OpenStack Compute (nova):
  New

Bug description:
  Ubuntu 16.04.3 LTS
  Openstack Release - Ocata

  I'm not getting dashboard in chrome

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1710794/+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 1710792] [NEW] openstack server list Unexpected API Error.

2017-08-15 Thread prakash 
Public bug reported:

Ubuntu Version: Ubuntu 16.04.3 LTS
Openstack - Ocata

Getting the below error while checking the status of my instance &
unable to proceed further

root@controller:~# openstack server list
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-3df735ee-cb94-45ac-8d4f-42845207091b)

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

Title:
  openstack server list Unexpected API Error.

Status in OpenStack Compute (nova):
  New

Bug description:
  Ubuntu Version: Ubuntu 16.04.3 LTS
  Openstack - Ocata

  Getting the below error while checking the status of my instance &
  unable to proceed further

  root@controller:~# openstack server list
  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-3df735ee-cb94-45ac-8d4f-42845207091b)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1710792/+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 1702454] Re: Transforming the RequestSpec object into legacy dicts doesn't support the requested_destination field

2017-08-15 Thread Tony Breeds 
** Also affects: nova/ocata
   Importance: Undecided
   Status: New

** Changed in: nova/ocata
   Importance: Undecided => High

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

Title:
  Transforming the RequestSpec object into legacy dicts doesn't support
  the requested_destination field

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) ocata series:
  New

Bug description:
  We added a new field in the RequestSpec object called
  'requested_destination' and we began using it for evacuations by
  https://review.openstack.org/#/c/315572/ (Newton)

  That object was tranformed into legacy dictionaries (called
  "filter_properties" and "request_spec") before being rehydrated for
  the rebuild_instance() method in the conductor service. That said,
  when transforming, we were forgetting about the
  'requested_destination' field in the object so that when we were
  calling the scheduler, we were never using that field.

  That bug was fixed implicitly by
  https://review.openstack.org/#/c/469037/ which is now merged in
  master, but the issue is still there in stable branches, and if you
  need to use the legacy methods, you'll not have it.

  As a consequence, the feature to pass a destination for evacuation is
  not working in Newton and Ocata. Fortunately, given we didn't
  transformed the object into dicts before calling the scheduler for
  live-migrations, it does work for that action.

  A proper resolution would be to make sure that we pass the
  requested_destination field into 'filter_properties' so that when
  transforming again into an object, we set again the field.

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