Actions
action #44447
closed[sle][functional][y] test fails in partitioning_full_lvm - seems that create_new_partition_table is not working anymore
Status:
Rejected
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 24
Start date:
2018-11-28
Due date:
% Done:
0%
Estimated time:
Difficulty:
Description
Compared with successful test run 5 days ago, we have now problem with create_new_partition_table.
Observation¶
openQA test in scenario sle-15-SP1-Installer-DVD-aarch64-lvm-full-encrypt@aarch64 fails in
partitioning_full_lvm
Reproducible¶
Fails since (at least) Build 102.1
Expected result¶
Last good: 101.2 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by mloviska over 5 years ago
Package list from sle-15-SP1-Installer-DVD-aarch64-Build101.2-lvm-full-encrypt@aarch64
yast2 [4.1.34-18.1.aarch64]
yast2-add-on [4.1.8-8.1.noarch] < skelcd-control-leanos
yast2-bootloader [4.1.11-6.24.aarch64] < yast2-kdump < skelcd-control-leanos
yast2-buildtools [4.1.0-3.12.noarch]
yast2-configuration-management [4.0.3-3.18.noarch] < skelcd-control-leanos
yast2-core [4.1.0-3.8.10.aarch64] < yast2
yast2-country [4.1.1-6.6.aarch64] < yast2-installation
yast2-country-data [4.1.1-6.6.aarch64] < yast2-installation
yast2-devtools [4.1.0-3.12.noarch]
yast2-fcoe-client [4.1.0-4.50.noarch] < skelcd-control-leanos
yast2-firewall [4.0.34-6.10.noarch] < skelcd-control-leanos
yast2-hardware-detection [4.0.0-1.22.aarch64] < yast2
yast2-installation [4.1.25-11.17.noarch]
yast2-iscsi-client [4.1.2-6.5.noarch] < skelcd-control-leanos
yast2-kdump [4.0.4-3.90.aarch64] < skelcd-control-leanos
yast2-ldap [4.0.0-1.43.aarch64] < yast2-users < skelcd-control-leanos
yast2-logs [4.1.34-18.1.aarch64] < yast2
yast2-multipath [4.0.1-3.58.noarch] < skelcd-control-leanos
yast2-network [4.1.15-9.21.noarch] < skelcd-control-leanos
yast2-nfs-client [4.1.0-4.76.noarch] < skelcd-control-leanos
yast2-nfs-common [4.0.1-3.58.noarch] < yast2-nfs-client < skelcd-control-leanos
yast2-ntp-client [4.1.3-6.26.noarch] < skelcd-control-leanos
yast2-packager [4.1.13-11.3.aarch64] < skelcd-control-leanos
yast2-pam [4.0.0-1.13.noarch] < yast2-users < skelcd-control-leanos
yast2-perl-bindings [4.0.1-1.18.aarch64] < yast2
yast2-pkg-bindings [4.1.0-4.6.aarch64] < yast2
yast2-proxy [4.0.2-3.58.noarch] < skelcd-control-leanos
yast2-rdp [4.0.2-3.90.noarch] < skelcd-control-leanos
yast2-registration [4.1.8-3.16.1.noarch] < skelcd-control-leanos
yast2-ruby-bindings [4.1.0-4.6.aarch64] < yast2
yast2-security [4.1.1-4.10.noarch] < yast2-users < skelcd-control-leanos
yast2-services-manager [4.1.8-9.13.noarch] < skelcd-control-leanos
yast2-slp [4.0.0-1.42.aarch64] < skelcd-control-leanos
yast2-storage-ng [4.1.32-21.3.aarch64]
yast2-theme-SLE [4.1.0-3.13.noarch] < skelcd-control-leanos
yast2-trans-stats [2.19.0-1.28.noarch] < skelcd-control-leanos
yast2-transfer [4.0.0-1.43.aarch64] < yast2-packager < skelcd-control-leanos
yast2-tune [4.0.1-3.58.aarch64] < skelcd-control-leanos
yast2-update [4.1.6-9.1.aarch64] < skelcd-control-leanos
yast2-users [4.0.7-4.19.aarch64] < skelcd-control-leanos
yast2-x11 [4.0.1-3.11.aarch64] < skelcd-control-leanos
yast2-xml [4.0.0-1.10.aarch64] < yast2
yast2-ycp-ui-bindings [4.1.0-3.4.aarch64] < yast2
vs sle-15-SP1-Installer-DVD-aarch64-Build110.1-lvm-full-encrypt@aarch64
yast2 [4.0.77-1.1.aarch64]
yast2-add-on [4.0.8-1.54.noarch] < skelcd-control-leanos
yast2-bootloader [4.0.35-1.4.aarch64] < yast2-kdump < skelcd-control-leanos
yast2-buildtools [4.0.5-1.13.noarch]
yast2-configuration-management [4.0.2-1.67.noarch] < skelcd-control-leanos
yast2-core [4.0.2-1.16.aarch64] < yast2
yast2-country [4.0.22-1.13.aarch64] < yast2-installation
yast2-country-data [4.0.22-1.13.aarch64] < yast2-installation
yast2-devtools [4.0.5-1.13.noarch]
yast2-fcoe-client [4.0.0-1.43.noarch] < skelcd-control-leanos
yast2-firewall [4.0.25-1.24.noarch] < skelcd-control-leanos
yast2-hardware-detection [4.0.0-1.22.aarch64] < yast2
yast2-installation [4.0.63-1.4.noarch]
yast2-iscsi-client [4.0.0-1.41.noarch] < skelcd-control-leanos
yast2-kdump [4.0.3-1.47.aarch64] < skelcd-control-leanos
yast2-ldap [4.0.0-1.43.aarch64] < yast2-users < yast2-installation
yast2-multipath [4.0.0-1.55.noarch] < skelcd-control-leanos
yast2-network [4.0.31-1.25.noarch] < yast2-installation
yast2-nfs-client [4.0.6-1.11.noarch] < skelcd-control-leanos
yast2-nfs-common [4.0.0-1.51.noarch] < yast2-nfs-client < skelcd-control-leanos
yast2-ntp-client [4.0.12-1.56.noarch] < skelcd-control-leanos
yast2-packager [4.0.67-1.5.aarch64] < yast2-installation
yast2-pam [4.0.0-1.13.noarch] < yast2-users < yast2-installation
yast2-perl-bindings [4.0.1-1.18.aarch64] < yast2
yast2-pkg-bindings [4.0.11-1.1.aarch64] < yast2-installation
yast2-proxy [4.0.1-1.12.noarch] < yast2-installation
yast2-rdp [4.0.1-1.64.noarch] < skelcd-control-leanos
yast2-registration [4.0.39-1.1.noarch] < skelcd-control-leanos
yast2-ruby-bindings [4.0.6-1.12.aarch64] < yast2-installation
yast2-security [4.0.0-1.42.noarch] < yast2-users < yast2-installation
yast2-services-manager [4.0.3-1.50.noarch] < yast2-installation
yast2-slp [4.0.0-1.42.aarch64] < skelcd-control-leanos
yast2-storage-ng [4.0.186-1.2.aarch64]
yast2-theme-SLE [4.0.4-1.10.noarch] < skelcd-control-leanos
yast2-trans-stats [2.19.0-1.28.noarch] < skelcd-control-leanos
yast2-transfer [4.0.0-1.43.aarch64] < yast2-packager < yast2-installation
yast2-tune [4.0.0-1.57.aarch64] < skelcd-control-leanos
yast2-update [4.0.14-1.25.aarch64] < skelcd-control-leanos
yast2-users [4.0.5-1.40.aarch64] < yast2-installation
yast2-x11 [4.0.0-1.17.aarch64] < skelcd-control-leanos
yast2-xml [4.0.0-1.10.aarch64] < yast2
yast2-ycp-ui-bindings [4.0.0-1.25.aarch64] < yast2
Let's hope that next build is not going to be affected anymore by bsc#1117365.
https://build.suse.de/request/show/178910
Updated by okurz over 5 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: lvm-full-encrypt
https://openqa.suse.de/tests/2340684
Updated by okurz over 5 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: lvm-full-encrypt
https://openqa.suse.de/tests/2340684
Updated by riafarov almost 5 years ago
- Status changed from New to Rejected
- Assignee set to riafarov
https://openqa.suse.de/tests/2822932 this step was fixed.
Actions