How to get a backport from upstream?
Hi,
I would like to know how to get a backport from upstream for a certain package. What do I have to do and where do I have to report such a request?
Example:
I am using ansible-2.4.0.0 from rhel-7-server-extras-rpms. This version contains some bugs which were fixed upstream in PR 32671.
Is this bufix going to be backported to the ansible package from the RHEL channel, too? If so, how long does it usually take to get these fixes? Or do I have to request the backport via support or bugzilla?
Kind regards,
Joerg
PS: I know that I could use the upstream version or run ansible from the github repository. But per policy I have to use packages from the repo channels, because only for these I could get support from Red Hat.
Responses
Guru
9710 points
Hi Jörg,
Question : "Is this bufix going to be backported to the ansible package from the RHEL channel, too?"
Answer : Depends ... on the importance of the related bugs - are they real show stoppers or not.
Question : "If so, how long does it usually take to get these fixes?"
Answer : Depends ... on the severity of the related bugs - do they provide security issues or not.
Question : "Or do I have to request the backport via support or bugzilla?"
Answer : You can ... you help to improve the system - but don't expect the fix to get backported.
Reasons : Red Hat Enterprise Linux is well respected for high availability, security and stability.
Everything is thoroughly tested before package updates get released ... and that takes its time.
Do you know if the new upstream packages don't bring along other new and even worse bugs ?
Right, you don't - if Red Hat would backport too fast, which (negative) impact would this have ?
Consequence : You'll have to wait and see, or use the upstream version when you really need to.
Exception : You are having a good friend who is working for Red Hat and wants to do you a favor.
The last sentence (the exception) was a little joke of course, hope you don't mind some humor. :)
Chances are that package updates might be released, because Red Hat is pushing Ansible hard.
Regards,
Christian
Guru
6222 points
Hi Jörg,
File a support case or open a bugzilla, and describe the issue you encounter. If the bugfix from upstream is the only possible fix, engineering will do a backport.
Regards,
Jan Gerrit
Guru
9710 points
Hi Jan Gerrit,
As I have tried to point out in my post, it depends on the severity of the problem.
I have opened such bug reports and not much happened in the current release. :)
Regards,
Christian
Guru
6222 points
A support case has more effect than a bugzilla report is my experience.
Guru
9710 points
That's reasonable and I really believe you, Jan Gerrit. What I still think is that it really depends on the severity of every single bug if a fix gets backported or not ... generally, the way to go is to report bugs using bugzilla, because otherwise customer support would be flooded with bug reports, which I think is not intended. Anyway, Jörg can open the support case and hopefully he achieves what he wants. :)
Regards,
Christian
Guru
6222 points
Hi Christian,
As my employer pays >1M$ I have less problems with opening suport cases instead of bug reports. We need fixes for our customers and cannot wait for a bug report to be accepted by the engineers team. If all Red Hat customers benefit from it, that is a plus. RFE I open if needed, so all Red Hat customers will surely benefit.
To me Red Hat is a vendor, not a charity fund. I request help, if I need it, for my employer pays for it.
It is a respectful vendor, so I respectfully ask them for help.
Regards,
Jan Gerrit
Guru
9710 points
Hi Jan Gerrit,
Your argumentation is absolutely correct and valid, that's the way it should be seen ! :)
Please don't get me wrong, but we all know that there are "customers and customers".
All I wanted to say is that Jörg shouldn't expect too much - nevertheless you are right.
Regards,
Christian
Expert
1223 points
Hi, And thanks a lot for all your answers.
Consequence : You'll have to wait and see, or use the upstream version when you really need to. Exception : You are having a good friend who is working for Red Hat and wants to do you a favor.
The last sentence (the exception) was a little joke of course, hope you don't mind some humor. :)
@Christian: There is nothing wrong with some humor around here. :-)
@Topic: I think I will decide from case to case what to do. At a first step I would look up if a bugzilla is already there.
So there is BZ1509360 and I will wait for the release to be published.
I think if I need changes fast to test new versions I have to use the upstream version instead. In this case we have to change our policy.
Regards, Joerg
Guru
9710 points
You're welcome Jörg,
I guess that you won't have to wait too long, because the status changed from VERIFIED to RELEASE_PENDING.
Cheers :)
Christian
Expert
1223 points
And I reveived just a mail that the status changed to close because errata exists. :-)
It's just twenty days between the release of 2.4.1 and the rebase. IMHO for an Enterprise Distribution this is very fast.
This is definitely quicker than usual, most likely due to the fact that at the moment Red Hat are so strongly focused on Ansible and pushing new features (especially Windows functionality parity) through to end users.
Particularly interesting is the comment in the changelog which suggests they have just rebased off Fedora rather than backporting:
2017-11-07 Pavel Cahyna <pcahyna@redhat.com> - 2.4.1.0-1
- Sync with Fedora version 2.4.1.0-2, brings Ansible 2.4.1.0.
Red Hat
Expert
1164 points
Hi Jörg,
Red Hat gives reports to bugs that are reported in support cases. Fixes need to be upstream before they are included in Red Hat releases, so pointing to an upstream fix should speed the process.
The severity of the bug does make a difference in prioritization. If the bug is affecting you, include information about how the bug is affecting you in the support case.
Regards,
Marc
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.