Bug 1619575
Summary: | ceilometer-expirer cron job does not run correctly [osp10] | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Cyril Lopez <cylopez> |
Component: | puppet-tripleo | Assignee: | Mehdi ABAAKOUK <mabaakou> |
Status: | CLOSED ERRATA | QA Contact: | Nataf Sharabi <nsharabi> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 10.0 (Newton) | CC: | aschultz, emacchi, jjoyce, jschluet, lnatapov, mabaakou, mmagr, mnadeem, slinaber, ssmolyak, tvignaud |
Target Milestone: | --- | Keywords: | Triaged, ZStream |
Target Release: | 10.0 (Newton) | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | puppet-tripleo-5.6.8-21.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-04-30 16:58:51 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
Cyril Lopez
2018-08-21 08:36:47 UTC
In the puppet file you must add two "/" The fix is in review: https://review.openstack.org/#/c/599421/ You can looks here for the exact change: https://review.openstack.org/#/c/599421/5/manifests/profile/base/ceilometer/expirer.pp Hi, I've installed OSP10 2019-04-18.1 & waited for approx. 36 hours. # virsh list Id Name State ---------------------------------------------------- 2 undercloud-0 running 8 compute-0 running 9 controller-0 running root@undercloud-0 spool]# ls -lah /var/spool/mail/ total 4.0K drwxrwxr-x. 2 root mail 79 Apr 24 03:23 . drwxr-xr-x. 10 root root 108 Apr 22 07:49 .. -rw-rw----. 1 cloud-user mail 0 Apr 22 07:39 cloud-user -rw-------. 1 root mail 2.1K Apr 24 03:23 root -rw-rw----. 1 rpc mail 0 Oct 10 2018 rpc -rw-rw----. 1 stack mail 0 Apr 22 07:40 stack -rw-rw----. 1 validations mail 0 Apr 22 07:56 validations There is no ceilometer file!!! 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/RHBA-2019:0921 |