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 1341923 - error: Message did not receive a reply (timeout by message bus)
Summary: error: Message did not receive a reply (timeout by message bus)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: atomic
Version: 7.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Brent Baude
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-02 03:50 UTC by Alex Jia
Modified: 2016-12-06 17:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-06 17:41:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2857 0 normal SHIPPED_LIVE atomic bug fix and enhancement update 2016-12-06 22:40:27 UTC

Description Alex Jia 2016-06-02 03:50:15 UTC 
Description of problem:
To install docker and atomic related RPM package on RHEL7.2 release, and there is no any ostree version deployment, atomc host status will get a error: Message did not receive a reply (timeout by message bus) w/ exit code 1, it's not friendly for users at least

Version-Release number of selected component (if applicable):
rpm -q atomic docker kernel PyYAML
atomic-1.10.3-1.el7.x86_64
docker-1.10.3-26.el7.x86_64
kernel-3.10.0-327.el7.x86_64
PyYAML-3.10-11.el7eng.x86_64


How reproducible:
always

Steps to Reproduce:
1. yum install -y atomic
2. atomic host status


Actual results:
# atomic host status
error: Message did not receive a reply (timeout by message bus)
# echo $?
1


Expected results:
No Deployments or No OSTree deployments found or something like that.

Additional info:
Comment 2 Colin Walters 2016-06-06 14:14:26 UTC 
Right now starting rpm-ostreed errors out if `/ostree/repo` doesn't exist (it used to crash).

We should change it to actually run I think, but also in the meantime, change the atomic command to detect whether `/ostree` exists and if not, say "No /ostree detected, not an Atomic Host system"?
Comment 3 Daniel Walsh 2016-08-26 16:13:22 UTC 
Currently atomic checks for the existence of /usr/bin/rpm-ostree and then addes the host commands, I am changing it to check


    if os.path.exists("/usr/bin/rpm-ostree") and os.path.exists("/ostree"):

With that change you would get.

 ./atomic host status
atomic: invalid choice: 'host' (choose from 'diff', 'help', 'info', 'install', 'images', 'mount', 'push', 'upload', 'pull', 'scan', 'ps', 'stop', 'run', 'storage', 'migrate', 'top', 'uninstall', 'unmount', 'umount', 'update', 'version', 'verify')
Comment 4 Daniel Walsh 2016-08-26 16:15:49 UTC 
https://github.com/projectatomic/atomic/pull/561
Comment 5 Daniel Walsh 2016-10-18 14:15:19 UTC 
Fixed in atomic-1.12
Comment 7 Alex Jia 2016-11-02 02:38:05 UTC 
(In reply to Daniel Walsh from comment #3)
> Currently atomic checks for the existence of /usr/bin/rpm-ostree and then
> addes the host commands, I am changing it to check
> 
> 
>     if os.path.exists("/usr/bin/rpm-ostree") and os.path.exists("/ostree"):
> 
> With that change you would get.
> 
>  ./atomic host status
> atomic: invalid choice: 'host' (choose from 'diff', 'help', 'info',
> 'install', 'images', 'mount', 'push', 'upload', 'pull', 'scan', 'ps',
> 'stop', 'run', 'storage', 'migrate', 'top', 'uninstall', 'unmount',
> 'umount', 'update', 'version', 'verify')

well, the host command has been removed from atomic commands in RHEL7 system, but the man page still exists, I think it's not a big deal.

Colin, is it okay for you? if so, I will move the bug to VERIFIED status.
Comment 8 Colin Walters 2016-11-02 02:48:44 UTC 
That's the expected result currently.
Comment 9 Alex Jia 2016-11-02 02:56:25 UTC 
(In reply to Colin Walters from comment #8)
> That's the expected result currently.

Thanks Colin.
Comment 10 Daniel Walsh 2016-11-02 12:50:09 UTC 
man atomic host

       This command is a high-level wrapper for the underlying rpm-ostree tool
       which can perform upgrades, rollbacks, and system state inspection.  It
       is used for implementations of the Project Atomic Host pattern.

       #NOTE  The  host  subcommand  is  only  available  when  rpm-ostree  is
       installed.

We should open a bug on the man page to expand the description on it not being available on non-atomic host machines.
Comment 11 Alex Jia 2016-11-03 02:05:57 UTC 
(In reply to Daniel Walsh from comment #10)

> We should open a bug on the man page to expand the description on it not
> being available on non-atomic host machines.

The bug 1391308 is used for tracking man page issue.
Comment 13 errata-xmlrpc 2016-12-06 17:41:39 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://rhn.redhat.com/errata/RHBA-2016-2857.html
Note You need to log in before you can comment on or make changes to this bug.