-
```
Hi
First, of course I've seen the other issue about!
But I just want to know if BOSH support is realy out of date...
No matter which distro, Jabber and Webserver I use, I always get the
followin…
-
```
Hi
First, of course I've seen the other issue about!
But I just want to know if BOSH support is realy out of date...
No matter which distro, Jabber and Webserver I use, I always get the
followin…
-
Getting the following error when testing on a bosh 1.x line:
```
• Failure [8.380 seconds]
BOSH Kit
/Users/dbell/code/src/github.com/genesis-community/bosh-genesis-kit/spec/spec_test.go:11
cp…
-
Can't seem to connect via BOSH , the error returned by JAXL is :
jaxl:219 - 2012-12-06 13:32:07 - strict mode enabled, adding exception handlers. Set 'strict'=>TRUE inside JAXL config to disable this…
-
In [this commit](https://github.com/cloudfoundry/capi-ci/commit/63016bb4baac3de604f8c08cbdb358d03f1f5a8d), the kiki `apply_latest_migrations.sh` script was switched from using proxychains to apply mig…
-
Maybe this is intentional but when using the External BOSH feature, I have to manually upload the releases from each forge in order to make service creation work. e.g.
```
$ cf cs postgresql stand…
-
After step "While still SSHed into a VM, locate the agent.json and throw some un-parseable junk in there.", we need to kill the process in order to see resurrection failed due to bad agent.json file.
-
currently the agent uses iptables to create mbus firewall rules.
as we now use cgroupv2 these rules wont work anymore.
we could add this now to the stemcell. or the agent
if we put it in the stem…
-
**Is your feature request related to a problem? Please describe.**
Changes to a deployer (say bosh director stemcell upgrade) that may trigger downtime may cause failure of bosh deployments managed…
-
```
Hi
First, of course I've seen the other issue about!
But I just want to know if BOSH support is realy out of date...
No matter which distro, Jabber and Webserver I use, I always get the
followin…