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

Provision dialog for ec2 with public images fails - high worker memory utilization #446

Closed
dmetzger57 opened this issue Jun 23, 2020 · 5 comments
Assignees

Comments

@dmetzger57
Copy link

Original BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1662972

Steps to Reproduce:

  1. Add ec2 provider with region us-east-1 and public images enabled
  2. Wait for full refresh
  3. Go to Compute -> Cloud -> Instances
  4. Select provision an instance
  5. Select an image and go to next step

Actual results:
When I select an image and then click on continue I get Error requesting data from server

@dmetzger57 dmetzger57 added the bug label Jun 23, 2020
@Fryguy
Copy link
Member

Fryguy commented Jun 25, 2020

@NickLaMuro Seems you were working on this in the BZ...is it still in your court or should it be moved to someone else or marked help wanted?

@NickLaMuro
Copy link
Member

@Fryguy A year and a half ago, I had provided some fixes and approaches on how to improve this, but it was deemed low priority so they never got priority for review or pressured (from management) to be pursued further.

I have no problem taking this ticket on, but progress on addressing what I already have:

has been slow or non-existent. Comments like this one:

ManageIQ/manageiq-schema#322 (comment)

Remained unanswered, which gave me the impression that this was not a heavily desired improvement, and so I haven't pursued it further. I think we the remaining PRs, there is a big discussion to be had about if the approach of adding a caching column is the right approach and one we want to move forward with, or if it will potentially cause bugs itself and isn't worth the risk.

Also worth noting, we probably have had 3 releases since I originally opened these proposals, so I probably have to re-evaluate my performance improvements as well with the updated codebase.

@Fryguy
Copy link
Member

Fryguy commented Jun 25, 2020

No need to prioritize now. This just came in and I didn't know that the status was. Thanks for the updates

@miq-bot
Copy link
Member

miq-bot commented Mar 6, 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 miq-bot added the stale label Mar 6, 2023
@miq-bot miq-bot closed this as completed Jun 12, 2023
@miq-bot
Copy link
Member

miq-bot commented Jun 12, 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.

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

4 participants