Skip to content

Conversation

@maximenoel8
Copy link
Contributor

What does this PR change?

Bump everything sles15sp4 to sles15sp7. Including:

  • build host
  • terminals
  • pxeboot
  • docker => changed the way to select the environment to be more dynamic (I enter "([^"]*)" relative to profiles as "([^"]*))
  • sync and channel testing sles15sp7
  • I had issue with the sles15sp4 installer module, it doesn't exist in sles15sp7 so I use container module for the similar test
  • Also proxy extension is in slmicro6.1 product or sles15sp7 product now and not a standalone product
  • changed the autoyast to deploy sles15sp7 with salt bundle
  • changed the tftpboot package

Fixes including in this PR:

  • cleaning terminals for retail mass import -> switch to API
  • exporting rake parallel result in the correct result folder
  • cleaning channel in content cycle, use the option a (I delete these channels( with children)? with spacewalk-remove-channel)
  • fix a drop down selection (I select "([^"]*)" from drop-down in table line with "([^"]*) )
  • and more !

What left to do:

  • find ptf compatible with sles15sp7 for lotus project
  • check new ptf testing from Wiktor (credentials were missing in personal pipeline)
  • pxe boot bootstrap using script is still failing
  • check for other side effect

GUI diff

No difference.

  • DONE

Documentation

  • No documentation needed: only internal and user invisible changes

  • DONE

Test coverage

ℹ️ If a major new functionality is added, it is strongly recommended that tests for the new functionality are added to the Cucumber test suite

  • No tests: already covered

  • DONE

Links

Issue(s):

Port(s): Port will be done but in one by one case
Depends on: SUSE/susemanager-ci#1807

  • DONE

Changelogs

Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository

If you don't need a changelog check, please mark this checkbox:

  • No changelog needed

If you uncheck the checkbox after the PR is created, you will need to re-run changelog_test (see below)

Re-run a test

If you need to re-run a test, please mark the related checkbox, it will be unchecked automatically once it has re-run:

  • Re-run test "changelog_test"
  • Re-run test "backend_unittests_pgsql"
  • Re-run test "java_lint_checkstyle"
  • Re-run test "java_pgsql_tests"
  • Re-run test "ruby_rubocop"
  • Re-run test "schema_migration_test_pgsql"
  • Re-run test "susemanager_unittests"
  • Re-run test "frontend_checks"
  • Re-run test "spacecmd_unittests"

Before you merge

Check How to branch and merge properly!

@maximenoel8 maximenoel8 requested a review from a team as a code owner November 27, 2025 20:16
@github-actions
Copy link
Contributor

👋 Hello! Thanks for contributing to our project.
Acceptance tests will take some time (aprox. 1h), please be patient ☕

You can see the progress at the end of this page and at https://github.com/uyuni-project/uyuni/pull/11258/checks
Once tests finish, if they fail, you can check 👀 the cucumber report. See the link at the output of the action.
You can also check the artifacts section, which contains the logs at https://github.com/uyuni-project/uyuni/pull/11258/checks.

If you are unsure the failing tests are related to your code, you can check the "reference jobs". These are jobs that run on a scheduled time with code from master. If they fail for the same reason as your build, it means the tests or the infrastructure are broken. If they do not fail, but yours do, it means it is related to your code.

Reference tests:

KNOWN ISSUES

Sometimes the build can fail when pulling new jar files from download.opensuse.org . This is a known limitation. Given this happens rarely, when it does, all you need to do is rerun the test. Sorry for the inconvenience.

For more tips on troubleshooting, see the troubleshooting guide.

Happy hacking!
⚠️ You should not merge if acceptance tests fail to pass. ⚠️

@maximenoel8 maximenoel8 self-assigned this Nov 27, 2025
@maximenoel8 maximenoel8 changed the title Bump all minions from sles15sp4 to sles15sp7 WP: Bump all minions from sles15sp4 to sles15sp7 Nov 27, 2025
@maximenoel8 maximenoel8 marked this pull request as draft November 27, 2025 20:19
@maximenoel8 maximenoel8 changed the title WP: Bump all minions from sles15sp4 to sles15sp7 WP-CI: Uyuni/Head: Bump all minions from sles15sp4 to sles15sp7 Nov 27, 2025
@maximenoel8 maximenoel8 force-pushed the ci_bump_all_sles15sp7 branch from 17e7255 to cf2e963 Compare November 27, 2025 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant