@skip_if_github_validation @scope_cobbler @flaky

Feature: 0080 - Cobbler and distribution autoinstallation

File name: srv_cobbler_distro.feature

Relative path: secondary/srv_cobbler_distro.feature

Scenarios

Chart

Status

Progress

Passed	96.15 %
Failed	3.85 %

Total duration:

00:02:27.339

@skip_if_github_validation @scope_cobbler

Scenario: Start Cobbler monitoring

When I start local monitoring of Cobbler 00:00:13.922

And I backup Cobbler settings file 00:00:02.530

@skip_if_github_validation @scope_cobbler

Scenario: Log in as testing user

Given I am authorized as "testing" with password "testing" 00:00:02.466

And I am logged in via the Cobbler API as user "testing" with password "testing" 00:00:01.591

@skip_if_github_validation @scope_cobbler

Scenario: Copy cobbler profiles on the server

@skip_if_github_validation @scope_cobbler

Scenario: Ask cobbler to create a distribution via API

Given cobblerd is running 00:00:00.003

When I create "testdistro" kickstart tree via the API 00:00:01.568

@skip_if_github_validation @scope_cobbler

Scenario: Create dummy profile

Given cobblerd is running 00:00:00.002

When I create a "testprofile" profile via the API using import file for "testdistro" distribution 00:00:01.648

@skip_if_github_validation @scope_cobbler

Scenario: Check cobbler created distro and profile

When I follow the left menu "Systems > Autoinstallation > Profiles" 00:00:00.226

Then I should see a "testprofile" text 00:00:00.069

And I should see a "testdistro" text 00:00:00.068

@skip_if_github_validation @scope_cobbler

Scenario: Create SUSE distribution with installer updates

When I follow the left menu "Systems > Autoinstallation > Distributions" 00:00:00.082

And I follow "Create Distribution" 00:00:00.320

And I enter "SLE-15-FAKE" as "label" 00:00:00.066

And I enter "/var/autoinstall/SLES15-SP7-x86_64/DVD1/" as "basepath" 00:00:00.097

And I select "SLE-Product-SLES15-SP7-Pool for x86_64" from "channelid" 00:00:00.296

And I select "SUSE Linux Enterprise 15" from "installtype" 00:00:00.069

And I click on "Create Autoinstallable Distribution" 00:00:00.898

And I wait until I see "Autoinstallable Distribution Created" text 00:00:00.073

Then I should see a "Autoinstallable Distributions" text 00:00:00.072

And I should see a "SLE-15-FAKE" link 00:00:00.013

When I follow "SLE-15-FAKE" 00:00:00.428

Then I should see "self_update=http://" in field identified by "kernelopts" 00:00:00.024

@skip_if_github_validation @scope_cobbler

Scenario: Create a distribution via the UI

When I follow the left menu "Systems > Autoinstallation > Distributions" 00:00:00.104

And I follow "Create Distribution" 00:00:00.395

When I enter "fedora_kickstart_distro" as "label" 00:00:00.071

And I enter "/var/autoinstall/Fedora_12_i386/" as "basepath" 00:00:00.082

And I select "Fedora" from "installtype" 00:00:00.060

And I click on "Create Autoinstallable Distribution" 00:00:00.740

Then I should see a "Autoinstallable Distributions" text 00:00:00.073

And I should see a "fedora_kickstart_distro" link 00:00:00.013

@skip_if_github_validation @scope_cobbler

Scenario: Create a distribution via the API, without kernel options

When I create "fedora_kickstart_distro_api" kickstart tree via the API 00:00:01.418

When I follow the left menu "Systems > Autoinstallation > Distributions" 00:00:00.079

Then I should see a "fedora_kickstart_distro_api" link 00:00:00.013

@skip_if_github_validation @scope_cobbler

Scenario: Create a distribution via the API, with kernel options

When I create a kickstart tree with kernel options via the API 00:00:01.453

When I follow the left menu "Systems > Autoinstallation > Distributions" 00:00:00.073

Then I should see a "fedora_kickstart_distro_kernel_api" link 00:00:00.012

@skip_if_github_validation @scope_cobbler

Scenario: Update a distribution via the API

When I update a kickstart tree via the API 00:00:01.681

When I follow the left menu "Systems > Autoinstallation > Distributions" 00:00:00.074

And I follow "fedora_kickstart_distro_api" 00:00:00.344

Then option "Generic RPM" is selected as "installtype" 00:00:00.085

And I should see "self_update=0" in field identified by "kernelopts" 00:00:00.022

And I should see "self_update=1" in field identified by "postkernelopts" 00:00:00.026

@skip_if_github_validation @scope_cobbler

Scenario: Create a profile via the UI

When I follow the left menu "Systems > Autoinstallation > Profiles" 00:00:00.078

And I follow "Create Kickstart Profile" 00:00:00.336

When I enter "fedora_kickstart_profile" as "kickstartLabel" 00:00:00.079

And I click on "Next" 00:00:00.352

And I click on "Next" 00:00:00.428

And I enter "linux" as "rootPassword" 00:00:00.054

And I enter "linux" as "rootPasswordConfirm" 00:00:00.061

And I click on "Finish" 00:00:01.753

Then I should see a "Autoinstallation: fedora_kickstart_profile" text 00:00:00.084

And I should see a "Autoinstallation Details" link 00:00:00.013

@skip_if_github_validation @scope_cobbler

Scenario: Upload a profile via the UI

When I follow the left menu "Systems > Autoinstallation > Profiles" 00:00:00.079

And I follow "Upload Kickstart/AutoYaST File" 00:00:00.380

When I enter "fedora_kickstart_profile_upload" as "kickstartLabel" 00:00:00.083

And I select "fedora_kickstart_distro" from "kstreeId" 00:00:00.052

And I attach the file "/example.ks" to "fileUpload" 00:00:00.039

And I click on "Create" 00:00:01.619

Then I should see a "Autoinstallation: fedora_kickstart_profile_upload" text 00:00:00.101

And I should see a "Autoinstallation Details" text 00:00:00.101

@skip_if_github_validation @scope_cobbler

Scenario: Add an unprovisioned range to the created profile

When I follow the left menu "Systems > Autoinstallation > Profiles" 00:00:00.081

And I follow "fedora_kickstart_profile" 00:00:00.654

And I follow "Unprovisioned Autoinstallation" 00:00:00.418

And I enter "10" as "octet1a" 00:00:00.056

And I enter "10" as "octet1b" 00:00:00.057

And I enter "0" as "octet1c" 00:00:00.057

And I enter "100" as "octet1d" 00:00:00.058

And I enter "10" as "octet2a" 00:00:00.058

And I enter "10" as "octet2b" 00:00:00.059

And I enter "0" as "octet2c" 00:00:00.056

And I enter "200" as "octet2d" 00:00:00.055

And I click on "Add IP Range" 00:00:00.069

Then I should see a "Successfully added IP Range" text 00:00:00.844

@skip_if_github_validation @scope_cobbler

Scenario: Add a variable to the uploaded profile

When I follow the left menu "Systems > Autoinstallation > Profiles" 00:00:00.081

And I follow "fedora_kickstart_profile_upload" 00:00:00.586

And I follow "Variables" 00:00:00.396

And I enter "my_var=A_Test_String" as "variables" 00:00:00.078

And I click on "Update Variables" 00:00:00.067

And I follow "Autoinstallation File" 00:00:00.517

Then I should see a "A_Test_String" text 00:00:00.063

@skip_if_github_validation @scope_cobbler

Scenario: Add a kernel option to the created profile

When I follow the left menu "Systems > Autoinstallation > Profiles" 00:00:00.079

And I follow "fedora_kickstart_profile" 00:00:00.564

And I enter "kernel_option=a_value" as "kernel_options" 00:00:00.087

And I click on "Update" 00:00:00.070

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "kernel_option=a_value" on server 00:00:03.085

@skip_if_github_validation @scope_cobbler

Scenario: Add a kernel option to the uploaded profile

When I follow the left menu "Systems > Autoinstallation > Profiles" 00:00:00.080

And I follow "fedora_kickstart_profile_upload" 00:00:00.523

And I enter "kernel_option2=a_value2" as "kernel_options" 00:00:00.075

And I click on "Update" 00:00:00.067

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "kernel_option2=a_value2" on server 00:00:04.457

@skip_if_github_validation @scope_cobbler

Scenario: Check default snippets

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 00:00:00.085

And I follow "Default Snippets" 00:00:00.357

And I enter "spacewalk/sles_no_signature_checks" as the filtered snippet name 00:00:00.098

And I click on the filter button 00:00:00.491

And I follow "spacewalk/sles_no_signature_checks" 00:00:00.464

Then I should see "<signature-handling>" in the textarea 00:00:00.016

@skip_if_github_validation @scope_cobbler

Scenario: Create a snippet

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 00:00:00.076

And I follow "Create Snippet" 00:00:00.302

And I enter "created_test_snippet" as "name" 00:00:00.071

And I enter "<test_element>a text string</test_element>" in the editor 00:00:00.007

And I click on "Create Snippet" 00:00:00.067

Then I should see a "created_test_snippet created successfully." text 00:00:00.690

@skip_if_github_validation @scope_cobbler

Scenario: Delete a snippet

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 00:00:00.086

And I follow "created_test_snippet" 00:00:00.369

And I follow "Delete Snippet" 00:00:00.237

And I click on "Delete Snippet" 00:00:00.437

Then I should see a "created_test_snippet deleted successfully." text 00:00:00.069

@skip_if_github_validation @scope_cobbler

Scenario: Test for PXE environment files

Given cobblerd is running 00:00:00.011

When I wait until file "/srv/tftpboot/pxelinux.cfg/default" exists on server 00:00:02.614

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "inst.ks=.*fedora_kickstart_profile:1" on server 00:00:02.500

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "inst.ks=.*fedora_kickstart_profile_upload:1" on server 00:00:02.524

And I wait until file "/srv/tftpboot/images/fedora_kickstart_distro:1:SUSETest/initrd.img" exists on server 00:00:04.593

And I wait until file "/srv/tftpboot/images/fedora_kickstart_distro:1:SUSETest/vmlinuz" exists on server 00:00:02.576

And I wait until file "/srv/tftpboot/menu.c32" exists on server 00:00:02.516

And I wait until file "/srv/tftpboot/pxelinux.0" exists on server 00:00:02.485

@skip_if_github_validation @scope_cobbler

Scenario: Trigger the creation of a cobbler system record

When I clear the caches on the server 00:00:03.700

And I am on the Systems overview page of this "sle_minion" 00:00:02.026

And I follow "Provisioning" 00:00:01.052

And I click on profile "testprofile" 00:00:00.061

And I click on "Create PXE installation configuration" 00:00:01.439

Then I should see a "System record created" text 00:00:00.091

And I wait until file "/srv/tftpboot/pxelinux.cfg/01-*" contains "autoyast=" on server 00:00:02.263

@skip_if_github_validation @scope_cobbler

Scenario: Create a cobbler system record via API

When I create a system record 00:00:01.334

And I wait until file "/srv/tftpboot/pxelinux.cfg/01-00-22-22-77-ee-cc" contains "inst.ks=.*testserver:1" on server 00:00:02.517

Then the cobbler report should contain "testserver.example.com" for cobbler system name "testserver:1" 00:00:03.336

And the cobbler report should contain "1.1.1.1" for cobbler system name "testserver:1" 00:00:03.183

And the cobbler report should contain "00:22:22:77:ee:cc" for cobbler system name "testserver:1" 00:00:04.774

@skip_if_github_validation @scope_cobbler

Scenario: Cleanup: delete test profiles and distributions using API

When I wait for "10" seconds 00:00:10.000

When I delete profile and distribution using the API for "testdistro" kickstart tree 00:00:01.387

When I delete profile and distribution using the API for "fedora_kickstart_distro" kickstart tree 00:00:01.687

When I delete profile and distribution using the API for "fedora_kickstart_distro_api" kickstart tree 00:00:01.745

When I delete profile and distribution using the API for "fedora_kickstart_distro_kernel_api" kickstart tree 00:00:01.232

When I delete profile and distribution using the API for "SLE-15-FAKE" kickstart tree 00:00:01.187

When I follow the left menu "Systems > Autoinstallation > Distributions" 00:00:00.168

And I should not see a "testdistro" text 00:00:00.064

And I should not see a "fedora_kickstart_distro" text 00:00:00.060

And I should not see a "fedora_kickstart_distro_api" text 00:00:00.059

And I should not see a "fedora_kickstart_distro_kernel_api" text 00:00:00.059

And I should not see a "SLE-15-FAKE" text 00:00:00.069

@skip_if_github_validation @scope_cobbler @flaky

Scenario: Check for errors in Cobbler monitoring

1
1
Duration: 00:00:19.399

When I wait for "5" seconds 00:00:05.000

Then the local logs for Cobbler should not contain errors 00:00:14.399

+ Show Error + Show Info + Screenshot

Errors in Cobbler logs (ScriptError)
./features/step_definitions/cobbler_steps.rb:293:in `/^the local logs for Cobbler should not contain errors$/'
features/secondary/srv_cobbler_distro.feature:200:in `the local logs for Cobbler should not contain errors'

Error in Cobbler log:
["[2026-06-15_214151_sync] 2026-06-15T21:41:52 - ERROR | ### TASK FAILED ###\n"]

Error in Cobbler debug log:
[{"threadName"=>"2026-06-15_214151_sync", "asctime"=>"2026-06-15 21:41:52,457", "levelname"=>"ERROR", "message"=>"### TASK FAILED ###"}]

@skip_if_github_validation @scope_cobbler

Feature: 0080 - Cobbler and distribution autoinstallation

Scenarios

Scenario: Start Cobbler monitoring

Scenario: Log in as testing user

Scenario: Copy cobbler profiles on the server

Scenario: Ask cobbler to create a distribution via API

Scenario: Create dummy profile

Scenario: Check cobbler created distro and profile

Scenario: Create SUSE distribution with installer updates

Scenario: Create a distribution via the UI

Scenario: Create a distribution via the API, without kernel options

Scenario: Create a distribution via the API, with kernel options

Scenario: Update a distribution via the API

Scenario: Create a profile via the UI

Scenario: Upload a profile via the UI

Scenario: Add an unprovisioned range to the created profile

Scenario: Add a variable to the uploaded profile

Scenario: Add a kernel option to the created profile

Scenario: Add a kernel option to the uploaded profile

Scenario: Check default snippets

Scenario: Create a snippet

Scenario: Delete a snippet

Scenario: Test for PXE environment files

Scenario: Trigger the creation of a cobbler system record

Scenario: Create a cobbler system record via API

Scenario: Cleanup: delete test profiles and distributions using API

Scenario: Check for errors in Cobbler monitoring

Scenario: Logout from the Cobbler API