8 ms·
It goes further than that. If you file a bug on Red Hat's bugzilla with or without a support contract, you will quite often get a response if you put the effort
by carwyn 4y ago
It goes further than that. If you file a bug on Red Hat's bugzilla with or without a support contract, you will quite often get a response if you put the effort into producing a detailed report. No guarantee, sometimes just others with the same issue, but still pretty good. You will also find Red Hat employees on the mailing lists for the OSS projects they contribute or depend on who actively participate in conversations there.
If you have a support contract though and open a case, the level and quality of support is usually very high.
- jacobr1 4y agoIs this still true after the IBM acquisition?
- bonzini 4y agoThere's been absolutely no change for most employees after the acquisition.
- jacobr1 4y agoAwesome to hear!
- worthless-trash 4y agoCan confirm. No change in product security.
- djbusby 4y agoI've been involved with companies buying from IBM for over 20 years. Since the Lotus Notes days I've always been impressed by their support chasing down hairy issues. Like, their tier1 would escalate to T3 when mostly needed. Compare to Google where robots lock you out for days. Expensive but never had a client be mad about it.
- josephcsible 4y agoThis isn't my experience at all. I've personally had three paid support cases attached to Bugzilla issues. Two of them were for bugs that had one-line fixes that were already committed upstream, along with test cases, and that I just needed Red Hat to backport. They sat for about 6 months before I got any response other than the automated monthly "our engineers are working on the Bugzilla." The third was for a problem that existed upstream too. It was opened over 2 years ago and still isn't fixed.
- bonzini 4y agoBZ number for the third? Also what components?
- josephcsible 4y agoThe components for the first two were NSS (Network Security Services, not Name Service Switch) and GCC, and the third was Kerberos. I don't have the BZ number handy right now.
- bonzini 4y agoFor the first two it's probably that they were considered not bad enough for an asynchronous release. With CentOS Stream, you would have a better understanding of when the patch was committed and more certainty of whether it would be fixed in the next minor (6-months cadence) release. Feel free to write to me at pbonzini@redhat.com, I don't work on Kerberos myself but I know people in the team.
- iasay 4y agoSame experience with RHEL support. We just didn’t bother in the end. We fix our own bugs or work around them. CentOS/Rocky has better ROI is better when stuff doesn’t get fixed on something you are paying money for.