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.
DescriptionBrad Buckingham
2013-10-10 18:46:01 UTC
Description of problem:
The Satellite CLI reports "Sync Complete" for "node sync"; however, the node appears to be continuing to sync content. This can be confusing to the user.
Version-Release number of selected component (if applicable):
katello-1.4.6-21.el6sat.noarch
katello-cli-1.4.3-18.el6sat.noarch
pulp-server-2.3.0-0.17.beta.el6sat.noarch
How reproducible:
So far, I've seen this occur on 1 out of 3 nodes; therefore, reproducing it might be tricky.
Steps to Reproduce:
1. Install/configure Satellite 6 (katello-configure)
2. Import a manifest, enable & sync RHEL 6Server
3. Create a content view definition, adding the repo from 3
4. Publish a content view from the definition
5. Install/configure Satellite 6 node (node-installer)
6. Using the CLI on the Satellite 6, add Library to the node. E.g,
node add_environment --org Katello_Infrastructure --environment Library --id 1
7. Sync the Library to the node
node sync --org Katello_Infrastructure --environment Library --id 1
Actual results:
After some time, CLI reports:
Sync Complete
However, the node appears to be continuing to sync content. E.g.
pulp-admin -u [user] -p [password] tasks details --task-id 1fe27def-5c4c-44e6-aba7-4e9b2634c90c
+----------------------------------------------------------------------+
Task Details
+----------------------------------------------------------------------+
Operations: sync
Resources: Katello_Infrastructure-Red_Hat_Enterprise_Linux_Server-Red_Hat_Ent
erprise_Linux_6_Server_RPMs_x86_64_6Server (repository)
State: Running
Start Time: 2013-10-10T12:47:15Z
Finish Time: Incomplete
Result: Incomplete
Task Id: 1fe27def-5c4c-44e6-aba7-4e9b2634c90c
Progress:
Nodes Http Importer:
Repo Id: Katello_Infrastructure-Red_Hat_Enterprise_Linux_Server-Red_Hat_Ent
erprise_Linux_6_Server_RPMs_x86_64_6Server
State: adding_units
Unit Add:
Completed: 3316
Details: /var/lib/pulp/content/rpm/selinux-policy/3.7.19/93.el6/noarch/e
ad049fa1f26b929a935f8d25e1e3f0a486827e7/Packages/selinux-policy
-3.7.19-93.el6.noarch.rpm
Total: 13169
[root@sat-perf-05 rhel]# pulp-admin -u [user] -p [password] tasks details --task-id 1fe27def-5c4c-44e6-aba7-4e9b2634c90c
+----------------------------------------------------------------------+
Task Details
+----------------------------------------------------------------------+
Operations: sync
Resources: Katello_Infrastructure-Red_Hat_Enterprise_Linux_Server-Red_Hat_Ent
erprise_Linux_6_Server_RPMs_x86_64_6Server (repository)
State: Running
Start Time: 2013-10-10T12:47:15Z
Finish Time: Incomplete
Result: Incomplete
Task Id: 1fe27def-5c4c-44e6-aba7-4e9b2634c90c
Progress:
Nodes Http Importer:
Repo Id: Katello_Infrastructure-Red_Hat_Enterprise_Linux_Server-Red_Hat_Ent
erprise_Linux_6_Server_RPMs_x86_64_6Server
State: adding_units
Unit Add:
Completed: 3770
Details: /var/lib/pulp/content/rpm/initscripts/9.03.23/1.el6/x86_64/2ba3
1c42345159643b07df6b95081db2870d3eb7/Packages/initscripts-9.03.
23-1.el6.x86_64.rpm
Total: 13169
Expected results:
The CLI shouldn't report the sync as complete until all tasks associated have been completed.
Additional info:
This was observed on a production install. It is possible that this issue was triggered by the low timeout values in /etc/pulp/server.conf (e.g. update_timeout: 10:600). In other words the Satellite 6 server may have timed out at the 600s, while the agent on the node continued syncing.
The root cause of this bug and bug 1018236 are the same. Closing this once, since the other was opened by QA. :)
*** This bug has been marked as a duplicate of bug 1018236 ***
Description of problem: The Satellite CLI reports "Sync Complete" for "node sync"; however, the node appears to be continuing to sync content. This can be confusing to the user. Version-Release number of selected component (if applicable): katello-1.4.6-21.el6sat.noarch katello-cli-1.4.3-18.el6sat.noarch pulp-server-2.3.0-0.17.beta.el6sat.noarch How reproducible: So far, I've seen this occur on 1 out of 3 nodes; therefore, reproducing it might be tricky. Steps to Reproduce: 1. Install/configure Satellite 6 (katello-configure) 2. Import a manifest, enable & sync RHEL 6Server 3. Create a content view definition, adding the repo from 3 4. Publish a content view from the definition 5. Install/configure Satellite 6 node (node-installer) 6. Using the CLI on the Satellite 6, add Library to the node. E.g, node add_environment --org Katello_Infrastructure --environment Library --id 1 7. Sync the Library to the node node sync --org Katello_Infrastructure --environment Library --id 1 Actual results: After some time, CLI reports: Sync Complete However, the node appears to be continuing to sync content. E.g. pulp-admin -u [user] -p [password] tasks details --task-id 1fe27def-5c4c-44e6-aba7-4e9b2634c90c +----------------------------------------------------------------------+ Task Details +----------------------------------------------------------------------+ Operations: sync Resources: Katello_Infrastructure-Red_Hat_Enterprise_Linux_Server-Red_Hat_Ent erprise_Linux_6_Server_RPMs_x86_64_6Server (repository) State: Running Start Time: 2013-10-10T12:47:15Z Finish Time: Incomplete Result: Incomplete Task Id: 1fe27def-5c4c-44e6-aba7-4e9b2634c90c Progress: Nodes Http Importer: Repo Id: Katello_Infrastructure-Red_Hat_Enterprise_Linux_Server-Red_Hat_Ent erprise_Linux_6_Server_RPMs_x86_64_6Server State: adding_units Unit Add: Completed: 3316 Details: /var/lib/pulp/content/rpm/selinux-policy/3.7.19/93.el6/noarch/e ad049fa1f26b929a935f8d25e1e3f0a486827e7/Packages/selinux-policy -3.7.19-93.el6.noarch.rpm Total: 13169 [root@sat-perf-05 rhel]# pulp-admin -u [user] -p [password] tasks details --task-id 1fe27def-5c4c-44e6-aba7-4e9b2634c90c +----------------------------------------------------------------------+ Task Details +----------------------------------------------------------------------+ Operations: sync Resources: Katello_Infrastructure-Red_Hat_Enterprise_Linux_Server-Red_Hat_Ent erprise_Linux_6_Server_RPMs_x86_64_6Server (repository) State: Running Start Time: 2013-10-10T12:47:15Z Finish Time: Incomplete Result: Incomplete Task Id: 1fe27def-5c4c-44e6-aba7-4e9b2634c90c Progress: Nodes Http Importer: Repo Id: Katello_Infrastructure-Red_Hat_Enterprise_Linux_Server-Red_Hat_Ent erprise_Linux_6_Server_RPMs_x86_64_6Server State: adding_units Unit Add: Completed: 3770 Details: /var/lib/pulp/content/rpm/initscripts/9.03.23/1.el6/x86_64/2ba3 1c42345159643b07df6b95081db2870d3eb7/Packages/initscripts-9.03. 23-1.el6.x86_64.rpm Total: 13169 Expected results: The CLI shouldn't report the sync as complete until all tasks associated have been completed. Additional info: This was observed on a production install. It is possible that this issue was triggered by the low timeout values in /etc/pulp/server.conf (e.g. update_timeout: 10:600). In other words the Satellite 6 server may have timed out at the 600s, while the agent on the node continued syncing.