`git push` after a previous failed `git push` dies with a minio error

[technosophos]

I did a git push of a repo. That push failed. So I changed the code and then pushed again. Now I get this error:

⇒  git push deis master
Counting objects: 3, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 291 bytes | 0 bytes/s, done.
Total 3 (delta 2), reused 0 (delta 0)
Added host ‘http://10.247.151.115:9000’ successfully.
mc: <ERROR> Unable to make bucket ‘http://10.247.151.115:9000/git’. The requested bucket name is not available.
‘hearty-checkers.tar.gz’ -> ‘http://10.247.151.115:9000/git/home/hearty-checkers:git-6241aef4/tar’
Total: 2.33 KB, Transferred: 2.33 KB, Speed: 808.72 KB/s
-----> stored tarfile in http://10.247.151.115:9000/git/home/hearty-checkers:git-6241aef4/tar
-----> creating builder pod in namespace deis
pod "hearty-checkers-git-6241aef4" created
Waiting for build to complete...
..........
Build complete.
-----> Launching...
2015/12/16 22:49:06 failed retrieving config from controller: <h1>Server Error (500)</h1>
To ssh://git@deis.10.245.1.3.xip.io:2222/hearty-checkers.git
   e159088..6241aef  master -> master

The important detail seems to be this:

mc: <ERROR> Unable to make bucket ‘http://10.247.151.115:9000/git’. The requested bucket name is not available.

But maybe that's just ignored.

[technosophos]

I'm retesting, and I think this error doesn't make a difference at all.

[arschles]

nope, the error doesn't matter at all and is ignored. it's mc ensuring there's a bucket for all tarballs (something minio requires). it should be piped to /dev/null but https://github.com/deis/builder/issues/29 will remove the error message (and the need to use mc) entirely

[technosophos]

Dumping into Beta

[arschles]

72 has fixed this by adding a uuid to each builder pod's name. closing