-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove references to Pulpcore module stream for Pulpcore 3.39 #2597
Remove references to Pulpcore module stream for Pulpcore 3.39 #2597
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now dnf-module
and dnf-modules
are the same. Do we want to drop dnf-modules
altogether now?
I agree with this. |
1b0e7c5
to
bfdf6d8
Compare
I've added a note to disable the |
bfdf6d8
to
8543017
Compare
I've removed references to |
8543017
to
7fecc7e
Compare
The linting error appears to be an issue connecting to an external URL. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to also add this as an upgrade warning in the release notes? So here:
[id="katello-upgrade-warnings"] | |
== Upgrade Warnings | |
There are no upgrade warnings with Katello {KatelloVersion}. |
guides/doc-Upgrading_Project/topics/proc_upgrading-smartproxy-server.adoc
Show resolved
Hide resolved
guides/doc-Upgrading_Project/topics/proc_upgrading-a-connected-project-server.adoc
Show resolved
Hide resolved
I was going to stick it in when I do my whole Katello 4.11 release notes update. I suppose I could put it in now. |
And now I wonder if we should also recommend removing the python39 module. |
7fecc7e
to
211d8b5
Compare
@ekohl missed your earlier comments, I'll get to that. |
I added it here: https://github.com/theforeman/foreman-documentation/pull/2602/files |
211d8b5
to
a0f9fd0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Ian, LGTM. By now, I think we'll have to cherry-pick to 3.9. Please tick this box in your PR description.
Handing over to Ewoud for final ACK.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This part is actually fixing an existing bug:
diff -Nrwu old/Installing_Proxy/index-satellite.html preview/nightly/Installing_Proxy/index-satellite.html
--- old/Installing_Proxy/index-satellite.html 2023-12-05 23:12:22.000000000 +0000
+++ preview/nightly/Installing_Proxy/index-satellite.html 2023-12-05 23:12:28.000000000 +0000
@@ -3497,7 +3497,7 @@
<p>Enable the DNF modules:</p>
<div class="listingblock">
<div class="content">
-<pre class="nowrap"># dnf module enable satellite:el8</pre>
+<pre class="nowrap"># dnf module enable satellite-capsule:el8</pre>
</div>
</div>
</li>
@Lennonka would you mind having a look about fixing that for downstream stable branches?
We absolutely should not, at least not as long as other tools (like ansible-runner) are using it. |
@ekohl Downstream branches are copied from upstream. It must be, therefore, fixed in upstream and then it will be synced to downstream once merged. It can theoretically be done by correct cherry-picks to stable branches here in upstream, but I'm not sure all changes in this PR are desirable in older releases. |
3.9 was branched since, so a CP is needed ;) |
(cherry picked from commit c6b2be6)
@mjivraja @AkshayGadhaveRH Would you mind taking a look at this? I'm slammed :( and you might have a related bug for this in your team. |
FYI ran into this with testing upgrading from Katello 4.10 to 4.11 today, was getting tons of dnf/rpm errors until I figured it out. THIS SHOULD BE IN THE RELEASE NOTES to disable the pulpcore module before upgrading, my eye just got lucky and noticed it in the nightly docs, but it will trip lots of people up who are upgrading. |
@nixfu the note will be there once they're merged https://github.com/theforeman/foreman-documentation/pull/2632/files#diff-a3acd643a9303d35f8f0d8c49bd0099a29f8576e1fa1648475da1258c8fad7deR44 It'll be in before official GA. |
…eman#2597) (cherry picked from commit c6b2be6)
(cherry picked from commit c6b2be6)
No CP should be needed, this is for Foreman 3.9
Pulpcore 3.39 is almost definitely losing its module stream, so it will no longer be needed in the docs.
Don't merge until after theforeman/puppet-pulpcore#315 get in.
Please cherry-pick my commits into: