https://bigfix-ideas.hcltechsw.com/ideas/BFPTCH-I-187
Does anyone know if this will get any traction?
Over 4 years old.
We are starting to crash and burn on streams content from Red Hat and Bigfix does not handle it well at all.
https://bigfix-ideas.hcltechsw.com/ideas/BFPTCH-I-187
Does anyone know if this will get any traction?
Over 4 years old.
We are starting to crash and burn on streams content from Red Hat and Bigfix does not handle it well at all.
A follow-up question here: even if the Streams configuration prevents their installation to maintain a particular major or minor version, the patches in question are technically applicable/needed, correct? (i.e. the packages in question are in fact down-leveled)
The challenge here makes sense…I’m just trying to think through how best to represent the state of the endpoint (as it relates to vulnerabilities for instance) while at the same time better supporting the update mechanisms to support this RH feature.
If the package is outdated and there is a new fixlet/package to install, it is still needed and should be relevant.
Can you address why there is an idea in the idea DB that is over 4y old that would have addressed this?
I have to say, we run into RHEL 8 issues with Bigfix over and over and it goes without saying that BF customers are not impressed.
When can we expect as HCL customers, better support for Red Hat 8+ in general?
RedHat 8 Module Streams patching is supported in BigFix since long time…
Did you check this article in the documentation?
You have to follow the configuration steps included in the documentation in order to enable the Module Streams, as explained in the page I liked.
If this solution does not meet your requirements, I’m happy to have a conversation to better understand the Use Case you have.
We do push the prerequisite fixlet. It’s still an issue where the server’s stream is NOT enabled but the fixlet is relevant so it fails to install.