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 1467439 - Unable to start a container using Satellite6
Summary: Unable to start a container using Satellite6
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management
Version: 6.2.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-03 22:15 UTC by sthirugn@redhat.com
Modified: 2017-07-07 20:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-07 20:19:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description sthirugn@redhat.com 2017-07-03 22:15:38 UTC
Description of problem:
Unable to start a container using Satellite6

Version-Release number of selected component (if applicable):
satellite-6.2.10-4.0.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. Install Satellite6 (I hosted Satellite6 in AWS)
2. Install external docker computer resource
3. Pull fedora/ssh docker container in Satellite, publish/promote
4. Create a new fedora/ssh container in external docker compute resource.
For command use \bin\bash

Actual results:
Container is stopped and is not started

I dont see any error message in logs.

Expected results:
Container is running

Additional info:
* The docker image is pulled in the external docker compute resource
* I can run a container manually in the external docker compute resoure:
# docker run -it sat6-aws-scenario3a.duckdns.org:5000/default_organization-custom_product_1-fedora_ssh /bin/bash
15+0 records in
15+0 records out
15 bytes copied, 5.618e-05 s, 267 kB/s
Generating public/private rsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_rsa_key.
Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub.
The key fingerprint is:
SHA256:/D+yKbzLyATf90B6GZ0VCy0WFPHGt96cBsaUp+mA8iM root@12c07d79a868
The key's randomart image is:
+---[RSA 2048]----+
|           .*=.  |
|            o+oo |
|           . +*..|
|       .  ..o++..|
|    .  .S.o.o* . |
|     o .o+ o+ o.o|
|      oEoo*  . +o|
|     o o+oo=. .  |
|      o ++ooo.   |
+----[SHA256]-----+
Changing password for user user.
passwd: all authentication tokens updated successfully.
ssh user password: mdeJnEEDalMmW6TMFz2m
[root@12c07d79a868 /]#

Comment 2 sthirugn@redhat.com 2017-07-07 20:19:53 UTC
User error - the command /bin/bash finishes too fast to notice it.  As suggested by Jake Callahan, I tried using `ping -c localhost`, I was able to see the container.  If I find any other issue, I will reopen this bug. But for now, I am closing this bug as user error.


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