Bug #9382
closed
Wrong Docker Compute resource getting provisioned
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 > but select the good host
3) Search for busybox repo ( you should get a 500 but thats a different bug).
4) Now do Containers -> new container again
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,
Updated by Partha Aji about 10 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,
Updated by The Foreman Bot about 10 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-docker/pull/85 added
- Pull request deleted (
)
Updated by David Davis about 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset foreman-docker|5397ee73e891b8c9b9a2cda87a26954982f59133.