Apply-changes fails for new products with errand config option

[kreutziger]

Hello,

when trying to deploy a new product to an OpsManager with an errand file, I get the following error:

$ om --env opsman.env.yml apply-changes --product-name p-rabbitmq --config errands.yml   

attempting to apply changes to the targeted Ops Manager
skipping errand configuration for 'cf' since it was not provided as a productName flag
skipping errand configuration for 'p-isolation-segment-alpha' since it was not provided as a productName flag
skipping errand configuration for 'p-isolation-segment-beta' since it was not provided as a productName flag
2021/06/04 11:22:40 installation failed to trigger: request failed: unexpected response from /api/v0/installations:
HTTP/1.1 422 Unprocessable Entity
[...]

8d
{"errors":["The product with guid \"p-rabbitmq-0c1565f5abd07993dba0\" cannot be found in deployed products. Has the product been deployed?"]}

If I do the same apply-changes without the errand file, the apply changes goes through:

$ om --env opsman.env.yml apply-changes --product-name p-rabbitmq   
attempting to apply changes to the targeted Ops Manager
{"type":"step_started","id":"bosh_product.deploying","description":"Installing BOSH"}
===== 2021-06-04 09:22:59 UTC Running "/usr/local/bin/bosh --no-color --non-interactive --tty create-env /var/tempest/workspaces/default/deployments/bosh.yml"
Deployment manifest: '/var/tempest/workspaces/default/deployments/bosh.yml'
Deployment state: '/var/tempest/workspaces/default/deployments/bosh-state.json'
[...]

Is that behaviour expected?

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

[jaristiz]

Hi @kreutziger,

Do we have more information about this issue that may help us debug it? Or can you provide more context?

[jaristiz]

As there was no more information on the issue I will close it, feel free to reopen it if any new information is gathered.

[markstokan]

A second customer has reported this same issue.

Specifically, the errands.yml that is being passed to om apply-changes --config contains a pre-delete errand for a new Tile that has not been deployed yet.

The error message originates in the Ops Manager code, which refuses to allow pre-delete errands to be configured during apply-changes on tiles that have not been deployed.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.