date:20181121

Public bug reported:


Description:
Plug/unplug the audio jack external speaker that connected to BME Dock's 
Headset port, and the external speakers output noise sound.

Expected Behavior:
External speakers not output noise when plug/unplug on BME Dock

Severity:
Sev-2
P3
C3
L1

Test environment:
1. Project: Northbay 13
 2. BIOS: 0.4.1
 3. Driver list:V27
 4. OS:CI Ubuntu 18.04
 5. Dock info: BME dock(REV-A05 Dock-168 FW:0.1.17)
 6. Speaker: Dell SPEAKER-20 (REV-A00) Dell 2.0speaker (AE215) AE215

Notes:
1. VP on Salomon dock
2. VP on IE Dock
3. Line-out port can't detect external device

Cross platform:
1. N/A

Test Case: 
[CPV-TC-4641][WIS-TC-4201] Linux_NB_BME-Wired-Dock-The I/O Port Functionality 
Test   Step 11
 
Steps to Reproduce : 
1. Install Ubuntu OS 18.04.1 LTS
2. Boot to OS, dock the BME dock to SUT.
3. Plug/unplug external speaketr to audio port of BME dock.
4. Find the external speaker output noise--->Problem(refer to video)

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: north-bay-13

** Attachment added: "Noise.mp4"
   https://bugs.launchpad.net/bugs/1804559/+attachment/5215149/+files/Noise.mp4

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

Title:
  Linux, Ubuntu, 18.04, CI, NB13, External speaker output noise when
  plug/unplug on BME dock.(FR:100%)

Status in Glance:
  New

Bug description:
  
  Description:
  Plug/unplug the audio jack external speaker that connected to BME Dock's 
Headset port, and the external speakers output noise sound.

  Expected Behavior:
  External speakers not output noise when plug/unplug on BME Dock

  Severity:
  Sev-2
  P3
  C3
  L1

  Test environment:
  1. Project: Northbay 13
   2. BIOS: 0.4.1
   3. Driver list:V27
   4. OS:CI Ubuntu 18.04
   5. Dock info: BME dock(REV-A05 Dock-168 FW:0.1.17)
   6. Speaker: Dell SPEAKER-20 (REV-A00) Dell 2.0speaker (AE215) AE215

  Notes:
  1. VP on Salomon dock
  2. VP on IE Dock
  3. Line-out port can't detect external device

  Cross platform:
  1. N/A

  Test Case: 
  [CPV-TC-4641][WIS-TC-4201] Linux_NB_BME-Wired-Dock-The I/O Port Functionality 
Test   Step 11
   
  Steps to Reproduce : 
  1. Install Ubuntu OS 18.04.1 LTS
  2. Boot to OS, dock the BME dock to SUT.
  3. Plug/unplug external speaketr to audio port of BME dock.
  4. Find the external speaker output noise--->Problem(refer to video)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1804559/+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 1795992] Re: retry_select_destinations decorator can make a mess with allocations in placement in a large multi-create request

Reviewed:  https://review.openstack.org/607735
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=5af632e9cab670cc25c2f627bb0d4c0a02258277
Submitter: Zuul
Branch:master

commit 5af632e9cab670cc25c2f627bb0d4c0a02258277
Author: Matt Riedemann 
Date:   Wed Oct 3 18:57:45 2018 -0400

Use long_rpc_timeout in select_destinations RPC call

Conductor RPC calls the scheduler to get hosts during
server create, which in a multi-create request with a
lot of servers and the default rpc_response_timeout, can
trigger a MessagingTimeout. Due to the old
retry_select_destinations decorator, conductor will retry
the select_destinations RPC call up to max_attempts times,
so thrice by default. This can clobber the scheduler and
placement while the initial scheduler worker is still
trying to process the beefy request and allocate resources
in placement.

This has been recreated in a devstack test patch [1] and
shown to fail with 1000 instances in a single request with
the default rpc_response_timeout of 60 seconds. Changing the
rpc_response_timeout to 300 avoids the MessagingTimeout and
retry loop.

Since Rocky we have the long_rpc_timeout config option which
defaults to 1800 seconds. The RPC client can thus be changed
to heartbeat the scheduler service during the RPC call every
$rpc_response_timeout seconds with a hard timeout of
$long_rpc_timeout. That change is made here.

As a result, the problematic retry_select_destinations
decorator is also no longer necessary and removed here. That
decorator was added in I2b891bf6d0a3d8f45fd98ca54a665ae78eab78b3
and was a hack for scheduler high availability where a
MessagingTimeout was assumed to be a result of the scheduler
service dying so retrying the request was reasonable to hit
another scheduler worker, but is clearly not sufficient
in the large multi-create case, and long_rpc_timeout is a
better fit for that HA type scenario to heartbeat the scheduler
service.

[1] https://review.openstack.org/507918/

Change-Id: I87d89967bbc5fbf59cf44d9a63eb6e9d477ac1f3
Closes-Bug: #1795992


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

Title:
  retry_select_destinations decorator can make a mess with allocations
  in placement in a large multi-create request

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) rocky series:
  Triaged

Bug description:
  There is no rate-limiting on the min/max count parameters when
  creating multiple servers in a single request besides the 'instances'
  quota that the tenant has. However, some tenants could have a
  relatively high instances quota (100 or more).

  Because of the retry_select_destinations decorator in the scheduler
  RPC API client code:

  
https://github.com/openstack/nova/blob/cce3208cc28268e4b50e155c205bcab9f1da2a4b/nova/scheduler/utils.py#L921

  It can be relatively easy with a default rpc_response_timeout value to
  cause the scheduler to retry a select_destinations call with a large
  number of instances in a multi-create request to fail with a
  MessagingTimeout and retry, which will make the scheduler process the
  same set of instances and potentially create duplicate allocations in
  placement, and subsequently fail to cleanup allocations because the
  consumers generation has changed, as seen in the logs from this
  recreate patch:

  https://review.openstack.org/#/c/507918/

  http://logs.openstack.org/18/507918/8/check/tempest-
  
full/a9f3849/controller/logs/screen-n-sch.txt.gz?level=TRACE#_Oct_02_23_29_12_475481

  Oct 02 23:29:12.377430 ubuntu-xenial-limestone-regionone-0002536892 
nova-scheduler[22653]: WARNING nova.scheduler.client.report [None 
req-f4fe43ea-d117-4b7d-a3a4-23dcb59f3058 admin admin] Unable to submit 
allocation for instance 63ae7544-7693-4749-886b-024dc93f09f9 (409 {"errors": 
[{"status": 409, "request_id": "req-0e85117c-871c-46c2-9e01-53c84e811b44", 
"code": "placement.undefined_code", "detail": "There was a conflict when trying 
to complete your request.\n\n Unable to allocate inventory: Unable to create 
allocation for 'MEMORY_MB' on resource provider 
'b7709a93-f14c-42ed-addf-9736fb721728'. The requested amount would exceed the 
capacity.  ", "title": "Conflict"}]})
  Oct 02 23:29:12.472553 ubuntu-xenial-limestone-regionone-0002536892 
nova-scheduler[22653]: WARNING nova.scheduler.client.report [None 
req-f4fe43ea-d117-4b7d-a3a4-23dcb59f3058 admin admin] Unable to delete 
allocation for instance 6962f92b-7dca-4912-aeb2-dcae03c4b52e: (409 {"errors": 
[{"status": 409, "request_id": "req-13df41fe-cb55-49f1-a998-09b34e48f05b", 
"code": "placement.concurrent_update", "detail": "There was a conflict

[Yahoo-eng-team] [Bug 1801919] Re: brctl is obsolete use ip

Reviewed:  https://review.openstack.org/617836
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=2572c158f5290ddc3bc2e4f06ecbd4768c82eee4
Submitter: Zuul
Branch:master

commit 2572c158f5290ddc3bc2e4f06ecbd4768c82eee4
Author: Brian Haley 
Date:   Tue Nov 13 15:54:29 2018 -0500

Change to use iproute2 instead of brctl

brctl is being deprecated in some Linux distros, so
change neutron to start using iproute2 commands or
the pyroute2 library where possible.

Added create() to IpLinkCommand class to allow usage
of pyroute2 for bridge creation.

Change-Id: If679e79fa3242ee1cd8610b5525deca35b41c87e
Closes-bug: #1801919


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

Title:
  brctl is obsolete  use ip

Status in devstack:
  In Progress
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  bridge-utils (brctl) is obsolete, no modern software should depend on it.
  Used in: neutron/agent/linux/bridge_lib.py

  http://man7.org/linux/man-pages/man8/brctl.8.html

  Please use `ip` for basic bridge operations,
  than we can drop one obsolete dependency..

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1801919/+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 1801702] Re: Spawn may fail when cache=none on block device with logical block size > 512

Reviewed:  https://review.openstack.org/616580
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=14d98ef1b48ca7b2ea468a8f1ec967b954955a63
Submitter: Zuul
Branch:master

commit 14d98ef1b48ca7b2ea468a8f1ec967b954955a63
Author: Jens Harbott 
Date:   Thu Nov 8 15:06:26 2018 +

Make supports_direct_io work on 4096b sector size

The current check uses an alignment of 512 bytes and will fail when the
underlying device has sectors of size 4096 bytes, as is common e.g. for
NVMe disks. So use an alignment of 4096 bytes, which is a multiple of
512 bytes and thus will cover both cases.

Change-Id: I5151ae01e90506747860d9780547b0d4ce91d8bc
Closes-Bug: 1801702
Co-Authored-By: Alexandre Arents 


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

Title:
  Spawn may fail when cache=none on block device with logical block size
  > 512

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  Triaged
Status in OpenStack Compute (nova) pike series:
  In Progress
Status in OpenStack Compute (nova) queens series:
  In Progress
Status in OpenStack Compute (nova) rocky series:
  In Progress

Bug description:
  Description
  ===
  When we spawn instances without cache enabled (cache='none') on a file system
  there a check in nova code that test if file system support direct IO:
  https://github.com/openstack/nova/blob/master/nova/privsep/utils.py#L34
  Because this test use 512b alignment size it seems to failed on newer block 
device that have
  logical block size > 512b like nvme:

  parted /dev/nvme0n1 print | grep "Sector size"
  Sector size (logical/physical): 4096B/4096B

  reason should be that alignement size of direct io must be a multiple
  of logical block size of underlying device (not of fs block size) as
  explain here:

  http://man7.org/linux/man-pages/man2/open.2.html
   O_DIRECT
 ...
 Under Linux 2.4, transfer sizes, and the alignment of the user buffer
 and the file offset must all be multiples of the logical block size
 of the filesystem.  Since Linux 2.6.0, alignment to the logical block
 size of the underlying storage (typically 512 bytes) suffices

  Because this test failed, it fallbacks value of cache to "writethrough" which 
have following consequences:
  1) qemu run without direct io even device/fs support but with higher block 
size
  2) qemu failed to start because cache=writethrough may conflict with other 
dev paramer like "io=native": with the following message:

  2018-08-22 20:50:41.226 80512 ERROR oslo_messaging.rpc.server   File 
"/usr/lib/python2.7/dist-packages/libvirt.py", line 1065, in createWithFlags
  2018-08-22 20:50:41.226 80512 ERROR oslo_messaging.rpc.server if ret == 
-1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self)
  2018-08-22 20:50:41.226 80512 ERROR oslo_messaging.rpc.server libvirtError: 
unsupported configuration: native I/O needs either no disk cache or directsync 
cache mode, QEMU will fallback to aio=threads

  
  Steps to reproduce
  ==
  to reproduce spawn issue:
  having instances on fs with block device with logical block size > 512b 
(typically nvme with 4096 8192 sector size)
  nova.conf with:
  images_type=raw
  preallocate_images=space

  Solution
  
  Can we consider increasing align_size from 512b to 8192b as it will work on 
most cases?
  Is there any other reason to keep 512b ?

  Set it to 4096 or 8192 fix the issue in my environment.

  Environment
  ===
  I met the issue on newton, but same check with 512b exists on master.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1801702/+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 1803882] Re: Keystone – error message is not correct/clear in case when no “rule” is associated to user

2018-11-21 Thread Colleen Murphy

Using the --project flag with the openstack client sets the
default_project_id attribute of a user which was only used for the
keystone v2 API. With the v3 API (the only supported version) it's now
necessary to explicitly create the role assignment with

$ openstack role add --user new-user --project new-project member

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

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

Title:
  Keystone – error message is not correct/clear in case when no “rule”
  is associated to user

Status in OpenStack Identity (keystone):
  Invalid

Bug description:
  Keystone – error message is not correct/clear in case when no “rule”
  is associated to user

  Scenario:
  1) Source as admin user 
  . overcloudrc
  2) Create a new project
  openstack project create --description 'my new project' new-project --domain 
default
  3) Create user for previously created project
  openstack user create --project new-project --password PASSWORD new-user
  4) Copy overcloudrc content to userrc file and change
  cp overcloudrc userrc
  5) Change relevant for new-user values:
  export OS_USERNAME=new-user
  export OS_PASSWORD=PASSWORD
  export OS_PROJECT_NAME= new-project
  6) Save modified file and source now with this gile
  source userrc
  7) Execute some openstack command for example:
  openstack network list

  Actual Result:
  On CLI output the error which is shown to user is:
  The request you have made requires authentication. (HTTP 401) (Request-ID: 
req-373d8b48-15b7-4036-83d1-c82453584f15)

  In keystone log:
  /var/log/containers/keystone/keystone.log (5739, 5739)
  2018-11-18 15:09:15.902 35 WARNING keystone.common.wsgi 
[req-373d8b48-15b7-4036-83d1-c82453584f15 - - - - -] Authorization failed. The 
request you have made requires authentication. from 192.168.100.27: 
Unauthorized: The request you have made requires authentication.

  Expected Result:
  The real reason no rule is asociated to ‘new-user’ (or something like that) 
should be logged and prompted to user.
  Actual message we have is not relevant and not clear.

  Keystone logs attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1803882/+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 1803014] Re: The user setting page sets the "Items Per Page" minimum or maximum value, which affects the display of "Log Lines Per Instance"

Reviewed:  https://review.openstack.org/617419
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=a81098b1d3234760ac9aece2f43fb81cda511166
Submitter: Zuul
Branch:master

commit a81098b1d3234760ac9aece2f43fb81cda511166
Author: pengyuesheng 
Date:   Tue Nov 13 10:20:12 2018 +0800

fix the bug of checkSpinnerValue

The user setting page sets the "Items Per Page" minimum or maximum value,
which affects the display of "Log Lines Per Instance"

Change-Id: I087412272257b665b6ac1de6ba5eabd06f011e74
Closes-Bug: #1803014


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

Title:
  The user setting page sets the "Items Per Page" minimum or maximum
  value, which affects the display of "Log Lines Per Instance"

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  1. Open the user settings interface
  2.  Enter the minimum value 1 and press the Save button.
  3. The status of the minus button of  is disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1803014/+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 1789423] Re: Server operations fail to complete with versioned notifications if payload contains unset is_public field

Reviewed:  https://review.openstack.org/615134
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=c4f6b0bf6cc903cf52c4b238c3771604dda174b8
Submitter: Zuul
Branch:master

commit c4f6b0bf6cc903cf52c4b238c3771604dda174b8
Author: Mohammed Naser 
Date:   Fri Nov 2 12:21:26 2018 +0100

Default embedded instance.flavor.is_public attribute

It is possible that really old instances don't actually have this
attribute defined which can lead to raising exceptions when loading
their embedded flavors from the database.

This patch fixes this by defaulting these values to true if they
are not set.

Change-Id: If04cd802ce7184dc94f94804c743faebe0d4bd8c
Closes-Bug: #1789423


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

Title:
  Server operations fail to complete with versioned notifications if
  payload contains unset is_public field

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  Triaged
Status in OpenStack Compute (nova) pike series:
  In Progress
Status in OpenStack Compute (nova) queens series:
  In Progress
Status in OpenStack Compute (nova) rocky series:
  In Progress

Bug description:
  This is a follow up to bug 1739325 which fixed the scenario that the
  flavor.disabled field was missing from the embedded instance flavor.
  The same case occurs for the is_public field, so we should default
  that to True if it's not set in the embedded instance.flavor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1789423/+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 1804520] [NEW] Remove obsolete service provider policies from policy.v3cloudsample.json

Public bug reported:

Once support for scope types landed in the service provider API
policies, the policies in policy.v3cloudsample.json became obsolete
[0][1].

We should add formal protection for the policies with enforce_scope =
True in keystone.tests.unit.protection.v3 and remove the old policies
from the v3 sample policy file.

This will reduce confusion by having a true default policy for identity
providers.

[0] https://review.openstack.org/#/c/526173/
[1] 
https://git.openstack.org/cgit/openstack/keystone/tree/etc/policy.v3cloudsample.json?id=fb73912d87b61c419a86c0a9415ebdcf1e186927#n216

** Affects: keystone
 Importance: Medium
 Status: Triaged


** Tags: policy

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

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

** Tags added: policy

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

Title:
  Remove obsolete service provider policies from
  policy.v3cloudsample.json

Status in OpenStack Identity (keystone):
  Triaged

Bug description:
  Once support for scope types landed in the service provider API
  policies, the policies in policy.v3cloudsample.json became obsolete
  [0][1].

  We should add formal protection for the policies with enforce_scope =
  True in keystone.tests.unit.protection.v3 and remove the old policies
  from the v3 sample policy file.

  This will reduce confusion by having a true default policy for
  identity providers.

  [0] https://review.openstack.org/#/c/526173/
  [1] 
https://git.openstack.org/cgit/openstack/keystone/tree/etc/policy.v3cloudsample.json?id=fb73912d87b61c419a86c0a9415ebdcf1e186927#n216

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1804520/+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 1804522] [NEW] Service provider API doesn't use default roles

Public bug reported:

In Rocky, keystone implemented support to ensure at least three default
roles were available [0]. The service provider (federation) API doesn't
incorporate these defaults into its default policies [1], but it should.

[0] 
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html
[1] 
https://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/service_provider.py?id=fb73912d87b61c419a86c0a9415ebdcf1e186927

** Affects: keystone
 Importance: Medium
 Status: Triaged


** Tags: default-roles policy

** Tags added: default-roles policy

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

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

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

Title:
  Service provider API doesn't use default roles

Status in OpenStack Identity (keystone):
  Triaged

Bug description:
  In Rocky, keystone implemented support to ensure at least three
  default roles were available [0]. The service provider (federation)
  API doesn't incorporate these defaults into its default policies [1],
  but it should.

  [0] 
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html
  [1] 
https://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/service_provider.py?id=fb73912d87b61c419a86c0a9415ebdcf1e186927

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1804522/+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 1804521] [NEW] Mapping API doesn't use default roles

Public bug reported:

In Rocky, keystone implemented support to ensure at least three default
roles were available [0]. The federated mapping API doesn't incorporate
these defaults into its default policies [1], but it should.

[0] 
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html
[1] 
https://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/mapping.py?id=fb73912d87b61c419a86c0a9415ebdcf1e186927

** Affects: keystone
 Importance: Medium
 Status: Triaged


** Tags: default-roles policy

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

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

** Tags added: default-roles policy

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

Title:
  Mapping API doesn't use default roles

Status in OpenStack Identity (keystone):
  Triaged

Bug description:
  In Rocky, keystone implemented support to ensure at least three
  default roles were available [0]. The federated mapping API doesn't
  incorporate these defaults into its default policies [1], but it
  should.

  [0] 
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html
  [1] 
https://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/mapping.py?id=fb73912d87b61c419a86c0a9415ebdcf1e186927

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1804521/+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 1729933] Re: region update doesn't update extras

Reviewed:  https://review.openstack.org/517726
Committed: 
https://git.openstack.org/cgit/openstack/keystone/commit/?id=ef331f46b46b7b9705b2b4be0e62b0ac6a1e694e
Submitter: Zuul
Branch:master

commit ef331f46b46b7b9705b2b4be0e62b0ac6a1e694e
Author: David Lyle 
Date:   Fri Nov 3 14:50:58 2017 -0600

Region update extra support

The region update API currently does not allow for adding any
extra values via the update API. This effectively means that while
an extra can be set at create time, they cannot be altered once
set, nor can any additional values be added.

This patch add the missing inclusion of extra to the new ref.

Change-Id: I6e99764c0e360656ddbb47ebb23fe9576c97b99f
Closes-Bug: #1729933


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

Title:
  region update doesn't update extras

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  The region table contains an `extra` column.

  Although the API for regions supports setting `extra`. The update
  method does not support updating extras in the default sql driver
  backend. This effectively means that while an extra can be set at
  create time, they cannot be altered once set, nor can additional
  values be added.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1729933/+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 1804523] [NEW] Federated protocol API doesn't use default roles

Public bug reported:

In Rocky, keystone implemented support to ensure at least three default
roles were available [0]. The protocol (federation) API doesn't
incorporate these defaults into its default policies [1], but it should.

[0] 
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html
[1] 
https://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/protocol.py?id=fb73912d87b61c419a86c0a9415ebdcf1e186927

** Affects: keystone
 Importance: Medium
 Status: Triaged


** Tags: default-roles policy

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

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

** Tags added: default-roles policy

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

Title:
  Federated protocol API doesn't use default roles

Status in OpenStack Identity (keystone):
  Triaged

Bug description:
  In Rocky, keystone implemented support to ensure at least three
  default roles were available [0]. The protocol (federation) API
  doesn't incorporate these defaults into its default policies [1], but
  it should.

  [0] 
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html
  [1] 
https://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/protocol.py?id=fb73912d87b61c419a86c0a9415ebdcf1e186927

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1804523/+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 1804517] [NEW] Remove obsolete idp policies from policy.v3cloudsample.json

Public bug reported:

Once support for scope types landed in the identity provider API
policies, the policies in policy.v3cloudsample.json became obsolete
[0][1].

We should add formal protection for the policies with enforce_scope =
True in keystone.tests.unit.protection.v3 and remove the old policies
from the v3 sample policy file.

This will reduce confusion by having a true default policy for identity
providers.

[0] https://review.openstack.org/#/c/526145/
[1] 
https://git.openstack.org/cgit/openstack/keystone/tree/etc/policy.v3cloudsample.json?id=fb73912d87b61c419a86c0a9415ebdcf1e186927#n198

** Affects: keystone
 Importance: Medium
 Status: Triaged


** Tags: policy

** Tags added: policy

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

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

** Description changed:

  Once support for scope types landed in the identity provider API
  policies, the policies in policy.v3cloudsample.json became obsolete
  [0][1].
  
  We should add formal protection for the policies with enforce_scope =
  True in keystone.tests.unit.protection.v3 and remove the old policies
  from the v3 sample policy file.
  
- This will reduce confusion by having a true default policy for
- endpoints.
+ This will reduce confusion by having a true default policy for identity
+ providers.
  
  [0] https://review.openstack.org/#/c/526145/
  [1] 
https://git.openstack.org/cgit/openstack/keystone/tree/etc/policy.v3cloudsample.json?id=fb73912d87b61c419a86c0a9415ebdcf1e186927#n198

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

Title:
  Remove obsolete idp policies from policy.v3cloudsample.json

Status in OpenStack Identity (keystone):
  Triaged

Bug description:
  Once support for scope types landed in the identity provider API
  policies, the policies in policy.v3cloudsample.json became obsolete
  [0][1].

  We should add formal protection for the policies with enforce_scope =
  True in keystone.tests.unit.protection.v3 and remove the old policies
  from the v3 sample policy file.

  This will reduce confusion by having a true default policy for
  identity providers.

  [0] https://review.openstack.org/#/c/526145/
  [1] 
https://git.openstack.org/cgit/openstack/keystone/tree/etc/policy.v3cloudsample.json?id=fb73912d87b61c419a86c0a9415ebdcf1e186927#n198

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1804517/+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 1804518] [NEW] Remove obsolete protocol policies from policy.v3cloudsample.json

Public bug reported:

Once support for scope types landed in the protocol API policies, the
policies in policy.v3cloudsample.json became obsolete [0][1].

We should add formal protection for the policies with enforce_scope =
True in keystone.tests.unit.protection.v3 and remove the old policies
from the v3 sample policy file.

This will reduce confusion by having a true default policy for
protocols.

[0] https://review.openstack.org/#/c/526161/
[1] 
https://git.openstack.org/cgit/openstack/keystone/tree/etc/policy.v3cloudsample.json?id=fb73912d87b61c419a86c0a9415ebdcf1e186927#n204

** Affects: keystone
 Importance: Medium
 Status: Triaged


** Tags: policy

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

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

** Tags added: policy

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

Title:
  Remove obsolete protocol policies from policy.v3cloudsample.json

Status in OpenStack Identity (keystone):
  Triaged

Bug description:
  Once support for scope types landed in the protocol API policies, the
  policies in policy.v3cloudsample.json became obsolete [0][1].

  We should add formal protection for the policies with enforce_scope =
  True in keystone.tests.unit.protection.v3 and remove the old policies
  from the v3 sample policy file.

  This will reduce confusion by having a true default policy for
  protocols.

  [0] https://review.openstack.org/#/c/526161/
  [1] 
https://git.openstack.org/cgit/openstack/keystone/tree/etc/policy.v3cloudsample.json?id=fb73912d87b61c419a86c0a9415ebdcf1e186927#n204

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1804518/+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 1804516] [NEW] Identity provider API doesn't use default roles

Public bug reported:

In Rocky, keystone implemented support to ensure at least three default
roles were available [0]. The identity provider (federation) API doesn't
incorporate these defaults into its default policies [1], but it should.

[0] 
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html
[1] 
https://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/identity_provider.py?id=fb73912d87b61c419a86c0a9415ebdcf1e186927

** Affects: keystone
 Importance: Medium
 Status: Triaged


** Tags: default-roles policy

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

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

** Tags added: default-roles policy

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

Title:
  Identity provider API doesn't use default roles

Status in OpenStack Identity (keystone):
  Triaged

Bug description:
  In Rocky, keystone implemented support to ensure at least three
  default roles were available [0]. The identity provider (federation)
  API doesn't incorporate these defaults into its default policies [1],
  but it should.

  [0] 
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html
  [1] 
https://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/identity_provider.py?id=fb73912d87b61c419a86c0a9415ebdcf1e186927

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1804516/+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 1804519] [NEW] Remove obsolete mapping policies from policy.v3cloudsample.json

Public bug reported:

Once support for scope types landed in the mapping API policies, the
policies in policy.v3cloudsample.json became obsolete [0][1].

We should add formal protection for the policies with enforce_scope =
True in keystone.tests.unit.protection.v3 and remove the old policies
from the v3 sample policy file.

This will reduce confusion by having a true default policy for mappings.

[0] https://review.openstack.org/#/c/525701/
[1] 
https://git.openstack.org/cgit/openstack/keystone/tree/etc/policy.v3cloudsample.json?id=fb73912d87b61c419a86c0a9415ebdcf1e186927#n210

** Affects: keystone
 Importance: Medium
 Status: Triaged


** Tags: policy

** Tags added: policy

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

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

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

Title:
  Remove obsolete mapping policies from policy.v3cloudsample.json

Status in OpenStack Identity (keystone):
  Triaged

Bug description:
  Once support for scope types landed in the mapping API policies, the
  policies in policy.v3cloudsample.json became obsolete [0][1].

  We should add formal protection for the policies with enforce_scope =
  True in keystone.tests.unit.protection.v3 and remove the old policies
  from the v3 sample policy file.

  This will reduce confusion by having a true default policy for
  mappings.

  [0] https://review.openstack.org/#/c/525701/
  [1] 
https://git.openstack.org/cgit/openstack/keystone/tree/etc/policy.v3cloudsample.json?id=fb73912d87b61c419a86c0a9415ebdcf1e186927#n210

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1804519/+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 1804510] [NEW] mysql_exceptions_OperationalError, "Authentication plugin 'caching_sha2_password' cannot be loaded:

2018-11-21 Thread sumit Kumar

Public bug reported:

Description
===
I am following this link (https://docs.openstack.org/install-guide) to install 
the openstack Rocky release and successfully installed the all prerequisite.  

I successfully configure the Keystone service now moving forward to compute 
service that is NOVA and I am following this link 
(https://docs.openstack.org/nova/rocky/install/compute-install-rdo.html) to 
configure the NOVA on controller node.
When I ran this command from root user

# /bin/sh -c "nova-manage api_db sync" nova
I got this error
/usr/lib/python2.7/site-packages/pymysql/cursors.py:170: Warning: (3719, 
u"'utf8' is currently an alias for the character set UTF8MB3, but will be an 
alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order 
to be unambiguous.")
  result = self._query(query)
An error has occurred:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/nova/cmd/manage.py", line 2310, in main
ret = fn(*fn_args, **fn_kwargs)
  File "/usr/lib/python2.7/site-packages/nova/cmd/manage.py", line 866, in sync
return migration.db_sync(version2, database='api') and result
  File "/usr/lib/python2.7/site-packages/nova/db/migration.py", line 26, in 
db_sync
return IMPL.db_sync(version=version, database=database, context=context)
  File "/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/migration.py", line 
57, in db_sync
current_version = db_version(database, context=context)
  File "/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/migration.py", line 
70, in db_version
return versioning_api.db_version(get_engine(database, context=context),
  File "/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/migration.py", line 
45, in get_engine
return db_session.get_api_engine()
  File "/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 141, 
in get_api_engine
return api_context_manager.get_legacy_facade().get_engine()
  File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", 
line 803, in get_legacy_facade
return self._factory.get_legacy_facade()
  File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", 
line 352, in get_legacy_facade
self._start()
  File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", 
line 496, in _start
engine_args, maker_args)
  File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", 
line 520, in _setup_for_connection
sql_connection=sql_connection, **engine_kwargs)
  File "/usr/lib/python2.7/site-packages/debtcollector/renames.py", line 43, in 
decorator
return wrapped(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/engines.py", line 
202, in create_engine
test_conn = _test_connection(engine, max_retries, retry_interval)
  File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/engines.py", line 
380, in _test_connection
return engine.connect()
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 
2102, in connect
return self._connection_cls(self, **kwargs)
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 90, 
in __init__
if connection is not None else engine.raw_connection()
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 
2188, in raw_connection
self.pool.unique_connection, _connection)
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 
2162, in _wrap_pool_connect
e, dialect, self)
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 
1472, in _handle_dbapi_exception_noconnection
util.raise_from_cause(newraise, exc_info)
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/util/compat.py", line 
203, in raise_from_cause
reraise(type(exception), exception, tb=exc_tb, cause=cause)
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 
2158, in _wrap_pool_connect
return fn()
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 345, in 
unique_connection
return _ConnectionFairy._checkout(self)
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 788, in 
_checkout
fairy = _ConnectionRecord.checkout(pool)
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 532, in 
checkout
rec = pool._do_get()
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 1193, in 
_do_get
self._dec_overflow()
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/util/langhelpers.py", 
line 66, in __exit__
compat.reraise(exc_type, exc_value, exc_tb)
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 1190, in 
_do_get
return self._create_connection()
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 350, in 
_create_connection
return _ConnectionRecord(self)
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 477, in 
__init__
self.__connect(first_connect_ch

[Yahoo-eng-team] [Bug 1789423] Re: Server operations fail to complete with versioned notifications if payload contains unset is_public field

2018-11-21 Thread Matt Riedemann

** Also affects: nova/ocata
   Importance: Undecided
   Status: New

** Also affects: nova/rocky
   Importance: Undecided
   Status: New

** Also affects: nova/queens
   Importance: Undecided
   Status: New

** Also affects: nova/pike
   Importance: Undecided
   Status: New

** Changed in: nova/pike
   Status: New => Triaged

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

** Changed in: nova/queens
   Status: New => Triaged

** Changed in: nova/pike
   Importance: Undecided => Medium

** Changed in: nova/queens
   Importance: Undecided => Medium

** Changed in: nova/rocky
   Importance: Undecided => Medium

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

Title:
  Server operations fail to complete with versioned notifications if
  payload contains unset is_public field

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) ocata series:
  New
Status in OpenStack Compute (nova) pike series:
  Triaged
Status in OpenStack Compute (nova) queens series:
  Triaged
Status in OpenStack Compute (nova) rocky series:
  New

Bug description:
  This is a follow up to bug 1739325 which fixed the scenario that the
  flavor.disabled field was missing from the embedded instance flavor.
  The same case occurs for the is_public field, so we should default
  that to True if it's not set in the embedded instance.flavor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1789423/+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 1804502] [NEW] Rebuild server with NUMATopologyFilter enabled fails (in some cases)

2018-11-21 Thread Inbar Stolberg

Public bug reported:

Description
===
server rebuild will fail in nova scheduler on NUMATopologyFilter if the 
computes do not have enough capacity (even though clearly the running server is 
already accounted into that calculation)

to resolve the issue a fix is required in NUMATopologyFilter to not
perform the rebuild operation in the case that the request is due to
rebuild.

the result of such a case will be that server rebuild will fail with
error of "no valid host found"

(do not mix resize with rebuild functions...)

Steps to reproduce
==

1. create a flavor that contain metadata that will point to a specific compute 
(use host aggregate with same key:value metadata
make sure flavor contain topology related metadata:
hw:cpu_cores='1', hw:cpu_policy='dedicated', hw:cpu_sockets='6', 
hw:cpu_thread_policy='prefer', hw:cpu_threads='1', hw:mem_page_size='large', 
location='area51'

2. create a server on that compute (preferably using heat stack)
3. (try to) rebuild the server using stack update
4. issue reproduced

Expected result
===
server in an active running state (if image was replaced in the rebuild command 
than with a reference to the new image in the server details.

Actual result
=
server in error state with error of no valid host found.

Environment
===
detected in Rocky release

KVM hypervisor

Ceph storage

Neutron networks

Logs & Configs
==
in nova.conf:
enabled_filters=AggregateInstanceExtraSpecsFilter,RetryFilter,AvailabilityZoneFilter,NUMATopologyFilter,PciPassthroughFilter,RamFilter,ComputeFilter,ImagePropertiesFilter,CoreFilter,ServerGroupAntiAffinityFilter,ServerGroupAffinityFilter,DiskFilter,ComputeCapabilitiesFilter,AggregateRamFilter,SameHostFilter,DifferentHostFilter

logs: tbd

** Affects: nova
 Importance: Undecided
 Assignee: Inbar Stolberg (inbarsto)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Inbar Stolberg (inbarsto)

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

Title:
  Rebuild server with NUMATopologyFilter enabled fails (in some cases)

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===
  server rebuild will fail in nova scheduler on NUMATopologyFilter if the 
computes do not have enough capacity (even though clearly the running server is 
already accounted into that calculation)

  to resolve the issue a fix is required in NUMATopologyFilter to not
  perform the rebuild operation in the case that the request is due to
  rebuild.

  the result of such a case will be that server rebuild will fail with
  error of "no valid host found"

  (do not mix resize with rebuild functions...)

  Steps to reproduce
  ==

  1. create a flavor that contain metadata that will point to a specific 
compute (use host aggregate with same key:value metadata
  make sure flavor contain topology related metadata:
  hw:cpu_cores='1', hw:cpu_policy='dedicated', hw:cpu_sockets='6', 
hw:cpu_thread_policy='prefer', hw:cpu_threads='1', hw:mem_page_size='large', 
location='area51'

  2. create a server on that compute (preferably using heat stack)
  3. (try to) rebuild the server using stack update
  4. issue reproduced

  Expected result
  ===
  server in an active running state (if image was replaced in the rebuild 
command than with a reference to the new image in the server details.

  Actual result
  =
  server in error state with error of no valid host found.

  Environment
  ===
  detected in Rocky release

  KVM hypervisor

  Ceph storage

  Neutron networks

  Logs & Configs
  ==
  in nova.conf:
  
enabled_filters=AggregateInstanceExtraSpecsFilter,RetryFilter,AvailabilityZoneFilter,NUMATopologyFilter,PciPassthroughFilter,RamFilter,ComputeFilter,ImagePropertiesFilter,CoreFilter,ServerGroupAntiAffinityFilter,ServerGroupAffinityFilter,DiskFilter,ComputeCapabilitiesFilter,AggregateRamFilter,SameHostFilter,DifferentHostFilter

  logs: tbd

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1804502/+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 1804482] [NEW] Remove obsolete endpoint policies from policy.v3cloudsample.json

Public bug reported:

Once support for scope types landed in the endpoint API policies, the
policies in policy.v3cloudsample.json became obsolete [0][1].

We should add formal protection for the policies with enforce_scope =
True in keystone.tests.unit.protection.v3 and remove the old policies
from the v3 sample policy file.

This will reduce confusion by having a true default policy for
endpoints.

[0] https://review.openstack.org/#/c/525695/
[1] 
http://git.openstack.org/cgit/openstack/keystone/tree/etc/policy.v3cloudsample.json?id=fb73912d87b61c419a86c0a9415ebdcf1e186927#n25

** Affects: keystone
 Importance: Medium
 Status: Triaged


** Tags: policy

** Tags added: policy

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

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

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

Title:
  Remove obsolete endpoint policies from policy.v3cloudsample.json

Status in OpenStack Identity (keystone):
  Triaged

Bug description:
  Once support for scope types landed in the endpoint API policies, the
  policies in policy.v3cloudsample.json became obsolete [0][1].

  We should add formal protection for the policies with enforce_scope =
  True in keystone.tests.unit.protection.v3 and remove the old policies
  from the v3 sample policy file.

  This will reduce confusion by having a true default policy for
  endpoints.

  [0] https://review.openstack.org/#/c/525695/
  [1] 
http://git.openstack.org/cgit/openstack/keystone/tree/etc/policy.v3cloudsample.json?id=fb73912d87b61c419a86c0a9415ebdcf1e186927#n25

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1804482/+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 1804483] [NEW] Endpoint API doesn't use default roles

Public bug reported:

In Rocky, keystone implemented support to ensure at least three default
roles were available [0]. The endpoint API doesn't incorporate these
defaults into its default policies [1], but it should.

[0] 
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html
[1] 
http://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/endpoint.py?id=fb73912d87b61c419a86c0a9415ebdcf1e186927

** Affects: keystone
 Importance: Medium
 Status: Triaged


** Tags: default-roles policy

** Tags added: policy

** Tags added: default-roles

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

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

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

Title:
  Endpoint API doesn't use default roles

Status in OpenStack Identity (keystone):
  Triaged

Bug description:
  In Rocky, keystone implemented support to ensure at least three
  default roles were available [0]. The endpoint API doesn't incorporate
  these defaults into its default policies [1], but it should.

  [0] 
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html
  [1] 
http://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/endpoint.py?id=fb73912d87b61c419a86c0a9415ebdcf1e186927

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1804483/+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 1792778] Re: Inconsistent use of btn-danger

Reviewed:  https://review.openstack.org/618096
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=55835c7305b52f03f8d391f5715ff8d3b75177d2
Submitter: Zuul
Branch:master

commit 55835c7305b52f03f8d391f5715ff8d3b75177d2
Author: manchandavishal 
Date:   Thu Nov 15 07:45:56 2018 +

Fix: Inconsistent use of btn-danger

The color of delete image button is inconsistent with other
destructive buttons.
This patch fixes the issue.

Change-Id: Id7acd54e5535912eff4e69cbfd360ef02e7d8786
Closes-Bug: #1792778


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

Title:
  Inconsistent use of btn-danger

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  I think this started in queens as a result of:
  https://review.openstack.org/#/c/339278/

  This changed some delete confirmation buttons from btn-primary to btn-
  danger. However, some buttons, such as "Delete Image", still uses btn-
  primary. This results in inconsistent colors for destructive buttons
  on confirmation modals.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1792778/+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 1803486] Re: Floating and negative values accepted in volume size field.

2018-11-21 Thread Ivan Kolodyazhny

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

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

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

Title:
  Floating and negative values accepted in volume size field.

Status in OpenStack Dashboard (Horizon):
  Won't Fix

Bug description:
  As we know that in cinder, volume size cannot be a decimal value, only 
integer values are accepted.
  So when a user create a volume from horizon,horizon allows user to enter a 
decimal value or negative value  in Size (GiB) field.
  obviously, user can't create a volume in decimal size as there are some 
validation on create button,
  But we can enforce more validation on the volume Size field (like user can't 
enter alphabets which is currently enforced), we shouldn't allow negative 
symbol '-' and decimal point '.' in the field too, So the user can only enter 
number from (0-9).

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1803486/+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 1804462] [NEW] Remove obsolete service policies from policy.v3cloudsample.json

Public bug reported:

Once support for scope types landed in the service API policies, the
policies in policy.v3cloudsample.json became obsolete [0][1].

We should add formal protection for the policies with enforce_scope =
True in keystone.tests.unit.protection.v3 and remove the old policies
from the v3 sample policy file.

This will reduce confusion by having a true default policy for services.

[0] https://review.openstack.org/#/c/525696/
[1] 
http://git.openstack.org/cgit/openstack/keystone/tree/etc/policy.v3cloudsample.json?id=fb73912d87b61c419a86c0a9415ebdcf1e186927#n19

** Affects: keystone
 Importance: Undecided
 Status: New


** Tags: policy

** Tags added: policy

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

Title:
  Remove obsolete service policies from policy.v3cloudsample.json

Status in OpenStack Identity (keystone):
  New

Bug description:
  Once support for scope types landed in the service API policies, the
  policies in policy.v3cloudsample.json became obsolete [0][1].

  We should add formal protection for the policies with enforce_scope =
  True in keystone.tests.unit.protection.v3 and remove the old policies
  from the v3 sample policy file.

  This will reduce confusion by having a true default policy for
  services.

  [0] https://review.openstack.org/#/c/525696/
  [1] 
http://git.openstack.org/cgit/openstack/keystone/tree/etc/policy.v3cloudsample.json?id=fb73912d87b61c419a86c0a9415ebdcf1e186927#n19

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1804462/+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 1804463] [NEW] Service API doesn't use default roles

Public bug reported:

In Rocky, keystone implemented support to ensure at least three default
roles were available [0]. The services API doesn't incorporate these
defaults into its default policies [1], but it should.

[0] 
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html
[1] 
http://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/service.py?id=fb73912d87b61c419a86c0a9415ebdcf1e186927

** Affects: keystone
 Importance: Medium
 Status: Triaged


** Tags: default-roles policy

** Tags added: default-roles policy

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

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

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

Title:
  Service API doesn't use default roles

Status in OpenStack Identity (keystone):
  Triaged

Bug description:
  In Rocky, keystone implemented support to ensure at least three
  default roles were available [0]. The services API doesn't incorporate
  these defaults into its default policies [1], but it should.

  [0] 
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html
  [1] 
http://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/service.py?id=fb73912d87b61c419a86c0a9415ebdcf1e186927

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1804463/+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 1804073] Re: Keystone fails to log policy target data

2018-11-21 Thread John Dennis

** No longer affects: keystone

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

Title:
  Keystone fails to log policy target data

Status in oslo.policy:
  New

Bug description:
  The Oslo Policy Enforcer requires 3 pieces of run-time information in
  addition to the policy rules to issue a RBAC decision:

  1) the name of the rule to be evaluated (called target in the oslo-policy doc)
  2) the auth context (called credentials in the oslo-policy doc)
  3) the target data (resource data relevant to the rule)

  If you are trying to debug policy enforcement or simply validate your
  policy works as expect one can use the oslopolicy-checker tool. But
  the oslopolicy-checker tool needs the *exact* same data keystone
  passes to the policy enforcement engine.

  The fact the target data needs to be logged but isn't is captured in
  this comment from Henry Nash in authorize.py

  # TODO(henry-nash) need to log the target attributes as well

  
https://github.com/openstack/keystone/blob/stable/rocky/keystone/common/authorization.py#L139

  But that is not the best location to log, the best place is where
  oslo.policy is called to evaluate a policy rule, that occurs in
  Policy.enforce() in keystone/policy/backends/policy.py

  
https://github.com/openstack/keystone/blob/stable/rocky/keystone/policy/backends/rules.py#L29:#L34

  Here we can see it logs the rule name (e.g. action) and the auth
  context (credentials)

  msg = 'enforce %(action)s: %(credentials)s'

  but the target data is not logged.

  Besides the fact the target data is not logged is the fact the logging
  relies on Python's str() method to convert an object into a string
  representation. This has two problems, 1) all contained objects must
  also have __str__() methods that fully log their contents, 2) the
  formatting is often in Python's "representation" style which only
  humans and Python can parse.

  Since both the credential and targets parameters to the enforce method
  are dicts (with arbitrary complex nesting) and the fact JSON is the
  data format we use for data exchange and the format used by
  oslopolicy-checker it makes sense to log the enforcement parameters in
  JSON format. This way no data is lost (because there wasn't an
  appropriate formatter for the object) and it makes it easy import the
  data to another tool (again, without loss of data).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oslo.policy/+bug/1804073/+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 1804453] [NEW] maximum recursion possible while setting aggregates in placement

2018-11-21 Thread Chris Dent

Public bug reported:

It's possible for the _ensure_aggregate code in
objects/resource_provider.py to, under unusual circumstances, reach a
maximum recursion error, because it calls itself when there is a
DBDuplicateEntry error.

http://logs.openstack.org/84/602484/30/check/placement-
perfload/8a8642e/controller/logs/screen-placement-
api.txt.gz#_Nov_21_13_05_03_661629

http://logs.openstack.org/84/602484/30/check/placement-
perfload/8a8642e/controller/logs/screen-placement-
api.txt.gz#_Nov_21_13_05_03_654874

" ERROR placement.fault_wrap [None req-5fc62d1e-a1bd-47e3-a61e-
45e01281fed3 None None] Placement API unexpected error: maximum
recursion depth exceeded while getting the str of an object:
RuntimeError: maximum recursion depth exceeded while getting the str of
an object"

The "getting the str" part appears to be a coincidence based on reaching
a bad stack depth at that particular moment.

This happened while the placeload script was doing its thing of adding
aggregates to to 1000 resource providers using asyncio, so concurrency
is high and weird. See https://review.openstack.org/#/c/602484/ for the
code that caused this.

It is unlikely that this is going to happen in the real world, but it is
the sort of thing it would be nice to be more robust about, perhaps by
counting attempts and bailing out?

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: placement

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

Title:
  maximum recursion possible while setting aggregates in placement

Status in OpenStack Compute (nova):
  New

Bug description:
  It's possible for the _ensure_aggregate code in
  objects/resource_provider.py to, under unusual circumstances, reach a
  maximum recursion error, because it calls itself when there is a
  DBDuplicateEntry error.

  http://logs.openstack.org/84/602484/30/check/placement-
  perfload/8a8642e/controller/logs/screen-placement-
  api.txt.gz#_Nov_21_13_05_03_661629

  http://logs.openstack.org/84/602484/30/check/placement-
  perfload/8a8642e/controller/logs/screen-placement-
  api.txt.gz#_Nov_21_13_05_03_654874

  " ERROR placement.fault_wrap [None req-5fc62d1e-a1bd-47e3-a61e-
  45e01281fed3 None None] Placement API unexpected error: maximum
  recursion depth exceeded while getting the str of an object:
  RuntimeError: maximum recursion depth exceeded while getting the str
  of an object"

  The "getting the str" part appears to be a coincidence based on
  reaching a bad stack depth at that particular moment.

  This happened while the placeload script was doing its thing of adding
  aggregates to to 1000 resource providers using asyncio, so concurrency
  is high and weird. See https://review.openstack.org/#/c/602484/ for
  the code that caused this.

  It is unlikely that this is going to happen in the real world, but it
  is the sort of thing it would be nice to be more robust about, perhaps
  by counting attempts and bailing out?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1804453/+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 1804446] [NEW] Regions API doesn't use default roles

Public bug reported:

In Rocky, keystone implemented support to ensure at least three default
roles were available [0]. The regions API doesn't incorporate these
defaults into its default policies [1], but it should.

[0] 
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html
[1] 
http://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/region.py?id=fb73912d87b61c419a86c0a9415ebdcf1e186927

** Affects: keystone
 Importance: Medium
 Status: Triaged

** Description changed:

  In Rocky, keystone implemented support to ensure at least three default
  roles were available [0]. The regions API doesn't incorporate these
- defaults into its default policies, but it should.
+ defaults into its default policies [1], but it should.
  
- [0] http://specs.openstack.org/openstack/keystone-
- specs/specs/keystone/rocky/define-default-roles.html
+ [0] 
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html
+ [1] 
http://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/region.py?id=fb73912d87b61c419a86c0a9415ebdcf1e186927

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

** Changed in: keystone
   Status: Confirmed => Triaged

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

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

Title:
  Regions API doesn't use default roles

Status in OpenStack Identity (keystone):
  Triaged

Bug description:
  In Rocky, keystone implemented support to ensure at least three
  default roles were available [0]. The regions API doesn't incorporate
  these defaults into its default policies [1], but it should.

  [0] 
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html
  [1] 
http://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/region.py?id=fb73912d87b61c419a86c0a9415ebdcf1e186927

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1804446/+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 1804436] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Max resolution is incorrect after run"xrandr" command.(FR:3/3units)

Public bug reported:

Description:
Connect 2K or 4K monitor, Open a terminal via superuser and execute "xrandr",
check display resolution find the 2k or 4K monitor max resolution both
show"8192x8192.

Expected Behavior:
The display correct max resolution after run"xrandr" command in terminal.

Severity:
Sev-3
P3
C3
L4

Test Environment:
1. Project: Northbay 13 SKU9
2. BIOS: 0.4.0
3. OS:CI Ubuntu 18.04
4. 4k Monitor:P2718Q&UP3216Q
5. 2K Monitor-35

Note:
1.VP on Bandon all SKU
2.VP on Northbay other SKU

Cross Platform:
N/A

Test case:
CSV-TC-4603[WIS-TC-4189] Linux_USB - USB Type-C With Dell Ultra-HD 4K
Display/Monitor Test (HDMI) step:4

Steps to Reproduce:
1.Plugin the "USB Type-C to HDMI" Dongle to the "USB Type-C" port on the SUT
and then plug in the external Ultra-HD 4K Monitor HDMI cable to the other end
of the dongle and turn the monitor on.
2.Check to make sure that both the SUT and the external monitor has the
duplicate display of Linux OS Desktop.
3.Open a terminal via superuser and execute "xrandr" ,check display resolution
find the max reslution show"8192x8192"-->problem.

** Affects: glance
Importance: Undecided
Status: New

** Tags: north-bay-13

** Attachment added: "IMG_20181115_185628.jpg"

https://bugs.launchpad.net/bugs/1804436/+attachment/5214953/+files/IMG_20181115_185628.jpg

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

Title:
Linux, Ubuntu, 18.04, CI, NB13, Max resolution is incorrect after
run"xrandr" command.(FR:3/3units)

Status in Glance:
New

Bug description:

Description:
Connect 2K or 4K monitor, Open a terminal via superuser and execute "xrandr",
check display resolution find the 2k or 4K monitor max resolution both
show"8192x8192.

Expected Behavior:
The display correct max resolution after run"xrandr" command in terminal.

Severity:
Sev-3
P3
C3
L4

Test Environment:
1. Project: Northbay 13 SKU9
2. BIOS: 0.4.0
3. OS:CI Ubuntu 18.04
4. 4k Monitor:P2718Q&UP3216Q
5. 2K Monitor-35

Note:
1.VP on Bandon all SKU
2.VP on Northbay other SKU

Cross Platform:
N/A

Test case:
CSV-TC-4603[WIS-TC-4189] Linux_USB - USB Type-C With Dell Ultra-HD 4K
Display/Monitor Test (HDMI) step:4

Steps to Reproduce:
1.Plugin the "USB Type-C to HDMI" Dongle to the "USB Type-C" port on the SUT
and then plug in the external Ultra-HD 4K Monitor HDMI cable to the other end
of the dongle and turn the monitor on.
2.Check to make sure that both the SUT and the external monitor has the
duplicate display of Linux OS Desktop.
3.Open a terminal via superuser and execute "xrandr" ,check display
resolution find the max reslution show"8192x8192"-->problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1804436/+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 1804440] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Perform Lid close is no function when use"dconf-editor"tool(FR:100%)

Public bug reported:

Description:
Run Command: 'sudo apt install dconf-editord', Then run command: 'conf-editor' 
to open the dconf Editor and set lid close: Hibernate, but after close lid, SUT 
not enter Hibernate.

Expected Behavior:
SUT enter Hibernate after lid close.

Severity:
Sev-2
P3
C3
L2

Test Environment:
1. Project: Northbay 13 SKU7
2. BIOS: 0.4.0
3. OS: CI Ubuntu 18.04
4. Tool: dconf-editor

Note:
1. VP on Northbay sku 6/8/9/10/11
2. VP on S5
3. VNP on suspend

Cross Platform:
N/A

Test case:
CSV-TC-5234[WIS-TC-4424] Linux_Thunderbolt3 - HDDs and Monitor Connected In 
Daisy-Chain Format Functionality Test step:39

Steps to Reproduce:  
1. Boot to Ubuntu OS;
2. Run cmmand: 'sudo apt install dconf-editord';
3. Then run cmmand: 'conf-editor' to open the dconf Editor and set lid close: 
Hibernate;
4. Close Lid and wait 1 min, open the Lid, find SUT not enter 
Hibernate.-->problem

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: north-bay-13

** Attachment added: "acpi(BIOS ).log"
   
https://bugs.launchpad.net/bugs/1804440/+attachment/5214955/+files/acpi%28BIOS%20%29.log

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

Title:
  Linux, Ubuntu, 18.04, CI, NB13, Perform Lid close is no function when
  use"dconf-editor"tool(FR:100%)

Status in Glance:
  New

Bug description:
  Description:
  Run Command: 'sudo apt install dconf-editord', Then run command: 
'conf-editor' to open the dconf Editor and set lid close: Hibernate, but after 
close lid, SUT not enter Hibernate.

  Expected Behavior:
  SUT enter Hibernate after lid close.

  Severity:
  Sev-2
  P3
  C3
  L2

  Test Environment:
  1. Project: Northbay 13 SKU7
  2. BIOS: 0.4.0
  3. OS: CI Ubuntu 18.04
  4. Tool: dconf-editor

  Note:
  1. VP on Northbay sku 6/8/9/10/11
  2. VP on S5
  3. VNP on suspend

  Cross Platform:
  N/A

  Test case:
  CSV-TC-5234[WIS-TC-4424] Linux_Thunderbolt3 - HDDs and Monitor Connected In 
Daisy-Chain Format Functionality Test step:39

  Steps to Reproduce:  
  1. Boot to Ubuntu OS;
  2. Run cmmand: 'sudo apt install dconf-editord';
  3. Then run cmmand: 'conf-editor' to open the dconf Editor and set lid close: 
Hibernate;
  4. Close Lid and wait 1 min, open the Lid, find SUT not enter 
Hibernate.-->problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1804440/+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 1804427] [NEW] Linux, Ubuntu, 18.04, CI, NB13, SUT flash screen twice if plug/unplug monitor cable on Salomon Dock.(FR:100%)

Public bug reported:

Description:
Boot to OS with connect Salomon TBT3 dock connected, then plug in external
monitor with DP/HDMI cable to Salomon Dock, find SUT flashes black screen 2
times after plug in external monitor cable to salomon dock. Then unplug
external monitor cable on Salomon dock, SUT flashes black screen 2 times again.
(FR:100%)

Expected Behavior:
SUT should only flash black screen one time when hot-plug/unplug external
monitor cable on Salomon Dock.

Severity:
Sev-2
P3
C3
L1

Test environment:
1. Project:Northbay 13
2. BIOS:0.4.1
4. OS:CI Ubuntu 18.04
5. Dock info: DOCK-126 REV-X00 Dell Salomon WD19TB Thunderbolt3 Dock DP/N
0XHKGV Salomon_TBT3 FW:00.00.12
6. Monitor: monitor-62 Dell U2415; ASUS MX27AQ

Notes:
1. VP on Northbay TBT&non-TBT sku
2. VP on Salomon single-c cable Dock
3. VNP on BME dock(REV-A05 Dock-114 FW:0.1.17)
4. VNP on derectly connect external monitor to SUT(HDMI)
5. VP on turn on external HDMI monitor that connected to Salomon TBT3 cable
Dock.

Cross Platform:
NA

Test case:
[CSV-TC-5196][WIS-TC-4409] Linux_NB_Salomon-Wired-Dock-The I/O Ports
Functionality Test (1/2) Step25

Steps to Reproduce:
1. Install Ubuntu OS 18.04.1 LTS
2. Boot to OS with connect Salomon TBT3 dock connected, then plug in external
monitor with DP/HDMI cable to Salomon Dock, find SUT flashes black screen 2
times after plug in external monitor to salomon dock.-->Problem(refer to video)
3. Then unplug external monitor to Salomon dock, SUT flashes black screen 2
times again.

** Affects: glance
Importance: Undecided
Status: New

** Tags: north-bay-13

** Attachment added: "sosreport-Ubuntu 18.04 LTSCILatitude2-5380.tar11.xz"

https://bugs.launchpad.net/bugs/1804427/+attachment/5214949/+files/sosreport-Ubuntu%2018.04%20LTSCILatitude2-5380.tar11.xz

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

Title:
Linux, Ubuntu, 18.04, CI, NB13, SUT flash screen twice if plug/unplug
monitor cable on Salomon Dock.(FR:100%)

Status in Glance:
New

Bug description:
Description:
Boot to OS with connect Salomon TBT3 dock connected, then plug in external
monitor with DP/HDMI cable to Salomon Dock, find SUT flashes black screen 2
times after plug in external monitor cable to salomon dock. Then unplug
external monitor cable on Salomon dock, SUT flashes black screen 2 times again.
(FR:100%)

Expected Behavior:
SUT should only flash black screen one time when hot-plug/unplug external
monitor cable on Salomon Dock.

Severity:
Sev-2
P3
C3
L1

Test environment:
1. Project:Northbay 13
2. BIOS:0.4.1
4. OS:CI Ubuntu 18.04
5. Dock info: DOCK-126REV-X00 Dell Salomon WD19TB Thunderbolt3 Dock
DP/N 0XHKGV Salomon_TBT3 FW:00.00.12
6. Monitor: monitor-62 Dell U2415; ASUS MX27AQ

Cross Platform:
NA

Test case:
[CSV-TC-5196][WIS-TC-4409] Linux_NB_Salomon-Wired-Dock-The I/O Ports
Functionality Test (1/2) Step25

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1804427/+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 1804423] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Three monitors connect to SUT can't be display at the same time.

Public bug reported:

Description:
The three external monitors with HDMI, DP and VGA cable connected to the 
"Trinity Imperial Express Wired Docking Station" HDMI, mDP and VGA ports  
cannot display at the same time with resolution 1280 x 1024.(FR:100%) 

Expected Behavior:
Follow IE Dock spec, can output 3 1280x1024@60Hz.

Severity:
Sev-3
P3
C3
L4

Test Environment:
1. Project: Northbay 13 SKU9
2. BIOS: 0.4.0
3. OS: CI Ubuntu 18.04
4. IE dock-112 FW: 1.0.4
5. BTOA Date: Test with CI image

Note:
1. VP on North Bay 13

Cross Platform:
N/A

Test case:
[CSV-TC-4685][WIS-TC-4215] Linux_NB_IE-Wired-Dock-The "Triple/Three (3) FHD 
Displays/Monitors" Support Test step:11
 
Steps to Reproduce:  
1. Plugin the IE dock to the "USB Type-C" port on the SUT; 
2. Connected three external monitors with HDMI, DP and VGA cable to the 
"Trinity Imperial Express Wired Docking Station" HDMI, mDP and VGA ports.
3. Turn on monitors, set resolution to 1280 x 1024, find three monitors cannot 
be display at the same time.-->problem(refer to attachments)

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: north-bay-13

** Attachment added: "sosreport-IE dock{WIS-IS-4215]-20181119003325.tar.xz"
   
https://bugs.launchpad.net/bugs/1804423/+attachment/5214944/+files/sosreport-IE%20dock%7BWIS-IS-4215%5D-20181119003325.tar.xz

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

Title:
  Linux, Ubuntu, 18.04, CI, NB13, Three monitors connect to SUT can't be
  display at the same time.

Status in Glance:
  New

Bug description:
  Description:
  The three external monitors with HDMI, DP and VGA cable connected to the 
"Trinity Imperial Express Wired Docking Station" HDMI, mDP and VGA ports  
cannot display at the same time with resolution 1280 x 1024.(FR:100%) 

  Expected Behavior:
  Follow IE Dock spec, can output 3 1280x1024@60Hz.

  Severity:
  Sev-3
  P3
  C3
  L4

  Test Environment:
  1. Project: Northbay 13 SKU9
  2. BIOS: 0.4.0
  3. OS: CI Ubuntu 18.04
  4. IE dock-112 FW: 1.0.4
  5. BTOA Date: Test with CI image

  Note:
  1. VP on North Bay 13

  Cross Platform:
  N/A

  Test case:
  [CSV-TC-4685][WIS-TC-4215] Linux_NB_IE-Wired-Dock-The "Triple/Three (3) FHD 
Displays/Monitors" Support Test step:11
   
  Steps to Reproduce:  
  1. Plugin the IE dock to the "USB Type-C" port on the SUT; 
  2. Connected three external monitors with HDMI, DP and VGA cable to the 
"Trinity Imperial Express Wired Docking Station" HDMI, mDP and VGA ports.
  3. Turn on monitors, set resolution to 1280 x 1024, find three monitors 
cannot be display at the same time.-->problem(refer to attachments)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1804423/+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 1804425] [NEW] Linux, Ubuntu, 18.04, CI, NB13, SUT flashes black screen when hot plug/unplug Salomon dock(FR:100%)

Public bug reported:

Description: 
Boot to OS, then connect Salomon TBT3 dock to SUT and find SUT will flash black 
screen. Disconnect Salomon TBT3 dock and find SUT flashes black screen again.


Expected Behavior: 
SUT doesn't flash black screen when hot plug/unplug Salomon Dock.

Severity:
Sev-2
P3
C3
L1

Test environment:
1. Project:Northbay 13
2. BIOS:0.4.1
4. OS:CI Ubuntu 18.04
5. Dock info: DOCK-126  REV-X00  Dell Salomon WD19TB Thunderbolt3 Dock DP/N 
0XHKGV  Salomon_TBT3  FW:00.00.12

Notes:
1. VP on Northbay TBT&non-TBT sku
2. VP on Salomon single-c cable Dock
3. VNP on BME dock(REV-A05 Dock-114  FW:0.1.17)

Cross Platform:
NA

Test case: 
[CSV-TC-5194][WIS-TC-4407] Linux_NB_Salomon-Wired-Dock-The Docked SUT 
"Plug/Unplug" Test  Step32

Steps to Reproduce:
1. Install Ubuntu OS 18.04.1 LTS
2. Boot to OS and connect Salomon Dock to SUT,find SUT will flash black 
screen.-->Problem(refer to video)
3. Disconnect Salomon dock and find SUT flashes black screen again.

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: north-bay-13

** Attachment added: "sosreport-Ubuntu 18.04 LTSCILatitude2-5380.tar11.xz"
   
https://bugs.launchpad.net/bugs/1804425/+attachment/5214947/+files/sosreport-Ubuntu%2018.04%20LTSCILatitude2-5380.tar11.xz

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

Title:
  Linux, Ubuntu, 18.04, CI, NB13,SUT flashes black screen when hot
  plug/unplug Salomon dock(FR:100%)

Status in Glance:
  New

Bug description:
  Description: 
  Boot to OS, then connect Salomon TBT3 dock to SUT and find SUT will flash 
black screen. Disconnect Salomon TBT3 dock and find SUT flashes black screen 
again.

  
  Expected Behavior: 
  SUT doesn't flash black screen when hot plug/unplug Salomon Dock.

  Severity:
  Sev-2
  P3
  C3
  L1

  Test environment:
  1. Project:Northbay 13
  2. BIOS:0.4.1
  4. OS:CI Ubuntu 18.04
  5. Dock info: DOCK-126REV-X00  Dell Salomon WD19TB Thunderbolt3 Dock 
DP/N 0XHKGV  Salomon_TBT3  FW:00.00.12

  Notes:
  1. VP on Northbay TBT&non-TBT sku
  2. VP on Salomon single-c cable Dock
  3. VNP on BME dock(REV-A05 Dock-114  FW:0.1.17)

  Cross Platform:
  NA

  Test case: 
  [CSV-TC-5194][WIS-TC-4407] Linux_NB_Salomon-Wired-Dock-The Docked SUT 
"Plug/Unplug" Test  Step32

  Steps to Reproduce:
  1. Install Ubuntu OS 18.04.1 LTS
  2. Boot to OS and connect Salomon Dock to SUT,find SUT will flash black 
screen.-->Problem(refer to video)
  3. Disconnect Salomon dock and find SUT flashes black screen again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1804425/+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 1804421] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Videos window show garbage when perform Max/minim it.(FR:100%)

Public bug reported:


Description:
While the a movie file is playing with Videos on the external monitor, perform 
maximization, minimization the movie window. Find the Videos window show 
garbage.

Expected Behavior:

Perform maximization/ minimization the movie window can't show garbage.

Severity:
Sev-2
P3
C3
L2

Test Environment:
1. Project: Northbay 13 SKU9
2. BIOS: 0.4.0
3. OS: CI Ubuntu 18.04
4. Monitor: Dell P2718Q
5. Test Join Displays mode
 
Note:
1. VP on monitor: Dell UP3216Q
2. VP on Mirror mode
3. VP on External only mode

Cross Platform:
N/A

Test case:
CSV-TC-4603[WIS-TC-4189] Linux_USB - USB Type-C With Dell Ultra-HD 4K 
Display/Monitor Test (HDMI) step:7
 
Steps to Reproduce:  
1. Plug the "USB Type-C to HDMI" Dongle to the "USB Type-C" port on the SUT and 
then plug the external monitor via the HDMI cable to the other end of the 
dongle and turn the monitor on;
2. Play a movie file on the monitor, perform maximization, minimization the 
movie window. Find the windows show garbage-->problem(refer to .mp4)

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: north-bay-13

** Attachment added: "sosreport-ubuntu9.-20181120210049.tar.xz"
   
https://bugs.launchpad.net/bugs/1804421/+attachment/5214934/+files/sosreport-ubuntu9.-20181120210049.tar.xz

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

Title:
  Linux, Ubuntu, 18.04, CI, NB13, Videos window show garbage when
  perform Max/minim it.(FR:100%)

Status in Glance:
  New

Bug description:
  
  Description:
  While the a movie file is playing with Videos on the external monitor, 
perform maximization, minimization the movie window. Find the Videos window 
show garbage.

  Expected Behavior:

  Perform maximization/ minimization the movie window can't show
  garbage.

  Severity:
  Sev-2
  P3
  C3
  L2

  Test Environment:
  1. Project: Northbay 13 SKU9
  2. BIOS: 0.4.0
  3. OS: CI Ubuntu 18.04
  4. Monitor: Dell P2718Q
  5. Test Join Displays mode
   
  Note:
  1. VP on monitor: Dell UP3216Q
  2. VP on Mirror mode
  3. VP on External only mode

  Cross Platform:
  N/A

  Test case:
  CSV-TC-4603[WIS-TC-4189] Linux_USB - USB Type-C With Dell Ultra-HD 4K 
Display/Monitor Test (HDMI) step:7
   
  Steps to Reproduce:  
  1. Plug the "USB Type-C to HDMI" Dongle to the "USB Type-C" port on the SUT 
and then plug the external monitor via the HDMI cable to the other end of the 
dongle and turn the monitor on;
  2. Play a movie file on the monitor, perform maximization, minimization the 
movie window. Find the windows show garbage-->problem(refer to .mp4)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1804421/+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 1804419] [NEW] Linux, Ubuntu, 18.04, NB13, HDMI Monitor show DP after run "xrandr" command. (FR:100%)

Public bug reported:


Description:
Connect a Single-c Salomin Dock to SUT, connect a HDMI Monitor by Type-c to 
HDMI dongle to Salomon Type-c port. Run "xrandr" command, show "DP-1-3".

Expected Behavior:
HDMI Monitor show HDMI after run "xrandr" command.

Severity:
Sev-3
P3
C3
L4

Test Environment:
1. Project: Northbay 13
2. BIOS: 0.4.0
3. OS:CI Ubuntu 18.04
4. Salomon SINGLE-C Dock 165: DP/N :0YVYPW REV X00  FW:00.00.12.01

Note:
1. VP on  TBT Salomon DOCK-126 REV-X00  Dell Salomon WD19TB Thunderbolt3 Dock 
DP/N 0XHKGV  Salomon_TBT3  FW:00.00.12 
2. VP on Connect HDMI Monitor directly on Salomon Dock
3. VNP on Connect HDMI Monitor directly on SUT

Cross Platform:
N/A

Test case:
[CSV-TC-4600][WIS-TC-4186] Linux_USB - USB Type-C With HDMI Video Test step:2
 
Steps to Reproduce:  
1. Flash Latest BIOS, install Ubuntu OS 18.04.
2. Boot to OS, Connect a Salomon Dock to SUT;
3. Connect a HDMI Monitor by Type-c to HDMI dongle to Salomon Type-c port;
4. Run "xrandr" command in Terminal, show "DP-1-3".>problem(refer to pic)

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: north-bay-13

** Attachment added: "sosreport-genericlog.1-20181120045802.tar.xz"
   
https://bugs.launchpad.net/bugs/1804419/+attachment/5214932/+files/sosreport-genericlog.1-20181120045802.tar.xz

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

Title:
  Linux, Ubuntu,18.04, NB13, HDMI Monitor show DP after run "xrandr"
  command. (FR:100%)

Status in Glance:
  New

Bug description:
  
  Description:
  Connect a Single-c Salomin Dock to SUT, connect a HDMI Monitor by Type-c to 
HDMI dongle to Salomon Type-c port. Run "xrandr" command, show "DP-1-3".

  Expected Behavior:
  HDMI Monitor show HDMI after run "xrandr" command.

  Severity:
  Sev-3
  P3
  C3
  L4

  Test Environment:
  1. Project: Northbay 13
  2. BIOS: 0.4.0
  3. OS:CI Ubuntu 18.04
  4. Salomon SINGLE-C Dock 165: DP/N :0YVYPW REV X00  FW:00.00.12.01

  Note:
  1. VP on  TBT Salomon DOCK-126 REV-X00  Dell Salomon WD19TB Thunderbolt3 Dock 
DP/N 0XHKGV  Salomon_TBT3  FW:00.00.12 
  2. VP on Connect HDMI Monitor directly on Salomon Dock
  3. VNP on Connect HDMI Monitor directly on SUT

  Cross Platform:
  N/A

  Test case:
  [CSV-TC-4600][WIS-TC-4186] Linux_USB - USB Type-C With HDMI Video Test step:2
   
  Steps to Reproduce:  
  1. Flash Latest BIOS, install Ubuntu OS 18.04.
  2. Boot to OS, Connect a Salomon Dock to SUT;
  3. Connect a HDMI Monitor by Type-c to HDMI dongle to Salomon Type-c port;
  4. Run "xrandr" command in Terminal, show "DP-1-3".>problem(refer to pic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1804419/+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 1804416] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Display setting show 3 monitors when connect TBT3 monitor(FR:100%)

Public bug reported:


Description:
Connect five LaCie d2 Thunderbolt-3 External HDDs to SUT as daisy chain, plug a 
LG 27" 5K Thunderbolt Type-3 Monitor as 6th deivce to the 5th HDD's TBT port, 
Display setting show 3 monitors.

Expected Behavior:
In Linux OS, connect five LaCie d2 Thunderbolt-3 External HDDs to SUT as daisy 
chain, plug a LG 27" 5K Thunderbolt Type-3 Monitor as 6th deivce to the 5th 
HDD's TBT port, Display setting show 1 monitor.

Severity:
Sev-2
P3
C3
L2

Test Environment:
1. Project: Northbay 13 SKU7
2. BIOS: 0.4.0
3. OS: CI Ubuntu 18.04
4. 5k monitor: LG 27MD5KA-B

Note:
1. VP on TBT monitor directy connect to SUT TBT Port

Cross Platform:
N/A

Test case:
CSV-TC-5234[WIS-TC-4424] Linux_Thunderbolt3 - HDDs and Monitor Connected In 
Daisy-Chain Format Functionality Test step:17
 
Steps to Reproduce:  
1. Plug in the Sixth (6th) device  LG 27" 5KMonitor  to the second  
Thunderbolt-3  port on the back of the fifth (5th)  LaCie d2 Thunderbolt-3 
External HDD
2. Check to verify that the sixth (6th) device, the  LG 27" 5K Thunderbolt 
Type-3 Monitor  is properly enumerated and functioning. 
3. Check the Linux OS Display Setting ,Find the Display setting show 3 monitors 
.-->problem(Refer to pic)

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: north-bay-13

** Attachment added: 
"sosreport-Ubuntu18.04LTSCILatitude-5380.WIS-TC-4424.tar1.xz"
   
https://bugs.launchpad.net/bugs/1804416/+attachment/5214929/+files/sosreport-Ubuntu18.04LTSCILatitude-5380.WIS-TC-4424.tar1.xz

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

Title:
  Linux, Ubuntu, 18.04, CI, NB13, Display setting show 3 monitors when
  connect TBT3 monitor(FR:100%)

Status in Glance:
  New

Bug description:
  
  Description:
  Connect five LaCie d2 Thunderbolt-3 External HDDs to SUT as daisy chain, plug 
a LG 27" 5K Thunderbolt Type-3 Monitor as 6th deivce to the 5th HDD's TBT port, 
Display setting show 3 monitors.

  Expected Behavior:
  In Linux OS, connect five LaCie d2 Thunderbolt-3 External HDDs to SUT as 
daisy chain, plug a LG 27" 5K Thunderbolt Type-3 Monitor as 6th deivce to the 
5th HDD's TBT port, Display setting show 1 monitor.

  Severity:
  Sev-2
  P3
  C3
  L2

  Test Environment:
  1. Project: Northbay 13 SKU7
  2. BIOS: 0.4.0
  3. OS: CI Ubuntu 18.04
  4. 5k monitor: LG 27MD5KA-B

  Note:
  1. VP on TBT monitor directy connect to SUT TBT Port

  Cross Platform:
  N/A

  Test case:
  CSV-TC-5234[WIS-TC-4424] Linux_Thunderbolt3 - HDDs and Monitor Connected In 
Daisy-Chain Format Functionality Test step:17
   
  Steps to Reproduce:  
  1. Plug in the Sixth (6th) device  LG 27" 5KMonitor  to the second  
Thunderbolt-3  port on the back of the fifth (5th)  LaCie d2 Thunderbolt-3 
External HDD
  2. Check to verify that the sixth (6th) device, the  LG 27" 5K Thunderbolt 
Type-3 Monitor  is properly enumerated and functioning. 
  3. Check the Linux OS Display Setting ,Find the Display setting show 3 
monitors .-->problem(Refer to pic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1804416/+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 1804420] [NEW] placement unit test placement.tests.unit.cmd.test_manage.TestCommandParsers.test_commands_associated fails on CentOS 7

2018-11-21 Thread Javier Peña

Public bug reported:

Test
placement.tests.unit.cmd.test_manage.TestCommandParsers.test_commands_associated
fails to run using tox -epy27 on CentOS 7. However, it works fine on
Fedora 28 (with a different Python 2 version).

I get the following:

placement.tests.unit.cmd.test_manage.TestCommandParsers.test_commands_associated


Captured stdout:

usage: run db [-h] {sync,version} ...

optional arguments:
  -h, --help  show this help message and exit

subcommands:
  database commands

  {sync,version}
sync  Sync the datatabse to the current version.
version   Report the current database version.


Captured traceback:
~~~
Traceback (most recent call last):
  File "placement/tests/unit/cmd/test_manage.py", line 55, in 
test_commands_associated
mock_command.assert_called_once_with()
  File "/placement/.tox/py27/lib/python2.7/site-packages/mock/mock.py", 
line 947, in assert_called_once_with
raise AssertionError(msg)
AssertionError: Expected 'db_version' to be called once. Called 0 times.

This started to fail since https://review.openstack.org/600161 was
merged.

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

Title:
  placement unit test
  
placement.tests.unit.cmd.test_manage.TestCommandParsers.test_commands_associated
  fails on CentOS 7

Status in OpenStack Compute (nova):
  New

Bug description:
  Test
  
placement.tests.unit.cmd.test_manage.TestCommandParsers.test_commands_associated
  fails to run using tox -epy27 on CentOS 7. However, it works fine on
  Fedora 28 (with a different Python 2 version).

  I get the following:

  
placement.tests.unit.cmd.test_manage.TestCommandParsers.test_commands_associated
  


  Captured stdout:
  
  usage: run db [-h] {sync,version} ...
  
  optional arguments:
-h, --help  show this help message and exit
  
  subcommands:
database commands
  
{sync,version}
  sync  Sync the datatabse to the current version.
  version   Report the current database version.
  

  Captured traceback:
  ~~~
  Traceback (most recent call last):
File "placement/tests/unit/cmd/test_manage.py", line 55, in 
test_commands_associated
  mock_command.assert_called_once_with()
File "/placement/.tox/py27/lib/python2.7/site-packages/mock/mock.py", 
line 947, in assert_called_once_with
  raise AssertionError(msg)
  AssertionError: Expected 'db_version' to be called once. Called 0 times.

  This started to fail since https://review.openstack.org/600161 was
  merged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1804420/+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 1804414] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Can't set max resolution on 5K monitor that connected to SUT(FR:100%)

Public bug reported:

Description:
Connect a LG 27" 5K Thunderbolt Type-3 Monitor to the  Thunderbolt-3 port of 
SUT, can't set maximum resolution(5160x2880) in Display setting, the maximum 
can be set is 4096 x 2304.

Expected Behavior:
Connect a LG 27" 5K Thunderbolt Type-3 Monitor to the  Thunderbolt-3 port of 
SUT, can set maximum resolution(5160x2880) in Display setting.


Severity:
Sev-2
P3
C3
L2

Test Environment:
1. Project: Northbay 13 SKU7
2. BIOS: 0.4.0
3. OS: CI Ubuntu 18.04
4. Monitor: LG 27MD5KA-B 

Note:
1. VP on Join Displays, External only mode

Cross Platform:
N/A

Test case:
CSV-TC-5234[WIS-TC-4424] Linux_Thunderbolt3 - HDDs and Monitor Connected In 
Daisy-Chain Format Functionality Test step:18

Steps to Reproduce:  
1. Power on SUT, then plugging in the  LG 27" 5K Thunderbolt Type-3 Monitor  to 
the  Thunderbolt-3  port on SUT;
2. Set SUT and the external monitor to external only mode;
3. Go to the Display Setting and Check to make sure that the  resolution 
4. Find can't set maximum resolution(5160x2880) in Display setting, the maximum 
can be set is 4096 x 2304.-->problem(Refer to pic)

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: north-bay-13

** Attachment added: "Lost max  resolution.jpg"
   
https://bugs.launchpad.net/bugs/1804414/+attachment/5214926/+files/Lost%20max%20%20resolution.jpg

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

Title:
  Linux, Ubuntu, 18.04, CI, NB13, Can't set max resolution on 5K monitor
  that connected to SUT(FR:100%)

Status in Glance:
  New

Bug description:
  Description:
  Connect a LG 27" 5K Thunderbolt Type-3 Monitor to the  Thunderbolt-3 port of 
SUT, can't set maximum resolution(5160x2880) in Display setting, the maximum 
can be set is 4096 x 2304.

  Expected Behavior:
  Connect a LG 27" 5K Thunderbolt Type-3 Monitor to the  Thunderbolt-3 port of 
SUT, can set maximum resolution(5160x2880) in Display setting.

  
  Severity:
  Sev-2
  P3
  C3
  L2

  Test Environment:
  1. Project: Northbay 13 SKU7
  2. BIOS: 0.4.0
  3. OS: CI Ubuntu 18.04
  4. Monitor: LG 27MD5KA-B 

  Note:
  1. VP on Join Displays, External only mode

  Cross Platform:
  N/A

  Test case:
  CSV-TC-5234[WIS-TC-4424] Linux_Thunderbolt3 - HDDs and Monitor Connected In 
Daisy-Chain Format Functionality Test step:18

  Steps to Reproduce:  
  1. Power on SUT, then plugging in the  LG 27" 5K Thunderbolt Type-3 Monitor  
to the  Thunderbolt-3  port on SUT;
  2. Set SUT and the external monitor to external only mode;
  3. Go to the Display Setting and Check to make sure that the  resolution 
  4. Find can't set maximum resolution(5160x2880) in Display setting, the 
maximum can be set is 4096 x 2304.-->problem(Refer to pic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1804414/+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 1804415] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Can't show select device box if power on with external speak insert.

Public bug reported:

Description:
Power off SUT, plug in external speaker, SUT can't pop-up 'Select Audio Device' 
window when boot to Ubuntu OS desktop.(FR:100%) 

Expected Behavior:
SUT should pop-up 'Select Audio Device' window when boot to Ubuntu OS desktop.

Severity:
Sev-2
P3
C3
L2

Test Environment:
1. Project: Northbay 13 SKU10
2. BIOS: 0.4.1
3. OS:CI Ubuntu 18.04
4. Speaker-07 Dell Ax210 REV-A01

Note:
VP on Northbay all skus

Cross Platform:
N/A

Test case:
[CSV-TC-4601][WIS-TC-4187] Linux_USB - USB Type-C With VGA Video Test, step2
 
Steps to Reproduce:  
1. Power off SUT, plug external speaker.
2. Power on SUT, found can't pop-up 'Select Audio Device' window.-->problem

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: north-bay-13

** Attachment added: "sosreport-speaker.WIS-TC-4187-20181120052522.tar.xz"
   
https://bugs.launchpad.net/bugs/1804415/+attachment/5214927/+files/sosreport-speaker.WIS-TC-4187-20181120052522.tar.xz

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

Title:
  Linux, Ubuntu, 18.04, CI, NB13, Can't show select device box if power
  on with external speak insert.

Status in Glance:
  New

Bug description:
  Description:
  Power off SUT, plug in external speaker, SUT can't pop-up 'Select Audio 
Device' window when boot to Ubuntu OS desktop.(FR:100%) 

  Expected Behavior:
  SUT should pop-up 'Select Audio Device' window when boot to Ubuntu OS desktop.

  Severity:
  Sev-2
  P3
  C3
  L2

  Test Environment:
  1. Project: Northbay 13 SKU10
  2. BIOS: 0.4.1
  3. OS:CI Ubuntu 18.04
  4. Speaker-07 Dell Ax210 REV-A01

  Note:
  VP on Northbay all skus

  Cross Platform:
  N/A

  Test case:
  [CSV-TC-4601][WIS-TC-4187] Linux_USB - USB Type-C With VGA Video Test, step2
   
  Steps to Reproduce:  
  1. Power off SUT, plug external speaker.
  2. Power on SUT, found can't pop-up 'Select Audio Device' window.-->problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1804415/+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 1804413] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Can't redetecte thunderbolt device after plug it back.(FR:10%)

Public bug reported:


Description:
While all six Thunderbolt-3 devices, the LaCie d2 Thunderbolt-3 External HDD 
and the "LG 27" 5K Thunderbolt Type-3 Monitor" are plugged in the Daisy-Chain 
format to the SUT Thunderbolt Port, safely unplug all six Thunderbolt Devices 
from the Thunderbolt-3 port of the SUT. Then replug the six thunderbolt devices 
to SUT thunderbolt port. Find the device can't be detected.

Expected Behavior:
No problem safely unplugging all six Thunderbolt-3 Devices. The SUT correctly 
detected this change.

Severity:
Sev-3
P3
C3
L4

Test Environment:
1. Project: Northbay 13 SKU7
2. BIOS: 0.4.0
3. OS: CI Ubuntu 18.04
4. 5k monitor: LG 27MD5KA-B
5. TBT3 HDD: LaCIE d2 Thunderbolt 3 
ST6000NE0023-2EX110*2
ST6000NE0023-2Eh11c*3

Note:
1. VP on hot plug
2. VNP on Win10

Cross Platform:
N/A

Test case:
CSV-TC-5234[WIS-TC-4424] Linux_Thunderbolt3 - HDDs and Monitor Connected In 
Daisy-Chain Format Functionality Test step:23
 
Steps to Reproduce:  
1. Six Thunderbolt-3 devices, the LaCie d2 Thunderbolt-3 External HDD and the 
"LG 27" 5K Thunderbolt Type-3 Monitor" are plugged in the  Daisy-Chain format 
to the SUT Thunderbolt Port;
2. Safely Unplug all six  Thunderbolt Devices from the  Thunderbolt-3  port of 
the SUT;
3. Wait one minute, replug the six thunderbolt device to SUT thunderbolt 
port.Find the device can't be detected.-->problem

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: north-bay-13

** Attachment added: "sosreport-genericlog.-20181117045121.tar.xz"
   
https://bugs.launchpad.net/bugs/1804413/+attachment/5214924/+files/sosreport-genericlog.-20181117045121.tar.xz

** Attachment removed: "sosreport-genericlog.-20181117045121.tar.xz"
   
https://bugs.launchpad.net/glance/+bug/1804413/+attachment/5214924/+files/sosreport-genericlog.-20181117045121.tar.xz

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

Title:
Linux, Ubuntu, 18.04, CI, NB13, Can't redetecte thunderbolt device
  after plug it back.(FR:10%)

Status in Glance:
  New

Bug description:
  
  Description:
  While all six Thunderbolt-3 devices, the LaCie d2 Thunderbolt-3 External HDD 
and the "LG 27" 5K Thunderbolt Type-3 Monitor" are plugged in the Daisy-Chain 
format to the SUT Thunderbolt Port, safely unplug all six Thunderbolt Devices 
from the Thunderbolt-3 port of the SUT. Then replug the six thunderbolt devices 
to SUT thunderbolt port. Find the device can't be detected.

  Expected Behavior:
  No problem safely unplugging all six Thunderbolt-3 Devices. The SUT correctly 
detected this change.

  Severity:
  Sev-3
  P3
  C3
  L4

  Test Environment:
  1. Project: Northbay 13 SKU7
  2. BIOS: 0.4.0
  3. OS: CI Ubuntu 18.04
  4. 5k monitor: LG 27MD5KA-B
  5. TBT3 HDD: LaCIE d2 Thunderbolt 3 
  ST6000NE0023-2EX110*2
  ST6000NE0023-2Eh11c*3

  Note:
  1. VP on hot plug
  2. VNP on Win10

  Cross Platform:
  N/A

  Test case:
  CSV-TC-5234[WIS-TC-4424] Linux_Thunderbolt3 - HDDs and Monitor Connected In 
Daisy-Chain Format Functionality Test step:23
   
  Steps to Reproduce:  
  1. Six Thunderbolt-3 devices, the LaCie d2 Thunderbolt-3 External HDD and the 
"LG 27" 5K Thunderbolt Type-3 Monitor" are plugged in the  Daisy-Chain format 
to the SUT Thunderbolt Port;
  2. Safely Unplug all six  Thunderbolt Devices from the  Thunderbolt-3  port 
of the SUT;
  3. Wait one minute, replug the six thunderbolt device to SUT thunderbolt 
port.Find the device can't be detected.-->problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1804413/+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 1799137] Re: [l3][port_forwarding] should not allow creating port_forwarding to a port which already has a binding floating IP

Reviewed:  https://review.openstack.org/614452
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=b8d2ab8543a27b03bde534ef994027d9b44556c4
Submitter: Zuul
Branch:master

commit b8d2ab8543a27b03bde534ef994027d9b44556c4
Author: LIU Yulong 
Date:   Mon Oct 8 14:52:16 2018 +0800

Prevent create port forwarding to port which has binding fip

For dvr scenario, if port has a bound floating, and then create
port forwarding to it, this port forwarding will not work, due to
the traffic is redirected to dvr rules.

This patch restricts such API request, if user try to create port
forwarding to a port, check if it has bound floating IP first.
This will be run for all type of routers, since neutron should
not let user to waste public IP address on a port which already
has a floating IP, it can take care all the procotol port
numbers.

Closes-Bug: #1799137
Change-Id: I4ba4b023d79185f8d478d60ce16417d3501bf785


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

Title:
  [l3][port_forwarding] should not allow creating port_forwarding to a
  port which already has a binding floating IP

Status in neutron:
  Fix Released

Bug description:
  Should not allow creating port_forwarding to a port which already has
  a binding floating IP for dvr routers.

  ENV: devstack master

  step to reproduce:
  1. create one distributed router, and connected it to private subnet, and set 
public gateway.
  2. create VM to the private subnet
  3. binding floating IP A to VM port
  4. create floating IP B with port forwarding to the VM port

  Then floating IP B with port forwarding will not work. This should be
  restricted by neutron.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1799137/+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 1804409] [NEW] Linux, Ubuntu, 18.04, NB13, "lspci -v" Command can't list Single-c Salomon and device connect on it.(FR:100%)