Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1269196 - hammer docker container status not showing correct status
Summary: hammer docker container status not showing correct status
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management
Version: 6.1.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-06 15:23 UTC by Andrii Balakhtar
Modified: 2017-01-11 19:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-11 19:29:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16102 0 None None None 2016-08-13 13:47:59 UTC

Description Andrii Balakhtar 2015-10-06 15:23:09 UTC
Description of problem:
'hammer docker container status' always shows 'Running: no' for all the containers, even after successful 'hammer docker container start' command.

Version-Release number of selected component (if applicable):
6.1.3C2

How reproducible:
Always

Steps to Reproduce:
1. # hammer -u admin -p changeme compute-resource create --name test_cr --organization-ids 37 --provider Docker --url unix:///var/run/docker.sock
Compute resource created

2. # hammer -u admin -p changeme docker container create --compute-resource-id 77 --organization-ids 37 --command top --name test_container --repository-name busybox --tag latest
Docker container created

3. # hammer -u admin -p changeme docker container status --id 30
Running: no

4. # hammer -u admin -p changeme docker container start --id 30
The container was started.

5. # hammer -u admin -p changeme docker container status --id 30
Running: no

Actual results:
'Running: no' status for started container.

Expected results:
'Running: yes' status for started container.

Additional info:

Comment 3 Bryan Kearney 2016-08-04 20:10:08 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 6 Bryan Kearney 2017-01-11 19:29:22 UTC
This is an older bug which has been reported upstream. We are not going to track this bug downstream. When the upstream issue is resolved, the next build will contain the fix. Thank you.


Note You need to log in before you can comment on or make changes to this bug.