Details
-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
4.16.0
-
None
-
Important
-
No
-
Rasputin OLM Sprint 252
-
1
-
Rejected
-
False
-
Description
Description of problem:
The latest upstream operator sdk init ansible type operator failed.
Version-Release number of selected component (if applicable):
operator-sdk version: "v1.34.0-3-g3969b9b9", commit: "3969b9b903480be2c3de877930ac12ebc705d539", kubernetes version: "v1.28.0", go version: "go1.21.4", GOOS: "linux", GOARCH: "amd64"
How reproducible:
always
Steps to Reproduce:
1.operator-sdk init --plugins=ansible.sdk.operatorframework.io/v1 --domain=my.domain
Actual results:
$operator-sdk init --plugins=ansible.sdk.operatorframework.io/v1 --domain=my.domain INFO[0000] Writing kustomize manifests for you to edit... Error: failed to initialize project: unable to scaffold with "base.ansible.sdk.operatorframework.io/v1": error updating init manifests: error updating kustomization.yaml files: remove config/default/kustomization.yaml patch and vars blocks: unable to find the content to be replaced Usage: operator-sdk init [flags]Examples: # Scaffold a project with no API ............... FATA[0000] failed to initialize project: unable to scaffold with "base.ansible.sdk.operatorframework.io/v1": error updating init manifests: error updating kustomization.yaml files: remove config/default/kustomization.yaml patch and vars blocks: unable to find the content to be replaced 2.$tree config/default/ config/default/ ├── kustomization.yaml ├── manager_auth_proxy_patch.yaml └── manager_config_patch.yaml
Expected results:
init ansible type operator success.
Additional info: