Skip to content

Invalid metadata in OpenStack instance #9086

@zetaab

Description

@zetaab

I am trying 1.18.0 alpha 3 release and creating instances:

Bad request with: [POST https://exxx.13774/v2.1/servers], error message: {"badRequest": {"message": "Invalid input for field/attribute metadata. Value: {u'kopsGroupName': u'master-zone-3-1', u'k8s': u'clusterospr-0502de.k8s.local', u'KopsRole': u'Master', u'k8s.io/cluster-autoscaler/node-template/label/kops.k8s.io/instancegroup': u'master-zone-3-1', u'cluster_generation': u'0', u'k8s.io/role/master': u'1', u'ig_generation': u'0', u'kops.k8s.io/instancegroup': u'master-zone-3-1', u'KubernetesCluster': u'clusterospr-0502de.k8s.local', u'KopsInstanceGroup': u'master-zone-3-1', u'KopsNetwork': u'clusterospr-0502de.k8s.local'}. u'k8s.io/cluster-autoscaler/node-template/label/kops.k8s.io/instancegroup', u'k8s.io/role/master', u'kops.k8s.io/instancegroup' do not match any of the regexes: '^[a-zA-Z0-9-_:. ]{1,255}$'", "code": 400}}

cc @mitch000001 that PR that you made broke this..

and this is now backported to all releases

problem PRs
#8999
#9001
#9013

It is impossible to use any latest kops version with openstack

versions affected:
v1.18.0-alpha.3
v1.17.0-beta.2
v1.16.2

/kind bug
/priority critical-urgent

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions