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.
Bug 1346942 - atomic shouldn't depend on ostree at runtime if ostree isn't installed
Summary: atomic shouldn't depend on ostree at runtime if ostree isn't installed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: atomic
Version: 7.2
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
Yoana Ruseva
URL:
Whiteboard:
Depends On:
Blocks: 1311544 1315369 1323934
TreeView+ depends on / blocked
 
Reported: 2016-06-15 17:09 UTC by Lokesh Mandvekar
Modified: 2016-06-23 16:22 UTC (History)
2 users (show)

Fixed In Version: atomic-1:1.10.5-5.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1343939
Environment:
Last Closed: 2016-06-23 16:22:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1273 0 normal SHIPPED_LIVE atomic bug fix and enhancement update 2016-06-23 20:13:11 UTC

Description Lokesh Mandvekar 2016-06-15 17:09:19 UTC 
+++ This bug was initially created as a clone of Bug #1343939 +++

--- Additional comment from Lokesh Mandvekar on 2016-06-15 10:52:57 CDT ---

with the build currently in errata, I'm seeing this:

$ sudo atomic images
global name 'OSTree' is not definedn
Comment 4 Alex Jia 2016-06-16 04:59:06 UTC 
I can't reproduce the bug in atomic-1.10.5-[2|3], I also gave a try w/ atomic-1.10.5-5 on rhelah 7.2.5(5b82b4035f), atomic images works well w/o any error, so moving the bug to VERIFIED status.

[cloud-user@atomic-host-001 ~]$ sudo ostree admin status
* rhel-atomic-host 5b82b4035f1920ceb0e31996aa627d8c975d7436260e5538d71728f43f34dfa6.0
    Version: 7.2.5
    Unlocked: hotfix
    origin refspec: rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard
  rhel-atomic-host 5b82b4035f1920ceb0e31996aa627d8c975d7436260e5538d71728f43f34dfa6.1
    Version: 7.2.5
    origin refspec: rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard

[cloud-user@atomic-host-001 ~]$ rpm -q atomic skopeo docker
atomic-1.10.5-5.el7.x86_64
skopeo-0.1.13-5.el7.x86_64
docker-1.10.3-40.el7.x86_64

[cloud-user@atomic-host-001 ~]$ sudo atomic images

  REPOSITORY                                                           TAG      IMAGE ID       CREATED            VIRTUAL SIZE      
> registry.access.redhat.com/rhel7.2                                   latest   sha256:bf203   2016-05-05 16:43   203.43 MB
Comment 6 errata-xmlrpc 2016-06-23 16:22:05 UTC 
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://access.redhat.com/errata/RHBA-2016:1273
Note You need to log in before you can comment on or make changes to this bug.