@scope_configuration_channels @sle_minion @rhlike_minion @deblike_minion @ssh_minion

Feature: 0119 - Management of configuration of all types of clients in a single channel

File name: allcli_config_channel.feature

Relative path: secondary/allcli_config_channel.feature

Scenarios

Chart

Status

Progress

Passed	71.43 %
Failed	28.57 %

Total duration:

00:10:29.306

@scope_configuration_channels

Scenario: Log in as org admin user

@scope_configuration_channels

Scenario: Create a configuration channel for mixed client types

When I follow the left menu "Configuration > Channels" 00:00:00.154

And I follow "Create Config Channel" 00:00:00.294

And I enter "Mixed Channel" as "cofName" 00:00:00.069

And I enter "mixedchannel" as "cofLabel" 00:00:00.065

And I enter "This is a configuration channel for different system types" as "cofDescription" 00:00:00.104

And I click on "Create Config Channel" 00:00:01.133

Then I should see a "Mixed Channel" text 00:00:00.069

@scope_configuration_channels

Scenario: Add a configuration file to the mixed configuration channel

When I follow the left menu "Configuration > Channels" 00:00:00.073

And I follow "Mixed Channel" 00:00:00.516

And I follow "Create Configuration File or Directory" 00:00:00.639

And I enter "/etc/s-mgr/config" as "cffPath" 00:00:00.074

And I enter "COLOR=white" in the editor 00:00:00.005

And I click on "Create Configuration File" 00:00:00.072

Then I should see a "Revision 1 of /etc/s-mgr/config from channel Mixed Channel" text 00:00:00.101

And file "/srv/susemanager/salt/manager_org_1/mixedchannel/init.sls" should exist on server 00:00:03.168

And file "/srv/susemanager/salt/manager_org_1/mixedchannel/etc/s-mgr/config" should exist on server 00:00:03.573

@scope_configuration_channels @sle_minion

Scenario: Subscribe a Salt minion to the configuration channel

When I am on the Systems overview page of this "sle_minion" 00:00:01.774

And I follow "Configuration" in the content area 00:00:00.079

And I follow "Manage Configuration Channels" in the content area 00:00:00.075

And I follow first "Subscribe to Channels" in the content area 00:00:00.075

And I check "Mixed Channel" in the list 00:00:00.063

And I click on "Continue" 00:00:00.657

And I click on "Update Channel Rankings" 00:00:00.814

Then I should see a "Channel Subscriptions successfully changed for" text 00:00:00.081

@scope_configuration_channels @rhlike_minion

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

7
1
Duration: 00:00:01.052

When I am on the Systems overview page of this "rhlike_minion" 00:00:01.052

+ Show Error + Screenshot

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

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

And I follow "Manage Configuration Channels" in the content area 0s

And I follow first "Subscribe to Channels" in the content area 0s

And I check "Mixed Channel" in the list 0s

And I click on "Continue" 0s

And I click on "Update Channel Rankings" 0s

Then I should see a "Channel Subscriptions successfully changed for" text 0s

@scope_configuration_channels @deblike_minion

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

7
1
Duration: 00:00:01.047

When I am on the Systems overview page of this "deblike_minion" 00:00:01.047

+ Show Error + Screenshot

No system found for hostname: uyuni-master-deblike-minion (RuntimeError)
./features/support/commonlib.rb:444:in `get_system_id'
./features/step_definitions/navigation_steps.rb:502:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/secondary/allcli_config_channel.feature:54:in `I am on the Systems overview page of this "deblike_minion"'

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

And I follow "Manage Configuration Channels" in the content area 0s

And I follow first "Subscribe to Channels" in the content area 0s

And I check "Mixed Channel" in the list 0s

And I click on "Continue" 0s

And I click on "Update Channel Rankings" 0s

Then I should see a "Channel Subscriptions successfully changed for" text 0s

@scope_configuration_channels @ssh_minion

Scenario: Subscribe a SSH minion to the configuration channel

When I am on the Systems overview page of this "ssh_minion" 00:00:01.998

And I follow "Configuration" in the content area 00:00:00.080

And I follow "Manage Configuration Channels" in the content area 00:00:00.067

And I follow first "Subscribe to Channels" in the content area 00:00:00.075

And I check "Mixed Channel" in the list 00:00:00.073

And I click on "Continue" 00:00:00.691

And I click on "Update Channel Rankings" 00:00:00.818

Then I should see a "Channel Subscriptions successfully changed for" text 00:00:00.078

@scope_configuration_channels

Scenario: Deploy the file to all systems

When I follow the left menu "Configuration > Channels" 00:00:00.157

And I follow "Mixed Channel" 00:00:00.547

And I follow "Deploy all configuration files to all subscribed systems" 00:00:00.518

Then I should see a "/etc/s-mgr/config" link 00:00:00.013

When I click on "Deploy Files to Selected Systems" 00:00:00.920

Then I should see a "revision-deploys are being scheduled," text 00:00:00.071

And I should see a "0 revision-deploys overridden." text 00:00:00.067

@scope_configuration_channels @sle_minion

Scenario: Check that file has been created on SLE minion

When I wait until file "/etc/s-mgr/config" exists on "sle_minion" 00:00:02.527

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 00:00:00.971

@scope_configuration_channels @rhlike_minion

Scenario: Check that file has been created on Red Hat-like minion

1
1
Duration: 00:04:10.003

When I wait until file "/etc/s-mgr/config" exists on "rhlike_minion" 00:04:10.003

+ Show Error + Screenshot

execution expired (Timeout::Error)
./features/support/commonlib.rb:89:in `repeat_until_timeout'
./features/step_definitions/command_steps.rb:816:in `/^I wait at most (\d+) seconds until file "([^"]*)" exists on "([^"]*)"$/'
./features/step_definitions/command_steps.rb:811:in `/^I wait until file "([^"]*)" exists on "([^"]*)"$/'
features/secondary/allcli_config_channel.feature:90:in `I wait until file "/etc/s-mgr/config" exists on "rhlike_minion"'

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "rhlike_minion" 0s

@scope_configuration_channels @deblike_minion

Scenario: Check that file has been created on Debian-like minion

1
1
Duration: 00:04:10.004

When I wait until file "/etc/s-mgr/config" exists on "deblike_minion" 00:04:10.004

+ Show Error + Screenshot

execution expired (Timeout::Error)
./features/support/commonlib.rb:89:in `repeat_until_timeout'
./features/step_definitions/command_steps.rb:816:in `/^I wait at most (\d+) seconds until file "([^"]*)" exists on "([^"]*)"$/'
./features/step_definitions/command_steps.rb:811:in `/^I wait until file "([^"]*)" exists on "([^"]*)"$/'
features/secondary/allcli_config_channel.feature:95:in `I wait until file "/etc/s-mgr/config" exists on "deblike_minion"'

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "deblike_minion" 0s

@scope_configuration_channels @ssh_minion

Scenario: Check that file has been created on SSH minion

When I wait until file "/etc/s-mgr/config" exists on "ssh_minion" 00:00:00.730

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "ssh_minion" 00:00:00.852

@scope_configuration_channels @sle_minion

Scenario: Apply highstate to override changed content on SLE minion

When I store "COLOR=blue" into file "/etc/s-mgr/config" on "sle_minion" 00:00:00.960

And I apply highstate on "sle_minion" 00:00:14.882

+ Show Info

Salt command: salt uyuni-master-suse-minion.sumaci.aws state.highstate

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 00:00:01.385

@scope_configuration_channels @rhlike_minion

Scenario: Apply highstate to override changed content on Red Hat-like minion

2
1
Duration: 00:00:00.306

When I store "COLOR=blue" into file "/etc/s-mgr/config" on "rhlike_minion" 00:00:00.306

+ Show Error + Screenshot

FAIL: echo "COLOR=blue" ) /etc/s-mgr/config returned status code = 1.
Output:
 (ScriptError)
./features/support/remote_node.rb:172:in `run_local'
./features/support/remote_node.rb:120:in `run'
./features/step_definitions/file_management_steps.rb:47:in `/^I store "([^"]*)" into file "([^"]*)" on "([^"]*)"$/'
features/secondary/allcli_config_channel.feature:111:in `I store "COLOR=blue" into file "/etc/s-mgr/config" on "rhlike_minion"'

And I apply highstate on "rhlike_minion" 0s

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "rhlike_minion" 0s

@scope_configuration_channels @deblike_minion

Scenario: Apply highstate to override changed content on Debian-like minion

2
1
Duration: 00:00:01.065

When I store "COLOR=blue" into file "/etc/s-mgr/config" on "deblike_minion" 00:00:01.065

+ Show Error + Screenshot

FAIL: echo "COLOR=blue" ) /etc/s-mgr/config returned status code = 1.
Output:
 (ScriptError)
./features/support/remote_node.rb:172:in `run_local'
./features/support/remote_node.rb:120:in `run'
./features/step_definitions/file_management_steps.rb:47:in `/^I store "([^"]*)" into file "([^"]*)" on "([^"]*)"$/'
features/secondary/allcli_config_channel.feature:117:in `I store "COLOR=blue" into file "/etc/s-mgr/config" on "deblike_minion"'

And I apply highstate on "deblike_minion" 0s

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "deblike_minion" 0s

@scope_configuration_channels @ssh_minion

Scenario: Apply highstate to override changed content on SSH minion

When I store "COLOR=blue" into file "/etc/s-mgr/config" on "ssh_minion" 00:00:00.722

And I apply highstate on "ssh_minion" 00:00:26.577

+ Show Info

Salt command: mgr-salt-ssh uyuni-master-suse-sshminion.sumaci.aws state.highstate

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "ssh_minion" 00:00:00.871

@scope_configuration_channels @rhlike_minion

Scenario: Unsubscribe Red Hat-like minion and delete configuration files

3
1
3
Duration: 00:00:10.657

When I follow the left menu "Configuration > Channels" 00:00:00.092

And I follow "Mixed Channel" 00:00:00.479

And I follow "Systems" in the content area 00:00:00.078

And I check the "rhlike_minion" client 00:00:10.006

+ Show Error + Screenshot

Unable to find xpath "//table/tbody/tr[.//td[contains(.,'uyuni-master-rhlike-minion')]]//input[@type='checkbox']" (Capybara::ElementNotFound)
./features/support/navigation_step_helper.rb:32:in `toggle_checkbox_in_list'
./features/step_definitions/navigation_steps.rb:556:in `/^I check the "([^"]*)" client$/'
features/secondary/allcli_config_channel.feature:132:in `I check the "rhlike_minion" client'

And I click on "Unsubscribe systems" 0s

Then I should see a "Successfully unsubscribed 1 system(s)." text 0s

And I destroy "/etc/s-mgr" directory on "rhlike_minion" 0s

@scope_configuration_channels @deblike_minion

Scenario: Unsubscribe Debian-like minion and delete configuration files

3
1
3
Duration: 00:00:10.657

When I follow the left menu "Configuration > Channels" 00:00:00.088

And I follow "Mixed Channel" 00:00:00.473

And I follow "Systems" in the content area 00:00:00.079

And I check the "deblike_minion" client 00:00:10.015

+ Show Error + Screenshot

Unable to find xpath "//table/tbody/tr[.//td[contains(.,'uyuni-master-deblike-minion')]]//input[@type='checkbox']" (Capybara::ElementNotFound)
./features/support/navigation_step_helper.rb:32:in `toggle_checkbox_in_list'
./features/step_definitions/navigation_steps.rb:556:in `/^I check the "([^"]*)" client$/'
features/secondary/allcli_config_channel.feature:142:in `I check the "deblike_minion" client'

And I click on "Unsubscribe systems" 0s

Then I should see a "Successfully unsubscribed 1 system(s)." text 0s

And I destroy "/etc/s-mgr" directory on "deblike_minion" 0s

@scope_configuration_channels @ssh_minion

Scenario: Unsubscribe SSH minion and delete configuration files

When I follow the left menu "Configuration > Channels" 00:00:00.076

And I follow "Mixed Channel" 00:00:00.461

And I follow "Systems" in the content area 00:00:00.065

And I check the "ssh_minion" client 00:00:00.071

And I click on "Unsubscribe systems" 00:00:00.599

Then I should see a "Successfully unsubscribed 1 system(s)." text 00:00:00.080

And I destroy "/etc/s-mgr" directory on "ssh_minion" 00:00:00.782

@scope_configuration_channels @sle_minion

Scenario: Change file on Salt minion and compare

When I am on the Systems overview page of this "sle_minion" 00:00:01.753

And I store "COLOR=red" into file "/etc/s-mgr/config" on "sle_minion" 00:00:00.864

And I follow "Configuration" in the content area 00:00:00.081

And I follow "Compare Files" in the content area 00:00:00.071

And I check "/etc/s-mgr/config" in the list 00:00:00.064

And I click on "Compare Files" 00:00:00.737

And I click on "Schedule Compare" 00:00:01.003

Then I should see a "1 files scheduled for comparison." text 00:00:00.077

When I wait until event "Show differences between profiled config files and deployed config files scheduled" is completed 00:00:02.692

Then I should see a "Differences exist" link 00:00:00.013

When I follow "Differences exist" 00:00:00.458

Then I should see a "+COLOR=white" text 00:00:00.068

And I should see a "-COLOR=red" text 00:00:00.067

@scope_configuration_channels @sle_minion

Scenario: Check configuration channel and files via API for Salt minion

Then channel "mixedchannel" should exist 00:00:00.986

And channel "mixedchannel" should contain file "/etc/s-mgr/config" 00:00:00.967

And "sle_minion" should be subscribed to channel "mixedchannel" 00:00:00.965

@scope_configuration_channels @sle_minion

Scenario: Extend configuration channel and deploy files via API for Salt minion

When I store "COLOR=green" into file "/etc/s-mgr/config" on "sle_minion" 00:00:00.517

And I add file "/etc/s-mgr/other" containing "NAME=Dante" to channel "mixedchannel" 00:00:01.121

And I deploy all systems registered to channel "mixedchannel" 00:00:01.216

And I wait until file "/etc/s-mgr/other" exists on "sle_minion" 00:00:02.050

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 00:00:00.970

And file "/etc/s-mgr/other" should contain "NAME=Dante" on "sle_minion" 00:00:00.990

@scope_configuration_channels @sle_minion

Scenario: Unsubscribe systems via API for Salt minion

When I unsubscribe "sle_minion" from configuration channel "mixedchannel" 00:00:01.987

Then "sle_minion" should not be subscribed to channel "mixedchannel" 00:00:01.460

@scope_configuration_channels @sle_minion

Scenario: Re-add SLE Minion via SSM

When I follow the left menu "Systems > System List > All" 00:00:00.167

And I click on the clear SSM button 00:00:00.062

And I check the "sle_minion" client 00:00:00.468

And I follow the left menu "Systems > System Set Manager > Overview" 00:00:00.561

And I follow "config channel subscriptions" in the content area 00:00:00.079

And I check "Mixed Channel" in the list 00:00:00.069

And I click on "Continue" 00:00:00.548

And I click on "Apply Subscriptions" 00:00:00.921

And I click on "Confirm" 00:00:00.817

Then I should see a "Configuration channel subscriptions changed for 1 system successfully." text 00:00:00.073

@scope_configuration_channels @sle_minion

Scenario: Cleanup: remove remaining Salt minion from configuration channel

When I follow the left menu "Configuration > Channels" 00:00:00.156

And I follow "Mixed Channel" 00:00:00.478

And I follow "Systems" in the content area 00:00:00.077

And I check the "sle_minion" client 00:00:00.062

And I click on "Unsubscribe systems" 00:00:00.556

Then I should see a "Successfully unsubscribed 1 system(s)." text 00:00:00.058

@scope_configuration_channels

Scenario: Cleanup: remove the mixed configuration channel

When I follow the left menu "Configuration > Channels" 00:00:00.077

And I follow "Mixed Channel" 00:00:00.386

And I follow "Delete Channel" 00:00:00.242

And I click on "Delete Config Channel" 00:00:00.457

Then file "/srv/susemanager/salt/manager_org_1/mixedchannel/init.sls" should not exist on server 00:00:02.994

@scope_configuration_channels @sle_minion

Scenario: Cleanup: delete configuration files on remaining Salt minion

@scope_configuration_channels

Feature: 0119 - Management of configuration of all types of clients in a single channel

Scenarios

Scenario: Log in as org admin user

Scenario: Create a configuration channel for mixed client types

Scenario: Add a configuration file to the mixed configuration channel

Scenario: Subscribe a Salt minion to the configuration channel

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

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

Scenario: Subscribe a SSH minion to the configuration channel

Scenario: Deploy the file to all systems

Scenario: Check that file has been created on SLE minion

Scenario: Check that file has been created on Red Hat-like minion

Scenario: Check that file has been created on Debian-like minion

Scenario: Check that file has been created on SSH minion

Scenario: Apply highstate to override changed content on SLE minion

Scenario: Apply highstate to override changed content on Red Hat-like minion

Scenario: Apply highstate to override changed content on Debian-like minion

Scenario: Apply highstate to override changed content on SSH minion

Scenario: Unsubscribe Red Hat-like minion and delete configuration files

Scenario: Unsubscribe Debian-like minion and delete configuration files

Scenario: Unsubscribe SSH minion and delete configuration files

Scenario: Change file on Salt minion and compare

Scenario: Check configuration channel and files via API for Salt minion

Scenario: Extend configuration channel and deploy files via API for Salt minion

Scenario: Unsubscribe systems via API for Salt minion

Scenario: Re-add SLE Minion via SSM

Scenario: Cleanup: remove remaining Salt minion from configuration channel

Scenario: Cleanup: remove the mixed configuration channel

Scenario: Cleanup: delete configuration files on remaining Salt minion

Scenario: Cleanup: remove remaining systems from SSM after tests of configuration channel on all clients