View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000562Rocky-Linux-8microcode_ctlpublic2022-10-19 10:292022-10-20 12:25
ReporterINVADE Third Line Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionopen 
Summary0000562: Messages in posttrans scriptlet do not use the same level
DescriptionThe microcode_ctl posttrans scriptlet script contains the following:

    if [ -n "${skipped}" ]; then
        skip_msg="After installation of a new version of microcode_ctl package,
initramfs hasn't been re-generated for all the installed kernel packages.
The following kernel packages have been skipped:${skipped}.
Please re-generate initramfs manually for these kernel packages with the
\"dracut -f --kver KERNEL_VERSION\" command in order to get the latest
Intel CPU microcode included into early initramfs image for it, if needed."

        if [ -e /usr/bin/logger ]; then
            echo "${skip_msg}" |
                /usr/bin/logger -p syslog.notice -t microcode_ctl
        fi

        if [ -e /dev/kmsg ]; then
            echo "${skip_msg}" > /dev/kmsg
        fi
    fi

The "logger" message is set to "notice" but the "/dev/kmsg" message uses the default kernel log priority, which is "warning".

I believe the "echo" line should read:

            echo "<5>${skip_msg}" > /dev/kmsg

to ensure the messages are logged at the same level.
Steps To ReproduceUpgrade the microcode_ctl package.
TagsNo tags attached.

Activities

Skip Grube

Skip Grube

2022-10-19 15:41

manager   ~0000727

Hi, thanks for this report! This definitely sounds like it should be filed against the upstream RHEL package, on https://bugzilla.redhat.com . I believe the same behavior is in RHEL 8's microcode_ctl , though I haven't checked RHEL 9. Rocky aims to be a 100% compatible clone of RHEL, so it will be changed here as soon as it can be modified upstream.

Thanks!

-Skip
INVADE Third Line

INVADE Third Line

2022-10-19 15:47

reporter   ~0000730

Thanks for the response.

Is that something I should do, or will you do it now that I have raised it here?

Apologies, I couldn't find any instructions on when to raise a bug here or upstream.
Skip Grube

Skip Grube

2022-10-19 16:04

manager   ~0000731

I'd recommend you do it, especially if it's something you care about :-) . I know the RHEL and downstream communities such as ours would appreciate it.

Generally speaking, Rocky Linux aims to match versions and behavior with RHEL 100%. "Bug for bug compatible" is a common tagline we like to use sometimes. Software packages available in RHEL should be the exact same in Rocky, and we should also have the exact same bugs.

For bug reports, the rule of thumb is simple: If the bug/behavior shows up in Rocky and in RHEL, it should go to the RHEL bugzilla. If the bug is Rocky-specific, and not present in RHEL, then we at the Rocky project will want to fix it immediately! So we can continue to match the upstream behavior.

Hope that makes sense. It's a good question - thanks for asking!
INVADE Third Line

INVADE Third Line

2022-10-19 16:14

reporter   ~0000732

Upstream bug raised:

https://bugzilla.redhat.com/show_bug.cgi?id=2136224
Skip Grube

Skip Grube

2022-10-20 12:23

manager   ~0000736

Thank you! We all appreciate it. I'm going to go ahead and close this ticket on our side.
Skip Grube

Skip Grube

2022-10-20 12:25

manager   ~0000737

Report pushed upstream

Issue History

Date Modified Username Field Change
2022-10-19 10:29 INVADE Third Line New Issue
2022-10-19 15:41 Skip Grube Note Added: 0000727
2022-10-19 15:47 INVADE Third Line Note Added: 0000730
2022-10-19 16:04 Skip Grube Note Added: 0000731
2022-10-19 16:14 INVADE Third Line Note Added: 0000732
2022-10-20 12:23 Skip Grube Note Added: 0000736
2022-10-20 12:25 Skip Grube Note Added: 0000737
2022-10-20 12:25 Skip Grube Status new => closed