While working on fixing[0] the masher today I noticed that wait_for_sync() only makes sure that one arch has made it to the master mirror, rather than making sure they all made it. After asking about this in #fedora-releng, dgilmore suggested that we could work around the current issue by hardcoding x86_64. Right now the masher blows up because it's trying to find aarch64 where the primary arches would be. I'm working on adding the ability for Bodhi to know where alternative arches are stored as well, but since Bodhi only checks one arch anyway Dennis's suggestion makes a lot of sense (all our repos have x86_64 as a primary arch). I've attached the patch I am proposing to this e-mail. What do you think? [0] https://github.com/fedora-infra/bodhi/issues/1343
From 72b062de6687502a9cd9498e70d2cd6c084527d0 Mon Sep 17 00:00:00 2001
From: Randy Barlow <randy@xxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 10 Mar 2017 15:11:10 -0500
Subject: [PATCH] Hard code wait_for_sync() to look for x86_64.
---
bodhi/server/consumers/masher.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bodhi/server/consumers/masher.py b/bodhi/server/consumers/masher.py
index 38e1eec3..978963fb 100644
--- a/bodhi/server/consumers/masher.py
+++ b/bodhi/server/consumers/masher.py
@@ -750,7 +750,7 @@ class MasherThread(threading.Thread):
force=True,
)
mash_path = os.path.join(self.path, self.id)
- arch = os.listdir(mash_path)[0]
+ arch = 'x86_64'
release = self.release.id_prefix.lower().replace('-', '_')
request = self.request.value
--
2.12.0
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
