On 25 April 2018 at 18:50, Dusty Mabe <dusty@xxxxxxxxxxxxx> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > > On Sunday April 22nd we identified an issue with the describe-conversion-tasks > AWS API that was causing fedimg to fail when uploading images. I worked with > David Duncan from AWS (and Fedora contributor) to raise the issue with AWS > and get it resolved. The fix did not land in time for the RC compose that ran > last night so in order to publish images we need to: > > - - run fedimg and let it fail > - - identify the volume that was created > - - hardcode that volume ID into the fedimg code I am not familiar with fedimg, but instead of harcoding the volume ID it would be better to set it via a configuration file. So it would be easier to change later. > - - run fedimg a 2nd time to let it complete > > I'd like permission to perform these actions, which I'm calling open heart surgery > so that we can get AMIs out the door for F28. > > Dusty > -----BEGIN PGP SIGNATURE----- > > iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlrgsb8ACgkQMwLb1zlS > 5nEcYA//WSvIE2+4jxm75YamPGdb7DYXYyJ5ll0EhJ2MPiyxETkTHfOWSghAWITG > ltk6eht3fBtuCqIcU8pobFDO+YxTlZmEVuvZIhXX6XxHwTY2+c0iZhKp+BlRfY5W > uozHP/LMoLP9Uh4MreGyomUymjv8r9mCw9JCJ9hGizPbigLubjIRJ2J+0BWqyFvU > 7VHhi5yaVbgvlWs2QsNSr7201Re/3uJx4/PxADcAX2VNrl++inb6yPzNVveS23Th > w6Pkogbx8eK0ArhLtHQfaYhGqzgdJCkSgcnOl9lfWHp7tJmoLZoBRSw+fdPSzZuw > uCMHctqzcEHgypv2Vx6iPUJb5zrp73c+xpC6bXHCFz8j00GYkh16R/SG2ucJJ9WC > L0zvHs1uWqL91dlUV/1lnM2QejoaX2tFfrT8bUWdyCTVEu2A05Qx1bHwJRZAAzje > /c39xBai2hSpaCWmZaiHhXEdjNi4vkPkpSC9/ScGSgyuKe4cYlOtAR+OBCaiimyT > Jmg4dDAHisXW3CCVM33RrQdJoqk8jhN32+Gus1bxZlWkn7FSjKmcom5dfSxCUgVL > x3AD10US9VeFHQQ2lHQ4v6Yjb2lscJhIA5UZjr3oZY2+V1krVHTnw5crDjF5NqeM > wGxaJPPKrkEyiGnOYWm0xq3i7nffl10F7eC6HF99puY3ti+RcJk= > =XQf9 > -----END PGP SIGNATURE----- > _______________________________________________ > infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
