https://bugzilla.redhat.com/show_bug.cgi?id=1455279
--- Comment #9 from Mat Booth <mat.booth(a)redhat.com> ---
(In reply to Roland Grunberg from comment #8)
@Mat, although this is a rare occurrence, I could see this as being a
bug in
how we deal with bundles that are symlinked into droplets.
Basically, one can modify the underlying bundle metadata corresponding to a
symlink in droplets and the stale metadata will persist (I believe a clean
only happens when the timestamp of some file under droplets changes). One
easy solution might be to fully resolve the symlink and use the resulting
file's timestamp in places where we rely on old timestamps to tell us if
things changed.
Yes first resolving a canonical path for symlink'd bundles is probably what it
should be doing.
I'll eventually mark this as CLOSED (WORKSFORME) but open a new bug
referencing this one to track the issue.
Good idea :-)
--
You are receiving this mail because:
You are on the CC list for the bug.