Bug #32320: "Current organization has no manifest imported" error when trying to import a manifest - Katello - Foreman

Actions

Copy link

Bug #32320

closed

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

Added by Jeremy Lenz about 3 years ago. Updated almost 3 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Partha Aji

Category:

Subscriptions

Target version:

Katello 4.1.0

Difficulty:

Triaged:

Yes

Bugzilla link:

Pull request:

https://github.com/Katello/katello/pull/9378

Fixed in Releases:

Katello 4.2.0

Found in Releases:

Red Hat JIRA:

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.