Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1370310 - add support for secondary fixed IP addresses for AWS ENI interfaces
add support for secondary fixed IP addresses for AWS ENI interfaces
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers (Show other bugs)
5.6.0
Unspecified Unspecified
high Severity medium
: GA
: 5.6.2
Assigned To: Ladislav Smola
Matouš Mojžíš
ec2
: ZStream
Depends On: 1370307
Blocks:
  Show dependency treegraph
 
Reported: 2016-08-25 19:13 EDT by Dave Johnson
Modified: 2016-10-04 10:32 EDT (History)
4 users (show)

See Also:
Fixed In Version: 5.6.2.0
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1370307
Environment:
Last Closed: 2016-10-04 10:32:11 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1996 normal SHIPPED_LIVE Important: CFME 4.1 bug fixes and enhancement update 2016-10-04 14:26:13 EDT

  None (edit)
Description Dave Johnson 2016-08-25 19:13:14 EDT
+++ This bug was initially created as a clone of Bug #1370307 +++

Description of problem:
===============================================
Seems like AWS supports a secondary fixed IP for ENI, but our current architecture does not allow that. 

As a backportable fix, we can show only the first one. The PR is for Amazon gem, but for 5.6, you can find that code inside ManageIQ,
https://github.com/ManageIQ/manageiq-providers-amazon/pull/33


Version-Release number of selected component (if applicable):
5.6.z
Comment 1 Ladislav Smola 2016-08-26 04:04:35 EDT
https://github.com/ManageIQ/manageiq/pull/10777
Comment 2 Matouš Mojžíš 2016-09-21 10:29:37 EDT
Verified in 5.6.2.0. After adding secondy IP address and refreshing no errors appeared.
Comment 4 errata-xmlrpc 2016-10-04 10:32:11 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-1996.html

Note You need to log in before you can comment on or make changes to this bug.