Concourse Deploy fails with "Error: Instance group 'web' with network '<network>' declares static ip '###.###.###.###', which belongs to no subnet:"
search cancel

Concourse Deploy fails with "Error: Instance group 'web' with network '<network>' declares static ip '###.###.###.###', which belongs to no subnet:"

book

Article ID: 404147

calendar_today

Updated On:

Products

Services Suite Concourse for VMware Tanzu

Issue/Introduction

During a Concourse deployment task with BOSH, the following error is encountered:

Error: Instance group 'web' with network '<NETWORK_NAME>' declares static ip '###.###.###.###', which belongs to no subnet

Environment

Concourse deployed on Bosh might encounter this failure. 

Cause

This failure occurs due to a mismatch in the configured concourse.yml 'static_ips' and the cloud-config.yml 'static' IP configuration. The concourse.yml is expecting a static IP assigned, but the BOSH cloud config is not configured to provide it.

Resolution

When the 'static_ips' field is configured in the networks section of the concourse.yml file, the cloud-config.yml must also contain a 'static' field in the networks section.

To resolve this:

  1. bosh cloud-config > cloud-config.yml
  2. Under the "static" section, add the web IP mentioned in the error. Place it within the [].
  3. Update with bosh update-cloud-config cloud-config.yml
  4. Then deployed concourse again.

Reference the following Concourse documentation which details that the Static IP's in the cloud-config should not be configured under the Reserved field.

If you face any problems with these steps, please contact support.