I have a packaging file (autoconf) that looks like this:

# abort script on any command that exits with a non zero value
set -e
set -x

PREFIX=${BOSH_INSTALL_TARGET}

export PATH=$PATH:${BOSH_INSTALL_TARGET}/bin:/var/vcap/
packages/dynomite1/bin

tar xvf autoconf/autoconf.tar.gz
(
set -e
cd autoconf-2.69
autoconf_dir=$PREFIX/share/autoconf ./configure --prefix=$PREFIX
make
make install prefix=$PREFIX
)

------------------------------------------------------------
------------------------------------
Then I have another packaging file (Dynomite) that looks like this:

# abort script on any command that exit with a non zero value
set -e
set -x

PREFIX=${BOSH_INSTALL_TARGET}

tar xvf dynomite1/dynomite.tar.gz
(
set -e
cd dynomite

autoreconf -fvi
CFLAGS="-ggdb3 -O0" ./configure --enable-debug=full --prefix=$PREFIX
make
make install prefix=$PREFIX
)
------------------------------------------------------------
--------------------------------------------------
Dynomite has a spec file that looks like this:

---
name: dynomite1
dependencies:
- autoconf
- libtool
files:
- dynomite1/dynomite*
------------------------------------------------------------
-------------------------------------------------------------
Dynomite depends on autoconf, as it uses the autoreconf command. When
building the packages, the autoreconf command fails, as I get the following
error:

"packaging: line 12: autoreconf: command not found"
------------------------------------------------------------
---------------------------------------------------------------

What might I be doing wrong?

Hello all

I am having a VM which is recreated often under one testing.
I was trying to check what causes the recreation but I got no clue yet.

If there are any hint how to check this?

On Aug 24, 2016, at 3:39 PM, Neil Watson <neil(a)watson-wilson.ca> wrote:

What does this error mean and how can I fix it?

Starting registry... Finished (00:00:00)
Uploading stemcell 'bosh-vsphere-esxi-ubuntu-trusty-go_agent/3262.5'... Failed (00:00:08)
Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)

Command 'deploy' failed:
creating stemcell (bosh-vsphere-esxi-ubuntu-trusty-go_agent 3262.5):
CPI 'create_stemcell' method responded with error: CmdError{"type":"Bosh::Clouds::CloudError","message":"No valid placement found for disks:\n- Size: 528, Target DS Pattern: /datastore[1-8]/, Current Location: N/A\n\nPossible placement options:\n- Cluster name: BOSH_CL\n Datastores:\n - Name: datastore1, free space: 1774121\n - Name: datastore8, free space: 1605822\n - Name: datastore7, free space: 1802097\n - Name: datastore5, free space: 1787646\n - Name: datastore4, free space: 635180\n - Name: datastore3, free space: 196208\n - Name: datastore2, free space: 611371\n - Name: datastore6, free space: 1170125\n\n","ok_to_retry":false}

Thanks Ronak. It worked. I have declared those properties and deployment
manifest got generated.
However when I tried to deploy most of the vms got deployed but consul
failed resulting in deployment error
Director task 302
Deprecation: Ignoring cloud config. Manifest contains 'networks' section.

Started preparing deployment > Preparing deployment. Done (00:00:01)

Started preparing package compilation > Finding packages to compile.
Done (00:00:00)

Started updating job consul_z1 > consul_z1/0 (xxxxxxxx) (canary).
Failed: 'consul_z1/0 (xxxxxx)' is not running after update. Review logs for
failed jobs: consul_agent (00:10:36)

Error 400007: 'consul_z1/0 (xxx)' is not running after update. Review logs
for failed jobs: consul_agent

The logs under /var/vcap/sys/log indicate "error parsing any
certificates"...I checked many times the consul certificates t but couldn't
figure out the issue.......I used certstarp to generate self signed certs
with an encrypted key...Do I need to declare any additional properties in
consul for my deployment manifest before doing bosh deploy? or is it purely
syntax related issue?

I was trying to deploy cloud foundry on vsphere. After creating stub file
and running script to generate deployment manifest I ran in to this error.

error generating manifest: unresolved nodes:
(( .properties.cc.external_port )) in /home/ssanke001c/cf-release/templates/cf.yml
jobs.[9].properties.route_registrar.routes.[0].port
(( .properties.nats.machines )) in /home/ssanke001c/cf-release/templates/cf.yml
properties.etcd_metrics_server.nats.machines
(( .properties.cc.external_port )) in
/home/ssanke001c/cf-release/templates/cf.yml meta.api_routes.[0].port

However I made a force deployment ignoring the above errors. As a result
deployment failed.
Also, I had seen few more errors related to unresolved nodes (static
ips). Because the cf.yml assumes two networks cf1,cf2. I have only cf1. I
configured the cf-infrastructure-vsphere.yml and cf.yml from templates by
removing jobs associated with cf2. I was able fix that issue. Can someone
help me to get an understanding of how to deal with external port related
issues and route registrar and how to configure them in my deployment
manifest? thanks in advance.