Skip to content

Regression in kubectl apply for TPR's in v1.4.8 #39906

@huggsboson

Description

@huggsboson

BUG REPORT
Kubernetes version (use kubectl version): v1.4.8

Environment:

  • Cloud provider or hardware configuration: Baremetal @ Box
  • OS (e.g. from /etc/os-release): ScientificLinux 6
  • Kernel (e.g. uname -a): Linux compute-master1001.ve.box.net 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Sep 15 05:09:55 CDT 2015 x86_64 x86_64 x86_64 GNU/Linux
  • Install tools:
  • Others:

What happened:
In kube v1.4.7 multiple invocations of kubectl apply -f instanceOfThirdPartyResource.yaml would succeed in v1.4.8 we get the error:

&{0xc820016d80 0xc82013bea0 user-dev pki-95c36eb44c4a9132082142f7d5e47bf0 /box/deployment-config/release/dsv31/dev/user/app.json &TypeMeta{Kind:,APIVersion:extensions/v1beta1,} &TypeMeta{Kind:,APIVersion:extensions/v1beta1,} 178335915 false}
for: "/box/deployment-config/release/dsv31/dev/user/app.json": error when getting instance of versioned object for box-pki.com/v1, Kind=Pki: "/box/deployment-config/release/dsv31/dev/user/app.json": no kind "Pki" is registered for version "box-pki.com/v1"

What you expected to happen:
Would expect it to succeed. (Though maybe not actually apply changes).

How to reproduce it (as minimally and precisely as possible):
Make a thirdpartyresource make an instance of it. And apply that multiple times on 1.4.8. Sorry I can't share our manifests. I'll try to get another person at Box to produce a test case.

Anything else do we need to know:
We believe the regression was introduced in:
261cdcc

@pwittrock @ymqytw @ahakanbaba

Metadata

Metadata

Assignees

No one assigned

    Labels

    sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions