Our kimchi hosts have people constantly working on from the command line
including changing qcow2 image names (our practice is to name them
similar to the instance name so its easy to see whats up in
/var/lib/libvirt/images)
So after a while the wok error log is full of these messages.
and we often get reoccuring pink error message in the WebUI.
Is there a way to cleanout/fix/ignore the datastore
-bill
WOKOBJST0001E: Unable to find 5f48fb31-0d73-4df7-948c-02beefee83d1 in
datastore
WOKOBJST0001E: Unable to find c7d94dcb-185f-4917-9b2e-d304f5ce807b in
datastore
WOKOBJST0001E: Unable to find d7f82fc8-44dd-484f-aaf9-f4ed0de3efe3 in
datastore
WOKOBJST0001E: Unable to find f88269b8-8ca9-4689-b8aa-c7e720e3c396 in
datastore
WOKOBJST0001E: Unable to find b46491f9-4351-4b82-ad57-87568dd55f3e in
datastore
WOKOBJST0001E: Unable to find 7c34a9fd-b3b6-4894-a6f1-baf6b7099403 in
datastore
WOKOBJST0001E: Unable to find 0eb316fe-803c-4b25-9dae-522c02748e5c in
datastore
WOKOBJST0001E: Unable to find 4e5663b8-300d-4ad0-8959-ecdc489e8c71 in
datastore
WOKOBJST0001E: Unable to find 5f48fb31-0d73-4df7-948c-02beefee83d1 in
datastore
WOKOBJST0001E: Unable to find c7d94dcb-185f-4917-9b2e-d304f5ce807b in
datastore

Kimchi Dev,
I didn't want to post an issue, because I solved it, but I think it'd be
useful to post a README update on how to update Wok to to listen on all
network devices so as to be accessed outside of localhost.
I was able to do so by updating /etc/nginx/conf.d/wok.conf to change
127.0.0.1 to 0.0.0.0 and then updating semanage rules:
(on Centos 7)
sudo systemctl stop wokd
sudo systemctl stop nginx
sudo sed -ri 's/127.0.0.1/0.0.0.0/g' /etc/nginx/conf.d/wok.conf
sudo semanage port -a -t http_port_t -p tcp 8001
sudo semanage port -a -t http_port_t -p tcp 8010
sudo semanage port -m -t http_port_t -p tcp 8000
sudo systemctl start wokd
Then after accessing from another machine I had to accept the SSL
certificates first, where it redirected me to
http://127.0.0.1:8010/login.html, which was confusing. Back after going
back to https://my-kimchi-host:8001 the login page successfully loaded.
I found this confusing and couldn't find any documentation or guide. I
think others may find this information useful. Should I post this to
the issue board for feedback?
Sincerely,
Jason