search

Azure / oms-log-analytics-firehose-nozzle

Microsoft Azure Log Analytics Nozzle
Apache License 2.0
11 stars 14 forks source link

Adds the command option to the pcf-tile manifest #19

Closed mike-carey closed 5 years ago

mike-carey commented 5 years ago

go_buildpack version: cflinuxfs2-v1.8.33 tile version: 1.3.0

Deploying the tile to our environment causes the following error in PCF:

[APP/PROC/WEB] bash: ./bin/...  No such file or directory

Fix:

  1. Rerun the errand and keep the VM alive: bosh -d $LOG_ANALYTICS_GUID run-errand deploy-all --keep-alive
  2. SSH into the VM: bosh -d $LOG_ANALYTICS_GUID ssh deploy-all
  3. Modify the /var/vcap/jobs/deploy-all/bin/run script by adding to the escaped yaml: \"command\": \"oms-log-analytics-firehose-nozzle\", as seen here
  4. Rerun the errand by hand as vcap: /var/vcap/jobs/deploy-all/bin/run
HDYA commented 5 years ago

Thanks for your feedback @mcarey-solstice

May I have more information about your environment? and does version 1.3.1 have the same problem on your environment?

and also as the product team is on vacation for Chinese new year, please expect slow response for a few days.

mike-carey commented 5 years ago

Thanks for getting back to me @HDYA ! I apologize as the release we used was actually 1.3.1. We pulled the tile from PivNet. What kind of information would you like to know about the environment?

lakshmantgld commented 5 years ago

Great @mcarey-solstice for finding out this bug and writing this fix. One Quick suggestion, for the 3rd step, \"command\":\"oms-log-analytics-firehose-nozzle\", there should not be any space between the key and value.

Kdecherf commented 5 years ago

Hello there,

I was able to reproduce the issue and the workaround (at least to temporarily unblock our pipelines). After checking deeper it may find its root cause in one go buildpack update (1.8.32 or 1.8.33).

It would be awesome to see this PR merged and released, thanks :)

HDYA commented 5 years ago

Thanks for your fix @mcarey-solstice and everyone's participation. We recently found and fixed the same issue when upgrading it to Xenial Stemcells, I'll merge your change and fix conflict later.

//Apology that I must have missed these notifications during Chinese New Year,