Bug 868286 - confusing and unnecessary messages during katello-service run
Summary: confusing and unnecessary messages during katello-service run
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Subscription Asset Manager
Classification: Retired
Component: katello-configure
Version: 1.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Miroslav Suchý
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: sam13-tracker 876323
TreeView+ depends on / blocked
 
Reported: 2012-10-19 12:17 UTC by Tom McKay
Modified: 2013-10-01 10:52 UTC (History)
3 users (show)

Fixed In Version: elasticsearch-0.19.9-3
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 876323 (view as bug list)
Environment:
Last Closed: 2013-10-01 10:52:04 UTC
Embargoed:


Attachments (Terms of Use)
katello-service (13.37 KB, image/png)
2012-10-19 12:17 UTC, Tom McKay
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2013:1390 0 normal SHIPPED_LIVE Release 1.3 of Subscription Asset Manager 2013-10-01 14:43:14 UTC

Description Tom McKay 2012-10-19 12:17:31 UTC
Created attachment 629999 [details]
katello-service

During 'katello-service restart' INFO messages are displayed (see attached screenshot). I have two issues with this:

1. The INFO is not at all informational or useful, as far as I can tell. It would be better just to state OK on success.

2. Each run seems to print a different name in the INFO message. In this case it was "Zero-G" which no one understands the significance. (Working with a customer we were unable to answer what it was or meant.) The next run I did the string was "Firefrost". This is a pointless confusion.

Comment 2 Miroslav Suchý 2012-10-19 12:41:11 UTC
This only happen on RHEL6 as on fedora this is eaten by systemd who redirect it to log.
And that verbose output is written by thin.

Comment 3 Miroslav Suchý 2012-11-13 11:11:06 UTC
Fixed in katello-thirdparty.git
* 3c1ae73 868286 - do not be verbose during startup

Comment 4 Bryan Kearney 2013-06-07 18:20:07 UTC
Moving all POST bugs to ON_QA since we have delivered a puddle with the bugs.

Comment 5 sthirugn@redhat.com 2013-08-12 00:51:11 UTC
Verified.

# katello-service restart
Shutting down Katello services...
Stopping katello: 
Stopping elasticsearch: [  OK  ]
Stopping thumbslug: [  OK  ]
Stopping httpd: [  OK  ]
Stopping tomcat6: [  OK  ]
Done.
Starting Katello services...
Starting tomcat6: [  OK  ]
Starting httpd: [  OK  ]
Starting thumbslug: Aug 11 20:47:52 [main] WARN  org.candlepin.thumbslug.Main - Shutting down...
[  OK  ]
Starting elasticsearch: [  OK  ]
Starting katello: [  OK  ]
Starting katello-jobs: [  OK  ]
Done.

I did not see the INFO messages as mentioned originally in this bug.

Package Verified:
* candlepin-0.8.19-1.el6sam.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.19-1.el6sam.noarch
* candlepin-tomcat6-0.8.19-1.el6sam.noarch
* elasticsearch-0.19.9-8.el6sat.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.4.2-2.el6sat.noarch
* katello-cli-1.4.3-5.el6sat.noarch
* katello-cli-common-1.4.3-5.el6sat.noarch
* katello-common-1.4.3-6.el6sam_splice.noarch
* katello-configure-1.4.4-2.el6sat.noarch
* katello-glue-candlepin-1.4.3-6.el6sam_splice.noarch
* katello-glue-elasticsearch-1.4.3-6.el6sam_splice.noarch
* katello-headpin-1.4.3-6.el6sam_splice.noarch
* katello-headpin-all-1.4.3-6.el6sam_splice.noarch
* katello-selinux-1.4.4-2.el6sat.noarch
* thumbslug-0.0.32-1.el6sam.noarch
* thumbslug-selinux-0.0.32-1.el6sam.noarch

Comment 7 errata-xmlrpc 2013-10-01 10:52:04 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/RHEA-2013-1390.html


Note You need to log in before you can comment on or make changes to this bug.