Project

General

Profile

Actions

Bug #32320

closed

"Current organization has no manifest imported" error when trying to import a manifest

Added by Jeremy Lenz almost 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Subscriptions
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

In a fresh org after performing a rake katello:reset, I tried to import a manifest from one of my old manifest files.

Actual behavior:
1. The task succeeded in about 3 seconds
2. I received a toast error notification "Current organization has no manifest imported"
3. If I look at the manifest import task's Dynflow console, in the Actions::Candlepin::Owner::Import (success) sub-action, I see the following:


state: FAILED
  previousState: RUNNING
  startTime: '2021-04-14T21:57:27+0000'
  endTime: '2021-04-14T21:57:27+0000'
  attempts: 1
  maxAttempts: 1
  statusPath: "/jobs/4028faf478d221d40178d2639c98359e" 
  resultData: 'Import is older than existing data The following conflicts were found:
    [ MANIFEST_OLD ]'

I think this may be related to the recent change to the async manifest import API. We used to surface this error ('Import is older than existing data') directly to the user, but now it's buried.

Expected behavior: The above error should cause a failed import task and inform the user.

Actions #1

Updated by Samir Jha almost 3 years ago

  • Target version set to Katello 4.1.0
  • Triaged changed from No to Yes
Actions #2

Updated by Jeremy Lenz almost 3 years ago

  • Assignee set to Partha Aji
Actions #3

Updated by The Foreman Bot almost 3 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/9378 added
Actions #4

Updated by The Foreman Bot over 2 years ago

  • Fixed in Releases Katello 4.2.0 added
Actions #5

Updated by Partha Aji over 2 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF