Add a note about IP addresses after migration #3919
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The PR preview for be7003c is available at theforeman-foreman-documentation-preview-pr-3919.surge.sh The following output files are affected by this PR: |
|
When I read this I was a bit confused at first. You mentioned DNS and that made me think of a different strategy (which is also valid): you can lower the DNS TTL in advance to a very low value (like 60, so 1 minute). Then the cache isn't really an issue. Your approach is also valid, but the phrasing could be clearer. I'd emphasize that in order to avoid DNS caches users should transition the IP to the new server. |
|
@ekohl thanks! I reworded the sentence a bit and dropped the note. I have just used a generic |
AkshayGadhaveRH
added
Needs tech review
ekohl
reviewed
Jun 23, 2025
guides/common/modules/proc_migrating-project-or-smartproxy-using-backup-restore.adoc
Outdated
Show resolved
Hide resolved
added 3 commits
June 24, 2025 12:30
After migrating from EL8 to EL9, the sync tasks fail with a network error. This is because DNS changes takes time. Adding a note about this and also a step to shut down the old system and reassign the IP to the new EL9 system. JIRA: https://issues.redhat.com/browse/SAT-28024
AkshayGadhaveRH
force-pushed
the
add_note_about_IP_3.12
branch
from
5472c7e to
be7003c
Compare
ekohl
approved these changes
Jul 3, 2025
ekohl
added
tech review done
aneta-petrova
approved these changes
Jul 3, 2025
aneta-petrova
added
style review done
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After migrating from EL8 to EL9, the sync tasks fail with a network error. This is because DNS changes takes time.
Adding a note about this and also a step to shut down the old system and reassign the IP to the new EL9 system.
JIRA:
https://issues.redhat.com/browse/SAT-28024
What changes are you introducing?
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
Checklists
Please cherry-pick my commits into: