Re: 2wk atomic release candidate: 20170410
On 04/10/2017 11:10 AM, Dusty Mabe wrote: > > We are going to attempt to release the 20170410 images. > These images contain the following ostree version/commit: > > 25.102 > d3ed59ffb427870c536002cc88e3bcb72355921ff191e78612cb764c20ab1ec4 > We are going to delay release as we have found at least one bug that is observed when installing containerized openshift on top of this version of Atomic Host. I suspect this is a kernel regression, but am still investigating. Example error text from the origin-node service: origin-node[10803]: I0411 00:15:34.995594 10859 kubelet_node_status.go:377] Recording NodeHasNoDiskPressure event message for node 10.0.111.54 origin-node[10803]: I0411 00:15:34.995740 10859 kubelet_node_status.go:73] Attempting to register node 10.0.111.54 origin-node[10803]: I0411 00:15:35.001804 10859 kubelet_node_status.go:112] Node 10.0.111.54 was previously registered origin-node[10803]: I0411 00:15:35.001845 10859 kubelet_node_status.go:76] Successfully registered node 10.0.111.54 origin-node[10803]: I0411 00:15:35.033412 10859 kubelet_node_status.go:377] Recording NodeNotSchedulable event message for node 10.0.111.54 origin-node[10803]: I0411 00:15:35.073467 10859 manager.go:290] Recovery completed origin-node[10803]: I0411 00:15:35.159477 10859 conversion.go:133] failed to handle multiple devices for container. Skipping Filesystem stats origin-node[10803]: E0411 00:15:35.878364 10859 controller.go:176] Error removing 10.128.0.0/23 route from dev tun0: timed out waiting for the condition; if the route appears later it will not be deleted. origin-node[10803]: F0411 00:15:35.878402 10859 node.go:350] error: SDN node startup failed: exit status 2 systemd[1]: origin-node.service: Main process exited, code=exited, status=255/n/a Dusty ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #253: lower case vs Initial Cap in Labels
yzhang added a new comment to an issue you are following: `` I've updated the guidelines at https://fedoraproject.org/wiki/Container:Guidelines `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/253 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Re: 2wk atomic release candidate: 20170410
Corrected URLs On 04/10/2017 11:10 AM, Dusty Mabe wrote: > > We are going to attempt to release the 20170410 images. > These images contain the following ostree version/commit: > > 25.102 > d3ed59ffb427870c536002cc88e3bcb72355921ff191e78612cb764c20ab1ec4 > > The atomic host VM images are here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-10270410.0/compose/CloudImages/x86_64/images/ https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170410.0/compose/CloudImages/x86_64/images/ > > The ISO image is here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-10270410.0/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-10270410.0.iso https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170410.0/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20170410.0.iso > > The AMIs are here: > > Fedora-Atomic-25-20170410.0.x86_64 EC2 (ap-northeast-1) ami-4810332f hvm > standard > Fedora-Atomic-25-20170410.0.x86_64 EC2 (ap-southeast-1) ami-8d7cc2ee hvm > standard > Fedora-Atomic-25-20170410.0.x86_64 EC2 (ap-southeast-2) ami-eeebe58d hvm > standard > Fedora-Atomic-25-20170410.0.x86_64 EC2 (eu-central-1) ami-3544975a hvm > standard > Fedora-Atomic-25-20170410.0.x86_64 EC2 (eu-west-1) ami-e5bf8483 hvm > standard > Fedora-Atomic-25-20170410.0.x86_64 EC2 (sa-east-1) ami-841577e8 hvm > standard > Fedora-Atomic-25-20170410.0.x86_64 EC2 (us-east-1) ami-796be56f hvm > standard > Fedora-Atomic-25-20170410.0.x86_64 EC2 (us-west-1) ami-4e7e5b2e hvm > standard > Fedora-Atomic-25-20170410.0.x86_64 EC2 (us-west-2) ami-1d88187d hvm > standard > Fedora-Atomic-25-20170410.0.x86_64 EC2 (ap-northeast-1) ami-a41536c3 hvm > gp2 > Fedora-Atomic-25-20170410.0.x86_64 EC2 (ap-southeast-1) ami-5f7dc33c hvm > gp2 > Fedora-Atomic-25-20170410.0.x86_64 EC2 (ap-southeast-2) ami-42ece221 hvm > gp2 > Fedora-Atomic-25-20170410.0.x86_64 EC2 (eu-central-1) ami-c94a99a6 hvm > gp2 > Fedora-Atomic-25-20170410.0.x86_64 EC2 (eu-west-1) ami-26be8540 hvm > gp2 > Fedora-Atomic-25-20170410.0.x86_64 EC2 (sa-east-1) ami-ce1a78a2 hvm > gp2 > Fedora-Atomic-25-20170410.0.x86_64 EC2 (us-east-1) ami-486ae45e hvm > gp2 > Fedora-Atomic-25-20170410.0.x86_64 EC2 (us-west-1) ami-db7c59bb hvm > gp2 > Fedora-Atomic-25-20170410.0.x86_64 EC2 (us-west-2) ami-838717e3 hvm > gp2 > > The diff between this and the previous released version is: > > ostree diff commit old: > 6a71adb06bc296c19839e951c38dc0b71ee5d7a82262fef9612f256f0c2a70da > ostree diff commit new: > d3ed59ffb427870c536002cc88e3bcb72355921ff191e78612cb764c20ab1ec4 > Upgraded: > GeoIP 1.6.9-2.fc24.x86_64 -> 1.6.10-1.fc25.x86_64 > GeoIP-GeoLite-data 2017.01-1.fc25.noarch -> 2017.04-1.fc25.noarch > audit 2.7.3-1.fc25.x86_64 -> 2.7.4-1.fc25.x86_64 > audit-libs 2.7.3-1.fc25.x86_64 -> 2.7.4-1.fc25.x86_64 > audit-libs-python 2.7.3-1.fc25.x86_64 -> 2.7.4-1.fc25.x86_64 > audit-libs-python3 2.7.3-1.fc25.x86_64 -> 2.7.4-1.fc25.x86_64 > cloud-init 0.7.8-6.fc25.noarch -> 0.7.9-4.fc25.noarch > cockpit-bridge 135-1.fc25.x86_64 -> 137-1.fc25.x86_64 > cockpit-docker 135-1.fc25.x86_64 -> 137-1.fc25.x86_64 > cockpit-networkmanager 135-1.fc25.noarch -> 137-1.fc25.noarch > cockpit-ostree 135-1.fc25.x86_64 -> 137-1.fc25.x86_64 > cockpit-system 135-1.fc25.noarch -> 137-1.fc25.noarch > curl 7.51.0-4.fc25.x86_64 -> 7.51.0-6.fc25.x86_64 > file 5.29-3.fc25.x86_64 -> 5.29-4.fc25.x86_64 > file-libs 5.29-3.fc25.x86_64 -> 5.29-4.fc25.x86_64 > gdbm 1.12-1.fc25.x86_64 -> 1.13-1.fc25.x86_64 > glusterfs 3.10.0-1.fc25.x86_64 -> 3.10.1-1.fc25.x86_64 > glusterfs-client-xlators 3.10.0-1.fc25.x86_64 -> 3.10.1-1.fc25.x86_64 > glusterfs-fuse 3.10.0-1.fc25.x86_64 -> 3.10.1-1.fc25.x86_64 > glusterfs-libs 3.10.0-1.fc25.x86_64 -> 3.10.1-1.fc25.x86_64 > gssproxy 0.7.0-2.fc25.x86_64 -> 0.7.0-3.fc25.x86_64 > kernel 4.9.14-200.fc25.x86_64 -> 4.10.8-200.fc25.x86_64 > kernel-core 4.9.14-200.fc25.x86_64 -> 4.10.8-200.fc25.x86_64 > kernel-modules 4.9.14-200.fc25.x86_64 -> 4.10.8-200.fc25.x86_64 > libcurl 7.51.0-4.fc25.x86_64 -> 7.51.0-6.fc25.x86_64 > libsolv 0.6.26-1.fc25.x86_64 -> 0.6.26-3.fc25.x86_64 > linux-firmware 20161205-69.git91ddce49.fc25.noarch -> > 20170313-72.git695f2d6d.fc25.noarch > nfs-utils 1:2.1.1-2.rc1.fc25.x86_64 -> 1:2.1.1-3.rc1.fc25.x86_64 > nss 3.28
[atomic-wg] Issue #248: Container Guidelines: Layered Images used as a base for other Layered Builds
eslobodo added a new comment to an issue you are following: `` Similarly with the uppercase first letters in labels (Name, Version, Release...). Are these really required to be uppercase or should the doc be updated? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/248 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #266: rpmostree_compose Ansible module
trishnag reported a new issue against the project: `atomic-wg` that you are following: `` As for Ansible module for atomic host we have `atomic_host` and `atomic_image` modules written. The plan/purpose of this ticket is to have rpm-ostree modules get done for Ansible as well. We can perhaps have all the `rpm-ostree` options as Ansible modules so that we really do not need to execute rpm-ostree commands as part of `shell`/`command` modules in Ansible. I wrote `rpmostree compose` Ansible module: https://github.com/ansible/ansible/pull/23209. Can anyone volunteer to review the PR? Bringing in @dustymabe @jberkus @walters @jlebon here. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/266 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
