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 837000 - [RFE] when updating sync plan by CLI, it resets the interval.
Summary: [RFE] when updating sync plan by CLI, it resets the interval.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: API
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Pavel Pokorny
QA Contact: Hayk Hovsepyan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-02 13:31 UTC by Hayk Hovsepyan
Modified: 2019-09-25 21:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Updating a sync plan via the command line caused the interval field to reset. This bug fix stops the interval from resetting. A sync plan's interval does not reset now when updating.
Clone Of:
Environment:
Last Closed: 2012-12-04 19:47:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1543 0 normal SHIPPED_LIVE Important: CloudForms System Engine 1.1 update 2012-12-05 00:39:57 UTC

Description Hayk Hovsepyan 2012-07-02 13:31:04 UTC 
Description of problem:
When updating sync plan name or date, it resets the "interval" field.

Version-Release number of selected component (if applicable):
pulp-common-1.1.11-1.el6.noarch
qpid-cpp-server-ssl-0.14-14.el6_2.x86_64
katello-glue-pulp-0.2.43-1.git.36.5ddcc14.el6.noarch
katello-repos-testing-0.2.4-1.el6.noarch
katello-0.2.43-1.git.36.5ddcc14.el6.noarch
katello-configure-0.2.28-1.git.4.81a551d.el6.noarch
candlepin-tomcat6-0.5.32-1.el6.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-agent-1.0.4-1.git.0.4d2cfb2.el6.noarch
m2crypto-0.21.1.pulp-7.el6.x86_64
mod_wsgi-3.3-3.pulp.el6.x86_64
python-qpid-0.14-7.el6_2.noarch
qpid-cpp-client-ssl-0.14-14.el6_2.x86_64
katello-glue-candlepin-0.2.43-1.git.36.5ddcc14.el6.noarch
katello-selinux-0.2.6-1.git.0.c9816da.el6.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-cli-0.2.41-1.git.25.9c71bc3.el6.noarch
candlepin-0.5.32-1.el6.noarch
qpid-cpp-server-0.14-14.el6_2.x86_64
katello-glue-foreman-0.2.43-1.git.36.5ddcc14.el6.noarch
pulp-1.1.11-1.el6.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-cli-common-0.2.41-1.git.25.9c71bc3.el6.noarch
katello-cli-tests-0.2.20-1.el6.noarch
python-oauth2-1.5.170-2.pulp.el6.noarch
katello-certs-tools-1.1.6-1.git.0.4878f30.el6.noarch
qpid-cpp-client-0.14-14.el6_2.x86_64
katello-common-0.2.43-1.git.36.5ddcc14.el6.noarch
katello-repos-0.2.4-1.el6.noarch
pulp-selinux-server-1.1.11-1.el6.noarch


How reproducible:
always

Steps to Reproduce:
1. Create some sync plan by CLI, specify some Interval for it.
2. Update just created sync plan name (sync_plan update --org $org --name $name --new_name $newname)
3. List sync plans and you will see that the Interval field for just updated sync plan is "none".
  
Actual results:
After updating sync plan name or date, it rests the interval field to "none"

Expected results:
It should not reset the interval field, and should update only specified fields.

Additional info:
By WebUI you can update sync plan name and interval is not changed.
Comment 1 Mike McCune 2012-09-05 15:21:59 UTC 
This is not an RFE and is a bug.  I'll attempt a fix in 1.1
Comment 2 Pavel Pokorny 2012-09-13 07:26:23 UTC 
Fixed in bfd9c08
Comment 4 Hayk Hovsepyan 2012-09-18 14:44:12 UTC 
Verified on revision:

katello-cli-1.1.8-4.el6cf.noarch
katello-certs-tools-1.1.8-1.el6cf.noarch
candlepin-selinux-0.7.8-1.el6cf.noarch
qpid-cpp-server-ssl-0.14-14.el6_2.x86_64
pulp-selinux-server-1.1.12-1.el6cf.noarch
katello-glue-pulp-1.1.12-7.el6cf.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-cli-common-1.1.8-4.el6cf.noarch
candlepin-0.7.8-1.el6cf.noarch
qpid-cpp-client-ssl-0.14-14.el6_2.x86_64
katello-configure-1.1.9-3.el6cf.noarch
katello-glue-candlepin-1.1.12-7.el6cf.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
candlepin-tomcat6-0.7.8-1.el6cf.noarch
pulp-common-1.1.12-1.el6cf.noarch
qpid-cpp-server-0.14-14.el6_2.x86_64
katello-selinux-1.1.1-1.el6cf.noarch
katello-all-1.1.12-7.el6cf.noarch
python-qpid-0.14-7.el6_2.noarch
python-isodate-0.4.4-4.pulp.el6.noarch
qpid-cpp-client-0.14-14.el6_2.x86_64
pulp-1.1.12-1.el6cf.noarch
katello-common-1.1.12-7.el6cf.noarch
katello-1.1.12-7.el6cf.noarch
katello-qpid-client-key-pair-1.0-1.noarch
m2crypto-0.21.1.pulp-7.el6.x86_64
python-oauth2-1.5.170-2.pulp.el6.noarch
mod_wsgi-3.3-3.pulp.el6.x86_64

Now it works correctly and does not reset interval.
Comment 6 errata-xmlrpc 2012-12-04 19:47:07 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-1543.html
Note You need to log in before you can comment on or make changes to this bug.