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:
Right now, atomic version <system containers images> only print out hash version instead of application version like rpm -q their counterparts. One of the developers mentioned that system containers do not use the label metadata.
# atomic version brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhel7/etcd:latest
brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhel7/etcd:latest: ba648b580c2ad25f95f9969ff21e138eb062d5c4f9ef3eb19b0461a75e96e8bf
Non-system containers work fine.
# atomic version registry.access.stage.redhat.com/rhel7/rhel-tools
Image Name: registry.access.stage.redhat.com/rhel7/rhel-tools:latest
distribution-scope: public
build-date: 2016-09-09T14:41:51.833402Z
RUN: docker run -it --name NAME --privileged --ipc=host --net=host --pid=host -e HOST=/host -e NAME=NAME -e IMAGE=IMAGE -v /run:/run -v /var/log:/var/log -v /etc/machine-id:/etc/machine-id -v /etc/localtime:/etc/localtime -v /:/host IMAGE
Name: rhel7/rhel-tools
License: GPLv3
Build_Host: rcm-img-docker02.build.eng.bos.redhat.com
vcs-type: git
vcs-ref: 553003eafc24b53361627c933d8afccee085e440
release: 104
Version: 7.2
Architecture: x86_64
Release: 51
Vendor: Red Hat, Inc.
BZComponent: rhel-tools-docker
Authoritative_Registry: registry.access.redhat.com
com.redhat.build-host: rcm-img-docker02.build.eng.bos.redhat.com
architecture: x86_64
Version-Release number of selected component (if applicable):
atomic-1.12.2-3.el7.x86_64
How reproducible:
always
Actual results:
Print out a hash version.
Expected results:
Print out a more meaningful daemon version like 2.3.7-8 like non-system containers.
Additional info:
flannel-docker and etc3-docker have the same issue.
Not sure why is this assigned to etcd-docker, reassigning to atomic.
Comment 3Giuseppe Scrivano
2016-09-21 06:34:09 UTC
this is still missing. System containers are currently using Docker to build the image but I am not sure we should hook more into Docker and use the LABELs metadata