rancher: Bug: Project shows "Cluster not ready"

What kind of request is this (question/bug/enhancement/feature request): Bug

Steps to reproduce (least amount of steps as possible): Unknown, happened after an upgrade. Unable to reproduce

Result:

Other details that may be helpful: The issue is related to DefaultNetworkPolicyCreated in API being set to unknown.

"lastUpdateTime": "2020-05-14T06:40:41Z",
"status": "Unknown",
"type": "DefaultNetworkPolicyCreated"

Previously it was possible to delete projectnetworkpolicies,cattle,io for the project in question and then force a sync by editing the project’s description which would fix the unknown status. In two other instances where this was seen however this didn’t fix it. Instead it came back as unknown.

kubectl delete projectnetworkpolicies.management.cattle.io -n p-69fs2

At the moment the only workaround is to delete the Unknown status directly from the project which will fix the UI although the underlying bug still exists.

kubectl get projects.management.cattle.io -A
kubectl get projects.management.cattle.io -n local p-ldn9h -o yaml > backup.yaml
kubectl edit projects.management.cattle.io -n local p-ldn9h

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.4.3
Installation option (single install/HA): HA

gz#11059 gz#11056 gz#11206 gz#10305 gz#12204 gz#13165 gz#13547

gz#14814

gz#14959

gz#15932

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 4
Comments: 18 (4 by maintainers)

Most upvoted comments

Hi @hcouplet and @chrisgelhaus

The commands from @patrick0057 need to be applied on the local Rancher cluster itself (not on the Rancher managed ones). We were able to fix it using the commands down here:

kubectl get projects.management.cattle.io -A 
kubectl get projects.management.cattle.io -n c-rsabc p-8r123 -o yaml > ~/Temp/backup.yaml
# Remove the whole entry with status "Unknown":
kubectl edit projects.management.cattle.io -n c-rsabc p-8r123

For me the regarding project object was inside another namespace (p-8r123) and not inside local as @patrick0057 wrote.

Hope this helps! If not please comment again. I hope Rancher fixes this issue soon (we opened a ticket via their support).

Regards, Philip

PhilipSchmid on Sep 24, 2020