Specify internal FQDN for messaging hostname

ManageIQ / manageiq-documentation

Documentation for the ManageIQ Management Platform

https://www.manageiq.org/docs/

Other

38 stars 113 forks source link

Specify internal FQDN for messaging hostname #1780

Closed nasark closed 7 months ago

nasark commented 7 months ago

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?

nasark commented 7 months ago

@mikemoroney @aileenjackson Please review

miq-bot commented 7 months ago

Checked commit https://github.com/nasark/manageiq-documentation/commit/b1f485950f3d7f1dbf7474e02b64159797d71e0c with ruby 2.7.8, rubocop 1.56.3, haml-lint 0.51.0, and yamllint 0 files checked, 0 offenses detected Everything looks fine. :star:

agrare commented 7 months ago

@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.

Fryguy commented 7 months ago

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)

Fryguy commented 7 months ago

@agrare Oh I interpreted internal FQDN as being specifically for Amazon...I didn't realize this was a blanket statement location.