Description of problem: HTTP Error 400 (Bad Request) Project name should not be greater than 64 characters during deployment Version-Release number of selected component (if applicable): TP3 RC4/QCI-1.0-RHEL-7-20160422.t.0 How reproducible: 100% Steps to Reproduce: 1. Install QCI and TripleO ISOs 2. Log in to run launch-fusor-*installer 3. Deploy with long name (100 characters) Actual results: Expected([200]) <=> Actual(400 Bad Request) response => #<Excon::Response:0x0000000e5a0e20 @data={:body=>"{\"error\": {\"message\": \"Project name should not be greater than 64 characters.\", \"code\": 400, \"title\": \"Bad Request\"}}", :headers=>{"Vary"=>"X-Auth-Token", "Content-Type"=>"application/json", "Content-Length"=>"117", "X-Openstack-Request-Id"=>"req-172018da-3ea1-4b53-bb78-78df65d9cf0a", "Date"=>"Fri, 22 Apr 2016 22:21:30 GMT"}, :status=>400, :remote_ip=>"192.168.150.5", :local_port=>38351, :local_address=>"192.168.252.10"}, @body="{\"error\": {\"message\": \"Project name should not be greater than 64 characters.\", \"code\": 400, \"title\": \"Bad Request\"}}", @headers={"Vary"=>"X-Auth-Token", "Content-Type"=>"application/json", "Content-Length"=>"117", "X-Openstack-Request-Id"=>"req-172018da-3ea1-4b53-bb78-78df65d9cf0a", "Date"=>"Fri, 22 Apr 2016 22:21:30 GMT"}, @status=400, @remote_ip="192.168.150.5", @local_port=38351, @local_address="192.168.252.10"> Expected results: UI should not allow > 64 characters for deployment name Additional info: Workaround: Redeploy with name <= 64 characters. Should be caught by UI
PR: https://github.com/fusor/fusor/pull/968
Addressed in ISO Set: QCI-1.2-RHEL-7-20160623.t.0-QCI-x86_64-dvd1.iso QCIOOO-8.0-RHEL-7-20160623.t.0-QCIOOO-x86_64-dvd1.iso
Verified in QCI 1.2: "This field must be 64 characters or less."
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2016:1862