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

error creating customized resource map for kustomize #1163

Closed
zmalik opened this issue Dec 11, 2019 · 1 comment · Fixed by #1234
Closed

error creating customized resource map for kustomize #1163

zmalik opened this issue Dec 11, 2019 · 1 comment · Fixed by #1234
Labels

Comments

@zmalik
Copy link
Member

zmalik commented Dec 11, 2019

What happened:
while extending an operator and including more steps/tasks I'm seeing the error in KUDO controller logs

2019/12/11 10:22:02 InstanceController: Error during execution: fatal error: default/kafka failed in deploy.deploy-cruise.deploy-cruise.cruise-control-deploy: error creating customized resource map for kustomize: <nil> is expected to be map[string]interface {}

What you expected to happen:
Give more information about the error, so operator developers can fix the issue or further debug the issue.

How to reproduce it (as minimally and precisely as possible):
use this branch https://github.com/kudobuilder/operators/tree/issue-1161 to install KUDO Kafka

kubectl kudo plan status  --instance=kafka
Plan(s) for "kafka" in namespace "default":
.
└── kafka (Operator-Version: "kafka-1.0.2" Active-Plan: "deploy")
    ├── Plan deploy (serial strategy) [FATAL_ERROR]
    │   ├── Phase deploy-kafka [COMPLETE]
    │   │   └── Step deploy (COMPLETE)
    │   └── Phase deploy-cruise [FATAL_ERROR]
    │       └── Step deploy-cruise (FATAL_ERROR)
    └── Plan not-allowed (serial strategy) [NOT ACTIVE]
        └── Phase not-allowed (serial strategy) [NOT ACTIVE]
            └── Step not-allowed (serial strategy) [NOT ACTIVE]
                └── not-allowed [NOT ACTIVE]

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version): 1.16.3
  • Kudo version (use kubectl kudo version): 0.8.0
  • Operator:
  • operatorVersion:
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@zmalik
Copy link
Member Author

zmalik commented Dec 11, 2019

the issue was caused by empty annotations
kubernetes-sigs/kustomize#1017

leaving this open, so we can close after

  • bumping kustomize depdendency
  • having more verbose logs to help operator developers to debug this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant