October 2017 - Atomic Working Group (ARCHIVED)

2wk atomic release candidate: 20171016

by Dusty Mabe

Tomorrow we will attempt to release the 20171016 images. These images contain the following ostree version/commit: 26.150 d518b37c348eb814093249f035ae852e7723840521b4bcb4a271a80b5988c44a The atomic host VM images are here: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-20171... The ISO image is here: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-20171... The AMIs are here: Fedora-Atomic-26-20171016.0.x86_64 EC2 (ap-northeast-1) ami-05f12963 hvm standard Fedora-Atomic-26-20171016.0.x86_64 EC2 (ap-southeast-1) ami-a71b5ec4 hvm standard Fedora-Atomic-26-20171016.0.x86_64 EC2 (ap-southeast-2) ami-e5cd2087 hvm standard Fedora-Atomic-26-20171016.0.x86_64 EC2 (eu-central-1) ami-3a5ae455 hvm standard Fedora-Atomic-26-20171016.0.x86_64 EC2 (eu-west-1) ami-37578b4e hvm standard Fedora-Atomic-26-20171016.0.x86_64 EC2 (sa-east-1) ami-b2d2acde hvm standard Fedora-Atomic-26-20171016.0.x86_64 EC2 (us-east-1) ami-cf8a5cb5 hvm standard Fedora-Atomic-26-20171016.0.x86_64 EC2 (us-west-1) ami-7bcefc1b hvm standard Fedora-Atomic-26-20171016.0.x86_64 EC2 (us-west-2) ami-5417d72c hvm standard Fedora-Atomic-26-20171016.0.x86_64 EC2 (ap-northeast-1) ami-19f32b7f hvm gp2 Fedora-Atomic-26-20171016.0.x86_64 EC2 (ap-southeast-1) ami-ad1b5ece hvm gp2 Fedora-Atomic-26-20171016.0.x86_64 EC2 (ap-southeast-2) ami-cacc21a8 hvm gp2 Fedora-Atomic-26-20171016.0.x86_64 EC2 (eu-central-1) ami-165ae479 hvm gp2 Fedora-Atomic-26-20171016.0.x86_64 EC2 (eu-west-1) ami-15528e6c hvm gp2 Fedora-Atomic-26-20171016.0.x86_64 EC2 (sa-east-1) ami-36d5ab5a hvm gp2 Fedora-Atomic-26-20171016.0.x86_64 EC2 (us-east-1) ami-4f8d5b35 hvm gp2 Fedora-Atomic-26-20171016.0.x86_64 EC2 (us-west-1) ami-f4cffd94 hvm gp2 Fedora-Atomic-26-20171016.0.x86_64 EC2 (us-west-2) ami-0016d678 hvm gp2 The diff between this and the previous released version is: ostree diff commit old: 541abd650d1ffb3929e2ba8114436a0b04ee41da76a691af669dd037589a1421 ostree diff commit new: d518b37c348eb814093249f035ae852e7723840521b4bcb4a271a80b5988c44a Upgraded: GeoIP-GeoLite-data 2017.07-1.fc26.noarch -> 2017.10-1.fc26.noarch boost-iostreams 1.63.0-8.fc26.x86_64 -> 1.63.0-9.fc26.x86_64 boost-program-options 1.63.0-8.fc26.x86_64 -> 1.63.0-9.fc26.x86_64 boost-random 1.63.0-8.fc26.x86_64 -> 1.63.0-9.fc26.x86_64 boost-regex 1.63.0-8.fc26.x86_64 -> 1.63.0-9.fc26.x86_64 boost-system 1.63.0-8.fc26.x86_64 -> 1.63.0-9.fc26.x86_64 boost-thread 1.63.0-8.fc26.x86_64 -> 1.63.0-9.fc26.x86_64 cockpit-bridge 151-1.fc26.x86_64 -> 151-2.fc26.x86_64 cockpit-docker 151-1.fc26.x86_64 -> 151-2.fc26.x86_64 cockpit-networkmanager 151-1.fc26.noarch -> 151-2.fc26.noarch cockpit-ostree 151-1.fc26.x86_64 -> 151-2.fc26.x86_64 cockpit-system 151-1.fc26.noarch -> 151-2.fc26.noarch container-storage-setup 0.7.0-1.git4ca59c5.fc26.noarch -> 0.8.0-1.git1d27ecf.fc26.noarch criu 3.3-2.fc26.x86_64 -> 3.5-1.fc26.x86_64 dnsmasq 2.76-3.fc26.x86_64 -> 2.76-5.fc26.x86_64 kernel 4.12.14-300.fc26.x86_64 -> 4.13.5-200.fc26.x86_64 kernel-core 4.12.14-300.fc26.x86_64 -> 4.13.5-200.fc26.x86_64 kernel-modules 4.12.14-300.fc26.x86_64 -> 4.13.5-200.fc26.x86_64 kubernetes 1.6.7-1.fc26.x86_64 -> 1.7.3-1.fc26.x86_64 kubernetes-client 1.6.7-1.fc26.x86_64 -> 1.7.3-1.fc26.x86_64 kubernetes-master 1.6.7-1.fc26.x86_64 -> 1.7.3-1.fc26.x86_64 kubernetes-node 1.6.7-1.fc26.x86_64 -> 1.7.3-1.fc26.x86_64 nspr 4.16.0-1.fc26.x86_64 -> 4.17.0-1.fc26.x86_64 nss 3.32.1-1.0.fc26.x86_64 -> 3.33.0-1.0.fc26.x86_64 nss-softokn 3.32.0-1.2.fc26.x86_64 -> 3.33.0-1.0.fc26.x86_64 nss-softokn-freebl 3.32.0-1.2.fc26.x86_64 -> 3.33.0-1.0.fc26.x86_64 nss-sysinit 3.32.1-1.0.fc26.x86_64 -> 3.33.0-1.0.fc26.x86_64 nss-tools 3.32.1-1.0.fc26.x86_64 -> 3.33.0-1.0.fc26.x86_64 nss-util 3.32.0-1.0.fc26.x86_64 -> 3.33.0-1.0.fc26.x86_64 python3 3.6.2-7.fc26.x86_64 -> 3.6.2-8.fc26.x86_64 python3-libs 3.6.2-7.fc26.x86_64 -> 3.6.2-8.fc26.x86_64 rpm-ostree 2017.8-2.fc26.x86_64 -> 2017.9-1.fc26.x86_64 rpm-ostree-libs 2017.8-2.fc26.x86_64 -> 2017.9-1.fc26.x86_64 sudo 1.8.20p2-1.fc26.x86_64 -> 1.8.21p2-1.fc26.x86_64 system-python 3.6.2-7.fc26.x86_64 -> 3.6.2-8.fc26.x86_64 system-python-libs 3.6.2-7.fc26.x86_64 -> 3.6.2-8.fc26.x86_64 vim-minimal 2:8.0.1097-1.fc26.x86_64 -> 2:8.0.1176-1.fc26.x86_64 The most notable changes in this release are a new version of the kernel kubernetes, rpm-ostree and dnsmasq. The dnsmasq update fixes quite a few CVEs. They are listed below: CVE-2017-14491 dnsmasq: heap overflow in the code responsible for building DNS replies - https://bugzilla.redhat.com/show_bug.cgi?id=1495409 CVE-2017-14492 dnsmasq: heap overflow in the IPv6 router advertisement code - https://bugzilla.redhat.com/show_bug.cgi?id=1495410 CVE-2017-14493 dnsmasq: stack buffer overflow in the DHCPv6 code - https://bugzilla.redhat.com/show_bug.cgi?id=1495411 CVE-2017-14494 dnsmasq: information leak in the DHCPv6 relay code - https://bugzilla.redhat.com/show_bug.cgi?id=1495412 CVE-2017-14495 dnsmasq: memory exhaustion vulnerability in the EDNS0 code - https://bugzilla.redhat.com/show_bug.cgi?id=1495415 CVE-2017-14496 dnsmasq: integer underflow leading to buffer over-read in the EDNS0 code - https://bugzilla.redhat.com/show_bug.cgi?id=1495416 Dusty

6 years, 6 months

1
0
0 / 0

[atomic-wg] Issue #325: atomic host two week release emails don't make it to the atomic-devel list

by Michael Scherer

misc added a new comment to an issue you are following: `` IT is asking to me what is the IP used to connect. I suspect that's bastion01 and likely another one ? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/325

6 years, 6 months

1
0
0 / 0

[atomic-wg] Issue #281: Figure out comprehensive strategy for atomic host container storage

by Colin Walters

walters added a new comment to an issue you are following: `` One thing that came up in a quick IRC discussion was: > <vgoyal> walters: last I checked that xfs on rootfs does not enable quota by default. > <vgoyal> walters: and with overlayfs openshift needs quota support to limit max container size I'd agree we should probably make this change by default. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/281

6 years, 6 months

1
0
0 / 0

[atomic-wg] Issue #281: Figure out comprehensive strategy for atomic host container storage

by Vivek Goyal

vgoyal added a new comment to an issue you are following: `` > Hum? What do you mean by overlay on overlay? I don' t know why anyone would do that. I thought docker will setup overlay mount points for each container. And if rootfs is overlay, this becomes overlay on top of overlay? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/281

6 years, 6 months

1
0
0 / 0

[atomic-wg] Issue #281: Figure out comprehensive strategy for atomic host container storage

by Colin Walters

walters added a new comment to an issue you are following: `` Hum? What do you mean by overlay on overlay? I don' t know why anyone would do that. Try grabbing an image from [today's compose](https://kojipkgs.fedoraproject.org/compose/branched/Fedora-27-20... and boot it - for example with the Vagrant box, we use all 40GB by default for the rootfs. For infrastructure clouds we'll expand to whatever the cloud does. We don't use a separate LV for containers by default, but that can be enabled via cloud-init for those cases. (For the Vagrant box you'd have to shut down docker first) `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/281

6 years, 6 months

1
0
0 / 0

[atomic-wg] Issue #302: F26s will not provision on Azure

by Dusty Mabe

dustymabe added a new comment to an issue you are following: `` for the final bug - @baude, can you test [this image](https://kojipkgs.fedoraproject.org//work/tasks/8412/22368412/Fedor... from today's rawhide compose and tell me if you have success on azure `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/302

6 years, 6 months

1
0
0 / 0

[atomic-wg] Issue #281: Figure out comprehensive strategy for atomic host container storage

by Vivek Goyal

vgoyal added a new comment to an issue you are following: `` Not sure why do we want to consume whole disk/VG by default. I am little concerned if people have tested overlay on top of overlay for container runtime and what are the issues involved. I guess once F27 makes overlay its rootfs and container runtime setup overaly on top, we will come to know. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/281

6 years, 6 months

1
0
0 / 0

[Fedocal] Reminder meeting : Atomic Working Group Weekly Meeting

by dusty＠dustymabe.com

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2017-10-11 from 17:00:00 to 18:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: This is the meeting for the Fedora Atomic Working Group. We typically go over previous meeting action items and then cover all tickets with the meeting keyword: https://pagure.io/atomic-wg/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/Atomic_WG#Meetings](https://fedoraproject.... Source: https://apps.fedoraproject.org/calendar/meeting/6952/

6 years, 6 months

1
0
0 / 0

[atomic-wg] Issue #294: VFAD: Docs Treasure Hunt

by Dusty Mabe

The status of the issue: `VFAD: Docs Treasure Hunt` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe. https://pagure.io/atomic-wg/issue/294

6 years, 6 months

1
0
0 / 0

[atomic-wg] Issue #281: Figure out comprehensive strategy for atomic host container storage

by Dusty Mabe

The status of the issue: `Figure out comprehensive strategy for atomic host container storage` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe. https://pagure.io/atomic-wg/issue/281

6 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) October 2017