-
Notifications
You must be signed in to change notification settings - Fork 658
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When deploying bosh on Vsphere, Prompt Cleaning up rendered CPI jobs... Finished #2463
Comments
Hi @yangdeyue-root, it seems like one of the jobs is failing to start. If you connect to the VM you can check If you don't have an easy way to get onto the VM, you can use the bosh cli to ssh to the VM: https://bosh.io/docs/cli-v2/#ssh Ssh is a bit tricky with a
Once you have those set, you can just run |
@jpalermo Hello, thank you very much for your reply. May I ask whether you are talking about ESXI log or vsphere log? I can check it here |
The logs I'm talking about are on the VM that failed to start properly. You'll need to get onto the VM to check the logs most likely. If you're unable to get onto the VM using the instructions above, you can also detach the disk from the VM and attach it to another VM you have working to read the logs from there. |
Hello, we have not found the problem. We want to use VirtualBox to install bosh and then deploy cloudfoundry on vsphere. Is this solution ok @jpalermo |
Very out of the ordinary, and you lose a lot of the HA aspects bosh gives you unless you are leaving the VirtualBox running all the time. But it is possible to deploy a bosh director VM using one CPI (in your case the VirtualBox CPI), but have that director deployed along with a different CPI (the vSphere CPI) that it will use to create VMs itself. |
As @jpalermo mentioned above you could detach the disk an look at the logs from an other VM, instructions for this can be found here: https://bosh.io/docs/tips/#unresponsive-vm-logs (from step 3 onwards). |
Thank you very much for your patient answer. Since we have just come into contact with this project and don't know much about it, I still can't connect to the vm and find out the cause of this problem. Could you please ask for more detailed operation steps |
The steps for connecting to the failed VM are here Also, @rkoster mentioned the alternative, detaching the disk from the failed VM, and attaching it to a working VM to view the logs here: https://bosh.io/docs/tips/#unresponsive-vm-logs We'd be happy to help with either set of steps, but we're not sure which part you are having trouble with. |
Hi, I think I found the log by separating the faulty vm disk, but I can't pinpoint the exact cause of the failure. |
Looks like the
So it seems like the timestamps on the generated certificates were off by 8 hours. I've never seen this problem before, but maybe make sure the ESX host has the correct time as well as wherever you are running the |
It seems that the problem is caused by different time zones. I adjusted the time zones of esxi, vsphere, and centos to UTC, and no error was reported when bosh was installed The following is the error message: Started validating Succeeded Started validating Failed to download the from 'https://bosh.io/d/github.com/cloudfoundry/os-conf-release?v=22.2.0' : Exit code 1 I see this link in the file jumpbox-user.yml name: os-conf I tried to change the link address, but failed |
If you download the file locally, you should be able to change the |
Hi, I have solved the above problems. I am currently trying to install and deploy cloudfoundry. According to the deployment of these tutorials, https://github.com/cloudfoundry/cf-deployment/blob/main/texts/deployment-guide.md, perform the BBL up, throws an error [root@localhost bosh-1]# Started validating Succeeded Started validating Started installing CPI Uploading stemcell 'bosh-vsphere-esxi-ubuntu-jammy-go_agent/1.222'... Finished (00:04:00) Started deploying Cleaning up rendered CPI jobs... Finished (00:00:00) Succeeded
Update runtime config: failed to update runtime-config: exit status 1 But it doesn't seem to affect subsequent operations, and I can perform subsequent operations until I make a mistake when I need to upload the stem cells. According to the prompt, it seems to be due to a problem with the cpi [root@localhost bosh-1]# bosh upload-stemcell bosh-stemcell-1.204-vsphere-esxi-ubuntu-bionic-go_agent.tgz [----------------------------------------------------] 100.00% 107.90 MiB/s 6.4s Task 5 | 06:34:47 | Update stemcell: Extracting stemcell archive (00:00:12) Task 5 Started Fri Sep 8 06:34:47 UTC 2023 Uploading stemcell file: Exit code 1 |
Hi @yangdeyue-root, seems like there might be some sort of problem with the vsphere configuration. Both tasks 1 and 5 failed. You can get the full logs by doing a The debug logs can be very large, but probably have some details in them. |
Based on the output, you don't see any additional prompts, just the exact cause of the error [root@bogon bosh-1]# bosh task 21 --debug Task 21 I, [2023-09-18T06:20:57.625658 #19] [0x1b9c70] INFO -- TaskHelper: Director Version: 274.1.0 Task 21 error Capturing task '21' output: Exit code 1 |
Yeah, it looks like the http client in the vSphere CPI is timing out while trying to upload the stemcell to vSphere. Does where you're running this from have access to the vCenter and the associated hosts and datastores? |
Hey @yangdeyue-root, have you had a chance to look at this again? |
Hi, I am still investigating this problem, and it has not been solved yet. I saw that ovf deployment task was submitted for execution on vsphere, but the final result was displayed as failure @jpalermo |
Yeah, I'm not sure what the error says but it does seem like there may either be some sort configuration problem in vSphere itself (maybe connectivity between ESX hosts and the datastore?), or something is wrong with the vSphere config given to the CPI (incorrect datastore or something) |
Yeah, that is true. However, when you successfully created the bosh director, the stemcell was uploaded to the datastore from when you ran the Could there be a communication problem caused by the fact that the bosh director is trying to upload the stemcell to the datastore from within the ESX host? That's not a problem I've ever seen before, but I could see a situation where connectivity from the VMs running ESX would be blocked from accessing the datstore. |
Speaking of this, I think of a problem, we have successfully deployed cloudfoundry once before, the first deployment, there are two disks on the machine, esxi system is installed in disk 1, the subsequent deployment of cloudfoundry is installed in disk 2, there was no such error at that time, during this deployment, There is only one disk, and the system and cloudfoundry are in the same disk. I don't know if it is caused by this problem. Now I am trying to mount a new disk on the machine and then try to deploy it |
Is your issue fixed? If not, could you please try the following experiment: On the VM at 10.2.160.5:
On the ESX host (10.2.162.11):
And let me know the output. This will help determine if the traffic is being blocked from the ESXi host to the VM or from the VM to the ESXi host. |
I've solved this problem by putting all the virtual machines on the same network segment so that they can be accessed from one VM to another |
[root@localhost bosh-1]# bosh create-env bosh-deployment/bosh.yml \
Deployment manifest: '/home/bosh-1/bosh-deployment/bosh.yml'
Deployment state: 'state.json'
Started validating
Downloading release 'bosh'... Finished (00:00:14)
Validating release 'bosh'... Finished (00:00:02)
Downloading release 'bpm'... Finished (00:00:14)
Validating release 'bpm'... Finished (00:00:01)
Downloading release 'bosh-vsphere-cpi'... Finished (00:00:38)
Validating release 'bosh-vsphere-cpi'... Finished (00:00:06)
Validating cpi release... Finished (00:00:00)
Validating deployment manifest... Finished (00:00:00)
Downloading stemcell... Finished (00:01:28)
Validating stemcell... Finished (00:00:17)
Finished validating (00:03:18)
Started installing CPI
Compiling package 'golang-1-darwin/a1cfad36b0071ef5a83ed91578b48ee30534f7054371bef8b54f3b5fa3034a88'... Finished (00:00:35)
Compiling package 'golang-1-linux/b09468ac73cd3350333a35eb09c980c6a06c5465be0e1ba430da62757dc10a04'... Finished (00:00:33)
Compiling package 'ruby-3.1/8b225e7cc2608305a7b784b5828b2b4b7c7adc3eb14af46e313d64a9e14a3ad6'... Finished (00:05:31)
Compiling package 'iso9660wrap/57da6c48c387379cc701856daa68f9f5269c2441d0195a0c5a735c93d6d2c489'... Finished (00:00:34)
Compiling package 'vsphere_cpi/0ed39dc9e020772257f07af9402ba9a4f8a62c7bd39f7e29e6ba99379398700e'... Finished (00:00:35)
Installing packages... Finished (00:00:12)
Rendering job templates... Finished (00:00:02)
Installing job 'vsphere_cpi'... Finished (00:00:00)
Finished installing CPI (00:08:05)
Uploading stemcell 'bosh-vsphere-esxi-ubuntu-jammy-go_agent/1.181'... Finished (00:04:12)
Started deploying
Creating VM for instance 'bosh/0' from stemcell 'sc-35792cdf-4377-440c-87e8-5af9aaa4b446'... Finished (00:00:25)
Waiting for the agent on VM 'vm-b46cf168-3d38-4683-a977-afe3ddc48111' to be ready... Finished (00:01:43)
Creating disk... Finished (00:00:10)
Attaching disk 'disk-a2189e85-869c-43ba-a151-c1e64ee6ba98' to VM 'vm-b46cf168-3d38-4683-a977-afe3ddc48111'... Finished (00:00:35)
Rendering job templates... Finished (00:00:14)
Compiling package 'golang-1-linux/29f2024e7d815be0694944c3c3c9512914a36a31d5fa1b2cbd2452c8d331ce90'... Skipped [Package already compiled] (00:00:01)
Compiling package 'director-ruby-3.2/84ee2f9d0485530a75822fa03e7fd0c73544aa4c2f6fe24aaebebe1757195efe'... Skipped [Package already compiled] (00:00:00)
Compiling package 'ruby-3.1/8b225e7cc2608305a7b784b5828b2b4b7c7adc3eb14af46e313d64a9e14a3ad6'... Finished (00:05:48)
Compiling package 'tini/3d7b02f3eeb480b9581bec4a0096dab9ebdfa4bc'... Skipped [Package already compiled] (00:00:00)
Compiling package 'bpm-runc/9f66395d85ace4b4d4908069742f7db27dc28d0a'... Skipped [Package already compiled] (00:00:00)
Compiling package 'mysql/67dc3882464cb721ac6f0c093a0b2aeb4d4f963a0c7cd6a8a6e5764f3e193293'... Skipped [Package already compiled] (00:00:00)
Compiling package 'libpq/b309a72768019e24e2c592f3f25ded2679e98cbb90f774c3a4d6b7745760079f'... Skipped [Package already compiled] (00:00:00)
Compiling package 'golang-1-darwin/a1cfad36b0071ef5a83ed91578b48ee30534f7054371bef8b54f3b5fa3034a88'... Finished (00:00:20)
Compiling package 'golang-1-linux/b09468ac73cd3350333a35eb09c980c6a06c5465be0e1ba430da62757dc10a04'... Finished (00:00:20)
Compiling package 'health_monitor/cd4d357a133796e0b6e330719d51b2368da8bf31e57d16d4e02287bf4ecef590'... Skipped [Package already compiled] (00:00:00)
Compiling package 'azure-storage-cli/069862c6e712ee894b1af3ef72a6cac5a03a83810df0cf7528786c12000f5008'... Skipped [Package already compiled] (00:00:00)
Compiling package 'davcli/c08e75b6a7335f5aee645b75cc35006674e7a0db2cd168229c5792f02d6d5d76'... Skipped [Package already compiled] (00:00:00)
Compiling package 's3cli/93ae9d812dcae6f1f924c60279365c53ddbda24b7e4bd8785b1fb9d5f9a57954'... Skipped [Package already compiled] (00:00:00)
Compiling package 'postgres-15/d60a5c68874e269beb9e2b03ea692912229bde7b0076d01f30203be6918323d2'... Skipped [Package already compiled] (00:00:00)
Compiling package 'vsphere_cpi/0ed39dc9e020772257f07af9402ba9a4f8a62c7bd39f7e29e6ba99379398700e'... Finished (00:00:29)
Compiling package 'nginx/ea3eadaa82bb9344018a8798a825b98315b1195bb1d495257f38421b0b7618a5'... Skipped [Package already compiled] (00:00:00)
Compiling package 'nats/91e42e9a8eb4420f55775f33ddcf58293481dccf1ebfe2a640992e063b02f5f1'... Skipped [Package already compiled] (00:00:00)
Compiling package 'verify_multidigest/e2cede15895902b58242b44023502380f68521af9ce68f1ed495158a97714327'... Skipped [Package already compiled] (00:00:00)
Compiling package 'bpm/a677a3b57b36b898c10f9709c9f9813da6d878f0'... Skipped [Package already compiled] (00:00:00)
Compiling package 'postgres-10/e3f2ed31116e1a0c929ae6fcdde983a9d6c000c25cafde8a784fd126e06400f9'... Skipped [Package already compiled] (00:00:00)
Compiling package 'bosh-gcscli/fc2b4b43a11fa3a6e4ac9f86ad4b750975f516371214ff04e01330f26e2a1222'... Skipped [Package already compiled] (00:00:00)
Compiling package 'postgres-13/fe1546f1a699070e23310d860d6c6ea6e61d086eb5cac3e50092cbb4368e8fa1'... Skipped [Package already compiled] (00:00:00)
Compiling package 'director/9da9955131180e1ee189d72ff5b98881706b2012bee63f78473bc513a943fec8'... Skipped [Package already compiled] (00:00:00)
Compiling package 'iso9660wrap/57da6c48c387379cc701856daa68f9f5269c2441d0195a0c5a735c93d6d2c489'... Finished (00:00:12)
Updating instance 'bosh/0'... Finished (00:00:16)
Waiting for instance 'bosh/0' to be running... Failed (00:05:03)
Failed deploying (00:15:46)
Cleaning up rendered CPI jobs... Finished (00:00:00)
Deploying:
Received non-running job state: 'failing'
Exit code 1
Now I don't know how to deal with this problem, hope to get your help
The text was updated successfully, but these errors were encountered: