Bug 623189

Summary:

sesame records do not survive restart

Product:

Red Hat Enterprise MRG

Reporter:

Jan Sarenik <jsarenik>

Component:

cumin

Assignee:

Justin Ross <jross>

Status:

CLOSED ERRATA

QA Contact:

Jan Sarenik <jsarenik>

Severity:

medium

Docs Contact:

Priority:

low

Version:

Development

CC:

jross, matt

Target Milestone:

1.3

Target Release:

---

Hardware:

All

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2010-10-20 11:28:53 UTC

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Bug Depends On:

Bug Blocks:

619768

Attachments:

Description	Flags
Deepest queue listing broken	none

Description Jan Sarenik 2010-08-11 14:44:39 UTC

I thought I have reported this already but can not find it now
so I realized it was not reported...

cumin-0.1.4195-1.el5
sesame-0.7.3918-6.el5

When I restart sesame* while running cumin, a new instance** is
created while the old gets deleted seconds after the original
sesame process was shut down by init script.

  * service sesame restart
  ** in Administrator -> Inventory -> <hostname>

The graph is started over while I would expect to see a gap
but then continued graph.

This issue is probably connected to unstable IDs, bug 622522

Comment 1 Justin Ross 2010-08-11 14:50:35 UTC

The data continuity problem described above is a current issue, and it's related to but distinct from the problem described in 622522.

Note, however, that it's expected that the "sesame record" is deleted.  The unexpected part is the loss of the old sesame's historical stats.

Comment 2 Justin Ross 2010-09-06 14:50:15 UTC

This is addressed in change 4255.  The issue described in 622522 will mean that sesame's still exhibit the problem.  It should work to test instead against a queue or exchange.

Comment 3 Jan Sarenik 2010-09-07 06:42:32 UTC

Created attachment 443411 [details]
Deepest queue listing broken

Is this fix connected with the issue on the picture?
(All the queues listed there result in APPLICATION ERROR
when their links are followed.)

Comment 4 Justin Ross 2010-09-07 14:59:21 UTC

No, those two issues are not connected.

Comment 5 Jan Sarenik 2010-09-13 14:04:52 UTC

FYI: the deepest queue listing APP ERROR is bug 623162

Comment 6 Jan Sarenik 2010-09-17 07:35:22 UTC

Verified with
  cumin-0.1.4297-1.el5
  sesame-0.7.4297-1.el5