Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 782226 - Error "There must be at leas one plan selected" when create a sync schedule
Summary: Error "There must be at leas one plan selected" when create a sync schedule
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks: katello-blockers
TreeView+ depends on / blocked
 
Reported: 2012-01-16 21:47 UTC by Steve Reichard
Modified: 2019-09-25 20:43 UTC (History)
4 users (show)

Fixed In Version: katello-0.1.179-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 18:20:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
movie showing steps and error (2.92 MB, video/ogg)
2012-01-16 21:47 UTC, Steve Reichard 		no flags Details
Applied sync plan on selected 'pulp' product. (114.99 KB, image/png)
2012-01-18 08:50 UTC, Sachin Ghai 		no flags Details
View All

Description Steve Reichard 2012-01-16 21:47:58 UTC 
Created attachment 555610 [details]
movie showing steps and error

Description of problem:

I have been trying to create a sync schedule and there the error.

I've attached a movie showing an example.


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


[root@cf-se1 log]# /pub/scripts/post_install_configuration_scripts/cf-se-versions 
Red Hat Enterprise Linux Server release 6.2 (Santiago)
Linux cf-se1.cloud.lab.eng.bos.redhat.com 2.6.32-220.2.1.el6.x86_64 #1 SMP Tue Dec 13 16:21:34 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
PyYAML-3.09-14.el6_1.x86_64
facter-1.5.9-1.el6.noarch
js-1.70-12.el6_0.x86_64
mongodb-1.6.4-3.el6_0.x86_64
mongodb-server-1.6.4-3.el6_0.x86_64
puppet-2.6.11-1.el6_1.noarch
pymongo-1.9-8.el6_1.x86_64
tomcat6-6.0.24-35.el6_1.noarch
ruby-1.8.7.352-3.el6.x86_64
grinder-0.0.136-1.el6.noarch
postgresql-server-8.4.9-1.el6_1.1.x86_64
postgresql-8.4.9-1.el6_1.1.x86_64
candlepin-0.5.8-1.el6.noarch
pulp-0.0.256-1.el6.noarch
katello-0.1.174-2.el6.noarch
katello-all-0.1.174-2.el6.noarch
katello-cli-0.1.34-2.el6.noarch
katello-configure-0.1.52-2.el6.noarch
[root@cf-se1 log]# 



How reproducible:


Initially I saw this before I had any channels sync'd.  I then tried again after my initial sync, with the same results.

I also had to re-install the system (network stroage failure)  and it occured on both installations.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Tomas Strachota 2012-01-17 09:01:40 UTC 
This is combination of wrong format of sync time being sent to Pulp and misleading error message.

I have fixed the first part while working on cli for scheduled sync. The patch is on it's way, taking.
Comment 2 Corey Welton 2012-01-17 13:55:04 UTC 
I think this is actually a dupe of bug #773314.
Comment 3 Tomas Strachota 2012-01-17 16:43:09 UTC 
Not completely. Only the misleading message is common. The described scenario was failing for me after 773314 was fixed.
Comment 4 Sachin Ghai 2012-01-18 08:48:55 UTC 
For me it's working from UI on following build:

[root@dhcp201-176 ~]# rpm -qa | grep katello
katello-glue-candlepin-0.1.178-1.el6.noarch
katello-trusted-ssl-cert-1.0-1.noarch
katello-common-0.1.178-1.el6.noarch
katello-httpd-ssl-key-pair-1.0-1.noarch
katello-repos-testing-0.1.5-1.el6.noarch
katello-cli-0.1.35-1.el6.noarch
katello-0.1.178-1.el6.noarch
katello-configure-0.1.53-1.el6.noarch
katello-glue-pulp-0.1.178-1.el6.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-cli-common-0.1.35-1.el6.noarch
katello-certs-tools-1.0.2-1.el6.noarch
katello-all-0.1.178-1.el6.noarch
katello-glue-foreman-0.1.178-1.el6.noarch
katello-repos-0.1.5-1.el6.noarch
[root@dhcp201-176 ~]# 


I can apply the sync plan and selected product. Please see the attached screenshot in next comment.
Comment 5 Sachin Ghai 2012-01-18 08:50:18 UTC 
Created attachment 555956 [details]
Applied sync plan on selected 'pulp' product.
Comment 6 Tomas Strachota 2012-01-18 09:22:15 UTC 
Fixed in katello-0.1.179-1

commit 57508593aa626baf122635ec620dedbe48ccb7f5
Author: Tomas Strachota <tstrachota>
Date:   Sun Jan 15 12:06:42 2012 +0100

    scheduled sync - time format of non-recurring sync plans


Please note that it is necessary to test with both recurring (eg. interval=weekly) and single (interval=none) sync plans. Recurring sync plans were not affected by this bug.
Comment 9 Corey Welton 2012-02-01 05:12:13 UTC 
QA Verified.
Note You need to log in before you can comment on or make changes to this bug.