Friday, 2021-04-02

*** muhaha has joined #airshipit12:45
*** openstackstatus has joined #airshipit14:30
*** ChanServ sets mode: +v openstackstatus14:30
airship-irc-bot<sean.eagan> Anyone know a cause/fix for this? ```Need to get 21.6 MB of archives. After this operation, 82.1 MB of additional disk space will be used. [91mE: You don't have enough free space in /var/cache/apt/archives/.``` https://zuul.openstack.org/builds?job_name=airship-images-publish15:34
airship-irc-bot<kk6740> too small vm15:36
airship-irc-bot<kk6740> and our images are monstrous in size15:36
airship-irc-bot<ratnopam.chakrabarti> Hi Team, can I please get some reviews on https://review.opendev.org/c/airship/treasuremap/+/779889 This is about subcluster-nw-catalogue. Thanks and Happy Good Friday to all :slightly_smiling_face:15:44
airship-irc-bot<sean.eagan> @kk6740 any quick fix for bigger VMs for this job? smaller images?15:51
airship-irc-bot<kk6740> lets check the Makefiles15:55
airship-irc-bot<kk6740> maybe a cleanup after push15:55
airship-irc-bot<kk6740> can help15:55
airship-irc-bot<kk6740> i think it would be fastest and best solution15:55
airship-irc-bot<sean.eagan> good idea. looks like we could run `make images clean` but doesn't seem multiple targets are supported by the ansible make module. i guess we could change that to a regular script which calls make.16:45
airship-irc-bot<kk6740> Just a simple shared delete script17:02
airship-irc-bot<kk6740> Docker rmi ...17:03
airship-irc-bot<kk6740> And include it into each make17:03
airship-irc-bot<sean.eagan> from what i can tell that is what `make clean` is already doing. took a crack at it here, hopefully i got the syntax right, new to ansible: https://review.opendev.org/c/airship/images/+/78460718:44
airship-irc-bot<kk6740> @sean.eagan just to understand, is it going to run after all images are build and pushed? or after each image is built/pushed18:51
airship-irc-bot<sean.eagan> after each image18:52
airship-irc-bot<sean.eagan> the top-level Makefile runs the targets you pass it for each image's Makefile in order18:53
airship-irc-bot<kk6740> so lets hope that every make file has clean target ;)18:54
airship-irc-bot<kk6740> @sean.eagan I’ve seen that u’ve created a toolbox image19:08
airship-irc-bot<kk6740> in quay19:08
airship-irc-bot<kk6740> but its empty for now, is that because nothing was merged yet?19:08
*** muhaha has quit IRC19:28
airship-irc-bot<sean.eagan> so when that toolbox krm-function was merged, the airshipctl image publish job started failing (for all images in airshipctl repo) because this one quay repo didn't exist yet, so i created it so that we will start getting images published again once the next patchset merges19:28
airship-irc-bot<sean.eagan> https://zuul.openstack.org/builds?job_name=airship-airshipctl-publish-image19:29
airship-irc-bot<kk6740> :+1:19:29
airship-irc-bot<kk6740> exactly what i was asking19:30
airship-irc-bot<kk6740> thank you19:30
airship-irc-bot<sean.eagan> i guess there is no way to rerun failed jobs in Zuul like there is with github actions19:31
airship-irc-bot<james.gu> @sean.eagan is v2.0 now the official branch for treasuremap v2 that replaces v2 branch?20:17
airship-irc-bot<ao129q> folks is there an issue with 32GB nodes?20:33
airship-irc-bot<ao129q> gate runner job is in queue for a while already, since yesterday actually20:34
airship-irc-bot<kk6740> it passed once i think20:34
airship-irc-bot<kk6740> but, the problem is there indeed20:34
airship-irc-bot<sean.eagan> @james.gu v2.0 is the GA release branch, so only stabilization changes should go there. v2 is for continued Airship 2 dev not tied to the GA release. However, it will shortly be renamed to master, see https://github.com/airshipit/treasuremap/issues/5021:12
airship-irc-bot<james.gu> Got it, Thanks Sean.21:13
*** muhaha has joined #airshipit21:15
*** muhaha has quit IRC21:32

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!