Feature: 0016 - Create activation keys

Description: In order to register systems to the server
As the testing user
I want to use activation keys

File name: srv_create_activationkey.feature

Relative path: reposync/srv_create_activationkey.feature

Scenarios

Chart

Status

Progress

Passed	100.00 %
Failed	0.00 %

Total duration:

00:00:27.551

Scenario: Log in as admin user

@sle_minion

Scenario: Create an activation key with a channel

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" 00:00:02.935

Then I should get the new activation key "1-SUSE-KEY-x86_64" 00:00:01.019

@rhlike_minion

Scenario: Create an activation key for RedHat-like minion

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" 00:00:02.090

Then I should get the new activation key "1-RH-LIKE-KEY" 00:00:00.959

@deblike_minion

Scenario: Create an activation key for Debian-like minion

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" 00:00:02.154

Then I should get the new activation key "1-DEBLIKE-KEY" 00:00:01.460

@ssh_minion

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

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" 00:00:02.228

Then I should get the new activation key "1-SUSE-SSH-KEY-x86_64" 00:00:00.967

@ssh_minion

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

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" 00:00:02.048

Then I should get the new activation key "1-SUSE-SSH-TUNNEL-KEY-x86_64" 00:00:00.969

@proxy

Scenario: Create an activation key for the proxy

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

Then I should get the new activation key "1-PROXY-KEY-x86_64" 00:00:00.944

@build_host

Scenario: Create an activation key for the build host

When I create an activation key with id "BUILD-HOST-KEY-x86_64", description "Build host Key x86_64" 00:00:02.101

And I set the entitlements of the activation key "1-BUILD-HOST-KEY-x86_64" to "container_build_host, osimage_build_host" 00:00:01.012

Then I should get the new activation key "1-BUILD-HOST-KEY-x86_64" 00:00:00.987

@scc_credentials

Scenario: Create an activation key for the terminal

When I create an activation key with id "TERMINAL-KEY-x86_64", description "Terminal Key x86_64" 00:00:02.087

Then I should get the new activation key "1-TERMINAL-KEY-x86_64" 00:00:01.050