Cucumber Feature Report

All Scenarios

201

Passed Scenarios

162

Failed Scenarios

0

Skipped Scenarios

39

Execution Time: 97m 23s 159ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 44s 964ms 10 2

In order to use the product
I want to be sure to use a sane environment

Scenario:
The server is healthy

11s 623ms 19

Then "server" should have a FQDN 379ms

And reverse resolution should work for "server" 623ms

And the clock from "server" should be exact 684ms

And service "apache2" is enabled on "server" 614ms

And service "apache2" is active on "server" 629ms

And service "cobblerd" is enabled on "server" 652ms

And service "cobblerd" is active on "server" 618ms

And service "rhn-search" is enabled on "server" 626ms

And service "rhn-search" is active on "server" 617ms

And service "salt-api" is enabled on "server" 614ms

And service "salt-api" is active on "server" 615ms

And service "salt-master" is enabled on "server" 619ms

And service "salt-master" is active on "server" 613ms

And service "taskomatic" is enabled on "server" 609ms

And service "taskomatic" is active on "server" 618ms

And socket "tftp" is enabled on "server" 617ms

And socket "tftp" is active on "server" 626ms

And service "tomcat" is enabled on "server" 626ms

And service "tomcat" is active on "server" 615ms

@proxy

Scenario:
The proxy is healthy

4s 528ms 4

Then "proxy" should have a FQDN 3s 34ms

And reverse resolution should work for "proxy" 279ms

And "proxy" should communicate with the server using public interface 942ms

And the clock from "proxy" should be exact 271ms

@sle_minion

Scenario:
The minion is healthy

6s 542ms 4

Then "sle_minion" should have a FQDN 4s 575ms

And reverse resolution should work for "sle_minion" 452ms

And "sle_minion" should communicate with the server using public interface 1s 95ms

And the clock from "sle_minion" should be exact 418ms

@build_host

Scenario:
The build host is healthy

4s 565ms 4

Then "build_host" should have a FQDN 3s 162ms

And reverse resolution should work for "build_host" 250ms

And "build_host" should communicate with the server using public interface 910ms

And the clock from "build_host" should be exact 242ms

@ssh_minion

Scenario:
The SSH minion is healthy

6s 646ms 4

Then "ssh_minion" should have a FQDN 4s 683ms

And reverse resolution should work for "ssh_minion" 470ms

And "ssh_minion" should communicate with the server using public interface 1s 84ms

And the clock from "ssh_minion" should be exact 407ms

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 211ms 4

Then "rhlike_minion" should have a FQDN 2s 18ms

And reverse resolution should work for "rhlike_minion" 205ms

And "rhlike_minion" should communicate with the server using public interface 806ms

And the clock from "rhlike_minion" should be exact 180ms

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 923ms 4

Then "deblike_minion" should have a FQDN 4s 653ms

And reverse resolution should work for "deblike_minion" 216ms

And "deblike_minion" should communicate with the server using public interface 841ms

And the clock from "deblike_minion" should be exact 212ms

@skip_if_cloud

Scenario:
The external resources can be reached

< 1ms 3

Then it should be possible to reach the test packages 0s

And it should be possible to reach the build sources 0s

And it should be possible to reach the Docker profiles 0s

@server_http_proxy

Scenario:
The HTTP proxy is working

< 1ms 1

Then it should be possible to use the HTTP proxy 0s

@auth_registry

Scenario:
The registry with authentication is healthy

652ms 1

Then it should be possible to reach the authenticated registry 652ms

@no_auth_registry

Scenario:
The registry without authentication is healthy

635ms 1

Then it should be possible to reach the not authenticated registry 635ms

@custom_download_endpoint

Scenario:
The custom download endpoint is working

633ms 1

Then it should be possible to use the custom download endpoint 633ms

Feature:Very first settings 47s 957ms 6 2

In order to use the product
As the admin user
I want to create the organisation, the first users and set the HTTP proxy

Scenario:
Cleanup Salt files

660ms 1

When I run "rm -Rf /srv/salt/*" on "server" 660ms

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

Given I access the host the first time 0s

When I go to the home page 0s

And I enter "SUSE Test" as "orgName" 0s

And I enter "admin" as "login" 0s

And I enter "admin" as "desiredpassword" 0s

And I enter "admin" as "desiredpasswordConfirm" 0s

And I select "Mr." from "prefix" 0s

And I enter "Admin" as "firstNames" 0s

And I enter "Admin" as "lastName" 0s

And I enter "galaxy-noise@localhost" as "email" 0s

And I click on "Create Organization" 0s

Then I am logged in 0s

Scenario:
Log in as admin user

39s 716ms 1

Given I am authorized for the "Admin" section 39s 716ms

Scenario:
Wait for refresh of list of products to finish

3s 455ms 1

When I wait until mgr-sync refresh is finished 3s 455ms

Scenario:
Create testing username

2s 220ms 12

When I follow the left menu "Users > User List > Active" 191ms

And I follow "Create User" 588ms

And I enter "testing" as "login" 69ms

And I enter "testing" as "desiredpassword" 67ms

And I enter "testing" as "desiredpasswordConfirm" 76ms

And I select "Mr." from "prefix" 48ms

And I enter "Test" as "firstNames" 60ms

And I enter "User" as "lastName" 59ms

And I enter "galaxy-noise@localhost" as "email" 102ms

And I click on "Create Login" 875ms

Then I should see a "Account testing created, login information sent to galaxy-noise@localhost" text 69ms

And I should see a "testing" link 12ms

Scenario:
Grant testing user administrative priviledges

1s 144ms 10

When I follow the left menu "Users > User List > Active" 74ms

And I follow "testing" 452ms

And I check "role_org_admin" 84ms

And I check "role_system_group_admin" 78ms

And I check "role_channel_admin" 76ms

And I check "role_activation_key_admin" 77ms

And I check "role_config_admin" 76ms

And I click on "Update" 57ms

Then I should see a "User information updated" text 88ms

And I should see a "testing" text 76ms

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

When I follow the left menu "Admin > Setup Wizard > HTTP Proxy" 0s

Then I should see a "HTTP Proxy Hostname" text 0s

And I should see a "HTTP Proxy Username" text 0s

And I should see a "HTTP Proxy Password" text 0s

When I enter the address of the HTTP proxy as "HTTP Proxy Hostname" 0s

And I enter "suma3" as "HTTP Proxy Username" 0s

And I enter "P4$$w/ord With%and&" as "HTTP Proxy Password" 0s

And I click on "Save and Verify" 0s

Then HTTP proxy verification should have succeeded 0s

Scenario:
Detect latest Salt changes on the server

759ms 1

* Mon Jan 19 2026 Marek Czernek
- Make syntax in httputil_test compatible with Python 3.6
- Fix KeyError in postgres module with PostgreSQL 17 (bsc#1254325)
- Added:
* fix-tornado-s-httputil_test-syntax-for-python-3.6.patch
* backport-add-maintain-m-privilege-to-postgres-module.patch

* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
- Speed up wheel key.finger call (bsc#1240532)
- Add security patches (bsc#1254903,bsc#1254905,bsc#1254904)
- Simplify and speed up utils.find_json function (bsc#1246130)
- Added:
* use-internal-salt.utils.pkg.deb-classes-instead-of-a.patch
* speedup-wheel-key.finger-call-bsc-1240532-713.patch

When I query latest Salt changes on "server" 759ms

Feature:Turn "disable_local_repos" feature on highstate off 3s 730ms 1

In order to test the product using shortcuts
As root user
I want to add pillar data to disable that feature

Scenario:
Create custom pillar to turn off "disable_local_repos"

3s 730ms 1

When I turn off disable_local_repos for all clients 3s 730ms

Feature:Organization credentials in the Setup Wizard < 1ms 1

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Organization Credentials" 0s

And I ask to add new credentials 0s

And I enter the SCC credentials 0s

And I click on "Save" 0s

And I wait until the SCC credentials are valid 0s

Feature:Change personal preferences 4s 382ms 2

In order to set up my personal preferences
As admin
I want to navigate through "Home" submenus changing some settings

Scenario:
Change page size to 100 per page in admin user

1s 339ms 5

Given I am authorized as "admin" with password "admin" 463ms

When I follow the left menu "Home > My Preferences" 66ms

And I select "100" from "pagesize" 66ms

And I click on "Save Preferences" 639ms

Then I should see a "Preferences modified" text 103ms

Scenario:
Change page size to 100 per page in testing user

3s 43ms 5

Given I am authorized as "testing" with password "testing" 2s 241ms

When I follow the left menu "Home > My Preferences" 58ms

And I select "100" from "pagesize" 49ms

And I click on "Save Preferences" 593ms

Then I should see a "Preferences modified" text 100ms

Feature:Prepare server for using Kiwi 3s 877ms 1

Scenario:
Create a Kiwi user with image administrators rights

3s 877ms 2

New user kiwikiwi created with roles: image_admin

Given I am authorized for the "Admin" section 2s 8ms

When I create a user with name "kiwikiwi" and password "kiwikiwi" with roles "image_admin" 1s 868ms

Feature:Prepare server for using Docker 5s 222ms 2

Scenario:
Create a Docker user with image administrators rights

2s 214ms 2

New user docker created with roles: image_admin

Given I am authorized for the "Admin" section 443ms

When I create a user with name "docker" and password "docker" with roles "image_admin" 1s 771ms

@no_auth_registry

Scenario:
Create an image store without credentials

3s 7ms 7

When I follow the left menu "Images > Stores" 116ms

And I follow "Create" 517ms

And I enter "galaxy-registry" as "label" 99ms

And I enter the URI of the registry as "uri" 138ms

And I click on "create-btn" 82ms

Then I wait until table row contains a "galaxy-registry" text 1s 982ms

And I should see a "Items 1 - 1 of 1" text 70ms

Feature:Do not let Taskomatic tasks interfere with our CI tests 46s 663ms 3

Scenario:
Log in as admin user

37s 528ms 1

Given I am authorized for the "Admin" section 37s 528ms

Scenario:
Disable scheduled reposyncs

4s 560ms 5

When I follow the left menu "Admin > Task Schedules" 140ms

And I follow "mgr-sync-refresh-default" 1s 255ms

And I choose "disabled" 64ms

And I click on "Update Schedule" 1s 453ms

And I click on "Disable Schedule" 1s 647ms

Scenario:
Disable scheduled Cobbler syncs

4s 573ms 5

When I follow the left menu "Admin > Task Schedules" 63ms

And I follow "cobbler-sync-default" 1s 251ms

And I choose "disabled" 49ms

And I click on "Update Schedule" 1s 541ms

And I click on "Disable Schedule" 1s 666ms

@scc_credentials
Feature:List available channels and enable them 1m 38s 737ms 5 1

In order to use software channels
As root user
I want to list available channels and enable them

Scenario:
List available channels

32s 907ms 5

When I refresh SCC 30s 630ms

And I execute mgr-sync "list channels -e" with user "admin" and password "admin" 2s 277ms

Then I should get "[ ] SLE-Product-SLES15-SP7-Pool for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-pool-x86_64]" < 1ms

And I should get " [ ] SLE-Product-SLES15-SP7-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-updates-x86_64]" < 1ms

And I should get " [ ] SLE15-SP7-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle15-sp7-installer-updates-x86_64]" < 1ms

Scenario:
List available mandatory channels

1s 471ms 4

When I execute mgr-sync "list channels -e --no-optional" 1s 471ms

Then I should get "[ ] SLE-Product-SLES15-SP7-Pool for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-pool-x86_64]" < 1ms

And I should get " [ ] SLE-Product-SLES15-SP7-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-updates-x86_64]" < 1ms

And I shouldn't get " [ ] SLE15-SP7-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle15-sp7-installer-updates-x86_64]" < 1ms

Scenario:
List Server product

1s 470ms 2

When I execute mgr-sync "list products" 1s 470ms

Then I should get "[ ] SUSE Linux Enterprise Server 15 SP7 x86_64" < 1ms

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

When I execute mgr-sync "list products --expand" 0s

Then I should get "[ ] SUSE Linux Enterprise Server 15 SP7 x86_64" 0s

And I should get " [ ] SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" 0s

And I should get " [ ] SUSE Multi-Linux Manager Proxy Extension for SLE 5.1 x86_64" 0s

And I should get " [ ] (R) SUSE Multi-Linux Manager Client Tools for SUSE Liberty Linux 7, RHEL and clones 7 x86_64" 0s

And I should get " [ ] (R) SUSE Multi-Linux Manager Client Tools for SLE 15 x86_64" 0s

Scenario:
List products with filter

1s 458ms 4

When I execute mgr-sync "list products --expand --filter x86_64" 1s 458ms

Then I should get "[ ] SUSE Linux Enterprise Server 15 SP7 x86_64" < 1ms

And I shouldn't get "ppc64" < 1ms

And I shouldn't get "s390x" < 1ms

Scenario:
Let mgr-sync time out

1m 1s 430ms 3

When I remove the mgr-sync cache file 665ms

And I execute mgr-sync refresh 1m 764ms

Then I should get "Timeout. No user input for 60 seconds. Exiting..." < 1ms

Feature:Synchronize products in the products page of the Setup Wizard 65m 45s 150ms 8 9

@scc_credentials

Scenario:
Refresh SCC

27s 847ms 1

When I refresh SCC 27s 847ms

@scc_credentials

Scenario:
Let the products page appear

2s 794ms 6

Given I am authorized for the "Admin" section 488ms

When I follow the left menu "Admin > Setup Wizard > Products" 864ms

And I wait until I see "Product Description" text 1s 70ms

Then I should see a "Arch" text 124ms

And I should see a "Channels" text 123ms

And I should not see a "WebYaST 1.3" text 123ms

@scc_credentials

Scenario:
Use the products and architecture filters

2s 406ms 7

When I follow the left menu "Admin > Setup Wizard > Products" 70ms

And I wait until I do not see "currently running" text 87ms

And I wait until I do not see "Loading" text 774ms

And I enter "RHEL and Liberty" as the filtered product description 164ms

Then I should see a "RHEL and Liberty 8 Base" text 88ms

When I select "x86_64" from "product-arch-filter" 1s 125ms

Then I should see a "RHEL and Liberty 8 Base" text 95ms

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

When I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "currently running" text 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Enterprise Server for SAP Applications 15 x86_64" as the filtered product description 0s

And I click the channel list of product "SUSE Linux Enterprise Server for SAP Applications 15 x86_64" 0s

Then I should see a "Product Channels" text 0s

And I should see a "Mandatory Channels" text 0s

And I should see a "Optional Channels" text 0s

When I close the modal dialog 0s

@scc_credentials @susemanager

Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools

< 1ms 30

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "currently running" text 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Enterprise Server 15 SP7" as the filtered product description 0s

And I wait until I see "SUSE Linux Enterprise Server 15 SP7 x86_64" text 0s

And I open the sub-list of the product "SUSE Linux Enterprise Server 15 SP7 x86_64" 0s

And I open the sub-list of the product "Basesystem Module 15 SP7 x86_64" 0s

And I open the sub-list of the product "Desktop Applications Module 15 SP7 x86_64" 0s

And I open the sub-list of the product "SUSE Multi-Linux Manager Client Tools for SLE 15 x86_64" if present 0s

Then I should see that the "Basesystem Module 15 SP7 x86_64" product is "recommended" 0s

And I should see that the "Server Applications Module 15 SP7 x86_64" product is "recommended" 0s

And I should see that the "SUSE Multi-Linux Manager Client Tools for SLE 15 x86_64" product is "recommended" 0s

When I select "SUSE Linux Enterprise Server 15 SP7 x86_64" as a product 0s

Then I should see the "SUSE Linux Enterprise Server 15 SP7 x86_64" selected 0s

And I should see the "Basesystem Module 15 SP7 x86_64" selected 0s

And I should see the "Server Applications Module 15 SP7 x86_64" selected 0s

And I should see the "SUSE Multi-Linux Manager Client Tools for SLE 15 x86_64" selected 0s

When I select "Desktop Applications Module 15 SP7 x86_64" as a product 0s

And I select "Development Tools Module 15 SP7 x86_64" as a product 0s

Then I should see the "Desktop Applications Module 15 SP7 x86_64" selected 0s

And I should see the "Development Tools Module 15 SP7 x86_64" selected 0s

When I select "Python 3 Module 15 SP7 x86_64" as a product 0s

Then I should see the "Python 3 Module 15 SP7 x86_64" selected 0s

When I select "Containers Module 15 SP7 x86_64" as a product 0s

Then I should see the "Containers Module 15 SP7 x86_64" selected 0s

When I click the Add Product button 0s

And I wait until I see "SUSE Linux Enterprise Server 15 SP7 x86_64" product has been added 0s

Then the SLE15 SP7 product should be added 0s

When I wait until all synchronized channels for "sles15-sp7" have finished 0s

@uyuni

Scenario:
Partially add openSUSE Tumbleweed product, only including the required packages to generate the bootstrap repository

2m 1s 297ms 4

Reposync of channel opensuse_tumbleweed-x86_64 killed
Channel opensuse_tumbleweed-uyuni-client-x86_64 added
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 added

When I use spacewalk-common-channel to add channel "opensuse_tumbleweed" with arch "x86_64" 7s 540ms

And I kill running spacewalk-repo-sync for "opensuse_tumbleweed-x86_64" channel 1s 393ms

And I use spacewalk-repo-sync to sync channel "opensuse_tumbleweed-x86_64" including only client tools dependencies 1m 36s 563ms

And I use spacewalk-common-channel to add all "tumbleweed-client-tools-x86_64" channels with arch "x86_64" 15s 800ms

@containerized_server @proxy @uyuni

Scenario:
Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools

54s 835ms 2

Channel opensuse_tumbleweed-x86_64 added
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 added
Channel uyuni-proxy-devel-tumbleweed-x86_64 added
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 finished reposync
Channel uyuni-proxy-devel-tumbleweed-x86_64 finished reposync
Channel opensuse_tumbleweed-x86_64 finished reposync
All channels for uyuni-proxy have been fully synced

When I use spacewalk-common-channel to add all "uyuni-proxy" channels with arch "x86_64" 21s 198ms

And I wait until all synchronized channels for "uyuni-proxy" have finished 33s 637ms

@scc_credentials @uyuni @build_host

Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature

61m 21s 699ms 20

Products list: Available Channels: Status: - [I] - channel is installed - [ ] - channel is not installed, but is available - [U] - channel is unavailable [ ] EL9-Pool for x86_64 RHEL and Liberty 9 Base [el9-pool-x86_64] [ ] RHEL7-Pool for x86_64 RHEL7 Base x86_64 [rhel7-pool-x86_64] [ ] RHEL8-Pool for x86_64 RHEL and Liberty 8 Base [rhel8-pool-x86_64] [ ] SLE-Micro-5.3-Pool for x86_64 SUSE Linux Enterprise Micro 5.3 x86_64 [sle-micro-5.3-pool-x86_64] [ ] SLE-Product-SLED15-SP4-Pool for x86_64 SUSE Linux Enterprise Desktop 15 SP4 x86_64 [sle-product-sled15-sp4-pool-x86_64] [ ] SLE-Product-SLES15-SP4-Pool for x86_64 SUSE Linux Enterprise Server 15 SP4 x86_64 [sle-product-sles15-sp4-pool-x86_64] [ ] SLE-Product-SLES15-SP5-Pool for x86_64 SUSE Linux Enterprise Server 15 SP5 x86_64 [sle-product-sles15-sp5-pool-x86_64] [ ] SLE-Product-SLES15-SP6-Pool for x86_64 SUSE Linux Enterprise Server 15 SP6 x86_64 [sle-product-sles15-sp6-pool-x86_64] [I] SLE-Product-SLES15-SP7-Pool for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-pool-x86_64] [I] SLE-Module-Basesystem15-SP7-Pool for x86_64 Basesystem Module 15 SP7 x86_64 [sle-module-basesystem15-sp7-pool-x86_64] [I] SLE-Module-Basesystem15-SP7-Updates for x86_64 Basesystem Module 15 SP7 x86_64 [sle-module-basesystem15-sp7-updates-x86_64] [ ] SLE-Module-Containers15-SP7-Pool for x86_64 Containers Module 15 SP7 x86_64 [sle-module-containers15-sp7-pool-x86_64] [ ] SLE-Module-Containers15-SP7-Updates for x86_64 Containers Module 15 SP7 x86_64 [sle-module-containers15-sp7-updates-x86_64] [I] SLE-Module-Desktop-Applications15-SP7-Pool for x86_64 Desktop Applications Module 15 SP7 x86_64 [sle-module-desktop-applications15-sp7-pool-x86_64] [I] SLE-Module-Desktop-Applications15-SP7-Updates for x86_64 Desktop Applications Module 15 SP7 x86_64 [sle-module-desktop-applications15-sp7-updates-x86_64] [I] SLE-Module-DevTools15-SP7-Pool for x86_64 Development Tools Module 15 SP7 x86_64 [sle-module-devtools15-sp7-pool-x86_64] [I] SLE-Module-DevTools15-SP7-Updates for x86_64 Development Tools Module 15 SP7 x86_64 [sle-module-devtools15-sp7-updates-x86_64] [ ] SLE-Module-Live-Patching15-SP7-Pool for x86_64 SUSE Linux Enterprise Live Patching 15 SP7 x86_64 [sle-module-live-patching15-sp7-pool-x86_64] [ ] SLE-Module-Live-Patching15-SP7-Updates for x86_64 SUSE Linux Enterprise Live Patching 15 SP7 x86_64 [sle-module-live-patching15-sp7-updates-x86_64] [ ] SLE-Module-Public-Cloud15-SP7-Pool for x86_64 Public Cloud Module 15 SP7 x86_64 [sle-module-public-cloud15-sp7-pool-x86_64] [ ] SLE-Module-Public-Cloud15-SP7-Updates for x86_64 Public Cloud Module 15 SP7 x86_64 [sle-module-public-cloud15-sp7-updates-x86_64] [I] SLE-Module-Python3-15-SP7-Pool for x86_64 Python 3 Module 15 SP7 x86_64 [sle-module-python3-15-sp7-pool-x86_64] [I] SLE-Module-Python3-15-SP7-Updates for x86_64 Python 3 Module 15 SP7 x86_64 [sle-module-python3-15-sp7-updates-x86_64] [I] SLE-Module-Server-Applications15-SP7-Pool for x86_64 Server Applications Module 15 SP7 x86_64 [sle-module-server-applications15-sp7-pool-x86_64] [I] SLE-Module-Server-Applications15-SP7-Updates for x86_64 Server Applications Module 15 SP7 x86_64 [sle-module-server-applications15-sp7-updates-x86_64] [I] SLE-Module-Systems-Management-15-SP7-Pool for x86_64 Systems Management Module 15 SP7 x86_64 [sle-module-systems-management-15-sp7-pool-x86_64] [I] SLE-Module-Systems-Management-15-SP7-Updates for x86_64 Systems Management Module 15 SP7 x86_64 [sle-module-systems-management-15-sp7-updates-x86_64] [ ] SLE-Module-Web-Scripting15-SP7-Pool for x86_64 Web and Scripting Module 15 SP7 x86_64 [sle-module-web-scripting15-sp7-pool-x86_64] [ ] SLE-Module-Web-Scripting15-SP7-Updates for x86_64 Web and Scripting Module 15 SP7 x86_64 [sle-module-web-scripting15-sp7-updates-x86_64] [I] SLE-Product-SLES15-SP7-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-updates-x86_64] [I] SLE15-SP7-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle15-sp7-installer-updates-x86_64] [ ] SUSE-MicroOS-5.2-Pool for x86_64 SUSE Linux Enterprise Micro 5.2 x86_64 [suse-microos-5.2-pool-x86_64]
Channel sles15-sp7-devel-uyuni-client-x86_64 finished reposync
1 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-product-sles15-sp7-pool-x86_64 finished reposync
Channel sle-product-sles15-sp7-updates-x86_64 finished reposync
Channel sle15-sp7-installer-updates-x86_64 finished reposync
2 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
3 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
4 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
5 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
6 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
7 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
8 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
9 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
10 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
11 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
12 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
13 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-basesystem15-sp7-updates-x86_64 finished reposync
14 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
15 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
16 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
17 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-basesystem15-sp7-pool-x86_64 finished reposync
18 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-server-applications15-sp7-pool-x86_64 finished reposync
Channel sle-module-server-applications15-sp7-updates-x86_64 finished reposync
Channel sle-module-python3-15-sp7-pool-x86_64 finished reposync
19 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-python3-15-sp7-updates-x86_64 finished reposync
Channel sle-module-systems-management-15-sp7-pool-x86_64 finished reposync
20 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-systems-management-15-sp7-updates-x86_64 finished reposync
21 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
22 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
23 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
24 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
25 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
26 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-desktop-applications15-sp7-pool-x86_64 finished reposync
Channel sle-module-desktop-applications15-sp7-updates-x86_64 finished reposync
27 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
28 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-devtools15-sp7-pool-x86_64 finished reposync
29 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
30 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
31 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
32 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
33 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
34 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
35 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
36 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
37 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
38 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
39 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
40 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
41 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
42 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
43 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-devtools15-sp7-updates-x86_64 finished reposync
All channels for sles15-sp7 have been fully synced

Given I am authorized for the "Admin" section 444ms

When I follow the left menu "Admin > Setup Wizard > Products" 1s 75ms

And I wait until I do not see "currently running" text 81ms

And I wait until I do not see "Loading" text 680ms

And I enter "SUSE Linux Enterprise Server 15 SP7 x86_64" as the filtered product description 153ms

And I select "SUSE Linux Enterprise Server 15 SP7 x86_64" as a product 69ms

Then I should see the "SUSE Linux Enterprise Server 15 SP7 x86_64" selected 28ms

When I open the sub-list of the product "SUSE Linux Enterprise Server 15 SP7 x86_64" 57ms

And I open the sub-list of the product "Basesystem Module 15 SP7 x86_64" 57ms

And I select "Desktop Applications Module 15 SP7 x86_64" as a product 67ms

Then I should see the "Desktop Applications Module 15 SP7 x86_64" selected 23ms

When I open the sub-list of the product "Desktop Applications Module 15 SP7 x86_64" 53ms

And I select "Development Tools Module 15 SP7 x86_64" as a product 63ms

Then I should see the "Development Tools Module 15 SP7 x86_64" selected 39ms

When I click the Add Product button 58ms

And I wait until I see "Selected channels/products were scheduled successfully for syncing." text 7s 299ms

Then the SLE15 SP7 product should be added 2s 822ms

When I use spacewalk-common-channel to add channel "sles15-sp7-devel-uyuni-client" with arch "x86_64" 8s 651ms

And I wait until I see "SUSE Linux Enterprise Server 15 SP7 x86_64" product has been added 12ms

And I wait until all synchronized channels for "sles15-sp7" have finished 60m 59s 960ms

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "currently running" text 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Micro 6.1" as the filtered product description 0s

And I select "SUSE Linux Micro 6.1 x86_64" as a product 0s

Then I should see the "SUSE Linux Micro 6.1 x86_64" selected 0s

When I open the sub-list of the product "SUSE Linux Micro 6.1 x86_64" 0s

And I open the sub-list of the product "SUSE Multi-Linux Manager Client Tools for SL Micro 6 x86_64" if present 0s

And I click the Add Product button 0s

And I wait until I see "Selected channels/products were scheduled successfully for syncing." text 0s

And I wait until I see "SUSE Linux Micro 6.1 x86_64" product has been added 0s

And I wait until all synchronized channels for "sl-micro-6.1" have finished 0s

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "currently running" text 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Enterprise Server 15 SP7" as the filtered product description 0s

And I select "SUSE Linux Enterprise Server 15 SP7 (BETA)" as a product 0s

Then I should see the "SUSE Linux Enterprise Server 15 SP7 (BETA)" selected 0s

When I click the Add Product button 0s

And I wait until I see "Selected channels/products were scheduled successfully for syncing." text 0s

And I wait until I see "SUSE Linux Enterprise Server 15 SP7 (BETA)" product has been added 0s

And I wait until all synchronized channels for "sles15-sp7" have finished 0s

@proxy @susemanager @transactional_server

Scenario:
Add SUSE MLM Proxy Extension 5.1 with SL Micro 6.1 as base OS

< 1ms 13

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "currently running" text 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Micro 6.1" as the filtered product description 0s

When I open the sub-list of the product "SUSE Linux Micro 6.1 x86_64" 0s

And I select "SUSE Linux Micro 6.1 x86_64" as a product 0s

And I select "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" selected 0s

When I click the Add Product button 0s

And I wait until I see "Selected channels/products were scheduled successfully for syncing." text 0s

And I wait until I see "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" product has been added 0s

And I wait until all synchronized channels for "suse-multi-linux-manager-proxy-51" have finished 0s

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SUSE MLM Proxy Extension 5.1 with SLES 15 SP7 as base OS

< 1ms 12

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "currently running" text 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Enterprise Server 15 SP7" as the filtered product description 0s

When I open the sub-list of the product "SUSE Linux Enterprise Server 15 SP7 x86_64" 0s

And I select "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" selected 0s

When I click the Add Product button 0s

And I wait until I see "Selected channels/products were scheduled successfully for syncing." text 0s

And I wait until I see "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" product has been added 0s

And I wait until all synchronized channels for "suse-multi-linux-manager-proxy-51-sp7" have finished 0s

@proxy @susemanager @transactional_server

Scenario:
Add SUSE MLM Retail Branch Server Extension 5.1 with SL Micro 6.1 as base OS

< 1ms 13

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "currently running" text 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Micro 6.1" as the filtered product description 0s

When I open the sub-list of the product "SUSE Linux Micro 6.1 x86_64" 0s

And I select "SUSE Linux Micro 6.1 x86_64" as a product 0s

And I select "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" selected 0s

When I click the Add Product button 0s

And I wait until I see "Selected channels/products were scheduled successfully for syncing." text 0s

And I wait until I see "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" product has been added 0s

And I wait until all synchronized channels for "suse-multi-linux-manager-retail-branch-server-51" have finished 0s

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SUSE MLM Retail Branch Server Extension 5.1 with SLES 15 SP7 as base OS

< 1ms 12

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "currently running" text 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Enterprise Server 15 SP7" as the filtered product description 0s

When I open the sub-list of the product "SUSE Linux Enterprise Server 15 SP7 x86_64" 0s

And I select "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" selected 0s

When I click the Add Product button 0s

And I wait until I see "Selected channels/products were scheduled successfully for syncing." text 0s

And I wait until I see "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" product has been added 0s

And I wait until all synchronized channels for "suma-retail-branch-server-extension-51-sp7" have finished 0s

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

When I execute mgr-sync "list channels" with user "admin" and password "admin" 0s

And I should get " [I] SLE15-SP7-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle15-sp7-installer-updates-x86_64]" 0s

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

54s 269ms 7

Given I am authorized for the "Admin" section 11s 365ms

When I follow the left menu "Admin > Setup Wizard > Products" 743ms

And I wait until I see "Setup Wizard" text 87ms

And I wait until I do not see "Loading" text 759ms

Then I should not see a "Operation not successful" text 130ms

And I select "250" from "pageSize" 1s 131ms

And I should only see success signs in the product list 40s 51ms

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

When I report the synchronization duration for "sles15-sp7" < 1ms

Feature:Create fake channels 24s 865ms 11 1

In Order to distribute software to the clients
As an authorized user
I want to create fake channels for each distribution

Scenario:
Log in as admin user

476ms 1

Given I am authorized for the "Admin" section 476ms

Scenario:
Add a fake base channel for x86_64

1s 824ms 10

When I follow the left menu "Software > Manage > Channels" 202ms

And I follow "Create Channel" 324ms

And I enter "Fake-Base-Channel-SUSE-like" as "Channel Name" 130ms

And I enter "fake-base-channel-suse-like" as "Channel Label" 113ms

And I select "None" from "Parent Channel" 58ms

And I select "x86_64" from "Architecture:" 46ms

And I enter "Base channel for testing" as "Channel Summary" 116ms

And I enter "No more description for base channel." as "Channel Description" 127ms

And I click on "Create Channel" 624ms

Then I should see a "Channel Fake-Base-Channel-SUSE-like created." text 80ms

Scenario:
Add a fake child channel into the fake base channel x86_64

1s 618ms 10

When I follow the left menu "Software > Manage > Channels" 79ms

And I follow "Create Channel" 312ms

And I enter "Fake-Child-Channel-SUSE-like" as "Channel Name" 113ms

And I enter "fake-child-channel-suse-like" as "Channel Label" 114ms

And I select "Fake-Base-Channel-SUSE-like" from "Parent Channel" 74ms

And I select "x86_64" from "Architecture:" 37ms

And I enter "Child channel for testing" as "Channel Summary" 105ms

And I enter "Description for Fake Child Channel SUSE like." as "Channel Description" 139ms

And I click on "Create Channel" 563ms

Then I should see a "Channel Fake-Child-Channel-SUSE-like created." text 77ms

@sle_minion

Scenario:
Add a SUSE fake child channel to the SUSE Product base channel

1s 74ms 10

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Create Channel" 315ms

And I enter "Fake-RPM-SUSE-Channel" as "Channel Name" 95ms

And I enter "fake-rpm-suse-channel" as "Channel Label" 94ms

And I select the parent channel for the "sle_minion" from "Parent Channel" 52ms

And I select "x86_64" from "Architecture:" 39ms

And I enter "Fake-RPM-SUSE-Channel for testing" as "Channel Summary" 116ms

And I enter "Description for Fake-RPM-SUSE-Channel Child Channel." as "Channel Description" 150ms

And I click on "Create Channel" 56ms

Then I should see a "Channel Fake-RPM-SUSE-Channel created." text 80ms

Scenario:
Add a fake base channel for i586

1s 545ms 10

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Create Channel" 324ms

And I enter "Fake-Base-Channel-i586" as "Channel Name" 98ms

And I enter "fake-base-channel-i586" as "Channel Label" 96ms

And I select "None" from "Parent Channel" 40ms

And I select "IA-32" from "Architecture:" 59ms

And I enter "Fake-Base-Channel-i586 channel for testing" as "Channel Summary" 134ms

And I enter "No more description for base channel." as "Channel Description" 118ms

And I click on "Create Channel" 523ms

Then I should see a "Channel Fake-Base-Channel-i586 created." text 77ms

Scenario:
Add a fake child channel into the fake base channel i586

1s 76ms 10

When I follow the left menu "Software > Manage > Channels" 71ms

And I follow "Create Channel" 321ms

And I enter "Fake-Child-Channel-i586" as "Channel Name" 101ms

And I enter "fake-child-channel-i586" as "Channel Label" 100ms

And I select "Fake-Base-Channel-i586" from "Parent Channel" 67ms

And I select "IA-32" from "Architecture:" 37ms

And I enter "Fake Child Channel i586 for testing" as "Channel Summary" 118ms

And I enter "Description for Fake Child Channel i586." as "Channel Description" 123ms

And I click on "Create Channel" 56ms

Then I should see a "Channel Fake-Child-Channel-i586 created." text 78ms

Scenario:
Add a test base channel for x86_64

1s 573ms 10

When I follow the left menu "Software > Manage > Channels" 74ms

And I follow "Create Channel" 326ms

And I enter "Test-Base-Channel-x86_64" as "Channel Name" 101ms

And I enter "test-base-channel-x86_64" as "Channel Label" 99ms

And I select "None" from "Parent Channel" 41ms

And I select "x86_64" from "Architecture:" 35ms

And I enter "Test-Base-Channel-x86_64 channel for testing" as "Channel Summary" 137ms

And I enter "No more description for base channel." as "Channel Description" 122ms

And I click on "Create Channel" 555ms

Then I should see a "Channel Test-Base-Channel-x86_64 created." text 78ms

Scenario:
Add a child channel into the test base channel x86_64

1s 529ms 10

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Create Channel" 253ms

And I enter "Test-Child-Channel-x86_64" as "Channel Name" 101ms

And I enter "test-child-channel-x86_64" as "Channel Label" 102ms

And I select "Test-Base-Channel-x86_64" from "Parent Channel" 65ms

And I select "x86_64" from "Architecture:" 37ms

And I enter "Test-Child-Channel-x86_64 channel for testing" as "Channel Summary" 141ms

And I enter "Description for Test-Child-Channel-x86_64 Channel." as "Channel Description" 143ms

And I click on "Create Channel" 533ms

Then I should see a "Channel Test-Child-Channel-x86_64 created." text 76ms

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add a fake terminal child channel to the SUSE Product base channel

< 1ms 10

When I follow the left menu "Software > Manage > Channels" 0s

And I follow "Create Channel" 0s

And I enter "Fake-RPM-Terminal-Channel" as "Channel Name" 0s

And I enter "fake-rpm-terminal-channel" as "Channel Label" 0s

And I select the parent channel for the "pxeboot_minion" from "Parent Channel" 0s

And I select "x86_64" from "Architecture:" 0s

And I enter "Fake-RPM-Terminal-Channel for testing" as "Channel Summary" 0s

And I enter "Description for Fake-RPM-Terminal-Channel Child Channel." as "Channel Description" 0s

And I click on "Create Channel" 0s

Then I should see a "Channel Fake-RPM-Terminal-Channel created." text 0s

@deblike_minion

Scenario:
Add Debian-like AMD64 base channel

11s 632ms 11

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Create Channel" 254ms

And I enter "Fake-Base-Channel-Debian-like" as "Channel Name" 112ms

And I enter "fake-base-channel-debian-like" as "Channel Label" 108ms

And I select "None" from "Parent Channel" 45ms

And I select "AMD64 Debian" from "Architecture:" 64ms

And I enter "Fake-Base-Channel-Debian-like for testing" as "Channel Summary" 133ms

And I enter "No more description for base channel." as "Channel Description" 117ms

And I uncheck "gpg_check" 10s 71ms

And I click on "Create Channel" 65ms

Then I should see a "Channel Fake-Base-Channel-Debian-like created." text 585ms

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 457ms 10

When I follow the left menu "Software > Manage > Channels" 75ms

And I follow "Create Channel" 256ms

And I enter "Fake-Base-Channel-RH-like" as "Channel Name" 103ms

And I enter "fake-base-channel-rh-like" as "Channel Label" 104ms

And I select "None" from "Parent Channel" 42ms

And I select "x86_64" from "Architecture:" 45ms

And I enter "Fake-Base-Channel-RH-like for testing" as "Channel Summary" 126ms

And I enter "No more description for base channel." as "Channel Description" 120ms

And I click on "Create Channel" 503ms

Then I should see a "Channel Fake-Base-Channel-RH-like created." text 78ms

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 56ms 10

When I follow the left menu "Software > Manage > Channels" 74ms

And I follow "Create Channel" 289ms

And I enter "Fake-Base-Channel-AppStream" as "Channel Name" 111ms

And I enter "fake-base-channel-appstream" as "Channel Label" 105ms

And I select "None" from "Parent Channel" 41ms

And I select "x86_64" from "Architecture:" 36ms

And I enter "Fake-Base-Channel-AppStream for testing" as "Channel Summary" 127ms

And I enter "Description for Fake-Base-Channel-AppStream." as "Channel Description" 132ms

And I click on "Create Channel" 58ms

Then I should see a "Channel Fake-Base-Channel-AppStream created." text 79ms

Feature:Create fake repositories for each fake child channel 52s 212ms 14 1

In order to distribute software to the clients
As an authorized user
I want to create a fake repository per fake child channel

Scenario:
Log in as admin user

505ms 1

Given I am authorized for the "Admin" section 505ms

Scenario:
Create a fake repository for distributions using RPM

1s 177ms 7

When I follow the left menu "Software > Manage > Repositories" 177ms

And I follow "Create Repository" 312ms

And I enter "fake-rpm-repo" as "label" 61ms

And I enter "http://localhost/pub/TestRepoRpmUpdates/" as "url" 89ms

And I click on "Create Repository" 451ms

Then I should see a "Repository created successfully" text 65ms

And I should see "metadataSigned" as checked 19ms

Scenario:
Disable metadata check for the fake RPM repository

11s 13ms 6

When I follow the left menu "Software > Manage > Repositories" 72ms

And I follow "fake-rpm-repo" 327ms

And I uncheck "metadataSigned" 10s 83ms

And I click on "Update Repository" 447ms

Then I should see a "Repository updated successfully" text 66ms

And I should see "metadataSigned" as unchecked 16ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 26ms 7

When I follow the left menu "Software > Manage > Repositories" 73ms

And I follow "Create Repository" 295ms

And I enter "fake-appstream-repo" as "label" 64ms

And I enter "http://localhost/pub/TestRepoAppStream/" as "url" 86ms

And I click on "Create Repository" 423ms

Then I should see a "Repository created successfully" text 65ms

And I should see "metadataSigned" as checked 16ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 904ms 6

When I follow the left menu "Software > Manage > Repositories" 72ms

And I follow "fake-appstream-repo" 242ms

And I uncheck "metadataSigned" 10s 68ms

And I click on "Update Repository" 439ms

Then I should see a "Repository updated successfully" text 65ms

And I should see "metadataSigned" as unchecked 16ms

@sle_minion

Scenario:
Add the fake RPM repository to the SUSE fake child channel

2s 143ms 9

When I follow the left menu "Software > Manage > Channels" 80ms

And I follow "Fake-RPM-SUSE-Channel" 456ms

And I enter "file:///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key" as "GPG key URL" 175ms

And I click on "Update Channel" 652ms

Then I should see a "Channel Fake-RPM-SUSE-Channel updated" text 80ms

When I follow "Repositories" in the content area 74ms

And I select the "fake-rpm-repo" repo 58ms

And I click on "Save Repositories" 488ms

Then I should see a "Fake-RPM-SUSE-Channel repository information was successfully updated" text 76ms

Scenario:
Add the fake RPM repository to the Test child channel

2s 691ms 9

When I follow the left menu "Software > Manage > Channels" 71ms

And I follow "Test-Child-Channel-x86_64" 355ms

And I enter "file:///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key" as "GPG key URL" 176ms

And I click on "Update Channel" 582ms

Then I should see a "Channel Test-Child-Channel-x86_64 updated" text 78ms

When I follow "Repositories" in the content area 69ms

And I select the "fake-rpm-repo" repo 51ms

And I click on "Save Repositories" 1s 231ms

Then I should see a "Test-Child-Channel-x86_64 repository information was successfully updated" text 75ms

@rhlike_minion

Scenario:
Add the fake RPM repository to the RedHat-like base channel

2s 631ms 9

When I follow the left menu "Software > Manage > Channels" 70ms

And I follow "Fake-Base-Channel-RH-like" 354ms

And I enter "file:///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key" as "GPG key URL" 179ms

And I click on "Update Channel" 540ms

Then I should see a "Channel Fake-Base-Channel-RH-like updated" text 75ms

When I follow "Repositories" in the content area 63ms

And I select the "fake-rpm-repo" repo 51ms

And I click on "Save Repositories" 1s 222ms

Then I should see a "Fake-Base-Channel-RH-like repository information was successfully updated" text 73ms

@rhlike_minion

Scenario:
Add the fake AppStream repository to the AppStream base channel

2s 553ms 9

When I follow the left menu "Software > Manage > Channels" 69ms

And I follow "Fake-Base-Channel-AppStream" 354ms

And I enter "file:///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key" as "GPG key URL" 182ms

And I click on "Update Channel" 614ms

Then I should see a "Channel Fake-Base-Channel-AppStream updated" text 78ms

When I follow "Repositories" in the content area 64ms

And I select the "fake-appstream-repo" repo 57ms

And I click on "Save Repositories" 1s 60ms

Then I should see a "Fake-Base-Channel-AppStream repository information was successfully updated" text 73ms

Scenario:
Create a fake repository for i586

11s 130ms 7

When I follow the left menu "Software > Manage > Repositories" 77ms

And I follow "Create Repository" 312ms

And I enter "fake-i586-repo" as "label" 63ms

And I enter "file:///srv/www/htdocs/pub/TestRepoRpmUpdates/" as "url" 95ms

And I uncheck "metadataSigned" 10s 80ms

And I click on "Create Repository" 435ms

Then I should see a "Repository created successfully" text 65ms

Scenario:
Add the repository to the i586 channel

2s 2ms 9

When I follow the left menu "Software > Manage > Channels" 76ms

And I follow "Fake-Child-Channel-i586" 380ms

And I enter "file:///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key" as "GPG key URL" 177ms

And I click on "Update Channel" 490ms

Then I should see a "Channel Fake-Child-Channel-i586 updated" text 78ms

When I follow "Repositories" in the content area 65ms

And I select the "fake-i586-repo" repo 56ms

And I click on "Save Repositories" 603ms

Then I should see a "Fake-Child-Channel-i586 repository information was successfully updated" text 71ms

@sle_minion

Scenario:
Add the repository to the SUSE-like child channel

1s 626ms 6

When I follow the left menu "Software > Manage > Channels" 70ms

And I follow "Fake-Child-Channel-SUSE-like" 351ms

And I follow "Repositories" in the content area 61ms

And I select the "fake-rpm-repo" repo 57ms

And I click on "Save Repositories" 1s 12ms

Then I should see a "Fake-Child-Channel-SUSE-like repository information was successfully updated" text 72ms

@deblike_minion

Scenario:
Create a fake repository for Debian-like

752ms 7

When I follow the left menu "Software > Manage > Repositories" 74ms

And I follow "Create Repository" 324ms

And I enter "fake-debian-repo" as "label" 65ms

And I select "deb" from "contenttype" 67ms

And I enter "http://localhost/pub/TestRepoDebUpdates/" as "url" 88ms

And I click on "Create Repository" 57ms

Then I should see a "Repository created successfully" text 74ms

@deblike_minion

Scenario:
Add the repository to the Debian-like base channel

2s 52ms 6

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Fake-Base-Channel-Debian-like" 548ms

And I follow "Repositories" in the content area 58ms

And I select the "fake-debian-repo" repo 55ms

And I click on "Save Repositories" 1s 239ms

Then I should see a "Fake-Base-Channel-Debian-like repository information was successfully updated" text 77ms

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

When I follow the left menu "Software > Manage > Channels" 0s

And I follow "Fake-RPM-Terminal-Channel" 0s

And I enter "file:///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key" as "GPG key URL" 0s

And I click on "Update Channel" 0s

Then I should see a "Channel Fake-RPM-Terminal-Channel updated" text 0s

When I follow "Repositories" in the content area 0s

And I select the "fake-rpm-repo" repo 0s

And I click on "Save Repositories" 0s

Then I should see a "Fake-RPM-Terminal-Channel repository information was successfully updated" text 0s

@skip_if_github_validation
Feature:Create custom channels with development repositories 29s 326ms 9

In Order to use product packages in development to the clients
As an authorized user
I want to create custom channels for each distribution

Scenario:
Log in as admin user

499ms 1

Given I am authorized for the "Admin" section 499ms

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 188ms 10

When I follow the left menu "Software > Manage > Channels" 174ms

And I follow "Create Channel" 273ms

And I enter "Devel-SUSE-Channel" as "Channel Name" 117ms

And I enter "devel-suse-channel" as "Channel Label" 93ms

And I select the parent channel for the "sle_minion" from "Parent Channel" 56ms

And I select "x86_64" from "Architecture:" 47ms

And I enter "Devel-SUSE-Channel for development repositories" as "Channel Summary" 146ms

And I enter "Channel containing development repositories" as "Channel Description" 132ms

And I click on "Create Channel" 66ms

Then I should see a "Channel Devel-SUSE-Channel created." text 79ms

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 511ms 1

When I prepare the development repositories of "sle_minion" as part of "devel-suse-channel" channel 6s 511ms

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 721ms 10

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Create Channel" 371ms

And I enter "Devel-Build-Host-Channel" as "Channel Name" 106ms

And I enter "devel-build-host-channel" as "Channel Label" 105ms

And I select the parent channel for the "build_host" from "Parent Channel" 51ms

And I select "x86_64" from "Architecture:" 38ms

And I enter "Devel-Build-Host-Channel for development repositories" as "Channel Summary" 157ms

And I enter "Channel containing development repositories" as "Channel Description" 129ms

And I click on "Create Channel" 610ms

Then I should see a "Channel Devel-Build-Host-Channel created." text 78ms

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 635ms 1

When I prepare the development repositories of "build_host" as part of "devel-build-host-channel" channel 4s 635ms

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 100ms 10

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Create Channel" 269ms

And I enter "Devel-Debian-like-Channel" as "Channel Name" 106ms

And I enter "devel-debian-like-channel" as "Channel Label" 117ms

And I select "Fake-Base-Channel-Debian-like" from "Parent Channel" 67ms

And I select "AMD64 Debian" from "Architecture:" 42ms

And I enter "Devel-Debian-like-Channel for development repositories" as "Channel Summary" 157ms

And I enter "Channel containing development repositories" as "Channel Description" 129ms

And I click on "Create Channel" 59ms

Then I should see a "Channel Devel-Debian-like-Channel created." text 78ms

@deblike_minion

Scenario:
Create custom repositories inside the Debian-like custom channel

6s 995ms 1

When I prepare the development repositories of "deblike_minion" as part of "devel-debian-like-channel" channel 6s 995ms

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 658ms 10

When I follow the left menu "Software > Manage > Channels" 71ms

And I follow "Create Channel" 373ms

And I enter "Devel-RH-like-Channel" as "Channel Name" 96ms

And I enter "devel-rh-like-channel" as "Channel Label" 107ms

And I select "Fake-Base-Channel-RH-like" from "Parent Channel" 67ms

And I select "x86_64" from "Architecture:" 36ms

And I enter "Devel-RH-like-Channel for development repositories" as "Channel Summary" 150ms

And I enter "Channel containing development repositories" as "Channel Description" 129ms

And I click on "Create Channel" 547ms

Then I should see a "Channel Devel-RH-like-Channel created." text 77ms

@rhlike_minion

Scenario:
Create custom repositories inside the RH-like custom channel

5s 16ms 1

When I prepare the development repositories of "rhlike_minion" as part of "devel-rh-like-channel" channel 5s 16ms

Feature:Synchronize fake channels 58s 150ms 12 2

In order to use the content provided inside the repositories of the fake channels
As admin
I want to synchronize the fake channels

Scenario:
Log in as admin user

2s 35ms 2

Given I am authorized for the "Admin" section 491ms

And I enable source package syncing 1s 543ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 901ms 9

Given I am authorized for the "Admin" section 489ms

When I follow the left menu "Software > Manage > Channels" 151ms

And I follow "Fake-RPM-SUSE-Channel" 474ms

And I follow "Repositories" in the content area 58ms

And I follow "Sync" 431ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 65ms

And I click on "Sync Now" 1s 743ms

Then I should see a "Repository sync scheduled for Fake-RPM-SUSE-Channel." text 67ms

And I wait until the channel "fake-rpm-suse-channel" has been synced 418ms

@sle_minion

Scenario:
Verify state of Fake-RPM-SUSE-Channel channel

4s 855ms 2

Then "orion-dummy-1.1-1.1.x86_64.rpm" package should have been stored 4s 207ms

And solver file for "fake-rpm-suse-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm" 647ms

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 730ms 9

Given I am authorized for the "Admin" section 434ms

When I follow the left menu "Software > Manage > Channels" 157ms

And I follow "Fake-Child-Channel-i586" 391ms

And I follow "Repositories" in the content area 60ms

And I follow "Sync" 427ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 66ms

And I click on "Sync Now" 1s 731ms

Then I should see a "Repository sync scheduled for Fake-Child-Channel-i586." text 71ms

And I wait until the channel "fake-child-channel-i586" has been synced 389ms

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

14s 663ms 9

Given I am authorized for the "Admin" section 454ms

When I follow the left menu "Software > Manage > Channels" 155ms

And I follow "Test-Child-Channel-x86_64" 392ms

And I follow "Repositories" in the content area 61ms

And I follow "Sync" 862ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 68ms

And I click on "Sync Now" 1s 826ms

Then I should see a "Repository sync scheduled for Test-Child-Channel-x86_64." text 66ms

And I wait until the channel "test-child-channel-x86_64" has been synced 10s 774ms

@sle_minion

Scenario:
Synchronize Fake-Child-Channel-SUSE-like channel

3s 620ms 9

Given I am authorized for the "Admin" section 428ms

When I follow the left menu "Software > Manage > Channels" 157ms

And I follow "Fake-Child-Channel-SUSE-like" 385ms

And I follow "Repositories" in the content area 56ms

And I follow "Sync" 346ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 69ms

And I click on "Sync Now" 1s 731ms

Then I should see a "Repository sync scheduled for Fake-Child-Channel-SUSE-like." text 69ms

And I wait until the channel "fake-child-channel-suse-like" has been synced 374ms

@deblike_minion

Scenario:
Synchronize Fake-Base-Channel-Debian-like channel

4s 225ms 9

Given I am authorized for the "Admin" section 469ms

When I follow the left menu "Software > Manage > Channels" 156ms

And I follow "Fake-Base-Channel-Debian-like" 483ms

And I follow "Repositories" in the content area 59ms

And I follow "Sync" 697ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 69ms

And I click on "Sync Now" 1s 819ms

Then I should see a "Repository sync scheduled for Fake-Base-Channel-Debian-like." text 67ms

And I wait until the channel "fake-base-channel-debian-like" has been synced 401ms

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-RH-like channel

4s 264ms 9

Given I am authorized for the "Admin" section 505ms

When I follow the left menu "Software > Manage > Channels" 162ms

And I follow "Fake-Base-Channel-RH-like" 385ms

And I follow "Repositories" in the content area 54ms

And I follow "Sync" 786ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 72ms

And I click on "Sync Now" 1s 807ms

Then I should see a "Repository sync scheduled for Fake-Base-Channel-RH-like." text 67ms

And I wait until the channel "fake-base-channel-rh-like" has been synced 421ms

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 142ms 9

Given I am authorized for the "Admin" section 480ms

When I follow the left menu "Software > Manage > Channels" 160ms

And I follow "Fake-Base-Channel-AppStream" 382ms

And I follow "Repositories" in the content area 67ms

And I follow "Sync" 698ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 68ms

And I click on "Sync Now" 1s 839ms

Then I should see a "Repository sync scheduled for Fake-Base-Channel-AppStream." text 66ms

And I wait until the channel "fake-base-channel-appstream" has been synced 377ms

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Synchronize the repository in the terminal channel

< 1ms 9

Given I am authorized for the "Admin" section 0s

And I follow the left menu "Software > Manage > Channels" 0s

And I follow "Fake-RPM-Terminal-Channel" 0s

And I follow "Repositories" in the content area 0s

And I follow "Sync" 0s

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 0s

And I click on "Sync Now" 0s

Then I should see a "Repository sync scheduled for Fake-RPM-Terminal-Channel." text 0s

And I wait until the channel "fake-rpm-terminal-channel" has been synced 0s

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Verify state of Fake-RPM-Terminal-Channel custom channel

< 1ms 2

Then "orion-dummy-1.1-1.1.x86_64.rpm" package should have been stored 0s

And solver file for "fake-rpm-terminal-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm" 0s

Scenario:
Refresh the errata cache

6s 578ms 6

When I follow the left menu "Admin > Task Schedules" 114ms

And I follow "errata-cache-default" 1s 347ms

And I follow "errata-cache-bunch" 1s 607ms

And I click on "Single Run Schedule" 986ms

Then I should see a "bunch was scheduled" text 268ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 254ms

Scenario:
Refresh the channel's repository data

5s 142ms 6

When I follow the left menu "Admin > Task Schedules" 65ms

And I follow "channel-repodata-default" 1s 243ms

And I follow "channel-repodata-bunch" 1s 179ms

And I click on "Single Run Schedule" 364ms

Then I should see a "bunch was scheduled" text 245ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 43ms

Scenario:
Cleanup disable source package syncing

991ms 1

Then I disable source package syncing 991ms

@skip_if_github_validation
Feature:Synchronize development channels 16s 477ms 4

In order to use the content provided inside the repositories of the dev channels
As admin
I want to synchronize the dev channels

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

3s 679ms 9

Given I am authorized for the "Admin" section 437ms

When I follow the left menu "Software > Manage > Channels" 186ms

And I follow "Devel-SUSE-Channel" 385ms

And I follow "Repositories" in the content area 84ms

And I follow "Sync" 352ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 66ms

And I click on "Sync Now" 1s 723ms

Then I should see a "Repository sync scheduled for Devel-SUSE-Channel." text 69ms

And I wait until the channel "devel-suse-channel" has been synced 373ms

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 304ms 9

Given I am authorized for the "Admin" section 505ms

When I follow the left menu "Software > Manage > Channels" 169ms

And I follow "Devel-Debian-like-Channel" 380ms

And I follow "Repositories" in the content area 59ms

And I follow "Sync" 798ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 68ms

And I click on "Sync Now" 1s 816ms

Then I should see a "Repository sync scheduled for Devel-Debian-like-Channel." text 73ms

And I wait until the channel "devel-debian-like-channel" has been synced 431ms

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 250ms 9

Given I am authorized for the "Admin" section 468ms

When I follow the left menu "Software > Manage > Channels" 158ms

And I follow "Devel-RH-like-Channel" 292ms

And I follow "Repositories" in the content area 63ms

And I follow "Sync" 972ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 70ms

And I click on "Sync Now" 1s 795ms

Then I should see a "Repository sync scheduled for Devel-RH-like-Channel." text 68ms

And I wait until the channel "devel-rh-like-channel" has been synced 360ms

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 243ms 9

Given I am authorized for the "Admin" section 451ms

When I follow the left menu "Software > Manage > Channels" 153ms

And I follow "Devel-Build-Host-Channel" 396ms

And I follow "Repositories" in the content area 56ms

And I follow "Sync" 886ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 67ms

And I click on "Sync Now" 1s 763ms

Then I should see a "Repository sync scheduled for Devel-Build-Host-Channel." text 71ms

And I wait until the channel "devel-build-host-channel" has been synced 397ms

Feature:Create activation keys 18s 137ms 9

In order to register systems to the server
As the testing user
I want to use activation keys

Scenario:
Log in as admin user

491ms 1

Given I am authorized for the "Admin" section 491ms

@sle_minion

Scenario:
Create an activation key with a channel

2s 213ms 2

When I create an activation key with id "SUSE-KEY-x86_64", description "SUSE Test Key x86_64", limit of 20 and contact method "default" 1s 631ms

Then I should get the new activation key "1-SUSE-KEY-x86_64" 581ms

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

2s 93ms 2

When I create an activation key with id "RH-LIKE-KEY", description "RedHat like Test Key", base channel "fake-base-channel-rh-like", limit of 20 and contact method "default" 993ms

Then I should get the new activation key "1-RH-LIKE-KEY" 1s 100ms

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

2s 644ms 2

When I create an activation key with id "DEBLIKE-KEY", description "Debian-like Test Key", base channel "fake-base-channel-debian-like", limit of 20 and contact method "default" 1s 555ms

Then I should get the new activation key "1-DEBLIKE-KEY" 1s 89ms

@ssh_minion

Scenario:
Create an activation key with a channel for salt-ssh

1s 937ms 2

When I create an activation key with id "SUSE-SSH-KEY-x86_64", description "SUSE SSH Test Key x86_64", limit of 20 and contact method "ssh-push" 883ms

Then I should get the new activation key "1-SUSE-SSH-KEY-x86_64" 1s 54ms

@ssh_minion

Scenario:
Create an activation key with a channel for salt-ssh via tunnel

1s 843ms 2

When I create an activation key with id "SUSE-SSH-TUNNEL-KEY-x86_64", description "SUSE SSH Tunnel Test Key x86_64", limit of 20 and contact method "ssh-push-tunnel" 796ms

Then I should get the new activation key "1-SUSE-SSH-TUNNEL-KEY-x86_64" 1s 47ms

@proxy

Scenario:
Create an activation key for the proxy

2s 43ms 2

When I create an activation key with id "PROXY-KEY-x86_64", description "Proxy Key x86_64", limit of 1 799ms

Then I should get the new activation key "1-PROXY-KEY-x86_64" 1s 243ms

@build_host

Scenario:
Create an activation key for the build host

2s 706ms 3

When I create an activation key with id "BUILD-HOST-KEY-x86_64", description "Build host Key x86_64" 878ms

And I set the entitlements of the activation key "1-BUILD-HOST-KEY-x86_64" to "container_build_host, osimage_build_host" 527ms

Then I should get the new activation key "1-BUILD-HOST-KEY-x86_64" 1s 301ms

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 163ms 2

When I create an activation key with id "TERMINAL-KEY-x86_64", description "Terminal Key x86_64" 758ms

Then I should get the new activation key "1-TERMINAL-KEY-x86_64" 1s 404ms

Feature:Update activation keys 22s 906ms 11 8

In order to register systems to the spacewalk server
As admin
I want to update activation keys to use synchronized base products

Scenario:
Log in as admin user

495ms 1

Given I am authorized for the "Admin" section 495ms

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "SUSE Test Key x86_64" in the content area 0s

And I wait for child channels to appear 0s

And I select the parent channel for the "sle_minion" from "selectedBaseChannel" 0s

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I wait until "SLE-Module-Basesystem15-SP7-Pool for x86_64" has been checked 0s

And I wait until "SLE-Module-Basesystem15-SP7-Updates for x86_64" has been checked 0s

And I wait until "SLE-Module-Server-Applications15-SP7-Pool for x86_64" has been checked 0s

And I wait until "SLE-Module-Server-Applications15-SP7-Updates for x86_64" has been checked 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I wait until "SLE-Module-DevTools15-SP7-Updates for x86_64" has been checked 0s

And I wait until "SLE-Module-Desktop-Applications15-SP7-Pool for x86_64" has been checked 0s

And I wait until "SLE-Module-Desktop-Applications15-SP7-Updates for x86_64" has been checked 0s

And I check "SLE-Module-Containers15-SP7-Pool for x86_64" 0s

And I wait until "SLE-Module-Containers15-SP7-Updates for x86_64" has been checked 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I wait until "Fake-RPM-SUSE-Channel" has been checked 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key SUSE Test Key x86_64 has been modified" text 0s

@uyuni

Scenario:
Update openSUSE Tumbleweed key with synced base product

2s 665ms 10

When I follow the left menu "Systems > Activation Keys" 123ms

And I follow "SUSE Test Key x86_64" in the content area 69ms

And I wait until I do not see "Loading..." text 676ms

And I select the parent channel for the "sle_minion" from "selectedBaseChannel" 62ms

And I wait until I do not see "Loading..." text 77ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 714ms

And I check "Fake-RPM-SUSE-Channel" 82ms

And I wait until "Fake-RPM-SUSE-Channel" has been checked 15ms

And I click on "Update Activation Key" 766ms

Then I should see a "Activation key SUSE Test Key x86_64 has been modified" text 76ms

@scc_credentials @susemanager

Scenario:
Update SLE SSH key with synced base product

< 1ms 14

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "SUSE SSH Test Key x86_64" in the content area 0s

And I wait for child channels to appear 0s

And I select the parent channel for the "sle_minion" from "selectedBaseChannel" 0s

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I wait until "SLE-Module-DevTools15-SP7-Updates for x86_64" has been checked 0s

And I wait until "SLE-Module-Desktop-Applications15-SP7-Pool for x86_64" has been checked 0s

And I wait until "SLE-Module-Desktop-Applications15-SP7-Updates for x86_64" has been checked 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I wait until "Fake-RPM-SUSE-Channel" has been checked 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key SUSE SSH Test Key x86_64 has been modified" text 0s

@uyuni

Scenario:
Update openSUSE Tumbleweed SSH key with synced base product

2s 252ms 10

When I follow the left menu "Systems > Activation Keys" 65ms

And I follow "SUSE SSH Test Key x86_64" in the content area 67ms

And I wait until I do not see "Loading..." text 746ms

And I select the parent channel for the "sle_minion" from "selectedBaseChannel" 40ms

And I wait until I do not see "Loading..." text 72ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 493ms

And I check "Fake-RPM-SUSE-Channel" 95ms

And I wait until "Fake-RPM-SUSE-Channel" has been checked 17ms

And I click on "Update Activation Key" 579ms

Then I should see a "Activation key SUSE SSH Test Key x86_64 has been modified" text 74ms

@scc_credentials @susemanager

Scenario:
Update SLE SSH tunnel key with synced base product

< 1ms 14

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "SUSE SSH Tunnel Test Key x86_64" in the content area 0s

And I wait for child channels to appear 0s

And I select the parent channel for the "sle_minion" from "selectedBaseChannel" 0s

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I wait until "SLE-Module-DevTools15-SP7-Updates for x86_64" has been checked 0s

And I wait until "SLE-Module-Desktop-Applications15-SP7-Pool for x86_64" has been checked 0s

And I wait until "SLE-Module-Desktop-Applications15-SP7-Updates for x86_64" has been checked 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I wait until "Fake-RPM-SUSE-Channel" has been checked 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key SUSE SSH Tunnel Test Key x86_64 has been modified" text 0s

@uyuni

Scenario:
Update openSUSE Tumbleweed SSH tunnel key with synced base product

1s 735ms 10

When I follow the left menu "Systems > Activation Keys" 64ms

And I follow "SUSE SSH Tunnel Test Key x86_64" in the content area 69ms

And I wait until I do not see "Loading..." text 664ms

And I select the parent channel for the "sle_minion" from "selectedBaseChannel" 41ms

And I wait until I do not see "Loading..." text 75ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 597ms

And I check "Fake-RPM-SUSE-Channel" 71ms

And I wait until "Fake-RPM-SUSE-Channel" has been checked 15ms

And I click on "Update Activation Key" 60ms

Then I should see a "Activation key SUSE SSH Tunnel Test Key x86_64 has been modified" text 75ms

@scc_credentials @susemanager @proxy @containerized_server @transactional_server

Scenario:
Update the SLE Micro proxy key with synced base product

< 1ms 11

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "Proxy Key x86_64" in the content area 0s

And I wait for child channels to appear 0s

And I select the parent channel for the "proxy_container" from "selectedBaseChannel" 0s

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I wait until "ManagerTools-SL-Micro-6.1 for x86_64" has been checked 0s

And I check "SUSE-Multi-Linux-Manager-Proxy-5.1 for x86_64" 0s

And I check "SUSE-Multi-Linux-Manager-Retail-Branch-Server-5.1 for x86_64" 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key Proxy Key x86_64 has been modified" text 0s

@scc_credentials @susemanager @proxy @containerized_server @skip_if_transactional_server

Scenario:
Update the SLES proxy key with synced base product

< 1ms 11

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "Proxy Key x86_64" in the content area 0s

And I wait for child channels to appear 0s

And I select the parent channel for the "proxy_nontransactional" from "selectedBaseChannel" 0s

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I wait until "ManagerTools-SLE15-Pool for x86_64 SP7" has been checked 0s

And I check "SUSE-Manager-Proxy-5.1-Pool for x86_64" 0s

And I check "SUSE-Manager-Proxy-5.1-Updates for x86_64" 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key Proxy Key x86_64 has been modified" text 0s

@uyuni @proxy @containerized_server @skip_if_cloud

Scenario:
Update the openSUSE Tumbleweed Proxy Host key with synced base product

< 1ms 8

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "Proxy Key x86_64" in the content area 0s

And I wait for child channels to appear 0s

And I select the parent channel for the "proxy_container" from "selectedBaseChannel" 0s

And I wait for child channels to appear 0s

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key Proxy Key x86_64 has been modified" text 0s

@scc_credentials @build_host

Scenario:
Update build host key with synced base product

3s 520ms 20

When I follow the left menu "Systems > Activation Keys" 62ms

And I follow "Build host Key x86_64" in the content area 71ms

And I wait for child channels to appear 1s 594ms

And I select the parent channel for the "build_host" from "selectedBaseChannel" 51ms

And I wait for child channels to appear 527ms

And I include the recommended child channels 191ms

And I wait until "SLE-Module-Basesystem15-SP7-Pool for x86_64" has been checked 34ms

And I wait until "SLE-Module-Basesystem15-SP7-Updates for x86_64" has been checked 19ms

And I wait until "SLE-Module-Server-Applications15-SP7-Pool for x86_64" has been checked 19ms

And I wait until "SLE-Module-Server-Applications15-SP7-Updates for x86_64" has been checked 19ms

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 80ms

And I wait until "SLE-Module-DevTools15-SP7-Updates for x86_64" has been checked 18ms

And I wait until "SLE-Module-Desktop-Applications15-SP7-Pool for x86_64" has been checked 19ms

And I wait until "SLE-Module-Desktop-Applications15-SP7-Updates for x86_64" has been checked 19ms

And I wait until "SLE-Module-Systems-Management-15-SP7-Pool for x86_64" has been checked 19ms

And I wait until "SLE-Module-Systems-Management-15-SP7-Updates for x86_64" has been checked 19ms

And I wait until "SLE-Module-Python3-15-SP7-Pool for x86_64" has been checked 19ms

And I wait until "SLE-Module-Python3-15-SP7-Updates for x86_64" has been checked 19ms

And I click on "Update Activation Key" 636ms

Then I should see a "Activation key Build host Key x86_64 has been modified" text 76ms

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 220ms 9

When I follow the left menu "Systems > Activation Keys" 64ms

And I follow "Build host Key x86_64" in the content area 62ms

And I wait for child channels to appear 948ms

And I select the parent channel for the "build_host" from "selectedBaseChannel" 25ms

And I wait for child channels to appear 323ms

And I check "Uyuni Client Tools for SLES15 SP7 x86_64 (Development)" 88ms

And I wait until "Uyuni Client Tools for SLES15 SP7 x86_64 (Development)" has been checked 15ms

And I click on "Update Activation Key" 615ms

Then I should see a "Activation key Build host Key x86_64 has been modified" text 75ms

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 165ms 9

When I follow the left menu "Systems > Activation Keys" 64ms

And I follow "Build host Key x86_64" in the content area 61ms

And I wait for child channels to appear 934ms

And I select the parent channel for the "build_host" from "selectedBaseChannel" 23ms

And I wait for child channels to appear 314ms

And I check "Devel-Build-Host-Channel" 83ms

And I wait until "Devel-Build-Host-Channel" has been checked 16ms

And I click on "Update Activation Key" 594ms

Then I should see a "Activation key Build host Key x86_64 has been modified" text 74ms

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

2s 950ms 16

When I follow the left menu "Systems > Activation Keys" 62ms

And I follow "Terminal Key x86_64" in the content area 89ms

And I wait for child channels to appear 1s 235ms

And I select the parent channel for the "pxeboot_minion" from "selectedBaseChannel" 47ms

And I wait for child channels to appear 445ms

And I include the recommended child channels 173ms

And I wait until "SLE-Module-Basesystem15-SP7-Pool for x86_64" has been checked 16ms

And I wait until "SLE-Module-Basesystem15-SP7-Updates for x86_64" has been checked 16ms

And I wait until "SLE-Module-Server-Applications15-SP7-Pool for x86_64" has been checked 17ms

And I wait until "SLE-Module-Server-Applications15-SP7-Updates for x86_64" has been checked 16ms

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 100ms

And I wait until "SLE-Module-DevTools15-SP7-Updates for x86_64" has been checked 16ms

And I wait until "SLE-Module-Desktop-Applications15-SP7-Pool for x86_64" has been checked 16ms

And I wait until "SLE-Module-Desktop-Applications15-SP7-Updates for x86_64" has been checked 16ms

And I click on "Update Activation Key" 603ms

Then I should see a "Activation key Terminal Key x86_64 has been modified" text 77ms

@susemanager @scc_credentials @build_host

Scenario:
Update terminal key with normal SUSE fake channel

< 1ms 9

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "Terminal Key x86_64" in the content area 0s

And I wait for child channels to appear 0s

And I check "SLE-Module-Containers15-SP7-Pool for x86_64" 0s

And I wait until "SLE-Module-Containers15-SP7-Updates for x86_64" has been checked 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I wait until "Fake-RPM-SUSE-Channel" has been checked 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key Terminal Key x86_64 has been modified" text 0s

@pxeboot_minion @uyuni @scc_credentials @build_host

Scenario:
Update terminal key with specific fake channel

< 1ms 9

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "Terminal Key x86_64" in the content area 0s

And I wait for child channels to appear 0s

And I check "Fake-RPM-Terminal-Channel" 0s

And I wait until "Fake-RPM-Terminal-Channel" has been checked 0s

And I check "Uyuni Client Tools for SLES15 SP7 x86_64 (Development)" 0s

And I wait until "Uyuni Client Tools for SLES15 SP7 x86_64 (Development)" has been checked 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key Terminal Key x86_64 has been modified" text 0s

@skip_if_github_validation @sle_minion

Scenario:
Update SLE key with to include dev child channel

1s 831ms 6

When I follow the left menu "Systems > Activation Keys" 59ms

And I follow "SUSE Test Key x86_64" in the content area 70ms

And I wait for child channels to appear 919ms

And I check "Devel-SUSE-Channel" 100ms

And I click on "Update Activation Key" 604ms

Then I should see a "Activation key SUSE Test Key x86_64 has been modified" text 75ms

@skip_if_github_validation @deblike_minion

Scenario:
Update Debian-like key with to include dev child channel

1s 698ms 6

When I follow the left menu "Systems > Activation Keys" 64ms

And I follow "Debian-like Test Key" in the content area 69ms

And I wait for child channels to appear 825ms

And I check "Devel-Debian-like-Channel" 97ms

And I click on "Update Activation Key" 567ms

Then I should see a "Activation key Debian-like Test Key has been modified" text 74ms

@skip_if_github_validation @rhlike_minion

Scenario:
Update RedHat-like key with to include dev child channel

1s 370ms 6

When I follow the left menu "Systems > Activation Keys" 62ms

And I follow "RedHat like Test Key" in the content area 67ms

And I wait for child channels to appear 1s 11ms

And I check "Devel-RH-like-Channel" 99ms

And I click on "Update Activation Key" 52ms

Then I should see a "Activation key RedHat like Test Key has been modified" text 76ms

Feature:Create bootstrap repositories 9s 367ms 4

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

2s 265ms 1

When I create the bootstrap repositories including custom channels 2s 265ms

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

2s 198ms 1

base_channel: openSUSE Tumbleweed (x86_64)
channel: openSUSE-Tumbleweed-x86_64-uyuni
parent_channel:
Creating the bootstrap repository on the server:
mgr-create-bootstrap-repo --create openSUSE-Tumbleweed-x86_64-uyuni --with-custom-channels

When I create the bootstrap repository for "sle_minion" on the server 2s 198ms

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 114ms 1

When I create the bootstrap repository for "proxy" on the server 2s 114ms

@build_host

Scenario:
Create the bootstrap repository for Build Host

2s 790ms 1

base_channel: SLE-Product-SLES15-SP7-Pool for x86_64
channel: SLE-15-SP7-x86_64
parent_channel: sle-product-sles15-sp7-pool-x86_64
Creating the bootstrap repository on the server:
mgr-create-bootstrap-repo --create SLE-15-SP7-x86_64 --with-parent-channel sle-product-sles15-sp7-pool-x86_64 --with-custom-channels

When I create the bootstrap repository for "build_host" on the server 2s 790ms

@containerized_server @scope_containerized_proxy @proxy
Feature:Setup containerized proxy 3m 26s 459ms 10 2

In order to use a containerized proxy with the server
As the system administrator
I want to register the containerized proxy on the server

Scenario:
Clean up sumaform leftovers on proxy

6s 433ms 1

When I perform a full salt minion cleanup on "proxy" 6s 433ms

@transactional_server

Scenario:
Reboot after clean up

< 1ms 1

When I reboot the "proxy" host through SSH, waiting until it comes back 0s

Scenario:
Log in as admin user

37s 523ms 1

Given I am authorized for the "Admin" section 37s 523ms

Scenario:
Bootstrap the proxy host as a salt minion

35s 846ms 9

The hostname of proxy is uyuni-master-proxy.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 138ms

Then I should see a "Bootstrap Minions" text 85ms

When I enter the hostname of "proxy" as "hostname" 117ms

And I enter "22" as "port" 50ms

And I enter "root" as "user" 56ms

And I enter "linux" as "password" 56ms

And I select "1-PROXY-KEY-x86_64" from "activationKeys" 75ms

And I click on "Bootstrap" 64ms

And I wait until I see "Bootstrap process initiated." text 35s 200ms

@skip_if_cloud @transactional_server

Scenario:
Reboot the proxy host

< 1ms 1

When I reboot the "proxy" host through SSH, waiting until it comes back 0s

Scenario:
Wait until the proxy host appears

1m 22s 634ms 1

When I wait until onboarding is completed for "proxy" 1m 22s 634ms

Scenario:
Generate containerized proxy configuration

11s 249ms 2

When I generate the configuration "/tmp/proxy_container_config.tar.gz" of containerized proxy on the server 8s 350ms

And I copy the configuration "/tmp/proxy_container_config.tar.gz" of containerized proxy from the server to the proxy 2s 899ms

Scenario:
Set up the containerized proxy service to support Avahi

< 1ms 1

Record not added - avahi domain was not detected

When I add avahi hosts in containerized proxy configuration < 1ms

Scenario:
Run a containerized proxy

17s 216ms 1

When I run "mgrpxy install podman /tmp/proxy_container_config.tar.gz" on "proxy" 17s 216ms

Scenario:
Wait until containerized proxy service is active

3s 866ms 10

And I wait until "uyuni-proxy-pod" service is active on "proxy" 574ms

And I wait until "uyuni-proxy-httpd" service is active on "proxy" 428ms

And I wait until "uyuni-proxy-salt-broker" service is active on "proxy" 565ms

And I wait until "uyuni-proxy-squid" service is active on "proxy" 436ms

And I wait until "uyuni-proxy-ssh" service is active on "proxy" 349ms

And I wait until "uyuni-proxy-tftpd" service is active on "proxy" 277ms

And I wait until port "8022" is listening on "proxy" container 298ms

And I wait until port "80" is listening on "proxy" container 296ms

And I wait until port "443" is listening on "proxy" container 291ms

And I visit "Proxy" endpoint of this "proxy" 347ms

Scenario:
The containerized proxy should be registered automatically

762ms 2

When I follow the left menu "Systems" 61ms

And I wait until I see the name of "proxy", refreshing the page 701ms

Scenario:
Check if Monitoring can be enabled on the containerized proxy

10s 925ms 3

Given I am on the Systems overview page of this "proxy" 848ms

When I follow "Properties" in the content area 74ms

Then the "monitoring_entitled" checkbox should be disabled 10s 1ms

@containerized_server @scope_containerized_proxy @proxy @private_net
Feature:Prepare the containerized branch server for PXE booting < 1ms 3

In order to use a containerized proxy as a Retail Branch server
As the system administrator
I make sure the network setup is as expected

Scenario:
Adapt the proxy for Retail

< 1ms 3

When I rename the proxy for Retail 0s

And I connect the second interface of the proxy to the private network 0s

And I restart all proxy containers 0s

Scenario:
Check the branch network

< 1ms 2

Then the "dhcp_dns" host should be present on private network 0s

And name resolution should work on private network 0s

Scenario:
Let the server know about the new IP and FQDN of the containerized proxy

< 1ms 11

Given I am authorized for the "Admin" section 0s

When I am on the Systems overview page of this "proxy" 0s

And I follow "Details" in the content area 0s

And I follow "Hardware" in the content area 0s

And I click on "Schedule Hardware Refresh" 0s

Then I should see a "You have successfully scheduled a hardware profile refresh" text 0s

When I wait until event "Hardware List Refresh scheduled by admin" is completed 0s

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "proxy" 0s

And I follow "Details" in the content area 0s

And I follow "Hardware" in the content area 0s

Then I should see a "proxy.example.org" text 0s

@sle_minion
Feature:Bootstrap a Salt minion via the GUI 2m 58s 607ms 6 2

Scenario:
Clean up sumaform leftovers on SLES minion

10s 428ms 1

When I perform a full salt minion cleanup on "sle_minion" 10s 428ms

Scenario:
Log in as admin user

37s 499ms 1

Given I am authorized for the "Admin" section 37s 499ms

Scenario:
Bootstrap a SLES minion

42s 391ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 144ms

Then I should see a "Bootstrap Minions" text 79ms

When I enter the hostname of "sle_minion" as "hostname" 132ms

And I enter "22" as "port" 52ms

And I enter "root" as "user" 55ms

And I enter "linux" as "password" 55ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 74ms

And I select the hostname of "proxy" from "proxies" if present 2s 771ms

And I click on "Bootstrap" 60ms

And I wait until I see "Bootstrap process initiated." text 38s 964ms

And I report the bootstrap duration for "sle_minion" < 1ms

Scenario:
Check the new bootstrapped minion in System List page

1m 25s 971ms 8

It took 2 seconds to contact the minion

When I follow the left menu "Salt > Keys" 133ms

And I wait until I do not see "Loading..." text 60ms

Then I should see a "accepted" text 334ms

When I follow the left menu "Systems > System List > All" 180ms

And I wait until I see the name of "sle_minion", refreshing the page 44s 624ms

And I wait until onboarding is completed for "sle_minion" 38s 553ms

Then the Salt master can reach "sle_minion" 2s 85ms

And I report the onboarding duration for "sle_minion" < 1ms

@susemanager

Scenario:
Use correct kernel image on the SLES minion

< 1ms 2

When I remove package "kernel-default-base" from this "sle_minion" 0s

And I install package "kernel-default" on this "sle_minion" 0s

@susemanager

Scenario:
Reboot the SLES minion to use the new kernel

< 1ms 1

When I reboot the "sle_minion" host through SSH, waiting until it comes back 0s

@proxy

Scenario:
Check connection from minion to proxy

1s 149ms 4

Given I am on the Systems overview page of this "sle_minion" 934ms

When I follow "Details" in the content area 75ms

And I follow "Connection" in the content area 69ms

Then I should see "proxy" short hostname 69ms

@proxy

Scenario:
Check registration on proxy of minion

1s 167ms 4

Given I am on the Systems overview page of this "proxy" 954ms

When I follow "Details" in the content area 63ms

And I follow "Proxy" in the content area 67ms

Then I should see "sle_minion" hostname 82ms

@ssh_minion
Feature:Bootstrap a Salt host managed via salt-ssh 2m 52s 975ms 5 2

Scenario:
Clean up sumaform leftovers on SLES SSH minion

10s 629ms 1

When I perform a full salt minion cleanup on "ssh_minion" 10s 629ms

Scenario:
Log in as admin user

458ms 1

Given I am authorized for the "Admin" section 458ms

Scenario:
Bootstrap a SLES SSH minion

2m 39s 759ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 128ms

Then I should see a "Bootstrap Minions" text 69ms

When I check "manageWithSSH" 92ms

And I enter the hostname of "ssh_minion" as "hostname" 143ms

And I enter "linux" as "password" 58ms

And I select the hostname of "proxy" from "proxies" if present 77ms

And I click on "Bootstrap" 65ms

And I wait until I see "Bootstrap process initiated." text 56s 608ms

And I follow the left menu "Systems > System List > All" 148ms

And I wait until I see the name of "ssh_minion", refreshing the page 58s 185ms

And I wait until onboarding is completed for "ssh_minion" 44s 180ms

@susemanager

Scenario:
Use correct kernel image on the SSH minion

< 1ms 2

When I remove package "kernel-default-base" from this "ssh_minion" 0s

And I install package "kernel-default" on this "ssh_minion" 0s

@susemanager

Scenario:
Reboot the SSH minion to use the new kernel

< 1ms 1

When I reboot the "ssh_minion" host through SSH, waiting until it comes back 0s

@proxy

Scenario:
Check connection from SSH minion to proxy

1s 113ms 4

Given I am on the Systems overview page of this "ssh_minion" 895ms

When I follow "Details" in the content area 79ms

And I follow "Connection" in the content area 69ms

Then I should see "proxy" short hostname 69ms

@proxy

Scenario:
Check registration on proxy of SSH minion

1s 15ms 4

Given I am on the Systems overview page of this "proxy" 791ms

When I follow "Details" in the content area 64ms

And I follow "Proxy" in the content area 71ms

Then I should see "ssh_minion" hostname 88ms

@rhlike_minion
Feature:Bootstrap a Red Hat-like minion and do some basic operations on it 3m 14s 425ms 7

Scenario:
Log in as admin user

439ms 1

Given I am authorized for the "Admin" section 439ms

Scenario:
Bootstrap a Red Hat-like minion

1m 59s 57ms 13

The hostname of rhlike_minion is uyuni-master-rhlike-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 125ms

Then I should see a "Bootstrap Minions" text 69ms

When I enter the hostname of "rhlike_minion" as "hostname" 2s 137ms

And I enter "22" as "port" 51ms

And I enter "root" as "user" 56ms

And I enter "linux" as "password" 58ms

And I select "1-RH-LIKE-KEY" from "activationKeys" 72ms

And I select the hostname of "proxy" from "proxies" if present 63ms

And I click on "Bootstrap" 60ms

And I wait until I see "Bootstrap process initiated." text 33s 723ms

And I follow the left menu "Systems > System List > All" 148ms

And I wait until I see the name of "rhlike_minion", refreshing the page 30s 940ms

And I wait until onboarding is completed for "rhlike_minion" 51s 549ms

@proxy

Scenario:
Check connection from Red Hat-like minion to proxy

1s 19ms 4

Given I am on the Systems overview page of this "rhlike_minion" 802ms

When I follow "Details" in the content area 77ms

And I follow "Connection" in the content area 72ms

Then I should see "proxy" short hostname 66ms

@proxy

Scenario:
Check registration on proxy of Red Hat-like minion

1s 14ms 4

Given I am on the Systems overview page of this "proxy" 793ms

When I follow "Details" in the content area 63ms

And I follow "Proxy" in the content area 66ms

Then I should see "rhlike_minion" hostname 90ms

Scenario:
Subscribe the Red Hat-like minion to a base channel

20s 792ms 11

Warning: Radio button 'Fake-Base-Channel-RH-like' is already checked

Given I am on the Systems overview page of this "rhlike_minion" 774ms

When I follow "Software" in the content area 68ms

And I follow "Software Channels" in the content area 88ms

And I wait until I do not see "Loading..." text 70ms

And I check radio button "Fake-Base-Channel-RH-like" 177ms

And I wait until I do not see "Loading..." text 344ms

And I click on "Next" 68ms

Then I should see a "Confirm Software Channel Change" text 60ms

When I click on "Confirm" 79ms

Then I should see a "Changing the channels has been scheduled." text 300ms

And I wait until event "Subscribe channels scheduled by admin" is completed 18s 758ms

Scenario:
Detect latest Salt changes on the Red Hat-like minion

367ms 1

* Mon Feb 02 2026 Michael Calmer
- Rebuild because of maintenance release

* Mon Jan 19 2026 Marek Czernek
- Make syntax in httputil_test compatible with Python 3.6
- Fix KeyError in postgres module with PostgreSQL 17 (bsc#1254325)
- Added:
* fix-tornado-s-httputil_test-syntax-for-python-3.6.patch
* backport-add-maintain-m-privilege-to-postgres-module.patch

* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
* Drop dependency on saltbundlepy-apt
- Speed up wheel key.finger call (bsc#1240532)
- Add security patches (bsc#1254903,bsc#1254905,bsc#1254904)

When I query latest Salt changes on "rhlike_minion" 367ms

Scenario:
Check events history for failures on Red Hat-like minion

51s 734ms 2

Given I am on the Systems overview page of this "rhlike_minion" 826ms

Then I check for failed events on history event page 50s 908ms

@deblike_minion
Feature:Bootstrap a Debian-like minion and do some basic operations on it 3m 17s 530ms 7

Scenario:
Log in as admin user

451ms 1

Given I am authorized for the "Admin" section 451ms

Scenario:
Bootstrap a Debian-like minion

2m 2s 220ms 14

The hostname of deblike_minion is uyuni-master-deblike-minion.sumaci.aws
* Mon Feb 2 2026 Michael Calmer
- Rebuild because of maintenance release
* Mon Jan 19 2026 Marek Czernek
- Make syntax in httputil_test compatible with Python 3.6
- Fix KeyError in postgres module with PostgreSQL 17 (bsc#1254325)
- Added:
* fix-tornado-s-httputil_test-syntax-for-python-3.6.patch
* backport-add-maintain-m-privilege-to-postgres-module.patch
* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
* Drop dependency on saltbundlepy-apt
- Speed up wheel key.finger call (bsc#1240532)
- Add security patches (bsc#1254903,bsc#1254905,bsc#1254904)
- Simplify and speed up utils.find_json function (bsc#1246130)
- Added:

When I follow the left menu "Systems > Bootstrapping" 137ms

Then I should see a "Bootstrap Minions" text 70ms

When I enter the hostname of "deblike_minion" as "hostname" 4s 887ms

And I enter "22" as "port" 53ms

And I enter "root" as "user" 58ms

And I enter "linux" as "password" 64ms

And I select "1-DEBLIKE-KEY" from "activationKeys" 74ms

And I select the hostname of "proxy" from "proxies" if present 63ms

And I click on "Bootstrap" 64ms

And I wait until I see "Bootstrap process initiated." text 36s 84ms

And I follow the left menu "Systems > System List > All" 144ms

And I wait until I see the name of "deblike_minion", refreshing the page 1m 11s 693ms

And I wait until onboarding is completed for "deblike_minion" 7s 809ms

And I query latest Salt changes on Debian-like system "deblike_minion" 1s 13ms

@proxy

Scenario:
Check connection from the Debian-like minion to proxy

1s 23ms 4

Given I am on the Systems overview page of this "deblike_minion" 810ms

When I follow "Details" in the content area 75ms

And I follow "Connection" in the content area 68ms

Then I should see "proxy" short hostname 69ms

@proxy

Scenario:
Check registration on proxy of the Debian-like minion

1s 22ms 4

Given I am on the Systems overview page of this "proxy" 797ms

When I follow "Details" in the content area 64ms

And I follow "Proxy" in the content area 66ms

Then I should see "deblike_minion" hostname 94ms

Scenario:
Subscribe the Debian-like minion to a base channel

20s 618ms 11

Warning: Radio button 'Fake-Base-Channel-Debian-like' is already checked

Given I am on the Systems overview page of this "deblike_minion" 796ms

When I follow "Software" in the content area 70ms

And I follow "Software Channels" in the content area 62ms

And I wait until I do not see "Loading..." text 68ms

And I check radio button "Fake-Base-Channel-Debian-like" 135ms

And I wait until I do not see "Loading..." text 403ms

And I click on "Next" 83ms

Then I should see a "Confirm Software Channel Change" text 63ms

When I click on "Confirm" 76ms

Then I should see a "Changing the channels has been scheduled." text 291ms

And I wait until event "Subscribe channels scheduled by admin" is completed 18s 565ms

Scenario:
Detect latest Salt changes on the Debian-like minion

502ms 1

* Mon Feb 2 2026 Michael Calmer
- Rebuild because of maintenance release
* Mon Jan 19 2026 Marek Czernek
- Make syntax in httputil_test compatible with Python 3.6
- Fix KeyError in postgres module with PostgreSQL 17 (bsc#1254325)
- Added:
* fix-tornado-s-httputil_test-syntax-for-python-3.6.patch
* backport-add-maintain-m-privilege-to-postgres-module.patch
* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
* Drop dependency on saltbundlepy-apt
- Speed up wheel key.finger call (bsc#1240532)
- Add security patches (bsc#1254903,bsc#1254905,bsc#1254904)
- Simplify and speed up utils.find_json function (bsc#1246130)
- Added:

When I query latest Salt changes on Debian-like system "deblike_minion" 502ms

Scenario:
Check events history for failures on Debian-like minion

51s 691ms 2

Given I am on the Systems overview page of this "deblike_minion" 776ms

Then I check for failed events on history event page 50s 914ms

@build_host
Feature:Bootstrap a build host via the GUI 5m 32s 788ms 9

Scenario:
Clean up sumaform leftovers on build host

9s 915ms 1

When I perform a full salt minion cleanup on "build_host" 9s 915ms

Scenario:
Log in as admin user

476ms 1

Given I am authorized for the "Admin" section 476ms

Scenario:
Bootstrap a build host

48s 933ms 10

The hostname of build_host is uyuni-master-build-host.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 137ms

Then I should see a "Bootstrap Minions" text 70ms

When I enter the hostname of "build_host" as "hostname" 141ms

And I enter "22" as "port" 53ms

And I enter "root" as "user" 56ms

And I enter "linux" as "password" 60ms

And I select "1-BUILD-HOST-KEY-x86_64" from "activationKeys" 74ms

And I select the hostname of "proxy" from "proxies" if present 63ms

And I click on "Bootstrap" 63ms

And I wait until I see "Bootstrap process initiated." text 48s 210ms

Scenario:
Check the new bootstrapped build host in System Overview page

3m 7s 685ms 6

It took 2 seconds to contact the minion

When I follow the left menu "Salt > Keys" 132ms

Then I should see a "accepted" text 261ms

When I follow the left menu "Systems > System List > All" 182ms

And I wait at most 500 seconds until I see the name of "build_host", refreshing the page 28s 72ms

And I wait at most 500 seconds until onboarding is completed for "build_host" 2m 37s 141ms

Then the Salt master can reach "build_host" 1s 895ms

@proxy

Scenario:
Check connection from build host to proxy

1s 118ms 4

Given I am on the Systems overview page of this "build_host" 901ms

When I follow "Details" in the content area 79ms

And I follow "Connection" in the content area 65ms

Then I should see "proxy" short hostname 71ms

@proxy

Scenario:
Check registration on build host of minion

1s 35ms 4

Given I am on the Systems overview page of this "proxy" 806ms

When I follow "Details" in the content area 62ms

And I follow "Proxy" in the content area 67ms

Then I should see "build_host" hostname 98ms

Scenario:
Detect latest Salt changes on the SLES build host

769ms 1

* Mon Feb 02 2026 mc@suse.com
- Rebuild because of maintenance release

* Mon Jan 19 2026 marek.czernek@suse.com
- Make syntax in httputil_test compatible with Python 3.6
- Fix KeyError in postgres module with PostgreSQL 17 (bsc#1254325)
- Added:
* fix-tornado-s-httputil_test-syntax-for-python-3.6.patch
* backport-add-maintain-m-privilege-to-postgres-module.patch

* Wed Jan 14 2026 marek.czernek@suse.com
- Use internal deb classes instead of external aptsource lib
* Drop dependency on saltbundlepy-apt
- Speed up wheel key.finger call (bsc#1240532)
- Add security patches (bsc#1254903,bsc#1254905,bsc#1254904)

When I query latest Salt changes on "build_host" 769ms

Scenario:
Check that the build host is a build host

1s 59ms 3

Given I am on the Systems overview page of this "build_host" 868ms

Then I should see a "[Container Build Host]" text 95ms

Then I should see a "[OS Image Build Host]" text 94ms

Scenario:
Check events history for failures on SLES build host

1m 21s 795ms 2

Given I am on the Systems overview page of this "build_host" 869ms

Then I check for failed events on history event page 1m 20s 925ms

@transactional_server
Feature:SELinux debugging < 1ms 1

In order for the server to behave correctly after a reboot
I want to be sure that there is no wrong SELinux label

Scenario:
No previous operation has created wrong SELinux label

< 1ms 1

Then files on container volumes should all have the proper SELinux label 0s

@new_issue
Feature:Debug the server after the testsuite has run 20s 966ms 5

Scenario:
Call spacewalk-debug on server

16s 839ms 1

When I execute spacewalk-debug on the server 16s 839ms

Scenario:
Check the tomcat logs on server

702ms 1

Then the tomcat logs should not contain errors 702ms

Scenario:
Check salt event log for failures on server

2s 34ms 1

Then the salt event log on server should contain no failures 2s 34ms

Scenario:
Check the taskomatic logs on server

702ms 1

Then the taskomatic logs should not contain errors 702ms

Scenario:
Check for out of memory errors

687ms 1

Then the log messages should not contain out of memory errors 687ms

Feature:Debug the clients after the testsuite has run 1m 47s 276ms 1

Scenario:
Extract the logs from all our clients

1m 47s 276ms 1

When I extract the log files from all our active nodes 1m 47s 276ms

@srv_scc_access_logging
Feature:Test for excessive SCC accesses < 1ms 2

Scenario:
Count UI SCC accesses in rhn_web_ui.log

< 1ms 1

Then the word "scc.suse.com" does not occur more than 100 times in "/var/log/rhn/rhn_web_ui.log" on "server" 0s

Scenario:
Count Taskomatic SCC accesses in rhn_taskomatic_daemon.log

< 1ms 1

Then the word "scc.suse.com" does not occur more than 50 times in "/var/log/rhn/rhn_taskomatic_daemon.log" on "server" 0s

All Scenarios

201

Passed Scenarios

162

Failed Scenarios

0

Skipped Scenarios

39

@proxy Scenario:The proxy is healthy 4s 528ms 4

@sle_minion Scenario:The minion is healthy 6s 542ms 4

@build_host Scenario:The build host is healthy 4s 565ms 4

@ssh_minion Scenario:The SSH minion is healthy 6s 646ms 4

@rhlike_minion Scenario:The Red Hat-like minion is healthy 3s 211ms 4

@deblike_minion Scenario:The Debian-like minion is healthy 5s 923ms 4

@skip_if_cloud Scenario:The external resources can be reached < 1ms 3

@server_http_proxy Scenario:The HTTP proxy is working < 1ms 1

@auth_registry Scenario:The registry with authentication is healthy 652ms 1

@no_auth_registry Scenario:The registry without authentication is healthy 635ms 1

@custom_download_endpoint Scenario:The custom download endpoint is working 633ms 1

@skip_if_containerized_server Scenario:Create admin user and first organization < 1ms 12

@server_http_proxy Scenario:Setup HTTP proxy < 1ms 9

@scc_credentials @no_mirror Scenario:Enter valid SCC credentials < 1ms 6

@no_auth_registry Scenario:Create an image store without credentials 3s 7ms 7

@scc_credentials Feature:List available channels and enable them 1m 38s 737ms 5 1

@proxy @susemanager Scenario:List all products for SUSE Multi-Linux Manager < 1ms 6

@scc_credentials Scenario:Refresh SCC 27s 847ms 1

@scc_credentials Scenario:Let the products page appear 2s 794ms 6

@scc_credentials Scenario:Use the products and architecture filters 2s 406ms 7

@scc_credentials @susemanager Scenario:View the channels list in the products page < 1ms 9

@scc_credentials @susemanager Scenario:Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools < 1ms 30

@uyuni Scenario:Partially add openSUSE Tumbleweed product, only including the required packages to generate the bootstrap repository 2m 1s 297ms 4

@containerized_server @proxy @uyuni Scenario:Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools 54s 835ms 2

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 61m 21s 699ms 20

@proxy @susemanager @transactional_server Scenario:Add SL Micro 6.1 as base OS for proxy < 1ms 13

@proxy @susemanager @skip_if_transactional_server Scenario:Add SLES 15 SP7 as base OS for proxy < 1ms 11

@proxy @susemanager @transactional_server Scenario:Add SUSE MLM Proxy Extension 5.1 with SL Micro 6.1 as base OS < 1ms 13

@proxy @susemanager @skip_if_transactional_server Scenario:Add SUSE MLM Proxy Extension 5.1 with SLES 15 SP7 as base OS < 1ms 12

@proxy @susemanager @transactional_server Scenario:Add SUSE MLM Retail Branch Server Extension 5.1 with SL Micro 6.1 as base OS < 1ms 13

@proxy @susemanager @skip_if_transactional_server Scenario:Add SUSE MLM Retail Branch Server Extension 5.1 with SLES 15 SP7 as base OS < 1ms 12

@scc_credentials @susemanager Scenario:Installer update channels got enabled when products were added < 1ms 2

@scc_credentials @skip_if_github_validation Scenario:Detect product loading issues from the UI 54s 269ms 7

@scc_credentials @skip_if_github_validation Scenario:Report the synchronization duration for SLES 15 SP7 < 1ms 1

@sle_minion Scenario:Add a SUSE fake child channel to the SUSE Product base channel 1s 74ms 10

@pxeboot_minion @uyuni @scc_credentials Scenario:Add a fake terminal child channel to the SUSE Product base channel < 1ms 10

@deblike_minion Scenario:Add Debian-like AMD64 base channel 11s 632ms 11

@rhlike_minion Scenario:Add a RedHat-like base channel 1s 457ms 10

@rhlike_minion Scenario:Add a fake AppStream base channel 1s 56ms 10

@rhlike_minion Scenario:Create a fake AppStream repository 1s 26ms 7

@rhlike_minion Scenario:Disable metadata check for the fake AppStream repository 10s 904ms 6

@sle_minion Scenario:Add the fake RPM repository to the SUSE fake child channel 2s 143ms 9

@rhlike_minion Scenario:Add the fake RPM repository to the RedHat-like base channel 2s 631ms 9

@rhlike_minion Scenario:Add the fake AppStream repository to the AppStream base channel 2s 553ms 9

@sle_minion Scenario:Add the repository to the SUSE-like child channel 1s 626ms 6

@deblike_minion Scenario:Create a fake repository for Debian-like 752ms 7

@deblike_minion Scenario:Add the repository to the Debian-like base channel 2s 52ms 6

@pxeboot_minion @uyuni @scc_credentials Scenario:Add the repository to the terminal child channel < 1ms 9

@skip_if_github_validation Feature:Create custom channels with development repositories 29s 326ms 9

@sle_minion Scenario:Create a custom channel for SUSE minions 1s 188ms 10

@sle_minion Scenario:Create custom repositories inside the SUSE custom channel 6s 511ms 1

@uyuni @build_host Scenario:Create a custom channel for Build Host 1s 721ms 10

@uyuni @build_host Scenario:Create custom repositories inside the Build Host custom channel 4s 635ms 1

@deblike_minion Scenario:Create a custom channel for Debian-like minions 1s 100ms 10

@deblike_minion Scenario:Create custom repositories inside the Debian-like custom channel 6s 995ms 1

@rhlike_minion Scenario:Create a custom channel for RH-like minions 1s 658ms 10

@rhlike_minion Scenario:Create custom repositories inside the RH-like custom channel 5s 16ms 1

@sle_minion Scenario:Synchronize Fake-RPM-SUSE-Channel channel 3s 901ms 9

@sle_minion Scenario:Verify state of Fake-RPM-SUSE-Channel channel 4s 855ms 2

@skip_if_github_validation Scenario:Synchronize Fake-Child-Channel-i586 channel 3s 730ms 9

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 3s 620ms 9

@deblike_minion Scenario:Synchronize Fake-Base-Channel-Debian-like channel 4s 225ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-RH-like channel 4s 264ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-AppStream channel 4s 142ms 9

@pxeboot_minion @uyuni @scc_credentials Scenario:Synchronize the repository in the terminal channel < 1ms 9

@pxeboot_minion @uyuni @scc_credentials Scenario:Verify state of Fake-RPM-Terminal-Channel custom channel < 1ms 2

@skip_if_github_validation Feature:Synchronize development channels 16s 477ms 4

@sle_minion Scenario:Synchronize Devel-SUSE-Channel channel 3s 679ms 9

@deblike_minion Scenario:Synchronize Devel-Debian-like-Channel channel 4s 304ms 9

@rhlike_minion Scenario:Synchronize Devel-RH-like-Channel channel 4s 250ms 9

@build_host @uyuni Scenario:Synchronize Devel-Build-Host-Channel channel 4s 243ms 9

@sle_minion Scenario:Create an activation key with a channel 2s 213ms 2

@proxy

Scenario:
The proxy is healthy

4s 528ms 4

@sle_minion

Scenario:
The minion is healthy

6s 542ms 4

@build_host

Scenario:
The build host is healthy

4s 565ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 646ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 211ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 923ms 4

@skip_if_cloud

Scenario:
The external resources can be reached

< 1ms 3

@server_http_proxy

Scenario:
The HTTP proxy is working

< 1ms 1

@auth_registry

Scenario:
The registry with authentication is healthy

652ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

635ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

633ms 1

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

@no_auth_registry

Scenario:
Create an image store without credentials

3s 7ms 7

@scc_credentials
Feature:List available channels and enable them 1m 38s 737ms 5 1

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

27s 847ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 794ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 406ms 7

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

@scc_credentials @susemanager

Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools

< 1ms 30

@uyuni

Scenario:
Partially add openSUSE Tumbleweed product, only including the required packages to generate the bootstrap repository

2m 1s 297ms 4

@containerized_server @proxy @uyuni

Scenario:
Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools

54s 835ms 2

@scc_credentials @uyuni @build_host

Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature

61m 21s 699ms 20

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

@proxy @susemanager @transactional_server

Scenario:
Add SUSE MLM Proxy Extension 5.1 with SL Micro 6.1 as base OS

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SUSE MLM Proxy Extension 5.1 with SLES 15 SP7 as base OS

< 1ms 12

@proxy @susemanager @transactional_server

Scenario:
Add SUSE MLM Retail Branch Server Extension 5.1 with SL Micro 6.1 as base OS

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SUSE MLM Retail Branch Server Extension 5.1 with SLES 15 SP7 as base OS

< 1ms 12

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

54s 269ms 7

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

@sle_minion

Scenario:
Add a SUSE fake child channel to the SUSE Product base channel

1s 74ms 10

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add a fake terminal child channel to the SUSE Product base channel

< 1ms 10

@deblike_minion

Scenario:
Add Debian-like AMD64 base channel

11s 632ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 457ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 56ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 26ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 904ms 6

@sle_minion

Scenario:
Add the fake RPM repository to the SUSE fake child channel

2s 143ms 9

@rhlike_minion

Scenario:
Add the fake RPM repository to the RedHat-like base channel

2s 631ms 9

@rhlike_minion

Scenario:
Add the fake AppStream repository to the AppStream base channel

2s 553ms 9

@sle_minion

Scenario:
Add the repository to the SUSE-like child channel

1s 626ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

752ms 7

@deblike_minion

Scenario:
Add the repository to the Debian-like base channel

2s 52ms 6

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

@skip_if_github_validation
Feature:Create custom channels with development repositories 29s 326ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 188ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 511ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 721ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 635ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 100ms 10

@deblike_minion

Scenario:
Create custom repositories inside the Debian-like custom channel

6s 995ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 658ms 10

@rhlike_minion

Scenario:
Create custom repositories inside the RH-like custom channel

5s 16ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 901ms 9

@sle_minion

Scenario:
Verify state of Fake-RPM-SUSE-Channel channel

4s 855ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 730ms 9

@sle_minion

Scenario:
Synchronize Fake-Child-Channel-SUSE-like channel

3s 620ms 9

@deblike_minion

Scenario:
Synchronize Fake-Base-Channel-Debian-like channel

4s 225ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-RH-like channel

4s 264ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 142ms 9

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Synchronize the repository in the terminal channel

< 1ms 9

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Verify state of Fake-RPM-Terminal-Channel custom channel

< 1ms 2

@skip_if_github_validation
Feature:Synchronize development channels 16s 477ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

3s 679ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 304ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 250ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 243ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 213ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

2s 93ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

2s 644ms 2

@ssh_minion

Scenario:
Create an activation key with a channel for salt-ssh

1s 937ms 2

@ssh_minion

Scenario:
Create an activation key with a channel for salt-ssh via tunnel

1s 843ms 2

@proxy

Scenario:
Create an activation key for the proxy

2s 43ms 2

@build_host

Scenario:
Create an activation key for the build host

2s 706ms 3

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 163ms 2

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20