cloudfoundry-attic
cannot run `bosh-init deploy` simultaneously
bosh-init deploy fails to run if there is already a bosh-init deploy running:
Started installing CPI
Compiling package 'ruby_aws_cpi/052a28b8976e6d9ad14d3eaec6d3dd237973d800'... Finished (00:00:00)
Compiling package 'bosh_aws_cpi/deabbf731a4fedc9285324d85af6456cfa74c10c'... Finished (00:00:00)
Rendering job templates... Finished (00:00:00)
Installing packages... Finished (00:00:03)
Installing job 'cpi'... Finished (00:00:00)
Finished installing CPI (00:00:03)
Starting registry...%
Will this problem go away entirely when registry is removed?
Can registry be launched on a new port if its preferred port is already in use?
Once registry removed this would not be a problem.
Before we tell people to use this as a replacement to bosh micro we will change such that registry port is determined automatically from the pool of ephemeral ports.
Currently you can set registry port yourself in the registry section.
Sent from my iPhone
On Apr 16, 2015, at 10:05 PM, Dr Nic Williams [email protected] wrote:
bosh-init deploy fails to run if there is already a bosh-init deploy running:
Started installing CPI Compiling package 'ruby_aws_cpi/052a28b8976e6d9ad14d3eaec6d3dd237973d800'... Finished (00:00:00) Compiling package 'bosh_aws_cpi/deabbf731a4fedc9285324d85af6456cfa74c10c'... Finished (00:00:00) Rendering job templates... Finished (00:00:00) Installing packages... Finished (00:00:03) Installing job 'cpi'... Finished (00:00:00) Finished installing CPI (00:00:03)
Starting registry...%
Will this problem go away entirely when registry is removed?Can registry be launched on a new port if its preferred port is already in use?
— Reply to this email directly or view it on GitHub.
After the following story (https://www.pivotaltracker.com/story/show/93032340) registry port will be determined automatically at runtime.
scope for the story was cut down. registry will always be on port 6901 until we remove it completely.