[Yahoo-eng-team] [Bug 1804757] [NEW] Linux, Ubuntu, 18.04, NB13, Monitors plugged to Salomon dock show garbage after change resolution.(FR:2/10times)
Public bug reported: Description: Connect a Single-c Salomon Dock to SUT, connect 3 monitors to dock, change resolution of external monitors to any value, external monitor show garbage. Move mouse or Press Keyboard, garbage disappear. Expected Behavior: External monitor don't show garbage after change resolution. Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:CI Ubuntu 18.04 4. Salomon SINGLE-C Dock 165: DP/N :0YVYPW REV X00 FW:00.00.12.01 5. Monitor: Dell P2214H (Monitor-15), Dell S2718HN(Monitor-77), Alienware AW2518H(Monitor-83) Note: 1. VP on Salomon TBT DOCK-126 REV-X00 Dell Salomon WD19TB Thunderbolt3 Dock DP/N 0XHKGV Salomon_TBT3 FW:00.00.12 2. VP on Dock/unDock 3. VP on BME/IE Dock Cross Platform: N/A Test case: [CSV-TC-5209][WIS-TC-4396] Linux_NB_Salomon-Wired-Dock-The "Cold Boot" Stress Test step:15 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, two DP monitors to SUT; 4. Change resolution of external monitors; 5. Find one External Monitor show Garbage.>problem(refer to Video) 6. Move mouse or press keyboard garbage disapear. ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-genericlog.1-20181120045802.tar.xz" https://bugs.launchpad.net/bugs/1804757/+attachment/5215515/+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/1804757 Title: Linux, Ubuntu,18.04, NB13, Monitors plugged to Salomon dock show garbage after change resolution.(FR:2/10times) Status in Glance: New Bug description: Description: Connect a Single-c Salomon Dock to SUT, connect 3 monitors to dock, change resolution of external monitors to any value, external monitor show garbage. Move mouse or Press Keyboard, garbage disappear. Expected Behavior: External monitor don't show garbage after change resolution. Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:CI Ubuntu 18.04 4. Salomon SINGLE-C Dock 165: DP/N :0YVYPW REV X00 FW:00.00.12.01 5. Monitor: Dell P2214H (Monitor-15), Dell S2718HN(Monitor-77), Alienware AW2518H(Monitor-83) Note: 1. VP on Salomon TBT DOCK-126 REV-X00 Dell Salomon WD19TB Thunderbolt3 Dock DP/N 0XHKGV Salomon_TBT3 FW:00.00.12 2. VP on Dock/unDock 3. VP on BME/IE Dock Cross Platform: N/A Test case: [CSV-TC-5209][WIS-TC-4396] Linux_NB_Salomon-Wired-Dock-The "Cold Boot" Stress Test step:15 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, two DP monitors to SUT; 4. Change resolution of external monitors; 5. Find one External Monitor show Garbage.>problem(refer to Video) 6. Move mouse or press keyboard garbage disapear. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804757/+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 1804756] [NEW] Linux, Ubuntu, 18.04, CI, NB13, External speaker output noise when plug/unplug on Salomon dock.(FR:100%)
Public bug reported: Description: Plug/unplug the audio jack external speaker that connected to Salomon Dock's Headset port, and the external speakers output noise sound. Expected Behavior: External speakers not output noise when plug/unplug on Salomon 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: Salomon Single-C Dock 165: DP/N :0YVYPW REV X00 FW:00.00.12.01 6. Speaker: Dell Speaker-20 (REV-A00) Dell 2.0 speaker AE215 Notes: 1. VP on BME Dock 2. VP on IE Dock 3. VP on Headset 4. Line-out port can't detect external device Cross platform: 1. N/A Test Case: [CSV-TC-5194][WIS-TC-4407] Linux_NB_Salomon-Wired-Dock-The Docked SUT "Plug/Unplug" Test step:16 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, dock the Salomon dock to SUT. 3. Plug/unplug external speaketr to headset port of Salomon dock. 4. Find the external speaker output noise--->Problem(refer to video) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "VID_speaker noise.mp4" https://bugs.launchpad.net/bugs/1804756/+attachment/5215511/+files/VID_speaker%20noise.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/1804756 Title: Linux, Ubuntu, 18.04, CI, NB13, External speaker output noise when plug/unplug on Salomon dock.(FR:100%) Status in Glance: New Bug description: Description: Plug/unplug the audio jack external speaker that connected to Salomon Dock's Headset port, and the external speakers output noise sound. Expected Behavior: External speakers not output noise when plug/unplug on Salomon 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: Salomon Single-C Dock 165: DP/N :0YVYPW REV X00 FW:00.00.12.01 6. Speaker: Dell Speaker-20 (REV-A00) Dell 2.0 speaker AE215 Notes: 1. VP on BME Dock 2. VP on IE Dock 3. VP on Headset 4. Line-out port can't detect external device Cross platform: 1. N/A Test Case: [CSV-TC-5194][WIS-TC-4407] Linux_NB_Salomon-Wired-Dock-The Docked SUT "Plug/Unplug" Test step:16 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, dock the Salomon dock to SUT. 3. Plug/unplug external speaketr to headset port of Salomon 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/1804756/+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 1791963] Re: Unexpected API Error
[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.] ** Changed in: nova Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1791963 Title: Unexpected API Error Status in OpenStack Compute (nova): Expired Bug description: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-41b96d36-f5eb-41b3-91f9-78240052bdca) NOVA API Log: 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions [req-acddcde4-3811-4c79-a5d0-3f91b15f4692 7ca32b814591425b8ea8448522d2b86b a06097f729654a579cde3891b69cb85f - default default] Unexpected exception in API method 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions Traceback (most recent call last): 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 338, in wrapped 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions return f(*args, **kwargs) 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 181, in wrapper 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 181, in wrapper 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/compute/servers.py", line 214, in detail 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions servers = self._get_servers(req, is_detail=True) 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/compute/servers.py", line 357, in _get_servers 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions sort_keys=sort_keys, sort_dirs=sort_dirs) 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 2488, in get_all 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions sort_dirs=sort_dirs) 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 2631, in _get_instances_by_filters 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions expected_attrs=fields, sort_keys=sort_keys, sort_dirs=sort_dirs) 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/oslo_versionedobjects/base.py", line 184, in wrapper 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions result = fn(cls, context, *args, **kwargs) 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/objects/instance.py", line 1227, in get_by_filters 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions use_slave=use_slave, sort_keys=sort_keys, sort_dirs=sort_dirs) 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 236, in wrapper 2018-09-11 03:09:06.446 6305 ERROR nova.api.openstack.extensions return f(*args, **kwargs) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1791963/+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 1804745] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Monitors connected as Daisy chain, video play show garbage.(FR:100%)
Public bug reported: Description: Connect 5 LaCie d2 Thunderbolt-3 External HDDs as Daisy chain to SUT, monitor connected to the 5th HDD as Daisy chain, video play window on these displays, video play show garbage on these displays. Expected Behavior: No problems opening the Linux Video and start the movie play on the primary display 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 2. VP on play video on external monitor 3. VNP on play video on SUT without TBT monitor connected. 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:20 Steps to Reproduce: 1. Plug in the Sixth (6th) device LG 27" 5K monitor 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. Then open up the Linux Videos and start playing the 1080p movie in the MPEG-4 format on the primary display; 4. While start the movie play on the primary display, the video show garbage.--Problem(Refer to video) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "Video Garbage.mp4" https://bugs.launchpad.net/bugs/1804745/+attachment/5215488/+files/Video%20Garbage.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/1804745 Title: Linux, Ubuntu, 18.04, CI, NB13, Monitors connected as Daisy chain, video play show garbage.(FR:100%) Status in Glance: New Bug description: Description: Connect 5 LaCie d2 Thunderbolt-3 External HDDs as Daisy chain to SUT, monitor connected to the 5th HDD as Daisy chain, video play window on these displays, video play show garbage on these displays. Expected Behavior: No problems opening the Linux Video and start the movie play on the primary display 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 2. VP on play video on external monitor 3. VNP on play video on SUT without TBT monitor connected. 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:20 Steps to Reproduce: 1. Plug in the Sixth (6th) device LG 27" 5K monitor 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. Then open up the Linux Videos and start playing the 1080p movie in the MPEG-4 format on the primary display; 4. While start the movie play on the primary display, the video show garbage.--Problem(Refer to video) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804745/+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 1804743] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Press Dock's button once, can't wake SUT from suspend(FR:3/3Units)
Public bug reported: Description: Connect BME dock to SUT, press the dock button to put the SUT into the suspend mode. Wait for 30-seconds and press Dock's button once, can't wake SUT from suspend, need press it again to wake SUT. Expected Behavior: No problems waking up the SUT from Suspend mode by pressing the "Dock Button". 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. DELL BME DOCK-114(REV-A05 FW:1.0.0) Note: 1. VP on other TBT SKU 2. VNP on wake form shutdown 3. VNP on Salomon TBT3 & single-C dock(REV-X00 FW:0.0.12) 4. VP on IE dock(REV-A05 Dock-113 FW:0.1.16) Cross Platform: N/A Test case: CSV-TC-4645[WIS-TC-4202] Linux_NB_BME-Wired-Dock-The "Dock Button Behavior" Test step:19 Steps to Reproduce: 1. Connect BME Dock to SUT, set press the dock button to put the SUT into the Suspend mode; 2. Then press the dock button to put the SUT into the Suspend mode; 3. Wait about 30-seconds, press the "Dock Button" again to wake it up. 4. Find can't wake from suspend ,need press it again to wake SUT.-->problem ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-DOCKbutton.4202-20181117065226.tar.xz" https://bugs.launchpad.net/bugs/1804743/+attachment/5215487/+files/sosreport-DOCKbutton.4202-20181117065226.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/1804743 Title: Linux, Ubuntu, 18.04, CI, NB13, Press Dock's button once, can't wake SUT from suspend(FR:3/3Units) Status in Glance: New Bug description: Description: Connect BME dock to SUT, press the dock button to put the SUT into the suspend mode. Wait for 30-seconds and press Dock's button once, can't wake SUT from suspend, need press it again to wake SUT. Expected Behavior: No problems waking up the SUT from Suspend mode by pressing the "Dock Button". 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. DELL BME DOCK-114(REV-A05 FW:1.0.0) Note: 1. VP on other TBT SKU 2. VNP on wake form shutdown 3. VNP on Salomon TBT3 & single-C dock(REV-X00 FW:0.0.12) 4. VP on IE dock(REV-A05 Dock-113 FW:0.1.16) Cross Platform: N/A Test case: CSV-TC-4645[WIS-TC-4202] Linux_NB_BME-Wired-Dock-The "Dock Button Behavior" Test step:19 Steps to Reproduce: 1. Connect BME Dock to SUT, set press the dock button to put the SUT into the Suspend mode; 2. Then press the dock button to put the SUT into the Suspend mode; 3. Wait about 30-seconds, press the "Dock Button" again to wake it up. 4. Find can't wake from suspend ,need press it again to wake SUT.-->problem To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804743/+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 1804736] [NEW] Linux, Ubuntu, 18.04, CI, NB13, SUT show 'System program problem detected' sometimes.(FR:7/7units)
Public bug reported: Description: Boot to Ubuntu OS, SUT will show 'System program problem detected' sometimes. Expected Behavior: SUT doesn't show any unexpected problems. Severity: Sev-2 P3 C3 L2 Test environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 4. OS: CI Ubuntu 18.04 Notes: VP on Northbay all skus Cross Platform: NA Test case: [CSV-TC-4602][WIS-TC-4188] Linux_USB - USB Type-C with Dell Ultra-HD 4K Display/Monitor Test (DisplayPort) Step 2 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, found SUT show 'System program problem detected' sometimes.-->Problem(refer to pic) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-OS.WIS-TC-4188-20181122070605.tar.xz" https://bugs.launchpad.net/bugs/1804736/+attachment/5215471/+files/sosreport-OS.WIS-TC-4188-20181122070605.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/1804736 Title: Linux, Ubuntu, 18.04, CI, NB13, SUT show 'System program problem detected' sometimes.(FR:7/7units) Status in Glance: New Bug description: Description: Boot to Ubuntu OS, SUT will show 'System program problem detected' sometimes. Expected Behavior: SUT doesn't show any unexpected problems. Severity: Sev-2 P3 C3 L2 Test environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 4. OS: CI Ubuntu 18.04 Notes: VP on Northbay all skus Cross Platform: NA Test case: [CSV-TC-4602][WIS-TC-4188] Linux_USB - USB Type-C with Dell Ultra-HD 4K Display/Monitor Test (DisplayPort) Step 2 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, found SUT show 'System program problem detected' sometimes.-->Problem(refer to pic) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804736/+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 1804731] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Thunderbolt HDD can be detected under"User Authorization"mode.(FR:100%)
Public bug reported: Description: 1. Set the Thunderbolt Security Level as " User Authorization "in BIOS Setup.Then plug in the TBT3 HDD to TBT port on SUT, Open Disks Utility, check that TB3 HDD ,Find the HDD still listed and recognized by the OS(3/3Units) 2. Run command "cat /sys/bus/thunderbolt/devices/0-1/authorized", it return "1" Expected Behavior: 1. The TBT 3 HDD can't be detected and not list in Disks Utility 2. Run command "cat /sys/bus/thunderbolt/devices/0-1/authorized", it should return "0"(0 means no PCIe tunnels are created yes.) 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.TBT3 HDD:LaCIE d2 Thunderbolt 3 ST6000NE0023-2EX110*2 ST6000NE0023-2Eh11c*3 Note: VP on other TBT SKU Cross Platform: N/A Test case: CSV-TC-4635[WIS-TC-4199] Linux_Thunderbolt3 - Storage Basic Functionality Test with Different Security Levels step:16 Steps to Reproduce: 1.Enter the BIOS, go to "Thunderbolt Option" to set the Thunderbolt Security Level as " User Authorization ". 2.Then plug in the TBT3 HDD to TBT port on SUT, Open Disks Utility, check that TB3 HDD ,Find the HDD still listed and recognized by the OS-->problem 3.Run command "cat /sys/bus/thunderbolt/devices/0-1/authorized", Find the return show "1"-->problem. ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-Ubuntu18.04LTSCILatitude-5380.WIS-TC-4199-20181117033043.tar.xz" https://bugs.launchpad.net/bugs/1804731/+attachment/5215460/+files/sosreport-Ubuntu18.04LTSCILatitude-5380.WIS-TC-4199-20181117033043.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/1804731 Title: Linux, Ubuntu, 18.04, CI, NB13, Thunderbolt HDD can be detected under"User Authorization"mode.(FR:100%) Status in Glance: New Bug description: Description: 1. Set the Thunderbolt Security Level as " User Authorization "in BIOS Setup.Then plug in the TBT3 HDD to TBT port on SUT, Open Disks Utility, check that TB3 HDD ,Find the HDD still listed and recognized by the OS(3/3Units) 2. Run command "cat /sys/bus/thunderbolt/devices/0-1/authorized", it return "1" Expected Behavior: 1. The TBT 3 HDD can't be detected and not list in Disks Utility 2. Run command "cat /sys/bus/thunderbolt/devices/0-1/authorized", it should return "0"(0 means no PCIe tunnels are created yes.) 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.TBT3 HDD:LaCIE d2 Thunderbolt 3 ST6000NE0023-2EX110*2 ST6000NE0023-2Eh11c*3 Note: VP on other TBT SKU Cross Platform: N/A Test case: CSV-TC-4635[WIS-TC-4199] Linux_Thunderbolt3 - Storage Basic Functionality Test with Different Security Levels step:16 Steps to Reproduce: 1.Enter the BIOS, go to "Thunderbolt Option" to set the Thunderbolt Security Level as " User Authorization ". 2.Then plug in the TBT3 HDD to TBT port on SUT, Open Disks Utility, check that TB3 HDD ,Find the HDD still listed and recognized by the OS-->problem 3.Run command "cat /sys/bus/thunderbolt/devices/0-1/authorized", Find the return show "1"-->problem. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804731/+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 1804729] [NEW] Linux, Ubuntu, 18.04, NB13, Show Skylake information in Terminal after run lspci -v.(FR:100%)
Public bug reported: Description: Show two Skylake information in Terminal after run lspci -v. Expected Behavior: Shoud show Whiskey lake information in Terminal after run lspci -v. Severity: Sev-3 P3 C3 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:CI Ubuntu 18.04 Note: NA Cross Platform: N/A Test case: [CSV-TC-5196][WIS-TC-4409] Linux_NB_Salomon-Wired-Dock-The I/O Ports Functionality Test (1/2) step:6 Steps to Reproduce: 1. Flash Latest BIOS, install Ubuntu OS 18.04. 2. Boot to OS, Open Terminal-->Type lspci -v-->press 'enter' 3. Find show two Skylake information on Whiskey lake platform.>problem(refer to pic) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "show two Skylake info on Whiskey lake.jpg" https://bugs.launchpad.net/bugs/1804729/+attachment/5215458/+files/show%20two%20Skylake%20info%20on%20Whiskey%20lake.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/1804729 Title: Linux, Ubuntu,18.04, NB13, Show Skylake information in Terminal after run lspci -v.(FR:100%) Status in Glance: New Bug description: Description: Show two Skylake information in Terminal after run lspci -v. Expected Behavior: Shoud show Whiskey lake information in Terminal after run lspci -v. Severity: Sev-3 P3 C3 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:CI Ubuntu 18.04 Note: NA Cross Platform: N/A Test case: [CSV-TC-5196][WIS-TC-4409] Linux_NB_Salomon-Wired-Dock-The I/O Ports Functionality Test (1/2) step:6 Steps to Reproduce: 1. Flash Latest BIOS, install Ubuntu OS 18.04. 2. Boot to OS, Open Terminal-->Type lspci -v-->press 'enter' 3. Find show two Skylake information on Whiskey lake platform.>problem(refer to pic) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804729/+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 1804728] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Plug DP monitor to Salomon as default device but can't output sound.(FR:1/5times)
Public bug reported: Description: Connect a Salomon Dock to SUT, connect a DP monitor to Salomon Dock, set Audio device to "HDMI/Disport 2-Built-in Audio"(DP Monitor), Play a Video, Find no Voice output from the speaker that connected to monitor.(FR:2/5times) Expected Behavior: The Audio ouput voice normally on DP Monitor connected on Salomon Dock. Severity: Sev-2 P2 C2 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 5. Monitor: DELL AW2518H Note: 1. VNP on HDMI Port on Salomon; 2. VNP on Type-c Display Port on Salomon; Cross Platform: N/A Test case: [CSV-TC-5195][WIS-TC-4408] Linux_NB_Salomon-Wired-Dock-The "USB-C" Connectors/Ports Test with "USB-C v3.1 (Gen-2) Storage Devices" step:8 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 DP monotior on Salomon Dock; 4. Set Audio device to "HDMI/Disport 2-Built-in Audio"(DP Monitor) in Sound setting; 5. Play a Video, Find no Voice output from the speaker that connected to monitor.--->problem(refer to video) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "VID_speaker no voice.mp4" https://bugs.launchpad.net/bugs/1804728/+attachment/5215456/+files/VID_speaker%20no%20voice.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/1804728 Title: Linux, Ubuntu, 18.04, CI, NB13, Plug DP monitor to Salomon as default device but can't output sound.(FR:1/5times) Status in Glance: New Bug description: Description: Connect a Salomon Dock to SUT, connect a DP monitor to Salomon Dock, set Audio device to "HDMI/Disport 2-Built-in Audio"(DP Monitor), Play a Video, Find no Voice output from the speaker that connected to monitor.(FR:2/5times) Expected Behavior: The Audio ouput voice normally on DP Monitor connected on Salomon Dock. Severity: Sev-2 P2 C2 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 5. Monitor: DELL AW2518H Note: 1. VNP on HDMI Port on Salomon; 2. VNP on Type-c Display Port on Salomon; Cross Platform: N/A Test case: [CSV-TC-5195][WIS-TC-4408] Linux_NB_Salomon-Wired-Dock-The "USB-C" Connectors/Ports Test with "USB-C v3.1 (Gen-2) Storage Devices" step:8 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 DP monotior on Salomon Dock; 4. Set Audio device to "HDMI/Disport 2-Built-in Audio"(DP Monitor) in Sound setting; 5. Play a Video, Find no Voice output from the speaker that connected to monitor.--->problem(refer to video) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804728/+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 1804726] [NEW] Linux, Ubuntu, 18.04, NB13, Display setting show two Monitors when connect Salomon without Monitor.(FR:100%)
Public bug reported: Description: Connect a Single-c Salomon Dock without monitor to SUT, open display setting of Ubuntu, wait a while, find there is two monitors are listed. Expected Behavior: Display setting show one monitor when connect Salomon without Monitor. Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 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 Salomon TBT DOCK-126 REV-X00 Dell Salomon WD19TB Thunderbolt3 Dock DP/N 0XHKGV Salomon_TBT3 FW:00.00.12 2. VNP on IE/BME Dock Cross Platform: N/A Test case: [CSV-TC-5209][WIS-TC-4396] Linux_NB_Salomon-Wired-Dock-The "Cold Boot" Stress Test step:5 Steps to Reproduce: 1. Flash Latest BIOS, install Ubuntu OS 18.04. 2. Boot to OS, Connect a Salomon Dock to SUT; 3. Open Display setting of Ubuntu; 4. Find there is two Monitors are listed in Display setting.>problem(refer to pic) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "IMG_display setting show two monitors.jpg" https://bugs.launchpad.net/bugs/1804726/+attachment/5215447/+files/IMG_display%20setting%20show%20two%20monitors.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/1804726 Title: Linux, Ubuntu,18.04, NB13, Display setting show two Monitors when connect Salomon without Monitor.(FR:100%) Status in Glance: New Bug description: Description: Connect a Single-c Salomon Dock without monitor to SUT, open display setting of Ubuntu, wait a while, find there is two monitors are listed. Expected Behavior: Display setting show one monitor when connect Salomon without Monitor. Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 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 Salomon TBT DOCK-126 REV-X00 Dell Salomon WD19TB Thunderbolt3 Dock DP/N 0XHKGV Salomon_TBT3 FW:00.00.12 2. VNP on IE/BME Dock Cross Platform: N/A Test case: [CSV-TC-5209][WIS-TC-4396] Linux_NB_Salomon-Wired-Dock-The "Cold Boot" Stress Test step:5 Steps to Reproduce: 1. Flash Latest BIOS, install Ubuntu OS 18.04. 2. Boot to OS, Connect a Salomon Dock to SUT; 3. Open Display setting of Ubuntu; 4. Find there is two Monitors are listed in Display setting.>problem(refer to pic) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804726/+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 1804724] [NEW] Linux, Ubuntu, 18.04, NB13, Type-c USB3.1 Gen2 SSD will lost after dock/undock Salomon.(FR:3/10times)
Public bug reported: Description: Connect a Single-c Salomon Dock with three Monitors, Connect a Type-c USB3.1 Gen2 SSD to Salomon dock data port. Unplug/plug Salomon Dock, Typec-c SSD will lost. Expected Behavior: Type-c USB3.1 Gen2 SSD won't lost after dock/undock Salomon Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:CI Ubuntu 18.04 4. Salomon SINGLE-C Dock 165: DP/N :0YVYPW REV X00 FW:00.00.12.01 5. Type-c USB3.1 480G SanDisk SSD-26 A8881705 Note: N/A Cross Platform: N/A Test case: [CSV-TC-5194][WIS-TC-4407] Linux_NB_Salomon-Wired-Dock-The Docked SUT "Plug/Unplug" Test step:17/32 Steps to Reproduce: 1. Flash Latest BIOS, install Ubuntu OS 18.04. 2. Boot to OS, Connect a Salomon Dock to SUT with three Mnitors; 3. Connect a Type-c USB3.1 Gen2 SSD to Salomon dock data port. 4. Uplug Salomon Dock from SUT, wait 1 minute, Plug back Salomon Dock to SUT; 5. Find Typec-c SSD will lost.>problem(refer to pic) 6. Unplug/plug SanDisk A8881705 SSD from type-c data port on Dock, SSD will appear again. ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "IMG_type-c usb gen2 ssd lost.jpg" https://bugs.launchpad.net/bugs/1804724/+attachment/5215445/+files/IMG_type-c%20usb%20gen2%20ssd%20lost.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/1804724 Title: Linux, Ubuntu,18.04, NB13, Type-c USB3.1 Gen2 SSD will lost after dock/undock Salomon.(FR:3/10times) Status in Glance: New Bug description: Description: Connect a Single-c Salomon Dock with three Monitors, Connect a Type-c USB3.1 Gen2 SSD to Salomon dock data port. Unplug/plug Salomon Dock, Typec-c SSD will lost. Expected Behavior: Type-c USB3.1 Gen2 SSD won't lost after dock/undock Salomon Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:CI Ubuntu 18.04 4. Salomon SINGLE-C Dock 165: DP/N :0YVYPW REV X00 FW:00.00.12.01 5. Type-c USB3.1 480G SanDisk SSD-26 A8881705 Note: N/A Cross Platform: N/A Test case: [CSV-TC-5194][WIS-TC-4407] Linux_NB_Salomon-Wired-Dock-The Docked SUT "Plug/Unplug" Test step:17/32 Steps to Reproduce: 1. Flash Latest BIOS, install Ubuntu OS 18.04. 2. Boot to OS, Connect a Salomon Dock to SUT with three Mnitors; 3. Connect a Type-c USB3.1 Gen2 SSD to Salomon dock data port. 4. Uplug Salomon Dock from SUT, wait 1 minute, Plug back Salomon Dock to SUT; 5. Find Typec-c SSD will lost.>problem(refer to pic) 6. Unplug/plug SanDisk A8881705 SSD from type-c data port on Dock, SSD will appear again. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804724/+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 1804723] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Line-out port of Salomon Dock can't detect external speaker.(FR:100%)
Public bug reported: Description: Plug an audio jack external speaker to Line-out port of Salomon Dock, and the external speakers can't be detected. Expected Behavior: Plug External speaker to Line-out port of Salomon Dock can be detected . 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: Salomon SINGLE-C Dock 165: DP/N :0YVYPW REV X00 FW:00.00.12.01 6. Speaker: Dell SPEAKER-20 (REV-A00) Dell 2.0speaker (AE215) AE215 Notes: 1. VP on BME/IE Dock 2. VNP on Salomon dock headset audio port 3. VP on Salomon TBT DOCK-126 REV-X00 Dell Salomon WD19TB Thunderbolt3 Dock DP/N 0XHKGV Salomon_TBT3 FW:00.00.12 Cross platform: 1. N/A Test Case: [CSV-TC-5194][WIS-TC-4407] Linux_NB_Salomon-Wired-Dock-The Docked SUT "Plug/Unplug" Test step:16 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, connect the Salomon dock to SUT. 3. Plug external speaketr to Line-out port of Salomon dock. 4. Find the external speaker can't be detected.--->Problem(refer to video) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "VID_speaker no voice.mp4" https://bugs.launchpad.net/bugs/1804723/+attachment/5215443/+files/VID_speaker%20no%20voice.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/1804723 Title: Linux, Ubuntu, 18.04, CI, NB13, Line-out port of Salomon Dock can't detect external speaker.(FR:100%) Status in Glance: New Bug description: Description: Plug an audio jack external speaker to Line-out port of Salomon Dock, and the external speakers can't be detected. Expected Behavior: Plug External speaker to Line-out port of Salomon Dock can be detected . 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: Salomon SINGLE-C Dock 165: DP/N :0YVYPW REV X00 FW:00.00.12.01 6. Speaker: Dell SPEAKER-20 (REV-A00) Dell 2.0speaker (AE215) AE215 Notes: 1. VP on BME/IE Dock 2. VNP on Salomon dock headset audio port 3. VP on Salomon TBT DOCK-126 REV-X00 Dell Salomon WD19TB Thunderbolt3 Dock DP/N 0XHKGV Salomon_TBT3 FW:00.00.12 Cross platform: 1. N/A Test Case: [CSV-TC-5194][WIS-TC-4407] Linux_NB_Salomon-Wired-Dock-The Docked SUT "Plug/Unplug" Test step:16 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, connect the Salomon dock to SUT. 3. Plug external speaketr to Line-out port of Salomon dock. 4. Find the external speaker can't be detected.--->Problem(refer to video) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804723/+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 1804700] [NEW] keystone-manage bootstrap raises ValueError
Public bug reported: The 'keystone-manage bootstrap' command still raises Value Error despite 'keystone-manage fernet_setup' command was successful. The whole bug is: shuayb@shuayb-HP-EliteBook-Folio-9470m:~/keystone$ keystone-manage bootstrap Either --bootstrap-password argument or OS_BOOTSTRAP_PASSWORD must be set. 2018-11-22 21:51:51.394 3884 CRITICAL keystone [-] Unhandled error: ValueError 2018-11-22 21:51:51.394 3884 ERROR keystone Traceback (most recent call last): 2018-11-22 21:51:51.394 3884 ERROR keystone File "/home/shuayb/anaconda3/bin/keystone-manage", line 10, in 2018-11-22 21:51:51.394 3884 ERROR keystone sys.exit(main()) 2018-11-22 21:51:51.394 3884 ERROR keystone File "/home/shuayb/keystone/keystone/cmd/manage.py", line 41, in main 2018-11-22 21:51:51.394 3884 ERROR keystone cli.main(argv=sys.argv, developer_config_file=developer_config) 2018-11-22 21:51:51.394 3884 ERROR keystone File "/home/shuayb/keystone/keystone/cmd/cli.py", line 1349, in main 2018-11-22 21:51:51.394 3884 ERROR keystone CONF.command.cmd_class.main() 2018-11-22 21:51:51.394 3884 ERROR keystone File "/home/shuayb/keystone/keystone/cmd/cli.py", line 178, in main 2018-11-22 21:51:51.394 3884 ERROR keystone klass.do_bootstrap() 2018-11-22 21:51:51.394 3884 ERROR keystone File "/home/shuayb/keystone/keystone/cmd/cli.py", line 156, in do_bootstrap 2018-11-22 21:51:51.394 3884 ERROR keystone raise ValueError 2018-11-22 21:51:51.394 3884 ERROR keystone ValueError 2018-11-22 21:51:51.394 3884 ERROR keystone ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1804700 Title: keystone-manage bootstrap raises ValueError Status in OpenStack Identity (keystone): New Bug description: The 'keystone-manage bootstrap' command still raises Value Error despite 'keystone-manage fernet_setup' command was successful. The whole bug is: shuayb@shuayb-HP-EliteBook-Folio-9470m:~/keystone$ keystone-manage bootstrap Either --bootstrap-password argument or OS_BOOTSTRAP_PASSWORD must be set. 2018-11-22 21:51:51.394 3884 CRITICAL keystone [-] Unhandled error: ValueError 2018-11-22 21:51:51.394 3884 ERROR keystone Traceback (most recent call last): 2018-11-22 21:51:51.394 3884 ERROR keystone File "/home/shuayb/anaconda3/bin/keystone-manage", line 10, in 2018-11-22 21:51:51.394 3884 ERROR keystone sys.exit(main()) 2018-11-22 21:51:51.394 3884 ERROR keystone File "/home/shuayb/keystone/keystone/cmd/manage.py", line 41, in main 2018-11-22 21:51:51.394 3884 ERROR keystone cli.main(argv=sys.argv, developer_config_file=developer_config) 2018-11-22 21:51:51.394 3884 ERROR keystone File "/home/shuayb/keystone/keystone/cmd/cli.py", line 1349, in main 2018-11-22 21:51:51.394 3884 ERROR keystone CONF.command.cmd_class.main() 2018-11-22 21:51:51.394 3884 ERROR keystone File "/home/shuayb/keystone/keystone/cmd/cli.py", line 178, in main 2018-11-22 21:51:51.394 3884 ERROR keystone klass.do_bootstrap() 2018-11-22 21:51:51.394 3884 ERROR keystone File "/home/shuayb/keystone/keystone/cmd/cli.py", line 156, in do_bootstrap 2018-11-22 21:51:51.394 3884 ERROR keystone raise ValueError 2018-11-22 21:51:51.394 3884 ERROR keystone ValueError 2018-11-22 21:51:51.394 3884 ERROR keystone To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1804700/+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 1713499] Re: Cannot delete a neutron network, if the currently configured MTU is lower than the network's MTU
This is now Fix Released for Queens UCA since the patch is in 12.0.4 release and UCA no has 12.0.5 (from bug 1795424) ** Changed in: cloud-archive/queens Status: In Progress => Fix Released ** Changed in: neutron (Ubuntu Bionic) 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/1713499 Title: Cannot delete a neutron network, if the currently configured MTU is lower than the network's MTU Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive pike series: Fix Released Status in Ubuntu Cloud Archive queens series: Fix Released Status in neutron: Fix Released Status in neutron package in Ubuntu: Fix Released Status in neutron source package in Bionic: Fix Released Bug description: Currently, the neutron API returns an error [1] when trying to delete a neutron network which has a higher MTU than the configured MTU[2][3]. This issue has been noticed in Pike. [1] Error: http://paste.openstack.org/show/619627/ [2] neutron.conf: http://paste.openstack.org/show/619629/ [3] ml2_conf.ini: http://paste.openstack.org/show/619630/ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1713499/+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 1758868] Re: ovs restart can lead to critical ovs flows missing
*** This bug is a duplicate of bug 1584647 ***
https://bugs.launchpad.net/bugs/1584647
On the assumption that bug 1584647 resolved this issue marking as a dupe
- please comment if this is not the case or the issue remains.
** This bug has been marked a duplicate of bug 1584647
[SRU] "Interface monitor is not active" can be observed at ovs-agent start
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1758868
Title:
ovs restart can lead to critical ovs flows missing
Status in neutron:
New
Status in neutron package in Ubuntu:
New
Bug description:
Hi,
Running mitaka on xenial (neutron 2:8.4.0-0ubuntu6). We have l2pop and
no l3ha. Using ovs with GRE tunnels.
The cloud has around 30 compute nodes (mostly arm64). Last week, ovs
got restarted during a package upgrade :
2018-03-21 17:17:25 upgrade openvswitch-common:arm64
2.5.2-0ubuntu0.16.04.3 2.5.4-0ubuntu0.16.04.1
This led to instances on 2 arm64 compute nodes lose networking
completely. Upon closer inspection, I realized that a flow was missing
in br-tun table 3 : https://pastebin.ubuntu.com/p/VXRJJX8J3k/
I believe this is due to a race in ovs_neutron_agent.py. These flows
in table 3 are set up in provision_local_vlan() :
https://github.com/openstack/neutron/blob/mitaka-
eol/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L675
which is called by port_bound() :
https://github.com/openstack/neutron/blob/mitaka-eol/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L789-L791
which is called by treat_vif_port() :
https://github.com/openstack/neutron/blob/mitaka-
eol/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1405-L1410
which is called by treat_devices_added_or_updated() :
https://github.com/openstack/neutron/blob/mitaka-
eol/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1517-L1525
which is called by process_network_ports() :
https://github.com/openstack/neutron/blob/mitaka-
eol/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1618-L1623
which is called by the big rpc_loop() :
https://github.com/openstack/neutron/blob/mitaka-
eol/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L2023-L2029
So how does the agent knows when to create these table 3 flows ? Well, in
rpc_loop(), it checks for OVS restarts
(https://github.com/openstack/neutron/blob/mitaka-eol/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1947-L1948),
and if OVS did restart, it does some basic ovs setup (default flows, etc), and
(very important for later), it restarts the OVS polling manager.
Later (still in rpc_loop()), it sets "ovs_restarted" to True, and
process the ports as usual. The expected behaviour here is that since
the polling manager got restarted, any port up will be marked as
"added" and processed as such, in port_bound() (see call stack above).
If this function is called on a port when ovs_restarted is True, then
provision_local_vlan() will get called and will able the table 3
flows.
This is all working great under the assumption that the polling
manager (which is an async process) will raise the "I got new port !"
event before the rpc_loop() checks it (in process_port_events(),
called by process_port_info()). However, if for example the node is
under load, this may not always be the case.
What happens then is that the rpc_loop in which OVS is detected as
restarted doesn't see any change on the ports, and so does nothing.
The next run of the rpc_loop will process the "I got new port !"
events, but that loop will not be running with ovs_restarted set to
True, so the ports won't be brought up properly - more specifically,
the table 3 flows in br-tun will be missing. This is shown in the
debug logs : https://pastebin.ubuntu.com/p/M8yYn3YnQ6/ - you can see
the loop in which "OVS is restarted" is detected (loop iteration
320773) doesn't process any port ("iteration:320773 completed.
Processed ports statistics: {'regular': {'updated': 0, 'added': 0,
'removed': 0}}.), but the next iteration does process 3 "added" ports.
You can see that the "output received" is logged in the first loop,
49ms after "starting polling" is logged, which is presumably the
problem. On all the non-failing nodes, the output is received before
"starting polling".
I believe the proper thing to do is to set "sync" to True (in
rpc_loop()) if an ovs restart is detected, forcing process_port_info()
to not use async events and scan the ports itself using scan_ports().
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1758868/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~
[Yahoo-eng-team] [Bug 1804420] Re: placement unit test placement.tests.unit.cmd.test_manage.TestCommandParsers.test_commands_associated fails on CentOS 7
** No longer affects: oslo.config
--
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 1803486] Re: Floating and negative values accepted in volume size field.
Ivan, what is the reason of "Won't Fix"? I set the status to Confirmed. ** Changed in: horizon Status: Won't Fix => Confirmed -- 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): Confirmed 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 1804634] [NEW] [RFE] l3_agent should separate router_info creation logic
Public bug reported: Currently, l3-agent has tightly coupled with router_info creation logic, so there is no way to make a big change of default router's behaviors. Even there are already many diverse routers (dvr, dvrha, dvr_snat...), every routers depend detailed implementation rather than structured interfaces. So it makes hard to add new feature. I found a majority of networking-* with l3 implementation just override core L3NatAgent and add a little tweaking functions to change default l3-agent behavior. IMHO, if there is clear interface in L3 agent for specific router, they just add their router business logic rather than did not override core agent class. I noticed they did not change RPC mechanism a lot in agent side, and want to just make few tweak like us. What I suggest is make abstract class for router with minimal functions (initialize(), process()..), and add create router logic with dynamically configured router_info class. It decouples the creation and RPC controller so that plugin developer can easily change the default router behavior. To provide more specific use case, what we have done was to add linux VRF feature instead of namespace and East-West traffic is enabled by default so that there is no need to add GW / internal port at all. We do not need majority of functions except floating IP, but every kind of API / RPC is useful at the same time from server side. ** Affects: neutron Importance: Undecided Status: New ** Tags: rfe ** Tags added: rfe -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1804634 Title: [RFE] l3_agent should separate router_info creation logic Status in neutron: New Bug description: Currently, l3-agent has tightly coupled with router_info creation logic, so there is no way to make a big change of default router's behaviors. Even there are already many diverse routers (dvr, dvrha, dvr_snat...), every routers depend detailed implementation rather than structured interfaces. So it makes hard to add new feature. I found a majority of networking-* with l3 implementation just override core L3NatAgent and add a little tweaking functions to change default l3-agent behavior. IMHO, if there is clear interface in L3 agent for specific router, they just add their router business logic rather than did not override core agent class. I noticed they did not change RPC mechanism a lot in agent side, and want to just make few tweak like us. What I suggest is make abstract class for router with minimal functions (initialize(), process()..), and add create router logic with dynamically configured router_info class. It decouples the creation and RPC controller so that plugin developer can easily change the default router behavior. To provide more specific use case, what we have done was to add linux VRF feature instead of namespace and East-West traffic is enabled by default so that there is no need to add GW / internal port at all. We do not need majority of functions except floating IP, but every kind of API / RPC is useful at the same time from server side. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1804634/+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 1804653] [NEW] Provide user data to instances in nova should explicitly tell in the docs about the size limit
Public bug reported: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: So, you think cloud init is cool and you start building on it. The more you learn about cloud init, the more you like it. Until your cloud init becomes too big to the dislikes of who every design the database schema or API. Then your calls to nova API will fail with: novaclient.exceptions.BadRequest: User data too large. User data must be no larger than 65535 bytes once base64 encoded. Your data is 66080 bytes (HTTP 400) (Request-ID: req-13e1d006-2c77-4ab4-903f-92f279d64cfc) At this point you invested quite sometime ... and now you have to figure a new strategy. The documentation could at least warn in advance ... https://github.com/openstack/nova/blob/c6218428e9b29a2c52808ec7d27b4b21aadc0299/doc/source/user /user-data.rst Somewhere in there should be a notice about the max userdata size. --- Release: 18.0.4.dev11 on 2018-11-21 20:54 SHA: e90e89219410a771f9b6b0c4200edb0480360afe Source: https://git.openstack.org/cgit/openstack/nova/tree/doc/source/user/user-data.rst URL: https://docs.openstack.org/nova/rocky/user/user-data.html ** 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/1804653 Title: Provide user data to instances in nova should explicitly tell in the docs about the size limit Status in OpenStack Compute (nova): New Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: So, you think cloud init is cool and you start building on it. The more you learn about cloud init, the more you like it. Until your cloud init becomes too big to the dislikes of who every design the database schema or API. Then your calls to nova API will fail with: novaclient.exceptions.BadRequest: User data too large. User data must be no larger than 65535 bytes once base64 encoded. Your data is 66080 bytes (HTTP 400) (Request-ID: req-13e1d006-2c77-4ab4-903f- 92f279d64cfc) At this point you invested quite sometime ... and now you have to figure a new strategy. The documentation could at least warn in advance ... https://github.com/openstack/nova/blob/c6218428e9b29a2c52808ec7d27b4b21aadc0299/doc/source/user /user-data.rst Somewhere in there should be a notice about the max userdata size. --- Release: 18.0.4.dev11 on 2018-11-21 20:54 SHA: e90e89219410a771f9b6b0c4200edb0480360afe Source: https://git.openstack.org/cgit/openstack/nova/tree/doc/source/user/user-data.rst URL: https://docs.openstack.org/nova/rocky/user/user-data.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1804653/+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 1804652] [NEW] nova.db.sqlalchemy.migration.db_version is racy
Public bug reported: db_version() attempts to initialise versioning if the db is not versioned. However, it doesn't consider concurrency, so we can get errors if multiple watchers try to get the db version before the db is initialised. We are seeing this in practise during tripleo deployments in a script which waits on multiple controller nodes for db sync to complete. ** 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/1804652 Title: nova.db.sqlalchemy.migration.db_version is racy Status in OpenStack Compute (nova): New Bug description: db_version() attempts to initialise versioning if the db is not versioned. However, it doesn't consider concurrency, so we can get errors if multiple watchers try to get the db version before the db is initialised. We are seeing this in practise during tripleo deployments in a script which waits on multiple controller nodes for db sync to complete. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1804652/+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 1797309] Re: Every item in navigation bar of workflow form should be hide if the parameter ready is false
Marking Ubuntu bug task as invalid - its fixed upstream in the Horizon project and will be picked up with the next snapshot upload to Ubuntu development. ** Changed in: horizon (Ubuntu) Status: New => Triaged ** Changed in: horizon (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1797309 Title: Every item in navigation bar of workflow form should be hide if the parameter ready is false Status in OpenStack Dashboard (Horizon): Fix Released Status in horizon package in Ubuntu: Invalid Bug description: In workflow wizard, every item of navigation used parameter 'ng-show="viewModel.ready"' to determine whether it should be display. I think it should use the parameter 'ready' of every item, like this: 'ng-show="step.ready"'. I think it make sense. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1797309/+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] Re: placement unit test placement.tests.unit.cmd.test_manage.TestCommandParsers.test_commands_associated fails on CentOS 7
I've attached a simple script to reproduce this behaviour outside of
placement.
I'm struggling to find where but AFAICT the oslo.config code parsing the
command line args is failing and defaulting to the default help func for
the top level command parser.
# cat /etc/redhat-release
Fedora release 28 (Twenty Eight)
# python --version
Python 2.7.15
# pip freeze | grep oslo.config
oslo.config==6.7.0
# python reproduce.py cmd bar
>
# cat /etc/redhat-release
CentOS Linux release 7.5.1804 (Core)
# python --version
Python 2.7.5
# pip freeze | grep oslo.config
oslo.config==6.7.0
# python reproduce.py cmd bar
,
conflict_handler='error', add_help=True)>
** Attachment added: "reproduce.py"
https://bugs.launchpad.net/nova/+bug/1804420/+attachment/5215276/+files/reproduce.py
** Also affects: oslo.config
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
Status in oslo.config:
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 1804633] [NEW] Linux, Ubuntu, 18.04, CI, NB13, External speaker output noise when plug/unplug on IE dock.(FR:100%)
Public bug reported: Description: Plug/unplug a audio jack external speaker on IE Dock, and the external speakers output noise sound. Expected Behavior: External speakers not output noise when plug/unplug on IE 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: IE dock(REV-A05 Dock-110 FW:1.0.4) 6. Speaker: Dell SPEAKER-20 (REV-A00) Dell 2.0speaker (AE215) AE215 Notes: 1. VP on Salomon dock 2. VP on BME Dock 3. Line-out port can't detect external device Cross platform: 1. N/A Test Case: [CPV-TC-4688][WIS-TC-4153] Linux_NB_IE-Wired-Dock-The Docked SUT ''Power Management(S3)'' Test Step 14 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, dock theIE dock to SUT. 3. Plug/unplug external speaketr to audio port of IE dock. 4. Find the external speaker output noise--->Problem(refer to video) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "Speaker noise.mp4" https://bugs.launchpad.net/bugs/1804633/+attachment/5215266/+files/Speaker%20noise.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/1804633 Title: Linux, Ubuntu, 18.04, CI, NB13, External speaker output noise when plug/unplug on IE dock.(FR:100%) Status in Glance: New Bug description: Description: Plug/unplug a audio jack external speaker on IE Dock, and the external speakers output noise sound. Expected Behavior: External speakers not output noise when plug/unplug on IE 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: IE dock(REV-A05 Dock-110 FW:1.0.4) 6. Speaker: Dell SPEAKER-20 (REV-A00) Dell 2.0speaker (AE215) AE215 Notes: 1. VP on Salomon dock 2. VP on BME Dock 3. Line-out port can't detect external device Cross platform: 1. N/A Test Case: [CPV-TC-4688][WIS-TC-4153] Linux_NB_IE-Wired-Dock-The Docked SUT ''Power Management(S3)'' Test Step 14 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, dock theIE dock to SUT. 3. Plug/unplug external speaketr to audio port of IE 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/1804633/+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 1804629] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Wake up from suspend, output video sound before login.(FR:100%)
Public bug reported: Description: When SUT connect monitor by HDMI cable or by DOCK station, While the movie is playing, put the SUT into Suspend mode and wait for 30s, then Let SUT wake up from Suspend mode, there is a short sounds output before login. Expected Behavior: The SUT wakes up from the Suspend/Suspend-To-Idle without any problems or issues. 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. Monitor: Dell U2713Hb(Monitor-01) Notes: 1. VP on Salomon dock 2. VP on IE Dock 3. VP on BME Dock 4. VP on connect monitor to SUT with HDMI cable Cross platform: 1. N/A Test Case: CSV-TC-5199 [WIS-TC-4411] Linux_NB_Salomon-Wired-Dock-The I/O Ports Functionality Test (2/2), step-13. issue steps: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, connect a monitor by HDMI Cable or by SLM DOCK/IE DOCK/BME DOCK. 3.While the movie is playing, put SUT into Suspend mode, wait at least 30s. 4. Let SUT wake up from Suspend mode,there is a short sounds output before login.--->problem(refer to attached video:suspend wake up.MP4) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "Suspend wake up.mp4" https://bugs.launchpad.net/bugs/1804629/+attachment/5215264/+files/Suspend%20wake%20up.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/1804629 Title: Linux, Ubuntu, 18.04, CI, NB13, Wake up from suspend, output video sound before login.(FR:100%) Status in Glance: New Bug description: Description: When SUT connect monitor by HDMI cable or by DOCK station, While the movie is playing, put the SUT into Suspend mode and wait for 30s, then Let SUT wake up from Suspend mode, there is a short sounds output before login. Expected Behavior: The SUT wakes up from the Suspend/Suspend-To-Idle without any problems or issues. 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. Monitor: Dell U2713Hb(Monitor-01) Notes: 1. VP on Salomon dock 2. VP on IE Dock 3. VP on BME Dock 4. VP on connect monitor to SUT with HDMI cable Cross platform: 1. N/A Test Case: CSV-TC-5199 [WIS-TC-4411] Linux_NB_Salomon-Wired-Dock-The I/O Ports Functionality Test (2/2), step-13. issue steps: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, connect a monitor by HDMI Cable or by SLM DOCK/IE DOCK/BME DOCK. 3.While the movie is playing, put SUT into Suspend mode, wait at least 30s. 4. Let SUT wake up from Suspend mode,there is a short sounds output before login.--->problem(refer to attached video:suspend wake up.MP4) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804629/+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 1804631] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Line-out port of IE Dock can't detect external speaker.(FR:100%)
Public bug reported: Description: Plug an audio jack external speaker to Line-out port of IE Dock, and the external speakers can't be detected. Expected Behavior: Plug External speaker to Line-out port of IE Dock can be detected . Severity: Sev-2 P2 C2 L4 Test environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. Driver list: V27 4. OS: CI Ubuntu 18.04 5. Dock info: IE dock(REV-A05 Dock-110 FW:1.0.4) 6. Speaker: Dell SPEAKER-20 (REV-A00) Dell 2.0speaker (AE215) AE215 Notes: 1. VP on Salomon dock 2. VP on BME Dock 3. VNP in Windows 10 Cross platform: 1. N/A Test Case: [CPV-TC-4688][WIS-TC-4153] Linux_NB_IE-Wired-Dock-The Docked SUT ''Power Management(S3)'' Test Step 14 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, dock the BME dock to SUT. 3. Plug external speaketr to Line-out port of IE dock. 4. Find the external speaker can't be detected. ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-Ubuntu.123-20181121205012.tar.xz" https://bugs.launchpad.net/bugs/1804631/+attachment/5215265/+files/sosreport-Ubuntu.123-20181121205012.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/1804631 Title: Linux, Ubuntu, 18.04, CI, NB13, Line-out port of IE Dock can't detect external speaker.(FR:100%) Status in Glance: New Bug description: Description: Plug an audio jack external speaker to Line-out port of IE Dock, and the external speakers can't be detected. Expected Behavior: Plug External speaker to Line-out port of IE Dock can be detected . Severity: Sev-2 P2 C2 L4 Test environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. Driver list: V27 4. OS: CI Ubuntu 18.04 5. Dock info: IE dock(REV-A05 Dock-110 FW:1.0.4) 6. Speaker: Dell SPEAKER-20 (REV-A00) Dell 2.0speaker (AE215) AE215 Notes: 1. VP on Salomon dock 2. VP on BME Dock 3. VNP in Windows 10 Cross platform: 1. N/A Test Case: [CPV-TC-4688][WIS-TC-4153] Linux_NB_IE-Wired-Dock-The Docked SUT ''Power Management(S3)'' Test Step 14 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, dock the BME dock to SUT. 3. Plug external speaketr to Line-out port of IE dock. 4. Find the external speaker can't be detected. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804631/+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 1804613] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Camera captured picture is not mirrored.(FR:100%)
You have been subscribed to a public bug: Description: Open '' Cheese", found the image is not mirrored. Expected Behavior: The captured picture is mirrored. Severity: Sev-2 P3 C3 L3 Test Environment: 1. Project: Northbay 13 SKU6 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 Note: 1. VP on Northbay all skus Cross Platform: N/A Test case: [CSV-TC-5004]][WIS-TC-4391] Linux_LED - LED and Power Button Basic Functionality Test, step18 Steps to Reproduce: 1. Start "Cheese" from "Show Application"->"Cheese" 2. Found the image is not mirrored.-->Problem. ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 -- Linux, Ubuntu, 18.04, CI, NB13, Camera captured picture is not mirrored.(FR:100%) https://bugs.launchpad.net/bugs/1804613 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. -- 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 1804605] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Erorr is logged after execute shutdown(FR:100%)
You have been subscribed to a public bug: Description: clear log/messages firstly, check /var/log/messages after execute shutdown,find some errors. Expected Behavior: No errors logged after execute shutdown. Severity: Sev-3 P3 C3 L4 Test Environment: 1. Project: Northbay 13 SKU6 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. VP on Exercise S5 using the Desktop 5. VP on Exercise S5 using a terminal Note: 1. VP on DC 2. VP on AC 3. VP on Northbay all skus Cross Platform: N/A Test case: [CSV-TC-4587[WIS-TC-4175] Linux_ACPI - S5 Shutdown and Wake, step2 Steps to Reproduce: 1. Clear log/messages 2. Select "battery icon": -> "Power" from the task bar, click "Power Off" 3. Press power button, then check /var/log/messages for any errors, use command "tail -100 /var/log/messages" to check the log file,find errors-->Problem(plz refer to logs) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 -- Linux, Ubuntu, 18.04, CI, NB13, Erorr is logged after execute shutdown(FR:100%) https://bugs.launchpad.net/bugs/1804605 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. -- 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 1804609] [NEW] Linux, Ubuntu, 18.04, CI, NB13, TP zoom in/out function is not sensitive.(FR:40%)
You have been subscribed to a public bug: Description: Use two fingers to zoom in/out a picture, found sometimes the picture can't zoom in/out. Expected Behavior: The picture can be zoom in/out by two finger all the time. Severity: Sev-2 P3 C3 L3 Test Environment: 1. Project: Northbay 13 SKU6 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. Failure Rate: NB 13 SKU6_8 4/10, (failed @ 3rd, 7th, 9th,10th) NB 13 SKU6_5 5/10, (failed @ 4th, 5th, 6th, 7th, 9th,10th) NB 13 SKU11_3 4/10, (failed @ 3rd, 6th, 7th, 8th) 5. test with.jpg Note: 1. VP on NB all skus Cross Platform: N/A Test case: [CSV-TC-4996][WIS-TC-4401] Linux_NB_Touchpad&Trackpoint - Basic Functionality Test, step10 Steps to Reproduce: 1. Use two fingers to zoom in/out a picture, found sometimes the gesture lost function-->Problem(plz refer to video) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 -- Linux, Ubuntu, 18.04, CI, NB13, TP zoom in/out function is not sensitive.(FR:40%) https://bugs.launchpad.net/bugs/1804609 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. -- 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 1804628] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Sound/picture are not smooth after unplug/plug Dock when playing video.
Public bug reported: Description: When SUT connect monitor by Salomon Dock, when a movie file is playing, unplug/plug Salomon Dock, both Sound/picture are not smooth about 5~10s. (FR:100%) Expected Behavior: When SUT connect monitor by Salomon Dock, when a movie file is playing, unplug/plug Salomon Dock, both Sound/picture are smooth 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. Monitor: Monitor-01, U2713Hb Notes: 1. VP on Salomon dock 2. VP on IE Dock 3. VP on BME Dock 4. VNP on connect monitor by HDMI cable directly. Cross platform: 1. N/A Test Case: CSV-TC-5199 [WIS-TC-4411] Linux_NB_Salomon-Wired-Dock-The I/O Ports Functionality Test (2/2), step-16. issue steps: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, connect a monitor by HDMI Cable to Salomon dock; 3. When a movie file is playing, unplug/plug Salomon dock, find both Sound/picture are not smooth about 5~10s--->problem(refer to attached video:hang up.MP4) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "hang up.mp4" https://bugs.launchpad.net/bugs/1804628/+attachment/5215262/+files/hang%20up.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/1804628 Title: Linux,Ubuntu,18.04,CI,NB13, Sound/picture are not smooth after unplug/plug Dock when playing video. Status in Glance: New Bug description: Description: When SUT connect monitor by Salomon Dock, when a movie file is playing, unplug/plug Salomon Dock, both Sound/picture are not smooth about 5~10s. (FR:100%) Expected Behavior: When SUT connect monitor by Salomon Dock, when a movie file is playing, unplug/plug Salomon Dock, both Sound/picture are smooth 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. Monitor: Monitor-01, U2713Hb Notes: 1. VP on Salomon dock 2. VP on IE Dock 3. VP on BME Dock 4. VNP on connect monitor by HDMI cable directly. Cross platform: 1. N/A Test Case: CSV-TC-5199 [WIS-TC-4411] Linux_NB_Salomon-Wired-Dock-The I/O Ports Functionality Test (2/2), step-16. issue steps: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, connect a monitor by HDMI Cable to Salomon dock; 3. When a movie file is playing, unplug/plug Salomon dock, find both Sound/picture are not smooth about 5~10s--->problem(refer to attached video:hang up.MP4) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804628/+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 1804609] Re: Linux, Ubuntu, 18.04, CI, NB13, TP zoom in/out function is not sensitive.(FR:40%)
** Project changed: kicad => glance -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804609 Title: Linux, Ubuntu, 18.04, CI, NB13, TP zoom in/out function is not sensitive.(FR:40%) Status in Glance: New Bug description: Description: Use two fingers to zoom in/out a picture, found sometimes the picture can't zoom in/out. Expected Behavior: The picture can be zoom in/out by two finger all the time. Severity: Sev-2 P3 C3 L3 Test Environment: 1. Project: Northbay 13 SKU6 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. Failure Rate: NB 13 SKU6_8 4/10, (failed @ 3rd, 7th, 9th,10th) NB 13 SKU6_5 5/10, (failed @ 4th, 5th, 6th, 7th, 9th,10th) NB 13 SKU11_3 4/10, (failed @ 3rd, 6th, 7th, 8th) 5. test with.jpg Note: 1. VP on NB all skus Cross Platform: N/A Test case: [CSV-TC-4996][WIS-TC-4401] Linux_NB_Touchpad&Trackpoint - Basic Functionality Test, step10 Steps to Reproduce: 1. Use two fingers to zoom in/out a picture, found sometimes the gesture lost function-->Problem(plz refer to video) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804609/+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 1804613] Re: Linux, Ubuntu, 18.04, CI, NB13, Camera captured picture is not mirrored.(FR:100%)
** Project changed: kicad => glance -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804613 Title: Linux, Ubuntu, 18.04, CI, NB13, Camera captured picture is not mirrored.(FR:100%) Status in Glance: New Bug description: Description: Open '' Cheese", found the image is not mirrored. Expected Behavior: The captured picture is mirrored. Severity: Sev-2 P3 C3 L3 Test Environment: 1. Project: Northbay 13 SKU6 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 Note: 1. VP on Northbay all skus Cross Platform: N/A Test case: [CSV-TC-5004]][WIS-TC-4391] Linux_LED - LED and Power Button Basic Functionality Test, step18 Steps to Reproduce: 1. Start "Cheese" from "Show Application"->"Cheese" 2. Found the image is not mirrored.-->Problem. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804613/+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 1804605] Re: Linux, Ubuntu, 18.04, CI, NB13, Erorr is logged after execute shutdown(FR:100%)
** Project changed: kicad => glance -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1804605 Title: Linux, Ubuntu, 18.04, CI, NB13, Erorr is logged after execute shutdown(FR:100%) Status in Glance: New Bug description: Description: clear log/messages firstly, check /var/log/messages after execute shutdown,find some errors. Expected Behavior: No errors logged after execute shutdown. Severity: Sev-3 P3 C3 L4 Test Environment: 1. Project: Northbay 13 SKU6 2. BIOS: 0.4.0 3. OS:CI Ubuntu 18.04 4. VP on Exercise S5 using the Desktop 5. VP on Exercise S5 using a terminal Note: 1. VP on DC 2. VP on AC 3. VP on Northbay all skus Cross Platform: N/A Test case: [CSV-TC-4587[WIS-TC-4175] Linux_ACPI - S5 Shutdown and Wake, step2 Steps to Reproduce: 1. Clear log/messages 2. Select "battery icon": -> "Power" from the task bar, click "Power Off" 3. Press power button, then check /var/log/messages for any errors, use command "tail -100 /var/log/messages" to check the log file,find errors-->Problem(plz refer to logs) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804605/+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 1804614] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Resolution can't reach HD when set display mode to Mirror.(FR:100%)
Public bug reported: Description: Connect an HDMI monitor to SUT by type-c to HDMI dongle, Press Win+P Key Set display mode to Mirror, find resolution is 1280*720, lack 1366*768. Expected Behavior: Resolution value have 1366*768 and can set to it when set display mode to Mirror. Severity: Sev-2 P3 C3 L2 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS: CI Ubuntu 18.04 4. Monitor: S2718D Dell(MONITOR-86)(REV-A05) 5. Dongle: Type-C to HDMI Dell(Dongle-295)(REV-A02) Note: 1. VP on Connect HDMI Monitor directly 2. VP on HD(1366*768) config 3. VNP on FHD(1920*1080) config 4. VNP on Join Displays/External Only display mode Cross Platform: N/A Test case: [CSV-TC-4600][WIS-TC-4186] Linux_USB - USB Type-C With HDMI Video Test step:3 Steps to Reproduce 1. Flash Latest BIOS, Install Ubuntu OS 18.04. 2. Boot to OS, Connect a HDMI Monitor by type-c to HDMI Dongle. 3. Press "Win+P" key to set display mode to Mirror mode. 4. Find resolution is 1280*720, can't set to 1366*768.>problem(refer to pic) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "IMG_mirror.jpg" https://bugs.launchpad.net/bugs/1804614/+attachment/5215235/+files/IMG_mirror.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/1804614 Title: Linux, Ubuntu, 18.04, CI, NB13, Resolution can't reach HD when set display mode to Mirror.(FR:100%) Status in Glance: New Bug description: Description: Connect an HDMI monitor to SUT by type-c to HDMI dongle, Press Win+P Key Set display mode to Mirror, find resolution is 1280*720, lack 1366*768. Expected Behavior: Resolution value have 1366*768 and can set to it when set display mode to Mirror. Severity: Sev-2 P3 C3 L2 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS: CI Ubuntu 18.04 4. Monitor: S2718D Dell(MONITOR-86)(REV-A05) 5. Dongle: Type-C to HDMI Dell(Dongle-295)(REV-A02) Note: 1. VP on Connect HDMI Monitor directly 2. VP on HD(1366*768) config 3. VNP on FHD(1920*1080) config 4. VNP on Join Displays/External Only display mode Cross Platform: N/A Test case: [CSV-TC-4600][WIS-TC-4186] Linux_USB - USB Type-C With HDMI Video Test step:3 Steps to Reproduce 1. Flash Latest BIOS, Install Ubuntu OS 18.04. 2. Boot to OS, Connect a HDMI Monitor by type-c to HDMI Dongle. 3. Press "Win+P" key to set display mode to Mirror mode. 4. Find resolution is 1280*720, can't set to 1366*768.>problem(refer to pic) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804614/+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 1804602] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Line-out port of BME Dock can't detect external speaker.(FR:100%)
Public bug reported: Description: Plug an audio jack external speaker to Line-out port of BME Dock, and the external speakers can't be detected. Expected Behavior: Plug External speaker to Line-out port of BME Dock can be detected . Severity: Sev-2 P2 C2 L4 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. VNP in Windows 10 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 external speaketr to Line-out port of BME dock. 4. Find the external speaker can't be detected. ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-Ubuntu.123-20181121205012.tar.xz" https://bugs.launchpad.net/bugs/1804602/+attachment/5215217/+files/sosreport-Ubuntu.123-20181121205012.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/1804602 Title: Linux, Ubuntu, 18.04, CI, NB13, Line-out port of BME Dock can't detect external speaker.(FR:100%) Status in Glance: New Bug description: Description: Plug an audio jack external speaker to Line-out port of BME Dock, and the external speakers can't be detected. Expected Behavior: Plug External speaker to Line-out port of BME Dock can be detected . Severity: Sev-2 P2 C2 L4 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. VNP in Windows 10 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 external speaketr to Line-out port of BME dock. 4. Find the external speaker can't be detected. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804602/+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
