Bug 1285461
| Summary: | [RFE] Improve formatting of "atomic images" output | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Yoana Ruseva <yruseva> |
| Component: | atomic | Assignee: | Brent Baude <bbaude> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.2 | CC: | ajia, dwalsh, lsm5 |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-03-31 23:25:28 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Yoana Ruseva
2015-11-25 16:18:33 UTC
A fix for this was pushed into atomic master: https://github.com/projectatomic/atomic/commit/c9a028ece05e81fd53b8bce72d598149d04c651c Are you able to pull master and see if this remedies your RFE and provide feedback here please. Fixed in atomic-1.8 It looks fine on atomic-1.8-6.git1bc3814.el7.x86_64, so move the bug to VERIFIED status. # atomic images REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE centos_stop_label latest 3e7ae7fa2964 2016-02-01 11:41 196.63 MB busybox_label latest b400a4e19136 2016-01-21 11:40 1.11 MB docker.io/centos latest c8a648134623 2015-12-24 23:30 196.63 MB docker.io/busybox latest fc0db02f3072 2015-12-09 02:31 1.11 MB registry.access.redhat.com/rhel7/rhel-tools latest fd2acbeb2b97 2015-12-04 18:44 1.16 GB registry.access.redhat.com/rhel7/rsyslog latest b98636a98907 2015-12-03 18:02 214.12 MB docker-registry.usersys.redhat.com/micah/fedora-uat latest fc918be8d896 2015-07-17 00:12 1.26 GB 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/RHBA-2016-0527.html |