Re: Heads up! Influence of our recent Mock/Proxy changes on Lago jobs

But we should (CCing Sandro). I do not see any mistrust here. Even if we can make our infra behave abnormal way there is no warranty that such RPM will not get wild (or be prevented from going out). We cannot clear caches of all of our users. I even not sure how repoman will behave when oVirt releases are composed in this case, it does not compare RPM content and assumes that they are immutable as designed. So makes sense to check this. This can take time, every maintainer has his own (bad) habits, and not This is correct. So sounds like we need to send an announcement that RPM versions are supposed to change when content change and see who have issues with this and try to analyse why and help if needed. In the meantime we need to be resilient to such issues if we can. We Meantime if we need to support this we have to disable caching for everything minus repos we know follow the rules. But I would insist that this is not normal situation and we need to have an idea of how we notify people to fix it and how we can help. And we are not fixing the world. yum is there for a long time and world is ok. It is just we have problem in our stuff we need to fix so we can use all the systems the world designed for us. Afaik we have a configuration on proxy server that caches only immutable content for yum repos? So this is indeed an interesting discovery! Anton. -- Anton Marchukov Senior Software Engineer - RHEV CI - Red Hat