Status: New
Owner: ----
New issue 914 by [email protected]: gnt-job info and list corrupted after
gnt-cluster destroy / init
http://code.google.com/p/ganeti/issues/detail?id=914
What software version are you running? Please provide the output of "gnt-
cluster --version", "gnt-cluster version", and "hspace --version".
# gnt-cluster --version
gnt-cluster (ganeti v2.10.1) 2.10.1
# gnt-cluster version
Software version: 2.10.1
Internode protocol: 2100000
Configuration format: 2100000
OS api version: 20
Export interface: 0
VCS version: (ganeti) version v2.10.1
# hspace --version
hspace (ganeti) version v2.10.1
compiled with ghc 6.12
running on linux x86_64
What distribution are you using?
debian
What steps will reproduce the problem?
1. gnt-cluster init ...
2. gnt-node add ...
3. run jobs.
4. gnt-node remove ..
5. gnt-cluster destroy ...
6. gnt-cluster init ..., gnt-node add ..., run jobs..
7. gnt-job info or gnt-job list
What is the expected output? What do you see instead?
The expected output is the most recent job information. However, we
observed that the job list and information was being reported from
/var/lib/ganeti/queue/archive/0/ (jobs from previous cluster state before
the latest gnt-cluster init) instead of /var/lib/ganeti/queue/ (jobs since
the latest gnt-cluster init). This was confusing and caused automation
failures because the expected jobs appeared to not exist after submission.
We observe that /var/lib/ganeti/queue/serial was reset across cluster
inits, but /var/lib/ganeti/queue/archive/ was not cleaned up. If there was
a monotonically increasing serial number or archive directory was cleaned
up, then the job list will not cause confusion.
This bug is a request for gnt-cluster init / destroy / init to leave the
system in a consistent state.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
