-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DRAFT: openSUSE Leap 16.0 (Alpha) #9491
base: master
Are you sure you want to change the base?
Conversation
👋 Hello! Thanks for contributing to our project. 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! |
Suggested tests to cover this Pull Request
|
60e4b94
to
29dce47
Compare
@@ -0,0 +1 @@ | |||
insert into rhnPackageKey (id, key_id, key_type_id, provider_id) (select sequence_nextval('rhn_pkey_id_seq'), 'fec28eaf09d9ea69', lookup_package_key_type('gpg'), lookup_package_provider('SUSE LLC') from dual where not exists (select 1 from rhnPackageKey where key_id = 'fec28eaf09d9ea69')); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note, this is probably going to be needed to support SLE Micro 6.1, so if we add support before merging this PR, this needs to be done on master
, and this will need to be removed from this PR.
@@ -1512,6 +1512,26 @@ | |||
"PKGLIST": PKGLIST15_SALT + PKGLIST15_X86_ARM, | |||
"DEST": DOCUMENT_ROOT + "/pub/repositories/opensuse/15/6/bootstrap/", | |||
}, | |||
"openSUSE-Leap-16.0-x86_64-uyuni": { | |||
"BASECHANNEL": "opensuse_leap16_0-x86_64", | |||
"PKGLIST": PKGLISTMICRO_BUNDLE_ONLY, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am tempted to create a group called PKGLIST_BUNDLE_ONLY
... any new OS will only support bundle, regardless of being Micro
or not... right?
Co-authored-by: Marina Latini <[email protected]>
29dce47
to
8629c94
Compare
gpgkey_url = file:///usr/lib/rpm/gnupg/keys/gpg-pubkey-29b700a4-62b07e22.asc | ||
gpgkey_id = 29B700A4 | ||
gpgkey_fingerprint = AD48 5664 E901 B867 051A B15F 35A2 F86E 29B7 00A4 | ||
repo_url = https://cdn.opensuse.org/distribution/leap/16.0/repo/oss/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this repo was available at the instance as both download.opensuse.org
and cdn.opensuse.org
, it seems cdn.opensuse.org
is the future: https://news.opensuse.org/2023/07/31/try-out-cdn-with-opensuse-repos/
This change is already part of openSUSE Leap Micro 6.0, so expect it to be part of openSUSE Leap 16.0
gpgkey_url = %(_uyuni_gpgkey_url)s | ||
gpgkey_id = %(_uyuni_gpgkey_id)s | ||
gpgkey_fingerprint = %(_uyuni_gpgkey_fingerprint)s | ||
repo_url = https://cdn.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable:/SLMicro6-Uyuni-Client-Tools/SL-Micro6/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Work for now, but we need to decide if we want SLMicro6 or other client tools. Should be related to what we want to do for SUSE Linux 16 as well.
# This is expected. openSUSE Leap 16.0 client tools are valid for all openSUSE Leap 16.X releases | ||
[opensuse_leap16_0-uyuni-client] | ||
name = Uyuni Client Tools for %(base_channel_name)s | ||
archs = x86_64, aarch64, s390x, ppc6le |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, for now they ISOs for all of them: https://get.opensuse.org/leap/16.0/
gpgkey_url = %(_uyuni_gpgkey_url)s | ||
gpgkey_id = %(_uyuni_gpgkey_id)s | ||
gpgkey_fingerprint = %(_uyuni_gpgkey_fingerprint)s | ||
repo_url = https://cdn.opensuse.org/repositories/systemsmanagement:/Uyuni:/Master:/SLMicro6-Uyuni-Client-Tools/SL-Micro6/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as before
What does this PR change?
WIP: openSUSE Leap 16.0 (Alpha)
To be continued tomorrow. As of today, this is the state:
Because of the /etc/os-release content, our bootstrap salt states fail to correctly detect Leap 16.0 (in fact because the salt grains doesn't show this as openSUSE):
So I faked the fix Lubos will do for os-release:
GUI diff
No difference. Just a new OS
Documentation
Documentation issue was created: DRAFT: Document openSUSE Leap 16.0 uyuni-docs#3468
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: Being this a hack week project and Leap 16.0 still an Alpha, I will not add tests for now.
DONE
Links
https://hackweek.opensuse.org/24/projects/testing-gnu-slash-linux-distributions-on-uyuni
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:
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:
Before you merge
Check How to branch and merge properly!