workspace new -state fails lineage check for remote state

[jbardin]

The lineage and serial checks have become more strict, but the -state flag for workspace new now gets caught when trying to push an existing state.

The workaround for now is to create a new workspace, then use state push -force to put the desired state in place.

[fatgit]

@jbardin
terraform state push -force s3.tfstate

Failed to write state: incompatible state lineage; given 9dec780b-2b5a-402c-acc9-f97eab09a152 but want 64281297-ade7-4206-a940-546534a25f1c

Anyway, to push my tfstate, I had to change "lineage" manually to the one that was created in the new workspace in empty tfstate

[jbardin]

@fatgit

Thanks for following up. I verified this with 0.9.11, but yes, it looks like that workaround hits the same lineage check now too.

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.