Skip to content
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

Need to review and update HA Guide to align with current build process #1599

Open
dehawkins512 opened this issue Sep 9, 2021 · 8 comments
Open
Assignees

Comments

@dehawkins512
Copy link
Contributor

Comments from @Fryguy
"This particular document (HA Guide) seems to have been missed when we converted all of the Red Hat CloudForms documents wholesale into the Infrastructure Management documents. The way appliances work from the IM distribution do not work like Red Hat CloudForms appliances, and, as such, the documentation doesn't apply."
This issue is opened to get the HA Guide corrected.

@dehawkins512
Copy link
Contributor Author

@dehawkins512
Copy link
Contributor Author

ref. https://www.manageiq.org/docs/reference/latest/high_availability_guide/index.html#updating-a-highly-available-manageiq-environment

This topic needs to be reviewed for accuracy. Note: the "Registering and Updating ManageIQ" in General Configuration no longer exists.
Prerequisites.

Ensure each appliance is registered to Red Hat Subscription Manager and subscribed to the update channels required by ManageIQ in order to access updates.

To verify if your appliance is registered and subscribed to the correct update channels, run:

yum repolist

Appliances must be subscribed to the following channels:
{product-repo_cfme}
{product-repo_ansible}
{product-repo_extras}
{product-repo_optional}
{product-repo_server}

If any appliance shows it is not registered or is missing a subscription to any of these channels, see Registering and Updating ManageIQ in General Configuration to register and subscribe the appliance.

@miq-bot
Copy link
Member

miq-bot commented Feb 27, 2023

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

@miq-bot
Copy link
Member

miq-bot commented May 29, 2023

This issue has been automatically closed because it has not been updated for at least 3 months.

Feel free to reopen this issue if this issue is still valid.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

@miq-bot miq-bot closed this as completed May 29, 2023
@bdunne bdunne reopened this May 30, 2023
@bdunne bdunne removed the stale label May 30, 2023
@miq-bot miq-bot added the stale label Sep 4, 2023
@miq-bot
Copy link
Member

miq-bot commented Sep 4, 2023

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

@miq-bot
Copy link
Member

miq-bot commented Dec 11, 2023

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

2 similar comments
@miq-bot
Copy link
Member

miq-bot commented Mar 18, 2024

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

@miq-bot
Copy link
Member

miq-bot commented Jun 24, 2024

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants