| Summary: | Error "There must be at leas one plan selected" when create a sync schedule | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Steve Reichard <sreichar> | ||||||
| Component: | Content Management | Assignee: | Katello Bug Bin <katello-bugs> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Corey Welton <cwelton> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.0.0 | CC: | cwelton, scollier, sghai, tstrachota | ||||||
| Target Milestone: | Unspecified | ||||||||
| Target Release: | Unused | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | katello-0.1.179-1 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-08-22 18:20:08 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 747354 | ||||||||
| Attachments: |
|
||||||||
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. I think this is actually a dupe of bug #773314. Not completely. Only the misleading message is common. The described scenario was failing for me after 773314 was fixed. 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. Created attachment 555956 [details]
Applied sync plan on selected 'pulp' product.
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.
QA Verified. |
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: