Error deploying CF on virtualbox using Bosh












0














I am using mac OS and trying to deploy CF on virtualbox using BOSH.



BOSH Director installed has the following details



$ bosh -e vbox env
Using environment '192.168.50.6' as user 'admin'

Name bosh-lite
UUID bbdcc68d-5390-4d08-bd80-900bf3aa3551
Version 268.2.0 (00000000)
CPI warden_cpi
Features compiled_package_cache: disabled
config_server: enabled
local_dns: enabled
power_dns: disabled
snapshots: disabled
User admin


Bosh CLI version is



version 5.4.0-891ff634-2018-11-14T00:21:14Z


To deploy CF, I run the following script



bosh -e 192.168.50.6 -d cf deploy 
cf-deployment.yml
-o operations/bosh-lite.yml
-v system_domain=bosh-lite.com


I get the following error:



Task 33 | 15:26:34 | Updating instance diego-api: diego-api/95e076b7-0fc4-43e0-9db6-afbd8b79d76d (0) (canary) (00:20:19)
L Error: 'diego-api/95e076b7-0fc4-43e0-9db6-afbd8b79d76d (0)' is not running after update. Review logs for failed jobs: bbs, silk-controller, locket
Task 33 | 15:46:53 | Error: 'diego-api/95e076b7-0fc4-43e0-9db6-afbd8b79d76d (0)' is not running after update. Review logs for failed jobs: bbs, silk-controller, locket

Task 33 Started Fri Nov 16 15:24:57 UTC 2018
Task 33 Finished Fri Nov 16 15:46:53 UTC 2018
Task 33 Duration 00:21:56
Task 33 error

Updating deployment:
Expected task '33' to succeed but state is 'error'

Exit code 1


cf-deployment file and ops file (from iaas/bosh-lite/cloud-config.yml) folder) that I use are from



https://github.com/cloudfoundry/cf-deployment


I also uploaded ubuntu-xenial stemcell that the cf-deployment file uses



There is a similar issue reported here



https://github.com/cloudfoundry/cloud_controller_ng/issues/1047


but I couldn't really gather the solution.



Is there a way to resolve this issue and move on ?










share|improve this question



























    0














    I am using mac OS and trying to deploy CF on virtualbox using BOSH.



    BOSH Director installed has the following details



    $ bosh -e vbox env
    Using environment '192.168.50.6' as user 'admin'

    Name bosh-lite
    UUID bbdcc68d-5390-4d08-bd80-900bf3aa3551
    Version 268.2.0 (00000000)
    CPI warden_cpi
    Features compiled_package_cache: disabled
    config_server: enabled
    local_dns: enabled
    power_dns: disabled
    snapshots: disabled
    User admin


    Bosh CLI version is



    version 5.4.0-891ff634-2018-11-14T00:21:14Z


    To deploy CF, I run the following script



    bosh -e 192.168.50.6 -d cf deploy 
    cf-deployment.yml
    -o operations/bosh-lite.yml
    -v system_domain=bosh-lite.com


    I get the following error:



    Task 33 | 15:26:34 | Updating instance diego-api: diego-api/95e076b7-0fc4-43e0-9db6-afbd8b79d76d (0) (canary) (00:20:19)
    L Error: 'diego-api/95e076b7-0fc4-43e0-9db6-afbd8b79d76d (0)' is not running after update. Review logs for failed jobs: bbs, silk-controller, locket
    Task 33 | 15:46:53 | Error: 'diego-api/95e076b7-0fc4-43e0-9db6-afbd8b79d76d (0)' is not running after update. Review logs for failed jobs: bbs, silk-controller, locket

    Task 33 Started Fri Nov 16 15:24:57 UTC 2018
    Task 33 Finished Fri Nov 16 15:46:53 UTC 2018
    Task 33 Duration 00:21:56
    Task 33 error

    Updating deployment:
    Expected task '33' to succeed but state is 'error'

    Exit code 1


    cf-deployment file and ops file (from iaas/bosh-lite/cloud-config.yml) folder) that I use are from



    https://github.com/cloudfoundry/cf-deployment


    I also uploaded ubuntu-xenial stemcell that the cf-deployment file uses



    There is a similar issue reported here



    https://github.com/cloudfoundry/cloud_controller_ng/issues/1047


    but I couldn't really gather the solution.



    Is there a way to resolve this issue and move on ?










    share|improve this question

























      0












      0








      0







      I am using mac OS and trying to deploy CF on virtualbox using BOSH.



      BOSH Director installed has the following details



      $ bosh -e vbox env
      Using environment '192.168.50.6' as user 'admin'

      Name bosh-lite
      UUID bbdcc68d-5390-4d08-bd80-900bf3aa3551
      Version 268.2.0 (00000000)
      CPI warden_cpi
      Features compiled_package_cache: disabled
      config_server: enabled
      local_dns: enabled
      power_dns: disabled
      snapshots: disabled
      User admin


      Bosh CLI version is



      version 5.4.0-891ff634-2018-11-14T00:21:14Z


      To deploy CF, I run the following script



      bosh -e 192.168.50.6 -d cf deploy 
      cf-deployment.yml
      -o operations/bosh-lite.yml
      -v system_domain=bosh-lite.com


      I get the following error:



      Task 33 | 15:26:34 | Updating instance diego-api: diego-api/95e076b7-0fc4-43e0-9db6-afbd8b79d76d (0) (canary) (00:20:19)
      L Error: 'diego-api/95e076b7-0fc4-43e0-9db6-afbd8b79d76d (0)' is not running after update. Review logs for failed jobs: bbs, silk-controller, locket
      Task 33 | 15:46:53 | Error: 'diego-api/95e076b7-0fc4-43e0-9db6-afbd8b79d76d (0)' is not running after update. Review logs for failed jobs: bbs, silk-controller, locket

      Task 33 Started Fri Nov 16 15:24:57 UTC 2018
      Task 33 Finished Fri Nov 16 15:46:53 UTC 2018
      Task 33 Duration 00:21:56
      Task 33 error

      Updating deployment:
      Expected task '33' to succeed but state is 'error'

      Exit code 1


      cf-deployment file and ops file (from iaas/bosh-lite/cloud-config.yml) folder) that I use are from



      https://github.com/cloudfoundry/cf-deployment


      I also uploaded ubuntu-xenial stemcell that the cf-deployment file uses



      There is a similar issue reported here



      https://github.com/cloudfoundry/cloud_controller_ng/issues/1047


      but I couldn't really gather the solution.



      Is there a way to resolve this issue and move on ?










      share|improve this question













      I am using mac OS and trying to deploy CF on virtualbox using BOSH.



      BOSH Director installed has the following details



      $ bosh -e vbox env
      Using environment '192.168.50.6' as user 'admin'

      Name bosh-lite
      UUID bbdcc68d-5390-4d08-bd80-900bf3aa3551
      Version 268.2.0 (00000000)
      CPI warden_cpi
      Features compiled_package_cache: disabled
      config_server: enabled
      local_dns: enabled
      power_dns: disabled
      snapshots: disabled
      User admin


      Bosh CLI version is



      version 5.4.0-891ff634-2018-11-14T00:21:14Z


      To deploy CF, I run the following script



      bosh -e 192.168.50.6 -d cf deploy 
      cf-deployment.yml
      -o operations/bosh-lite.yml
      -v system_domain=bosh-lite.com


      I get the following error:



      Task 33 | 15:26:34 | Updating instance diego-api: diego-api/95e076b7-0fc4-43e0-9db6-afbd8b79d76d (0) (canary) (00:20:19)
      L Error: 'diego-api/95e076b7-0fc4-43e0-9db6-afbd8b79d76d (0)' is not running after update. Review logs for failed jobs: bbs, silk-controller, locket
      Task 33 | 15:46:53 | Error: 'diego-api/95e076b7-0fc4-43e0-9db6-afbd8b79d76d (0)' is not running after update. Review logs for failed jobs: bbs, silk-controller, locket

      Task 33 Started Fri Nov 16 15:24:57 UTC 2018
      Task 33 Finished Fri Nov 16 15:46:53 UTC 2018
      Task 33 Duration 00:21:56
      Task 33 error

      Updating deployment:
      Expected task '33' to succeed but state is 'error'

      Exit code 1


      cf-deployment file and ops file (from iaas/bosh-lite/cloud-config.yml) folder) that I use are from



      https://github.com/cloudfoundry/cf-deployment


      I also uploaded ubuntu-xenial stemcell that the cf-deployment file uses



      There is a similar issue reported here



      https://github.com/cloudfoundry/cloud_controller_ng/issues/1047


      but I couldn't really gather the solution.



      Is there a way to resolve this issue and move on ?







      bosh cloud-foundry-bosh






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 16 '18 at 16:12









      Ray S

      155




      155
























          1 Answer
          1






          active

          oldest

          votes


















          0














          I had the same issue and found this github issue



          To fix it I executed:



          bosh update-runtime-config bosh-deployment/runtime-configs/dns.yml --name dns



          I hope this fixes your problem as well ;)






          share|improve this answer





















          • Is there a way to ssh in to the VM created on virtualbox by bosh and check the logs ? I tried to use admin as username and admin_password in creds.yml but that didn't work.
            – Ray S
            Nov 20 '18 at 6:04










          • You can use a jumpbox. You have to create your environment with jumpbox user enabled ` -o ~/workspace/bosh-deployment/jumpbox-user.yml` bosh-lite on Virtualbox and then follow the Enabling SSH Access guide. Than check the Using Logs and bosh cli log command
            – Jovan Kostovski
            Nov 20 '18 at 9:52












          • so once i have deployed cf on a virtualbox using bosh, how do i push an app in cf? Are there any special instructions around that somewhere ? I was also not able to enable ssh access. I didn't like the key that i interpolated from creds.yml and gave a warning "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! "
            – Ray S
            Nov 21 '18 at 6:31












          • check your ~/.ssh/known_hosts file, delete the key from the bosh vm and try to enable ssh access once again. There are many tutorials in the web on how to deploy an app you will find one that will work for you ;)
            – Jovan Kostovski
            Nov 21 '18 at 8:39










          • what do you mean when you say delete the key from bosh vm? I didn't quite follow that.
            – Ray S
            Nov 23 '18 at 18:18











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53341624%2ferror-deploying-cf-on-virtualbox-using-bosh%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          I had the same issue and found this github issue



          To fix it I executed:



          bosh update-runtime-config bosh-deployment/runtime-configs/dns.yml --name dns



          I hope this fixes your problem as well ;)






          share|improve this answer





















          • Is there a way to ssh in to the VM created on virtualbox by bosh and check the logs ? I tried to use admin as username and admin_password in creds.yml but that didn't work.
            – Ray S
            Nov 20 '18 at 6:04










          • You can use a jumpbox. You have to create your environment with jumpbox user enabled ` -o ~/workspace/bosh-deployment/jumpbox-user.yml` bosh-lite on Virtualbox and then follow the Enabling SSH Access guide. Than check the Using Logs and bosh cli log command
            – Jovan Kostovski
            Nov 20 '18 at 9:52












          • so once i have deployed cf on a virtualbox using bosh, how do i push an app in cf? Are there any special instructions around that somewhere ? I was also not able to enable ssh access. I didn't like the key that i interpolated from creds.yml and gave a warning "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! "
            – Ray S
            Nov 21 '18 at 6:31












          • check your ~/.ssh/known_hosts file, delete the key from the bosh vm and try to enable ssh access once again. There are many tutorials in the web on how to deploy an app you will find one that will work for you ;)
            – Jovan Kostovski
            Nov 21 '18 at 8:39










          • what do you mean when you say delete the key from bosh vm? I didn't quite follow that.
            – Ray S
            Nov 23 '18 at 18:18
















          0














          I had the same issue and found this github issue



          To fix it I executed:



          bosh update-runtime-config bosh-deployment/runtime-configs/dns.yml --name dns



          I hope this fixes your problem as well ;)






          share|improve this answer





















          • Is there a way to ssh in to the VM created on virtualbox by bosh and check the logs ? I tried to use admin as username and admin_password in creds.yml but that didn't work.
            – Ray S
            Nov 20 '18 at 6:04










          • You can use a jumpbox. You have to create your environment with jumpbox user enabled ` -o ~/workspace/bosh-deployment/jumpbox-user.yml` bosh-lite on Virtualbox and then follow the Enabling SSH Access guide. Than check the Using Logs and bosh cli log command
            – Jovan Kostovski
            Nov 20 '18 at 9:52












          • so once i have deployed cf on a virtualbox using bosh, how do i push an app in cf? Are there any special instructions around that somewhere ? I was also not able to enable ssh access. I didn't like the key that i interpolated from creds.yml and gave a warning "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! "
            – Ray S
            Nov 21 '18 at 6:31












          • check your ~/.ssh/known_hosts file, delete the key from the bosh vm and try to enable ssh access once again. There are many tutorials in the web on how to deploy an app you will find one that will work for you ;)
            – Jovan Kostovski
            Nov 21 '18 at 8:39










          • what do you mean when you say delete the key from bosh vm? I didn't quite follow that.
            – Ray S
            Nov 23 '18 at 18:18














          0












          0








          0






          I had the same issue and found this github issue



          To fix it I executed:



          bosh update-runtime-config bosh-deployment/runtime-configs/dns.yml --name dns



          I hope this fixes your problem as well ;)






          share|improve this answer












          I had the same issue and found this github issue



          To fix it I executed:



          bosh update-runtime-config bosh-deployment/runtime-configs/dns.yml --name dns



          I hope this fixes your problem as well ;)







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 19 '18 at 16:05









          Jovan Kostovski

          5016




          5016












          • Is there a way to ssh in to the VM created on virtualbox by bosh and check the logs ? I tried to use admin as username and admin_password in creds.yml but that didn't work.
            – Ray S
            Nov 20 '18 at 6:04










          • You can use a jumpbox. You have to create your environment with jumpbox user enabled ` -o ~/workspace/bosh-deployment/jumpbox-user.yml` bosh-lite on Virtualbox and then follow the Enabling SSH Access guide. Than check the Using Logs and bosh cli log command
            – Jovan Kostovski
            Nov 20 '18 at 9:52












          • so once i have deployed cf on a virtualbox using bosh, how do i push an app in cf? Are there any special instructions around that somewhere ? I was also not able to enable ssh access. I didn't like the key that i interpolated from creds.yml and gave a warning "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! "
            – Ray S
            Nov 21 '18 at 6:31












          • check your ~/.ssh/known_hosts file, delete the key from the bosh vm and try to enable ssh access once again. There are many tutorials in the web on how to deploy an app you will find one that will work for you ;)
            – Jovan Kostovski
            Nov 21 '18 at 8:39










          • what do you mean when you say delete the key from bosh vm? I didn't quite follow that.
            – Ray S
            Nov 23 '18 at 18:18


















          • Is there a way to ssh in to the VM created on virtualbox by bosh and check the logs ? I tried to use admin as username and admin_password in creds.yml but that didn't work.
            – Ray S
            Nov 20 '18 at 6:04










          • You can use a jumpbox. You have to create your environment with jumpbox user enabled ` -o ~/workspace/bosh-deployment/jumpbox-user.yml` bosh-lite on Virtualbox and then follow the Enabling SSH Access guide. Than check the Using Logs and bosh cli log command
            – Jovan Kostovski
            Nov 20 '18 at 9:52












          • so once i have deployed cf on a virtualbox using bosh, how do i push an app in cf? Are there any special instructions around that somewhere ? I was also not able to enable ssh access. I didn't like the key that i interpolated from creds.yml and gave a warning "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! "
            – Ray S
            Nov 21 '18 at 6:31












          • check your ~/.ssh/known_hosts file, delete the key from the bosh vm and try to enable ssh access once again. There are many tutorials in the web on how to deploy an app you will find one that will work for you ;)
            – Jovan Kostovski
            Nov 21 '18 at 8:39










          • what do you mean when you say delete the key from bosh vm? I didn't quite follow that.
            – Ray S
            Nov 23 '18 at 18:18
















          Is there a way to ssh in to the VM created on virtualbox by bosh and check the logs ? I tried to use admin as username and admin_password in creds.yml but that didn't work.
          – Ray S
          Nov 20 '18 at 6:04




          Is there a way to ssh in to the VM created on virtualbox by bosh and check the logs ? I tried to use admin as username and admin_password in creds.yml but that didn't work.
          – Ray S
          Nov 20 '18 at 6:04












          You can use a jumpbox. You have to create your environment with jumpbox user enabled ` -o ~/workspace/bosh-deployment/jumpbox-user.yml` bosh-lite on Virtualbox and then follow the Enabling SSH Access guide. Than check the Using Logs and bosh cli log command
          – Jovan Kostovski
          Nov 20 '18 at 9:52






          You can use a jumpbox. You have to create your environment with jumpbox user enabled ` -o ~/workspace/bosh-deployment/jumpbox-user.yml` bosh-lite on Virtualbox and then follow the Enabling SSH Access guide. Than check the Using Logs and bosh cli log command
          – Jovan Kostovski
          Nov 20 '18 at 9:52














          so once i have deployed cf on a virtualbox using bosh, how do i push an app in cf? Are there any special instructions around that somewhere ? I was also not able to enable ssh access. I didn't like the key that i interpolated from creds.yml and gave a warning "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! "
          – Ray S
          Nov 21 '18 at 6:31






          so once i have deployed cf on a virtualbox using bosh, how do i push an app in cf? Are there any special instructions around that somewhere ? I was also not able to enable ssh access. I didn't like the key that i interpolated from creds.yml and gave a warning "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! "
          – Ray S
          Nov 21 '18 at 6:31














          check your ~/.ssh/known_hosts file, delete the key from the bosh vm and try to enable ssh access once again. There are many tutorials in the web on how to deploy an app you will find one that will work for you ;)
          – Jovan Kostovski
          Nov 21 '18 at 8:39




          check your ~/.ssh/known_hosts file, delete the key from the bosh vm and try to enable ssh access once again. There are many tutorials in the web on how to deploy an app you will find one that will work for you ;)
          – Jovan Kostovski
          Nov 21 '18 at 8:39












          what do you mean when you say delete the key from bosh vm? I didn't quite follow that.
          – Ray S
          Nov 23 '18 at 18:18




          what do you mean when you say delete the key from bosh vm? I didn't quite follow that.
          – Ray S
          Nov 23 '18 at 18:18


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53341624%2ferror-deploying-cf-on-virtualbox-using-bosh%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          MongoDB - Not Authorized To Execute Command

          in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith

          How to fix TextFormField cause rebuild widget in Flutter