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

[Bug]: cannot convert from the spoke version "v1beta1" to the hub version "v1beta2" #162

Open
1 task done
jorgelon opened this issue Oct 30, 2024 · 1 comment
Open
1 task done
Labels
bug Something isn't working needs:triage

Comments

@jorgelon
Copy link

jorgelon commented Oct 30, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Affected Resource(s)

applications.azuread.upbound.io/v1beta1 updating from provider-azuread v1.1.0 to v1.2.0 or v1.4.1

Resource MRs required to reproduce the bug

I do not know what application(s) give me that error but this is an example

apiVersion: applications.azuread.upbound.io/v1beta1
kind: Application
metadata:
  name: myappp
spec:
  forProvider:
    displayName: "whatever"
    web:
      - redirectUris:
          - "https://XXXX"
          - "https://YYYY"
      - homepageUrl: "ZZZZZZZZ"

Steps to Reproduce

run a
kubectl get applications.applications.azuread.upbound.io

What happened?

I cannot get the applications. Also kyverno shows that error

Relevant Error Output Snippet

Error from server: conversion webhook for applications.azuread.upbound.io/v1beta1, Kind=Application failed: cannot convert from the spoke version "v1beta1" to the hub version "v1beta2": cannot apply the PavedConversion for the "azuread_application" object: failed to convert the source map in mode "toEmbeddedObject" with source API version "v1beta1", target API version "v1beta2": singleton list, at the field path optionalClaims, must have a length of at most 1 but it has a length of 3

Crossplane Version

1.14, 1.15 and 1.16

Provider Version

v1.2.0 or v1.4.1

Kubernetes Version

1.29

Kubernetes Distribution

kubeadm

Additional Info

No response

@jorgelon jorgelon added bug Something isn't working needs:triage labels Oct 30, 2024
@CCOLLOT
Copy link

CCOLLOT commented Dec 2, 2024

I'm facing the same issue. Could a maintainer take a look?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs:triage
Projects
None yet
Development

No branches or pull requests

2 participants