Cucumber Feature Report

All Scenarios

148

Passed Scenarios

116

Failed Scenarios

2

Skipped Scenarios

30

Execution Time: 73m 37s 731ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 43s 928ms 10 2

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

Scenario:
The server is healthy

11s 693ms 19

Then "server" should have a FQDN 393ms

And reverse resolution should work for "server" 634ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 527ms 4

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

And reverse resolution should work for "proxy" 279ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 450ms 4

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

And reverse resolution should work for "sle_minion" 436ms

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

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

@build_host

Scenario:
The build host is healthy

3s 774ms 4

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

And reverse resolution should work for "build_host" 222ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 369ms 4

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

And reverse resolution should work for "ssh_minion" 457ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 194ms 4

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

And reverse resolution should work for "rhlike_minion" 191ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 845ms 4

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

And reverse resolution should work for "deblike_minion" 212ms

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

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

699ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

725ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

647ms 1

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

Feature:Very first settings 47s 352ms 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

686ms 1

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

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

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

Scenario:
Wait for refresh of list of products to finish

3s 387ms 1

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

Scenario:
Create testing username

1s 248ms 12

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

And I follow "Create User" 564ms

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

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

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

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

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

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

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

And I click on "Create Login" 63ms

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

And I should see a "testing" link 11ms

Scenario:
Grant testing user administrative priviledges

1s 650ms 10

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

And I follow "testing" 509ms

And I check "role_org_admin" 80ms

And I check "role_system_group_admin" 73ms

And I check "role_channel_admin" 72ms

And I check "role_activation_key_admin" 76ms

And I check "role_config_admin" 71ms

And I click on "Update" 566ms

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

And I should see a "testing" text 62ms

@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

681ms 1

* Mon Nov 24 2025 Alexander Graul
- Add minimum_auth_version to enforce security (CVE-2025-62349)
- Backport security fixes for vendored tornado
* BDSA-2024-3438
* BDSA-2024-3439
* BDSA-2024-9026
- Junos module yaml loader fix (CVE-2025-62348)
- Added:
* backport-3006.17-security-fixes-739.patch

* Thu Nov 13 2025 Marek Czernek
- Require Python dependencies only for used Python version

* Tue Nov 11 2025 Marek Czernek
- Fix TLS and x509 modules for OSes with older cryptography module

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

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

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

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 784ms 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 351ms 5

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

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

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

And I click on "Save Preferences" 618ms

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

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

3s 433ms 5

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

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

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

And I click on "Save Preferences" 734ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 403ms 2

New user kiwikiwi created with roles: image_admin

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

When I create a user with name "kiwikiwi" and password "kiwikiwi" with roles "image_admin" 2s 127ms

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

Scenario:
Create a Docker user with image administrators rights

2s 146ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

3s 34ms 7

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

And I follow "Create" 511ms

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

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

And I click on "create-btn" 163ms

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

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

Feature:Do not let Taskomatic tasks interfere with our CI tests 35s 752ms 3

Scenario:
Log in as admin user

26s 748ms 1

Given I am authorized for the "Admin" section 26s 748ms

Scenario:
Disable scheduled reposyncs

4s 477ms 5

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

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

And I choose "disabled" 54ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 527ms 5

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

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

And I choose "disabled" 44ms

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

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

@scc_credentials
Feature:List available channels and enable them 1m 36s 238ms 5 1

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

Scenario:
List available channels

30s 340ms 5

When I refresh SCC 28s 31ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 663ms

And I execute mgr-sync refresh 1m 766ms

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

Feature:Synchronize products in the products page of the Setup Wizard 64m 12s 652ms 8 9

@scc_credentials

Scenario:
Refresh SCC

26s 5ms 1

When I refresh SCC 26s 5ms

@scc_credentials

Scenario:
Let the products page appear

1s 954ms 6

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

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

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

Then I should see a "Arch" text 102ms

And I should see a "Channels" text 102ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 429ms 7

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

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

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

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

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

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

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

@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

3m 31s 521ms 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 346ms

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

And I use spacewalk-repo-sync to sync channel "opensuse_tumbleweed-x86_64" including only client tools dependencies 3m 4s 873ms

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

@containerized_server @proxy @uyuni

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

54s 854ms 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" 21s 84ms

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

@scc_credentials @uyuni @build_host

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

58m 32s 554ms 20

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 53ms

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

Then the SLE15 SP7 product should be added 3s 48ms

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

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

And I wait until all synchronized channels for "sles15-sp7" have finished 58m 10s 946ms

@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

43s 332ms 7

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

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

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

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

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

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

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

@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 22s 457ms 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

480ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 572ms 10

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

And I follow "Create Channel" 293ms

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

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

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

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

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

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

And I click on "Create Channel" 601ms

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

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

1s 400ms 10

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

And I follow "Create Channel" 293ms

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

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

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

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

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

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

And I click on "Create Channel" 571ms

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

@sle_minion

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

863ms 10

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

And I follow "Create Channel" 295ms

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

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

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

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

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

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

And I click on "Create Channel" 53ms

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

Scenario:
Add a fake base channel for i586

1s 337ms 10

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

And I follow "Create Channel" 298ms

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

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

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

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

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

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

And I click on "Create Channel" 510ms

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

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

881ms 10

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

And I follow "Create Channel" 305ms

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

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

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

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

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

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

And I click on "Create Channel" 53ms

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

Scenario:
Add a test base channel for x86_64

1s 319ms 10

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

And I follow "Create Channel" 299ms

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

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

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

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

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

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

And I click on "Create Channel" 511ms

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

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

886ms 10

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

And I follow "Create Channel" 289ms

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

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

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

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

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

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

And I click on "Create Channel" 62ms

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

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

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

And I follow "Create Channel" 298ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 89ms

And I click on "Create Channel" 501ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

948ms 10

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

And I follow "Create Channel" 329ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 337ms 10

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

And I follow "Create Channel" 315ms

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

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

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

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

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

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

And I click on "Create Channel" 501ms

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

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

494ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 77ms 7

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

And I follow "Create Repository" 276ms

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

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

And I click on "Create Repository" 428ms

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

And I should see "metadataSigned" as checked 17ms

Scenario:
Disable metadata check for the fake RPM repository

10s 952ms 6

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

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

And I uncheck "metadataSigned" 10s 64ms

And I click on "Update Repository" 458ms

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

And I should see "metadataSigned" as unchecked 14ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

989ms 7

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

And I follow "Create Repository" 261ms

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

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

And I click on "Create Repository" 454ms

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

And I should see "metadataSigned" as checked 14ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 886ms 6

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

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

And I uncheck "metadataSigned" 10s 72ms

And I click on "Update Repository" 436ms

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

And I should see "metadataSigned" as unchecked 15ms

@sle_minion

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

1s 580ms 9

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

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

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

And I click on "Update Channel" 60ms

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

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

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

And I click on "Save Repositories" 654ms

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

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

2s 538ms 9

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

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

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

And I click on "Update Channel" 51ms

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

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

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

And I click on "Save Repositories" 926ms

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

@rhlike_minion

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

2s 684ms 9

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

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

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

And I click on "Update Channel" 483ms

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

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

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

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

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

@rhlike_minion

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

2s 717ms 9

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

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

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

And I click on "Update Channel" 615ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 69ms 7

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

And I follow "Create Repository" 264ms

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

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

And I uncheck "metadataSigned" 10s 92ms

And I click on "Create Repository" 444ms

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

Scenario:
Add the repository to the i586 channel

1s 873ms 9

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

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

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

And I click on "Update Channel" 503ms

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

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

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

And I click on "Save Repositories" 602ms

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

@sle_minion

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

1s 564ms 6

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

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

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

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

And I click on "Save Repositories" 925ms

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

663ms 7

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

And I follow "Create Repository" 275ms

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

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

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

And I click on "Create Repository" 51ms

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

@deblike_minion

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

1s 382ms 6

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

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

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

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

And I click on "Save Repositories" 807ms

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

@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 36s 344ms 8 1

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

510ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 564ms 10

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

And I follow "Create Channel" 318ms

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

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

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

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

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

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

And I click on "Create Channel" 605ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

15s 334ms 1 1

When I prepare the development repositories of "sle_minion" as part of "devel-suse-channel" channel 1s 625ms Show Error +

                                            
 No FQDN for 'uyuni-master-suse-minion'. Response code:  (StandardError)
./features/support/remote_node.rb:46:in `initialize'
./features/support/remote_nodes_env.rb:39:in `new'
./features/support/remote_nodes_env.rb:39:in `get_target'
./features/step_definitions/setup_steps.rb:534:in `/^I prepare the development repositories of "([^"]*)" as part of "([^"]*)" channel$/'
features/reposync/srv_create_devel_channels.feature:28:in `I prepare the development repositories of "sle_minion" as part of "devel-suse-channel" channel'

13s 708ms Show Info +

20:38:50:000 - 20:38:52:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Edit.do?cid=131

Screenshot +

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 367ms 10

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

And I follow "Create Channel" 313ms

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

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

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

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

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

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

And I click on "Create Channel" 513ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 101ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

940ms 10

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

And I follow "Create Channel" 330ms

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

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

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

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

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

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

And I click on "Create Channel" 53ms

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

@deblike_minion

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

6s 821ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 348ms 10

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

And I follow "Create Channel" 268ms

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

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

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

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

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

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

And I click on "Create Channel" 536ms

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

@rhlike_minion

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

4s 356ms 1

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

Feature:Synchronize fake channels 58s 537ms 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 848ms 2

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

And I enable source package syncing 1s 399ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 882ms 9

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

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

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

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

And I follow "Sync" 381ms

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

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

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

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

@sle_minion

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

4s 790ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 656ms 9

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

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

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

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

And I follow "Sync" 371ms

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

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

4s 194ms 9

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

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

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

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

And I follow "Sync" 815ms

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

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

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

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

@sle_minion

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

14s 451ms 9

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

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

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

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

And I follow "Sync" 767ms

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

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

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

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

@deblike_minion

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

3s 539ms 9

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

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

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

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

And I follow "Sync" 297ms

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

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

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

@rhlike_minion

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

4s 340ms 9

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

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

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

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

And I follow "Sync" 981ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 136ms 9

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

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

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

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

And I follow "Sync" 824ms

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

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

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

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

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

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

6s 230ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

980ms 1

Then I disable source package syncing 980ms

@skip_if_github_validation
Feature:Synchronize development channels 39s 331ms 3 1

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

26s 718ms 8 1 1

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

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

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

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

And I follow "Sync" 341ms

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

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

Then I should see a "Repository sync scheduled for Devel-SUSE-Channel." text 10s 41ms Show Error +

                                            
 Text 'Repository sync scheduled for Devel-SUSE-Channel.' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:661:in `/^I should see a "([^"]*)" text$/'
features/reposync/srv_sync_devel_channels.feature:19:in `I should see a "Repository sync scheduled for Devel-SUSE-Channel." text'

And I wait until the channel "devel-suse-channel" has been synced 0s

13s 857ms Show Info +

20:40:33:000 - 20:40:46:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=131

Screenshot +

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 8ms 9

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

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

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

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

And I follow "Sync" 405ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 333ms 9

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

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

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

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

And I follow "Sync" 683ms

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

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 270ms 9

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

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

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

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

And I follow "Sync" 648ms

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

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

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

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

508ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

2s 203ms 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 688ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 623ms 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" 1s 22ms

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 573ms 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" 805ms

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

@ssh_minion

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

1s 587ms 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" 754ms

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

@ssh_minion

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

1s 834ms 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" 849ms

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

@proxy

Scenario:
Create an activation key for the proxy

3s 437ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

3s 9ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 283ms 2

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

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

Feature:Update activation keys 29s 771ms 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

529ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 736ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 709ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 781ms

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

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

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

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

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

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

And I wait for child channels to appear 503ms

And I include the recommended child channels 232ms

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 667ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

3s 608ms 9

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

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

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

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

And I wait for child channels to appear 352ms

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

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

And I click on "Update Activation Key" 976ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 692ms 9

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

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

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

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

And I wait for child channels to appear 303ms

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

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

And I click on "Update Activation Key" 711ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

4s 202ms 16

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

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

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

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

And I wait for child channels to appear 598ms

And I include the recommended child channels 204ms

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 917ms

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

@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

2s 302ms 6

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

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

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

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

And I click on "Update Activation Key" 691ms

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

@skip_if_github_validation @deblike_minion

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

2s 133ms 6

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

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

And I wait for child channels to appear 963ms

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

And I click on "Update Activation Key" 713ms

Then I should see a "Activation key Debian-like Test Key has been modified" text 77ms

@skip_if_github_validation @rhlike_minion

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

2s 219ms 6

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

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

And I wait for child channels to appear 924ms

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

And I click on "Update Activation Key" 870ms

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

Feature:Create bootstrap repositories 9s 83ms 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 292ms 1

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 143ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

@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 392ms 5

Scenario:
Call spacewalk-debug on server

14s 447ms 1

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

Scenario:
Check the tomcat logs on server

748ms 1

Then the tomcat logs should not contain errors 748ms

Scenario:
Check salt event log for failures on server

1s 858ms 1

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

Scenario:
Check the taskomatic logs on server

670ms 1

Then the taskomatic logs should not contain errors 670ms

Scenario:
Check for out of memory errors

667ms 1

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

Feature:Debug the clients after the testsuite has run 41s 264ms 1

Scenario:
Extract the logs from all our clients

41s 264ms 1

When I extract the log files from all our active nodes 41s 264ms

@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

148

Passed Scenarios

116

Failed Scenarios

2

Skipped Scenarios

30

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

@sle_minion Scenario:The minion is healthy 6s 450ms 4

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

@ssh_minion Scenario:The SSH minion is healthy 6s 369ms 4

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

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

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

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

@scc_credentials Feature:List available channels and enable them 1m 36s 238ms 5 1

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

@scc_credentials Scenario:Refresh SCC 26s 5ms 1

@scc_credentials Scenario:Let the products page appear 1s 954ms 6

@scc_credentials Scenario:Use the products and architecture filters 2s 429ms 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 3m 31s 521ms 4

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

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 58m 32s 554ms 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 43s 332ms 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 863ms 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 430ms 11

@rhlike_minion Scenario:Add a RedHat-like base channel 948ms 10

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

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

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

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

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

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

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

@deblike_minion Scenario:Create a fake repository for Debian-like 663ms 7

@deblike_minion Scenario:Add the repository to the Debian-like base channel 1s 382ms 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 36s 344ms 8 1

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

@sle_minion Scenario:Create custom repositories inside the SUSE custom channel 15s 334ms 1 1

@uyuni @build_host Scenario:Create a custom channel for Build Host 1s 367ms 10

@uyuni @build_host Scenario:Create custom repositories inside the Build Host custom channel 4s 101ms 1

@deblike_minion Scenario:Create a custom channel for Debian-like minions 940ms 10

@deblike_minion Scenario:Create custom repositories inside the Debian-like custom channel 6s 821ms 1

@rhlike_minion Scenario:Create a custom channel for RH-like minions 1s 348ms 10

@rhlike_minion Scenario:Create custom repositories inside the RH-like custom channel 4s 356ms 1

@sle_minion Scenario:Synchronize Fake-RPM-SUSE-Channel channel 3s 882ms 9

@sle_minion Scenario:Verify state of Fake-RPM-SUSE-Channel channel 4s 790ms 2

@skip_if_github_validation Scenario:Synchronize Fake-Child-Channel-i586 channel 3s 656ms 9

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 14s 451ms 9

@deblike_minion Scenario:Synchronize Fake-Base-Channel-Debian-like channel 3s 539ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-RH-like channel 4s 340ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-AppStream channel 4s 136ms 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 39s 331ms 3 1

@sle_minion Scenario:Synchronize Devel-SUSE-Channel channel 26s 718ms 8 1 1

@deblike_minion Scenario:Synchronize Devel-Debian-like-Channel channel 4s 8ms 9

@rhlike_minion Scenario:Synchronize Devel-RH-like-Channel channel 4s 333ms 9

@build_host @uyuni Scenario:Synchronize Devel-Build-Host-Channel channel 4s 270ms 9

@sle_minion Scenario:Create an activation key with a channel 2s 203ms 2

@proxy

Scenario:
The proxy is healthy

4s 527ms 4

@sle_minion

Scenario:
The minion is healthy

6s 450ms 4

@build_host

Scenario:
The build host is healthy

3s 774ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 369ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 194ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 845ms 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

699ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

725ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

647ms 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 34ms 7

@scc_credentials
Feature:List available channels and enable them 1m 36s 238ms 5 1

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

26s 5ms 1

@scc_credentials

Scenario:
Let the products page appear

1s 954ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

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

3m 31s 521ms 4

@containerized_server @proxy @uyuni

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

54s 854ms 2

@scc_credentials @uyuni @build_host

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

58m 32s 554ms 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

43s 332ms 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

863ms 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 430ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

948ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 337ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

989ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 886ms 6

@sle_minion

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

1s 580ms 9

@rhlike_minion

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

2s 684ms 9

@rhlike_minion

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

2s 717ms 9

@sle_minion

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

1s 564ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

663ms 7

@deblike_minion

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

1s 382ms 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 36s 344ms 8 1

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 564ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

15s 334ms 1 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 367ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 101ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

940ms 10

@deblike_minion

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

6s 821ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 348ms 10

@rhlike_minion

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

4s 356ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 882ms 9

@sle_minion

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

4s 790ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 656ms 9

@sle_minion

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

14s 451ms 9

@deblike_minion

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

3s 539ms 9

@rhlike_minion

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

4s 340ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 136ms 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 39s 331ms 3 1

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

26s 718ms 8 1 1

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 8ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 333ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 270ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 203ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 623ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 573ms 2

@ssh_minion

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

1s 587ms 2

@ssh_minion

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

1s 834ms 2

@proxy

Scenario:
Create an activation key for the proxy

3s 437ms 2

@build_host

Scenario:
Create an activation key for the build host

3s 9ms 3