s3cmd fails on buckets with "."s

Bug #1439811 reported by Luke Faraone
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
s3cmd (Ubuntu)
Fix Released
Medium
Luke Faraone
Trusty
Confirmed
Undecided
Unassigned
Vivid
Confirmed
Undecided
Unassigned

Bug Description

When running on a bucket like "foo.luke.wf", s3cmd will print an error like this:

WARNING: Retrying failed request: /?prefix=ops/ (hostname 'foo.luke.wf.s3.amazonaws.com' doesn't match either of '*.s3.amazonaws.com', 's3.amazonaws.com')

Fixed upstream in https://github.com/s3tools/s3cmd/commit/ecee692cbc355f775508b7d769493a3b56f12656

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: s3cmd 1.5.0~rc1-2
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Apr 2 11:37:42 2015
InstallationDate: Installed on 2014-10-01 (182 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3)
PackageArchitecture: all
SourcePackage: s3cmd
UpgradeStatus: Upgraded to vivid on 2015-02-04 (56 days ago)

Revision history for this message
Luke Faraone (lfaraone) wrote :
Changed in s3cmd (Ubuntu):
importance: Undecided → Medium
tags: added: patch
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

I guess this is fixed in wily.

Changed in s3cmd (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in s3cmd (Ubuntu Trusty):
status: New → Confirmed
Changed in s3cmd (Ubuntu Vivid):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.