Force the generation of bootstrap repositories in CT

testsuite/features/init_clients/buildhost_bootstrap.feature

@@ -4,6 +4,9 @@
 @buildhost
 Feature: Bootstrap a build host via the GUI
 
+  Scenario: Clean up sumaform leftovers on build host
+    When I perform a full salt minion cleanup on "build_host"
+
   Scenario: Log in as admin user
     Given I am authorized for the "Admin" section
 

testsuite/features/init_clients/min_virthost.feature

@@ -7,6 +7,9 @@
 @virthost_kvm
 Feature: Bootstrap a virtualization host minion and set it up for virtualization
 
+  Scenario: Clean up sumaform leftovers on KVM virtual host
+    When I perform a full salt minion cleanup on "kvm_server"
+
   Scenario: Log in as admin user
     Given I am authorized for the "Admin" section
 

testsuite/features/init_clients/sle_minion.feature

@@ -4,6 +4,9 @@
 @sle_minion
 Feature: Bootstrap a Salt minion via the GUI
 
+  Scenario: Clean up sumaform leftovers on SLES minion
+    When I perform a full salt minion cleanup on "sle_minion"
+
   Scenario: Log in as admin user
     Given I am authorized for the "Admin" section
 

testsuite/features/init_clients/sle_ssh_minion.feature

@@ -4,6 +4,9 @@
 @ssh_minion
 Feature: Bootstrap a Salt host managed via salt-ssh
 
+  Scenario: Clean up sumaform leftovers on SLES SSH minion
+    When I perform a full salt minion cleanup on "ssh_minion"
+
   Scenario: Log in as admin user
     Given I am authorized for the "Admin" section
 

testsuite/features/reposync/srv_create_bootstrap_repositories.feature

@@ -0,0 +1,10 @@
+# Copyright (c) 2021-2024 SUSE LLC
+# Licensed under the terms of the MIT license.
+
+Feature: Create bootstrap repositories
+  In order to be able to enroll clients with MU repositories
+  As the system administrator
+  I create all bootstrap repos with --with-custom-channels option
+
+  Scenario: Create the bootstrap repositories including custom channels
+    When I create the bootstrap repositories including custom channels

testsuite/features/step_definitions/command_steps.rb

@@ -1076,6 +1076,11 @@
   get_target('server').run(cmd)
 end
 
+When(/^I create the bootstrap repositories including custom channels$/) do
+  get_target('server').wait_while_process_running('mgr-create-bootstrap-repo')
+  get_target('server').run('mgr-create-bootstrap-repo --auto --force --with-custom-channels', check_errors: false, verbose: true)
+end
+
 When(/^I install "([^"]*)" product on the proxy$/) do |product|
   out, = get_target('proxy').run("zypper ref && zypper --non-interactive install --auto-agree-with-licenses --force-resolution -t product #{product}")
   log "Installed #{product} product: #{out}"

testsuite/run_sets/reference_reposync.yml

@@ -23,6 +23,7 @@
 
 # Special reference repo sync
 - features/reposync/reference_srv_sync_products_extra.feature
+- features/reposync/srv_create_bootstrap_repositories.feature
 #- features/reposync/reference_srv_check_reposync.feature
 
 ## Channels and Product synchronization features END ###

testsuite/run_sets/reposync.yml

@@ -19,4 +19,5 @@
 # Activation keys can only be created after products and channels are synced
 - features/reposync/srv_create_activationkey.feature
 - features/reposync/allcli_update_activationkeys.feature
+- features/reposync/srv_create_bootstrap_repositories.feature
 ## Channels and Product synchronization features END ###