[Yahoo-eng-team] [Bug 1643121] [NEW] The Result is different from API document about 'qos-policy-show'

[QunyingRan]

Public bug reported:

The rules descriptions In response of 'qos-policy-show' is different from 
actual result.
In API document,the response of 'qos-policy-show' is follow:
{
"policy": {
"project_id": "8d4c70a21fed4aeba121a1a429ba0d04",
"tenant_id": "8d4c70a21fed4aeba121a1a429ba0d04",
"id": "46ebaec0-0570-43ac-82f6-60d2b03168c4",
"name": "10Mbit",
"description": "This policy limits the ports to 10Mbit max.",
"shared": false,
"bandwidth_limit_rules": [
{
"id": "5f126d84-551a-4dcf-bb01-0e9c0df0c793",
"policy_id": "46ebaec0-0570-43ac-82f6-60d2b03168c4",
"max_kbps": "1",
"max_burst_kbps": "0"
}
],
"dscp_marking_rules": [
{
"id": "5f126d84-551a-4dcf-bb01-0e9c0df0c794",
"policy_id": "46ebaec0-0570-43ac-82f6-60d2b03168c4",
"dscp_mark": "26"
}
]
}
}

but the result in fact is:
{"policy":
 {"name": "p1", 
 "rules": [
  {"max_kbps": 1, 
  "type": "bandwidth_limit",
  "id": "25352eaa-0651-4c3d-b0e0-f1eb5857d4b7",
  "max_burst_kbps": 0, 
  "qos_policy_id": "d92847df-38b2-48db-bf56-d12288e9cdbb"},
  {"dscp_mark": 20, 
  "type": "dscp_marking", 
  "id": "4c31a158-73ff-484f-aef4-7cfb14035009", 
  "qos_policy_id": "d92847df-38b2-48db-bf56-d12288e9cdbb"}
  ], 
  "tenant_id": "9a5b27e4da8b4aec99df42b222a8a696", 
  "created_at": "2016-11-19T03:48:05Z", 
  "updated_at": "2016-11-19T03:49:30Z", 
  "revision_number": 3,
  "shared": false, 
  "project_id": "9a5b27e4da8b4aec99df42b222a8a696", 
  "id": "d92847df-38b2-48db-bf56-d12288e9cdbb", 
  "description": ""}
 }

** Affects: neutron
 Importance: Undecided
 Assignee: QunyingRan (ran-qunying)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) => QunyingRan (ran-qunying)

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

Title:
  The Result is different from API document about 'qos-policy-show'

Status in neutron:
  New

Bug description:
  The rules descriptions In response of 'qos-policy-show' is different from 
actual result.
  In API document,the response of 'qos-policy-show' is follow:
  {
  "policy": {
  "project_id": "8d4c70a21fed4aeba121a1a429ba0d04",
  "tenant_id": "8d4c70a21fed4aeba121a1a429ba0d04",
  "id": "46ebaec0-0570-43ac-82f6-60d2b03168c4",
  "name": "10Mbit",
  "description": "This policy limits the ports to 10Mbit max.",
  "shared": false,
  "bandwidth_limit_rules": [
  {
  "id": "5f126d84-551a-4dcf-bb01-0e9c0df0c793",
  "policy_id": "46ebaec0-0570-43ac-82f6-60d2b03168c4",
  "max_kbps": "1",
  "max_burst_kbps": "0"
  }
  ],
  "dscp_marking_rules": [
  {
  "id": "5f126d84-551a-4dcf-bb01-0e9c0df0c794",
  "policy_id": "46ebaec0-0570-43ac-82f6-60d2b03168c4",
  "dscp_mark": "26"
  }
  ]
  }
  }

  but the result in fact is:
  {"policy":
   {"name": "p1", 
   "rules": [
{"max_kbps": 1, 
"type": "bandwidth_limit",
"id": "25352eaa-0651-4c3d-b0e0-f1eb5857d4b7",
"max_burst_kbps": 0, 
"qos_policy_id": "d92847df-38b2-48db-bf56-d12288e9cdbb"},
{"dscp_mark": 20, 
"type": "dscp_marking", 
"id": "4c31a158-73ff-484f-aef4-7cfb14035009", 
"qos_policy_id": "d92847df-38b2-48db-bf56-d12288e9cdbb"}
], 
"tenant_id": "9a5b27e4da8b4aec99df42b222a8a696", 
"created_at": "2016-11-19T03:48:05Z", 
"updated_at": "2016-11-19T03:49:30Z", 
"revision_number": 3,
"shared": false, 
"project_id": "9a5b27e4da8b4aec99df42b222a8a696", 
"id": "d92847df-38b2-48db-bf56-d12288e9cdbb", 
"description": ""}
   }

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1643121/+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 1633337] Re: There is no event send out when floating updated

[LIU Yulong]

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

** This bug has been marked a duplicate of bug 1642918
   floating-ip nova notification is broken

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

Title:
  There is no event send out when floating updated

Status in neutron:
  In Progress

Bug description:
  We register the event with this constant
  
https://github.com/openstack/neutron/blob/master/neutron/callbacks/resources.py#L16,
  It is the string 'floating_ip'.

  But from the log message "Notify callbacks [] for floatingip,
  before_response", the resource name is 'floatingip'. There is no '_'.

  Due to this different name for the resource, there is no event send
  out when floating ip updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/167/+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 1642062] Re: cloud-init-local.service should be RequiresMountsFor=/var/lib/cloud rather than /var/lib

[Steve Langasek]

Hello Scott, or anyone else affected,

Accepted cloud-init into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-init/0.7.8-49
-g9e904bb-0ubuntu1~16.04.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Released => Fix Committed

** Changed in: cloud-init (Ubuntu)
   Status: New => Fix Released

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

Title:
  cloud-init-local.service should be RequiresMountsFor=/var/lib/cloud
  rather than /var/lib

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Committed
Status in cloud-init source package in Yakkety:
  New

Bug description:
  cloud-init-local.service writes to /var/lib/cloud/ and is more correct
  to have that listed here than /var/lib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1642062/+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 1643112] [NEW] Auth plugins should be linked to Federation Protocol

[Adam Young]

Public bug reported:

When setting up Federation, if the protocol needs an new auth plugin,
the current mechanism is to add it to the methods list for the [auth]
section.  However, this has the effect of linking them all together,
when the real method should be to link the auth plugin with the
protocol.  Most of the Federation code is going to require the mapped
plugin, but that should not be included in the stack that is then used
for password or token based authentication.

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

Title:
  Auth plugins should be linked to Federation Protocol

Status in OpenStack Identity (keystone):
  New

Bug description:
  When setting up Federation, if the protocol needs an new auth plugin,
  the current mechanism is to add it to the methods list for the [auth]
  section.  However, this has the effect of linking them all together,
  when the real method should be to link the auth plugin with the
  protocol.  Most of the Federation code is going to require the mapped
  plugin, but that should not be included in the stack that is then used
  for password or token based authentication.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1643112/+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 1643100] [NEW] Flavors with zero disk size should not be disabled

[Ying Zuo]

Public bug reported:

Steps to reproduce:

1. Create a flavor with zero root disk

2. Create an image with minimum disk size as 10GB

3. Try to launch an instance from the image created in step 2 from
either the Angular launch instance modal or the Python launch instance
modal. You will get a help message indicating the flavor created in step
1 is not a valid option because it doesn't meet the minimum disk size
set in the image.


I noticed a few issues:

1. On the Python launch instance modal, the help text message is
overlapping with the next input label. Also, the user can't really tell
which flavors are disabled because all flavors in the dropdown are
clickable and have the same text styling. However, after they click on a
disabled flavor, the selected option in the dropdown doesn't change.

2. The user won't be able to launch an instance with the zero disk
flavor with either Angular or Python launch instance modal. According to
the openstack guide[1], zero is a special case which uses the image size
for the instance. Thus flavors with zero disk size should not be
disabled because of the image disk requirement.

[1] http://docs.openstack.org/admin-guide/compute-flavors.html

** Affects: horizon
 Importance: Undecided
 Assignee: Ying Zuo (yingzuo)
 Status: New

** Changed in: horizon
 Assignee: (unassigned) => Ying Zuo (yingzuo)

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

Title:
  Flavors with zero disk size should not be disabled

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Steps to reproduce:

  1. Create a flavor with zero root disk

  2. Create an image with minimum disk size as 10GB

  3. Try to launch an instance from the image created in step 2 from
  either the Angular launch instance modal or the Python launch instance
  modal. You will get a help message indicating the flavor created in
  step 1 is not a valid option because it doesn't meet the minimum disk
  size set in the image.

  
  I noticed a few issues:

  1. On the Python launch instance modal, the help text message is
  overlapping with the next input label. Also, the user can't really
  tell which flavors are disabled because all flavors in the dropdown
  are clickable and have the same text styling. However, after they
  click on a disabled flavor, the selected option in the dropdown
  doesn't change.

  2. The user won't be able to launch an instance with the zero disk
  flavor with either Angular or Python launch instance modal. According
  to the openstack guide[1], zero is a special case which uses the image
  size for the instance. Thus flavors with zero disk size should not be
  disabled because of the image disk requirement.

  [1] http://docs.openstack.org/admin-guide/compute-flavors.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1643100/+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 1642681] Re: _process_instance_vif_deleted_event fails with "TypeError: detach_interface() takes exactly 4 arguments (3 given)"

[OpenStack Infra]

Reviewed:  https://review.openstack.org/399155
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=383e795a5ed16cdafdab04858c1bd889fa893fe5
Submitter: Jenkins
Branch:master

commit 383e795a5ed16cdafdab04858c1bd889fa893fe5
Author: Dan Smith 
Date:   Thu Nov 17 09:59:32 2016 -0800

Fix detach_interface() call from external event handler

The signature for VirtDriver.detach_interface() changed recently in
41591c9456fd4eb91407551b9b9898e8f4974050, but the call from the
external event handler was not updated. This does that.

Change-Id: I560920ed521f09909d91bb0aac42bf97447475b0
Closes-Bug: #1642681


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

Title:
  _process_instance_vif_deleted_event fails with "TypeError:
  detach_interface() takes exactly 4 arguments (3 given)"

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Seeing this in a gate job here:

  http://logs.openstack.org/00/398800/1/gate/gate-tempest-dsvm-full-
  devstack-plugin-ceph-ubuntu-
  xenial/a387fb0/logs/screen-n-cpu.txt.gz?level=TRACE#_2016-11-17_11_29_10_965

  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server 
[req-1e141c4e-e2eb-4b06-89b5-849ecf4d065d nova service] Exception during 
message handling
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server Traceback (most 
recent call last):
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 
155, in _process_incoming
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server res = 
self.dispatcher.dispatch(message)
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
225, in dispatch
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server return 
self._do_dispatch(endpoint, method, ctxt, args)
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
195, in _do_dispatch
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server result = 
func(ctxt, **new_args)
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server   File 
"/opt/stack/new/nova/nova/exception_wrapper.py", line 75, in wrapped
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server 
function_name, call_dict, binary)
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server 
self.force_reraise()
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server 
six.reraise(self.type_, self.value, self.tb)
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server   File 
"/opt/stack/new/nova/nova/exception_wrapper.py", line 66, in wrapped
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server return 
f(self, context, *args, **kw)
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server   File 
"/opt/stack/new/nova/nova/compute/manager.py", line 6755, in 
external_instance_event
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server event.tag)
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server   File 
"/opt/stack/new/nova/nova/compute/manager.py", line 6724, in 
_process_instance_vif_deleted_event
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server 
self.driver.detach_interface(instance, vif)
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server TypeError: 
detach_interface() takes exactly 4 arguments (3 given)
  2016-11-17 11:29:10.965 2249 ERROR oslo_messaging.rpc.server 

  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22_process_instance_vif_deleted_event%5C%22%20AND%20message%3A%5C%22TypeError%3A%20detach_interface()%20takes%20exactly%204%20arguments%20(3%20given)%5C%22%20AND%20tags%3A%5C%22screen-n-cpu.txt%5C%22=7d

  New regression as of 11/16: https://review.openstack.org/#/c/209362/

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1642681/+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 1642918] Re: floating-ip nova notification is broken

[OpenStack Infra]

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

commit eef348f74a13f42780713aa9dfca9cc617fa52c8
Author: YAMAMOTO Takashi 
Date:   Fri Nov 18 19:37:50 2016 +0900

callbacks: Make the value of FLOATING_IP match with api resource

Note: BEFORE_RESPONSE code assumes they match.  Nova notifier uses
FLOATING_IP/BEFORE_RESPONSE.

Closes-Bug: #1642918
Change-Id: If834ca1ee52d538cae4a5d164e0e0343c7019546


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

Title:
  floating-ip nova notification is broken

Status in neutron:
  Fix Released

Bug description:
  I1d7d4b80ee77deefce18df22f76cab81750c0397 seems to assume api resource names
  matches with callbacks resource names.
  unfortunately it isn't the case for floating-ip.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1642918/+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 1576888] Re: Support local_id configuration

[OpenStack Infra]

Reviewed:  https://review.openstack.org/378068
Committed: 
https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=5f53e32f46c19afdb0695a0379e8826b1480f297
Submitter: Jenkins
Branch:master

commit 5f53e32f46c19afdb0695a0379e8826b1480f297
Author: Trevor McCasland 
Date:   Wed Sep 7 13:12:39 2016 -0500

api-ref: Update local_id configuration

Adding local_id configuration support to api-ref with respect to the
changes made in this commit 7cf4ef682f83fc08484011454f62c27882064dff.

Change-Id: I2ea43c8cad95cb94529a3f576dced5d306b8da4c
Closes-Bug: #1576888


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

Title:
  Support local_id configuration

Status in neutron:
  Fix Released
Status in openstack-manuals:
  Confirmed

Bug description:
  https://review.openstack.org/310676
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.

  commit 7cf4ef682f83fc08484011454f62c27882064dff
  Author: nick.zhuyj 
  Date:   Wed Apr 27 03:36:02 2016 -0500

  Support local_id configuration
  
  In some case, we want to specify the local id instead of use the
  external ip. For example, the router is behind NAT, and we don't
  want to expose this IP to peer. This patch will make local_id
  configurable. Most often, local id would be domain name, email
  address etc. But if local id is not configured then external ip
  will still be used as the leftid.
  
  Note: this change is DocImpact & APIImpact
  
  Change-Id: I2433d72ba22ce410cbfafb7b8bfb16f51eefdfc1
  Closes-Bug: #1513353

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1576888/+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 1611074] Re: Reformatting of ephemeral drive fails on resize of Azure VM

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1

---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1) zesty; urgency=medium

  * debian/cloud-init.postinst: update /etc/fstab on Azure to fix
future resize operations. (LP: #1611074)
  * New upstream snapshot.
- Add activate_datasource, for datasource specific code paths.
  Use that on Azure to handle re-formatting of ephemeral disk.
  (LP: #1611074)

 -- Scott Moser   Fri, 18 Nov 2016 16:37:34 -0500

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Reformatting of ephemeral drive fails on resize of Azure VM

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed

Bug description:
  === Begin SRU Template ===
  [Impact]
  In some cases, cloud-init writes entries to /etc/fstab, and on azure it will
  even format a disk for mounting and then write the entry for that 'ephemeral'
  disk there.

  A supported operation on Azure is to "resize" the system.  When you do this
  the system is shut down, resized (given larger/faster disks and more CPU) and
  then brought back up.  In that process, the "ephemeral" disk re-initialized
  to its original NTFS format.  The designed goal is for cloud-init to recognize
  this situation and re-format the disk to ext4.

  The problem is that the mount of that disk happens before cloud-init can
  reformat.  Thats because the entry in fstab has 'auto' and is automatically
  mounted.  The end result is that after resize operation the user will be left
  with the ephemeral disk mounted at /mnt and having a ntfs filesystem rather
  than ext4.

  [Test Case]
  The text in comment 3 describes how to recreate by the original reporter.
  Another way to do this is to just re-format the ephemeral disk as
  ntfs and then reboot.  The result *should* be that after reboot it
  comes back up and has an ext4 filesystem on it.

  1.) boot system on azure
    (for this, i use https://gist.github.com/smoser/5806147, but you can
     use web ui or any other way).
 Save output of
   journalctl --no-pager > journalctl.orig
   systemctl status --no-pager > systemctl-status.orig
   systemctl --no-pager > systemctl.orig

  2.) unmount the ephemeral disk
     $ umount /mnt

  3.) repartition it so that mkfs.ntfs does less and is faster
     This is not strictly necessary, but mkfs.ntfs can take upwards of
     20 minutes.  shrinking /dev/sdb2 to be 200M means it will finish
     in < 1 minute.

     $ disk=/dev/disk/cloud/azure_resource
     $ part=/dev/disk/cloud/azure_resource-part1
     $ echo "2048,$((2*1024*100)),7" | sudo sfdisk "$disk"
     $ time mkfs.ntfs --quick "$part"

  4.) reboot
  5.) expect that /proc/mounts has /dev/disk/cloud/azure_resource-part1 as ext4
  and that fstab has x-systemd.requires in it.

  $ awk '$2 == "/mnt" { print $0 }' /proc/mounts
  /dev/sdb1 /mnt ext4 rw,relatime,data=ordered 0 0

  $ awk '$2 == "/mnt" { print $0 }' /etc/fstab
  /dev/sdb1 /mnt auto 
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig 0 2

  6.) collect journal and systemctl information as described in step 1 above.
  Compare output, specifically looking for case insensitve "breaks"

  [Regression Potential]
  Regression is unlikely.  Likely failure case is just that the problem is not
  correctly fixed, and the user ends up with either an NTFS formated disk that
  is mounted at /mnt or there is nothing mounted at /mnt.

  === End SRU Template ===

  After resizing a 16.04 VM on Azure, the VM is presented with a new
  ephemeral drive (of a different size), which initially is NTFS
  formatted. Cloud-init tries to format the appropriate partition ext4,
  but fails because it is mounted. Cloud-init has unmount logic for
  exactly this case in the get_data call on the Azure data source, but
  this is never called because fresh cache is found.

  Jun 27 19:07:47 azubuntu1604arm [CLOUDINIT] handlers.py[DEBUG]: start: 
init-network/check-cache: attempting to read from cache [trust]
  Jun 27 19:07:47 azubuntu1604arm [CLOUDINIT] util.py[DEBUG]: Reading from 
/var/lib/cloud/instance/obj.pkl (quiet=False)
  Jun 27 19:07:47 azubuntu1604arm [CLOUDINIT] util.py[DEBUG]: Read 5950 bytes 
from /var/lib/cloud/instance/obj.pkl
  Jun 27 19:07:47 azubuntu1604arm [CLOUDINIT] stages.py[DEBUG]: restored from 
cache: DataSourceAzureNet [seed=/dev/sr0]
  Jun 27 19:07:47 azubuntu1604arm [CLOUDINIT] handlers.py[DEBUG]: finish: 
init-network/check-cache: SUCCESS: restored from cache: DataSourceAzureNet 
[seed=/dev/sr0]
  ...
  Jun 27 19:07:48 azubuntu1604arm [CLOUDINIT] cc_disk_setup.py[DEBUG]: Creating 
file system None on /dev/sdb1
  Jun 27 19:07:48 

[Yahoo-eng-team] [Bug 1643080] [NEW] horizon dashboard can't be loaded properly ASN1 undefined

[Jerry Zhao]

Public bug reported:

Uncaught ReferenceError: ASN1 is not defined
at fc3281fe5592.js:6115
10.0.10.10/:58 Uncaught TypeError: Cannot set property 'languageCode' of 
undefined
at 10.0.10.10/:58
at 10.0.10.10/:81
e9822d1af741.js:32 Uncaught TypeError: Cannot set property 'string' of undefined
at e9822d1af741.js:32
fc3281fe5592.js:818 Uncaught Error: [$injector:nomod] Module 'horizon.app' is 
not available! You either misspelled the module name or forgot to load it. If 
registering a module ensure that you specify the dependencies as the second 
argument.

I am using the master branch on 10/17/2016

There is no Login button on login page, no Cancel button in modal
windows and can't select item from drop down list. All those pages have
the error above in the browser console.

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

Title:
  horizon dashboard can't be loaded properly ASN1 undefined

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Uncaught ReferenceError: ASN1 is not defined
  at fc3281fe5592.js:6115
  10.0.10.10/:58 Uncaught TypeError: Cannot set property 'languageCode' of 
undefined
  at 10.0.10.10/:58
  at 10.0.10.10/:81
  e9822d1af741.js:32 Uncaught TypeError: Cannot set property 'string' of 
undefined
  at e9822d1af741.js:32
  fc3281fe5592.js:818 Uncaught Error: [$injector:nomod] Module 'horizon.app' is 
not available! You either misspelled the module name or forgot to load it. If 
registering a module ensure that you specify the dependencies as the second 
argument.

  I am using the master branch on 10/17/2016

  There is no Login button on login page, no Cancel button in modal
  windows and can't select item from drop down list. All those pages
  have the error above in the browser console.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1643080/+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 1643078] [NEW] Minimum disk size of an image should be prepopulated on create volume from image modal

[Ying Zuo]

Public bug reported:

Steps to reproduce:

1. Create an image with minimum disk size set as higher than the actual
image size.

2. Click the Create Volume action in the action menu of the image
created in step 1.

3. Note that the actual size of the image is pre-populated on the Size
input box, but the minimum disk size set on the image should be pre-
populated instead.

** Affects: horizon
 Importance: Undecided
 Assignee: Ying Zuo (yingzuo)
 Status: New

** Changed in: horizon
 Assignee: (unassigned) => Ying Zuo (yingzuo)

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

Title:
  Minimum disk size of an image should be prepopulated on create volume
  from image modal

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Steps to reproduce:

  1. Create an image with minimum disk size set as higher than the
  actual image size.

  2. Click the Create Volume action in the action menu of the image
  created in step 1.

  3. Note that the actual size of the image is pre-populated on the Size
  input box, but the minimum disk size set on the image should be pre-
  populated instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1643078/+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 1643074] [NEW] policy check for panels and dashboards don't handle nested policy rules

[David Lyle]

Public bug reported:

The policy_rules property on Panel and Dashboard is intended to handle
nested policy rules, where the top level rules are OR'd and the lower
level is AND'd. Currently regardless of what is passed in, it's wrapped
in another list. There should be a check that policy_rules is not
already a list.

** Affects: horizon
 Importance: High
 Assignee: David Lyle (david-lyle)
 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/1643074

Title:
  policy check for panels and dashboards don't handle nested policy
  rules

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  The policy_rules property on Panel and Dashboard is intended to handle
  nested policy rules, where the top level rules are OR'd and the lower
  level is AND'd. Currently regardless of what is passed in, it's
  wrapped in another list. There should be a check that policy_rules is
  not already a list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1643074/+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 1643043] [NEW] random seed command output not captured

[Joshua Powers]

Public bug reported:

[description]
While using a 16.04 (Xenial) lxd cloud image, trying to create random seed data 
with a command does not get put into a specified file.

[cloud-config]
#cloud-config
random_seed:
  command: ["cat", "/proc/sys/kernel/random/uuid"]
  command_required: true
  file: /root/seed

[steps to reproduce]
Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)
cloud-init: 0.7.8-1-g3705bb5-0ubuntu1~16.04.3

lxc init ubuntu:xenial/amd64 xenial
lxc config set xenial user.user-data - < cloud-config.yaml
lxc start xenial

[actual result]
There is no file called /root/seed and no error messages even though the 
command is marked as required.

[expected result]
I would have expected the file /root/seed to exist with a uuid in it.

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

** Attachment added: "cloud-init.log"
   
https://bugs.launchpad.net/bugs/1643043/+attachment/4779452/+files/cloud-init.log

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

Title:
  random seed command output not captured

Status in cloud-init:
  New

Bug description:
  [description]
  While using a 16.04 (Xenial) lxd cloud image, trying to create random seed 
data with a command does not get put into a specified file.

  [cloud-config]
  #cloud-config
  random_seed:
command: ["cat", "/proc/sys/kernel/random/uuid"]
command_required: true
file: /root/seed

  [steps to reproduce]
  Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)
  cloud-init: 0.7.8-1-g3705bb5-0ubuntu1~16.04.3

  lxc init ubuntu:xenial/amd64 xenial
  lxc config set xenial user.user-data - < cloud-config.yaml
  lxc start xenial

  [actual result]
  There is no file called /root/seed and no error messages even though the 
command is marked as required.

  [expected result]
  I would have expected the file /root/seed to exist with a uuid in it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1643043/+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 1620684] Re: nova list --status soft_deleted is not showing soft deleted Instances

[OpenStack Infra]

** Changed in: nova
   Status: Opinion => In Progress

** Changed in: nova
 Assignee: Anusha Unnam (anusha-unnam) => jichenjc (jichenjc)

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

Title:
  nova list --status soft_deleted is not showing soft deleted Instances

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  Steps to reproduce:

  1. Set reclaim_instance_interval to a value in nova.conf
  2. Boot an instance.
  3. delete the instance(instance will be soft_deleted)
  4. nova list --status soft_deleted

  Expected result:
  should display the soft_deleted instances based on the 
reclaim_instance_interval.

  Actual result:
  No instances are displayed.

  This bug is reported in the admin context.

  Environment:
  current master devstack

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1620684/+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 1643041] [NEW] snappy module does not install snaps

[Joshua Powers]

Public bug reported:

[description]
While using a 16.04 (Xenial) lxd cloud image, trying to setup snappy to install 
hello-world does not work.

[cloud-config]
#cloud-config
snappy:
  system_snappy: yes (or auto)
  packages: [hello-world]

[steps to reproduce]
Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)
cloud-init: 0.7.8-1-g3705bb5-0ubuntu1~16.04.3

lxc init ubuntu:xenial/amd64 xenial
lxc config set xenial user.user-data - < cloud-config.yaml
lxc start xenial

[actual result]
snappy is installed, however, `snap list` returns no snaps installed.

[expected result]
I would have expected the "hello-world" snap to be installed.

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

Title:
  snappy module does not install snaps

Status in cloud-init:
  New

Bug description:
  [description]
  While using a 16.04 (Xenial) lxd cloud image, trying to setup snappy to 
install hello-world does not work.

  [cloud-config]
  #cloud-config
  snappy:
system_snappy: yes (or auto)
packages: [hello-world]

  [steps to reproduce]
  Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)
  cloud-init: 0.7.8-1-g3705bb5-0ubuntu1~16.04.3

  lxc init ubuntu:xenial/amd64 xenial
  lxc config set xenial user.user-data - < cloud-config.yaml
  lxc start xenial

  [actual result]
  snappy is installed, however, `snap list` returns no snaps installed.

  [expected result]
  I would have expected the "hello-world" snap to be installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1643041/+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 1444532] Re: nova-scheduler doesnt reconnect to databases when started and database is down

[Chuck Short]

** Changed in: nova (Ubuntu)
   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/1444532

Title:
  nova-scheduler doesnt reconnect to databases when started and database
  is down

Status in OpenStack Compute (nova):
  Invalid
Status in nova package in Ubuntu:
  Invalid

Bug description:
  In Juno release (ubuntu packages), when you start nova-scheduler but
  database is down, the service never reconnects, the stacktrace is as
  follow :

  
  AUDIT nova.service [-] Starting scheduler node (version 2014.2.2)
  ERROR nova.openstack.common.threadgroup [-] (OperationalError) (2003, "Can't 
connect to MySQL server on '10.128.30.11' (111)") None None
  TRACE nova.openstack.common.threadgroup Traceback (most recent call last):
  TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/dist-packages/nova/openstack/common/threadgroup.py", line 
125, in wait
  TRACE nova.openstack.common.threadgroup x.wait()
  TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/dist-packages/nova/openstack/common/threadgroup.py", line 
47, in wait
  TRACE nova.openstack.common.threadgroup return self.thread.wait()
  TRACE nova.openstack.common.threadgroup   File 
"/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 173, in 
wait
  TRACE nova.openstack.common.threadgroup return self._exit_event.wait()
  TRACE nova.openstack.common.threadgroup   File 
"/usr/local/lib/python2.7/dist-packages/eventlet/event.py", line 121, in wait
  TRACE nova.openstack.common.threadgroup return hubs.get_hub().switch()
  TRACE nova.openstack.common.threadgroup   File 
"/usr/local/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 293, in 
switch
  TRACE nova.openstack.common.threadgroup return self.greenlet.switch()
  TRACE nova.openstack.common.threadgroup   File 
"/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 212, in 
main
  TRACE nova.openstack.common.threadgroup result = function(*args, **kwargs)
  TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/dist-packages/nova/openstack/common/service.py", line 490, 
in run_service
  TRACE nova.openstack.common.threadgroup service.start()
  TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/dist-packages/nova/service.py", line 169, in start
  TRACE nova.openstack.common.threadgroup self.host, self.binary)
  TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/dist-packages/nova/conductor/api.py", line 161, in 
service_get_by_args
  TRACE nova.openstack.common.threadgroup binary=binary, topic=None)
  TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/dist-packages/nova/utils.py", line 949, in wrapper
  TRACE nova.openstack.common.threadgroup return func(*args, **kwargs)
  TRACE nova.openstack.common.threadgroup   File 
"/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/server.py", line 
139, in inner
  TRACE nova.openstack.common.threadgroup return func(*args, **kwargs)
  TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/dist-packages/nova/conductor/manager.py", line 279, in 
service_get_all_by
  TRACE nova.openstack.common.threadgroup result = 
self.db.service_get_by_args(context, host, binary)
  TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/dist-packages/nova/db/api.py", line 136, in 
service_get_by_args
  TRACE nova.openstack.common.threadgroup return 
IMPL.service_get_by_args(context, host, binary)
  TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py", line 125, in 
wrapper
  TRACE nova.openstack.common.threadgroup return f(*args, **kwargs)
  TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py", line 490, in 
service_get_by_args
  TRACE nova.openstack.common.threadgroup result = model_query(context, 
models.Service).\
  TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py", line 213, in 
model_query
  TRACE nova.openstack.common.threadgroup session = kwargs.get('session') 
or get_session(use_slave=use_slave)
  TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py", line 101, in 
get_session
  TRACE nova.openstack.common.threadgroup facade = _create_facade_lazily()
  TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py", line 91, in 
_create_facade_lazily
  TRACE nova.openstack.common.threadgroup _ENGINE_FACADE = 
db_session.EngineFacade.from_config(CONF)
  TRACE nova.openstack.common.threadgroup   File 
"/usr/local/lib/python2.7/dist-packages/oslo/db/sqlalchemy/session.py", line 
795, in from_config
  TRACE 

[Yahoo-eng-team] [Bug 1554522] Re: time zone from local_settings.py is not taken into account

[OpenStack Infra]

Reviewed:  https://review.openstack.org/289920
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=4b1cb06f955ad6f7db06314db84766d699fef105
Submitter: Jenkins
Branch:master

commit 4b1cb06f955ad6f7db06314db84766d699fef105
Author: Matthias Runge 
Date:   Tue Mar 8 14:36:11 2016 +0100

take time zone into account

Previously, settings fell back to UTC
rather than using what was configured in local_settings.

Change-Id: I39113b90364fb53b3a14b2f0ad26637a438fee04
Closes-Bug: #1554522


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

Title:
  time zone from local_settings.py is not taken into account

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  one can set the time zone in local_settings.py

  but it is not taken into account for time zone settings at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1554522/+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 1457598] Re: Horizon unable to change quotas if routers extension is disabled in neutron

[OpenStack Infra]

Reviewed:  https://review.openstack.org/185820
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=1a3ab89f22dd37aa1ff1491777b9e3e789517d13
Submitter: Jenkins
Branch:master

commit 1a3ab89f22dd37aa1ff1491777b9e3e789517d13
Author: liyingjun 
Date:   Wed May 27 10:07:07 2015 +0800

Disable router and fip quotas when router is disabled

Currently Horizon unable to change quotas if routers extension is
disabled, fix this by adding router and floatingip quotas to
disabled_quotas when router extension is disabled.

Change-Id: I14d8a6e2e439ab48b62ce64c88ebb4643d11e49f
Closes-bug: #1457598


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

Title:
  Horizon unable to change quotas if routers extension is disabled in
  neutron

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Horizon version:

  openstack-dashboard 1:2014.2.2-0ubuntu1~cloud0
  python-django-horizon   1:2014.2.2-0ubuntu1~cloud0

  Steps to reproduce:

  1. Disable router extension in neutron (empty service_plugins in neutron.conf)
  2. Disable routers in horizon OPENSTACK_NEUTRON_NETWORK = { 
'enable_router': False, ...
  3. Try to change quotas for tenant

  Expected behaviour:

  1. Quotes dialogue without fields 'routers/floatingips'
  2. Changes in quotas can be saved.

  Actual behaviour:

  1. Interface shows empty fields 'routers' and 'floatingips'
  2. Attempt to save quotas without changes fails (see screenshot), complaining 
about 'this field is required'.
  3. Any values in this fields rejected by server: 'Error: Modified project 
information and members, but unable to modify project quotas.'

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1457598/+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 1643022] [NEW] landscape module does not work

[Joshua Powers]

Public bug reported:

[description]
While using a 16.04 (Xenial) lxd cloud image, trying to setup landscape does 
not install the landscape-client or set up the config and has no error message.

[cloud-config]
#cloud-conifg
landscape:
  client:
log_level: "info"
url: "https://landscape.canonical.com/message-system;
ping_url: "http://landscape.canonical.com/ping;
data_path: "/var/lib/landscape/client"
http_proxy: "http://my.proxy.com/foobar;
https_proxy: "https://my.proxy.com/foobar;
tags: "server,cloud"
computer_title: "footitle"
registration_key: "fookey"
account_name: "fooaccount"

[steps to reproduce]
Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)
cloud-init: 0.7.8-1-g3705bb5-0ubuntu1~16.04.3

lxc init ubuntu:xenial/amd64 xenial
lxc config set xenial user.user-data - < cloud-config.yaml
lxc start xenial

[actual result]
root@xenial-lxd:/var/log# cat cloud-init.log  | grep landscape
Nov 18 17:40:00 xenial-lxd [CLOUDINIT] stages.py[DEBUG]: Running module 
landscape () with 
frequency once-per-instance
Nov 18 17:40:00 xenial-lxd [CLOUDINIT] handlers.py[DEBUG]: start: 
modules-final/config-landscape: running config-landscape with frequency 
once-per-instance
Nov 18 17:40:00 xenial-lxd [CLOUDINIT] util.py[DEBUG]: Writing to 
/var/lib/cloud/instances/xenial-lxd/sem/config_landscape - wb: [420] 24 bytes
Nov 18 17:40:00 xenial-lxd [CLOUDINIT] helpers.py[DEBUG]: Running 
config-landscape using lock ()
Nov 18 17:40:00 xenial-lxd [CLOUDINIT] handlers.py[DEBUG]: finish: 
modules-final/config-landscape: SUCCESS: config-landscape ran successfully

[expected result]
I would have expected landscape-client to get installed and the configuration 
file to be written.

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

Title:
  landscape module does not work

Status in cloud-init:
  New

Bug description:
  [description]
  While using a 16.04 (Xenial) lxd cloud image, trying to setup landscape does 
not install the landscape-client or set up the config and has no error message.

  [cloud-config]
  #cloud-conifg
  landscape:
client:
  log_level: "info"
  url: "https://landscape.canonical.com/message-system;
  ping_url: "http://landscape.canonical.com/ping;
  data_path: "/var/lib/landscape/client"
  http_proxy: "http://my.proxy.com/foobar;
  https_proxy: "https://my.proxy.com/foobar;
  tags: "server,cloud"
  computer_title: "footitle"
  registration_key: "fookey"
  account_name: "fooaccount"

  [steps to reproduce]
  Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)
  cloud-init: 0.7.8-1-g3705bb5-0ubuntu1~16.04.3

  lxc init ubuntu:xenial/amd64 xenial
  lxc config set xenial user.user-data - < cloud-config.yaml
  lxc start xenial

  [actual result]
  root@xenial-lxd:/var/log# cat cloud-init.log  | grep landscape
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] stages.py[DEBUG]: Running module 
landscape () with 
frequency once-per-instance
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] handlers.py[DEBUG]: start: 
modules-final/config-landscape: running config-landscape with frequency 
once-per-instance
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] util.py[DEBUG]: Writing to 
/var/lib/cloud/instances/xenial-lxd/sem/config_landscape - wb: [420] 24 bytes
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] helpers.py[DEBUG]: Running 
config-landscape using lock ()
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] handlers.py[DEBUG]: finish: 
modules-final/config-landscape: SUCCESS: config-landscape ran successfully

  [expected result]
  I would have expected landscape-client to get installed and the configuration 
file to be written.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1643022/+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 1643020] [NEW] zfs backed lxd fails with missing /dev/zfs

[Joshua Powers]

Public bug reported:

[description]
While using a 16.04 (Xenial) lxd cloud image, trying to setup lxd backed by zfs 
fails to create due to a missing /dev/zfs

[cloud-config]
#cloud-config
lxd:
  init:
storage_backend: zfs
storage_pool: lxd

[steps to reproduce]
Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)

lxc init ubuntu:xenial/amd64 xenial
lxc config set xenial user.user-data - < cloud-config.yaml
lxc start xenial

[actual result]
Nov 18 17:27:42 xenial-lxd [CLOUDINIT] util.py[DEBUG]: Running module lxd 
() 
failed#012Traceback (most recent call last):#012  File 
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 785, in 
_run_modules#012freq=freq)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 70, in run#012
return self._runners.run(name, functor, args, freq, clear_on_fail)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 199, in run#012
results = functor(*args)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/config/cc_lxd.py", line 104, in 
handle#012util.subp(cmd)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/util.py", line 1832, in subp#012
cmd=args)#012cloudinit.util.ProcessExecutionError: Unexpected error while 
running command.#012Command: ['lxd', 'init', '--auto', '--storage-backend=zfs', 
'--storage-pool=lxd']#012Exit code: 1#012Reason
 : -#012Stdout: ''#012Stderr: 'error: Invalid ZFS pool: /dev/zfs and 
/proc/self/mounts are required.\n'

root@xenial-lxd:~# ls /dev/zfs
ls: cannot access '/dev/zfs': No such file or directory
root@xenial-lxd:~# ls /proc/self/mounts
/proc/self/mounts

[expected result]
I would have expected zfs to be setup with a pool named 'lxd' and cloud-init to 
complete successfully.

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

** Attachment added: "cloud-init.log"
   
https://bugs.launchpad.net/bugs/1643020/+attachment/4779422/+files/lxd-zfs-cloud-init.log

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

Title:
  zfs backed lxd fails with missing /dev/zfs

Status in cloud-init:
  New

Bug description:
  [description]
  While using a 16.04 (Xenial) lxd cloud image, trying to setup lxd backed by 
zfs fails to create due to a missing /dev/zfs

  [cloud-config]
  #cloud-config
  lxd:
init:
  storage_backend: zfs
  storage_pool: lxd

  [steps to reproduce]
  Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)

  lxc init ubuntu:xenial/amd64 xenial
  lxc config set xenial user.user-data - < cloud-config.yaml
  lxc start xenial

  [actual result]
  Nov 18 17:27:42 xenial-lxd [CLOUDINIT] util.py[DEBUG]: Running module lxd 
() 
failed#012Traceback (most recent call last):#012  File 
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 785, in 
_run_modules#012freq=freq)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 70, in run#012
return self._runners.run(name, functor, args, freq, clear_on_fail)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 199, in run#012
results = functor(*args)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/config/cc_lxd.py", line 104, in 
handle#012util.subp(cmd)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/util.py", line 1832, in subp#012
cmd=args)#012cloudinit.util.ProcessExecutionError: Unexpected error while 
running command.#012Command: ['lxd', 'init', '--auto', '--storage-backend=zfs', 
'--storage-pool=lxd']#012Exit code: 1#012Reas
 on: -#012Stdout: ''#012Stderr: 'error: Invalid ZFS pool: /dev/zfs and 
/proc/self/mounts are required.\n'

  root@xenial-lxd:~# ls /dev/zfs
  ls: cannot access '/dev/zfs': No such file or directory
  root@xenial-lxd:~# ls /proc/self/mounts
  /proc/self/mounts

  [expected result]
  I would have expected zfs to be setup with a pool named 'lxd' and cloud-init 
to complete successfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1643020/+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 1643017] [NEW] libvirtError: block copy still active: disk 'vdb' not ready for pivot yet

[Lee Yarwood]

Public bug reported:

This is an additional corner case for swap_volume not covered by
bug#1630600.

The following failure is taken from the devstack change enabling the new
swap_volume tempest test :

tempest: configure compute-feature-enabled.swap_volume if libvirt
https://review.openstack.org/#/c/374373/

http://logs.openstack.org/73/374373/3/check/gate-tempest-dsvm-neutron-
full-ubuntu-
xenial/961698c/logs/screen-n-cpu.txt.gz#_2016-11-18_16_11_39_759

2016-11-18 16:11:39.759 4511 ERROR root [req-f40054e1-f18d-478a-
ae14-9c738bb961f2 tempest-TestVolumeSwap-1057055027 tempest-
TestVolumeSwap-1057055027] Original exception being dropped: ['Traceback
(most recent call last):\n', '  File
"/opt/stack/new/nova/nova/virt/libvirt/driver.py", line 1228, in
_swap_volume\ndev.abort_job(pivot=True)\n', '  File
"/opt/stack/new/nova/nova/virt/libvirt/guest.py", line 647, in
abort_job\nself._guest._domain.blockJobAbort(self._disk,
flags=flags)\n', '  File "/usr/local/lib/python2.7/dist-
packages/eventlet/tpool.py", line 186, in doit\nresult =
proxy_call(self._autowrap, f, *args, **kwargs)\n', '  File
"/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 144, in
proxy_call\nrv = execute(f, *args, **kwargs)\n', '  File
"/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 125, in
execute\nsix.reraise(c, e, tb)\n', '  File "/usr/local/lib/python2.7
/dist-packages/eventlet/tpool.py", line 83, in tworker\nrv =
meth(*args, **kwargs)\n', '  File "/usr/local/lib/python2.7/dist-
packages/libvirt.py", line 739, in blockJobAbort\nif ret == -1:
raise libvirtError (\'virDomainBlockJobAbort() failed\', dom=self)\n',
"libvirtError: block copy still active: disk 'vdb' not ready for pivot
yet\n"]

As discussed in bug#1630600 and at length in RHBZ#1382165 the issue here
is that QEMU reports the progress of the block job as complete
(status.cur == status.end) _before_ updating the ready field of the
block job. This causes the following attempt to pivot to fail.

Nova should attempt to use the ready field of the block job when
available (libvirt >1.2.18) to ensure that we are able to pivot.

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

Title:
  libvirtError: block copy still active: disk 'vdb' not ready for pivot
  yet

Status in OpenStack Compute (nova):
  New

Bug description:
  This is an additional corner case for swap_volume not covered by
  bug#1630600.

  The following failure is taken from the devstack change enabling the
  new swap_volume tempest test :

  tempest: configure compute-feature-enabled.swap_volume if libvirt
  https://review.openstack.org/#/c/374373/

  http://logs.openstack.org/73/374373/3/check/gate-tempest-dsvm-neutron-
  full-ubuntu-
  xenial/961698c/logs/screen-n-cpu.txt.gz#_2016-11-18_16_11_39_759

  2016-11-18 16:11:39.759 4511 ERROR root [req-f40054e1-f18d-478a-
  ae14-9c738bb961f2 tempest-TestVolumeSwap-1057055027 tempest-
  TestVolumeSwap-1057055027] Original exception being dropped:
  ['Traceback (most recent call last):\n', '  File
  "/opt/stack/new/nova/nova/virt/libvirt/driver.py", line 1228, in
  _swap_volume\ndev.abort_job(pivot=True)\n', '  File
  "/opt/stack/new/nova/nova/virt/libvirt/guest.py", line 647, in
  abort_job\nself._guest._domain.blockJobAbort(self._disk,
  flags=flags)\n', '  File "/usr/local/lib/python2.7/dist-
  packages/eventlet/tpool.py", line 186, in doit\nresult =
  proxy_call(self._autowrap, f, *args, **kwargs)\n', '  File
  "/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 144,
  in proxy_call\nrv = execute(f, *args, **kwargs)\n', '  File
  "/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 125,
  in execute\nsix.reraise(c, e, tb)\n', '  File
  "/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 83,
  in tworker\nrv = meth(*args, **kwargs)\n', '  File
  "/usr/local/lib/python2.7/dist-packages/libvirt.py", line 739, in
  blockJobAbort\nif ret == -1: raise libvirtError
  (\'virDomainBlockJobAbort() failed\', dom=self)\n', "libvirtError:
  block copy still active: disk 'vdb' not ready for pivot yet\n"]

  As discussed in bug#1630600 and at length in RHBZ#1382165 the issue
  here is that QEMU reports the progress of the block job as complete
  (status.cur == status.end) _before_ updating the ready field of the
  block job. This causes the following attempt to pivot to fail.

  Nova should attempt to use the ready field of the block job when
  available (libvirt >1.2.18) to ensure that we are able to pivot.

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

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

[Yahoo-eng-team] [Bug 1604397] Re: [SRU] python-swiftclient is missing in requirements.txt (for glare)

[Ryan Beisner]

This bug was fixed in the package python-glance-store - 0.18.0-0ubuntu1.1~cloud0
---

 python-glance-store (0.18.0-0ubuntu1.1~cloud0) xenial-newton; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 python-glance-store (0.18.0-0ubuntu1.1) yakkety; urgency=medium
 .
   [ Corey Bryant ]
   * d/control: Add run-time dependency for python-swiftclient (LP: #1604397).
   * d/p/drop-enum34.patch: Fix python3 test failures.
 .
   [ Thomas Goirand ]
   * Fixed enum34 runtime depends.


** Changed in: cloud-archive
   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/1604397

Title:
  [SRU] python-swiftclient is missing in requirements.txt (for glare)

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in Glance:
  New
Status in python-glance-store package in Ubuntu:
  Fix Released
Status in python-glance-store source package in Yakkety:
  Fix Released
Status in python-glance-store source package in Zesty:
  Fix Released

Bug description:
  [Description]
  [Test Case]
  I'm using UCA glance packages (version "13.0.0~b1-0ubuntu1~cloud0").
  And I've got this error:
  <30>Jul 18 16:03:45 node-2 glance-glare[17738]: ERROR: Store swift could not 
be configured correctly. Reason: Missing dependency python_swiftclient.

  Installing "python-swiftclient" fix the problem.

  In master
  (https://github.com/openstack/glance/blob/master/requirements.txt)
  package "python-swiftclient" is not included in requirements.txt. So
  UCA packages don't have proper dependencies.

  I think requirements.txt should be updated (add python-swiftclient
  there). This change should affect UCA packages.

  [Regression Potential]
  Minimal as this just adds a new dependency.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1604397/+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 1643013] [NEW] admin dashboard policy check wrong

[David Lyle]

Public bug reported:

The addition of all the hardcoded policy rules in dashboards/admin/dashboard.py 
is unnecessary and actually wrong because it imposes policy based on content 
for panels that may be disabled. The functionality is actually already built in 
and designed to be dynamic, see: 
https://github.com/openstack/horizon/blob/master/horizon/base.py#L648
where the panels are iterated over to check for policy.

** Affects: horizon
 Importance: High
 Assignee: David Lyle (david-lyle)
 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/1643013

Title:
  admin dashboard policy check wrong

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  The addition of all the hardcoded policy rules in 
dashboards/admin/dashboard.py is unnecessary and actually wrong because it 
imposes policy based on content for panels that may be disabled. The 
functionality is actually already built in and designed to be dynamic, see: 
https://github.com/openstack/horizon/blob/master/horizon/base.py#L648
  where the panels are iterated over to check for policy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1643013/+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 1643009] [NEW] ceilometer policy check is incorrect

[David Lyle]

Public bug reported:

The policy in the admin dashboard includes ceilometer incorrectly.
Ceilometer policy is a different beast and should not be treated the
same way. Also, ceilometer content is deprecated and disabled by default
and about to be removed.

** Affects: horizon
 Importance: Medium
 Assignee: David Lyle (david-lyle)
 Status: In Progress


** Tags: ceilometer newton-backport-potential

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

Title:
  ceilometer policy check is incorrect

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  The policy in the admin dashboard includes ceilometer incorrectly.
  Ceilometer policy is a different beast and should not be treated the
  same way. Also, ceilometer content is deprecated and disabled by
  default and about to be removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1643009/+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 1642969] Re: npm tests failing upstream

[Rob Cresswell]

** Changed in: horizon
   Status: Confirmed => Fix Released

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

Title:
  npm tests failing upstream

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  horizon.framework.util.filters simpleDate returns the expected time FAILED
Expected '24/06/2016, 05:19:07' to be '6/24/2016, 4:19:07 AM'.
at Object. (framework/util/filters/filters.spec.js:52:57)

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1642969/+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 1642419] Re: GPU Passthrough isn't working

[Michał Jastrzębski]

** Also affects: kolla-ansible
   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/1642419

Title:
  GPU Passthrough isn't working

Status in kolla-ansible:
  New
Status in OpenStack Compute (nova):
  New

Bug description:
  Hi,
  I cannot get IOMMU working on my Openstack cloud. Everytime I launch an 
instance with one gpu I get this error complaining that host doesn't have the 
requested feature.

  Message
  Exceeded maximum number of retries. Exceeded max scheduling attempts 10 for 
instance 769a2108-9a53-4cf5-9055-82411ce5cafd. Last exception: internal error: 
process exited while connecting to monitor: warning: host doesn't support 
requested feature: CPUID.0
  Code
  500
  Details
  File 
"/var/lib/kolla/venv/local/lib/python2.7/site-packages/nova/conductor/manager.py",
 line 480, in build_instances filter_properties, instances[0].uuid) File 
"/var/lib/kolla/venv/local/lib/python2.7/site-packages/nova/scheduler/utils.py",
 line 184, in populate_retry raise exception.MaxRetriesExceeded(reason=msg)

  Here is the log from nova-compute:
  http://paste.openstack.org/show/589527/

  And here is a log from nova-scheduler:
  http://paste.openstack.org/show/589528/

  
  I'm running Openstack Kolla v3.0.1 on an i7 4790k. My GPU is Nvidia GTX 970 
(that I want to passthrough) and my motherboard is Maximus VI Extreme.

  IOMMU has worked on this setup in the past on Arch Linux.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kolla-ansible/+bug/1642419/+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 1641623] Re: keystone-manage doctor needs developer docs

[OpenStack Infra]

Reviewed:  https://review.openstack.org/399163
Committed: 
https://git.openstack.org/cgit/openstack/keystone/commit/?id=98b3109324d990b54c10e950d4c76fe536d27adf
Submitter: Jenkins
Branch:master

commit 98b3109324d990b54c10e950d4c76fe536d27adf
Author: Lance Bragstad 
Date:   Thu Nov 17 18:02:38 2016 +

Add developer docs for keystone-manage doctor

``keyestone-manage doctor`` is a thing, but we don't really provide
any sort of developer documentation on how to write checks for it. We
should have some developer docs that describe the basic steps for
writing new symptoms ``doctor`` should check for.

Change-Id: I98171d5a81cab10020cbaa166bc649bacf7d5a67
Closes-Bug: 1641623


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

Title:
  keystone-manage doctor needs developer docs

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  There are no developer docs on how to create a new doctor check, or
  how the existing ones work. They should be added to a new section in
  the "developer docs" here:
  http://docs.openstack.org/developer/keystone/#developers-documentation

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1641623/+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 1633878] Re: nova boot error

[jichenjc]

liberty is EOL, you log shows

2016-10-16 20:37:11.129 4043 ERROR nova.api.openstack.extensions "No 
sql_connection parameter is established")
2016-10-16 20:37:11.129 4043 ERROR nova.api.openstack.extensions 
CantStartEngineError: No sql_connection parameter is established

seems you are missing configuration

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

Title:
   nova boot error

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Hello,

   nova boot --flavor m1.tiny --image cirros --nic 
net-id=0d88f440-038f-442a-b37d-c7cc0f994838 \
  >   --security-group default --key-name mykey public-instance
  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-72511dda-de6b-4ed6-97cd-a95e3ba093ad)

  
  Ubuntu 14.04 and liberty

  Please help me in fixing the issue and let me know if more info
  required. Thank you

  Best regards,
  Dhanabalan

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1633878/+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 1642988] [NEW] Avoid encoding of project id in fernet tokens

[Jose Castro Leon]

Public bug reported:

The proposal is to allow an operator to disable the encoding of the
project_id in fernet via a configuration setting. In this way operators
that have project ids in a different uuid format than the hex format,
can opt-out for the try/catch conversion with uuid resulting in a valid
encoding/decoding of this information inside the fernet token. The
configuration setting will be disabled by default, not modifying the
default behavior.

** Affects: keystone
 Importance: Undecided
 Assignee: Jose Castro Leon (jose-castro-leon)
 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/1642988

Title:
  Avoid encoding of project id in fernet tokens

Status in OpenStack Identity (keystone):
  In Progress

Bug description:
  The proposal is to allow an operator to disable the encoding of the
  project_id in fernet via a configuration setting. In this way
  operators that have project ids in a different uuid format than the
  hex format, can opt-out for the try/catch conversion with uuid
  resulting in a valid encoding/decoding of this information inside the
  fernet token. The configuration setting will be disabled by default,
  not modifying the default behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1642988/+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 1642500] Re: nova boot min_count and max_count not limited by neutron port quota

[jichenjc]

liberty is EOL, and you may refer to this change for further info

commit de1583b09c73e78772afb145c6f7cad052c7ffe5
Author: Roman Podoliaka 
Date:   Mon Jan 18 16:40:49 2016 +0200

Issue an info log msg when port quota is exceeded

When booting multiple instances at once using max_count it's possible
to exceed the port quota in Neutron. Currently, we proceed with
booting min(quota_value, max_count) number of instances and only
issue a debug message to Nova logs. It may be unclear to an operator,
why a fewer number of VMs were booted, and there will be nothing
useful in logs, if debug wasn't enabled.

Issue an info level log message instead, so that it's visible in
production logs without debug logging enabled (oslo.log now defaults
to verbose=True).

TrivialFix

Change-Id: I1e5edf17ce7d5a3bc2ac9403c7a8d492de274789


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

Title:
  nova boot min_count and max_count not limited by neutron port quota

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

Bug description:
  openstack-liberty

  1) set user quota:
  neutron-port:  10（4 used by network:router_interface and network:dhcp）
  nova instance: 10
  nova cores:10
  nova rams: 51200M

  2) want to create 10 vms in a request
  # nova boot --flavor m1.tiny --image xxx --min-count 10 --max-count 10 --nic 
net-id=yyy instance

  
  i thought nova boot would fail because only 6 ports left. Actually, 6 
instances are created and no error happened.

  is it reasonable?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1642500/+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 1634746] Re: RevokeEvent.to_dict() is very slow

[Richard]

** Changed in: keystone
 Assignee: (unassigned) => Richard (csravelar)

** Changed in: keystone
   Status: New => 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/1634746

Title:
  RevokeEvent.to_dict() is very slow

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  When our keystone to valid token , it cost too much time on function
  check_revocation.

  In the path /keystone/revoke/backends/sql.py  func list_events()

  >
  events = [revoke_model.RevokeEvent(**e.to_dict()) for e in query]

  It cost about 3 second and our database on revocation_event table has
  38596 row.

  Query sql from this table cost 0.01 second,but transfer this to a dict
  cost 3s.

  ---
  mysql> select count(*) from revocation_event;   
  +--+
  | count(*) |
  +--+
  |38596 |
  +--+

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1634746/+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 1642985] [NEW] Support for arrays of entities in endpoint group definition

[Jose Castro Leon]

Public bug reported:

The proposal is to allow arrays of entities, so a deployer can aggregate
several endpoints with a single endpoint group. When you have multiple
services with different ids, you can't aggregate them into a single
endpoint group. Then if you have a large deployment it is very
inconvenient to add the endpoint filters one by one into a newly created
project.

** Affects: keystone
 Importance: Undecided
 Assignee: Jose Castro Leon (jose-castro-leon)
 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/1642985

Title:
  Support for arrays of entities in endpoint group definition

Status in OpenStack Identity (keystone):
  In Progress

Bug description:
  The proposal is to allow arrays of entities, so a deployer can
  aggregate several endpoints with a single endpoint group. When you
  have multiple services with different ids, you can't aggregate them
  into a single endpoint group. Then if you have a large deployment it
  is very inconvenient to add the endpoint filters one by one into a
  newly created project.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1642985/+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 1642969] [NEW] npm tests failing upstream

[Rob Cresswell]

Public bug reported:

horizon.framework.util.filters simpleDate returns the expected time FAILED
Expected '24/06/2016, 05:19:07' to be '6/24/2016, 4:19:07 AM'.
at Object. (framework/util/filters/filters.spec.js:52:57)

** Affects: horizon
 Importance: High
 Assignee: Rob Cresswell (robcresswell)
 Status: New

** Changed in: horizon
Milestone: None => ocata-1

** Changed in: horizon
 Assignee: (unassigned) => Rob Cresswell (robcresswell)

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

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

Title:
  npm tests failing upstream

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  horizon.framework.util.filters simpleDate returns the expected time FAILED
Expected '24/06/2016, 05:19:07' to be '6/24/2016, 4:19:07 AM'.
at Object. (framework/util/filters/filters.spec.js:52:57)

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1642969/+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 1606500] Re: [OSSA 2016-013] Heat: template source URL allows network port scan (CVE-2016-9185)

[Tristan Cacqueray]

** Summary changed:

- Heat: template source URL allows network port scan (CVE-2016-9185)
+ [OSSA 2016-013] Heat: template source URL allows network port scan 
(CVE-2016-9185)

** Changed in: ossa
   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/1606500

Title:
  [OSSA 2016-013] Heat: template source URL allows network port scan
  (CVE-2016-9185)

Status in heat:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Invalid
Status in OpenStack Security Advisory:
  Fix Released

Bug description:
  Launching a new Heat stack and giving the template from an URL like
  http://localhost:22

  Results in an error message like:

  ERROR: Could not retrieve template: Failed to retrieve template:
  ('Connection aborted.', BadStatusLine('SSH-2.0-OpenSSH_6.6.1\r\n',))

  This is a security issue as it allows users to scan the network for
  listening ports.

  heat CLI does not allow that:

  heat stack-create -u http://localhost:22 test
  [Errno 104] Connection reset by peer

To manage notifications about this bug go to:
https://bugs.launchpad.net/heat/+bug/1606500/+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 1637214] Re: [api-ref] include changelog from v3.0 -> 3.7

[OpenStack Infra]

Reviewed:  https://review.openstack.org/399301
Committed: 
https://git.openstack.org/cgit/openstack/keystone/commit/?id=f4a30aac662a36cfa7e35737fd5fce4a14860518
Submitter: Jenkins
Branch:master

commit f4a30aac662a36cfa7e35737fd5fce4a14860518
Author: Steve Martinelli 
Date:   Thu Nov 17 18:59:00 2016 -0500

[api] add changelog from 3.0 -> 3.7

This section was missed from the migration (from specs to api-ref).

Change-Id: Id7243ea0f2dbfbb4b579489fdb4f75c7a4b7b940
Closes-Bug: 1637214


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

Title:
  [api-ref] include changelog from v3.0 -> 3.7

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  Include https://github.com/openstack/keystone-
  specs/blob/master/attic/v3/identity-api-v3.rst in the file
  https://raw.githubusercontent.com/openstack/keystone/master/api-
  ref/source/v3/index.rst

  3.7 == Newton, work your way back from there.

  
  ---
  Release: v3.7 on 'Sat Oct 22 01:20:06 2016, commit b8435cc'
  SHA: 
  Source: 
http://git.openstack.org/cgit/openstack/keystone/tree/api-ref/source/v3/index.rst
  URL: http://developer.openstack.org/api-ref/identity/v3/index.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1637214/+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 1642935] [NEW] can't boot lxd container from volume

[Ondrej Linha]

Public bug reported:

lxd container initalization failed when booting from block device (lvm)
 
* ubutnu server 16.04 lts
** nova-compute-lxd 14.0.0-0ubuntu1~cloud0 
** python-nova-lxd 14.0.0-0ubuntu1~cloud0  

2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager 
[req-9225eff7-0bc0-488e-aa26-f3961f5e57ae 3a3320729a2346a0ae4f44d122fc0c2c 
bae1c166a41547c289fe7ae077272648 - - -] [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] Instance failed to spawn
2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] Traceback (most recent call last):
2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2078, in 
_build_resources
2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] yield resources
2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1920, in 
_build_and_run_instance
2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] block_device_info=block_device_info)
2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/lxd/driver.py", line 274, in spawn
2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] self.setup_image(context, instance, 
image_meta)
2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/lxd/driver.py", line 1177, in 
setup_image
2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] 
container_utils.get_container_rootfs_image(image_meta)
2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/lxd/utils.py", line 30, in 
get_container_rootfs_image
2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] return os.path.join(BASE_DIR, 
'%s-rootfs.tar.gz' % image_meta.id)
2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 67, in 
getter
2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] self.obj_load_attr(name)
2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 632, in 
obj_load_attr
2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] _("Cannot load '%s' in the base 
class") % attrname)
2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] NotImplementedError: Cannot load 'id' in 
the base class

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

Title:
  can't boot lxd container from volume

Status in OpenStack Compute (nova):
  New

Bug description:
  lxd container initalization failed when booting from block device (lvm)
   
  * ubutnu server 16.04 lts
  ** nova-compute-lxd 14.0.0-0ubuntu1~cloud0 
  ** python-nova-lxd 14.0.0-0ubuntu1~cloud0  

  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager 
[req-9225eff7-0bc0-488e-aa26-f3961f5e57ae 3a3320729a2346a0ae4f44d122fc0c2c 
bae1c166a41547c289fe7ae077272648 - - -] [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] Instance failed to spawn
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] Traceback (most recent call last):
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2078, in 
_build_resources
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] yield resources
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1920, in 
_build_and_run_instance
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] block_device_info=block_device_info)
  2016-11-18 12:20:58.308 20325 ERROR 

[Yahoo-eng-team] [Bug 1642918] [NEW] floating-ip nova notification is broken

[YAMAMOTO Takashi]

Public bug reported:

I1d7d4b80ee77deefce18df22f76cab81750c0397 seems to assume api resource names
matches with callbacks resource names.
unfortunately it isn't the case for floating-ip.

** Affects: neutron
 Importance: Undecided
 Assignee: YAMAMOTO Takashi (yamamoto)
 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/1642918

Title:
  floating-ip nova notification is broken

Status in neutron:
  In Progress

Bug description:
  I1d7d4b80ee77deefce18df22f76cab81750c0397 seems to assume api resource names
  matches with callbacks resource names.
  unfortunately it isn't the case for floating-ip.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1642918/+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 1642910] [NEW] Create volume from snapshot : Get mismatched form after a invalid submission

[lijunli]

Public bug reported:

Version: Mitaka

Steps to reproduce:

1. Go to Project -> Volumes Snapshots
2. Pick an existing volume, click "Create Volume" and get a modal form
3. Enter an invalid value(for example, a value which is smaller than the 
original size) for "Size(Gib)" field and click "Create Volume"
4. Get another modal form with a warning message "The volume size cannot be 
less than the 
snapshot size(2GiB)."


Expected:
4. You should get the same modal form with step 2 except the warning message.

Actually:
The forms in step 2 and 4 are different.

** Affects: horizon
 Importance: Undecided
 Assignee: lijunli (lijunli)
 Status: New

** Attachment added: "Forms in step 2 and step 4"
   
https://bugs.launchpad.net/bugs/1642910/+attachment/4779197/+files/Form_in_step_2.jpg

** Changed in: horizon
 Assignee: (unassigned) => lijunli (lijunli)

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

Title:
  Create volume from snapshot : Get mismatched form after a invalid
  submission

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Version: Mitaka

  Steps to reproduce:

  1. Go to Project -> Volumes Snapshots
  2. Pick an existing volume, click "Create Volume" and get a modal form
  3. Enter an invalid value(for example, a value which is smaller than the 
original size) for "Size(Gib)" field and click "Create Volume"
  4. Get another modal form with a warning message "The volume size cannot be 
less than the 
  snapshot size(2GiB)."

  
  Expected:
  4. You should get the same modal form with step 2 except the warning message.

  Actually:
  The forms in step 2 and 4 are different.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1642910/+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 1642890] [NEW] Please backport LP 1602057 to Mitaka

[Serhii Ovsianikov]

Public bug reported:

Please backport the fix of the bug
https://bugs.launchpad.net/nova/+bug/1602057 "(libvirt) KeyError
updating resources for some node, guest.uuid is not in BDM list" into
the MOS-9.0/9.1 (Mitaka).

** Affects: mos
 Importance: Undecided
 Status: New


** Tags: ct2 customer-found support

** Project changed: nova => mos

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

Title:
  Please backport LP 1602057 to Mitaka

Status in Mirantis OpenStack:
  New

Bug description:
  Please backport the fix of the bug
  https://bugs.launchpad.net/nova/+bug/1602057 "(libvirt) KeyError
  updating resources for some node, guest.uuid is not in BDM list" into
  the MOS-9.0/9.1 (Mitaka).

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