[Yahoo-eng-team] [Bug 1804780] [NEW] Linux, Ubuntu, 18.04, NB13, The file copyed to desktop will overlap the external disk icon(FR:100%)
Public bug reported: Description: Plug in a USB devcie to SUT, then copy a file from external USB device to desktop, found the coppyed file icon will overlap the external USB device icon on desktop. Expected Behavior: The file should not overlap the external USB device icon on desktop. Severity: Sev-2 P3 C3 L3 Test Environment: 1. Project: Northbay 13 sku6 2. BIOS: 0.4.1 3. OS:CI Ubuntu 18.04 Note: 1. VP on all Nortbay skus 3. VP on Copy/Cut 3. VP on Move to.. 4. VP on Copy to.. Cross Platform: N/A Test case: [CSV-TC-4616][WIS-TC-4190] Linux_USB - USB Type-C With DVI Video Test( found by chance) Steps to Reproduce: 1. Plug in a USB device to SUT. 2. Copy a file from USB external device to desktop. 3. Found the coppyed file icon will overlap the external USB device icon on desktop-->Problem(plz refer to video) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "Overlap video.mp4" https://bugs.launchpad.net/bugs/1804780/+attachment/5215550/+files/Overlap%20video.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/1804780 Title: Linux, Ubuntu,18.04, NB13, The file copyed to desktop will overlap the external disk icon(FR:100%) Status in Glance: New Bug description: Description: Plug in a USB devcie to SUT, then copy a file from external USB device to desktop, found the coppyed file icon will overlap the external USB device icon on desktop. Expected Behavior: The file should not overlap the external USB device icon on desktop. Severity: Sev-2 P3 C3 L3 Test Environment: 1. Project: Northbay 13 sku6 2. BIOS: 0.4.1 3. OS:CI Ubuntu 18.04 Note: 1. VP on all Nortbay skus 3. VP on Copy/Cut 3. VP on Move to.. 4. VP on Copy to.. Cross Platform: N/A Test case: [CSV-TC-4616][WIS-TC-4190] Linux_USB - USB Type-C With DVI Video Test( found by chance) Steps to Reproduce: 1. Plug in a USB device to SUT. 2. Copy a file from USB external device to desktop. 3. Found the coppyed file icon will overlap the external USB device icon on desktop-->Problem(plz refer to video) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804780/+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 1804783] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Show not found after run 'sudo uefi-fw-tools.fwupdmgr get-devices'.
Public bug reported: Description: Show 'sudo: uefi-fw-tools.fwupdmgr: command not found' after run 'sudo uefi-fw-tools.fwupdmgr get-devices' in Terminal. (FR:100%) Expected Behavior: Commands execute without error. 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-5008][WIS-TC-4392] Linux_BIOS - Update BIOS via local UEFI Firmware UpdateCapsule Step3 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, open Terminal and run 'sudo uefi-fw-tools.fwupdmgr get-devices', found show 'sudo: uefi-fw-tools.fwupdmgr: command not found'.-->Problem(refer to pic) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-tool.WIS-TC-4392-20181122070605.tar.xz" https://bugs.launchpad.net/bugs/1804783/+attachment/521/+files/sosreport-tool.WIS-TC-4392-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/1804783 Title: Linux, Ubuntu, 18.04, CI, NB13, Show not found after run 'sudo uefi- fw-tools.fwupdmgr get-devices'. Status in Glance: New Bug description: Description: Show 'sudo: uefi-fw-tools.fwupdmgr: command not found' after run 'sudo uefi-fw-tools.fwupdmgr get-devices' in Terminal. (FR:100%) Expected Behavior: Commands execute without error. 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-5008][WIS-TC-4392] Linux_BIOS - Update BIOS via local UEFI Firmware UpdateCapsule Step3 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, open Terminal and run 'sudo uefi-fw-tools.fwupdmgr get-devices', found show 'sudo: uefi-fw-tools.fwupdmgr: command not found'.-->Problem(refer to pic) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804783/+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 1804781] [NEW] Linux, Ubuntu, 18.04, CI, NB13, Mobile Broadband Card can't be recognized by SUT.(FR:100%)
Public bug reported: Description: Boot to OS, in Network option, not have Mobile Broadband Card with WWAN card information, SUT can't detect Mobile Broadband Card with WWAN card, then run "lsusb" in Terminal, no WWAN information. Expected Behavior: SUT can detect Mobile Broadband Card. Severity: Sev-2 P3 C2 L2 Test environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 4. OS: CI Ubuntu 18.04 5. WWAN: MDM,WRLES,DW5820E,X10,4G,HF (284DC) Notes: 1. VP on Northbay WWAN skus Cross Platform: NA Test case: [CSV-TC-5011][WIS-TC-4403] Linux_WWAN - Basic Functionality Test Step3 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS; 2. Boot to OS with WWAN card connected, open Terminal run "lsusb", found can't detect mobile broadband card;-->Problem(refer to check WWAN.png) 3. Open Show Applications->Settings->Network, found no mobile options.-->Problem(refer to WWAN.png) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-WWAN.WIS-TC-4403-20181122031931.tar.xz" https://bugs.launchpad.net/bugs/1804781/+attachment/5215552/+files/sosreport-WWAN.WIS-TC-4403-20181122031931.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/1804781 Title: Linux, Ubuntu, 18.04, CI, NB13, Mobile Broadband Card can't be recognized by SUT.(FR:100%) Status in Glance: New Bug description: Description: Boot to OS, in Network option, not have Mobile Broadband Card with WWAN card information, SUT can't detect Mobile Broadband Card with WWAN card, then run "lsusb" in Terminal, no WWAN information. Expected Behavior: SUT can detect Mobile Broadband Card. Severity: Sev-2 P3 C2 L2 Test environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 4. OS: CI Ubuntu 18.04 5. WWAN: MDM,WRLES,DW5820E,X10,4G,HF (284DC) Notes: 1. VP on Northbay WWAN skus Cross Platform: NA Test case: [CSV-TC-5011][WIS-TC-4403] Linux_WWAN - Basic Functionality Test Step3 Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS; 2. Boot to OS with WWAN card connected, open Terminal run "lsusb", found can't detect mobile broadband card;-->Problem(refer to check WWAN.png) 3. Open Show Applications->Settings->Network, found no mobile options.-->Problem(refer to WWAN.png) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804781/+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 1804788] [NEW] Linux, Ubuntu, 18.04, CI, NB13, No copy progress when copy file from external storage to SUT(FR:100%)
Public bug reported: Description: There are no copy progress or any copy complete information shows in OS when copy a file from external USB Storage to SUT. Expected Behavior: No problems or issues performing the copy process of file from the external USB storage to SUT. 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 Notes: 1. VNP on copy file from SUT to External USB storage. Cross platform: 1. 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-10. Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, plug in an external USB storage to SUT. 3. Copy file from external USB storage to SUT, there no any complete information or copy progress.--->(problem). ** 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/1804788/+attachment/5215569/+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/1804788 Title: Linux, Ubuntu, 18.04, CI, NB13,No copy progress when copy file from external storage to SUT(FR:100%) Status in Glance: New Bug description: Description: There are no copy progress or any copy complete information shows in OS when copy a file from external USB Storage to SUT. Expected Behavior: No problems or issues performing the copy process of file from the external USB storage to SUT. 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 Notes: 1. VNP on copy file from SUT to External USB storage. Cross platform: 1. 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-10. Steps to Reproduce: 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS, plug in an external USB storage to SUT. 3. Copy file from external USB storage to SUT, there no any complete information or copy progress.--->(problem). To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804788/+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 1804789] [NEW] Linux, Ubuntu, 18.04, NB13, SUT Lid close can't enter suspend when connect external monitor on Dock.(FR:100%)
Public bug reported: Description: Connect a Single-c Salomin Dock to SUT, connect three monitors to Salomon Dock. Open Dconf Editer, set Lid close to suspend, close Lid of SUT. Find display change to external Monitor after Lid closed. Expected Behavior: SUT Lid close can enter suspend when connect external monitor on Dock. 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. P2214H Dell Moniotr-15 6. S2718HN Dell Moniotr-77 7. AW2518H Alienware Moniotr-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 Cross Platform: N/A Test case: [CSV-TC-5207][WIS-TC-4415] Linux_NB_Salomon-Wired-Dock-The Docked SUT "Power Management (S3)" Test step:36 Steps to Reproduce: 1. Flash Latest BIOS, install Ubuntu OS 18.04. 2. Boot to BIOS setup, set Power Management sleep mode to force S3; 3. Boot to OS, Connect a Salomon Dock to SUT; 4. Connect a HDMI monitor, two DP monitors to Salomon Dock; 5. Install Dconf Editer in Ubuntu Software; 6. Open Dconf Editer, set Lid close to suspend as default; 7. Close Lid of SUT, find display change to external monitors, not Suspend.>problem(refer to Video) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "VID_Lid close not suspend.mp4" https://bugs.launchpad.net/bugs/1804789/+attachment/5215571/+files/VID_Lid%20close%20not%20suspend.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/1804789 Title: Linux, Ubuntu,18.04, NB13, SUT Lid close can't enter suspend when connect external monitor on Dock.(FR:100%) Status in Glance: New Bug description: Description: Connect a Single-c Salomin Dock to SUT, connect three monitors to Salomon Dock. Open Dconf Editer, set Lid close to suspend, close Lid of SUT. Find display change to external Monitor after Lid closed. Expected Behavior: SUT Lid close can enter suspend when connect external monitor on Dock. 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. P2214H Dell Moniotr-15 6. S2718HN Dell Moniotr-77 7. AW2518H Alienware Moniotr-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 Cross Platform: N/A Test case: [CSV-TC-5207][WIS-TC-4415] Linux_NB_Salomon-Wired-Dock-The Docked SUT "Power Management (S3)" Test step:36 Steps to Reproduce: 1. Flash Latest BIOS, install Ubuntu OS 18.04. 2. Boot to BIOS setup, set Power Management sleep mode to force S3; 3. Boot to OS, Connect a Salomon Dock to SUT; 4. Connect a HDMI monitor, two DP monitors to Salomon Dock; 5. Install Dconf Editer in Ubuntu Software; 6. Open Dconf Editer, set Lid close to suspend as default; 7. Close Lid of SUT, find display change to external monitors, not Suspend.>problem(refer to Video) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804789/+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 1804791] [NEW] Linux, Ubuntu, 18.04, NB13, USB Type-A/C devices that connected to Salomon Dock lost on BIOS 0.4.1.
Public bug reported: Description: Flash bin BIOS 0.4.1 fromBIOS 0.4.0. Connect a Single-c Salomin Dock to SUT. Connect USB devices and monitor to Salomon Dock. 1. Boot to SUT, find all USB Type-A and Type-c port, and TBT port devices lost.(FR:2/10times) 2. Close Lid of SUT, put SUT to Suspend mode by time out or press power button. Press power button on Salomon Dock to wake SUT, find all USB Type-A and Type-c port, and TBT port devices lost.(FR:1/30times) 3. Shut down SUT, cold boot SUT, find all USB Type-A and Type-c port, and TBT port devices lost.(FR:1/35times) All external monitors work normally when USB Type-A/C device lost. Expected Behavior: All USB Type-A and Type-c port, and TBT port devices work normally at any time after flash BIOS. 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. Devices: (1). USB2.0 Dell Mouse-70 (REV-A01) MS116 0H9W5N, USB2.0 Dell Keboard-32 (REV-A00) DELL Rusty KB216T; (2). ADATA USB3.0-26 USB3.0 8GB, SanDisk USB-C-06 16GB SDCZ450, USB3.1 / 480G SanDisk SSD-26 ; (3). 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 flash bin BIOS from 0.4.0 to 0.4.1(2/10 times) 3. VP on resume from Suspend(1/30times) 4. VP on Cold boot(1/35times) 5. VP on SUT Lid is open/close Cross Platform: N/A Test case: [CSV-TC-5207][WIS-TC-4415] Linux_NB_Salomon-Wired-Dock-The Docked SUT "Power Management (S3)" Test step:32 Steps to Reproduce: 1. Flash BIOS 0.4.0, Install Ubuntu OS 18.04. 2. Boot to BIOS setup, set Power management sleep mode to Force S3; 3. Boot to OS, connect a Salomon Dock to SUT; 4. Connect a HDMI Monitor two DP monitor to Salomon Dock; 5. Connect USB Keyboard and USB Mouse to Salomon Dock; 6. Connect Type-A 3.0 and Type-c USB 3.1 Memory Key to Salomon Dock; 7. Connect a Type-c 3.1 SSD to Salomon Dock; 8. Connect a Speaker to Salomon Dock; 9. Flash bin BIOS 0.4.1 fromBIOS 0.4.0. 10. Boot to OS, find all USB Type-A and Type-c port, and TBT port devices lost.>problem1 11. Flash bin BIOS 0.4.1 fromBIOS 0.4.0.(refer to Video) 12. Close Lid of SUT, put SUT to Suspend mode by time out or press power button. Press power button on Salomon Dock to wake SUT, find all USB Type-A and Type-c port, and TBT port devices lost.>problem2(refer to Video) 13. Flash bin BIOS 0.4.1 fromBIOS 0.4.0. 14. Boot to OS, shut down SUT, cold boot SUT, find all USB Type-A and Type-c port, and TBT port devices lost.>problem3(refer to Video) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "IMG_usb port device lost.mp4" https://bugs.launchpad.net/bugs/1804791/+attachment/5215573/+files/IMG_usb%20port%20device%20lost.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/1804791 Title: Linux, Ubuntu,18.04, NB13, USB Type-A/C devices that connected to Salomon Dock lost on BIOS 0.4.1. Status in Glance: New Bug description: Description: Flash bin BIOS 0.4.1 fromBIOS 0.4.0. Connect a Single-c Salomin Dock to SUT. Connect USB devices and monitor to Salomon Dock. 1. Boot to SUT, find all USB Type-A and Type-c port, and TBT port devices lost.(FR:2/10times) 2. Close Lid of SUT, put SUT to Suspend mode by time out or press power button. Press power button on Salomon Dock to wake SUT, find all USB Type-A and Type-c port, and TBT port devices lost.(FR:1/30times) 3. Shut down SUT, cold boot SUT, find all USB Type-A and Type-c port, and TBT port devices lost.(FR:1/35times) All external monitors work normally when USB Type-A/C device lost. Expected Behavior: All USB Type-A and Type-c port, and TBT port devices work normally at any time after flash BIOS. 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. Devices: (1). USB2.0 Dell Mouse-70 (REV-A01) MS116 0H9W5N, USB2.0 Dell Keboard-32 (REV-A00) DELL Rusty KB216T; (2). ADATA USB3.0-26 USB3.0 8GB, SanDisk USB-C-06 16GB SDCZ450, USB3.1 / 480G SanDisk SSD-26 ; (3). 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 flash bin BIOS from 0.4.0 to 0.4.1(2/10 times) 3. VP on resume from Suspend(1/30times) 4. VP on Cold boot(1/35times) 5. VP on SUT Lid is open/close Cross Platform: N/A Test case: [CSV-TC-5207][WIS-TC-4415] Linux_NB_Salomon-Wired-Dock-The Docked SUT "Power Management (S3)" Test step:32 Steps to Reprod
[Yahoo-eng-team] [Bug 1804792] [NEW] Linux, Ubuntu, 18.04, NB13, SUT hung at warm boot progress when connect Salomon Dock.(FR:8/10times)
Public bug reported: Description: Connect a Single-c Salomin Dock to SUT, 1.Connect three monitors to Salomon Dock. Close Lid of SUT, warm boot SUT, SUT will hang in warm boot progress. 2. Connect some devices to Salomon Dock, warm boot SUT, SUT will hang in warm boot progress. Expected Behavior: SUT Warm Boot normally with Salomon Dock and device connect on it. Severity: Sev-1 P2 C2 L2 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.Devices: USB2.0 Dell Mouse-70 (REV-A01) MS116 0H9W5N USB2.0 Dell Keboard-32 (REV-A00) DELL Rusty KB216T ADATA USB3.0-26 USB3.0 8GB SanDisk USB-C-06 16GB SDCZ450 USB3.1 / 480G SanDisk SSD-26 6.Monitors: P2214H Dell Monitor-15 S2718HN Dell Monitor-77 AW2518H Alienware Monitor-83 Note: N/A Cross Platform: N/A Test case: [CSV-TC-5209][WIS-TC-4396] Linux_NB_Salomon-Wired-Dock-The "Cold Boot" Stress Test step:27 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. Close lid of SUT set external three displays to Join Display Mode; 5. Warm boot SUT; 6. SUT will hang in warm boot progress.>problem1(refer to Video) 7. Connect USB Keyboard and USB Mouse to SUT; 8. Connect USB-A 3.0 and Type-c USB 3.1 Memory Key to SUT; 9. Connect a Type-c 3.1 SSD to SUT; 10. Close SUT Lid, set external three displays to Join Display Mode; 11. Warm boot SUT; 12. Find SUT hang in cold boot progress.>problem2(refer to Video) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "VID_hung cold boot.mp4" https://bugs.launchpad.net/bugs/1804792/+attachment/5215575/+files/VID_hung%20cold%20boot.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/1804792 Title: Linux, Ubuntu,18.04, NB13, SUT hung at warm boot progress when connect Salomon Dock.(FR:8/10times) Status in Glance: New Bug description: Description: Connect a Single-c Salomin Dock to SUT, 1.Connect three monitors to Salomon Dock. Close Lid of SUT, warm boot SUT, SUT will hang in warm boot progress. 2. Connect some devices to Salomon Dock, warm boot SUT, SUT will hang in warm boot progress. Expected Behavior: SUT Warm Boot normally with Salomon Dock and device connect on it. Severity: Sev-1 P2 C2 L2 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.Devices: USB2.0 Dell Mouse-70 (REV-A01) MS116 0H9W5N USB2.0 Dell Keboard-32 (REV-A00) DELL Rusty KB216T ADATA USB3.0-26 USB3.0 8GB SanDisk USB-C-06 16GB SDCZ450 USB3.1 / 480G SanDisk SSD-26 6.Monitors: P2214H Dell Monitor-15 S2718HN Dell Monitor-77 AW2518H Alienware Monitor-83 Note: N/A Cross Platform: N/A Test case: [CSV-TC-5209][WIS-TC-4396] Linux_NB_Salomon-Wired-Dock-The "Cold Boot" Stress Test step:27 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. Close lid of SUT set external three displays to Join Display Mode; 5. Warm boot SUT; 6. SUT will hang in warm boot progress.>problem1(refer to Video) 7. Connect USB Keyboard and USB Mouse to SUT; 8. Connect USB-A 3.0 and Type-c USB 3.1 Memory Key to SUT; 9. Connect a Type-c 3.1 SSD to SUT; 10. Close SUT Lid, set external three displays to Join Display Mode; 11. Warm boot SUT; 12. Find SUT hang in cold boot progress.>problem2(refer to Video) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804792/+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 1804794] [NEW] Linux, Ubuntu, 18.04, NB13, SUT hung at cold boot progress when connect Salomon Dock.(FR:1/10times)
Public bug reported: Description: Connect a Single-c Salomin Dock to SUT, 1.Connect three monitors to Salomon Dock. Close Lid of SUT, shut down SUT. Cold Boot SUT by press Dock power button, SUT will hang in cold boot progress. 2. Connect some devices to Salomon Dock, cold boot SUT, SUT will hang in cold boot progress. Expected Behavior: SUT cold boot normally with Salomon Dock and device connect on it. 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.Devices: USB2.0 Dell Mouse-70 (REV-A01) MS116 0H9W5N USB2.0 Dell Keboard-32 (REV-A00) DELL Rusty KB216T ADATA USB3.0-26 USB3.0 8GB SanDisk USB-C-06 16GB SDCZ450 USB3.1 / 480G SanDisk SSD-26 6.Monitors: P2214H Dell Monitor-15 S2718HN Dell Monitor-77 AW2518H Alienware Monitor-83 Note: 1. VNP on Lid open Cross Platform: N/A Test case: [CSV-TC-5209][WIS-TC-4396] Linux_NB_Salomon-Wired-Dock-The "Cold Boot" Stress Test step:27 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. Close lid of SUT set external three displays to Join Display Mode; 5. Press Power Button on Salomon Dock to Shut Down SUT; 6. Press Power Button on Salomon Dock to Power on SUT; 7. SUT will hang in cold boot progress.>problem1(refer to Video) 8. Connect USB Keyboard and USB Mouse to SUT; 9. Connect USB-A 3.0 and Type-c USB 3.1 Memory Key to SUT; 10. Connect a Type-c 3.1 SSD to SUT; 11. Close SUT Lid, set external three displays to Join Display Mode; 12. Press Power Button on Salomon Dock to Shut Down SUT; 13. Press Power Button on Salomon Dock to Power on SUT; 14. Find SUT hang in cold boot progress.>problem2(refer to Video) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "VID_hung cold boot 1.mp4" https://bugs.launchpad.net/bugs/1804794/+attachment/5215589/+files/VID_hung%20cold%20boot%201.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/1804794 Title: Linux, Ubuntu,18.04, NB13, SUT hung at cold boot progress when connect Salomon Dock.(FR:1/10times) Status in Glance: New Bug description: Description: Connect a Single-c Salomin Dock to SUT, 1.Connect three monitors to Salomon Dock. Close Lid of SUT, shut down SUT. Cold Boot SUT by press Dock power button, SUT will hang in cold boot progress. 2. Connect some devices to Salomon Dock, cold boot SUT, SUT will hang in cold boot progress. Expected Behavior: SUT cold boot normally with Salomon Dock and device connect on it. 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.Devices: USB2.0 Dell Mouse-70 (REV-A01) MS116 0H9W5N USB2.0 Dell Keboard-32 (REV-A00) DELL Rusty KB216T ADATA USB3.0-26 USB3.0 8GB SanDisk USB-C-06 16GB SDCZ450 USB3.1 / 480G SanDisk SSD-26 6.Monitors: P2214H Dell Monitor-15 S2718HN Dell Monitor-77 AW2518H Alienware Monitor-83 Note: 1. VNP on Lid open Cross Platform: N/A Test case: [CSV-TC-5209][WIS-TC-4396] Linux_NB_Salomon-Wired-Dock-The "Cold Boot" Stress Test step:27 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. Close lid of SUT set external three displays to Join Display Mode; 5. Press Power Button on Salomon Dock to Shut Down SUT; 6. Press Power Button on Salomon Dock to Power on SUT; 7. SUT will hang in cold boot progress.>problem1(refer to Video) 8. Connect USB Keyboard and USB Mouse to SUT; 9. Connect USB-A 3.0 and Type-c USB 3.1 Memory Key to SUT; 10. Connect a Type-c 3.1 SSD to SUT; 11. Close SUT Lid, set external three displays to Join Display Mode; 12. Press Power Button on Salomon Dock to Shut Down SUT; 13. Press Power Button on Salomon Dock to Power on SUT; 14. Find SUT hang in cold boot progress.>problem2(refer to Video) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804794/+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 1804799] [NEW] Linux, Ubuntu, 18.04, NB13, Run USB tests in checkbox show error after insert USB device(FR:100%)
Public bug reported: Description: USB tests in checkbox showe error information after insert USB device. Expected Behavior: USB tests should not show error information after insert USB2.0/USB3.0 devices. Severity: Sev-3 P3 C3 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:Ubuntu.18.04 CI Note: NA Cross Platform: N/A Test case: [CPV-TC-5239][WIS-TC-4427] Ubuntu18.04_Certification - Automation Test using Checkbox step:4 Steps to Reproduce: 1. Flash BIOS to 0.4.1,install ubuntu OS 18.04. 2. Boot to OS, Install Checkbox - Offline:sh ./odm-checkbox-installer.sh. 3. Open terminal and run: ./odm-somerville-cli, 4. Select test categories related to the Categories in Test Case Notes and press < OK > to enter test case selection screen. 5. Select USB tests,press 'T' to start,enter 's' skip this job,Skip to 'USB 2.0 storage device insertion detected. 6. Press 'enter' to continue-->insert USB2.0 USB key when prompt 'insert now. 7. Find show error info:error:root:Unable to locate drive associated with /org/freedesktop/UDisk2/block_devices/loop.-->Problem(refer pic) ** Affects: glance Importance: Undecided Status: New ** Attachment added: "sosreport-SKU8.NB13-2018112202-0425.tar.xz" https://bugs.launchpad.net/bugs/1804799/+attachment/5215597/+files/sosreport-SKU8.NB13-2018112202-0425.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/1804799 Title: Linux, Ubuntu,18.04, NB13, Run USB tests in checkbox show error after insert USB device(FR:100%) Status in Glance: New Bug description: Description: USB tests in checkbox showe error information after insert USB device. Expected Behavior: USB tests should not show error information after insert USB2.0/USB3.0 devices. Severity: Sev-3 P3 C3 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:Ubuntu.18.04 CI Note: NA Cross Platform: N/A Test case: [CPV-TC-5239][WIS-TC-4427] Ubuntu18.04_Certification - Automation Test using Checkbox step:4 Steps to Reproduce: 1. Flash BIOS to 0.4.1,install ubuntu OS 18.04. 2. Boot to OS, Install Checkbox - Offline:sh ./odm-checkbox-installer.sh. 3. Open terminal and run: ./odm-somerville-cli, 4. Select test categories related to the Categories in Test Case Notes and press < OK > to enter test case selection screen. 5. Select USB tests,press 'T' to start,enter 's' skip this job,Skip to 'USB 2.0 storage device insertion detected. 6. Press 'enter' to continue-->insert USB2.0 USB key when prompt 'insert now. 7. Find show error info:error:root:Unable to locate drive associated with /org/freedesktop/UDisk2/block_devices/loop.-->Problem(refer pic) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804799/+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 1804809] [NEW] salt-minion not started after installation
Public bug reported: the cc_salt_minion.py module uses the service command to start salt- minion after installation. However this command is not guaranteed to exist on all distributions. In Gentoo, openrc stopped providing this binary not so long ago [1] but using systemd on Gentoo does not provide this either. In debian 9 the bin is provided by init-system-helpers [2] which is an essential package meaning removing it most likely breaks your system. I wanted to suggest to use distro class init_cmd but even this feels a bit limited as it requires duplication for distributions that support more than one init system. Would it make sense to create a class hierarchy to support the classical init systems out there (openrc, debian-style init, systemd) and allow automatic detection of the actual init being used ? [1] https://www.gentoo.org/support/news-items/2017-10-13-openrc-service-binary-removal.html [2] https://packages.debian.org/unstable/main/init-system-helpers ** Affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1804809 Title: salt-minion not started after installation Status in cloud-init: New Bug description: the cc_salt_minion.py module uses the service command to start salt- minion after installation. However this command is not guaranteed to exist on all distributions. In Gentoo, openrc stopped providing this binary not so long ago [1] but using systemd on Gentoo does not provide this either. In debian 9 the bin is provided by init-system-helpers [2] which is an essential package meaning removing it most likely breaks your system. I wanted to suggest to use distro class init_cmd but even this feels a bit limited as it requires duplication for distributions that support more than one init system. Would it make sense to create a class hierarchy to support the classical init systems out there (openrc, debian-style init, systemd) and allow automatic detection of the actual init being used ? [1] https://www.gentoo.org/support/news-items/2017-10-13-openrc-service-binary-removal.html [2] https://packages.debian.org/unstable/main/init-system-helpers To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1804809/+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 1804811] [NEW] DatabaseAtVersion fixture causes order-related failures in tests using Database fixture
Public bug reported: The DatabaseAtVersion fixture starts the global TransactionContext, but doesn't set the guard to configure() used by the Database fixture. Consequently, if Database runs after DatabaseAtVersion in the same worker, the subsequent fixture will fail. An example ordering which fails is: nova.tests.unit.db.test_sqlalchemy_migration.TestNewtonCellsCheck.test_upgrade_without_cell0 nova.tests.unit.db.test_sqlalchemy_migration.TestNewtonCheck.test_pci_device_type_vf_not_migrated ** 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/1804811 Title: DatabaseAtVersion fixture causes order-related failures in tests using Database fixture Status in OpenStack Compute (nova): New Bug description: The DatabaseAtVersion fixture starts the global TransactionContext, but doesn't set the guard to configure() used by the Database fixture. Consequently, if Database runs after DatabaseAtVersion in the same worker, the subsequent fixture will fail. An example ordering which fails is: nova.tests.unit.db.test_sqlalchemy_migration.TestNewtonCellsCheck.test_upgrade_without_cell0 nova.tests.unit.db.test_sqlalchemy_migration.TestNewtonCheck.test_pci_device_type_vf_not_migrated To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1804811/+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 1804815] [NEW] Linux, Ubuntu, 18.04, NB13, Monitors plugged to BME dock show garbage after dock/undock BME.
Public bug reported: Description: Boot to OS with BME dock is connected, plug in two 4K monitors to dock, hot plug/unplug BME dock, and then find a external monitor show garbage.(FR: 1/10 times) Expected Behavior: External monitor don't show garbage after dock/undock BME. Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS: CI Ubuntu 18.04 4. BME-DOCK-114(REV-A05) FW:0.1.17 5. Monitor: Sumsung U28E590D, Dell P2715Q 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 change resolution. Cross Platform: N/A Test case: CSV-TC-4663[WIS-TC-4209] Linux_NB_BME-Wired-Dock-The "Multiple "4K@60-Hz" Displays/Monitors" (HDMI/DP) Support Test step:12 Steps to Reproduce 1. Flash Latest BIOS, install Ubuntu OS 18.04. 2. Boot to OS, connect a BME Dock to SUT; 3. Connect two 4K Monitors to SUT; 4. Dock/undock BME and find one Monitor show Garbage.>problem(refer to pic) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "Garbage1.jpg" https://bugs.launchpad.net/bugs/1804815/+attachment/5215648/+files/Garbage1.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/1804815 Title: Linux, Ubuntu,18.04, NB13, Monitors plugged to BME dock show garbage after dock/undock BME. Status in Glance: New Bug description: Description: Boot to OS with BME dock is connected, plug in two 4K monitors to dock, hot plug/unplug BME dock, and then find a external monitor show garbage.(FR: 1/10 times) Expected Behavior: External monitor don't show garbage after dock/undock BME. Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS: CI Ubuntu 18.04 4. BME-DOCK-114(REV-A05) FW:0.1.17 5. Monitor: Sumsung U28E590D, Dell P2715Q 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 change resolution. Cross Platform: N/A Test case: CSV-TC-4663[WIS-TC-4209] Linux_NB_BME-Wired-Dock-The "Multiple "4K@60-Hz" Displays/Monitors" (HDMI/DP) Support Test step:12 Steps to Reproduce 1. Flash Latest BIOS, install Ubuntu OS 18.04. 2. Boot to OS, connect a BME Dock to SUT; 3. Connect two 4K Monitors to SUT; 4. Dock/undock BME and find one Monitor show Garbage.>problem(refer to pic) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804815/+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 1804824] [NEW] Linux, Ubuntu, 18.04, CI, NB13, 2 4K monitors connected to SUT via BME and local LCD can't be display
Public bug reported: Description: Boot to OS and connect BME dock to SUT. Plug two 4K monitors to BME dock via HDMI/mDP or DP/HDMI or DP/mDP, find SUT's internal LCD and external monitors don't have display. Expected Behavior: SUT and external monitor should display normally. Severity: Sev-2 P3 C3 L1 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:Ubuntu.18.04 CI 4. BME Dock: Dock-114 FW:0.1.17 REV-A05 Note: 1. VNP on Salomon Single-C & TBT3 dock 2. VNP on Win10 RS5 17763 3. VNP on connect 1x4K monitor to BME dock 4. VNP on connect other resolution(<3840x2160) monitors to BME dock Cross Platform: N/A Test case: [CSV-TC-4663][WIS-TC-4209] Linux_NB_BME-Wired-Dock-The "Multiple "4K@60-Hz" Displays/Monitors" (HDMI/DP) Support Test Step11 Steps to Reproduce 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS with BME Dock connected. 3. Plug in 2 4K monitors to BME dock via DP/HDMI, find SUT and external monitor don't have display.-->Problem(refer to picture) 4. Plug in 2 4K monitors to BME dock via mDP/HDMI, find SUT and external monitor don't have display.-->Problem 5. Plug in 2 4K monitors to BME dock via DP/mDP, find SUT and external monitor don't have display.-->Problem ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-Ubuntu18.04-LTSCILatitude2-5380.tar11.xz" https://bugs.launchpad.net/bugs/1804824/+attachment/5215666/+files/sosreport-Ubuntu18.04-LTSCILatitude2-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/1804824 Title: Linux, Ubuntu, 18.04, CI, NB13,2 4K monitors connected to SUT via BME and local LCD can't be display Status in Glance: New Bug description: Description: Boot to OS and connect BME dock to SUT. Plug two 4K monitors to BME dock via HDMI/mDP or DP/HDMI or DP/mDP, find SUT's internal LCD and external monitors don't have display. Expected Behavior: SUT and external monitor should display normally. Severity: Sev-2 P3 C3 L1 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:Ubuntu.18.04 CI 4. BME Dock: Dock-114 FW:0.1.17 REV-A05 Note: 1. VNP on Salomon Single-C & TBT3 dock 2. VNP on Win10 RS5 17763 3. VNP on connect 1x4K monitor to BME dock 4. VNP on connect other resolution(<3840x2160) monitors to BME dock Cross Platform: N/A Test case: [CSV-TC-4663][WIS-TC-4209] Linux_NB_BME-Wired-Dock-The "Multiple "4K@60-Hz" Displays/Monitors" (HDMI/DP) Support Test Step11 Steps to Reproduce 1. Install Ubuntu OS 18.04.1 LTS 2. Boot to OS with BME Dock connected. 3. Plug in 2 4K monitors to BME dock via DP/HDMI, find SUT and external monitor don't have display.-->Problem(refer to picture) 4. Plug in 2 4K monitors to BME dock via mDP/HDMI, find SUT and external monitor don't have display.-->Problem 5. Plug in 2 4K monitors to BME dock via DP/mDP, find SUT and external monitor don't have display.-->Problem To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804824/+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 1804842] [NEW] When kill(sometines doesn't restart) the ovs switch or restart it in the compute nodes vm conectivity is lost
Public bug reported: OSP 14 3 controllers + 3 computes + dvr several vms in one compute with fip. Problem 1 : root@compute-2 heat-admin]# systemctl restart openvswitch fip conectivity with undercloud vm is lost and no recover conectivity with other computes is lost, but it is recovered restarting neutron openvswitch agent container root@compute-2 heat-admin]# systemctl restart openvswitch. Problem 2: After kill -9 "pid ovs switch" Sometimes the ovs switch in not restarted automatically Same problems that in the scenario1 [root@compute-2 heat-admin]# ps -ef | grep ovs root 105587292 0 12:09 ?00:00:01 /usr/bin/python2 /bin/privsep-helper --config-file /usr/share/nova/nova-dist.conf --config-file /etc/nova/nova.conf --privsep_context vif_plug_ovs.privsep.vif_plug --privsep_sock_path /tmp/tmpATdioG/privsep.sock 42435 46886 46871 0 13:17 ?00:00:00 /bin/bash /neutron_ovs_agent_launcher.sh openvsw+ 49054 1 1 13:20 ?00:00:00 ovs-vswitchd unix:/var/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info --mlockall --user openvswitch:hugetlbfs --no-chdir --log-file=/var/log/openvswitch/ovs-vswitchd.log --pidfile=/var/run/openvswitch/ovs-vswitchd.pid --detach root 49217 17666 0 13:21 pts/000:00:00 grep --color=auto ovs [root@compute-2 heat-admin]# [root@compute-2 heat-admin]# [root@compute-2 heat-admin]# ps -ef | grep ovs root 105587292 0 12:09 ?00:00:01 /usr/bin/python2 /bin/privsep-helper --config-file /usr/share/nova/nova-dist.conf --config-file /etc/nova/nova.conf --privsep_context vif_plug_ovs.privsep.vif_plug --privsep_sock_path /tmp/tmpATdioG/privsep.sock 42435 46886 46871 0 13:17 ?00:00:00 /bin/bash /neutron_ovs_agent_launcher.sh openvsw+ 49054 1 0 13:20 ?00:00:00 ovs-vswitchd unix:/var/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info --mlockall --user openvswitch:hugetlbfs --no-chdir --log-file=/var/log/openvswitch/ovs-vswitchd.log --pidfile=/var/run/openvswitch/ovs-vswitchd.pid --detach root 49421 17666 0 13:21 pts/000:00:00 grep --color=auto ovs [root@compute-2 heat-admin]# [root@compute-2 heat-admin]# [root@compute-2 heat-admin]# ps -ef | grep ovs root 105587292 0 12:09 ?00:00:01 /usr/bin/python2 /bin/privsep-helper --config-file /usr/share/nova/nova-dist.conf --config-file /etc/nova/nova.conf --privsep_context vif_plug_ovs.privsep.vif_plug --privsep_sock_path /tmp/tmpATdioG/privsep.sock 42435 46886 46871 0 13:17 ?00:00:00 /bin/bash /neutron_ovs_agent_launcher.sh openvsw+ 49054 1 0 13:20 ?00:00:00 ovs-vswitchd unix:/var/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info --mlockall --user openvswitch:hugetlbfs --no-chdir --log-file=/var/log/openvswitch/ovs-vswitchd.log --pidfile=/var/run/openvswitch/ovs-vswitchd.pid --detach root 49423 17666 0 13:21 pts/000:00:00 grep --color=auto ovs [root@compute-2 heat-admin]# [root@compute-2 heat-admin]# [root@compute-2 heat-admin]# [root@compute-2 heat-admin]# kill -9 49054 [root@compute-2 heat-admin]# ps -ef | grep ovs root 105587292 0 12:09 ?00:00:01 /usr/bin/python2 /bin/privsep-helper --config-file /usr/share/nova/nova-dist.conf --config-file /etc/nova/nova.conf --privsep_context vif_plug_ovs.privsep.vif_plug --privsep_sock_path /tmp/tmpATdioG/privsep.sock 42435 46886 46871 0 13:17 ?00:00:00 /bin/bash /neutron_ovs_agent_launcher.sh root 49610 17666 0 13:22 pts/000:00:00 grep --color=auto ovs [root@compute-2 heat-admin]# [root@compute-2 heat-admin]# [root@compute-2 heat-admin]# [root@compute-2 heat-admin]# ps -ef | grep ovs root 105587292 0 12:09 ?00:00:01 /usr/bin/python2 /bin/privsep-helper --config-file /usr/share/nova/nova-dist.conf --config-file /etc/nova/nova.conf --privsep_context vif_plug_ovs.privsep.vif_plug --privsep_sock_path /tmp/tmpATdioG/privsep.sock 42435 46886 46871 0 13:17 ?00:00:00 /bin/bash /neutron_ovs_agent_launcher.sh root 49628 17666 0 13:22 pts/000:00:00 grep --color=auto ovs [root@compute-2 heat-admin]# date Fri Nov 23 13:22:22 UTC 2018 [root@compute-2 heat-admin]# ps -ef | grep ovs root 105587292 0 12:09 ?00:00:01 /usr/bin/python2 /bin/privsep-helper --config-file /usr/share/nova/nova-dist.conf --config-file /etc/nova/nova.conf --privsep_context vif_plug_ovs.privsep.vif_plug --privsep_sock_path /tmp/tmpATdioG/privsep.sock 42435 46886 46871 0 13:17 ?00:00:00 /bin/bash /neutron_ovs_agent_launcher.sh root 49788 17666 0 13:22 pts/000:00:00 grep --color=auto ovs [root@compute-2 heat-admin]# [root@compute-2 heat-admin]# [root@compute-2 heat-admin]# ps -ef | grep ovs root 105587292 0 12:09 ?00:00:01 /usr/bin/python2 /bin/privsep-helper --config-file /usr/share/nova/nova-dist.conf --config-file /e
[Yahoo-eng-team] [Bug 1804844] [NEW] CI jobs definitions should be migrated to Zuul v3 syntax
Public bug reported: List of Neutron CI jobs defined with legacy zuul syntax: neutron-functional neutron-functional-with-uwsgi neutron-fullstack neutron-fullstack-with-uwsgi neutron-tempest-dvr neutron-tempest-linuxbridge neutron-grenade neutron-grenade-multinode neutron-grenade-dvr-multinode neutron-tempest-dvr-ha-multinode-full neutron-tempest-iptables_hybrid neutron-tempest-with-ryu-master neutron-tempest-with-uwsgi We need to migrate them to Zuul v3. ** Affects: neutron Importance: Low Assignee: Slawek Kaplonski (slaweq) Status: Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1804844 Title: CI jobs definitions should be migrated to Zuul v3 syntax Status in neutron: Confirmed Bug description: List of Neutron CI jobs defined with legacy zuul syntax: neutron-functional neutron-functional-with-uwsgi neutron-fullstack neutron-fullstack-with-uwsgi neutron-tempest-dvr neutron-tempest-linuxbridge neutron-grenade neutron-grenade-multinode neutron-grenade-dvr-multinode neutron-tempest-dvr-ha-multinode-full neutron-tempest-iptables_hybrid neutron-tempest-with-ryu-master neutron-tempest-with-uwsgi We need to migrate them to Zuul v3. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1804844/+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 1804900] [NEW] share-pci-between-numa-nodes.html implemented spec for Queens still contains reference to image and flavor metadata
Public bug reported:
share-pci-between-numa-nodes.html implemented spec for Queens still contains
reference to image and flavor metadata
--
Note that
https://review.openstack.org/#/q/topic:bp/share-pci-between-numa-nodes links to
[Update 'share-pci-between-numa-nodes' spec to reflect
reality](https://review.openstack.org/#/c/555000/)
With description:
~~~
Update 'share-pci-between-numa-nodes' spec to reflect reality Upon
implementation, the per-device configuration was deemed preferable to adding
yet more image metadata and flavor extra spec keys. Update the spec to reflect
this change.
~~~
However, the spec seems to have omitted that there is a section still
talking about image and flavor metadata:
https://review.openstack.org/#/c/555000/3/specs/queens/implemented/share-pci-between-numa-nodes.rst
https://specs.openstack.org/openstack/nova-specs/specs/queens/implemented/share-pci-between-numa-nodes.html
~~~
If both image and flavor properties are not set (equals ``None``) the
``legacy`` policy will be used. If one of image *or* flavor property is not set
(equals ``None``) but the other property is set then the value of the set
property will be used. In a case of conflicts between flavor and image
properties (both properties are set and they are not equal) an exception will
be raised.
The end result will be an option that looks something like this::
[pci]
alias = '{
"name": "QuickAssist",
"product_id": "0443",
"vendor_id": "8086",
"device_type": "type-PCI",
"numa_policy": "legacy"
}'
~~~
** Affects: nova
Importance: Undecided
Assignee: Andreas Karis (akaris)
Status: New
** Changed in: nova
Assignee: (unassigned) => Andreas Karis (akaris)
--
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/1804900
Title:
share-pci-between-numa-nodes.html implemented spec for Queens still
contains reference to image and flavor metadata
Status in OpenStack Compute (nova):
New
Bug description:
share-pci-between-numa-nodes.html implemented spec for Queens still contains
reference to image and flavor metadata
--
Note that
https://review.openstack.org/#/q/topic:bp/share-pci-between-numa-nodes links to
[Update 'share-pci-between-numa-nodes' spec to reflect
reality](https://review.openstack.org/#/c/555000/)
With description:
~~~
Update 'share-pci-between-numa-nodes' spec to reflect reality Upon
implementation, the per-device configuration was deemed preferable to adding
yet more image metadata and flavor extra spec keys. Update the spec to reflect
this change.
~~~
However, the spec seems to have omitted that there is a section still
talking about image and flavor metadata:
https://review.openstack.org/#/c/555000/3/specs/queens/implemented/share-pci-between-numa-nodes.rst
https://specs.openstack.org/openstack/nova-specs/specs/queens/implemented/share-pci-between-numa-nodes.html
~~~
If both image and flavor properties are not set (equals ``None``) the
``legacy`` policy will be used. If one of image *or* flavor property is not
set
(equals ``None``) but the other property is set then the value of the set
property will be used. In a case of conflicts between flavor and image
properties (both properties are set and they are not equal) an exception will
be raised.
The end result will be an option that looks something like this::
[pci]
alias = '{
"name": "QuickAssist",
"product_id": "0443",
"vendor_id": "8086",
"device_type": "type-PCI",
"numa_policy": "legacy"
}'
~~~
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1804900/+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 1804903] [NEW] Linux, Ubuntu, 18.04, NB13, Monitor can't display after plug it to salomon when SUT in suspend mode.
Public bug reported: Description: Connect a Single-c Salomin dock to SUT, put SUT to suspend mode. Plug an external monitor to Salomon dock via DP/HDMI cable, wake up SUT, find external monitor can't display. Expected Behavior: External monitor can display normally when plug it on salomon dock in suspend mode. 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. P2715Q Dell Monitor-89 Note: 1. VP on Salomon TBT3 cable Dock 2. VNP on BME dock(REV-A05 FW:01.17) Cross Platform: N/A Test case: [CSV-TC-5197][WIS-TC-4410] Linux_NB_Salomon-Wired-Dock-The Single "4K@60-Hz Display/Monitor Support" Test step:23 Steps to Reproduce: 1. Flash Latest BIOS, install Ubuntu OS 18.04. 2. Boot to BIOS setup, set Power Management sleep mode to force suspend; 3. Boot to OS, connect a Salomon dock to SUT; 4. Put SUT to suspend mode; 5. Plug in HDMI monitor to Salomon dock; 6. Wake up SUT, find external monitor can't display.>problem(refer to pic) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "IMG_no display plug in suspend.jpg" https://bugs.launchpad.net/bugs/1804903/+attachment/5215805/+files/IMG_no%20display%20plug%20in%20suspend.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/1804903 Title: Linux, Ubuntu,18.04, NB13, Monitor can't display after plug it to salomon when SUT in suspend mode. Status in Glance: New Bug description: Description: Connect a Single-c Salomin dock to SUT, put SUT to suspend mode. Plug an external monitor to Salomon dock via DP/HDMI cable, wake up SUT, find external monitor can't display. Expected Behavior: External monitor can display normally when plug it on salomon dock in suspend mode. 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. P2715Q Dell Monitor-89 Note: 1. VP on Salomon TBT3 cable Dock 2. VNP on BME dock(REV-A05 FW:01.17) Cross Platform: N/A Test case: [CSV-TC-5197][WIS-TC-4410] Linux_NB_Salomon-Wired-Dock-The Single "4K@60-Hz Display/Monitor Support" Test step:23 Steps to Reproduce: 1. Flash Latest BIOS, install Ubuntu OS 18.04. 2. Boot to BIOS setup, set Power Management sleep mode to force suspend; 3. Boot to OS, connect a Salomon dock to SUT; 4. Put SUT to suspend mode; 5. Plug in HDMI monitor to Salomon dock; 6. Wake up SUT, find external monitor can't display.>problem(refer to pic) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804903/+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 1804904] [NEW] Linux, Ubuntu, 18.04, NB13, Network connection not according to settings after switch User.
Public bug reported: Description: Connect a Lan cable to SUT's RJ45 Lan port. 1. Set wired connect automatically checked, disconnect Lan connecttion. Switch to another user, Network don't connect automatically. 2. Set wired connect automatically unchecked, enable Lan connection. Switch to another user, Network connect automatically. Expected Behavior: Network connection according setting after switch User. Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS: CI Ubuntu 18.04 Note: 1. VP on Salomon Single-C Dock 165: DP/N :0YVYPW REV X00 FW:00.00.12.01 Lan Port Cross Platform: N/A Test case: [CSV-TC-4572][WIS-TC-4167] Linux_Wired - Basic Functionality Test step:10/11/12/13 Steps to Reproduce 1. Flash Latest BIOS, install Ubuntu OS 18.04; 2. Boot to OS, connect a Lan cable to SUT Lan port; 3. Navigate to Network wired setting; 4. Set wired connect automatically checked, disconnect Lan connecttion; 5. Switch to another user, Network don't connect automatically.>problem(refer to Video) 6. Navigate to Network wired setting; 7. Set wired connect automatically unchecked, enable Lan connection; 8. Switch to another user, Network connect automatically.>problem(refer to Video) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "VID_Lan connect not according setting.mp4" https://bugs.launchpad.net/bugs/1804904/+attachment/5215807/+files/VID_Lan%20connect%20not%20according%20setting.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/1804904 Title: Linux, Ubuntu,18.04, NB13, Network connection not according to settings after switch User. Status in Glance: New Bug description: Description: Connect a Lan cable to SUT's RJ45 Lan port. 1. Set wired connect automatically checked, disconnect Lan connecttion. Switch to another user, Network don't connect automatically. 2. Set wired connect automatically unchecked, enable Lan connection. Switch to another user, Network connect automatically. Expected Behavior: Network connection according setting after switch User. Severity: Sev-2 P2 C2 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.0 3. OS: CI Ubuntu 18.04 Note: 1. VP on Salomon Single-C Dock 165: DP/N :0YVYPW REV X00 FW:00.00.12.01 Lan Port Cross Platform: N/A Test case: [CSV-TC-4572][WIS-TC-4167] Linux_Wired - Basic Functionality Test step:10/11/12/13 Steps to Reproduce 1. Flash Latest BIOS, install Ubuntu OS 18.04; 2. Boot to OS, connect a Lan cable to SUT Lan port; 3. Navigate to Network wired setting; 4. Set wired connect automatically checked, disconnect Lan connecttion; 5. Switch to another user, Network don't connect automatically.>problem(refer to Video) 6. Navigate to Network wired setting; 7. Set wired connect automatically unchecked, enable Lan connection; 8. Switch to another user, Network connect automatically.>problem(refer to Video) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804904/+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 1804905] [NEW] Linux, Ubuntu, 18.04, CI, NB13, After lid close/open, external screen show black screen about 10s.
Public bug reported: Description: Connect monitor to SUT, local LCD and external monitor display as Join Displays normaly, close/open lid external monitor show black screen about 10s, then display OS desktop. Expected Behavior: External monitor show OS desktop immediately after close/open lid. 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 2. VP on Salomon single-c/TBT cable Dock 3. VP on BME Dock(REV-A05 Dock-114 FW:0.1.17) 4. VP on IE Dock(REV-A03 FW:1.0.4) 5. VP on Type-C/HDMI/DP/VGA 6. VP on Join Displays/Mirror/Single Display mode 7. VNP on Windows OS Cross Platform: NA Test case: [CSV-TC-5222][WIS-TC-4399] Linux_NB_Salomon-Wired-Dock-The "DisplayPort Over USB-C" Connector/Port Video Test with "USB-C to HDMI" Adapter/Dongle,step 16. Steps to Reproduce: 1. Clean Install Ubuntu OS 18.04 2. Boot to OS and connect salomon dock to SUT; 3. Connect an external monitor to SUT, local LCD and external monitor display as Join Displays normaly, close lid, find external monitor show black screen about 10s.-->Problem(refer to video) 4. Open lid, find SUT and external monitor show black screen about 10s.-->Problem ** Affects: glance Importance: Undecided Status: New ** Attachment added: "sosreport-zach.yy-20181123035355.tar.xz" https://bugs.launchpad.net/bugs/1804905/+attachment/5215809/+files/sosreport-zach.yy-20181123035355.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/1804905 Title: Linux, Ubuntu, 18.04, CI, NB13, After lid close/open, external screen show black screen about 10s. Status in Glance: New Bug description: Description: Connect monitor to SUT, local LCD and external monitor display as Join Displays normaly, close/open lid external monitor show black screen about 10s, then display OS desktop. Expected Behavior: External monitor show OS desktop immediately after close/open lid. 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 2. VP on Salomon single-c/TBT cable Dock 3. VP on BME Dock(REV-A05 Dock-114 FW:0.1.17) 4. VP on IE Dock(REV-A03 FW:1.0.4) 5. VP on Type-C/HDMI/DP/VGA 6. VP on Join Displays/Mirror/Single Display mode 7. VNP on Windows OS Cross Platform: NA Test case: [CSV-TC-5222][WIS-TC-4399] Linux_NB_Salomon-Wired-Dock-The "DisplayPort Over USB-C" Connector/Port Video Test with "USB-C to HDMI" Adapter/Dongle,step 16. Steps to Reproduce: 1. Clean Install Ubuntu OS 18.04 2. Boot to OS and connect salomon dock to SUT; 3. Connect an external monitor to SUT, local LCD and external monitor display as Join Displays normaly, close lid, find external monitor show black screen about 10s.-->Problem(refer to video) 4. Open lid, find SUT and external monitor show black screen about 10s.-->Problem To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804905/+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 1804911] [NEW] Linux, Ubuntu, 18.04, NB13, Stress tests in checkbox can't be completed.(FR:6/6units)
Public bug reported: Description: Stress tests in checkbox tool can't be complete. Expected Behavior: Stress tests can be completed without errors. Severity: Sev-3 P3 C3 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:Ubuntu.18.04 CI Note: NA Cross Platform: N/A Test case: [CPV-TC-5239][WIS-TC-4427] Ubuntu18.04_Certification - Automation Test using Checkbox step:4 Steps to Reproduce: 1. Flash BIOS to 0.4.1,install ubuntu OS 18.04. 2. Boot to OS, Connected LOM,Install Checkbox - Offline:sh ./odm-checkbox-installer.sh. 3. Open terminal and run: ./odm-somerville-cli, 4. Press 'X' to Select 'Somerville ODM testing' and press'Enter' to continue. 5. Choose 'Stress tests' to run,press 'T' to start. 6. Press 'P' and 'enter' to continue-->press Enter to continue when prompt.SUT will enter suspend. 7. After 3-4 hours,The SUT alway black screen,can't resume,press power button to resume SUT. 8. Find The stress tests can't complete and will stop on terminal UI .-->Problem(refer pic) ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-sku9.stresstests-20181123052456.tar.xz" https://bugs.launchpad.net/bugs/1804911/+attachment/5215822/+files/sosreport-sku9.stresstests-20181123052456.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/1804911 Title: Linux, Ubuntu,18.04, NB13, Stress tests in checkbox can't be completed.(FR:6/6units) Status in Glance: New Bug description: Description: Stress tests in checkbox tool can't be complete. Expected Behavior: Stress tests can be completed without errors. Severity: Sev-3 P3 C3 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:Ubuntu.18.04 CI Note: NA Cross Platform: N/A Test case: [CPV-TC-5239][WIS-TC-4427] Ubuntu18.04_Certification - Automation Test using Checkbox step:4 Steps to Reproduce: 1. Flash BIOS to 0.4.1,install ubuntu OS 18.04. 2. Boot to OS, Connected LOM,Install Checkbox - Offline:sh ./odm-checkbox-installer.sh. 3. Open terminal and run: ./odm-somerville-cli, 4. Press 'X' to Select 'Somerville ODM testing' and press'Enter' to continue. 5. Choose 'Stress tests' to run,press 'T' to start. 6. Press 'P' and 'enter' to continue-->press Enter to continue when prompt.SUT will enter suspend. 7. After 3-4 hours,The SUT alway black screen,can't resume,press power button to resume SUT. 8. Find The stress tests can't complete and will stop on terminal UI .-->Problem(refer pic) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804911/+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 1803189] Re: Error during login 'bool' object is not callable
This report is about ubuntu package, so I added it to the affected
project.
As upstream horizon, I could not reproduce this... so I mark it as
Incomplete.
** Also affects: horizon (Ubuntu)
Importance: Undecided
Status: New
** Changed in: horizon
Status: New => Incomplete
--
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/1803189
Title:
Error during login 'bool' object is not callable
Status in OpenStack Dashboard (Horizon):
Incomplete
Status in horizon package in Ubuntu:
New
Bug description:
I have installed Openstack horizon rocky using ubuntu apt package
manager. But as soon as i give my login credentials, i am hitting at
this error.
Environment:
Request Method: GET
Request URL: http://10.10.20.10:10443/auth/login/?next=/
Django Version: 1.11.15
Python Version: 2.7.15
Installed Applications:
['openstack_dashboard.dashboards.project',
'heat_dashboard',
'openstack_dashboard.dashboards.admin',
'openstack_dashboard.dashboards.identity',
'openstack_dashboard.dashboards.settings',
'openstack_dashboard',
'django.contrib.contenttypes',
'django.contrib.auth',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'django.contrib.humanize',
'django_pyscss',
'openstack_dashboard.django_pyscss_fix',
'compressor',
'horizon',
'openstack_auth']
Installed Middleware:
('django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'horizon.middleware.OperationLogMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.contrib.auth.middleware.SessionAuthenticationMiddleware',
'horizon.middleware.HorizonMiddleware',
'horizon.themes.ThemeMiddleware',
'django.middleware.locale.LocaleMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
'openstack_dashboard.contrib.developer.profiler.middleware.ProfilerClientMiddleware',
'openstack_dashboard.contrib.developer.profiler.middleware.ProfilerMiddleware')
Traceback:
File
"/usr/local/lib/python2.7/dist-packages/django/core/handlers/exception.py" in
inner
41. response = get_response(request)
File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py" in
_legacy_get_response
244. response = middleware_method(request)
File "/usr/share/openstack-dashboard/horizon/middleware/base.py" in
process_request
52. if not hasattr(request, "user") or not
request.user.is_authenticated():
Exception Type: TypeError at /auth/login/
Exception Value: 'bool' object is not callable
Any idea about the error ?
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1803189/+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 1804915] [NEW] Linux, Ubuntu, 18.04, NB13, SUT can't wake from power off via WOL when connect Dock.(FR:100%)
Public bug reported: Description: 1.SUT can't wake from power off via WOL when connect Dock(BME/Saomon cable Dock/IE Dock). 2.SUT can wake from Suspend via WOL when connect Dock(BME/Saomon cable Dock/IE Dock). Expected Behavior: SUT can wake from power off via WOL when connect Dock. Severity: Sev-3 P3 C3 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:Ubuntu.18.04 CI 4. Dock:IE Dock-113 A05 FW:0.1.16 Note: 1.VP on Salomon Single-c cable dock-150 X01 FW:00.00.12.01 2.VP on BME Dock-116 A05 FW:0.1.17 3.VP on Salomon TBT3 cable dock-125 X01 FW:00.00.12.01 4.VNP on use another SUT directly to Wake on Lan from Suspend/Shutdown power state. Cross Platform: N/A Test case: [CPV-TC-5215][WIS-TC-4419] Linux_NB_Salomon-Wired-Dock-The "Dock Setup & Basic Functionality" Test step:44 Steps to Reproduce 1. Flash BIOS to 0.4.1,install ubuntu OS 18.04. 2. Connected Dock on SUT,Setting Wake on LAN in OS and BIOS on Two SUT(refer Link: blog,sina.com.cn/s/blog_8a06d57b01031b8u.html). 3. Power off SUT under test. 4. Type wakeonlan mac adress in terminal to wake another SUT. 5. Find SUT can't wake from power off via WOL when connect Dock.-->Problem. ** Affects: glance Importance: Undecided Status: New ** Tags: north-bay-13 ** Attachment added: "sosreport-SKU8-NB13-2018112202-0425.tar.xz" https://bugs.launchpad.net/bugs/1804915/+attachment/5215831/+files/sosreport-SKU8-NB13-2018112202-0425.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/1804915 Title: Linux, Ubuntu,18.04, NB13, SUT can't wake from power off via WOL when connect Dock.(FR:100%) Status in Glance: New Bug description: Description: 1.SUT can't wake from power off via WOL when connect Dock(BME/Saomon cable Dock/IE Dock). 2.SUT can wake from Suspend via WOL when connect Dock(BME/Saomon cable Dock/IE Dock). Expected Behavior: SUT can wake from power off via WOL when connect Dock. Severity: Sev-3 P3 C3 L4 Test Environment: 1. Project: Northbay 13 2. BIOS: 0.4.1 3. OS:Ubuntu.18.04 CI 4. Dock:IE Dock-113 A05 FW:0.1.16 Note: 1.VP on Salomon Single-c cable dock-150 X01 FW:00.00.12.01 2.VP on BME Dock-116 A05 FW:0.1.17 3.VP on Salomon TBT3 cable dock-125 X01 FW:00.00.12.01 4.VNP on use another SUT directly to Wake on Lan from Suspend/Shutdown power state. Cross Platform: N/A Test case: [CPV-TC-5215][WIS-TC-4419] Linux_NB_Salomon-Wired-Dock-The "Dock Setup & Basic Functionality" Test step:44 Steps to Reproduce 1. Flash BIOS to 0.4.1,install ubuntu OS 18.04. 2. Connected Dock on SUT,Setting Wake on LAN in OS and BIOS on Two SUT(refer Link: blog,sina.com.cn/s/blog_8a06d57b01031b8u.html). 3. Power off SUT under test. 4. Type wakeonlan mac adress in terminal to wake another SUT. 5. Find SUT can't wake from power off via WOL when connect Dock.-->Problem. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1804915/+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
