Bug 1513993
| Summary: | tendrl services reports too long error lines in system log | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Martin Bukatovic <mbukatov> |
| Component: | web-admin-tendrl-commons | Assignee: | Anmol Sachan <asachan> |
| Status: | CLOSED ERRATA | QA Contact: | Martin Bukatovic <mbukatov> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.3 | CC: | nthomas, sankarshan |
| Target Milestone: | --- | ||
| Target Release: | RHGS 3.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | tendrl-commons-1.6.3-7.el7rhgs | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-04 06:58:06 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1503134 | ||
|
Description
Martin Bukatovic
2017-11-16 12:56:08 UTC
(In reply to Rohan Kanade from comment #3) > Fixed: https://github.com/Tendrl/monitoring-integration/issues/35 Could you either update FiV field or move this BZ into POST instead? Thank you. Checking tendrl python components (which are using tendrl commons, which is a component this BZ is about): tendrl-commons-1.6.3-6.el7rhgs tendrl-gluster-integration-1.6.3-4.el7rhgs tendrl-monitoring-integration-1.6.3-4.el7rhgs tendrl-node-agent-1.6.3-6.el7rhgs tendrl-notifier-1.6.3-3.el7rhgs Which contains these systemd services: /usr/lib/systemd/system/tendrl-node-agent.service /usr/lib/systemd/system/tendrl-notifier.service /usr/lib/systemd/system/tendrl-monitoring-integration.service /usr/lib/systemd/system/tendrl-gluster-integration.service The journald log entries looks good at first sight, there are no obvious problems as noted in the BZ (2nd example from Actual Results), eg.: ``` # journalctl -u tendrl-monitoring-integration --output=cat | head -30 Started Monitoring Integration. Starting Monitoring Integration... Creating namespace.monitoring from source tendrl.monitoring_integration namespace.monitoring created! Finding objects in namespace.monitoring.objects Registering object namespace.monitoring.objects.AlertOrganization Finding atoms in namespace.monitoring.objects.AlertOrganization.atoms Finding flows in namespace.monitoring.objects.AlertOrganization.flows Registering object namespace.monitoring.objects.AlertTypes Finding atoms in namespace.monitoring.objects.AlertTypes.atoms Finding flows in namespace.monitoring.objects.AlertTypes.flows Registering object namespace.monitoring.objects.Config Finding atoms in namespace.monitoring.objects.Config.atoms Finding flows in namespace.monitoring.objects.Config.flows Registering object namespace.monitoring.objects.Definition Finding atoms in namespace.monitoring.objects.Definition.atoms Finding flows in namespace.monitoring.objects.Definition.flows Registering object namespace.monitoring.objects.Trigger Finding atoms in namespace.monitoring.objects.Trigger.atoms Finding flows in namespace.monitoring.objects.Trigger.flows Finding flows in namespace.monitoring.flows Registering flow namespace.monitoring.flows.DeleteMonitoringData Registering flow namespace.monitoring.flows.DeleteResourceFromGraphite Registering flow namespace.monitoring.flows.SetupClusterAlias Registering flow namespace.monitoring.flows.UpdateDashboard Setup Tendrl definitions (.yml)for namespace.monitoring Validating registered (.py) flows in namespace.monitoring.flows Validating defined (.yml) flows in namespace.monitoring.flows Validating registered (.py) objects in namespace.monitoring.objects Validating defined (.yml) objects in namespace.monitoring.objects ``` Besides that, I searched for log lines longer that 500 characters (based on the 2nd example from the Actual Results section, where lines are about 2000 characters long), and didn't find anything interesting: ``` # journalctl -u tendrl-monitoring-integration | awk 'length($0)>500' # ``` I used both ways to check all tendrl python services, as listed above. But when I retry the exact reproducer noted in this BZ (setting etcd_connection to 0.0.0.0), I see quite long line, which seems not right: ``` # journalctl -u tendrl-monitoring-integration -f --output cat | grep 'connecting to central store (etcd)' Finding flows in namespace.tendrl.objectError connecting to central store (etcd), trying again...Error connecting to central store (etcd), trying again...Error connecting to central store (etcd), trying again...Error connecting to central store (etcd), trying again...Error connecting to central store (etcd), trying again...s.Os.flows Finding flows in namespace.tendrl.objectError connecting to central store (etcd), trying again...Error connecting to central store (etcd), trying again...Error connecting to central store (etcd), trying again...Error connecting to central store (etcd), trying again...Error connecting to central store (etcd), trying again...s.Os.flows Finding flows in namespace.tendrl.objectError connecting to central store (etcd), trying again...Error connecting to central store (etcd), trying again...Error connecting to central store (etcd), trying again...Error connecting to central store (etcd), trying again...Error connecting to central store (etcd), trying again...s.Os.flows ``` Note that the problem is different compared to original report for this particular case, but it still differs from expected behavior as well. Fixed via: https://github.com/Tendrl/commons/pull/987 Testing with tendrl-monitoring-integration-1.6.3-5.el7rhgs.noarch Based on comment 6, I retried the reproducer and now I see: ~~~ # journalctl -u tendrl-monitoring-integration -f --output cat | grep 'connecting to central store (etcd)' Error connecting to central store (etcd), trying again... Error connecting to central store (etcd), trying again... Error connecting to central store (etcd), trying again... Error connecting to central store (etcd), trying again... Error connecting to central store (etcd), trying again... ~~~ 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://access.redhat.com/errata/RHSA-2018:2616 |