Project

General

Profile

Actions

Bug #6913

closed

Content views that fail to publish should not have "promote" button.

Added by Brad Buckingham over 10 years ago. Updated almost 7 years ago.

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

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1092143
Description of problem:
Sometimes (for whatever reason?) a content view publish action fails. This is visible in the UI and has a red status bar, etc -- but the "promote" button remains.

We should require that any content view have a check that the most recent publish attempt was successful before displaying/enabling the promote button. There should probably be a help bubble explaining why promotion might be disabled.

Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140423.1

How reproducible:

Steps to Reproduce:
1. Attempt to publish a CV but assure this publish fails (how??)
2. View the results and click the 'Promote' button.
3. View results.

Actual results:

In this case I got
required lock: #<ForemanTasks::Lock:0x007fd9a4e3e858> conflicts wiht [#<ForemanTasks::Lock id: 224, task_id: "e0bfaa22-52f9-4cef-abe9-d0ad02afe30e", name: "read", resource_type: "Katello::ContentView", resource_id: 3, exclusive: true>]".

Expected results:
I am not sure how relevant/useful error message above is for the bz, but in any case, we should disable the promote button until a CV publish has been successful.

Additional info:

Actions

Also available in: Atom PDF