action #30703
closed[sle][functional][sle12 sp4][medium] job fails as incomplete in minimal+base+sdk+proxy_SCC-postreg@zkvm because does not schedule correct modules
Added by zluo over 6 years ago. Updated about 6 years ago.
0%
Description
https://openqa.suse.de/tests/1408075
Expected result¶
- Last good SLE 12 SP3 GM
Problem¶
The problem is that no bootloader test module is loaded at all in this scenario. So maybe the test never ran based loading an existing disk image and needs adjustement in the main.pm to execute "bootloader_zkvm.pm" like in other cases.
Updated by okurz over 6 years ago
- Subject changed from [sle][functional][sle12 sp4] yast_scc doesn't start to [sle][functional][medium][sle12 sp4] job fails as incomplete in minimal+base+sdk+proxy_SCC-postreg@zkvm because of "DIE 'current_console' is not set at /usr/lib/os-autoinst/backend/baseclass.pm line 731."
- Description updated (diff)
- Due date set to 2018-02-13
- Category set to Bugs in existing tests
- Assignee set to mgriessmeier
- Target version set to Milestone 14
That "current_console" not set sounds familiar. The only reference in tickets I could find is #28337 which was "resolved" by deleting the test scenarios.
@mgriessmeier does it ring a bell?
Updated by mgriessmeier over 6 years ago
okurz wrote:
That "current_console" not set sounds familiar. The only reference in tickets I could find is #28337 which was "resolved" by deleting the test scenarios.
@mgriessmeier does it ring a bell?
it does... but iirc it appears only if you're trying to start a zkvm job on a e.g. suse-kvm worker - so there might be some variable wrong... though it looks correct on the first look
I'll have a second tomorrow ;)
Updated by mgriessmeier over 6 years ago
uhm wait... there is no bootloader_zkvm loaded...
might be a fallout of https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4246 ;)
Updated by mgriessmeier over 6 years ago
- Subject changed from [sle][functional][medium][sle12 sp4] job fails as incomplete in minimal+base+sdk+proxy_SCC-postreg@zkvm because of "DIE 'current_console' is not set at /usr/lib/os-autoinst/backend/baseclass.pm line 731." to [sle][functional][medium][sle12 sp4][easy] job fails as incomplete in minimal+base+sdk+proxy_SCC-postreg@zkvm because of "DIE 'current_console' is not set at /usr/lib/os-autoinst/backend/baseclass.pm line 731."
Updated by okurz over 6 years ago
- Subject changed from [sle][functional][medium][sle12 sp4][easy] job fails as incomplete in minimal+base+sdk+proxy_SCC-postreg@zkvm because of "DIE 'current_console' is not set at /usr/lib/os-autoinst/backend/baseclass.pm line 731." to [sle][functional][sle12 sp4][easy] job fails as incomplete in minimal+base+sdk+proxy_SCC-postreg@zkvm because of "DIE 'current_console' is not set at /usr/lib/os-autoinst/backend/baseclass.pm line 731."
- Description updated (diff)
- Status changed from New to Workable
- Assignee deleted (
mgriessmeier)
Updated by JERiveraMoya about 6 years ago
- Status changed from Workable to In Progress
- Assignee set to JERiveraMoya
It schedules two modules boot_to_desktop and yast_scc. First one fails because this test is only for booting from existing image, which is not the case. It should schedule a completely different set of modules regarding last good in sle12sp3 (among them, bootloader_zkvm). Adding debug lines to main.pm but it is really messy to figure out how to create the original path of execution.
Updated by JERiveraMoya about 6 years ago
- Subject changed from [sle][functional][sle12 sp4][easy] job fails as incomplete in minimal+base+sdk+proxy_SCC-postreg@zkvm because of "DIE 'current_console' is not set at /usr/lib/os-autoinst/backend/baseclass.pm line 731." to [sle][functional][sle12 sp4][medium] job fails as incomplete in minimal+base+sdk+proxy_SCC-postreg@zkvm because does not schedule correct modules
- Status changed from In Progress to Feedback
- Priority changed from Normal to High
Trying to reproduce in my local the last good we can see that is also failing in the same way: http://dhcp227/tests/460, so I would say that this scenario stops working in all products with recent changes (fallout of https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4246 as @Matthias pointed)
Updated by mgriessmeier about 6 years ago
will pair up on this tomorrow with joaquin
Updated by mgriessmeier about 6 years ago
I did some kind of "bisect" on our testcode and found out that this PR has changed the order of scheduled test modules:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3595
before:
[2018-02-08T08:12:07.0213 CET] [debug] scheduling isosize tests/installation/isosize.pm
[2018-02-08T08:12:07.0215 CET] [debug] scheduling bootloader_zkvm tests/installation/bootloader_zkvm.pm
[2018-02-08T08:12:07.0216 CET] [debug] scheduling welcome tests/installation/welcome.pm
[2018-02-08T08:12:07.0217 CET] [debug] scheduling skip_registration tests/installation/skip_registration.pm
[2018-02-08T08:12:07.0219 CET] [debug] scheduling addon_products_sle tests/installation/addon_products_sle.pm
[2018-02-08T08:12:07.0219 CET] [debug] scheduling partitioning tests/installation/partitioning.pm
[2018-02-08T08:12:07.0219 CET] [debug] scheduling partitioning_finish tests/installation/partitioning_finish.pm
[2018-02-08T08:12:07.0220 CET] [debug] scheduling releasenotes tests/installation/releasenotes.pm
[2018-02-08T08:12:07.0221 CET] [debug] scheduling installer_timezone tests/installation/installer_timezone.pm
[2018-02-08T08:12:07.0221 CET] [debug] scheduling logpackages tests/installation/logpackages.pm
[2018-02-08T08:12:07.0222 CET] [debug] scheduling user_settings tests/installation/user_settings.pm
[2018-02-08T08:12:07.0223 CET] [debug] scheduling user_settings_root tests/installation/user_settings_root.pm
[2018-02-08T08:12:07.0223 CET] [debug] scheduling installation_overview_before tests/installation/installation_overview_before.pm
[2018-02-08T08:12:07.0224 CET] [debug] scheduling select_patterns_and_packages tests/installation/select_patterns_and_packages.pm
[2018-02-08T08:12:07.0225 CET] [debug] scheduling installation_overview tests/installation/installation_overview.pm
[2018-02-08T08:12:07.0226 CET] [debug] scheduling start_install tests/installation/start_install.pm
[2018-02-08T08:12:07.0228 CET] [debug] scheduling install_and_reboot tests/installation/install_and_reboot.pm
[2018-02-08T08:12:07.0229 CET] [debug] scheduling redefine_svirt_domain tests/installation/redefine_svirt_domain.pm
[2018-02-08T08:12:07.0229 CET] [debug] scheduling reconnect_s390 tests/installation/reconnect_s390.pm
[2018-02-08T08:12:07.0230 CET] [debug] scheduling first_boot tests/installation/first_boot.pm
[2018-02-08T08:12:07.0231 CET] [debug] scheduling consoletest_setup tests/console/consoletest_setup.pm
[2018-02-08T08:12:07.0232 CET] [debug] scheduling force_cron_run tests/console/force_cron_run.pm
[2018-02-08T08:12:07.0232 CET] [debug] scheduling textinfo tests/console/textinfo.pm
[2018-02-08T08:12:07.0233 CET] [debug] scheduling hostname tests/console/hostname.pm
[2018-02-08T08:12:07.0233 CET] [debug] scheduling zypper_lr tests/console/zypper_lr.pm
[2018-02-08T08:12:07.0233 CET] [debug] scheduling yast_scc tests/console/yast_scc.pm
[2018-02-08T08:12:07.0234 CET] [debug] scheduling zypper_ref tests/console/zypper_ref.pm
[2018-02-08T08:12:07.0234 CET] [debug] scheduling ncurses tests/console/ncurses.pm
[2018-02-08T08:12:07.0236 CET] [debug] scheduling yast2_lan tests/console/yast2_lan.pm
[2018-02-08T08:12:07.0236 CET] [debug] scheduling curl_https tests/console/curl_https.pm
[2018-02-08T08:12:07.0237 CET] [debug] scheduling zypper_up tests/update/zypper_up.pm
[2018-02-08T08:12:07.0237 CET] [debug] scheduling zypper_in tests/console/zypper_in.pm
[2018-02-08T08:12:07.0238 CET] [debug] scheduling yast2_i tests/console/yast2_i.pm
[2018-02-08T08:12:07.0238 CET] [debug] scheduling yast2_bootloader tests/console/yast2_bootloader.pm
[2018-02-08T08:12:07.0239 CET] [debug] scheduling vim tests/console/vim.pm
[2018-02-08T08:12:07.0239 CET] [debug] scheduling firewall_enabled tests/console/firewall_enabled.pm
[2018-02-08T08:12:07.0240 CET] [debug] scheduling sshd tests/console/sshd.pm
[2018-02-08T08:12:07.0240 CET] [debug] scheduling ssh_cleanup tests/console/ssh_cleanup.pm
[2018-02-08T08:12:07.0241 CET] [debug] scheduling mtab tests/console/mtab.pm
[2018-02-08T08:12:07.0241 CET] [debug] scheduling no_perl_bootloader tests/console/no_perl_bootloader.pm
[2018-02-08T08:12:07.0242 CET] [debug] scheduling http_srv tests/console/http_srv.pm
[2018-02-08T08:12:07.0242 CET] [debug] scheduling mysql_srv tests/console/mysql_srv.pm
[2018-02-08T08:12:07.0243 CET] [debug] scheduling mysql_odbc tests/console/mysql_odbc.pm
[2018-02-08T08:12:07.0243 CET] [debug] scheduling dns_srv tests/console/dns_srv.pm
[2018-02-08T08:12:07.0245 CET] [debug] scheduling postgresql96server tests/console/postgresql96server.pm
[2018-02-08T08:12:07.0245 CET] [debug] scheduling shibboleth tests/console/shibboleth.pm
[2018-02-08T08:12:07.0246 CET] [debug] scheduling apache_ssl tests/console/apache_ssl.pm
[2018-02-08T08:12:07.0246 CET] [debug] scheduling apache_nss tests/console/apache_nss.pm
[2018-02-08T08:12:07.0247 CET] [debug] scheduling zypper_lifecycle tests/console/zypper_lifecycle.pm
[2018-02-08T08:12:07.0248 CET] [debug] scheduling consoletest_finish tests/console/consoletest_finish.pm
[2018-02-08T08:12:07.0248 CET] [debug] Early exit has been requested with _EXIT_AFTER_SCHEDULE. Only evaluating test schedule.
after:
[2018-02-08T08:10:35.0959 CET] [debug] scheduling boot_to_desktop tests/boot/boot_to_desktop.pm
[2018-02-08T08:10:35.0960 CET] [debug] scheduling yast_scc tests/console/yast_scc.pm
[2018-02-08T08:10:35.0961 CET] [debug] Early exit has been requested with _EXIT_AFTER_SCHEDULE. Only evaluating test schedule.
Updated by mgriessmeier about 6 years ago
question to be clarified is:
do we want to do a full install again? or reuse an already created image?
anyway, we need to adjust those lines:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/products/sle/main.pm#L1516 and following
Updated by okurz about 6 years ago
use an already created image. This is what Yi has done last autumn and probably never looked at zkvm
Updated by riafarov about 6 years ago
- Due date changed from 2018-02-13 to 2018-02-27
Please, update the ticket. It looks like workable item.
Updated by JERiveraMoya about 6 years ago
- Status changed from Feedback to In Progress
just waiting for @Matthias to pair up. Using an image didn't work properly, we saw an error in the bootloader test.
Updated by JERiveraMoya about 6 years ago
- Status changed from In Progress to Blocked
I was not able to create an image to continue. There are severe problems with this architecture right now according discussion with @mgriessmeier.
Updated by riafarov about 6 years ago
- Due date changed from 2018-02-27 to 2018-03-13
Updated by okurz about 6 years ago
- Due date changed from 2018-03-13 to 2018-03-27
- Status changed from Blocked to Workable
- Assignee deleted (
JERiveraMoya) - Target version changed from Milestone 14 to Milestone 15
We should use Blocked only when there is an external reference where we follow on with the status.
Updated by riafarov about 6 years ago
- Status changed from Workable to Feedback
Updated by okurz about 6 years ago
- Related to action #27064: [functional][x86_64][s390x][uefi][y][yast][easy] Test suite minimal+base+sdk+proxy_SCC-postreg had a wrong scheduled module list with current version of os-autoinst-distri-opensuse added