Accessing to nonexistent nodes of storage model
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
watcher |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I faced the following trace in my watcher-
<email address hidden>
2018-11-05 05:00:11.032 3820664 ERROR watcher.
2018-11-05 05:00:11.032 3820664 ERROR watcher.
2018-11-05 05:00:11.032 3820664 ERROR watcher.
2018-11-05 05:00:11.032 3820664 ERROR watcher.
2018-11-05 05:00:11.032 3820664 ERROR watcher.
2018-11-05 05:00:11.032 3820664 ERROR watcher.
2018-11-05 05:00:11.032 3820664 ERROR watcher.
Looks like it tries to get node by volume_type name, not pool name.