Bug #7360
closedSynchronization status and refresh should not be available when repo is not synced
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
Updated by Brad Buckingham over 10 years ago
- Assignee set to Brad Buckingham
- Triaged changed from No to Yes
Updated by The Foreman Bot over 10 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 (
)
Updated by Brad Buckingham over 10 years ago
- Bugzilla link changed from 1120595 to 1094986
Updated by Brad Buckingham over 10 years ago
- Bugzilla link changed from 1094986 to 1128796
Updated by Brad Buckingham over 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|f2b47016c88614d7dd624ad665ff156a31b56ec3.
Updated by Eric Helms over 10 years ago
- Translation missing: en.field_release set to 13