Bug 1459252
Summary: | journalctl on node repeats UnmountVolume operation started for volume messages | ||
---|---|---|---|
Product: | OKD | Reporter: | Phil Cameron <pcameron> |
Component: | Storage | Assignee: | Matthew Wong <mawong> |
Status: | CLOSED NOTABUG | QA Contact: | Jianwei Hou <jhou> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.x | CC: | aos-bugs, aos-storage-staff, bbennett, eparis, hchen, mawong |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-06-13 17:03:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Phil Cameron
2017-06-06 15:58:23 UTC
Phil - Can you provide more information including the dump of PVs and PVCs and any pods? There are no PV/PVC in the setup # oc get po NAME READY STATUS RESTARTS AGE docker-registry-4-2hdmp 1/1 Running 0 1h hello-rc-c9m05 1/1 Running 0 4d Looks like https://github.com/kubernetes/kubernetes/issues/45935 Fix coming to 1.7 https://github.com/kubernetes/kubernetes/commit/c6bfa43c58d7323563a128b3189e0f7d2359cfc1 This was built with: # go version go version go1.8.1 linux/amd64 how dangerous is the backport of https://github.com/kubernetes/kubernetes/pull/43878 to 3.6? Officially we will only ever build 3.6 with golang 1.7 but Phil won't be the only dev to do so... Rebuilt with go 1.7.4 still getting the journal messages. Is there some way to clean things up? The bad "deleting~...deleting~ folders to clean up should be under /var/lib/origin/pods/$POD_UID/volumes/kubernetes.io~config-map correction: /var/lib/origin/openshift.local.volumes/pods/$POD_UID/volumes/kubernetes.io~config-map This was caused by go version mismatch, manual cleanup of directories is required but resolves the issue. |