[gateway-gcs] Incorrect error message when creating a bucket

[harshavardhana]

Expected Behavior

$ mc mb mygcs/testbucket
mc: <ERROR> Unable to make bucket `s3/testbucket`. The requested bucket name is not available. The bucket namespace is shared by all users of the system. Please select a different name and try again.

Current Behavior

$ mc mb --debug mygcs/testbucket
mc: <DEBUG> PUT /testbucket/ HTTP/1.1
Host: 10.0.0.13:9000
User-Agent: Minio (linux; amd64) minio-go/2.0.4 mc/2017-05-03T10:02:54Z
Content-Length: 0
Authorization: AWS4-HMAC-SHA256 Credential=minio/20170511/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=**REDACTED**
X-Amz-Content-Sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
X-Amz-Date: 20170511T070151Z
Accept-Encoding: gzip

mc: <DEBUG> HTTP/1.1 000 000 status code 000
Transfer-Encoding: chunked
Accept-Ranges: bytes
Content-Type: application/xml
Date: Thu, 11 May 2017 07:01:51 GMT
Server: Minio/DEVELOPMENT.2017-05-11T06-52-24Z (linux; amd64)
Vary: Origin
X-Amz-Bucket-Region: us-east-1
X-Amz-Request-Id: 14BD7B335BBDA362

cd
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code></Code><Message></Message><Key></Key><BucketName></BucketName><Resource>/testbucket/</Resource><RequestId>3L137</RequestId><HostId>3L137</HostId></Error>
0

mc: <DEBUG> Response Time:  698.062968ms

mc: <ERROR> Unable to make bucket `mygcs/testbucket`. 
 (1) mb-main.go:126 cmd.mainMakeBucket(..) Tags: [mygcs/testbucket]
 (0) client-s3.go:765 cmd.(*s3Client).MakeBucket(..)
 Release-Tag:DEVELOPMENT.2017-05-03T10-02-54Z | Commit:d9be3508f8df | Host:prtsc | OS:linux | Arch:amd64 | Lang:go1.7.5 | Mem:2.2MB/6.7MB | Heap:2.2MB/3.7MB

Possible Solution

Fix the error code propagation.

Steps to Reproduce (for bugs)

Just configure minio gateway gcs <project_id> and mc mb mygcs/testbucket

Context

GCS testing.

Your Environment

Using 8dcd491 from feature-gcs branch.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.