Lifecycle promotion does not work for particular lifecycle

[tothegills]

Team

• I've assigned a team label to this issue

Severity

Annoying for us

Version

2022.2.292

Latest Version

I could reproduce the problem in the latest build

What happened?

Two projects share a lifecycle configure to auto promote:

The promotions to External are not working for the OctoNotes and OctoVersion projects.

The deployment succeeded events are being process by the lifecycle promoter, but not deploying:

04:10:27   Verbose  |   Processing event block 4933858 to 4933864
04:10:27   Verbose  |   Processing automatic lifecycle promotions...
04:10:27   Verbose  |   Environments eligible for automatic release deployment: None

Reproduction

See above.

Error and Stacktrace

No response

More Information

See internal report: https://octopusdeploy.slack.com/archives/CNHBHV2BX/p1645588500813629

Workaround

Deploy manually (boo!)

[mlheureux]

Also experiencing this issue here since we updated to latest version :(

[N-lson]

Hey @mlheureux, could you check the lifecycle of the channel that the releases are part of and confirm that it's set to the expected lifecycle? We found that even though the project's default lifecycle was set to auto-deploy to both environments, the channel's lifecycle was set to a different one which only auto-deployed to the first environment. As per our docs if the lifecycle is set at the channel level it will override the project's default lifecycle.

If this isn't the case, I suggest reaching out to support@octopus.com and we'll be happy to help you further from there.

[N-lson]

Closing as it seems to have been a misconfiguration on our instance.

[mlheureux]

Hi @N-lson , I double-checked and our Channel Lifecycle is correct and should be set to auto-deploy

So there might be another configuration elsewhere that is preventing this, but so far everything I checked is ok and still not auto-deploying, we're still noticing the issue

[N-lson]

Thanks @mlheureux! It looks like those phases aren't being auto-deployed to as they're optional phases. I've raised a quick discussion internally and we've come to the conclusion that this is intentional behavior, but it's not being properly reflected in the UI or in our docs. I've raised an issue #7446 to make it clearer that optional phases are ignored when evaluating any phases for auto-deployments.

[mlheureux]

Well @N-lson that is exactly our situation and your comments helped us resolve our issue

The fact that the phases were Optional was causing the issue, just making them mandatory got us back to the expected behavior we previously had, it's all auto-deploying again !

I agree with you that this behavior makes total sense, but the UI could be a little improved to help avoid the mistake

Thanks again for your ideas and support on that one!