Skip to content

[BUG] Kustomizer makes Microshift to crash if manifest is not validated #208

@oglok

Description

@oglok

What happened:

Adding a set of buggy manifests to /var/lib/microshift/manifests/ and its kustomization.yaml provokes Microshift to crash.

What you expected to happen:

If a manifests has any error, don't apply it, but microshift should keep up and running.

How to reproduce it (as minimally and precisely as possible):

  1. Create a kustomization.yaml with one resource (i.e. pod.yaml)
  2. Pod.yaml must be buggy, and oc apply -f pod.yaml should not work.

Anything else we need to know?:

Environment:

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_BUGZILLA_PRODUCT_VERSION=8.4
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.4"

  • Kernel (e.g. uname -a): Linux localhost.localdomain 4.18.0-305.10.2.el8_4.x86_64 Init #1 SMP Mon Jul 12 04:43:18 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux

  • Others:

Relevant Logs

Aug 12 11:23:39 localhost.localdomain microshift[7840]: error: rawResources failed to read Resources: YAML file [klusterlet-kubeconfighub.yaml] encounters a format error.
Aug 12 11:23:39 localhost.localdomain microshift[7840]: error converting YAML to JSON: yaml: invalid map key: map[interface {}]interface {}{".kubeconfig":interface {}(nil)}
Aug 12 11:23:39 localhost.localdomain systemd[1]: microshift.service: Main process exited, code=exited, status=1/FAILURE
Aug 12 11:23:39 localhost.localdomain systemd[1]: microshift.service: Failed with result 'exit-code'.

Metadata

Metadata

Assignees

Labels

kind/bugCategorizes issue or PR as related to a bug.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions