-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
example https://github.com/pulumi/examples/tree/master/aws-java-eks-minimal fails to run #821
Comments
Thank you for the report! I could reproduce and added a few more bits of info. If you are affected downgrading Pulumi SDK to 0.5.2 works at the moment. |
I can reproduce the bug and the fact that downgrade to 0.5.2 changes the behaviour to intended, during preview |
I am seeing the same issue when pulumi SDK id downgrade to 0.5.2 too G:\DWork\osource\cloudc\devops\pulumi\java\aws\eks>pu View Live: https://app.pulumi.com/nagkumar/eks/dev/previews/d1729b03-8d9a-42c2-bdcf-b3017d20c7cb
Diagnostics:
|
G:\DWork\osource\cloudc\devops\pulumi\java\aws\eks>pulumi about Plugins Host This project is written in java: executable='d:\Apps\Dev\langs\java\jdk\17.x\bin\java.exe' version='java 17.0.2 2022-01-18 LTS Current Stack: dev Found no resources associated with dev Found no pending operations associated with dev Backend No dependencies found Pulumi locates its logs in C:\Users\RAJANA~1\AppData\Local\Temp by default |
I had to downgrade aws to 5.12.1 as 5.13.0 was using 0.5.4 +--- com.pulumi:aws:5.13.0 still issue now is. :\DWork\osource\cloudc\devops\pulumi\java\aws\eks>pu View Live: https://app.pulumi.com/nagkumar/eks/dev/previews/ba890777-53fc-472c-9121-3c249b146204 Downloading plugin: 123.19 MiB / 123.19 MiB [=====================] 100.00% 33s
Diagnostics:
|
It works when aws version is
my dependencies are however, it gives a warning
|
However the final thing again fails G:\DWork\osource\cloudc\devops\pulumi\java\aws\eks\app>pu View Live: https://app.pulumi.com/nagkumar/eks/dev/previews/f1ad5cce-a782-4b24-9b97-974ae7a60bd5
Diagnostics: Outputs: Updating (dev) View Live: https://app.pulumi.com/nagkumar/eks/dev/updates/17
Diagnostics: pulumi:pulumi:Stack (eks-dev):
kubernetes:core/v1:ConfigMap (my-cluster-nodeAccess): Resources: Duration: 10m27s |
I tried keeping kubectl version exactly 1.22.10 same as server still the same issue Diagnostics: pulumi:pulumi:Stack (eks-dev):
kubernetes:core/v1:ConfigMap (my-cluster-nodeAccess): |
Thank you for the information and the effort. The last message looks like it might be a separate issue. This looks to me at the first glance like some kind of incompatibility between the k8s api version and the k8s client version used by the provider:
Or maybe the file that contains the CRD ( |
I have used same k8s server and k8s client still the same issue. I tried with many verstions of k8s 1.22 and 1.23 etc.. same problem. Pl. see if analysis helps.. I believe the code that is used does not explicitly create a role required, hence the default role created internally by API uses apiextensions.k8s.io/v1beta1 and hence the issue. the file that is generated is |
Indeed thanks for extra info! We will be picking up the bug in the next iteration (next couple of weeks) and will get back to you on this. |
I was not able to create a simple storage account in Azure today ( I can provide some reproducer, but I can also try to fix this in the codebase (+ I would learn more 😁). Can I pick this up today/tomorrow? (Edit) ReproducerVersions <dependencies>
<dependency>
<groupId>com.pulumi</groupId>
<artifactId>pulumi</artifactId>
<version>0.5.4</version>
</dependency>
<dependency>
<groupId>com.pulumi</groupId>
<artifactId>azure-native</artifactId>
<version>1.74.0</version>
</dependency>
</dependencies> ❯ pulumi version
v3.39.1 ❯ mvn --version
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /usr/local/Cellar/maven/3.8.6/libexec
Java version: 18.0.2.1, vendor: Homebrew, runtime: /usr/local/Cellar/openjdk/18.0.2.1/libexec/openjdk.jdk/Contents/Home
Default locale: en_PL, platform encoding: UTF-8
OS name: "mac os x", version: "12.5.1", arch: "x86_64", family: "mac" ❯ pulumi plugin ls -p
NAME KIND VERSION SIZE INSTALLED LAST USED
azure-native resource 1.74.0 264 MB 1 hour ago 1 hour ago
java language n/a n/a never (not sure why java is "never" used) Error
Java codepackage myproject;
import com.pulumi.Pulumi;
import com.pulumi.azurenative.resources.ResourceGroup;
import com.pulumi.azurenative.resources.ResourceGroupArgs;
import com.pulumi.azurenative.storage.StorageAccount;
import com.pulumi.azurenative.storage.StorageAccountArgs;
import com.pulumi.azurenative.storage.enums.AccessTier;
import com.pulumi.azurenative.storage.enums.Kind;
import com.pulumi.azurenative.storage.enums.SkuName;
import com.pulumi.azurenative.storage.inputs.SkuArgs;
import java.util.Map;
public class App {
public static void main(String[] args) {
Pulumi.run(ctx -> {
var resourceGroup = new ResourceGroup("uploader-app",
ResourceGroupArgs.builder().build()
);
var storageAccount = new StorageAccount("uploaderstorage",
StorageAccountArgs.builder()
.resourceGroupName(resourceGroup.name())
.kind(Kind.BlobStorage)
.accessTier(AccessTier.Hot)
.sku(
SkuArgs.builder()
.name(SkuName.Standard_LRS)
.build()
)
.build()
);
});
}
} |
I'm working on tests for this in ma spare time. The fix itself should be simple, but a good test is another thing ;) |
What happened?
The aws-java-eks-minimal example stopped working. Downgrading to
com.pulumi:pulumi 0.5.2
makes it work again so there is a regression introduced in the Java SDK somewhere between 0.5.2 and 0.5.3. The preview ofaws:ec2/getVpc:getVpc result
hits a null check and fails to deserialize.Steps to reproduce
Clone
pulumi/exampes
,cd aws-java-eks-minimal
andpulumi preview
Expected Behavior
It is supposed to create k8s cluster in aws
Actual Behavior
Output of
pulumi about
Additional context
mvn dependency:tree
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: