Hi,

I used bosh-init to deploy microbosh in AWS using IAM instance profiles and it was successful..Deployed bosh as well using IAM instance profiles..While deploying CF, I'v been running into following issue.Used working yml file.Any advise would be appreicated

Started creating new packages
Started creating new packages > buildpack_python/f7f81defd518e5c9f29aefe9c8957cb2fbcd5028. Failed: unsupported action (00:00:03)

Error 100: unsupported action

Debug logs says :

I, [2015-10-15 19:05:13 #4784] [task:5] INFO -- DirectorJobRunner: Creating package 'acceptance-tests/f234c66613011d4ba818840b587a62c3906dbdd7' from provided bits
D, [2015-10-15 19:05:13 #4784] [] DEBUG -- DirectorJobRunner: Lock renewal thread exiting
D, [2015-10-15 19:05:13 #4784] [task:5] DEBUG -- DirectorJobRunner: Deleting lock: lock:release:cf
D, [2015-10-15 19:05:13 #4784] [task:5] DEBUG -- DirectorJobRunner: Deleted lock: lock:release:cf
E, [2015-10-15 19:05:14 #4784] [task:5] ERROR -- DirectorJobRunner: unsupported action
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/blobstore_client-1.3088.0/lib/blobstore_client/s3_blobstore_client.rb:66:in `create_file'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/blobstore_client-1.3088.0/lib/blobstore_client/base.rb:27:in `create'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/blob_util.rb:8:in `block in create_blob'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/blob_util.rb:8:in `open'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/blob_util.rb:8:in `create_blob'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:470:in `save_package_source_blob'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:447:in `create_package'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:347:in `block (2 levels) in create_packages'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/event_log.rb:97:in `call'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/event_log.rb:97:in `advance_and_track'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/event_log.rb:50:in `track'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:345:in `block in create_packages'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:342:in `each'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:342:in `create_packages'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:257:in `process_packages'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:144:in `process_release'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:49:in `block in perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/lock_helper.rb:24:in `block in with_release_lock'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/lock_helper.rb:36:in `with_release_locks'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/lock_helper.rb:24:in `with_release_lock'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:49:in `perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/job_runner.rb:108:in `perform_job'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/job_runner.rb:31:in `block in run'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3088.0/lib/common/thread_formatter.rb:49:in `with_thread_name'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/job_runner.rb:31:in `run'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/base_job.rb:10:in `perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/job.rb:227:in `perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:250:in `perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:189:in `block in work'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:166:in `loop'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:166:in `work'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/bin/bosh-director-worker:75:in `<top (required)>'
/var/vcap/packages/director/bin/bosh-director-worker:16:in `load'
/var/vcap/packages/director/bin/bosh-director-worker:16:in `<main>'
D, [2015-10-15 19:05:14 #4784] [task:5] DEBUG -- DirectorJobRunner: (0.001798s) SELECT NULL
D, [2015-10-15 19:05:14 #4784] [task:5] DEBUG -- DirectorJobRunner: (0.001104s) BEGIN
D, [2015-10-15 19:05:14 #4784] [task:5] DEBUG -- DirectorJobRunner: (0.001320s) UPDATE "tasks" SET "state" = 'error', "timestamp" = '2015-10-15 19:05:14.055672+0000', "description" = 'create release', "result" = 'unsupported action', "output" = '/var/vcap/store/director/tasks/5', "checkpoint_time" = '2015-10-15 19:05:12.673932+0000', "type" = 'update_release', "username" = 'admin' WHERE ("id" = 5)
D, [2015-10-15 19:05:14 #4784] [task:5] DEBUG -- DirectorJobRunner: (0.002808s) COMMIT

Unfortunetly error message is not descriptive, but it seems that Director
is using readonly blobstore but it should be using read-write blobstore
client. What is your blobstore Director configuration?

On Fri, Oct 16, 2015 at 9:34 AM, Satya Thokachichu <tsnraju(a)yahoo.com>
wrote:

Hi,

I used bosh-init to deploy microbosh in AWS using IAM instance profiles
and it was successful..Deployed bosh as well using IAM instance
profiles..While deploying CF, I'v been running into following issue.Used
working yml file.Any advise would be appreicated

Started creating new packages
Started creating new packages >
buildpack_python/f7f81defd518e5c9f29aefe9c8957cb2fbcd5028. Failed:
unsupported action (00:00:03)

Error 100: unsupported action

Debug logs says :

I, [2015-10-15 19:05:13 #4784] [task:5] INFO -- DirectorJobRunner:
Creating package
'acceptance-tests/f234c66613011d4ba818840b587a62c3906dbdd7' from provided
bits
D, [2015-10-15 19:05:13 #4784] [] DEBUG -- DirectorJobRunner: Lock renewal
thread exiting
D, [2015-10-15 19:05:13 #4784] [task:5] DEBUG -- DirectorJobRunner:
Deleting lock: lock:release:cf
D, [2015-10-15 19:05:13 #4784] [task:5] DEBUG -- DirectorJobRunner:
Deleted lock: lock:release:cf
E, [2015-10-15 19:05:14 #4784] [task:5] ERROR -- DirectorJobRunner:
unsupported action
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/blobstore_client-1.3088.0/lib/blobstore_client/s3_blobstore_client.rb:66:in
`create_file'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/blobstore_client-1.3088.0/lib/blobstore_client/base.rb:27:in
`create'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/blob_util.rb:8:in
`block in create_blob'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/blob_util.rb:8:in
`open'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/blob_util.rb:8:in
`create_blob'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:470:in
`save_package_source_blob'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:447:in
`create_package'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:347:in
`block (2 levels) in create_packages'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/event_log.rb:97:in
`call'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/event_log.rb:97:in
`advance_and_track'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/event_log.rb:50:in
`track'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:345:in
`block in create_packages'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:342:in
`each'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:342:in
`create_packages'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:257:in
`process_packages'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:144:in
`process_release'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:49:in
`block in perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/lock_helper.rb:24:in
`block in with_release_lock'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/lock_helper.rb:36:in
`with_release_locks'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/lock_helper.rb:24:in
`with_release_lock'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/update_release.rb:49:in
`perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/job_runner.rb:108:in
`perform_job'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/job_runner.rb:31:in
`block in run'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3088.0/lib/common/thread_formatter.rb:49:in
`with_thread_name'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/job_runner.rb:31:in
`run'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/lib/bosh/director/jobs/base_job.rb:10:in
`perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/job.rb:227:in
`perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:250:in
`perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:189:in
`block in work'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:166:in
`loop'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:166:in
`work'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3088.0/bin/bosh-director-worker:75:in
`<top (required)>'
/var/vcap/packages/director/bin/bosh-director-worker:16:in `load'
/var/vcap/packages/director/bin/bosh-director-worker:16:in `<main>'
D, [2015-10-15 19:05:14 #4784] [task:5] DEBUG -- DirectorJobRunner:
(0.001798s) SELECT NULL
D, [2015-10-15 19:05:14 #4784] [task:5] DEBUG -- DirectorJobRunner:
(0.001104s) BEGIN
D, [2015-10-15 19:05:14 #4784] [task:5] DEBUG -- DirectorJobRunner:
(0.001320s) UPDATE "tasks" SET "state" = 'error', "timestamp" = '2015-10-15
19:05:14.055672+0000', "description" = 'create release', "result" =
'unsupported action', "output" = '/var/vcap/store/director/tasks/5',
"checkpoint_time" = '2015-10-15 19:05:12.673932+0000', "type" =
'update_release', "username" = 'admin' WHERE ("id" = 5)
D, [2015-10-15 19:05:14 #4784] [task:5] DEBUG -- DirectorJobRunner:
(0.002808s) COMMIT

Thanks for the reply..
If I use IAM instance profile in blobstore director config ,I am getting "Unsupported action"..If I use aws access/secret key , able to deploy cf successfully.. s3 bucket can be accessed by Everyone. Please advise..


blobstore:
agent:
user: agent
password: agent
director:
user: director
password: director
provider: s3
bucket_name: satya-np-bosh
iam_instance_profile: test_profile ---> Doesnt work
---------------------------------
blobstore:
agent:
user: agent
password: agent
director:
user: director
password: director
provider: s3
bucket_name: satya-np-bosh
access_key_id: xxxxxxxxxxx
secret_access_key: xxxxxxxxxxx -> Works..