Fedora 19 Beta RC AMI's

[Dennis Gilmore]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi All

there is some ami's in us-east-1 on ec2
ami-21e08848 : us-east-1 image for i386
ami-f9e08890 : us-east-1 image for x86_64

the ec2 images are exactly the same as at
http://dl.fedoraproject.org/pub/alt/stage/19-Beta-RC4/Images/

I've compressed the qcow2 images and put up xz compressed raw images


Dennis
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
>
> iEYEARECAAYFAlGeg9QACgkQkSxm47BaWffJHQCfa6O6879+KP2rHv5842Ead6ux
> jcwAnj8VBzQ8s7/K/Pqofn2/jenhucZ+
> =l3Uq
> -----END PGP SIGNATURE-----
>

[Matthew Miller]

On Thu, May 23, 2013 at 04:02:11PM -0500, Dennis Gilmore wrote:
>  there is some ami's in us-east-1 on ec2
>  ami-21e08848 : us-east-1 image for i386
>  ami-f9e08890 : us-east-1 image for x86_64
>  the ec2 images are exactly the same as at
>  http://dl.fedoraproject.org/pub/alt/stage/19-Beta-RC4/Images/
>  I've compressed the qcow2 images and put up xz compressed raw images 
Awesome -- thanks Dennis!

Note that these have the same caveats as in the message I sent earlier
today. Particularly, the cloud-init bug which delays the ability to log in
after booting the image.

-- 
Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  <mattdm(a)fedoraproject.org&gt;

[Vitaly Kuznetsov]

Dennis Gilmore <dennis(a)ausil.us&gt; writes:

>  Hi All
>
>  there is some ami's in us-east-1 on ec2
>  ami-21e08848 : us-east-1 image for i386
>  ami-f9e08890 : us-east-1 image for x86_64
>  
Hi Dennis!

I've tried running them but they're failing to boot. The console log
ends like this:

"root (hd0)
 Filesystem type is ext2fs, using whole disk
kernel /vmlinuz-2.6.32-358.6.1.el6.x86_64 ro
 root=/dev/mapper/GuestVolGroup00-r
oot rd_LVM_LV=GuestVolGroup00/root rd_NO_LUKS rd_NO_MD rd_NO_DM
 LANG=en_US.UTF-
8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us console=ttyS0
 crashkern
el=auto

Error 15: File not found

Press any key to continue..."

I'm a bit confused with RHEL6 kernel (x86_64 for both AMIs) trying to
boot here, I guess there is a mistake in default grub conf. I've used
default kernel/ramdisk image ids.

P.S. It would be nice to have 'delete on termination = yes' for the
root volume in the default block map as well :-)

-- 
  Vitaly Kuznetsov

[Dennis Gilmore]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

El Thu, 23 May 2013 16:02:11 -0500
Dennis Gilmore <dennis(a)ausil.us&gt; escribió:
>  -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>  
>  Hi All
>  
>  there is some ami's in us-east-1 on ec2
>  ami-21e08848 : us-east-1 image for i386
>  ami-f9e08890 : us-east-1 image for x86_64
>  
due to an issue with how we uploaded the images they are not booting.
ive fixed the upload script and reuploaded. the new amis are as follows

ami-a73a51ce : us-east-1 image for i386
ami-6f3b5006 : us-east-1 image for x86_64

I have tested that they boot.

Dennis
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
>
> iEYEARECAAYFAlGf3EwACgkQkSxm47BaWffvmQCgtLJBpqu1nCiw8BydgsWFtbMV
> gqkAn1l4pIrYAOQ8FE792jXTxAlr6hsb
> =/4hL
> -----END PGP SIGNATURE-----
>

[Vitaly Kuznetsov]

Dennis Gilmore <dennis(a)ausil.us&gt; writes:

>  El Thu, 23 May 2013 16:02:11 -0500
>  Dennis Gilmore <dennis(a)ausil.us&gt; escribió:
>
>  ami-a73a51ce : us-east-1 image for i386
>  ami-6f3b5006 : us-east-1 image for x86_64
>
>  I have tested that they boot.
>  
Hi Dennis,

thanks for jumping into this!

I've tested them. Here is the list of discrepancies (between these and F18 AMIs):

1) There is no NETWORKING_IPV6=no setting in /etc/sysconfig/network (and
there is still no ipv6 in EC2)

2) There is no 'PasswordAuthentication no' setting in
/etc/ssh/sshd_config (it was there for a long time)

3) We have slightly different package set:
New packages:
['acl', 'authconfig', 'dracut-nohostonly',
'dracut-norescue',
'jbigkit-libs', 'libtiff', 'libverto', 'libwebp',
'make', 'mtools',
'nettle', 'newt', 'newt-python', 'openssl',
'p11-kit-trust',
'python-pillow', 'slang', 'syslinux',
'syslinux-extlinux']

Missing packages:
 ['dbus-glib', 'dbus-python', 'ebtables', 'file',
'gamin',
 'gobject-introspection', 'hwdata', 'libdb4',
'nss-myhostname',
 'psmisc', 'pygobject3-base', 'python-decorator',
'python-imaging',
 'python-slip', 'python-slip-dbus', 'tmpwatch']

4) cloud-init is not handling userdata scripts any more. I've tried
simple scripts (like 'touch /test_file_1'),  multipart/mixed, ... -
nothing works for me now. I can't find any error in
/var/log/cloud-init.log, I can see my scripts in
/var/lib/cloud/instance/scripts/ (only if I use multipart/mixed) but
they never were executed. Can anyone shed some light into this?

4+) I can also see cloud-init fails to set hostname:
/var/log/cloud-init.log:
May 27 10:19:59 localhost [CLOUDINIT] util.py[WARNING]: Failed to set
the hostname to ip-10-154-149-222.ec2.internal (ip-10-154-149-222)
May 27 10:19:59 localhost [CLOUDINIT] util.py[WARNING]: Running
set_hostname (<module 'cloudinit.config.cc_set_hostname' from
'/usr/lib/python2.7/site-packages/cloudinit/config/cc_set_hostname.pyc'>)
failed
May 27 10:20:24 localhost [CLOUDINIT] util.py[WARNING]: Failed to write
hostname ip-10-154-149-222.ec2.internal to /var/lib/cloud/data/previous-hostname

and a corresponding entry in /var/log/audit/audit.log:
/var/log/audit/audit.log:type=USER_AVC msg=audit(1369645724.117:16):
pid=199 uid=81 auid=4294967295 ses=4294967295
subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc:  denied
{ send_msg } for msgtype=method_return dest=:1.2 spid=520 tpid=519
scontext=system_u:system_r:systemd_hostnamed_t:s0
tcontext=system_u:system_r:initrc_t:s0 tclass=dbus
exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'
/var/log/audit/audit.log:type=USER_AVC msg=audit(1369645749.524:17):
pid=199 uid=81 auid=4294967295 ses=4294967295
subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc:  denied
{ send_msg } for msgtype=method_return dest=:1.4 spid=520 tpid=522
scontext=system_u:system_r:systemd_hostnamed_t:s0
tcontext=system_u:system_r:initrc_t:s0 tclass=dbus
exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'

-- 
  Vitaly Kuznetsov

[Matthew Miller]

On Mon, May 27, 2013 at 12:49:22PM +0200, Vitaly Kuznetsov wrote:
>  1) There is no NETWORKING_IPV6=no setting in /etc/sysconfig/network
> (and
>  there is still no ipv6 in EC2) 
There might be in OpenStack environments. Are there negative consequences

>  2) There is no 'PasswordAuthentication no' setting in
>  /etc/ssh/sshd_config (it was there for a long time) 
Hmmm; that was dropped from the kickstart from F15 to F16, with the comment
"let cloud-init setup sshd". Can we reverify this after the cloud-init
SELinux bug is fixed? 

https://bugzilla.redhat.com/show_bug.cgi?id=964006


>  3) We have slightly different package set: 
At least partly intentional. Reordering the list a bit and commenting...

>  New packages:
>  ['acl',  
Added to @core comps.

>  'authconfig', 
Ditto; also, good to have for configuration. I could see removing this if
people thing it's best.

>  'dracut-nohostonly', 'dracut-norescue', 
First of these keeps the image portable (next cut will be to have a
"dracut-cloud" module to replace "nohostonly"). The second prevents
the 
rescue image from being created to save space and because at least in EC2 it
can't really be used anyway.

>  'jbigkit-libs', 'libtiff',
>  'libwebp', 
>  'python-pillow', 
cloud-init deps. There are more, many of which seem equally unfortunate in a
minimal image.

>  'libverto' 
pulled in by krb5-libs as of 1.11.1-4.

>  'make', 
>  'openssl'
>  'newt', 'newt-python', 'p11-kit-trust',
>  'slang' 
Pulled in by authconfig; see above. Altogether, removing authconfig would
save 6.8 mb installed space.


>  'mtools', 
Pulled in by extlinux; https://bugzilla.redhat.com/show_bug.cgi?id=928055


>  'nettle',  
systemd pulls this in via gnutls, which is used _only_ for libmicrohttpd,
which in turn is used only by the journald gateway, which is a) off by
default and b) not ever supposed to be turned on except for developers. I
have an open request to make that a subpackage at the very least, but the
systemd packagers don't seem interested. See
https://bugzilla.redhat.com/show_bug.cgi?id=908081


>  'syslinux', 'syslinux-extlinux'] 
On purpose, so we have a lightweight bootloader for non pv-grub cloud
services.



>  Missing packages:
>   ['dbus-glib', 'dbus-python', 'ebtables', 'file',
> 'gamin',
>   'gobject-introspection', 'hwdata', 'libdb4',
> 'nss-myhostname',
>   'psmisc', 'pygobject3-base', 'python-decorator',
> 'python-imaging',
>   'python-slip', 'python-slip-dbus', 'tmpwatch'] 
I think this is all intentional. tmpwatch is now handled by systemd. Anyone
feel tha tany of these really should be there?



>  4) cloud-init is not handling userdata scripts any more. I've
> tried
>  simple scripts (like 'touch /test_file_1'),  multipart/mixed, ... -
>  nothing works for me now. I can't find any error in
>  /var/log/cloud-init.log, I can see my scripts in
>  /var/lib/cloud/instance/scripts/ (only if I use multipart/mixed) but
>  they never were executed. Can anyone shed some light into this? 
I _think_ this is probably just the above-mentioned bug. Retest after that's
fixed?

>  4+) I can also see cloud-init fails to set hostname: 
And this _is_ the above-mentioned bug. :)


-- 
Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  <mattdm(a)fedoraproject.org&gt;

[Vitaly Kuznetsov]

Matthew Miller <mattdm(a)fedoraproject.org&gt; writes:

>  On Mon, May 27, 2013 at 12:49:22PM +0200, Vitaly Kuznetsov wrote:
> > 1) There is no NETWORKING_IPV6=no setting in /etc/sysconfig/network (and
> > there is still no ipv6 in EC2)
>
>  There might be in OpenStack environments. Are there negative consequences
>  
Not aware of anything real but I can imaging something trying to use
ipv6 once it's up. Maybe it's another good candidate for cloud-init module.

> > 2) There is no 'PasswordAuthentication no' setting in
> > /etc/ssh/sshd_config (it was there for a long time)
>
>  Hmmm; that was dropped from the kickstart from F15 to F16, with the comment
>  "let cloud-init setup sshd". Can we reverify this after the cloud-init
>  SELinux bug is fixed? 
>
>  https://bugzilla.redhat.com/show_bug.cgi?id=964006 
Sure, I'll do new testing as soon as we have new AMIs.

> > Missing packages:
> >  ['dbus-glib', 'dbus-python', 'ebtables', 'file',
> 'gamin',
> >  'gobject-introspection', 'hwdata', 'libdb4',
> 'nss-myhostname',
> >  'psmisc', 'pygobject3-base', 'python-decorator',
> 'python-imaging',
> >  'python-slip', 'python-slip-dbus', 'tmpwatch']
>
>  I think this is all intentional. tmpwatch is now handled by systemd. Anyone
>  feel tha tany of these really should be there? 
file(1) is widely used in scripting ... but I'm not sure it's the criterion.

-- 
  Vitaly Kuznetsov