Cucumber Feature Report

All Scenarios

148

Passed Scenarios

111

Failed Scenarios

7

Skipped Scenarios

30

Execution Time: 26m 42s 420ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 46s 125ms 10 2

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

Scenario:
The server is healthy

11s 935ms 19

Then "server" should have a FQDN 404ms

And reverse resolution should work for "server" 664ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 460ms 4

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

And reverse resolution should work for "proxy" 277ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 539ms 4

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

And reverse resolution should work for "sle_minion" 418ms

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

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

@build_host

Scenario:
The build host is healthy

5s 474ms 4

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

And reverse resolution should work for "build_host" 342ms

And "build_host" should communicate with the server using public interface 1s 106ms

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 364ms 4

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

And reverse resolution should work for "ssh_minion" 441ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 421ms 4

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

And reverse resolution should work for "rhlike_minion" 191ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 941ms 4

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

And reverse resolution should work for "deblike_minion" 213ms

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

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

@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

677ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

669ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

641ms 1

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

Feature:Very first settings 49s 593ms 6 2

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

Scenario:
Cleanup Salt files

687ms 1

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

@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

40s 174ms 1

Given I am authorized for the "Admin" section 40s 174ms

Scenario:
Wait for refresh of list of products to finish

3s 976ms 1

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

Scenario:
Create testing username

2s 199ms 12

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

And I follow "Create User" 596ms

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

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

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

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

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

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

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

And I click on "Create Login" 914ms

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

And I should see a "testing" link 13ms

Scenario:
Grant testing user administrative priviledges

1s 776ms 10

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

And I follow "testing" 564ms

And I check "role_org_admin" 82ms

And I check "role_system_group_admin" 80ms

And I check "role_channel_admin" 79ms

And I check "role_activation_key_admin" 77ms

And I check "role_config_admin" 84ms

And I click on "Update" 584ms

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

And I should see a "testing" text 68ms

@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

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

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

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

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 77ms 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 316ms 5

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

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

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

And I click on "Save Preferences" 598ms

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

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

2s 760ms 5

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

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

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

And I click on "Save Preferences" 53ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 142ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights

2s 110ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

3s 639ms 7

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

And I follow "Create" 618ms

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

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

And I click on "create-btn" 111ms

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

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

Feature:Do not let Taskomatic tasks interfere with our CI tests 36s 244ms 3

Scenario:
Log in as admin user

26s 917ms 1

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

Scenario:
Disable scheduled reposyncs

4s 756ms 5

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

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

And I choose "disabled" 57ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 570ms 5

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

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

And I choose "disabled" 48ms

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

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

@scc_credentials
Feature:List available channels and enable them 1m 37s 405ms 5 1

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

Scenario:
List available channels

31s 358ms 5

When I refresh SCC 29s 123ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 671ms

And I execute mgr-sync refresh 1m 769ms

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

Feature:Synchronize products in the products page of the Setup Wizard 5m 9s 671ms 6 2 9

@scc_credentials

Scenario:
Refresh SCC

26s 680ms 1

When I refresh SCC 26s 680ms

@scc_credentials

Scenario:
Let the products page appear

2s 85ms 6

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

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

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

Then I should see a "Arch" text 108ms

And I should see a "Channels" text 109ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 384ms 7

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

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

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

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

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

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

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

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

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

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

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

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

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

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

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

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

When I close the modal dialog 0s

@scc_credentials @susemanager

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

< 1ms 30

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

Then the SLE15 SP7 product should be added 0s

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

@uyuni

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

2m 12s 174ms 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 449ms

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

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

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

@containerized_server @proxy @uyuni

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

1m 27s 441ms 2

Channel opensuse_tumbleweed-x86_64 added
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 added
Channel uyuni-proxy-devel-tumbleweed-x86_64 added
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 finished reposync
Channel opensuse_tumbleweed-x86_64 finished reposync
1 minutes out of 229 waiting for 'uyuni-proxy' channels to finish 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" 23s 276ms

And I wait until all synchronized channels for "uyuni-proxy" have finished 1m 4s 165ms

@scc_credentials @uyuni @build_host

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

34s 900ms 20 1

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-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] [ ] 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]

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 56ms

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

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

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

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 2s 178ms Show Error +

                                            
 Error during reposync:
unknown error - API failure: No such channel: sle-module-python3-15-sp7-pool-x86_64
Reposync for these channels did not complete:
 ["sle-product-sles15-sp7-pool-x86_64", "sle-product-sles15-sp7-updates-x86_64", "sle15-sp7-installer-updates-x86_64", "sle-module-basesystem15-sp7-pool-x86_64", "sle-module-basesystem15-sp7-updates-x86_64", "sle-module-python3-15-sp7-pool-x86_64", "sle-module-python3-15-sp7-updates-x86_64", "sle-module-server-applications15-sp7-pool-x86_64", "sle-module-server-applications15-sp7-updates-x86_64", "sle-module-desktop-applications15-sp7-pool-x86_64", "sle-module-desktop-applications15-sp7-updates-x86_64", "sle-module-devtools15-sp7-updates-x86_64", "sle-module-devtools15-sp7-pool-x86_64", "sle-module-systems-management-15-sp7-pool-x86_64", "sle-module-systems-management-15-sp7-updates-x86_64", "sles15-sp7-devel-uyuni-client-x86_64"] (ScriptError)
./features/step_definitions/command_steps.rb:486:in `rescue in block in (top (required))'
./features/step_definitions/command_steps.rb:462:in `/^I wait until all synchronized channels for "([^"]*)" have finished$/'
features/reposync/srv_sync_products.feature:113:in `I wait until all synchronized channels for "sles15-sp7" have finished'

14s 100ms Show Info +

13:20:08:000 - 13:20:30:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/setup/products

Screenshot +

@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

24s 5ms 7 1

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

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

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

And I wait until I do not see "Loading" text 5s 226ms

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

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

And I should only see success signs in the product list 2s 325ms Show Error +

                                            
 No product synchronized (ScriptError)
./features/step_definitions/navigation_steps.rb:854:in `/^I should only see success signs in the product list$/'
features/reposync/srv_sync_products.feature:236:in `I should only see success signs in the product list'

14s 456ms Show Info +

13:20:44:000 - 13:20:55:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/setup/products

Screenshot +

@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 23s 633ms 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

501ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 798ms 10

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

And I follow "Create Channel" 411ms

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

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

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

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

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

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

And I click on "Create Channel" 691ms

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

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

1s 562ms 10

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

And I follow "Create Channel" 374ms

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

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

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

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

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

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

And I click on "Create Channel" 617ms

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

@sle_minion

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

934ms 10

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

And I follow "Create Channel" 318ms

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

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

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

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

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

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

And I click on "Create Channel" 58ms

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

Scenario:
Add a fake base channel for i586

1s 15ms 10

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

And I follow "Create Channel" 394ms

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

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

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

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

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

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

And I click on "Create Channel" 57ms

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

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

1s 450ms 10

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

And I follow "Create Channel" 330ms

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

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

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

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

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

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

And I click on "Create Channel" 555ms

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

Scenario:
Add a test base channel for x86_64

1s 20ms 10

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

And I follow "Create Channel" 412ms

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

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

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

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

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

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

And I click on "Create Channel" 58ms

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

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

1s 138ms 10

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

And I follow "Create Channel" 486ms

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

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

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

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

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

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

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

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

And I follow "Create Channel" 392ms

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

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

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

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

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

And I uncheck "gpg_check" 10s 110ms

And I click on "Create Channel" 672ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 493ms 10

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

And I follow "Create Channel" 343ms

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

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

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

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

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

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

And I click on "Create Channel" 610ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

973ms 10

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

And I follow "Create Channel" 356ms

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

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

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

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

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

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

And I click on "Create Channel" 56ms

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

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

597ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 259ms 7

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

And I follow "Create Repository" 329ms

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

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

And I click on "Create Repository" 531ms

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

And I should see "metadataSigned" as checked 19ms

Scenario:
Disable metadata check for the fake RPM repository

11s 108ms 6

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

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

And I uncheck "metadataSigned" 10s 76ms

And I click on "Update Repository" 502ms

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

And I should see "metadataSigned" as unchecked 16ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 40ms 7

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

And I follow "Create Repository" 292ms

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

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

And I click on "Create Repository" 452ms

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

And I should see "metadataSigned" as checked 17ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 58ms 6

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

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

And I uncheck "metadataSigned" 10s 61ms

And I click on "Update Repository" 477ms

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

And I should see "metadataSigned" as unchecked 17ms

@sle_minion

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

2s 322ms 9

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

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

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

And I click on "Update Channel" 65ms

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

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

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

And I click on "Save Repositories" 783ms

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

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

2s 369ms 9

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

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

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

And I click on "Update Channel" 615ms

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

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

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

And I click on "Save Repositories" 829ms

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 761ms 9

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

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

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

And I click on "Update Channel" 570ms

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

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

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

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

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

@rhlike_minion

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

2s 623ms 9

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

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

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

And I click on "Update Channel" 551ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 198ms 7

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

And I follow "Create Repository" 292ms

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

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

And I uncheck "metadataSigned" 10s 64ms

And I click on "Create Repository" 548ms

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

Scenario:
Add the repository to the i586 channel

1s 976ms 9

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

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

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

And I click on "Update Channel" 528ms

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

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

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

And I click on "Save Repositories" 552ms

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

@sle_minion

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

1s 730ms 6

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

710ms 7

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

And I follow "Create Repository" 296ms

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

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

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

And I click on "Create Repository" 55ms

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

@deblike_minion

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

1s 328ms 6

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

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

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

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

And I click on "Save Repositories" 626ms

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

@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 51s 47ms 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

624ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 115ms 10

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

And I follow "Create Channel" 348ms

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

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

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

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

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

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

And I click on "Create Channel" 65ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

17s 822ms 1 1

When I prepare the development repositories of "sle_minion" as part of "devel-suse-channel" channel 1s 588ms 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'

16s 233ms Show Info +

13:22:42:000 - 13:22:44:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Edit.do?cid=127

Screenshot +

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 213ms 10

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

And I follow "Create Channel" 594ms

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

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

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

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

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

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

And I click on "Create Channel" 58ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

8s 102ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

2s 43ms 10

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

And I follow "Create Channel" 520ms

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

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

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

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

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

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

And I click on "Create Channel" 923ms

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

@deblike_minion

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

9s 869ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

2s 229ms 10

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

And I follow "Create Channel" 705ms

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

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

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

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

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

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

And I click on "Create Channel" 933ms

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

@rhlike_minion

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

8s 26ms 1

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

Feature:Synchronize fake channels 11m 19s 671ms 11 1 2

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

Scenario:
Log in as admin user

2s 726ms 2

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

And I enable source package syncing 1s 922ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

6s 927ms 9

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

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

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

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

And I follow "Sync" 802ms

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" 2s 810ms

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

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

@sle_minion

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

10m 18s 287ms 2 1

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

And solver file for "fake-rpm-suse-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm" 10m Show Error +

                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/command_steps.rb:420:in `/^solver file for "([^"]*)" should reference "([^"]*)"$/'
features/reposync/srv_sync_fake_channels.feature:36:in `solver file for "fake-rpm-suse-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm"'

17s 221ms Show Info +

13:23:46:000 - 13:33:47:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=119

Screenshot +

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

7s 276ms 9

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

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

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

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

And I follow "Sync" 883ms

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" 2s 905ms

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

And I wait until the channel "fake-child-channel-i586" has been synced 1s 310ms

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

6s 372ms 9

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

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

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

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

And I follow "Sync" 715ms

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" 2s 811ms

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

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

@sle_minion

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

6s 178ms 9

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

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

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

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

And I follow "Sync" 628ms

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" 2s 814ms

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

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

@deblike_minion

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

6s 423ms 9

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

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

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

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

And I follow "Sync" 629ms

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

And I click on "Sync Now" 2s 896ms

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

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

@rhlike_minion

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

5s 126ms 9

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

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

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

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

And I follow "Sync" 719ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

6s 425ms 9

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

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

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

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

And I follow "Sync" 1s 108ms

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" 2s 736ms

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

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

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

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

5s 802ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

1s 818ms 1

Then I disable source package syncing 1s 818ms

@skip_if_github_validation
Feature:Synchronize development channels 47s 968ms 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

29s 336ms 8 1 1

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

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

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

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

And I follow "Sync" 798ms

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

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

Then I should see a "Repository sync scheduled for Devel-SUSE-Channel." text 10s 43ms 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

15s 379ms Show Info +

13:35:11:000 - 13:35:27:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=127

Screenshot +

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

6s 166ms 9

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

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

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

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

And I follow "Sync" 560ms

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

And I click on "Sync Now" 2s 788ms

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

6s 262ms 9

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

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

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

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

And I follow "Sync" 544ms

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

And I click on "Sync Now" 2s 856ms

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

6s 202ms 9

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

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

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

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

And I follow "Sync" 641ms

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" 2s 801ms

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

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

Feature:Create activation keys 33s 609ms 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

829ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

4s 68ms 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" 3s 60ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

4s 197ms 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" 2s 782ms

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

3s 214ms 2

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

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

@ssh_minion

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

4s 443ms 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" 2s 379ms

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

@ssh_minion

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

3s 468ms 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" 1s 736ms

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

@proxy

Scenario:
Create an activation key for the proxy

4s 356ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

5s 23ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

4s 7ms 2

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

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

Feature:Update activation keys 1m 13s 683ms 10 1 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

927ms 1

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

@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

4s 159ms 10

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

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

And I wait until I do not see "Loading..." text 1s 133ms

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

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

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

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

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

And I click on "Update Activation Key" 1s 137ms

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

@scc_credentials @susemanager

Scenario:
Update SLE SSH key with synced base product

< 1ms 14

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni

Scenario:
Update openSUSE Tumbleweed SSH key with synced base product

3s 165ms 10

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

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

And I wait until I do not see "Loading..." text 1s 603ms

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

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

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

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

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

And I click on "Update Activation Key" 56ms

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

@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

4s 513ms 10

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

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

And I wait until I do not see "Loading..." text 1s 127ms

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

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

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

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

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

And I click on "Update Activation Key" 1s 820ms

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

@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

35s 578ms 15 5 1

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

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

And I wait for child channels to appear 2s 906ms

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

And I wait for child channels to appear 800ms

And I include the recommended child channels 156ms

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

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

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

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

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

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

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

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

And I wait until "SLE-Module-Systems-Management-15-SP7-Pool for x86_64" has been checked 15s 1ms Show Error +

                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/setup_steps.rb:424:in `/^I wait until "([^"]*)" has been checked$/'
features/reposync/allcli_update_activationkeys.feature:178:in `I wait until "SLE-Module-Systems-Management-15-SP7-Pool for x86_64" has been checked'

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

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

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

And I click on "Update Activation Key" 0s

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

16s 272ms Show Info +

13:36:59:000 - 13:37:20:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/activationkeys/Edit.do?tid=7

Screenshot +

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

5s 61ms 9

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

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

And I wait for child channels to appear 2s 574ms

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

And I wait for child channels to appear 966ms

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

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

And I click on "Update Activation Key" 1s 127ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

3s 385ms 9

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

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

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

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

And I wait for child channels to appear 266ms

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

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

And I click on "Update Activation Key" 1s 59ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

5s 678ms 16

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

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

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

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

And I wait for child channels to appear 637ms

And I include the recommended child channels 160ms

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 1s 614ms

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

@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

3s 544ms 6

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

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

And I wait for child channels to appear 2s 79ms

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

And I click on "Update Activation Key" 1s 160ms

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

@skip_if_github_validation @deblike_minion

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

4s 174ms 6

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

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

And I wait for child channels to appear 2s 431ms

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

And I click on "Update Activation Key" 1s 435ms

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

@skip_if_github_validation @rhlike_minion

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

3s 494ms 6

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

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

And I wait for child channels to appear 2s 53ms

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

And I click on "Update Activation Key" 1s 122ms

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

Feature:Create bootstrap repositories 30s 629ms 3 1

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

3s 679ms 1

When I create the bootstrap repositories including custom channels 3s 679ms

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

3s 582ms 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 3s 582ms

@proxy

Scenario:
Create the bootstrap repository for Proxy

3s 112ms 1

When I create the bootstrap repository for "proxy" on the server 3s 112ms

@build_host

Scenario:
Create the bootstrap repository for Build Host

20s 254ms 1 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 3s 981ms Show Error +

                                            
 FAIL: mgrctl exec -it 'mgr-create-bootstrap-repo --create SLE-15-SP7-x86_64 --with-parent-channel sle-product-sles15-sp7-pool-x86_64 --with-custom-channels' returned status code = 1.
Output:

Creating bootstrap repo for SLE-15-SP7-x86_64
Directory walk started
Directory walk done - 0 packages
Temporary output repo path: /srv/www/htdocs/pub/repositories/sle/15/7/bootstrap.tmp/.repodata/
Preparing sqlite DBs
Pool started (with 5 workers)
Pool finished
ERROR: package 'venv-salt-minion' not found
ERROR: package 'dmidecode' not found
ERROR: package 'libunwind' not found

Suggestions:
mgr-create-bootstrap-repo uses the locally synchronized versions of files
from the Tools repository, and uses the locally synchronized pool channel
for dependency resolution.
Both should be fully synced before running the mgr-create-bootstrap-repo script.

 (ScriptError)
./features/support/remote_node.rb:169:in `run_local'
./features/support/remote_node.rb:117:in `run'
./features/step_definitions/command_steps.rb:1109:in `/^I create the bootstrap repository for "([^"]*)" on the server((?: without flushing)?)$/'
features/reposync/srv_create_bootstrap_repositories.feature:22:in `I create the bootstrap repository for "build_host" on the server'

16s 272ms Show Info +

13:38:19:000 - 13:38:23:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/activationkeys/Edit.do?tid=2

Screenshot +

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

Scenario:
Call spacewalk-debug on server

14s 113ms 1

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

Scenario:
Check the tomcat logs on server

820ms 1

Then the tomcat logs should not contain errors 820ms

Scenario:
Check salt event log for failures on server

2s 285ms 1

Then the salt event log on server should contain no failures 2s 285ms

Scenario:
Check the taskomatic logs on server

839ms 1

Then the taskomatic logs should not contain errors 839ms

Scenario:
Check for out of memory errors

816ms 1

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

Feature:Debug the clients after the testsuite has run 34s 328ms 1

Scenario:
Extract the logs from all our clients

34s 328ms 1

When I extract the log files from all our active nodes 34s 328ms

@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

111

Failed Scenarios

7

Skipped Scenarios

30

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

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

@build_host Scenario:The build host is healthy 5s 474ms 4

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

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

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

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

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

@scc_credentials Feature:List available channels and enable them 1m 37s 405ms 5 1

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

@scc_credentials Scenario:Refresh SCC 26s 680ms 1

@scc_credentials Scenario:Let the products page appear 2s 85ms 6

@scc_credentials Scenario:Use the products and architecture filters 2s 384ms 7

@scc_credentials @susemanager Scenario:View the channels list in the products page < 1ms 9

@scc_credentials @susemanager Scenario:Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools < 1ms 30

@uyuni Scenario:Partially add openSUSE Tumbleweed product, only including the required packages to generate the bootstrap repository 2m 12s 174ms 4

@containerized_server @proxy @uyuni Scenario:Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools 1m 27s 441ms 2

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 34s 900ms 20 1

@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 24s 5ms 7 1

@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 934ms 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 743ms 11

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

@rhlike_minion Scenario:Add a fake AppStream base channel 973ms 10

@rhlike_minion Scenario:Create a fake AppStream repository 1s 40ms 7

@rhlike_minion Scenario:Disable metadata check for the fake AppStream repository 11s 58ms 6

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

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

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

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

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

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

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

@sle_minion Scenario:Create custom repositories inside the SUSE custom channel 17s 822ms 1 1

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

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

@deblike_minion Scenario:Create a custom channel for Debian-like minions 2s 43ms 10

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

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

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

@sle_minion Scenario:Synchronize Fake-RPM-SUSE-Channel channel 6s 927ms 9

@sle_minion Scenario:Verify state of Fake-RPM-SUSE-Channel channel 10m 18s 287ms 2 1

@skip_if_github_validation Scenario:Synchronize Fake-Child-Channel-i586 channel 7s 276ms 9

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 6s 178ms 9

@deblike_minion Scenario:Synchronize Fake-Base-Channel-Debian-like channel 6s 423ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-RH-like channel 5s 126ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-AppStream channel 6s 425ms 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 47s 968ms 3 1

@sle_minion Scenario:Synchronize Devel-SUSE-Channel channel 29s 336ms 8 1 1

@proxy

Scenario:
The proxy is healthy

4s 460ms 4

@sle_minion

Scenario:
The minion is healthy

6s 539ms 4

@build_host

Scenario:
The build host is healthy

5s 474ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 364ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 421ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

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

677ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

669ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

641ms 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 639ms 7

@scc_credentials
Feature:List available channels and enable them 1m 37s 405ms 5 1

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

26s 680ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 85ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 384ms 7

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

@scc_credentials @susemanager

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

< 1ms 30

@uyuni

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

2m 12s 174ms 4

@containerized_server @proxy @uyuni

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

1m 27s 441ms 2

@scc_credentials @uyuni @build_host

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

34s 900ms 20 1

@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

24s 5ms 7 1

@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

934ms 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 743ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 493ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

973ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 40ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 58ms 6

@sle_minion

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

2s 322ms 9

@rhlike_minion

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

2s 761ms 9

@rhlike_minion

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

2s 623ms 9

@sle_minion

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

1s 730ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

710ms 7

@deblike_minion

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

1s 328ms 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 51s 47ms 8 1

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 115ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

17s 822ms 1 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 213ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

8s 102ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

2s 43ms 10

@deblike_minion

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

9s 869ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

2s 229ms 10

@rhlike_minion

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

8s 26ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

6s 927ms 9

@sle_minion

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

10m 18s 287ms 2 1

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

7s 276ms 9

@sle_minion

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

6s 178ms 9

@deblike_minion

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

6s 423ms 9

@rhlike_minion

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

5s 126ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

6s 425ms 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 47s 968ms 3 1

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

29s 336ms 8 1 1