Run extension registration independently by the initial main image registration status #293
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…gistration status Both update registercloudguest and enable requested additional extensions independently by the initial registration state: so both for BYOS and PAYG. It is possible as at the playbook point that enable extensions, the image is already registered. Fix a couple of lint errors and improve the inline documentation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Both update registercloudguest and enable requested additional extensions independently by the initial registration state: so both for BYOS and PAYG. It is possible as at the playbook point that enable extensions, the image is already registered.
Fix a couple of lint errors and improve the inline documentation.
Related ticket: https://jira.suse.com/browse/TEAM-9808
Verification
qesap regression
Both VR are using os-autoinst/os-autoinst-distri-opensuse#20624 and are triggered with
BYOS
Highlights:
[Check for SUSEConnect binary presence]TASK [Ensure cloud-regionsrv-client is on latest version.]is executedTASK [Add additional authenticated modules]BYOS with LTSS-ES
sle-12-SP5-Qesap-Azure-Byos-x86_64-Buildmpagot_VR-qesap_azure_saptune_test
PAYG
Important file is http://openqaworker15.qa.suse.cz/tests/302830/logfile?filename=deploy-ansible.registration.log.txt
Highlights:
Add additional authenticated modules. It could be external issue but at least it is wrongly trying registering LTSS with SUSEConnect in place ofregistercloudguest.HanaSR
All of them without LTSS
BYOS
sle-15-SP6-HanaSr-Aws-Byos-x86_64-Build15-SP6_2024-11-14T03:03:15Z-hanasr_aws_test_fencing_sbd_crash ec2_r4.8xlarge
-> http://openqaworker15.qa.suse.cz/tests/302831 🟢
sle-15-SP6-HanaSr-Azure-Byos-x86_64-Build15-SP6_2024-11-14T03:03:15Z-hanasr_azure_test_saptune_msi az_Standard_E4s_v3
[vmhana02] SAP Hana cluster: Join the cluster creates=/etc/corosync/corosync.conf, _raw_params=crm cluster join -y -c vmhana01 -i eth0sle-15-SP6-HanaSr-Gcp-Byos-x86_64-Build15-SP6_2024-11-14T03:03:15Z-hanasr_gcp_test_fencing_sbd_crash gce_n1_highmem_8
-> http://openqaworker15.qa.suse.cz/tests/302833 🟢 fails later in Crash_site_a-primary
sle-12-SP5-HanaSr-Azure-Byos-x86_64-Build12-SP5_2024-11-14T03:03:15Z-hanasr_azure_test_msi az_Standard_E4s_v3
-> http://openqaworker15.qa.suse.cz/tests/302835
PAYG