Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
1. Proposed title of this feature request
podman - join multiple CNI network and set static IPs for them
2. Who is the customer behind the request?
see private comment
3. What is the nature and description of the request?
With podman-1.9.3-2.module+el8.2.1+6867+366c07d6 which we ship with RHEL 8.2.1 , customer is able to join one ( 1 ) CNI network and can configure a static IP. In the future they need to configure multiple static networks on their podman containers. Today it is not possible/supported.
4. Why does the customer need this? (List the business requirements here)
In the future they need to configure multiple static networks on their podman containers.
5. How would the customer like to achieve this? (List the functional requirements here)
for example:
# podman run -d --rm --name instance0 --network mynetwork1 --ip 172.25.0.200 --network mynetwork2 --ip 192.168.0.200 image:version
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
When "mynetwork1+ and "mynetwork2" are up and are able to communicate over these two networks
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
no
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
RHEL8
9. Is the sales team involved in this request and do they have any additional input?
no
10. List any affected packages or components.
podman-1.9.3-2
11. Would the customer be able to assist in testing this functionality if implemented?
yes
CNI presently only allows one static IP to be set, total. We can join multiple networks, or set a static IP, but not both. The good news is that I'm fairly certain the fix for this is in OCICNI, which we have much more control over than the actual CNI plugins. Probably not terrible to handle, but I haven't looked too deeply - if we do need CNI plugins changes the scale of the fix will rapidly increase.
Target is Podman 4.0, set to release RHEL 8.6.0. A reworking of the Podman network stack to enable features like this is presently under heavy development.
This will be contained in Podman v4.0.0-RC2, currently scheduled for delivery today or tomorrow dependent upon the CI gods.
@jnovy I'm setting this to Post and assigning to you for any further BZ and Packaging needs.
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 (Important: container-tools:rhel8 security, bug fix, and enhancement update), 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://access.redhat.com/errata/RHSA-2022:1762