Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QE: Adapt BV test suite code for Uyuni BV #7032

Merged
merged 3 commits into from
Aug 29, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion testsuite/documentation/cucumber-steps.md
Original file line number Diff line number Diff line change
Expand Up @@ -413,8 +413,9 @@ Note that the text area variant handles the new lines characters while the other
When I restart the spacewalk service
When I wait until "salt-minion" service is up and running on "rhlike_minion"
Then service "bind" is enabled on "proxy"
Then service "dhcpd" is running on "proxy"
And service "dhcpd" is running on "proxy"
When I restart the "bind" service on "sle_minion"
And I reload the "apache2" service on "proxy"
```

* File removal
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ Feature: Add the Alma 9 distribution custom repositories
Then I should see a "ruby-3.1" text
And I should see a "php-8.1" text

@susemanager
Scenario: Create a CLM project to remove AppStream metadata from Alma 9
When I follow the left menu "Content Lifecycle > Projects"
And I follow "Create Project"
Expand Down Expand Up @@ -44,3 +45,35 @@ Feature: Add the Alma 9 distribution custom repositories
And I enter "Initial build" as "message"
And I click the environment build button
Then I should see a "Version 1: Initial build" text

@uyuni
Scenario: Create a CLM project to remove AppStream metadata from Alma 9
When I follow the left menu "Content Lifecycle > Projects"
And I follow "Create Project"
And I enter "Remove AppStream metadata from Alma 9" as "name"
And I enter "no-appstream-alma-9" as "label"
And I click on "Create"
Then I should see a "Content Lifecycle Project - Remove AppStream metadata from Alma 9" text
When I click on "Attach/Detach Sources"
And I wait until I do not see "Loading" text
And I select "AlmaLinux 9 (x86_64)" from "selectedBaseChannel"
And I check "Uyuni Client Tools for AlmaLinux 9 (x86_64)"
And I check "Custom Channel for alma9_minion"
And I check "AlmaLinux 9 AppStream (x86_64)"
And I click on "Save"
Then I should see a "AlmaLinux 9 AppStream (x86_64)" text
When I click on "Attach/Detach Filters"
And I check "php-8.1: enable module php:8.1"
And I check "ruby-3.1: enable module ruby:3.1"
And I click on "Save"
Then I should see a "php-8.1: enable module php:8.1" text
When I click on "Add Environment"
And I enter "result" as "name"
And I enter "result" as "label"
And I enter "Filtered channels without AppStream channels" as "description"
And I click on "Save"
Then I should see a "not built" text
When I click on "Build"
And I enter "Initial build" as "message"
And I click the environment build button
Then I should see a "Version 1: Initial build" text
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
# Copyright (c) 2023 SUSE LLC
# Licensed under the terms of the MIT license.

@susemanager
@liberty9_minion
Feature: Add the Liberty Linux 9 distribution custom repositories
In order to use Liberty Linux 9 channels with Appstream modules
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ Feature: Add the Oracle 9 distribution custom repositories
Then I should see a "ruby-3.1" text
And I should see a "php-8.1" text

@susemanager
Scenario: Create a CLM project to remove AppStream metadata from Oracle 9
When I follow the left menu "Content Lifecycle > Projects"
And I follow "Create Project"
Expand All @@ -26,6 +27,7 @@ Feature: Add the Oracle 9 distribution custom repositories
And I wait until I do not see "Loading" text
And I select "oraclelinux9 for x86_64" from "selectedBaseChannel"
# "oraclelinux9-appstream for x86_64" is already checked
And I check "Uyuni Client Tools for Oracle Linux 9 (x86_64)"
And I check "Custom Channel for oracle9_minion"
And I click on "Save"
Then I should see a "EL9-Manager-Tools-Pool for x86_64 OL9" text
Expand All @@ -44,3 +46,35 @@ Feature: Add the Oracle 9 distribution custom repositories
And I enter "Initial build" as "message"
And I click the environment build button
Then I should see a "Version 1: Initial build" text

@uyuni
Scenario: Create a CLM project to remove AppStream metadata from Oracle 9
When I follow the left menu "Content Lifecycle > Projects"
And I follow "Create Project"
And I enter "Remove AppStream metadata from Oracle 9" as "name"
And I enter "no-appstream-oracle-9" as "label"
And I click on "Create"
Then I should see a "Content Lifecycle Project - Remove AppStream metadata from Oracle 9" text
When I click on "Attach/Detach Sources"
And I wait until I do not see "Loading" text
And I select "Oracle Linux 9 (x86_64)" from "selectedBaseChannel"
And I check "Uyuni Client Tools for Oracle Linux 9 (x86_64)"
And I check "Oracle Linux 9 AppStream (x86_64)"
And I check "Custom Channel for oracle9_minion"
And I click on "Save"
Then I should see a "Oracle Linux 9 AppStream (x86_64)" text
When I click on "Attach/Detach Filters"
And I check "php-8.1: enable module php:8.1"
And I check "ruby-3.1: enable module ruby:3.1"
And I click on "Save"
Then I should see a "php-8.1: enable module php:8.1" text
When I click on "Add Environment"
And I enter "result" as "name"
And I enter "result" as "label"
And I enter "Filtered channels without AppStream channels" as "description"
And I click on "Save"
Then I should see a "not built" text
When I click on "Build"
And I enter "Initial build" as "message"
And I click the environment build button
Then I should see a "Version 1: Initial build" text
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ Feature: Add the Rocky 8 distribution custom repositories
Scenario: Log in as admin user
Given I am authorized for the "Admin" section

@susemanager
Scenario: Add a child channel for Rocky 8 DVD repositories
When I follow the left menu "Software > Manage > Channels"
And I follow "Create Channel"
Expand All @@ -23,6 +24,17 @@ Feature: Add the Rocky 8 distribution custom repositories
And I click on "Create Channel"
Then I should see a "Channel Custom Channel for Rocky 8 DVD created" text

@uyuni
Scenario: Add a child channel for Rocky 8 DVD repositories
When I follow the left menu "Software > Manage > Channels"
And I follow "Create Channel"
And I enter "Custom Channel for Rocky 8 DVD" as "Channel Name"
And I enter "rocky-8-iso" as "Channel Label"
And I select "Rocky Linux 8 (x86_64)" from "Parent Channel"
And I enter "Custom channel" as "Channel Summary"
And I click on "Create Channel"
Then I should see a "Channel Custom Channel for Rocky 8 DVD created" text

Scenario: Add the Rocky 8 Appstream DVD repository
When I follow the left menu "Software > Manage > Repositories"
And I follow "Create Repository"
Expand Down Expand Up @@ -66,6 +78,7 @@ Feature: Add the Rocky 8 distribution custom repositories
Then I should see a "ruby-2.7" text
And I should see a "python-3.6" text

@susemanager
Scenario: Create a CLM project to remove AppStream metadata from Rocky 8
When I follow the left menu "Content Lifecycle > Projects"
And I follow "Create Project"
Expand Down Expand Up @@ -96,3 +109,36 @@ Feature: Add the Rocky 8 distribution custom repositories
And I enter "Initial build" as "message"
And I click the environment build button
Then I should see a "Version 1: Initial build" text

@uyuni
Scenario: Create a CLM project to remove AppStream metadata from Rocky 8
When I follow the left menu "Content Lifecycle > Projects"
And I follow "Create Project"
And I enter "Remove AppStream metadata from Rocky 8" as "name"
And I enter "no-appstream-8" as "label"
And I click on "Create"
Then I should see a "Content Lifecycle Project - Remove AppStream metadata from Rocky 8" text
When I click on "Attach/Detach Sources"
And I wait until I do not see "Loading" text
And I select "Rocky Linux 8 (x86_64)" from "selectedBaseChannel"
And I check "Uyuni Client Tools for Rocky Linux 8 (x86_64)"
And I check "Rocky Linux 8 - AppStream (x86_64)"
And I check "Custom Channel for Rocky 8 DVD"
And I check "Custom Channel for rocky8_minion"
And I click on "Save"
Then I should see a "Custom Channel for Rocky 8 DVD" text
When I click on "Attach/Detach Filters"
And I check "python-3.6: enable module python36:3.6"
And I check "ruby-2.7: enable module ruby:2.7"
And I click on "Save"
Then I should see a "python-3.6: enable module python36:3.6" text
When I click on "Add Environment"
And I enter "result" as "name"
And I enter "result" as "label"
And I enter "Filtered channels without AppStream channels" as "description"
And I click on "Save"
Then I should see a "not built" text
When I click on "Build"
And I enter "Initial build" as "message"
And I click the environment build button
Then I should see a "Version 1: Initial build" text
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ Feature: Add the Rocky 9 distribution custom repositories
Then I should see a "ruby-3.1" text
And I should see a "php-8.1" text

@susemanager
Scenario: Create a CLM project to remove AppStream metadata from Rocky 9
When I follow the left menu "Content Lifecycle > Projects"
And I follow "Create Project"
Expand Down Expand Up @@ -44,3 +45,35 @@ Feature: Add the Rocky 9 distribution custom repositories
And I enter "Initial build" as "message"
And I click the environment build button
Then I should see a "Version 1: Initial build" text

@uyuni
Scenario: Create a CLM project to remove AppStream metadata from Rocky 9
When I follow the left menu "Content Lifecycle > Projects"
And I follow "Create Project"
And I enter "Remove AppStream metadata from Rocky 9" as "name"
And I enter "no-appstream-9" as "label"
And I click on "Create"
Then I should see a "Content Lifecycle Project - Remove AppStream metadata from Rocky 9" text
When I click on "Attach/Detach Sources"
And I wait until I do not see "Loading" text
And I select "Rocky Linux 9 (x86_64)" from "selectedBaseChannel"
And I check "Uyuni Client Tools for Rocky Linux 9 (x86_64)"
And I check "Rocky Linux 9 AppStream (x86_64)"
And I check "Custom Channel for rocky9_minion"
And I click on "Save"
Then I should see a "Rocky Linux 9 AppStream (x86_64)" text
When I click on "Attach/Detach Filters"
And I check "php-8.1: enable module php:8.1"
And I check "ruby-3.1: enable module ruby:3.1"
And I click on "Save"
Then I should see a "php-8.1: enable module php:8.1" text
When I click on "Add Environment"
And I enter "result" as "name"
And I enter "result" as "label"
And I enter "Filtered channels without AppStream channels" as "description"
And I click on "Save"
Then I should see a "not built" text
When I click on "Build"
And I enter "Initial build" as "message"
And I click the environment build button
Then I should see a "Version 1: Initial build" text
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@
# 1) bootstrap a new Liberty Linux 9 minion
# 2) subscribe it to a base channel for testing

@susemanager
@liberty9_minion
Feature: Bootstrap a Liberty Linux 9 Salt minion

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@
# 1) bootstrap a new Liberty Linux 9 minion via salt-ssh
# 2) subscribe it to a base channel for testing

@susemanager
@liberty9_ssh_minion
Feature: Bootstrap a Liberty Linux 9 Salt SSH minion

Expand Down
22 changes: 19 additions & 3 deletions testsuite/features/build_validation/init_clients/proxy.feature
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Copyright (c) 2020-2022 SUSE LLC
# Copyright (c) 2020-2023 SUSE LLC
# Licensed under the terms of the MIT license.
#
# The scenarios in this feature are skipped if there is no proxy
Expand Down Expand Up @@ -41,17 +41,33 @@ Feature: Setup SUSE Manager proxy
Scenario: Detect latest Salt changes on the proxy
When I query latest Salt changes on "proxy"

Scenario: Copy the keys and configure the proxy
Scenario: Copy the server keys to the proxy
When I copy server's keys to the proxy
And I configure the proxy

Scenario: Configure the proxy
When I configure the proxy
And I allow all SSL protocols on the proxy's apache
And I reload the "apache2.service" service on "proxy"
And file "/etc/sysconfig/apache2" should contain "proxy" on "proxy"
And file "/etc/sysconfig/apache2" should contain "rewrite" on "proxy"
And file "/etc/sysconfig/apache2" should contain "version" on "proxy"
And file "/etc/sysconfig/apache2" should contain "ssl" on "proxy"
And file "/etc/sysconfig/apache2" should contain "access_compat" on "proxy"
And file "/etc/sysconfig/apache2" should contain "wsgi" on "proxy"
Then I should see "proxy" via spacecmd
And service "salt-broker" is active on "proxy"

@susemanager
Scenario: Check proxy system details
When I am on the Systems overview page of this "proxy"
Then I should see "proxy" short hostname
And I wait until I see "SUSE Manager Proxy" text, refreshing the page

@uyuni
Scenario: Check proxy system details
When I am on the Systems overview page of this "proxy"
Then I should see "proxy" short hostname
And I wait until I see "Uyuni Proxy" text, refreshing the page

Scenario: Check events history for failures on the proxy
When I check for failed events on history event page
Loading