Cucumber Feature Report

All Scenarios

201

Passed Scenarios

150

Failed Scenarios

12

Skipped Scenarios

39

Execution Time: 79m 46s 290ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 45s 188ms 10 2

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

Scenario:
The server is healthy

11s 945ms 19

Then "server" should have a FQDN 386ms

And reverse resolution should work for "server" 632ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 522ms 4

Then "proxy" should have a FQDN 2s 979ms

And reverse resolution should work for "proxy" 322ms

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

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

@sle_minion

Scenario:
The minion is healthy

8s 36ms 4

Then "sle_minion" should have a FQDN 5s 945ms

And reverse resolution should work for "sle_minion" 468ms

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

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

@build_host

Scenario:
The build host is healthy

3s 796ms 4

Then "build_host" should have a FQDN 2s 507ms

And reverse resolution should work for "build_host" 220ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

5s 937ms 4

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

And reverse resolution should work for "ssh_minion" 413ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 116ms 4

Then "rhlike_minion" should have a FQDN 1s 927ms

And reverse resolution should work for "rhlike_minion" 186ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 863ms 4

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

And reverse resolution should work for "deblike_minion" 212ms

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

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

@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

656ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

677ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

636ms 1

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

Feature:Very first settings 48s 593ms 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

647ms 1

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

@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 651ms 1

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

Scenario:
Wait for refresh of list of products to finish

3s 545ms 1

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

Scenario:
Create testing username

2s 237ms 12

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

And I follow "Create User" 580ms

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

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

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

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

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

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

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

And I click on "Create Login" 912ms

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

And I should see a "testing" link 12ms

Scenario:
Grant testing user administrative priviledges

1s 746ms 10

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

And I follow "testing" 506ms

And I check "role_org_admin" 82ms

And I check "role_system_group_admin" 73ms

And I check "role_channel_admin" 74ms

And I check "role_activation_key_admin" 74ms

And I check "role_config_admin" 75ms

And I click on "Update" 642ms

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

And I should see a "testing" text 71ms

@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

764ms 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" 764ms

Feature:Turn "disable_local_repos" feature on highstate off 3s 636ms 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 636ms 1

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

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 931ms 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 460ms 5

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

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

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

And I click on "Save Preferences" 724ms

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

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

3s 470ms 5

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

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

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

And I click on "Save Preferences" 620ms

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

Feature:Prepare server for using Kiwi 4s 246ms 1

Scenario:
Create a Kiwi user with image administrators rights

4s 246ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights

2s 313ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

3s 243ms 7

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

And I follow "Create" 476ms

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

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

And I click on "create-btn" 121ms

Then I wait until table row contains a "galaxy-registry" text 2s 232ms

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

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

Scenario:
Log in as admin user

37s 709ms 1

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

Scenario:
Disable scheduled reposyncs

4s 467ms 5

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

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

And I choose "disabled" 66ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 587ms 5

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

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

And I choose "disabled" 46ms

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

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

@scc_credentials
Feature:List available channels and enable them 1m 39s 359ms 5 1

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

Scenario:
List available channels

33s 479ms 5

When I refresh SCC 31s 131ms

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

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 501ms 4

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

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 482ms 2

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

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 450ms 4

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

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 446ms 3

When I remove the mgr-sync cache file 668ms

And I execute mgr-sync refresh 1m 777ms

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

Feature:Synchronize products in the products page of the Setup Wizard 51m 41s 756ms 8 9

@scc_credentials

Scenario:
Refresh SCC

27s 924ms 1

When I refresh SCC 27s 924ms

@scc_credentials

Scenario:
Let the products page appear

3s 27ms 6

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

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

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

Then I should see a "Arch" text 121ms

And I should see a "Channels" text 122ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 360ms 7

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

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

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

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

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

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

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

@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 2s 711ms 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 847ms

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

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

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

@containerized_server @proxy @uyuni

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

45s 129ms 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-x86_64 finished reposync
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 finished reposync
Channel uyuni-proxy-devel-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" 22s 367ms

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

@scc_credentials @uyuni @build_host

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

47m 36s 401ms 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
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
1 minutes out of 102 waiting for 'sles15-sp7' channels to finish 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
Channel sle-module-basesystem15-sp7-updates-x86_64 finished 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-pool-x86_64 finished reposync
Channel sle-module-server-applications15-sp7-pool-x86_64 finished reposync
14 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-server-applications15-sp7-updates-x86_64 finished reposync
Channel sle-module-python3-15-sp7-pool-x86_64 finished reposync
15 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
Channel sle-module-systems-management-15-sp7-updates-x86_64 finished reposync
16 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-desktop-applications15-sp7-updates-x86_64 finished reposync
17 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
18 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
19 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
20 minutes out of 102 waiting for 'sles15-sp7' channels to finish 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
Channel sle-module-desktop-applications15-sp7-pool-x86_64 finished 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
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
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
Channel sle-module-devtools15-sp7-updates-x86_64 finished reposync
33 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-devtools15-sp7-pool-x86_64 finished reposync
All channels for sles15-sp7 have been fully synced

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 55ms

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

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

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

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 47m 14s 146ms

@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

44s 202ms 7

Given I am authorized for the "Admin" section 1s 273ms

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

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

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

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

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

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

@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 414ms 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

493ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 761ms 10

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

And I follow "Create Channel" 317ms

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

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

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

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

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

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

And I click on "Create Channel" 606ms

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

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

1s 595ms 10

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

And I follow "Create Channel" 309ms

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

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

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

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

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

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

And I click on "Create Channel" 570ms

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

@sle_minion

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

1s 558ms 10

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

And I follow "Create Channel" 306ms

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

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

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

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

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

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

And I click on "Create Channel" 572ms

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

Scenario:
Add a fake base channel for i586

1s 55ms 10

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

And I follow "Create Channel" 309ms

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

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

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" 132ms

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

And I click on "Create Channel" 56ms

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

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

1s 51ms 10

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

And I follow "Create Channel" 311ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

Scenario:
Add a test base channel for x86_64

1s 57ms 10

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

And I follow "Create Channel" 322ms

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

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

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

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

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

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

And I click on "Create Channel" 63ms

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

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

1s 561ms 10

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

And I follow "Create Channel" 341ms

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

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

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

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

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

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

And I click on "Create Channel" 505ms

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

@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 667ms 11

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

And I follow "Create Channel" 335ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 79ms

And I click on "Create Channel" 547ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 521ms 10

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

And I follow "Create Channel" 335ms

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

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

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

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

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

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

And I click on "Create Channel" 513ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 88ms 10

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

And I follow "Create Channel" 350ms

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

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

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

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

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

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

And I click on "Create Channel" 59ms

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

Feature:Create fake repositories for each fake child channel 51s 777ms 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

493ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 181ms 7

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

And I follow "Create Repository" 315ms

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

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

And I click on "Create Repository" 451ms

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

And I should see "metadataSigned" as checked 18ms

Scenario:
Disable metadata check for the fake RPM repository

11s 8ms 6

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

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

And I uncheck "metadataSigned" 10s 71ms

And I click on "Update Repository" 477ms

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

And I should see "metadataSigned" as unchecked 14ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

946ms 7

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

And I follow "Create Repository" 223ms

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

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

And I click on "Create Repository" 52ms

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

And I should see "metadataSigned" as checked 15ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 900ms 6

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

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

And I uncheck "metadataSigned" 10s 57ms

And I click on "Update Repository" 449ms

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

And I should see "metadataSigned" as unchecked 14ms

@sle_minion

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

2s 39ms 9

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

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

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

And I click on "Update Channel" 605ms

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

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

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

And I click on "Save Repositories" 560ms

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

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

2s 685ms 9

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

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

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

And I click on "Update Channel" 591ms

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

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

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

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

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

@rhlike_minion

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

2s 659ms 9

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

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

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

And I click on "Update Channel" 84ms

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

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

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

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

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

@rhlike_minion

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

2s 655ms 9

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

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

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

And I click on "Update Channel" 575ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 102ms 7

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

And I follow "Create Repository" 310ms

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

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

And I uncheck "metadataSigned" 10s 73ms

And I click on "Create Repository" 431ms

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

Scenario:
Add the repository to the i586 channel

2s 70ms 9

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

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

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" 572ms

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

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

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

And I click on "Save Repositories" 600ms

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

@sle_minion

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

1s 660ms 6

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 101ms 7

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

And I follow "Create Repository" 308ms

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

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

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

And I click on "Create Repository" 436ms

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

@deblike_minion

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

1s 270ms 6

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

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

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

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

And I click on "Save Repositories" 644ms

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

@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 30s 521ms 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

503ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 737ms 10

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

And I follow "Create Channel" 374ms

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

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

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

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

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

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

And I click on "Create Channel" 552ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

8s 262ms 1

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

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 654ms 10

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

And I follow "Create Channel" 377ms

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

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

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

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

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

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

And I click on "Create Channel" 535ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

3s 968ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 73ms 10

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

And I follow "Create Channel" 274ms

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

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

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

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

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

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

And I click on "Create Channel" 58ms

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

@deblike_minion

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

7s 271ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 638ms 10

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

And I follow "Create Channel" 382ms

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

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

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

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

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

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

And I click on "Create Channel" 545ms

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

@rhlike_minion

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

4s 411ms 1

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

Feature:Synchronize fake channels 57s 561ms 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

1s 923ms 2

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

And I enable source package syncing 1s 486ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 795ms 9

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

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

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

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

And I follow "Sync" 334ms

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 791ms

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

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

@sle_minion

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

4s 799ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 649ms 9

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

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

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

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

And I follow "Sync" 330ms

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 781ms

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

4s 193ms 9

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

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

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

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

And I follow "Sync" 773ms

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 801ms

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

And I wait until the channel "test-child-channel-x86_64" has been synced 440ms

@sle_minion

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

14s 603ms 9

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

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

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

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

And I follow "Sync" 673ms

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 785ms

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

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

@deblike_minion

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

3s 791ms 9

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

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

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

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

And I follow "Sync" 342ms

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 795ms

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

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

@rhlike_minion

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

4s 293ms 9

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

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

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

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

And I follow "Sync" 864ms

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 806ms

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 156ms 9

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

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

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

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

And I follow "Sync" 685ms

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 799ms

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

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

@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 473ms 6

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

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

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

And I click on "Single Run Schedule" 1s 532ms

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

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

Scenario:
Refresh the channel's repository data

4s 884ms 6

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

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

And I follow "channel-repodata-bunch" 368ms

And I click on "Single Run Schedule" 1s 373ms

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

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

Scenario:
Cleanup disable source package syncing

995ms 1

Then I disable source package syncing 995ms

@skip_if_github_validation
Feature:Synchronize development channels 16s 611ms 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 914ms 9

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

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

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

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

And I follow "Sync" 516ms

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

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

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 352ms

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 152ms 9

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

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

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

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

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 67ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 338ms 9

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

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

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

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

And I follow "Sync" 936ms

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 833ms

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 205ms 9

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

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

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

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

And I follow "Sync" 765ms

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

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

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

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

Feature:Create activation keys 18s 375ms 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

526ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

2s 99ms 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 561ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 485ms 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" 910ms

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

2s 665ms 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 273ms

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

@ssh_minion

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

2s 607ms 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" 1s 308ms

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

@ssh_minion

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

1s 992ms 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" 944ms

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 69ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

2s 592ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 338ms 2

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

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

Feature:Update activation keys 24s 535ms 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

474ms 1

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

@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 845ms 10

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

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

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

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

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

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 1s 48ms

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

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

And I click on "Update Activation Key" 644ms

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

@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 315ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 562ms

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

@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

2s 260ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 600ms

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

@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 400ms 20

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

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

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

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

And I wait for child channels to appear 519ms

And I include the recommended child channels 175ms

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

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 18ms

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

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

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 18ms

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

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

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

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

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

And I click on "Update Activation Key" 656ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 262ms 9

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

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

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

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

And I wait for child channels to appear 304ms

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

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

And I click on "Update Activation Key" 602ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 328ms 9

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

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

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

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

And I wait for child channels to appear 316ms

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

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

And I click on "Update Activation Key" 586ms

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

3s 164ms 16

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

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

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

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

And I wait for child channels to appear 534ms

And I include the recommended child channels 162ms

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 14ms

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

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

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

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

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

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

And I click on "Update Activation Key" 610ms

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

@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 741ms 6

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

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

And I wait for child channels to appear 899ms

And I check "Devel-SUSE-Channel" 79ms

And I click on "Update Activation Key" 559ms

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

@skip_if_github_validation @deblike_minion

Scenario:
Update Debian-like key with to include dev child channel

1s 831ms 6

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

And I follow "Debian-like Test Key" in the content area 67ms

And I wait for child channels to appear 972ms

And I check "Devel-Debian-like-Channel" 75ms

And I click on "Update Activation Key" 581ms

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 908ms 6

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

And I follow "RedHat like Test Key" in the content area 73ms

And I wait for child channels to appear 961ms

And I check "Devel-RH-like-Channel" 106ms

And I click on "Update Activation Key" 637ms

Then I should see a "Activation key RedHat like Test Key has been modified" text 70ms

Feature:Create bootstrap repositories 8s 854ms 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 354ms 1

When I create the bootstrap repositories including custom channels 2s 354ms

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

2s 131ms 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 131ms

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 93ms 1

When I create the bootstrap repository for "proxy" on the server 2s 93ms

@build_host

Scenario:
Create the bootstrap repository for Build Host

2s 275ms 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 275ms

@containerized_server @scope_containerized_proxy @proxy
Feature:Setup containerized proxy 3m 29s 541ms 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 505ms 1

When I perform a full salt minion cleanup on "proxy" 6s 505ms

@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 498ms 1

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

Scenario:
Bootstrap the proxy host as a salt minion

36s 209ms 9

The hostname of proxy is uyuni-master-proxy.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 133ms

Then I should see a "Bootstrap Minions" text 68ms

When I enter the hostname of "proxy" as "hostname" 114ms

And I enter "22" as "port" 47ms

And I enter "root" as "user" 53ms

And I enter "linux" as "password" 51ms

And I select "1-PROXY-KEY-x86_64" from "activationKeys" 71ms

And I click on "Bootstrap" 61ms

And I wait until I see "Bootstrap process initiated." text 35s 608ms

@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 628ms 1

When I wait until onboarding is completed for "proxy" 1m 22s 628ms

Scenario:
Generate containerized proxy configuration

11s 599ms 2

When I generate the configuration "/tmp/proxy_container_config.tar.gz" of containerized proxy on the server 8s 728ms

And I copy the configuration "/tmp/proxy_container_config.tar.gz" of containerized proxy from the server to the proxy 2s 871ms

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

19s 336ms 1

When I run "mgrpxy install podman /tmp/proxy_container_config.tar.gz" on "proxy" 19s 336ms

Scenario:
Wait until containerized proxy service is active

4s 20ms 10

And I wait until "uyuni-proxy-pod" service is active on "proxy" 599ms

And I wait until "uyuni-proxy-httpd" service is active on "proxy" 517ms

And I wait until "uyuni-proxy-salt-broker" service is active on "proxy" 456ms

And I wait until "uyuni-proxy-squid" service is active on "proxy" 406ms

And I wait until "uyuni-proxy-ssh" service is active on "proxy" 390ms

And I wait until "uyuni-proxy-tftpd" service is active on "proxy" 288ms

And I wait until port "8022" is listening on "proxy" container 302ms

And I wait until port "80" is listening on "proxy" container 315ms

And I wait until port "443" is listening on "proxy" container 333ms

And I visit "Proxy" endpoint of this "proxy" 410ms

Scenario:
The containerized proxy should be registered automatically

743ms 2

When I follow the left menu "Systems" 60ms

And I wait until I see the name of "proxy", refreshing the page 683ms

Scenario:
Check if Monitoring can be enabled on the containerized proxy

10s 998ms 3

Given I am on the Systems overview page of this "proxy" 913ms

When I follow "Properties" in the content area 73ms

Then the "monitoring_entitled" checkbox should be disabled 10s 11ms

@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

@deblike_minion
Feature:Bootstrap a Debian-like minion and do some basic operations on it 1m 15s 637ms 1 6

Scenario:
Log in as admin user

21s 763ms 1

Given I am authorized for the "Admin" section 21s 763ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:592:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:460:in `/^I am authorized for the "([^"]*)" section$/'
features/init_clients/min_deblike_salt.feature:11:in `I am authorized for the "Admin" section'

Scenario:
Bootstrap a Debian-like minion

42s 898ms 13 1

When I follow the left menu "Systems > Bootstrapping" 42s 898ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:414:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:406:in `each'
./features/step_definitions/navigation_steps.rb:406:in `each_with_index'
./features/step_definitions/navigation_steps.rb:406:in `/^I follow the left menu "([^"]*)"$/'
features/init_clients/min_deblike_salt.feature:14:in `I follow the left menu "Systems ) Bootstrapping"'

Then I should see a "Bootstrap Minions" text 0s

When I enter the hostname of "deblike_minion" as "hostname" 0s

And I enter "22" as "port" 0s

And I enter "root" as "user" 0s

And I enter "linux" as "password" 0s

And I select "1-DEBLIKE-KEY" from "activationKeys" 0s

And I select the hostname of "proxy" from "proxies" if present 0s

And I click on "Bootstrap" 0s

And I wait until I see "Bootstrap process initiated." text 0s

And I follow the left menu "Systems > System List > All" 0s

And I wait until I see the name of "deblike_minion", refreshing the page 0s

And I wait until onboarding is completed for "deblike_minion" 0s

And I query latest Salt changes on Debian-like system "deblike_minion" 0s

@proxy

Scenario:
Check connection from the Debian-like minion to proxy

5s 99ms 3 1

Given I am on the Systems overview page of this "deblike_minion" 5s 99ms Show Error +

                                            
 No system found for hostname: uyuni-master-deblike-minion.sumaci.aws (RuntimeError)
./features/support/commonlib.rb:421:in `get_system_id'
./features/step_definitions/navigation_steps.rb:473:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/min_deblike_salt.feature:31:in `I am on the Systems overview page of this "deblike_minion"'

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

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

Then I should see "proxy" short hostname 0s

@proxy

Scenario:
Check registration on proxy of the Debian-like minion

3s 999ms 3 1

Given I am on the Systems overview page of this "proxy" 3s 999ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:475:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/min_deblike_salt.feature:38:in `I am on the Systems overview page of this "proxy"'

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

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

Then I should see "deblike_minion" hostname 0s

Scenario:
Subscribe the Debian-like minion to a base channel

518ms 10 1

Given I am on the Systems overview page of this "deblike_minion" 518ms Show Error +

                                            
 No system found for hostname: uyuni-master-deblike-minion.sumaci.aws (RuntimeError)
./features/support/commonlib.rb:421:in `get_system_id'
./features/step_definitions/navigation_steps.rb:473:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/min_deblike_salt.feature:44:in `I am on the Systems overview page of this "deblike_minion"'

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

And I follow "Software Channels" in the content area 0s

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

And I check radio button "Fake-Base-Channel-Debian-like" 0s

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

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

And I wait until event "Subscribe channels scheduled by admin" is completed 0s

Scenario:
Detect latest Salt changes on the Debian-like minion

472ms 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
* 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:
* 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 Debian-like system "deblike_minion" 472ms

Scenario:
Check events history for failures on Debian-like minion

887ms 1 1

Given I am on the Systems overview page of this "deblike_minion" 887ms Show Error +

                                            
 No system found for hostname: uyuni-master-deblike-minion.sumaci.aws (RuntimeError)
./features/support/commonlib.rb:421:in `get_system_id'
./features/step_definitions/navigation_steps.rb:473:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/min_deblike_salt.feature:60:in `I am on the Systems overview page of this "deblike_minion"'

Then I check for failed events on history event page 0s

@rhlike_minion
Feature:Bootstrap a Red Hat-like minion and do some basic operations on it 2m 15s 653ms 1 6

Scenario:
Log in as admin user

41s 914ms 1

Given I am authorized for the "Admin" section 41s 914ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:592:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:460:in `/^I am authorized for the "([^"]*)" section$/'
features/init_clients/min_rhlike_salt.feature:11:in `I am authorized for the "Admin" section'

Scenario:
Bootstrap a Red Hat-like minion

33s 35ms 12 1

When I follow the left menu "Systems > Bootstrapping" 33s 35ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/parent::div/parent::li" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:414:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:406:in `each'
./features/step_definitions/navigation_steps.rb:406:in `each_with_index'
./features/step_definitions/navigation_steps.rb:406:in `/^I follow the left menu "([^"]*)"$/'
features/init_clients/min_rhlike_salt.feature:14:in `I follow the left menu "Systems ) Bootstrapping"'

Then I should see a "Bootstrap Minions" text 0s

When I enter the hostname of "rhlike_minion" as "hostname" 0s

And I enter "22" as "port" 0s

And I enter "root" as "user" 0s

And I enter "linux" as "password" 0s

And I select "1-RH-LIKE-KEY" from "activationKeys" 0s

And I select the hostname of "proxy" from "proxies" if present 0s

And I click on "Bootstrap" 0s

And I wait until I see "Bootstrap process initiated." text 0s

And I follow the left menu "Systems > System List > All" 0s

And I wait until I see the name of "rhlike_minion", refreshing the page 0s

And I wait until onboarding is completed for "rhlike_minion" 0s

@proxy

Scenario:
Check connection from Red Hat-like minion to proxy

2s 485ms 3 1

Given I am on the Systems overview page of this "rhlike_minion" 2s 485ms Show Error +

                                            
 No system found for hostname: uyuni-master-rhlike-minion.sumaci.aws (RuntimeError)
./features/support/commonlib.rb:421:in `get_system_id'
./features/step_definitions/navigation_steps.rb:473:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/min_rhlike_salt.feature:30:in `I am on the Systems overview page of this "rhlike_minion"'

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

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

Then I should see "proxy" short hostname 0s

@proxy

Scenario:
Check registration on proxy of Red Hat-like minion

29s 41ms 2 2 1

Requested /rhn/systems/details/Overview.do?sid=1000010000, got https://uyuni-master-server.sumaci.aws/rhn/manager/login?url_bounce=%2Frhn%2Fsystems%2Fdetails%2FOverview.do%3Fsid%3D1000010000&request_method=GET

Given I am on the Systems overview page of this "proxy" 4s 457ms

When I follow "Details" in the content area 10s 18ms Show Error +

                                            
 Unable to find link "Details" within #(Capybara::Node::Element tag="section" path="/HTML/BODY[1]/DIV[1]/DIV[1]/SECTION[1]") (Capybara::ElementNotFound)
./features/support/commonlib.rb:198:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:339:in `/^I follow "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:361:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:360:in `/^I follow "([^"]*)" in the (.+)$/'
features/init_clients/min_rhlike_salt.feature:38:in `I follow "Details" in the content area'

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

Then I should see "rhlike_minion" hostname 0s

14s 564ms Show Info +

13:16:49:000 - 13:17:03:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/login?url_bounce=%2Frhn%2Fsystems%2Fdetails%2FOverview.do%3Fsid%3D1000010000&request_method=GET

Screenshot +

Scenario:
Subscribe the Red Hat-like minion to a base channel

14s 698ms 1 10 1

Given I am on the Systems overview page of this "rhlike_minion" 505ms Show Error +

                                            
 No system found for hostname: uyuni-master-rhlike-minion.sumaci.aws (RuntimeError)
./features/support/commonlib.rb:421:in `get_system_id'
./features/step_definitions/navigation_steps.rb:473:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/min_rhlike_salt.feature:43:in `I am on the Systems overview page of this "rhlike_minion"'

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

And I follow "Software Channels" in the content area 0s

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

And I check radio button "Fake-Base-Channel-RH-like" 0s

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

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

And I wait until event "Subscribe channels scheduled by admin" is completed 0s

14s 192ms Show Info +

13:17:18:000 - 13:17:18:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/Overview.do?sid=1000010000

Screenshot +

Scenario:
Detect latest Salt changes on the Red Hat-like minion

358ms 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
* 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:
* use-internal-salt.utils.pkg.deb-classes-instead-of-a.patch

When I query latest Salt changes on "rhlike_minion" 358ms

Scenario:
Check events history for failures on Red Hat-like minion

14s 120ms 1 1 1

Given I am on the Systems overview page of this "rhlike_minion" 301ms Show Error +

                                            
 No system found for hostname: uyuni-master-rhlike-minion.sumaci.aws (RuntimeError)
./features/support/commonlib.rb:421:in `get_system_id'
./features/step_definitions/navigation_steps.rb:473:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/min_rhlike_salt.feature:59:in `I am on the Systems overview page of this "rhlike_minion"'

Then I check for failed events on history event page 0s

13s 819ms Show Info +

13:17:33:000 - 13:17:33:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/Overview.do?sid=1000010000

Screenshot +

@build_host
Feature:Bootstrap a build host via the GUI 4m 37s 429ms 9

Scenario:
Clean up sumaform leftovers on build host

8s 443ms 1

When I perform a full salt minion cleanup on "build_host" 8s 443ms

Scenario:
Log in as admin user

37s 560ms 1

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

Scenario:
Bootstrap a build host

48s 276ms 10

The hostname of build_host is uyuni-master-build-host.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 163ms

Then I should see a "Bootstrap Minions" text 109ms

When I enter the hostname of "build_host" as "hostname" 176ms

And I enter "22" as "port" 60ms

And I enter "root" as "user" 70ms

And I enter "linux" as "password" 81ms

And I select "1-BUILD-HOST-KEY-x86_64" from "activationKeys" 116ms

And I select the hostname of "proxy" from "proxies" if present 3s 261ms

And I click on "Bootstrap" 70ms

And I wait until I see "Bootstrap process initiated." text 44s 165ms

Scenario:
Check the new bootstrapped build host in System Overview page

1m 45s 931ms 6

It took 1 seconds to contact the minion

When I follow the left menu "Salt > Keys" 195ms

Then I should see a "accepted" text 527ms

When I follow the left menu "Systems > System List > All" 295ms

And I wait at most 500 seconds until I see the name of "build_host", refreshing the page 42s 151ms

And I wait at most 500 seconds until onboarding is completed for "build_host" 1m 1s 172ms

Then the Salt master can reach "build_host" 1s 588ms

@proxy

Scenario:
Check connection from build host to proxy

1s 204ms 4

Given I am on the Systems overview page of this "build_host" 980ms

When I follow "Details" in the content area 79ms

And I follow "Connection" in the content area 74ms

Then I should see "proxy" short hostname 70ms

@proxy

Scenario:
Check registration on build host of minion

1s 157ms 4

Given I am on the Systems overview page of this "proxy" 925ms

When I follow "Details" in the content area 67ms

And I follow "Proxy" in the content area 68ms

Then I should see "build_host" hostname 96ms

Scenario:
Detect latest Salt changes on the SLES build host

548ms 1

* 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)
- Simplify and speed up utils.find_json function (bsc#1246130)
- Added:
* use-internal-salt.utils.pkg.deb-classes-instead-of-a.patch

When I query latest Salt changes on "build_host" 548ms

Scenario:
Check that the build host is a build host

1s 185ms 3

Given I am on the Systems overview page of this "build_host" 975ms

Then I should see a "[Container Build Host]" text 108ms

Then I should see a "[OS Image Build Host]" text 100ms

Scenario:
Check events history for failures on SLES build host

1m 13s 122ms 2

Given I am on the Systems overview page of this "build_host" 1s 72ms

Then I check for failed events on history event page 1m 12s 50ms

@sle_minion
Feature:Bootstrap a Salt minion via the GUI 3m 7s 957ms 6 2

Scenario:
Clean up sumaform leftovers on SLES minion

11s 234ms 1

When I perform a full salt minion cleanup on "sle_minion" 11s 234ms

Scenario:
Log in as admin user

37s 761ms 1

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

Scenario:
Bootstrap a SLES minion

46s 866ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 157ms

Then I should see a "Bootstrap Minions" text 78ms

When I enter the hostname of "sle_minion" as "hostname" 148ms

And I enter "22" as "port" 55ms

And I enter "root" as "user" 56ms

And I enter "linux" as "password" 57ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 81ms

And I select the hostname of "proxy" from "proxies" if present 3s 35ms

And I click on "Bootstrap" 92ms

And I wait until I see "Bootstrap process initiated." text 43s 105ms

And I report the bootstrap duration for "sle_minion" < 1ms

Scenario:
Check the new bootstrapped minion in System List page

1m 29s 179ms 8

It took 2 seconds to contact the minion

When I follow the left menu "Salt > Keys" 224ms

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

Then I should see a "accepted" text 112ms

When I follow the left menu "Systems > System List > All" 288ms

And I wait until I see the name of "sle_minion", refreshing the page 31s 296ms

And I wait until onboarding is completed for "sle_minion" 54s 881ms

Then the Salt master can reach "sle_minion" 2s 7ms

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 504ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 176ms

When I follow "Details" in the content area 118ms

And I follow "Connection" in the content area 114ms

Then I should see "proxy" short hostname 94ms

@proxy

Scenario:
Check registration on proxy of minion

1s 411ms 4

Given I am on the Systems overview page of this "proxy" 1s 123ms

When I follow "Details" in the content area 85ms

And I follow "Proxy" in the content area 106ms

Then I should see "sle_minion" hostname 95ms

@ssh_minion
Feature:Bootstrap a Salt host managed via salt-ssh 3m 13s 261ms 5 2

Scenario:
Clean up sumaform leftovers on SLES SSH minion

9s 368ms 1

When I perform a full salt minion cleanup on "ssh_minion" 9s 368ms

Scenario:
Log in as admin user

37s 762ms 1

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

Scenario:
Bootstrap a SLES SSH minion

2m 23s 109ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 165ms

Then I should see a "Bootstrap Minions" text 105ms

When I check "manageWithSSH" 114ms

And I enter the hostname of "ssh_minion" as "hostname" 180ms

And I enter "linux" as "password" 100ms

And I select the hostname of "proxy" from "proxies" if present 3s 420ms

And I click on "Bootstrap" 83ms

And I wait until I see "Bootstrap process initiated." text 52s 29ms

And I follow the left menu "Systems > System List > All" 181ms

And I wait until I see the name of "ssh_minion", refreshing the page 31s 544ms

And I wait until onboarding is completed for "ssh_minion" 55s 183ms

@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 264ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 24ms

When I follow "Details" in the content area 83ms

And I follow "Connection" in the content area 70ms

Then I should see "proxy" short hostname 85ms

@proxy

Scenario:
Check registration on proxy of SSH minion

1s 756ms 4

Given I am on the Systems overview page of this "proxy" 1s 532ms

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

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

Then I should see "ssh_minion" hostname 90ms

@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 18s 273ms 5

Scenario:
Call spacewalk-debug on server

14s 231ms 1

When I execute spacewalk-debug on the server 14s 231ms

Scenario:
Check the tomcat logs on server

723ms 1

Then the tomcat logs should not contain errors 723ms

Scenario:
Check salt event log for failures on server

1s 950ms 1

Then the salt event log on server should contain no failures 1s 950ms

Scenario:
Check the taskomatic logs on server

693ms 1

Then the taskomatic logs should not contain errors 693ms

Scenario:
Check for out of memory errors

674ms 1

Then the log messages should not contain out of memory errors 674ms

Feature:Debug the clients after the testsuite has run 1m 35s 847ms 1

Scenario:
Extract the logs from all our clients

1m 35s 847ms 1

When I extract the log files from all our active nodes 1m 35s 847ms

@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

150

Failed Scenarios

12

Skipped Scenarios

39

@proxy Scenario:The proxy is healthy 4s 522ms 4

@sle_minion Scenario:The minion is healthy 8s 36ms 4

@build_host Scenario:The build host is healthy 3s 796ms 4

@ssh_minion Scenario:The SSH minion is healthy 5s 937ms 4

@rhlike_minion Scenario:The Red Hat-like minion is healthy 3s 116ms 4

@deblike_minion Scenario:The Debian-like minion is healthy 5s 863ms 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 656ms 1

@no_auth_registry Scenario:The registry without authentication is healthy 677ms 1

@custom_download_endpoint Scenario:The custom download endpoint is working 636ms 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 243ms 7

@scc_credentials Feature:List available channels and enable them 1m 39s 359ms 5 1

@proxy @susemanager Scenario:List all products for SUSE Multi-Linux Manager < 1ms 6

@scc_credentials Scenario:Refresh SCC 27s 924ms 1

@scc_credentials Scenario:Let the products page appear 3s 27ms 6

@scc_credentials Scenario:Use the products and architecture filters 2s 360ms 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 2s 711ms 4

@containerized_server @proxy @uyuni Scenario:Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools 45s 129ms 2

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 47m 36s 401ms 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 44s 202ms 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 558ms 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 667ms 11

@rhlike_minion Scenario:Add a RedHat-like base channel 1s 521ms 10

@rhlike_minion Scenario:Add a fake AppStream base channel 1s 88ms 10

@rhlike_minion Scenario:Create a fake AppStream repository 946ms 7

@rhlike_minion Scenario:Disable metadata check for the fake AppStream repository 10s 900ms 6

@sle_minion Scenario:Add the fake RPM repository to the SUSE fake child channel 2s 39ms 9

@rhlike_minion Scenario:Add the fake RPM repository to the RedHat-like base channel 2s 659ms 9

@rhlike_minion Scenario:Add the fake AppStream repository to the AppStream base channel 2s 655ms 9

@sle_minion Scenario:Add the repository to the SUSE-like child channel 1s 660ms 6

@deblike_minion Scenario:Create a fake repository for Debian-like 1s 101ms 7

@deblike_minion Scenario:Add the repository to the Debian-like base channel 1s 270ms 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 30s 521ms 9

@sle_minion Scenario:Create a custom channel for SUSE minions 1s 737ms 10

@sle_minion Scenario:Create custom repositories inside the SUSE custom channel 8s 262ms 1

@uyuni @build_host Scenario:Create a custom channel for Build Host 1s 654ms 10

@uyuni @build_host Scenario:Create custom repositories inside the Build Host custom channel 3s 968ms 1

@deblike_minion Scenario:Create a custom channel for Debian-like minions 1s 73ms 10

@deblike_minion Scenario:Create custom repositories inside the Debian-like custom channel 7s 271ms 1

@rhlike_minion Scenario:Create a custom channel for RH-like minions 1s 638ms 10

@rhlike_minion Scenario:Create custom repositories inside the RH-like custom channel 4s 411ms 1

@sle_minion Scenario:Synchronize Fake-RPM-SUSE-Channel channel 3s 795ms 9

@sle_minion Scenario:Verify state of Fake-RPM-SUSE-Channel channel 4s 799ms 2

@skip_if_github_validation Scenario:Synchronize Fake-Child-Channel-i586 channel 3s 649ms 9

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 14s 603ms 9

@deblike_minion Scenario:Synchronize Fake-Base-Channel-Debian-like channel 3s 791ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-RH-like channel 4s 293ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-AppStream channel 4s 156ms 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 611ms 4

@sle_minion Scenario:Synchronize Devel-SUSE-Channel channel 3s 914ms 9

@deblike_minion Scenario:Synchronize Devel-Debian-like-Channel channel 4s 152ms 9

@rhlike_minion Scenario:Synchronize Devel-RH-like-Channel channel 4s 338ms 9

@build_host @uyuni Scenario:Synchronize Devel-Build-Host-Channel channel 4s 205ms 9

@sle_minion Scenario:Create an activation key with a channel 2s 99ms 2

@proxy

Scenario:
The proxy is healthy

4s 522ms 4

@sle_minion

Scenario:
The minion is healthy

8s 36ms 4

@build_host

Scenario:
The build host is healthy

3s 796ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

5s 937ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 116ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 863ms 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

656ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

677ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

636ms 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 243ms 7

@scc_credentials
Feature:List available channels and enable them 1m 39s 359ms 5 1

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

27s 924ms 1

@scc_credentials

Scenario:
Let the products page appear

3s 27ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 360ms 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 2s 711ms 4

@containerized_server @proxy @uyuni

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

45s 129ms 2

@scc_credentials @uyuni @build_host

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

47m 36s 401ms 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

44s 202ms 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 558ms 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 667ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 521ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 88ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

946ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 900ms 6

@sle_minion

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

2s 39ms 9

@rhlike_minion

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

2s 659ms 9

@rhlike_minion

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

2s 655ms 9

@sle_minion

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

1s 660ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 101ms 7

@deblike_minion

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

1s 270ms 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 30s 521ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 737ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

8s 262ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 654ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

3s 968ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 73ms 10

@deblike_minion

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

7s 271ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 638ms 10

@rhlike_minion

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

4s 411ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 795ms 9

@sle_minion

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

4s 799ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 649ms 9

@sle_minion

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

14s 603ms 9

@deblike_minion

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

3s 791ms 9

@rhlike_minion

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

4s 293ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 156ms 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 611ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

3s 914ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 152ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 338ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 205ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 99ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 485ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

2s 665ms 2

@ssh_minion

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

2s 607ms 2

@ssh_minion

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

1s 992ms 2

@proxy

Scenario:
Create an activation key for the proxy

2s 69ms 2

@build_host

Scenario:
Create an activation key for the build host

2s 592ms 3

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 338ms 2

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20