Project

General

Profile

Bug #5422

Every user interaction in API/CLI cause user orchestration to trigger

Added by Ivan Necas over 6 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
API
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

This leads to slower responses, as well as issues with locking when the orchestration is running.

It happens because the `user.last_logged_in` is being update every time the API is used by the user.

The fix should be not running the orchestration when this update happens.

Associated revisions

Revision 1f849fbb (diff)
Added by Ivan Necas over 6 years ago

Fixes #5422 - don't orchestrate user at login every login

Revision 59246072
Added by Ivan Necas over 6 years ago

Merge pull request #4070 from iNecas/5422

Fixes #5422 - don't orchestrate user at login every login

History

#1 Updated by Ivan Necas over 6 years ago

  • Status changed from New to Assigned
  • Priority changed from Normal to High

#4 Updated by Ivan Necas over 6 years ago

  • Status changed from Assigned to Ready For Testing

#5 Updated by Ivan Necas over 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Applied in changeset katello|commit:1f849fbb0e4117775e3df29001ef415e35226326.

#6 Updated by Eric Helms over 6 years ago

  • Target version set to 44

#7 Updated by Eric Helms over 6 years ago

  • Triaged changed from No to Yes

#8 Updated by Eric Helms about 6 years ago

  • Legacy Backlogs Release (now unused) set to 13

Also available in: Atom PDF