Description of problem: If an Amazon VPC has no gateways configured and is chose to deploy Amazon SSA agent on it, SSA will fail due to its unaccessible agent. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a VPC; 2. Do not attach any gateway to it; 3. Turn on 'DNS resolution', 'DNS hostname' to 'yes'; 4. Deploy an agent on this VPC; 5. Run SSA job; Actual results: SSA fails. Expected results: SSA works. Additional info:
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition. If it's something like a tracker bug where it doesn't matter, please set the severity to Low.
https://github.com/ManageIQ/manageiq-providers-amazon/pull/424
New commit detected on ManageIQ/manageiq-providers-amazon/master: https://github.com/ManageIQ/manageiq-providers-amazon/commit/4df81dff80d8b63512e3cf04d808d8d090aba753 commit 4df81dff80d8b63512e3cf04d808d8d090aba753 Author: hsong-rh <hsong> AuthorDate: Tue Mar 20 14:55:37 2018 -0400 Commit: hsong-rh <hsong> CommitDate: Tue Mar 20 14:55:37 2018 -0400 Fixes VPC selection to make sure it has internet gateway attached. https://bugzilla.redhat.com/show_bug.cgi?id=1557377 app/models/manageiq/providers/amazon/agent_coordinator.rb | 31 +- 1 file changed, 27 insertions(+), 4 deletions(-)
Able to see the agent deployed using VPC which has Gateway attached to it. Verified Version: 5.10.0.21.20181023151612_4c11b0d