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

OpenShift 4.16.x - can not recreate a namespace #29292

Open
n00bsi opened this issue Nov 14, 2024 · 1 comment
Open

OpenShift 4.16.x - can not recreate a namespace #29292

n00bsi opened this issue Nov 14, 2024 · 1 comment

Comments

@n00bsi
Copy link

n00bsi commented Nov 14, 2024

[provide a description of the issue]

Version

[provide output of the openshift version or oc version command]

$ oc version
Client Version: 4.16.17
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: 4.16.17
Kubernetes Version: v1.29.8+632b078

Steps To Reproduce
1. $ oc get rs,ds,job,cj,statefulset -n demo-system
No resources found in demo-system namespace.

2. $ oc new-project demo-system
Error from server: timed out waiting for the condition

Current Result

Error from server: timed out waiting for the condition

Expected Result

that the Namespace is created

Additional Information

[try to run $ oc adm diagnostics (or oadm diagnostics) command if possible]
[if you are reporting issue related to builds, provide build logs with BUILD_LOGLEVEL=5]
[consider attaching output of the $ oc get all -o json -n <namespace> command to the issue]
[visit https://docs.openshift.org/latest/welcome/index.html]

$ oc get all -o json -n longhorn-system
Warning: apps.openshift.io/v1 DeploymentConfig is deprecated in v4.14+, unavaila                                                                                                             ble in v4.10000+
{
    "apiVersion": "v1",
    "items": [],
    "kind": "List",
    "metadata": {
        "resourceVersion": ""
    }
}

How to fix this ?
Because I can create other Namespaces but only this namespace-name: demo-system is blocked...
but I needs to be there... can not use another Namespace name....

Reboot of all nodes ( step by step ) did not help

@n00bsi
Copy link
Author

n00bsi commented Nov 18, 2024

we found ...
there where some fragments after we deleted them we can recrate the namespace

Rolebindings
Roles
ServiceAccounts

Limitranges
Res. Quatas
Custom Res. Def

in YAML file remove finalizer

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

1 participant