|
Bugzilla – Full Text Bug Listing |
| Summary: | [Build 44.1] openQA test fails in system_prepare - SUSEConnect register product returned with 'Credential file is missing' | ||
|---|---|---|---|
| Product: | [openSUSE] PUBLIC SUSE Linux Enterprise Server 15 SP6 | Reporter: | Lemon Li <leli> |
| Component: | Registration | Assignee: | SCC Bugs <scc-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Hernan Schmidt <hschmidt> |
| Severity: | Normal | ||
| Priority: | P1 - Urgent | CC: | jeriveramoya, leli, rtsvetkov, swayammitra.tripathy, tschmidt |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| URL: | https://openqa.suse.de/tests/13005355/modules/system_prepare/steps/27 | ||
| Whiteboard: | |||
| Found By: | openQA | Services Priority: | |
| Business Priority: | Blocker: | Yes | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | y2 log | ||
|
Description
Lemon Li
2023-12-12 03:18:15 UTC
Could you please change that "SUSEConnect" call to include "--debug", so we can see a bit better why it fails on missing credentials file? Also if possible check the file + permissions of /etc/zypp/credentials.d/SCCcredentials. (In reply to Thomas Schmidt from comment #1) > Could you please change that "SUSEConnect" call to include "--debug", so we > can see a bit better why it fails on missing credentials file? > Also if possible check the file + permissions of > /etc/zypp/credentials.d/SCCcredentials. I used wrong for assert_script_run so stopped at checking access, http://openqa.nue.suse.com/tests/13095475#step/system_prepare/26 So it do not have permission to access /etc/zypp/credentials.d/SCCcredentials. I'm running a new run for '--debug', http://openqa.nue.suse.com/tests/13096075#live (In reply to Thomas Schmidt from comment #1) > Could you please change that "SUSEConnect" call to include "--debug", so we > can see a bit better why it fails on missing credentials file? > Also if possible check the file + permissions of > /etc/zypp/credentials.d/SCCcredentials. The output of SUSEConnect with "--debug" is here http://openqa.nue.suse.com/tests/13096075#step/system_prepare/35 Please ask me if more info needed. Thanks. It looks like the initial SLE 12 system was installed without SUSEConnect, all products got installed from disk. Then, after the migration suseconnect gets called. Is that intentional? (In reply to Thomas Schmidt from comment #4) > It looks like the initial SLE 12 system was installed without SUSEConnect, > all products got installed from disk. Then, after the migration suseconnect > gets called. Is that intentional? It seems before migration and update patch this registration works : https://openqa.suse.de/tests/13005355#step/patch_sle/32 I guess there is something changed for suseconnect-ng which do something during the update of patch. I will try to run the SUSEConnect registration after update patch to have a look. This issue happened since build 42.1. (In reply to Thomas Schmidt from comment #4) > It looks like the initial SLE 12 system was installed without SUSEConnect, > all products got installed from disk. Then, after the migration suseconnect > gets called. Is that intentional? The test boot from the installed system(qcow), should with SUSEConnect since before update patch the registration works. It seems after patching on base system, the SUSEConnect registration still work http://openqa.nue.suse.com/tests/13121058#step/patch_sle/174 I'm not sure there is an issue with SUSEConnect... Here's what I think is happening: The SCC registration is getting skipped during the upgrade: https://openqa.suse.de/tests/13005355#step/scc_registration/1 Maybe Yast doesn't copy registration data in that case. Then, in the migrated 15SP6 system, the test calls "SUSEConnect -p SLES/${VERSION_ID}/${CPU} -r ... " which doesn't seem right. To activate the base SLES product, no '-p' parameter is needed, it's detected automatically. (In reply to Thomas Schmidt from comment #8) > I'm not sure there is an issue with SUSEConnect... Here's what I think is > happening: > > The SCC registration is getting skipped during the upgrade: > https://openqa.suse.de/tests/13005355#step/scc_registration/1 > > Maybe Yast doesn't copy registration data in that case. Maybe need Yast developer to involve to analyze it? > > Then, in the migrated 15SP6 system, the test calls "SUSEConnect -p > SLES/${VERSION_ID}/${CPU} -r ... " which doesn't seem right. To activate the > base SLES product, no '-p' parameter is needed, it's detected automatically. I will try to update test code for this, it seems we continue use '-p' on SLE12* and remove '-p' on SLE15*, not sure but I will try to run more VR on different versions. (In reply to Ming Li from comment #9) > (In reply to Thomas Schmidt from comment #8) > > I'm not sure there is an issue with SUSEConnect... Here's what I think is > > happening: > > > > The SCC registration is getting skipped during the upgrade: > > https://openqa.suse.de/tests/13005355#step/scc_registration/1 > > > > Maybe Yast doesn't copy registration data in that case. > > Maybe need Yast developer to involve to analyze it? > > > > Then, in the migrated 15SP6 system, the test calls "SUSEConnect -p > > SLES/${VERSION_ID}/${CPU} -r ... " which doesn't seem right. To activate the > > base SLES product, no '-p' parameter is needed, it's detected automatically. > > I will try to update test code for this, it seems we continue use '-p' on > SLE12* and remove '-p' on SLE15*, not sure but I will try to run more VR on > different versions. I will run VR jobs after Proxy SCC recovered. The test failed for not supported parameter when removed '-p', http://openqa.nue.suse.com/tests/13240335#step/system_prepare/36 [2024-01-12T12:08:23.059032+01:00] [debug] [pid:81079] <<< testapi::type_string(string="SUSEConnect SLES/\${VERSION_ID}/\${CPU} -r 72d93c8cb933614a --url http://all-45.1.proxy.scc.suse.de --debug", max_interval=250, wait_screen_change=0, wait_still_screen=0, timeout=30, similarity_level=47) Please not just drop the '-p', but also it's value 'SLES/\${VERSION_ID}/\${CPU}' else the command is invalid.
(In reply to Thomas Schmidt from comment #12) > Please not just drop the '-p', but also it's value > 'SLES/\${VERSION_ID}/\${CPU}' else the command is invalid. Yes, it's my fault. Without '-p' for product 'SLES' then it passed, http://openqa.nue.suse.com/tests/13258305#step/system_prepare/29 I will create a ticket to update test code to follow it. Thanks. Filed ticket https://progress.opensuse.org/issues/153589 SUSE-RU-2024:0176-1: An update that has two fixes can now be installed. Category: recommended (critical) Bug References: 1217961, 1218649 Sources used: SUSE Linux Enterprise Micro 5.2 (src): suseconnect-ng-1.6.0~git0.31371c8-150300.3.6.1 SUSE Linux Enterprise Micro for Rancher 5.2 (src): suseconnect-ng-1.6.0~git0.31371c8-150300.3.6.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. SUSE-RU-2024:0175-1: An update that has two fixes can now be installed. Category: recommended (critical) Bug References: 1217961, 1218649 Sources used: SUSE Linux Enterprise Micro 5.1 (src): suseconnect-ng-1.6.0~git0.31371c8-150300.3.11.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. SUSE-RU-2024:0174-1: An update that has three fixes can now be installed. Category: recommended (critical) Bug References: 1217961, 1218364, 1218649 Sources used: SUSE Linux Enterprise High Performance Computing 12 SP5 (src): suseconnect-ng-1.6.0~git0.31371c8-3.6.1 SUSE Linux Enterprise Server 12 SP5 (src): suseconnect-ng-1.6.0~git0.31371c8-3.6.1 SUSE Linux Enterprise Server for SAP Applications 12 SP5 (src): suseconnect-ng-1.6.0~git0.31371c8-3.6.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. SUSE-RU-2024:0173-1: An update that has two fixes can now be installed. Category: recommended (critical) Bug References: 1217961, 1218649 Sources used: Basesystem Module 15-SP5 (src): suseconnect-ng-1.6.0~git0.31371c8-150500.3.12.1 openSUSE Leap 15.5 (src): suseconnect-ng-1.6.0~git0.31371c8-150500.3.12.1 SUSE Linux Enterprise Micro 5.5 (src): suseconnect-ng-1.6.0~git0.31371c8-150500.3.12.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. SUSE-RU-2024:0189-1: An update that has two fixes can now be installed. Category: recommended (critical) Bug References: 1217961, 1218649 Sources used: SUSE Linux Enterprise High Performance Computing 15 SP1 LTSS 15-SP1 (src): suseconnect-ng-1.6.0~git0.31371c8-150100.3.15.1 SUSE Linux Enterprise High Performance Computing 15 SP2 LTSS 15-SP2 (src): suseconnect-ng-1.6.0~git0.31371c8-150100.3.15.1 SUSE Linux Enterprise High Performance Computing LTSS 15 SP3 (src): suseconnect-ng-1.6.0~git0.31371c8-150100.3.15.1 SUSE Linux Enterprise Server 15 SP1 LTSS 15-SP1 (src): suseconnect-ng-1.6.0~git0.31371c8-150100.3.15.1 SUSE Linux Enterprise Server 15 SP2 LTSS 15-SP2 (src): suseconnect-ng-1.6.0~git0.31371c8-150100.3.15.1 SUSE Linux Enterprise Server 15 SP3 LTSS 15-SP3 (src): suseconnect-ng-1.6.0~git0.31371c8-150100.3.15.1 SUSE Linux Enterprise Server for SAP Applications 15 SP1 (src): suseconnect-ng-1.6.0~git0.31371c8-150100.3.15.1 SUSE Linux Enterprise Server for SAP Applications 15 SP2 (src): suseconnect-ng-1.6.0~git0.31371c8-150100.3.15.1 SUSE Linux Enterprise Server for SAP Applications 15 SP3 (src): suseconnect-ng-1.6.0~git0.31371c8-150100.3.15.1 SUSE Enterprise Storage 7.1 (src): suseconnect-ng-1.6.0~git0.31371c8-150100.3.15.1 SUSE CaaS Platform 4.0 (src): suseconnect-ng-1.6.0~git0.31371c8-150100.3.15.1 SUSE Linux Enterprise Server 15 SP1 (src): suseconnect-ng-1.6.0~git0.31371c8-150100.3.15.1 SUSE Linux Enterprise Server 15 SP2 (src): suseconnect-ng-1.6.0~git0.31371c8-150100.3.15.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. SUSE-RU-2024:0188-1: An update that has two fixes can now be installed. Category: recommended (critical) Bug References: 1217961, 1218649 Sources used: openSUSE Leap 15.4 (src): suseconnect-ng-1.6.0~git0.31371c8-150400.3.22.1 openSUSE Leap Micro 5.3 (src): suseconnect-ng-1.6.0~git0.31371c8-150400.3.22.1 openSUSE Leap Micro 5.4 (src): suseconnect-ng-1.6.0~git0.31371c8-150400.3.22.1 SUSE Linux Enterprise Micro for Rancher 5.3 (src): suseconnect-ng-1.6.0~git0.31371c8-150400.3.22.1 SUSE Linux Enterprise Micro 5.3 (src): suseconnect-ng-1.6.0~git0.31371c8-150400.3.22.1 SUSE Linux Enterprise Micro for Rancher 5.4 (src): suseconnect-ng-1.6.0~git0.31371c8-150400.3.22.1 SUSE Linux Enterprise Micro 5.4 (src): suseconnect-ng-1.6.0~git0.31371c8-150400.3.22.1 SUSE Linux Enterprise High Performance Computing ESPOS 15 SP4 (src): suseconnect-ng-1.6.0~git0.31371c8-150400.3.22.1 SUSE Linux Enterprise High Performance Computing LTSS 15 SP4 (src): suseconnect-ng-1.6.0~git0.31371c8-150400.3.22.1 SUSE Linux Enterprise Desktop 15 SP4 LTSS 15-SP4 (src): suseconnect-ng-1.6.0~git0.31371c8-150400.3.22.1 SUSE Linux Enterprise Server 15 SP4 LTSS 15-SP4 (src): suseconnect-ng-1.6.0~git0.31371c8-150400.3.22.1 SUSE Linux Enterprise Server for SAP Applications 15 SP4 (src): suseconnect-ng-1.6.0~git0.31371c8-150400.3.22.1 SUSE Manager Proxy 4.3 (src): suseconnect-ng-1.6.0~git0.31371c8-150400.3.22.1 SUSE Manager Retail Branch Server 4.3 (src): suseconnect-ng-1.6.0~git0.31371c8-150400.3.22.1 SUSE Manager Server 4.3 (src): suseconnect-ng-1.6.0~git0.31371c8-150400.3.22.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. Hi, Thomas, besides the 15SP6 do we need to remove '-p' parameter when activate the base product on migrated system such as 15SP* or 12SP*? It's unnecessary + undocumented to use the -p parameter to activate the base product. But it should still work, and with 1.6.0 you should not run into this issue. Hello SSC Team, Any Update on this issue Not from our side, according to comment#13 it works when changing the command. It seems the fix is not in build 50.2, the suseconnect-ng version is still 1.4.0 http://openqa.suse.de/tests/13449052#step/system_prepare/8. I used a branch to recover the original code to activate SLES via "SUSEConnect -p *" and it failed as before http://openqa.suse.de/tests/13449052#step/system_prepare/35 Same for another SAP migration test, http://openqa.nue.suse.com/tests/13449054#step/migrate_sles_to_sles4sap/4 This is an autogenerated message for OBS integration: This bug (1217961) was mentioned in https://build.opensuse.org/request/show/1146892 Factory / suseconnect-ng Please re-test with the latest suseconnect-ng submission 1.7.0. In the logs we still see suseconnect-ng-1.4.0 https://openqa.suse.de/tests/13549585/file/migrate_sles_to_sles4sap-y2logs.tar.xz who could help to bring 1.7.0 to SLES 15 SP6 Public Beta? We found the latest version(1.7) of suseconnect-ng already in build 58.1(https://openqa.suse.de/tests/13602007#step/system_prepare/8), and the test passed https://openqa.suse.de/tests/13602007#step/system_prepare/27. The migration from SLES15SP6 to SLES4SAP passed also, https://openqa.suse.de/tests/13584099#step/migrate_sles_to_sles4sap/38. Thanks. Closing according to comment#33 A SR mentioning this bug was successfully integrated into Build 58.1. Please, if needed, set it to RESOLVED FIXED for QE to verify it. |