Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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:
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.
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.
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.
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: