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

operator installation failed when installing in a custom numeric namespace #926

Open
LukasNg opened this issue Nov 18, 2022 · 2 comments
Open

Comments

@LukasNg
Copy link

LukasNg commented Nov 18, 2022

Hi team,

Installation of operator kept failing when I tried to install in a custom numeric namespace (e.g. 123) and seems like it's being recognised as empty:

logs from pod:
I1118 15:06:01.284823 1 request.go:621] Throttling request took 1.045048932s, request: GET:https://172.21.0.1:443/apis/apps/v1?timeout=32s I1118 15:06:05.307624 1 init.go:184] Single Deployment Status: true, MultiInstance Deployment status: false, SaaS Depolyment Status: false I1118 15:06:05.317230 1 main.go:194] Creating CommonService CR in the namespace 987 E1118 15:06:05.334289 1 main.go:196] Failed to create CommonService CR: an empty namespace may not be set when a resource name is provided

and my common-service-maps configmaps:
`namespaceMapping:

  • requested-from-namespace:
    • "987"
      map-to-common-service-namespace: "987"
      defaultCsNs: ibm-common-services`

we found a workaround for now: create CommonService manually and restart the pod

please can you have a look, thank you

@LukasNg
Copy link
Author

LukasNg commented Nov 21, 2022

Update: the "workaround" above isn't really a workaround - a bunch of config maps are missing so you'd probably have to manually create all of them before next step..

@Daniel-Fan
Copy link
Contributor

Hi @LukasNg

Thank you for bring this out!
We are investigating the root cause and will fix it ASAP

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

No branches or pull requests

2 participants