Deployment fails after an initial success (ResourceConflictException)

[TomerFi]

Confirm by changing [ ] to [x] below to ensure that it's a bug:

• I've gone though the User Guide and the API reference
• I've searched for previous similar issues and didn't find any solution

Describe the bug

I deployed a Java lambda function today from a CI process using:

aws lambda publish-version --function-name ...

This worked well the first time, later on, while deploying again, I received:

An error occurred (ResourceConflictException) when calling the PublishVersion operation: The operation cannot be performed at this time. An update is in progress for resource:...

I would like to emphasize that no modifications were done to the function sources after the first deployment,
I missed any documentation stating this might be a problem.

SDK version number
AWS CLI 2.4.16.

Platform/OS/Hardware/Device
Ubuntu 20.04.3 using gh's runner.

To Reproduce (observed behavior)
Deploy one time, later on, deploy again with no modifcations.

Expected behavior
I expected the deployment process to work well, as it did at the first attempt.

Logs/output
I'm deploying from a CI process,
please let me know if the --debug flag is required for this issue resolution,
if so I'll happily update my CI process and report back.

Additional context
I think the following issue claudiajs/claudia#226 might be similar.

[TomerFi]

Adding information:
Before the failing:

aws lambda publish-version --function-name ...

I have a:

aws lambda update-function-code --function-name ...  --zip-file fileb://...

I noticed on another workflow run that this command also failed.

[tim-finnigan]

Hi @TomerFi thanks for reaching out. This looks similar to a recent issue: #6585. I think this comment may help clarify things. It references an article announcing changes to Lambda with this section worth noting:

Nothing is changing about how functions are created, updated, or operate as part of this. However, this change may impact certain workflows that attempt to invoke or modify a function shortly after a create or an update action. Before making API calls to a function that was recently created or modified, confirm it is first in the Active state, and that the LastUpdateStatus is Successful.

Can you confirm that your Lambda function is first in the Active state and that the LastUpdateStatus is Successful?

[TomerFi]

@tim-finnigan
This is the same issue I believe, I must have missed it, sorry for that!
I was using aws:states:opt-out in the description field for a while now, and I figured it got me covered.
😉

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.