Kmod C74 Broken: Howto Report It

Home » CentOS » Kmod C74 Broken: Howto Report It
CentOS 4 Comments

hi all,

latest kmod update 20-15.el7_4.6 is broken on our systems, while previous 20-15.el7_4.4 was working fine (and downgrading fixes the issue).

the issue is with modules from mellanox kmod rpms that are symlinked in the weak-updates dir. the config files in /etc/depmod.d look ok (and do work with previous version): dist.conf has weak-updates after built-in, and mellanox kmod rpms ship a config that overrides it for all modules.

anyhow, before i try to get this upstream, how do i report this with CentOS team (to make sure the CentOS kmod rpm was correctly build).

(i have already asked here before how to properly report it, but can’t find my previous mail ;)

stijn

4 thoughts on - Kmod C74 Broken: Howto Report It

  • hi akemi,

    i also forgot about this thread. we already tested the latest kmod last week and it indeed fixes the issue.

    still no clue how to report issues to CentOS team to doublecheck packaging mishaps…

    stijn

  • If the package does not have a .CentOS. in the name (ie, firefox-52.6.0-1.el7.CentOS.x86_64.rpm) then we did not modify it, so we did not change the package in any way. An example of a normal package would be: liberation-sans-fonts-1.07.2-15.el7.noarch.rpm (no
    .el7.CentOS, just .el7, etc.)

    You can report CentOS bugs (something we have broken and is not upstream) at https://bugs.CentOS.org/

    If it is an upstream issue, we can’t fix it .. if we created the issue, we will try to fix it.

    This is one of many areas where we need community help. Anyone who wants to can get a bugs.CentOS.org account and can look at all open bugs. You can comment on any bug. What we need is the community to see if they can duplicate the bug in question .. and for people who can test the same bug in RHEL, please do so. If the bug also appears in RHEL, create a bug at bugzilla.redhat.com and reference the bugs.CentOS.org entry there.

    If the bug is present in CentOS Linux and not in RHEL, then add that to a comment in the bugs.CentOS.org entry. This kind of thing helps us greatly as we have a limited number of people who work on the main CentOS Linux distribution.

    So, people who ask .. what can I, as a community member, do to help the CentOS Project. This is one major way .. get a bugs.CentOS.org account and help us figure out if the issue is reproducible, and if it was introduced by the CentOS build or exists upstream.

    Other ways the community can help .. sign up for forums.CentOS.org and read issues there and respond. Answer questions on this mailing list and other CentOS.org mailing lists. You could also join a SIG
    (https://wiki.CentOS.org/SpecialInterestGroup).

    Thanks, Johnny Hughes