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.

Description of problem:


Version-Release number of selected component (if applicable):
docker-1.9.1-19.el7.x86_64
docker version: 1.9.1
Image full_name:registry.access.redhat.com/rhel7/rhel:latest
LONG_ID:bf63a676257aeb7a75a6bbbda138398bbaf223ab34fe9d169e458f9b399004ef 

How reproducible:
Unknown, failure found in CI: https://url.corp.redhat.com/acc530c
with job configuration: https://url.corp.redhat.com/e7afa6c

Steps to Reproduce:
1. run docker inspect against a running container

Actual results:
[
{
...cut...
    "NetworkSettings": {
        ...cut...
        "Networks": {
            "bridge": {     <----- lower-case B
...cut...
}
]

Expected results:
[
{
...cut...
    "NetworkSettings": {
        ...cut...
        "Networks": {
            "Bridge": {     <----- upper-case B
...cut...
}
]

Additional info:

I don't see this as a bug.  "bridge" is the name of the network.  It could just as easily been called "foobar".


man docker run
...
       --net="bridge"
          Set the Network mode for the container
                                      'bridge': create a network stack on  the
       default Docker bridge
                                      'none': no networking
                                      'container:<name|id>':   reuse   another
       container's network stack
                                      'host':  use  the  Docker  host  network
       stack.  Note:  the  host  mode gives the container full access to local
       system services such as D-bus and is therefore considered insecure.
                                      '<network-name>|<network-id>':   connect
       to a user-defined network

(In reply to Daniel Walsh from comment #2)
> I don't see this as a bug.  "bridge" is the name of the network.  It could
> just as easily been called "foobar".

Oh ok, so it's more of a 'data' key as opposed structural. Fair enough, I'll add an exception to checking this in CI.

(ref: https://github.com/autotest/autotest-docker/pull/585 )