Project

General

Profile

Actions

Bug #7360

closed

Synchronization status and refresh should not be available when repo is not synced

Added by Brad Buckingham over 9 years ago. Updated almost 6 years ago.

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

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1120595
Description of problem:
If you create a custom product with a custom channel that is not synchronized, you still can request the environment for a sync, that will fail with a warning.

Version-Release number of selected component (if applicable):
6.0.3

How reproducible:
Always

Steps to Reproduce:
1. Create a custom product
2. Create a custom repo without original yum server
3. Synchronize it

Actual results:
Sync starts as fails with a warning

Expected results:
A message and a dialog explaining that there is nothing to synchronize

Additional info:
I would expect a warning dialog explaining that only sync-able repos will be sync when I assign a synchronization plan to a product that is not sync-able

Actions #1

Updated by Brad Buckingham over 9 years ago

  • Assignee set to Brad Buckingham
  • Triaged changed from No to Yes
Actions #2

Updated by The Foreman Bot over 9 years ago

  • Status changed from New to Ready For Testing
  • Target version set to 55
  • Pull request https://github.com/Katello/katello/pull/4640 added
  • Pull request deleted ()
Actions #3

Updated by Brad Buckingham over 9 years ago

  • Bugzilla link changed from 1120595 to 1094986
Actions #4

Updated by Brad Buckingham over 9 years ago

  • Bugzilla link changed from 1094986 to 1128796
Actions #5

Updated by Brad Buckingham over 9 years ago

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

Updated by Eric Helms over 9 years ago

  • translation missing: en.field_release set to 13
Actions

Also available in: Atom PDF