@scope_configuration_channels @sle_minion @rhlike_minion @deblike_minion @ssh_minion

Feature: 0120 - 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	96.43 %
Failed	3.57 %

Total duration:

00:06:27.206

@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.132

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

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

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

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

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

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

@scope_configuration_channels

Scenario: Add a configuration file to the mixed configuration channel

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

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

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

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

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

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

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

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

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

@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.832

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

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

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

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

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

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

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

@scope_configuration_channels @rhlike_minion

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

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

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

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

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

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

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

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

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

@scope_configuration_channels @deblike_minion

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

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

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

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

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

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

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

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

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

@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.920

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

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

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

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

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

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

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

@scope_configuration_channels

Scenario: Deploy the file to all systems

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

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

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

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

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

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

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

@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.404

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

@scope_configuration_channels @rhlike_minion

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

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

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

@scope_configuration_channels @deblike_minion

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

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

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

@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:06.507

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

@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.470

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

+ 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.320

@scope_configuration_channels @rhlike_minion

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

1
1
1
Duration: 00:04:11.206

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

And I apply highstate on "rhlike_minion" 00:04:10.886

+ Show Error + Show Info + Screenshot

execution expired (Timeout::Error)
./features/support/commonlib.rb:89:in `repeat_until_timeout'
./features/support/remote_node.rb:189:in `run_until_ok'
./features/step_definitions/salt_steps.rb:655:in `/^I apply highstate on "([^"]*)"$/'
features/secondary/allcli_config_channel.feature:112:in `I apply highstate on "rhlike_minion"'

Salt command: salt uyuni-master-rhlike-minion state.highstate

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

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

And I apply highstate on "deblike_minion" 00:00:11.511

+ Show Info

Salt command: salt uyuni-master-deblike-minion state.highstate

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

@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.711

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

+ 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.853

@scope_configuration_channels @rhlike_minion

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

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

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

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

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

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

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

And I destroy "/etc/s-mgr" directory on "rhlike_minion" 00:00:00.315

@scope_configuration_channels @deblike_minion

Scenario: Unsubscribe Debian-like minion and delete configuration files

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

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

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

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

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

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

And I destroy "/etc/s-mgr" directory on "deblike_minion" 00:00:00.505

@scope_configuration_channels @ssh_minion

Scenario: Unsubscribe SSH minion and delete configuration files

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

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

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

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

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

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

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

@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.539

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

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

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

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

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

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

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

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

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

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

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

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

@scope_configuration_channels @sle_minion

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

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

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

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

@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.772

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

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

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

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

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

@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.995

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

@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.142

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

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

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

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

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

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

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

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

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

@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.133

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

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

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

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

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

@scope_configuration_channels

Scenario: Cleanup: remove the mixed configuration channel

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

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

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

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

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

@scope_configuration_channels @sle_minion

Scenario: Cleanup: delete configuration files on remaining Salt minion

@scope_configuration_channels

Feature: 0120 - 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