action #28624
closed[CaaSP] fails in register_and_check
0%
Description
Observation¶
openQA test in scenario caasp-2.0-CaaSP-DVD-Incidents-x86_64-QAM-CaaSP-autoyast1@qam-caasp_x86_64 fails in
register_and_check
Reproducible¶
Fails since (at least) Build :5745:grub2.1511980511 (current job)
Expected result¶
Last good: :5662:zypper.1511980438 (or more recent)
Further details¶
Always latest result in this scenario: latest
In the logs I can clearly see: dockerd[2523]: time="2017-11-29T19:49:49.319271599Z" level=warning msg="SUSE:secrets :: dangling symlink: /etc/SUSEConnect"
However, I am not sure if there's a real problem with the symlink or a problem with the internet connection to SCC.
I would propose to enhance the test to check:
ls -l /etc/products.d/baseproduct | grep CAASP.prod
lrwxrwxrwx 1 root root 10 Nov 10 13:38 /etc/products.d/baseproduct -> CAASP.prod
Also maybe running:
admin:~ # zypper products -i | grep CAASP
i+ | SUSE-CAASP-ALL-Pool | CAASP | SUSE Container as a Service Platform 2.0 | 2.0-0 | x86_64 | Yes
Also, if this fails: assert_script_run 'SUSEConnect --status-text | grep -o "Status: ACTIVE"';
I would propose to run: assert_script_run SUSEConnect --status-text --debug
and upload this log.
What do you think?
Updated by pgeorgiadis over 6 years ago
Happened again today: https://openqa.suse.de/tests/1292527#step/register_and_check/4
Updated by mkravec over 6 years ago
Quick first step: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4015
Updated by mkravec over 6 years ago
Your test uses incorrect settings:
- you can use REGISTER=installation ONLY for ISO manual installations, not autoyast
- autoyast nodes are registered automatically from profile or with REGISTER=suseconnect afterwards
Updated by pgeorgiadis over 6 years ago
So if I understood correctly:
Admin node:
- REGCODE
- REGISTER
All the other autoyast nodes (k8s master and workers) the need node of those. Right?
Updated by mkravec over 6 years ago
REGCODE - set it on medium for simplicity, it's not used if REGISTER= is not set
REGISTER=installation on admin node (because of bsc#1071681)
REGISTER=installation/suseconnect on YaST installations
REGISTER=??? it needs more logic for autoyast, I will look at it today - they should auto-detect registration from admin node
Updated by mkravec over 6 years ago
We should be able to debug it with y2log - https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4034
Updated by mkravec about 6 years ago
Is this issue still valid or we can close it?
Updated by pgeorgiadis about 6 years ago
- Status changed from New to Resolved
It's been quite a while when this bug did not happen. I guess it's safe to mark this done.