Before rebuilding found containers, yum repo must be created and contain required updated RPMs, which is done in ODCS. freshmaker calls ODCS API to request a new compose and will be used as the repo.
Signed-off-by: Chenxiong Qi cqi@redhat.com
I'm afraid we need another approach rather than checking and waiting for the compose to be done, otherwise Freshmaker will block on waiting for the compose to finish.
Blocking is just the first step. Will move to FACTORY-1117 eventually.
@qwan; This has been agreed on as a temporary solution. The proper way is to publish message in ODCS once the compose is done. But in the meantime this does not hurt a lot. Of course once we deploy and start rebuilding things, we should consider this as a priority to make the rebuilds faster. but it is not blocker for deployment.
+1
XXX - this needs to log the compose id or some information so we can find the failure in ODCS.
TODO - this should log the ODCS compose id (or some other info) so an admin watching freshmaker logs can go and also watch the odcs logs.
rebased
Log compose URL os that it could be convenient for tracking latest compose status from ODCS server.
Test failed due to 1) no odcs client is installed 2) python3-koji hasn't been installed as well 3) wired, BrewSignRPMHanlder is still detected, but they should be fixed already.
python3-koji
BrewSignRPMHanlder
Pull-Request has been merged by cqi
Before rebuilding found containers, yum repo must be created and contain
required updated RPMs, which is done in ODCS. freshmaker calls ODCS API
to request a new compose and will be used as the repo.
Signed-off-by: Chenxiong Qi cqi@redhat.com