Project

General

Profile

Bug #9901

Provisioning the same container name twice from the CLI in foreman just gives "500 Internal Server Error"

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

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1204298
Would be nice to show an error like "Container name already taken".

hammer -u admin -p changeme docker container create --name hello --command bash \

--repository-name busybox --tag latest --compute-resource DockerCP
Docker Container Created

hammer -u admin -p changeme docker container create --name hello --command bash \

--repository-name busybox --tag latest --compute-resource DockerCP
Could not create the container:
Error: 500 Internal Server Error

Associated revisions

Revision 2a0cf95b (diff)
Added by David Davis over 7 years ago

Fixes #9901 - Better handling of errors in container api

Revision 2a0cf95b (diff)
Added by David Davis over 7 years ago

Fixes #9901 - Better handling of errors in container api

History

#1 Updated by The Foreman Bot over 7 years ago

  • Status changed from New to Ready For Testing
  • Target version set to 68
  • Pull request https://github.com/theforeman/foreman-docker/pull/105 added
  • Pull request deleted ()

#2 Updated by Eric Helms over 7 years ago

  • Project changed from Katello to Docker
  • Category deleted (83)
  • Target version deleted (68)

#3 Updated by David Davis over 7 years ago

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

Also available in: Atom PDF