Bug 1467439 - Unable to start a container using Satellite6
Unable to start a container using Satellite6
Status: CLOSED NOTABUG
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Container Management (Show other bugs)
6.2.10
Unspecified Unspecified
unspecified Severity unspecified (vote)
: Unspecified
: --
Assigned To: satellite6-bugs
Katello QA List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-03 18:15 EDT by sthirugn@redhat.com
Modified: 2017-07-07 16:19 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-07-07 16:19:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description sthirugn@redhat.com 2017-07-03 18:15:38 EDT
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 16:19:53 EDT
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.