Issue type: Bug
Reported in: Microclimate 18.10
Internal issue: iterative-dev issue 221
Fixed in:
Description of issue:
After a long period of heavy use on IBM Cloud Private 3.1.1, inotify might fail to start in file watcher. A message appears that says, "Couldn't initialize inotify" in the file watcher logs. After this message appears, updates are not detected on projects, including projects that are currently running.
Workaround:
To fix this known issue with inotifywait on Kubernetes 1.11.3, restart the worker node that File Watcher is running on. After the restart, inotify works properly again, and you can update projects.
Status updates:
Issue type: Bug
Reported in: Microclimate 18.10
Internal issue: iterative-dev issue 221
Fixed in:
Description of issue:
After a long period of heavy use on IBM Cloud Private 3.1.1, inotify might fail to start in file watcher. A message appears that says, "Couldn't initialize inotify" in the file watcher logs. After this message appears, updates are not detected on projects, including projects that are currently running.
Workaround:
To fix this known issue with inotifywait on Kubernetes 1.11.3, restart the worker node that File Watcher is running on. After the restart, inotify works properly again, and you can update projects.
Status updates: