Bug 1383802
| Summary: | osp-director-10: After Upgrading osp9 to osp10 'openstack-ceilometer-api service' won't start after reboot. (unrecognized arguments: --logfile /var/log/ceilometer/api.log) | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Omri Hochman <ohochman> |
| Component: | openstack-ceilometer | Assignee: | Pradeep Kilambi <pkilambi> |
| Status: | CLOSED ERRATA | QA Contact: | Yurii Prokulevych <yprokule> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 10.0 (Newton) | CC: | dbecker, jruzicka, jschluet, mabaakou, mandreou, mburns, morazi, pkilambi, rhel-osp-director-maint, sasha, srevivo, ssmolyak |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | 10.0 (Newton) | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-ceilometer-7.0.0-2.1.el7ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-12-14 16:16:04 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: | |||
|
Description
Omri Hochman
2016-10-11 19:36:07 UTC
So this version of openstack-ceilometer-api doesn't support the arg --logfile nor --log-file. Downgraded to 6.1.3-2.el7ost and was able to start the service as well as runing the command with this arg. So, to be clear there are 2 issues here: 1. *undercloud* ceilometer is disabled by default on OSP9 to OSP10 upgrade unless operator sets "enable_telemetry = true" in undercloud.conf so we definitely need a docs bug for that to rhos-docs team 2. *undercloud* ceilometer fails to even start manually after the upgrade - there is a legitimate issue there that prad has fixed with https://review.rdoproject.org/r/#/c/3239/ which has merged. (@prad would this potentially affect the overcloud nodes too - I assume they get the same versions?) I'd propose we use this bug for 2 (since it has the trace above pointing at that). I filed https://bugzilla.redhat.com/show_bug.cgi?id=1383923 for the docs fix and assigned to rhos-docs. I think we can also move this BZ to post since that rdo fix merged. just reporting back to confirm that when I set enable_telemetry to true in /home/stack/undercloud.conf before running the OSP9-->OSP10 undercloud upgrade, I get to keep my ceilometer services (except the ceilometer-api issue that this BZ reports with the "--logfile " argument for which I didn't apply/get the fix yet):
[stack@instack ~]$ grep enable_telemetry ./undercloud.conf
enable_telemetry = true
[stack@instack ~]$ openstack-service status | grep ceilo
Failed to get properties: Unit name openstack-zaqar@.service is missing the instance name.
MainPID=0 Id=openstack-ceilometer-api.service ActiveState=failed
MainPID=12570 Id=openstack-ceilometer-central.service ActiveState=active
MainPID=12504 Id=openstack-ceilometer-collector.service ActiveState=active
MainPID=12491 Id=openstack-ceilometer-notification.service ActiveState=active
[stack@instack ~]$ systemctl status -l openstack-ceilometer-api
● openstack-ceilometer-api.service - OpenStack ceilometer API service
Loaded: loaded (/usr/lib/systemd/system/openstack-ceilometer-api.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Wed 2016-10-12 04:28:36 EDT; 18min ago
Process: 12683 ExecStart=/usr/bin/ceilometer-api --logfile /var/log/ceilometer/api.log (code=exited, status=2)
Main PID: 12683 (code=exited, status=2)
Hi Marios, Looks like the issue is not just with '--logfile' argument but also with port binding. I've opened separate bz 1384005 to track it. (In reply to Yurii Prokulevych from comment #7) > Hi Marios, > > Looks like the issue is not just with '--logfile' argument but also with > port binding. I've opened separate bz 1384005 to track it. Thanks for taking a look Yurii - left a note there... not saying there isn't another issue but I'm not clear if the undercloud config was properly applied see https://bugzilla.redhat.com/show_bug.cgi?id=1384005#c1. I guess we will also find out soon enough once we get the fix from Prad linked above into a puddle for testing. 7.0.0-2.1 does not yet include that fix. 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-2016-2948.html |