Closed nasark closed 7 months ago
@mikemoroney @aileenjackson Please review
@nasark @mikemoroney what is an "internal FQDN"? I know there was an issue with AWS but there is no AWS caveat here it is a blanket statement.
If we can't use localhost
I wonder if we'd be better off generically stating that the user has to use an existing fqdn hostname or create a hostname entry in /etc/hosts
that resolves properly? That would at least work on all platforms not just amazon.
Backported to quinteros
in commit ce4af9b84dbe419b205cff535d15ebf275ddfd1f.
commit ce4af9b84dbe419b205cff535d15ebf275ddfd1f
Author: Jason Frey <fryguy9@gmail.com>
Date: Tue Jan 30 13:35:29 2024 -0500
Merge pull request #1780 from nasark/hostname_guidelines
Specify internal FQDN for messaging hostname
(cherry picked from commit e24d0f040b45d115d8afbcb1a9436637d690b80b)
@agrare Oh I interpreted internal FQDN as being specifically for Amazon...I didn't realize this was a blanket statement location.
QA/Docs team suggested that it is important to specify the internal FQDN, since the external FQDN will cause issues
@miq-bot assign @Fryguy @miq-bot add_label enhancement, quinteros/yes?