Date
1 - 2 of 2
Creating another release with the same bosh director
|
Oded Gold
I am trying to create another release using the same bosh director I am not sure if what I am try is possible but in big I have done the following
Using a new user (linux user) I created a new release directory with a new deployment manifest When I try run bosh create release or bosh sync blobs I get the below error staging(a)ip-10-1-1-212:~/repos/bss-release$ bosh create release Syncing blobs... postgres/postgresql-9.0.3.tar.gz downloading 17.5M (600%) /home/staging/.rvm/gems/ruby-1.9.3-p327/gems/blobstore_client-1.3155.0/lib/blobstore_client/sha1_verifiable_blobstore_client.rb:38:in `check_sha1': sha1 mismatch expected=c8fb5d1d7930e78211e554bb5751183a8148d0ee actual=1c8bf334fd38a20564457cc3f16749650763371b (Bosh::Blobstore::BlobstoreError) from /home/staging/.rvm/gems/ruby-1.9.3-p327/gems/blobstore_client-1.3155.0/lib/blobstore_client/sha1_verifiable_blobstore_client.rb:24:in `get' from /home/staging/.rvm/gems/ruby-1.9.3-p327/gems/blobstore_client-1.3155.0/lib/blobstore_client/retryable_blobstore_client.rb:19:in `block in get' from /home/staging/.rvm/gems/ruby-1.9.3-p327/gems/bosh_common-1.3155.0/lib/common/retryable.rb:28:in `call' from /home/staging/.rvm/gems/ruby-1.9.3-p327/gems/bosh_common-1.3155.0/lib/common/retryable.rb:28:in `block in retryer' from /home/staging/.rvm/gems/ruby-1.9.3-p327/gems/bosh_common-1.3155.0/lib/common/retryable.rb:26:in `loop' from /home/staging/.rvm/gems/ruby-1.9.3-p327/gems/bosh_common-1.3155.0/lib/common/retryable.rb:26:in `retryer' from /home/staging/.rvm/gems/ruby-1.9.3-p327/gems/blobstore_client-1.3155.0/lib/blobstore_client/retryable_blobstore_client.rb:18:in `get' from /home/staging/.rvm/gems/ruby-1.9.3-p327/gems/bosh_cli-1.3155.0/lib/cli/blob_manager.rb:316:in `download_blob' from /home/staging/.rvm/gems/ruby-1.9.3-p327/gems/bosh_cli-1.3155.0/lib/cli/blob_manager.rb:242:in `block (3 levels) in process_index' from /home/staging/.rvm/gems/ruby-1.9.3-p327/gems/bosh_common-1.3155.0/lib/common/thread_pool.rb:77:in `call' from /home/staging/.rvm/gems/ruby-1.9.3-p327/gems/bosh_common-1.3155.0/lib/common/thread_pool.rb:77:in `block (2 levels) in create_thread' from /home/staging/.rvm/gems/ruby-1.9.3-p327/gems/bosh_common-1.3155.0/lib/common/thread_pool.rb:63:in `loop' from /home/staging/.rvm/gems/ruby-1.9.3-p327/gems/bosh_common-1.3155.0/lib/common/thread_pool.rb:63:in `block in create_thread' from /home/staging/.rvm/gems/ruby-1.9.3-p327/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in `call' from /home/staging/.rvm/gems/ruby-1.9.3-p327/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in `block in create_with_logging_context' Where does it get this sha values that it show the mismatch error. My previous deployment with is working Thank you |
|
|
|
Dmitriy Kalinin
Creating release doesnt involve the Director.
toggle quoted message
Show quoted text
bosh create release first downloads blobs listed in config/blobs.yml. It looks like CLI had a problem downloading postgres tgz and received a corrupt version (hence sha1 mismatch). I would try running bosh create release (or bosh sync blobs) again and see if this time download succeeds. On Thu, Dec 17, 2015 at 12:56 AM, Oded Gold <oded(a)nurego.com> wrote:
I am trying to create another release using the same bosh director I am |
|
|