Fixes #25978 - Debian Errata support#7961
Conversation
|
Do not merge! This patch has not been tested yet. Can an existing organization member please verify this patch? |
|
There were the following issues with the commit message:
If you don't have a ticket number, please create an issue in Redmine. More guidelines are available in Coding Standards or on the Foreman wiki. This message was auto-generated by Foreman's prprocessor |
theforeman-bot
added
Waiting on contributor
Needs testing
Not yet reviewed
and removed
Waiting on contributor
labels
|
There were the following issues with the commit message:
If you don't have a ticket number, please create an issue in Redmine. More guidelines are available in Coding Standards or on the Foreman wiki. This message was auto-generated by Foreman's prprocessor |
|
[test katello] |
|
There were the following issues with the commit message:
If you don't have a ticket number, please create an issue in Redmine. More guidelines are available in Coding Standards or on the Foreman wiki. This message was auto-generated by Foreman's prprocessor |
|
There were the following issues with the commit message:
If you don't have a ticket number, please create an issue in Redmine. More guidelines are available in Coding Standards or on the Foreman wiki. This message was auto-generated by Foreman's prprocessor |
|
Can one of the admins verify this patch? |
|
There were the following issues with the commit message:
If you don't have a ticket number, please create an issue in Redmine. More guidelines are available in Coding Standards or on the Foreman wiki. This message was auto-generated by Foreman's prprocessor |
|
ok to test |
|
@m-bucher looks like this has some merge conflicts now. I've also invited you to the katello org so the bot will auto test your prs |
|
@m-bucher could you also provide steps on how to test this end-to-end ? |
|
@m-bucher how goes this PR? Anything we can do to move it along? |
|
@jturel thanks for the offer. For testing you need to configure a You may use our running instance at For example: |
|
Thanks @m-bucher, while the PR gets rebased is there anything we can do? |
m-bucher
force-pushed
the
feature/debian_errata
branch
from
594b90a to
418dd18
Compare
|
There were the following issues with the commit message:
If you don't have a ticket number, please create an issue in Redmine. More guidelines are available in Coding Standards or on the Foreman wiki. This message was auto-generated by Foreman's prprocessor |
|
hi , any update for this PR? |
|
@itcloudgr geia! I believe there might be some other work going on that is related to this over at #9886 |
|
Are there any news about this? |
|
Hey @martux69 - I'll try figure out why the other pr was closed. |
|
Hi @melcorr , |
|
Fingers crossed that someone would promote this project |
|
Hey @martux69 @shay1197 |
|
I can give a brief update: We don't currently have the bandwidth for a major push on getting the Debain Errata feature in. It is currently probably around third place on our internal priority list for major long term projects we really want to work on. The top priority (moving our downstream to EL8) is under heavy development and making progress. After that we will need to do a round of upgrading to latest Foreman/Katello releases, and then we may find the bandwidth for a major push on Debian Errata. Optimistically this could happen somewhere towards the end of the first quarter of the new year. Of course high priority short term issues can and often do insert themselves in this road map, so there are no promises. Personally, I will be pushing internally to put this on our agenda in the first half of 2023. |
|
Thank you on the update :) |
|
@quba42 would love to know if there a chance of the feature landing in Katello. You previous update sounded optimistic. |
|
Update: We have not yet started our push on this, but it is moving up the internal priority list with some of the things ahead of it now completed. A push in the first quarter of 2023 obviously did not happen. A push within the next two Months is possible but not very likely. Early in the second half of 2023 is realistic. As always this is not a promise. 😉 |
|
Hi, |
Co-Authored-by: Markus Bucher <bucher@atix.de> Co-Authored-by: Bernhard Suttner <suttner@atix.de> Co-Authored-by: Manisha Singhal <singhal@atix.de>
|
Could someone post a status update for this issue? Perhaps is a final release date at the horizon? |
|
@martux69 unfortunately, I do not think it is on the horizon, yet. There are still some ToDos on the way. There is a discussion to be had regarding the current workflow, with a separate parser and server, where Katello syncs the Errata from. The question being should we rather integrate the Parser into Katello or a local service on the Foreman/Katello server. In the meantime I will have a look, if there are parts here that can already be merged separately, thus reducing the size of this PR. |
|
Hi again :) |
|
Does anyone know when this is likely to be merged to katello? |
|
Could someone post a status please :? |
|
Thank you for working on this, how are things going? |
|
A lot of the key people familiar with this work will be meeting in person at CfgMgmtCamp in Ghent soon. @m-bucher and myself will be holding a talk that will cover the state of this work. There will also be space (workshop day) for a technical discussion between us and key Katello maintainers on what it would take to drive this work towards completion. Once we have that plan there is still no guarantee it will be placed on our various road maps and have the necessary resources allocated to it, but I promise to post a next update after CfgMgmtCamp has concluded. |
|
@quba42 Thank you for the update. |
|
@quba42 The CfgMgmtCamp is over :-) It could be grateful if you can inform us about the planned road map for this feature. |
|
Unfortunately I was out of commission these past two weeks, and was therefore unable to attend CfgMgmtCamp. However, my colleague @m-bucher tells me there were discussions on what is required of a Debian errata feature that could be merged to upstream Katello. Updating this very stale PR will be substantial work, but also we now believe there need to be some changes to the approach/architecture, with parts of the implementation currently in an external component (https://github.com/ATIX-AG/errata_parser) needing to move into Katello (or possibly Pulp). Given other priorities I have grown more pessimistic about the possibility of a major push on this within the foreseeable future. I will keep looking for opportunities to free up the needed time, but making any kind of promises of a firm road map at this point would be misleading. Apologies I don't have better news from our end. |
As @melcorr posted on the other PR, I think that PR is unlikely to be revived. Even though I have sought to constrain expectations for any kind of rapid progress in the short term, I do believe our effort, currently represented by this PR is by far the most likely to eventually make it into the project. We will continue to transparently communicate any progress (or lack thereof), on our effort. Anything is possible in open source, but given everything I know, I think it unlikely a successful effort by anyone else will materialize. |
|
Hi, |
There is nothing disrespectful about not understanding, I will try to explain:
This is the hard part and it is as much an organizational effort, as it is a technical problem. All of this needs to come together while there are a thousand competing demands on everyone's time. As an example: I think the need to prioritize Pulp 2 to 3 singularly delayed any serious effort on this PR by at least two years. If we had not worked on creating a pulp3_deb plugin (which no one else was willing to do), Katello would have been forced to drop the existing deb/APT content support, so that was not an option. Based on my experience with the work we already did on Errata, as well as other recent major Katello features, I estimate that it will take something like two developers doing very little else for 6 months (that is just on the ATIX side) to get this PR over the finish line, maybe more. If you are willing to supply that (or if you think you can do it in an afternoon) we would happily help you do so (at least if we consider it a serious good faith effort). If not, we will be the ones to decide if and when we can free up the time. In a nutshell, that is how it can happen for a PR like this to remain open for years. 😉 |
|
Hi, |
17 participants
Depends on #7418
Add support for Debian/Ubuntu errata using external service, which:
parses Debian Security Announcements (DSA) and Ubuntu Security Notices (USN): https://github.com/ATIX-AG/errata_parser
serves the resulting errata: https://github.com/ATIX-AG/errata_server