- Atomic Working Group (ARCHIVED) - Fedora mailing-lists

[atomic-wg] PR #515: Update Two Week release steps with latest information
by Sinny Kumari 19 Nov '18

19 Nov '18

sinnykumari opened a new pull-request against the project: `atomic-wg` that you are following: `` Update Two Week release steps with latest information `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/pull-request/515

3 7

[atomic-wg] Issue #497: Add VARIANT_ID=container to /etc/os-release
by Colin Walters 09 Nov '18

09 Nov '18

walters reported a new issue against the project: `atomic-wg` that you are following: `` See https://bugzilla.redhat.com/show_bug.cgi?id=1542060 Probably the "clean" fix is a new `fedora-release-container`. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/497

2 4

[atomic-wg] Issue #512: no openshift origin less than 3.11 for Fedora 29 Atomic Host
by Dusty Mabe 06 Nov '18

06 Nov '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` We've investigated the systemd `Delegate=true` API issue before [1](https://pagure.io/atomic-wg/issue/452) [2](https://pagure.io/atomic-wg/issue/510). runc was [fixed upstream](https://github.com/opencontainers/runc/pull/1776) but this fix only made it into openshift origin 3.11 (kube 1.11); keep in mind runc is vendored in openshift/kube so the version of the runc rpm on the system doesn't matter. The API was [brought back](https://pagure.io/atomic-wg/issue/452#comment-506779) in F28 for us while we waited on upstreams. Now that we are moving to Fedora 29 anyone on openshift origin < 3.11 who want to upgrade/rebase to F29 will fail. We must recommend users: - on f28AH upgrade to origin 3.11 or greater before rebasing to f29AH - deploying to f29AH have to use origin 3.11 or greater - stay on f28AH (no official releases!!) if they need 3.10 or older Note that attempting to use cgroups v1 exclusively by setting `systemd.unified_cgroup_hierarchy=0` and `systemd.legacy_systemd_cgroup_controller=1` ([man page](https://www.freedesktop.org/software/systemd/man/systemd.html#) has no effect on this because it's an [API that was withdrawn](https://pagure.io/atomic-wg/issue/452#comment-506384). Thanks @sjenning for all the help and for providing relevant information. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/512

3 7

[atomic-wg] Issue #513: Hibernation enabled with ISO based installation
by Timothée Ravier 29 Oct '18

29 Oct '18

siosm reported a new issue against the project: `atomic-wg` that you are following: `` When installing Fedora Atomic using the ISO, Anaconda will set the resume=... kernel parameter if swap is available (most probably since https://github.com/poncovka/anaconda/commit/07c8591b107c34f3825dfa2d2b20c5c…). Booting such an install in QEMU/KVM will result in delays/timeouts. I will try to reproduce this on bare metal. Disabling this kernel parameter using "rpm-ostree ex kargs --delete=resume=..." works as workaround. Should we keep hibernation support enabled for atomic hosts? I will try to look further into the specific reason those timeouts occur. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/513

3 27

[atomic-wg] Issue #514: ISO image does not select Atomic Host Anaconda install class by default
by Dusty Mabe 18 Oct '18

18 Oct '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` By default the Atomic Host install class doesn't get chosen, which means things like having an XFS filesystem on root by default doesn't happen. We can further see this by looking at OpenQA where we should see a fedora atomic image rather than a blank image on this screen: https://openqa.fedoraproject.org/tests/296798#step/_boot_to_anaconda/3 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/514

1 3

[atomic-wg] Issue #502: atomic working group talks/sessions for flock 2018
by Dusty Mabe 12 Oct '18

12 Oct '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` [Flock](https://flocktofedora.org) has been announced and will take place Aug 8th-11th in Dresden Germany. The CFP is open and first round of reviews are due by 15th of June, with last round of reviews due by 15th of July. Let's coordinate our talks for Flock! `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/502

5 6

[atomic-wg] Issue #503: Atomic booth at Devconf.in 2018
by Sinny Kumari 12 Oct '18

12 Oct '18

sinnykumari reported a new issue against the project: `atomic-wg` that you are following: `` [Devconf.in 2018](https://devconf.info/in/2018) will be taking place on August 4-5, 2018. In today's [atomic-wg-apac meeting](https://meetbot.fedoraproject.org/fedora-meeting-1/2018-05-29/fedo… we discussed that it is possible to have atomic booth at the conference venue and @suraj353 will be helping us. We will update further progress in this ticket. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/503

2 2

[atomic-wg] Issue #510: Openshift Origin 3.9 fails with error message "Console install failed" on F29 Atomic Host nightly
by Sinny Kumari 09 Oct '18

09 Oct '18

sinnykumari reported a new issue against the project: `atomic-wg` that you are following: `` I tried to set-up basic 3 node OpenShift cluster using playbook playbooks/deploy_cluster.yml from openshift-ansible/openshift-ansible-3.9.41-1 on Fedora 29 Atomic Host latest nightly AMIs (Fedora-AtomicHost-28-20180902.0.x86_64). It fails during task run [openshift_web_console : Verify that the console is running] with error message "Console install failed." After doing ssh into master node and running`oc get nodes` says: ``` $ oc get nodes NAME STATUS ROLES AGE VERSION node1 NotReady master 2h v1.9.1+a0ce1bc657 node2 NotReady compute 2h v1.9.1+a0ce1bc657 node3 NotReady compute 2h v1.9.1+a0ce1bc657 ``` Running kubectl on master node gives following failure message: ``` $ kubectl describe node node1 ... Ready False Wed, 05 Sep 2018 12:11:39 +0000 Wed, 05 Sep 2018 10:08:02 +0000 KubeletNotReady Failed to start ContainerManager Delegation not available for unit type ... ``` Following package versions are available on F29 AH nightly: runc-1.0.0-50.dev.git20aff4f.fc29.x86_64 systemd-239-3.fc29.x86_64 docker-1.13.1-62.git9cb56fd.fc29.x86_64 `Note:` Same set-up works fine with latest F28 Atomic Host `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/510

5 25

[atomic-wg] Issue #465: Fedora 29 Atomic/Cloud Test Day
by Sinny Kumari 03 Oct '18

03 Oct '18

sinnykumari reported a new issue against the project: `atomic-wg` that you are following: `` As discussed in [atomic-wg](https://meetbot.fedoraproject.org/fedora-meeting-1/2018-05-02/fe… meeting today, we would like to have F29 Atomic/Cloud Test Day preferably right after Beta release. By looking at the [F29 schedule](https://fedoraproject.org/wiki/Releases/29/Schedule), Beta release date can be: 2018-09-18: Beta Release (Preferred target) 2018-09-25: Beta Release (Target #1) It will be good to discuss with Fedora QA team first and then see which date after 25th September works well. Corresponding Fedora QA ticket - https://www.pagure.io/fedora-qa/issue/553 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/465

3 7

Fedora 29 Atomic and Cloud Test Day on Monday, 1st October
by Sinny Kumari 01 Oct '18

01 Oct '18

Hi all, We are organizing Atomic and Cloud Test Day on Monday, 1st October. This Test Day is to make sure that Atomic Host and Cloud artifacts are working as expected in Fedora 29. If something is broken, we catch it and fix them as soon as possible to make sure they are all set before Fedora 29 GA. Details about this Test Day are available in wiki page https://fedoraproject.org/wiki/Test_Day:2018-10-01_Cloud-Atomic_Testday . Once you are done with testing, please enter your results at http://testdays.fedorainfracloud.org/events/49 . See you all on Monday! Thanks, Atomic and Cloud Working Group

2 1

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED)