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.
DescriptionDiksha Chaudhari
2019-06-26 01:05:56 UTC
Description of problem: Sync plans neither updates timestamp on Product/Repos nor create tasks after upgrading the Satellite to 6.4
Version-Release number of selected component (if applicable): Satellite 6.4.3
[This BZ is similar to # 1551957 which is closed stating that it is resolved in 6.4 but still this issue is observed in v6.4. Hence opening a new Bugzilla for this issue]
How reproducible: Every time
Steps to Reproduce:
1. Upgrade the Satellite from 6.3 to 6.4
2. After the sync plan is triggered the timestamp is never updated.
Actual results:
Sync plan run in the background, however the timestamp on the UI doesn't get updated.
Expected results:
If a Sync Plan is executed, it should have a corresponding sync tasks and relevant time stamp should be updated on the UI. This would cause confusion to the end user, as if the sync plans are not working.
Additional info:
Sync plans timestamp is updated when we inspect using pulp-admin command,
# pulp-admin -u admin -p $pulpAdminPassword rpm repo list // get the repo ID of the repository which is added in the sync plan
# pulp-admin repo history sync --repo-id cd7c9d79-95e0-40a0-b7fc-a9370df8ec1e // replace the repo ID with one you get from above output.
+----------------------------------------------------------------------+
Sync History [ 6f742caf-4638-4848-879c-e90802b5f4d0 ]
+----------------------------------------------------------------------+
Repo Id: 6f742caf-4638-4848-879c-e90802b5f4d0
Result: success
Started: 2019-06-20T01:00:06Z
Completed: 2019-06-20T01:00:15Z
Added Count: 0
Removed Count: 0
Updated Count: 0
Repo Id: 6f742caf-4638-4848-879c-e90802b5f4d0
Result: success
Started: 2019-06-19T01:00:06Z
Completed: 2019-06-19T01:00:15Z
Added Count: 0
Removed Count: 0
Updated Count: 0
Repo Id: 6f742caf-4638-4848-879c-e90802b5f4d0
Result: success
Started: 2019-06-18T01:00:07Z
Completed: 2019-06-18T01:16:17Z
Added Count: 13
Removed Count: 0
Updated Count: 3670
Repo Id: 6f742caf-4638-4848-879c-e90802b5f4d0
Result: success
Started: 2019-06-16T01:00:07Z
Completed: 2019-06-16T01:00:31Z
Added Count: 0
Removed Count: 0
Updated Count: 0
Repo Id: 6f742caf-4638-4848-879c-e90802b5f4d0
Result: success
Started: 2019-06-15T01:00:06Z
Completed: 2019-06-15T01:00:17Z
Added Count: 0
Removed Count: 0
Updated Count: 0
As a workaround you can try to call the Sync plan through REST API:
# curl -u admin -k -H 'content-type: application/json' -X PUT https://satellite.example.com/katello/api/organizations/1/sync_plans/2/sync
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.
Description of problem: Sync plans neither updates timestamp on Product/Repos nor create tasks after upgrading the Satellite to 6.4 Version-Release number of selected component (if applicable): Satellite 6.4.3 [This BZ is similar to # 1551957 which is closed stating that it is resolved in 6.4 but still this issue is observed in v6.4. Hence opening a new Bugzilla for this issue] How reproducible: Every time Steps to Reproduce: 1. Upgrade the Satellite from 6.3 to 6.4 2. After the sync plan is triggered the timestamp is never updated. Actual results: Sync plan run in the background, however the timestamp on the UI doesn't get updated. Expected results: If a Sync Plan is executed, it should have a corresponding sync tasks and relevant time stamp should be updated on the UI. This would cause confusion to the end user, as if the sync plans are not working. Additional info: Sync plans timestamp is updated when we inspect using pulp-admin command, # pulp-admin -u admin -p $pulpAdminPassword rpm repo list // get the repo ID of the repository which is added in the sync plan # pulp-admin repo history sync --repo-id cd7c9d79-95e0-40a0-b7fc-a9370df8ec1e // replace the repo ID with one you get from above output. +----------------------------------------------------------------------+ Sync History [ 6f742caf-4638-4848-879c-e90802b5f4d0 ] +----------------------------------------------------------------------+ Repo Id: 6f742caf-4638-4848-879c-e90802b5f4d0 Result: success Started: 2019-06-20T01:00:06Z Completed: 2019-06-20T01:00:15Z Added Count: 0 Removed Count: 0 Updated Count: 0 Repo Id: 6f742caf-4638-4848-879c-e90802b5f4d0 Result: success Started: 2019-06-19T01:00:06Z Completed: 2019-06-19T01:00:15Z Added Count: 0 Removed Count: 0 Updated Count: 0 Repo Id: 6f742caf-4638-4848-879c-e90802b5f4d0 Result: success Started: 2019-06-18T01:00:07Z Completed: 2019-06-18T01:16:17Z Added Count: 13 Removed Count: 0 Updated Count: 3670 Repo Id: 6f742caf-4638-4848-879c-e90802b5f4d0 Result: success Started: 2019-06-16T01:00:07Z Completed: 2019-06-16T01:00:31Z Added Count: 0 Removed Count: 0 Updated Count: 0 Repo Id: 6f742caf-4638-4848-879c-e90802b5f4d0 Result: success Started: 2019-06-15T01:00:06Z Completed: 2019-06-15T01:00:17Z Added Count: 0 Removed Count: 0 Updated Count: 0 As a workaround you can try to call the Sync plan through REST API: # curl -u admin -k -H 'content-type: application/json' -X PUT https://satellite.example.com/katello/api/organizations/1/sync_plans/2/sync