Unable to see public AWS AMIs


#1

I have enabled AWS public images (get_public_images: true) and have ensured that the user’s access and secret keys are correct. I have also confirmed that the user has admin permissions on AWS. Unfortunately, this does not appear to impact anything. I still have no view of the public AMIs within the ManageIQ interface.

If I’m not mistaken they should appear under Cloud->Instances->Lifecycle->Provision Instances. This presents what I suspect should be a table of all available images which should include the public images. The only thing I see, though, is “Provision Instances based on the selected image”, all of the table headers (Name, Operating System, etc), and the Continue and Cancel buttons. I don’t have any images to select from.

We don’t have an Azure account or any VMware servers to test with so I can’t say if this is an issue with the server or the provider.


#2

Yeah, same issue for me as well. I am using capablanca version


#3

@gmccullough can you review this question from @theillien and forward to a SME if necessary.


#4

@blomquisg Can you help out here?


#5

Hi,
looks like you ran into this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1293307
It was fixed here: https://github.com/ManageIQ/manageiq/pull/8094


#6

That fix must not have made it into the appliance (capablanca 2)

I did a git pull in /var/www/miq/vmdb but that does not appear to have solved the problem. In fact, it doesn’t look like the new code was actually pulled down, assuming the fix has been merged.

Even after applying the fixes manually the issue still isn’t resolved.


#7

yes, this was indeed not backported to capablanca

For capablanca you should apply this one: https://github.com/ManageIQ/manageiq/pull/5868

Pull 8094 was for fixing the same issue again, after we introduced config changes.


#8

I don’t really know how git works, I guess. I did a cherry-pick on that specific commit but it broke the app. In a previous installation I did a git pull on the entire tree but that didn’t fix the issue.

How do I get the one commit (#5868) into capablanca without breaking things?


#9

You might have luck with manually adding the changes in the first file here https://github.com/ManageIQ/manageiq/pull/5868/files
The spec files are just for tests, so dont bother with these.