From e4ee38416758ab421ec6520a2ce5e1f0bb9b6794 Mon Sep 17 00:00:00 2001 From: Jordi Massaguer Pla Date: Mon, 9 Oct 2023 16:38:12 +0200 Subject: [PATCH] Do not fake-rpm-terminal-channel if no scc credentials When running inside gh actions, we do not have scc credentials. Thus, syncing the fake-rpm-terminal-channel, which has SLE as a base, it produces an error. The fake-rpm-terminal-channel is used for the build host. Signed-off-by: Jordi Massaguer Pla f --- testsuite/features/core/srv_create_activationkey.feature | 1 + .../init_clients/allcli_update_activationkeys.feature | 2 ++ testsuite/features/reposync/srv_sync_fake_channels.feature | 4 ++++ 3 files changed, 7 insertions(+) diff --git a/testsuite/features/core/srv_create_activationkey.feature b/testsuite/features/core/srv_create_activationkey.feature index bb1d2a0e7fc1..cc4408c9581f 100644 --- a/testsuite/features/core/srv_create_activationkey.feature +++ b/testsuite/features/core/srv_create_activationkey.feature @@ -116,6 +116,7 @@ Feature: Create activation keys And I click on "Create Activation Key" Then I should see a "Activation key Build host Key x86_64 has been created" text +@scc_credentials Scenario: Create an activation key for the terminal When I follow the left menu "Systems > Activation Keys" And I follow "Create Key" diff --git a/testsuite/features/init_clients/allcli_update_activationkeys.feature b/testsuite/features/init_clients/allcli_update_activationkeys.feature index 362335ad9bea..fce6514f0997 100644 --- a/testsuite/features/init_clients/allcli_update_activationkeys.feature +++ b/testsuite/features/init_clients/allcli_update_activationkeys.feature @@ -190,6 +190,7 @@ Feature: Update activation keys Then I should see a "Activation key Terminal Key x86_64 has been modified" text @susemanager +@scc_credentials Scenario: Update terminal key with normal SUSE fake channel When I follow the left menu "Systems > Activation Keys" And I follow "Terminal Key x86_64" in the content area @@ -199,6 +200,7 @@ Feature: Update activation keys Then I should see a "Activation key Terminal Key x86_64 has been modified" text @uyuni +@scc_credentials Scenario: Update terminal key with specific fake channel When I follow the left menu "Systems > Activation Keys" And I follow "Terminal Key x86_64" in the content area diff --git a/testsuite/features/reposync/srv_sync_fake_channels.feature b/testsuite/features/reposync/srv_sync_fake_channels.feature index 56a4c924fd16..cb421102567d 100644 --- a/testsuite/features/reposync/srv_sync_fake_channels.feature +++ b/testsuite/features/reposync/srv_sync_fake_channels.feature @@ -49,6 +49,7 @@ Feature: Prepare fake SUSE channels And solver file for "fake-rpm-suse-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm" @uyuni +@scc_credentials Scenario: Add the terminal child channel to the base product channel When I follow the left menu "Software > Manage > Channels" And I follow "Create Channel" @@ -62,6 +63,7 @@ Feature: Prepare fake SUSE channels Then I should see a "Channel Fake-RPM-Terminal-Channel created." text @uyuni +@scc_credentials Scenario: Add the repository to the terminal child channel When I follow the left menu "Software > Manage > Channels" And I follow "Fake-RPM-Terminal-Channel" @@ -74,6 +76,7 @@ Feature: Prepare fake SUSE channels Then I should see a "Fake-RPM-Terminal-Channel repository information was successfully updated" text @uyuni +@scc_credentials Scenario: Synchronize the repository in the terminal channel When I enable source package syncing And I follow the left menu "Software > Manage > Channels" @@ -87,6 +90,7 @@ Feature: Prepare fake SUSE channels And I disable source package syncing @uyuni +@scc_credentials Scenario: Verify state of Fake-RPM-Terminal-Channel custom channel Then "orion-dummy-1.1-1.1.x86_64.rpm" package should have been stored And solver file for "fake-rpm-terminal-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm"