Description of problem: ------------------------ While upgrading RHSC from 2.1.6 to 3.0.4, running rhsc-setup after updating it, does not automatically update the rhsc-log-collector package. Version-Release number of selected component (if applicable): -------------------------------------------------------------- rhsc-setup-3.0.4-1.25.el6rhs.noarch How reproducible: ----------------- Observed once Steps to Reproduce: ------------------- 1. Set up RHSC 2.1.6 2. To upgrade RHSC, update rhsc-setup package to 3.0.4 and run `rhsc-setup' command Actual results: --------------- rhsc-log-collector package is not updated automatically when `rhsc-setup' command is run. Expected results: ------------------ rhsc-log-collector should be updated automatically when `rhsc-setup' is run. Additional info:
Hi Shubhendu, I see this bug being added in the Known Issues tracker bug for the 3.0.4 release. Could you please fill out the doc text?
Hi Shubhendu, Can you please review and sign off on the edited doc text?
Doc text looks technically correct.
cannot verify this bug until the bug below is fixed. https://bugzilla.redhat.com/show_bug.cgi?id=1225405
Moving this bug since i still do not see rhsc-log-collector being updated as part of rhsc-setup and running it after that.
Cannot verify this bug until the bug https://bugzilla.redhat.com/show_bug.cgi?id=1238244 is fixed
Could not verify this bug for upgrade from 2.1 to 3.1 due to the bug https://bugzilla.redhat.com/show_bug.cgi?id=1238244 Verified this bug by updating rhsc from 3.0.4 to 3.1. After running "yum update rhsc-setup" and running rhsc-setup i see that log collector has been updated. rpm -qa | grep rhsc-log-collector rhsc-log-collector-3.1.0-1.0.el6rhs.noarch Marking this verified.
Sahina, Could you review the edited doc text and sign-off?
Acked
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. https://rhn.redhat.com/errata/RHEA-2015-1494.html