Skip to content
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

Unable to create a cubeserver #188

Closed
hoffmannmario opened this issue Mar 27, 2024 · 2 comments · Fixed by #200
Closed

Unable to create a cubeserver #188

hoffmannmario opened this issue Mar 27, 2024 · 2 comments · Fixed by #200
Labels
bug Something isn't working

Comments

@hoffmannmario
Copy link

What happened?

Hello,
I wanted to get started with the crossplane provider and started with the examples[1]. After I set everything up I wanted to create a datacenter with a cubeserver in it.
When I execute these two commands, everything seems to work as expected (yaml attached below):

$ kubectl apply -f tmpdatacenter.yaml
datacenter.compute.ionoscloud.crossplane.io/example created
$ kubectl apply -f tmpcube.yaml
cubeserver.compute.ionoscloud.crossplane.io/examplecubeserver created

The datacenter gets created correctly in the cloud, but the cubeserver does not seem to get synced. Upod further investigation I ran $ kubectl get cubeserver -o yaml, which shows me this error:

[...]
    - lastTransitionTime: "2024-03-27T09:49:41Z"
      message: |-
        create failed: failed to create cube server. error: 422 Unprocessable Entity {
          "httpStatus" : 422,
          "messages" : [ {
            "errorCode" : "200",
            "message" : "[VDC-5-1921] The attribute 'cpuFamily' must not be provided for Cube servers."
          } ]
        }
[...]

But if I leave the cpuFamily attribute out, I get another error:
"message" : "[(root).properties.cpuFamily] Attribute value '' not allowed. Expected one of [AMD_OPTERON, AMD_EPYC, INTEL_SKYLAKE, INTEL_XEON, INTEL_ICELAKE]"

How can we reproduce it?

I guess apply those yaml files?

What environment did it happen in?

Crossplane Provider IONOS Cloud version: ghcr.io/ionos-cloud/crossplane-provider-ionoscloud:latest (as of 27th march, I guess v1.0.10?)

  • Client Version: v1.29.3
  • Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
  • Server Version: v1.29.2
  • OS: Ubuntu 22.04 WSL
  • Kernel: Linux A001320623 5.15.133.1-microsoft-standard-WSL2 feat: add DBaaS Postgres cluster support [WIP] #1 SMP Thu Oct 5 21:02:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Additional Notes

datacenter.yaml:

apiVersion: compute.ionoscloud.crossplane.io/v1alpha1
kind: Datacenter
metadata:
  name: example
managementPolicies:
  - "*"
spec:
  forProvider:
    name: exampleDatacenter
    location: de/txl
    description: test
  providerConfigRef:
    name: example

cube.yaml:

apiVersion: compute.ionoscloud.crossplane.io/v1alpha1
kind: CubeServer
metadata:
  name: examplecubeserver
managementPolicies:
  - "*"
spec:
  forProvider:
    name: exampleCubeServer
    availabilityZone: AUTO
    template:
      name: 1-2-30
    volume:
      name: exampleDasVolume
      bus: VIRTIO
      licenceType: LINUX
    datacenterConfig:
      datacenterIdRef:
        name: example
  providerConfigRef:
    name: example

References

Kind regards

@hoffmannmario hoffmannmario added the bug Something isn't working label Mar 27, 2024
@cristiGuranIonos
Copy link
Contributor

THanks for creating this, we'll take a look. Was it working until this latest release, or is it a new attempt?
To note, in this latest rel version the managementpolicies moved to the spec

@hoffmannmario
Copy link
Author

It was a new attempt. I am just trying to get into the crossplane-provider. Yes, a colleague of mine told me about the spec.
I installed the provider yesterday, but just tried to update and nothing changed. I will try a complete re-run and if anything changes I will come back to you

@cbeti-ionos cbeti-ionos linked a pull request Apr 2, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants