Project

General

Profile

Actions

Bug #5422

closed

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

Added by Ivan Necas almost 10 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
API
Target version:
Difficulty:
Triaged:
Yes
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.

Actions #1

Updated by Ivan Necas almost 10 years ago

  • Status changed from New to Assigned
  • Priority changed from Normal to High
Actions #4

Updated by Ivan Necas almost 10 years ago

  • Status changed from Assigned to Ready For Testing
Actions #5

Updated by Ivan Necas almost 10 years ago

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

Applied in changeset katello|commit:1f849fbb0e4117775e3df29001ef415e35226326.

Actions #6

Updated by Eric Helms almost 10 years ago

  • Target version set to 44
Actions #7

Updated by Eric Helms almost 10 years ago

  • Triaged changed from No to Yes
Actions #8

Updated by Eric Helms over 9 years ago

  • translation missing: en.field_release set to 13
Actions

Also available in: Atom PDF