devstack

Sometimes atop can't start with unable to find logs directory

Bug #2100870 reported by Vasyl Saienko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
devstack
New
Undecided
Unassigned

Bug Description

An example of failed deployment https://zuul.opendev.org/t/openstack/build/e166401ec00f40b8899b0ec47553ab8f, looks like a race during atop start.

_SYSTEMD_SLICE=system.slice
_CAP_EFFECTIVE=1ffffffffff
_TRANSPORT=stdout
_HOSTNAME=np0039982119
_STREAM_ID=a72615b88bf94da5ba4e47b0b3d02387
SYSLOG_IDENTIFIER=find
MESSAGE=/usr/bin/find: â<80><98>/opt/stack/logs/atopâ<80><99>: No such file or directory
_PID=34950
_COMM=find
_SYSTEMD_CGROUP=/system.slice/atop.service
_SYSTEMD_UNIT=atop.service
_SYSTEMD_INVOCATION_ID=bc6f392478174157ac2fa8360aaf4ce8

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.