Bug 760409 - Unable to mount s3 storage
Summary: Unable to mount s3 storage
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fuse-s3fs
Version: 16
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Neil Horman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-06 04:42 UTC by Boyd
Modified: 2012-01-25 22:34 UTC (History)
2 users (show)

Fixed In Version: fuse-s3fs-0.9-1.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-25 22:34:55 UTC
Type: ---


Attachments (Terms of Use)

Description Boyd 2011-12-06 04:42:21 UTC
Description of problem:  Unable to mount s3 storage as fuse file system


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Export AWS key and secret key into environment variables
AWS_SECRET_ACCESS_KEY=123456
AWS_ACCESS_KEY_ID=xyzabc


2. Run 's3fs bucketname /mnt/mountpoint'
3.
  
Actual results:  Python error & 403 error
Traceback (most recent call last):
  File "/usr/bin/s3fs", line 1531, in <module>
    main()
  File "/usr/bin/s3fs", line 1516, in main
    if fs.setup() == False:
  File "/usr/bin/s3fs", line 917, in setup
    fsdata_key = self.blockdev.bucket.get_key("fsdata")
  File "/usr/lib/python2.7/site-packages/boto/s3/bucket.py", line 198, in get_key
    response.status, response.reason, '')
boto.exception.S3ResponseError: S3ResponseError: 403 Forbidden


Expected results:  File system should be mounted


Additional info:

I have compiled and run another fuse s3 mounter from http://code.google.com/p/s3fs/wiki/FuseOverAmazon.  This works fine.

Comment 1 Neil Horman 2011-12-06 11:41:35 UTC
Looks like get_key has started throwing an exception, it used to not do that.  I can fix that pretty easily.   get_key is failing however because the bucket you are trying to mount is not yet formatted for fuse-s3fs.  You need to run the following command:
s3fs -C -f <bucket>

That will format the bucket by creating the fsdata file.  At that point you will be able to mount it.

Comment 2 Neil Horman 2011-12-06 16:42:13 UTC
I've fixed this with upstream commit f968e05043d2c658b9c1805988fa630a0c46c6b1.

Comment 3 Fedora Update System 2011-12-06 17:02:03 UTC
fuse-s3fs-0.7-6.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/fuse-s3fs-0.7-6.fc16

Comment 4 Fedora Update System 2011-12-10 19:49:10 UTC
Package fuse-s3fs-0.7-6.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fuse-s3fs-0.7-6.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-16887/fuse-s3fs-0.7-6.fc16
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2011-12-21 19:36:59 UTC
fuse-s3fs-0.9-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/fuse-s3fs-0.9-1.fc16

Comment 6 Fedora Update System 2012-01-25 22:34:55 UTC
fuse-s3fs-0.9-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.