Skip to content
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

Openstack: Error filling in template monit' for cell_z1/0' #66

Closed
jhiemer opened this issue Aug 5, 2015 · 7 comments
Closed

Openstack: Error filling in template monit' for cell_z1/0' #66

jhiemer opened this issue Aug 5, 2015 · 7 comments

Comments

@jhiemer
Copy link

jhiemer commented Aug 5, 2015

When I try to deploy diego besides bosh on Openstack I get the following error:

https://gist.github.com/jhiemer/4be4bbb61c71994ea7d4

The big problem is that I don't find any logs under /var/vcap/sys/log I could start debugging from. Did the logging directory change?

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/100663578.

@emalm
Copy link
Member

emalm commented Aug 5, 2015

Hi, @jhiemer,

It looks like your gist has only a snippet of the error you received. Could you provide more of the error output?

Also, what versions of CF and Diego are you deploying together? Are you using the manifest-generation scripts in the cf-release and diego-release repos, with those repos checked out to the same versions as the releases, or are you creating your manifests by some other mechanism? What stemcell are you using, and what version of the BOSH director is deployed?

Thanks,
Eric, CF Runtime Diego PM

@jhiemer
Copy link
Author

jhiemer commented Aug 5, 2015

Hi @ematpl,
here the complete gist: https://gist.github.com/jhiemer/88a721081a384d04310f

Repos are checked out according to the release details.

ubuntu@cf-jumphost:~$ bosh releases
Acting as user 'admin' on 'microbosh-openstack'

+---------------------+-----------------+-------------+
| Name                | Versions        | Commit Hash |
+---------------------+-----------------+-------------+
| cf                  | 212+dev.1       | b30e0fd5+   |
|                     | 212+dev.2       | b30e0fd5+   |
|                     | 212+dev.3*      | b30e0fd5+   |
| cf-services-contrib | 6*              | 57fd2098+   |
| diego               | 0.1304.0+dev.1* | 6e2004e6+   |
|                     | 0.1304.0+dev.2* | 6e2004e6+   |
|                     | 0.1304.0+dev.3* | 6e2004e6+   |
|                     | 0.1304.0+dev.4* | 6e2004e6+   |
|                     | 0.1304.0+dev.5* | 6e2004e6+   |
|                     | 0.1304.0+dev.6* | 6e2004e6+   |
+---------------------+-----------------+-------------+
ubuntu@cf-jumphost:~$ bosh stemcells
Acting as user 'admin' on 'microbosh-openstack'

+-------------------------------------------+----+---------+--------------------------------------+
| Name                                      | OS | Version | CID                                  |
+-------------------------------------------+----+---------+--------------------------------------+
| bosh-openstack-kvm-ubuntu-trusty-go_agent |    | 3019*   | 6dab2a39-fb60-433f-9073-0d90f0e4ed86 |
+-------------------------------------------+----+---------+--------------------------------------+

(*) Currently in-use

Stemcell of micro_bosh according to the version numbers above.

Thanks for your help,
Johannes

@Amit-PivotalLabs
Copy link

The

undefined method `[]' for #<OpenStruct...

seems weird. Looks like the [] method for OpenStruct is in Ruby 2+, but not in 1.9.3.

Compare:

http://ruby-doc.org/stdlib-2.0.0/libdoc/ostruct/rdoc/OpenStruct.html
http://ruby-doc.org/stdlib-1.9.3/libdoc/ostruct/rdoc/OpenStruct.html

@jhiemer
Copy link
Author

jhiemer commented Aug 5, 2015

The installed version of the cell_z1 0 node is currently 1.9.3. By installing 2+ you think this error should disappear?

@emalm
Copy link
Member

emalm commented Aug 26, 2015

Hi, @jhiemer,

I saw you had a post on cf-dev linking to your write-up at http://www.evoila.de/cloud-foundry/adding-diego-release-to-cloud-foundry-release-v212/, so sounds like you did get Diego 0.1304.0 to deploy successfully alongside CF v212. Since you didn't mention anything about this error, were you able to resolve it?

Thanks,
Eric

@jhiemer
Copy link
Author

jhiemer commented Aug 26, 2015

Yes, should have closed the issue. Please excuse.

@jhiemer jhiemer closed this as completed Aug 26, 2015
tas-runtime-bot added a commit that referenced this issue Apr 8, 2024
…n grootfs guardian idmapper

Submodule src/code.cloudfoundry.org/buildpackapplifecycle 548887f17..530b1b9ab:
  > Merge pull request #66 from cloudfoundry/update-dev-tools
Submodule src/code.cloudfoundry.org/credhub-cli 7d037f0eb..41a93a2e6:
  > Bump go modules
Submodule src/code.cloudfoundry.org/routing-api 8d0a58ac5..ef1509a3e:
  > Sync .github dir templates
  > Sync .github dir templates
  > Sync .github dir templates
Submodule src/code.cloudfoundry.org/routing-info 3a6d4ccb3..449674f04:
  > Sync .github dir templates
  > Sync .github dir templates
  > Sync .github dir templates
Submodule src/garden 9e27b1d0e..4b258b482:
  > Sync .github dir templates
  > Update go.mod dependencies
  > Update go.mod dependencies
Submodule src/grootfs db4251a80..bef9152fc:
  > Update go.mod dependencies
  > Sync .github dir templates
  > Update go.mod dependencies
  > Update go.mod dependencies
Submodule src/guardian 6e87a0a1d..c85edc94b:
  > Update go.mod dependencies
  > Sync .github dir templates
  > Update go.mod dependencies
  > Update go.mod dependencies
Submodule src/idmapper 4c2924087..bc7391de6:
  > Sync .github dir templates
  > Update go.mod dependencies
  > Update go.mod dependencies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants