I have just replied to tickets, and even opened a new one internally to get this fixed. This is clearly an unintentional error. The version shouldn't have changed, and no packages should ever disappear from CentOS Stream.Here's my quick analysis (and a workaround) I posted to RHEL-25802:I realised why the original mariadb version "disappeared".
RHEL 9 / CentOS Stream 9 don't have default module streams. Modules are additional alternatives. By marking this one default, it has masked the original mariadb package, and because the original package isn't a module, "dnf module list" won't show it.
I believe "dnf module disable mariadb:10.11" should fix it on that system (I'm typing that command out of memory, haven't had time to test, someone can verify.)
This change definitely wasn't intentional, hopefully we can get it fixed quickly.
On Tue, 20 Feb 2024 at 09:20, Alfredo Moralejo Alonso <amoralej@redhat.com> wrote:_______________________________________________On Tue, Feb 20, 2024 at 7:28 AM Fabian Arrotin <arrfab@centos.org> wrote:On 20/02/2024 03:01, Michel Lind wrote:
> Hi,
>
> On Wed, Feb 14, 2024 at 06:22:47PM +0100, Alfredo Moralejo Alonso wrote:
>> Hi,
>>
>> After the last C9S compose I'm getting the module mariadb:10.11 enabled by
>> default, which is breaking OpenStack deployment which was based on 10.5.
>>
>> # dnf module list
>> Last metadata expiration check: 0:05:11 ago on Wed Feb 14 17:15:59 2024.
>> CentOS Stream 9 - AppStream
>> Name Stream
>> Profiles
>> Summary
>>
>> mariadb 10.11 [d]
>> client, galera, server [d]
>> MariaDB Module
>>
>>
>> # dnf list mariadb
>> Last metadata expiration check: 0:05:34 ago on Wed Feb 14 17:15:59 2024.
>> Available Packages
>> mariadb.x86_64 3:10.11.6-1.module_el9+853+7b957b9b
>> appstream
>>
>> Is this a bug? I guess this goes against stability rules in RHEL?
>>
> Not a RH engineer myself, but from the documentation, the stability rules are more relaxed for appstream:
>
> https://access.redhat.com/support/policy/updates/rhel-app-streams-life-cycle
>
> """
> Application Streams will be available during the Red Hat Enterprise Linux lifecycle. Multiple versions of user space components are delivered and updated more frequently than the core operating system packages. This provides greater flexibility to customize Red Hat Enterprise Linux without impacting the underlying stability of the platform or specific deployments.
> """
>
> Best regards,
>
that's true but that exact same page also mentions (under "RHEL 9 Full
Life Application Streams Release Life Cycle") that mariadb 10.5 is there
(and the only mariadb version btw) with "retirement date" set to "May
2032" :-)
I guess new version should an "opt-in" module soon but shouldn't be the
default one ? (just a guess on my side though)
Alfredo : worth creating a ticket to ask for clarification ?
I already created one:As you said, mariadb 10.5 is in the list of applications supported during the major life cycle, so, imo it should be the default.Alfredo--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
https://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list
CentOS-devel@centos.org
https://lists.centos.org/mailman/listinfo/centos-devel
--_______________________________________________Principal Software Engineer
Adam Samalik
---------------------------
Red Hat
CentOS-devel mailing list
CentOS-devel@centos.org
https://lists.centos.org/mailman/listinfo/centos-devel