I am also seeing this on v20, since this thread has persisted since v16, can we assume that Redhat just does not care, wont fix, and is just hoping that it will go away? I don't see any RH participation on this thread, and no fix comming.
I am also seeing this on v20, since this thread has persisted since v16, can we assume that Redhat just does not care, wont fix, and is just hoping that it will go away? I don't see any RH participation on this thread, and no fix comming.