Log GSA Sync events

Bug #1067453 reported by Paul Everitt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KARL3
Fix Released
Medium
Chris Rossi

Bug Description

The GSA sync script used to report events ("it's running", "it found x items", "uh oh, fail".)

With the switch to redis logging, I think we're not getting GSA events, particularly errors.

Tags: r3.102
JimPGlenn (jpglenn09)
Changed in karl3:
milestone: m120 → m121
JimPGlenn (jpglenn09)
Changed in karl3:
milestone: m121 → m122
Revision history for this message
Chris Rossi (chris-archimedeanco) wrote :

Done on master. Probably just need to test on staging.

Changed in karl3:
status: New → Fix Committed
Revision history for this message
Paul Everitt (paul-agendaless) wrote : Re: [Bug 1067453] Log GSA Sync events

Is this something that requires you to do something for the testing?

Jim, this one is NOT a ticket that we can test on karldev. Can you mark it with r3.102 so we can track it?

--Paul

On Nov 20, 2012, at 2:10 PM, Chris Rossi <email address hidden> wrote:

> Done on master. Probably just need to test on staging.
>
> ** Changed in: karl3
> Status: New => Fix Committed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1067453
>
> Title:
> Log GSA Sync events
>
> Status in KARL3:
> Fix Committed
>
> Bug description:
> The GSA sync script used to report events ("it's running", "it found x
> items", "uh oh, fail".)
>
> With the switch to redis logging, I think we're not getting GSA
> events, particularly errors.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/karl3/+bug/1067453/+subscriptions

Revision history for this message
Chris Rossi (chris-archimedeanco) wrote :

No. When deploying to staging just make sure karl, karlserve and osi are
all deployed from git rather than eggs. This should pertain to the
'develop_packages' (or something like that) in config.py.

Chris

On Tue, Nov 20, 2012 at 3:29 PM, Paul Everitt <email address hidden> wrote:

> Is this something that requires you to do something for the testing?
>
> Jim, this one is NOT a ticket that we can test on karldev. Can you mark
> it with r3.102 so we can track it?
>
> --Paul
>
> On Nov 20, 2012, at 2:10 PM, Chris Rossi <email address hidden>
> wrote:
>
> > Done on master. Probably just need to test on staging.
> >
> > ** Changed in: karl3
> > Status: New => Fix Committed
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1067453
> >
> > Title:
> > Log GSA Sync events
> >
> > Status in KARL3:
> > Fix Committed
> >
> > Bug description:
> > The GSA sync script used to report events ("it's running", "it found x
> > items", "uh oh, fail".)
> >
> > With the switch to redis logging, I think we're not getting GSA
> > events, particularly errors.
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/karl3/+bug/1067453/+subscriptions
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1067453
>
> Title:
> Log GSA Sync events
>
> Status in KARL3:
> Fix Committed
>
> Bug description:
> The GSA sync script used to report events ("it's running", "it found x
> items", "uh oh, fail".)
>
> With the switch to redis logging, I think we're not getting GSA
> events, particularly errors.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/karl3/+bug/1067453/+subscriptions
>

JimPGlenn (jpglenn09)
tags: added: r3.102
Revision history for this message
JimPGlenn (jpglenn09) wrote :

looks good

Changed in karl3:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.