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.
ubi-8-baseos provides the network-scripts package but does not provide NetworkManager. Since network-scripts was deprecated in RHEL 8 and NetworkManager should be used instead, this situation does not make much sense. If network configuration is required in container images, NetworkManager should be available as well (IMHO).
Till,
Do you have a specific requirement to configure networking in the container with NetworkManager? Or, are you just saying that it's inconsistent? The network scripts may have been pulled in as a dependency of some other package. We definitely didn't design the dependency tree to imply that configuring networking in the container is even supported.
Product Manager - Red Hat Universal Base Image
Best Regards
Scott McCarty
Scott, this is mainly an inconsistency I noticed. Having NM in ubi would be useful for upstream testing of projects that build on top of NM. This was why I as looking into the situation. I do not have a business case to have either of them present in the image.
Till,
I think that the network scripts got pulled in as a depency for something else. Today, UBI is really targeted towards cloud native, application developers working with languages like Java, Node.js, Golang, .Net, Perl, Python, Ruby, and PHP [1]. Currently, this request does not fall within the currently approved use cases for inclusion in UBI. The scope of UBI will likely grow and we will keep this use case in mind.
[1]: https://developers.redhat.com/blog/2019/10/09/what-is-red-hat-universal-base-image/
Best Regards
Scott McCarty, RHCA
Product Management - Containers, Red Hat Enterprise Linux & OpenShift
Email: smccarty