Description of problem: Tried to install packages and errata to a registered/subscribed client using the katello web ui and even though the web ui told me that operation succeeded, the packages/errata count did not refresh to account for the changes. For instance, before installing an errata I had a total of 431 erratum, but after installing it I still had 431 shown. Reloading the page did not change this until I restarted rhsmcertd in the client. Version-Release number of selected component (if applicable): * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.8.7-1.el6_4.noarch * candlepin-scl-1-5.el6_4.noarch * candlepin-scl-quartz-2.1.5-5.el6_4.noarch * candlepin-scl-rhino-1.7R3-1.el6_4.noarch * candlepin-scl-runtime-1-5.el6_4.noarch * candlepin-selinux-0.8.7-1.el6_4.noarch * candlepin-tomcat6-0.8.7-1.el6_4.noarch * elasticsearch-0.19.9-8.el6sat.noarch * foreman-1.1.10002-29.noarch * foreman-postgresql-1.1.10002-29.noarch * katello-1.4.2-6.el6sat.noarch * katello-all-1.4.2-6.el6sat.noarch * katello-candlepin-cert-key-pair-1.0-1.noarch * katello-certs-tools-1.4.2-2.el6sat.noarch * katello-cli-1.4.2-5.el6sat.noarch * katello-cli-common-1.4.2-5.el6sat.noarch * katello-common-1.4.2-6.el6sat.noarch * katello-configure-1.4.3-9.el6sat.noarch * katello-configure-foreman-1.4.3-9.el6sat.noarch * katello-foreman-all-1.4.2-6.el6sat.noarch * katello-glue-candlepin-1.4.2-6.el6sat.noarch * katello-glue-elasticsearch-1.4.2-6.el6sat.noarch * katello-glue-pulp-1.4.2-6.el6sat.noarch * katello-qpid-broker-key-pair-1.0-1.noarch * katello-qpid-client-key-pair-1.0-1.noarch * katello-selinux-1.4.3-3.el6sat.noarch * openldap-2.4.23-31.el6.x86_64 * openldap-devel-2.4.23-31.el6.x86_64 * pulp-rpm-plugins-2.1.1-1.el6sat.noarch * pulp-selinux-2.1.1-1.el6sat.noarch * pulp-server-2.1.1-1.el6sat.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-ldap_fluff-0.1.7-3.el6sat.noarch * ruby193-rubygem-net-ldap-0.2.2-7.el6_4.noarch * signo-0.0.10-1.el6sat.noarch * signo-katello-0.0.10-1.el6sat.noarch How reproducible: Steps to Reproduce: 1. Install a package or errata to a registered/subscribed client 2. 3. Actual results: After an errata is installed, the total number of available erratum does not update Expected results: Additional info:
Aside from the mention of count changing, we need to investigate how the client's package profile is updated on the server as changes occur on the client. What triggers this update? What is the frequency?
This has been fixed with bug #1103937.
Verified. Satellite-6.1.0-RHEL-6-20150224.0
This bug is slated to be released with Satellite 6.1.
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.