#4808: EC2 image creation process

[Fedora Release Engineering]

#4808: EC2 image creation process
----------------------+-----------------------------------------------------
  Reporter:  jforbes  |       Owner:  rel-eng at lists.fedoraproject.org
      Type:  task     |      Status:  new                            
 Milestone:           |   Component:  koji                           
Resolution:           |    Keywords:                                 
----------------------+-----------------------------------------------------
Comment (by jgreguske):

 I was able to get past this. The issue is related to
 https://bugzilla.redhat.com/show_bug.cgi?id=729340.

 As part of the upload process an instance is started and an EBS volume
 attached to it. The image is then dd'd over ssh right to the block device
 exposed in the instance. Thanks to the bug, the device file was not being
 named what the script expected, so it was in effect, copying the image
 into /dev and running out of space.

 At this point I believe I have a working upload script. The sample image I
 used did not appear to boot due to a systemd issue though:

 [17516826.508852] systemd-getty-generator[223]: Failed to create symlink
 from /lib/systemd/system/serial-getty at .service to
 /run/systemd/generator/getty.target.wants/serial-getty at hvc0.service: File
 exists

 so I think I may be using a bad image. If there is a known-working image
 in Koji I can certainly try with that.

-- 
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4808#comment:14>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project