Project

General

Profile

Actions

Bug #9382

closed

Wrong Docker Compute resource getting provisioned

Added by Partha Aji over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1192614
1) Have 2 compute resources of Type docker, preferably one with a bad url(BadHost) and one good container host url (GoodHost)
2) Goto Containers > new container -> select BadHost and then go to "Docker Hub" for images
3) Search for busybox repo ( you should get a 500 but thats a different bug).
4) Now do Containers -> new container again
> but select the good host
5) Select katello-registry under images and select a katello repo and tag
6) Go ahead and try to create a new container hitting next and submit

Note that the container getting provisioned on the bad host, even though you asked it to get created on the Good One,

Actions #1

Updated by Partha Aji over 9 years ago

  • Project changed from Katello to Docker
  • Category deleted (83)
  • Assignee set to David Davis

1) Have 2 compute resources of Type docker, preferably one with a bad url(BadHost) and one good container host url (GoodHost)
2) Goto Containers > new container -> select BadHost and then go to "Docker Hub" for images
3) Search for busybox repo ( you should get a 500 but thats a different bug).
4) Now do Containers -> new container again > but select the good host
5) Select katello-registry under images and select a katello repo and tag
6) Go ahead and try to create a new container hitting next and submit

Note that the container getting provisioned on the bad host, even though you asked it to get created on the Good One,

Actions #2

Updated by The Foreman Bot over 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman-docker/pull/85 added
  • Pull request deleted ()
Actions #3

Updated by David Davis over 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF