bored-table-20691
06/09/2021, 1:41 AMerror: pre-step event returned an error: failed to verify snapshot: resource urn:pulumi:ssa-us-west-2::okera-infra-regions::kubernetes:yaml:ConfigFile$kubernetes:core/v1:ServiceAccount::cert-manager/cert-manager-webhook refers to unknown provider urn:pulumi:ssa-us-west-2::okera-infra-regions::pulumi:providers:kubernetes::k8s-ssa-provider::460da6b8-808b-4d03-b8f8-ee2fdc9ec693
I get this during pulumi up -f
, but same issue with if I do pulumi refresh
pulumi preview
seems to not hit the errorpulumi up
, I am in an error state:
error: the current deployment has 1 resource(s) with pending operations:
* urn:pulumi:ssa-us-west-2::okera-infra-regions::pulumi:providers:kubernetes::k8s-ssa-provider, interrupted while creating
These resources are in an unknown state because the Pulumi CLI was interrupted while
waiting for changes to these resources to complete. You should confirm whether or not the
operations listed completed successfully by checking the state of the appropriate provider.
For example, if you are using AWS, you can confirm using the AWS Console.
Once you have confirmed the status of the interrupted operations, you can repair your stack
using 'pulumi stack export' to export your stack to a file. For each operation that succeeded,
remove that operation from the "pending_operations" section of the file. Once this is complete,
use 'pulumi stack import' to import the repaired stack.
refusing to proceed
$ pulumi stack import --file stack.out
error: 2 errors occurred:
1) state file contains errors: resource urn:pulumi:ssa-us-west-2::okera-infra-regions::kubernetes:yaml:ConfigFile$kubernetes:core/v1:ServiceAccount::cert-manager/cert-manager-webhook refers to unknown provider urn:pulumi:ssa-us-west-2::okera-infra-regions::pulumi:providers:kubernetes::k8s-ssa-provider::460da6b8-808b-4d03-b8f8-ee2fdc9ec693
steep-toddler-94095
06/09/2021, 2:04 AMbored-table-20691
06/09/2021, 2:23 AMsteep-toddler-94095
06/09/2021, 2:28 AMbored-table-20691
06/09/2021, 2:29 AMsteep-toddler-94095
06/09/2021, 2:31 AMbored-table-20691
06/09/2021, 2:52 AMsteep-toddler-94095
06/09/2021, 3:08 AMpulumi up
to recreate it with the correct providerbored-table-20691
06/09/2021, 3:14 AMwhite-balloon-205
bored-table-20691
06/09/2021, 3:25 AMaws/eks
LookupCluster and manually making the kubeconfig.
2. I then made it use the kubeconfig from a pulumi-eks
cluster, and I didn’t have the ProviderCredentialOpts
setting on the cluster.
3. I did pulumi up
which gave me an error saying that it’s asking for credentials (this eks cluster is in another account than my default profile)
4. I added in ProviderCredentialOpts
, and then did pulumi up
, and from there I am in error land.
I can definitely see how something here might confuse it.
I’ve also sent the stack in DM.