This message was deleted.
# general
a
This message was deleted.
l
Seems to affect all non-builtin Node drivers. Just tested 3 different ones.
s
Are you provisioning RKE1 or RKE2, and which version of rancher are you coming from?
l
Trying to create RKE2 clusters
Brand new version 2.9.1 and upgraded from 2.8.4
s
Interesting. Would you be able to create an issue over at https://github.com/rancher/dashboard/issues with as much detail as you can, specifically on how to recreate the bug?
RKE1 provisioning hasn't changed in a while, but there may have been a regression RKE2 side
l
Maybe you can have a look @stocky-account-63046? Would be great!
s
Thanks, i've raised internally
l
Many thanks for the quick response!
h
I'm surprised... not 100% sure but I think I already used custom provisioning and 2.9.1 ... gotta check again
c
> Enter dummy values for
extraTagsAll
or
securityGroupIds
these are not fields consumed by RKE2, so this would be a UI or Rancher issue/
kinda sounds like there have been changes made to the struct on the rancher side that are out of sync with the non-builtin driver. ie something on the rancher machineconfig object is now an array, but the outscaleconfig object expects a string. or vice versa. Perhaps these drivers need to be updated to support rancher 2.9