April 2018 - Atomic Working Group (ARCHIVED)

[atomic-wg] Issue #447: coordinate Project Atomic-related talks for devconf.in
by Dusty Mabe 15 May '18

15 May '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` Please everyone comment on this if you either: 1. are submitting to DevConf.in but don't know what to talk about 2. already submitted to DevConf.in but don't want others to see what you submitted yet 3. already submitted and want others to see the abstract 4. know someone who fits into 1.-3. but doesn't know about this ticket here I'll approach you individually afterwards and have a link with gathered information ready for those who are participating - if you wanna give a talk but need help submitting, message me. # Important Dates - CfP Closes: May 4, 2018 - Accepted speakers confirmation: June 4, 2018 - Schedule published: July 2, 2018 - Event dates: Saturday, August 4 to Sunday, August 5, 2018 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/447

8 12

[atomic-wg] Issue #446: FAW 28 ISO requires network
by Colin Walters 12 May '18

12 May '18

walters reported a new issue against the project: `atomic-wg` that you are following: `` Presumably this is an anaconda regression; we have the ostree data cached in the ISO so there's no reason for us to require networking to install. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/446

3 5

[atomic-wg] Issue #462: articles for upgrade/features of f28 atomic host
by Dusty Mabe 09 May '18

09 May '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` For f27 we had an [upgrade article](http://www.projectatomic.io/blog/2017/11/fedora-atomic-26-to-27-upgrade/) on pa.io and a [features article](https://fedoramagazine.org/fedora-27-atomic-offering/) a little later on fedmag that also linked to the upgrade article. Would be nice if we could do the same for f28. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/462

3 12

[atomic-wg] Issue #455: Building of containers does not work
by Honza Horak 08 May '18

08 May '18

hhorak reported a new issue against the project: `atomic-wg` that you are following: `` I'm trying to build a container, but it always fails. I'm trying from more repos, e.g.: https://koji.fedoraproject.org/koji/taskinfo?taskID=26340825 Seeing: container_linux.go:247: starting container process caused "process_linux.go:364: container init caused \"rootfs_linux.go:54: mounting \\\"/var/lib/origin/openshift.local.volumes/pods/e2e09f0d-3f04-11e8-aa8d-5254004f20fd/volumes/kubernetes.io~secret/builder-token-01lfv\\\" to rootfs \\\"/var/lib/docker/devicemapper/mnt/777d7851d75b3ecc837d1cb61b9fbc9dd5beb379e66d7552b1f2eb6da2fbff8e/rootfs\\\" at \\\"/var/lib/docker/devicemapper/mnt/777d7851d75b3ecc837d1cb61b9fbc9dd5beb379e66d7552b1f2eb6da2fbff8e/rootfs/run/secrets/kubernetes.io/serviceaccount\\\" caused \\\"mkdir /var/lib/docker/devicemapper/mnt/777d7851d75b3ecc837d1cb61b9fbc9dd5beb379e66d7552b1f2eb6da2fbff8e/rootfs/run/secrets/kubernetes.io: read-only file system\\\"\"" `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/455

5 22

[atomic-wg] Issue #449: Fedora 28 Atomic Test Day
by Sinny Kumari 03 May '18

03 May '18

sinnykumari reported a new issue against the project: `atomic-wg` that you are following: `` Let's plan on having a Test Day to get Atomic well tested for Fedora 28. Some of the items which I can think of: - Involving Fedora QE members to get their input - Identify date for Test Day which suits majority of folks - Preparing Test cases which needs to be tested - Advertising about Atomic Test Day to get more testers involved. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/449

4 13

[atomic-wg] Issue #445: Fedora 28 Talking Points
by Dusty Mabe 02 May '18

02 May '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` From @mattdm : ``` Do we have anything I should emphasize for beta, coming up next week? What about in May? https://fedoraproject.org/wiki/Fedora_28_talking_points#Fedora_Atomic ``` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/445

8 26

[atomic-wg] Issue #456: F28 Atomic Beta AMIs do not connect to the network when using private IPs only
by Joe Doss 30 Apr '18

30 Apr '18

jdoss reported a new issue against the project: `atomic-wg` that you are following: `` It seems that Fedora 28 Atomic Beta (and F28 Beta Cloud) when using private IPs only, does not connect to the network. This results in the EC2 instance failing it's connectivity test and you cannot connect to it via SSH. If you test the AMI with a Public IP however, it will work just fine. This was tested with the Fedora-AtomicHost-28_Beta-1.3.x86_64-us-west-2-HVM-gp2-0 (ami-e5841f9d) AMI. I detached the failed EC2 instance's EBS volume and attached it to a working server to dump the cloud-init.log and the systemd journal. You can download them here. https://www.solidadmin.com/atomic/f28atomic-cloud-init.log https://www.solidadmin.com/atomic/f28atomic-journal.log I have included the Fedora 28 Cloud logs as well if they will help. https://www.solidadmin.com/atomic/f28cloud-cloud-init.log https://www.solidadmin.com/atomic/f28cloud-journal.log `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/456

3 13

[atomic-wg] Issue #461: use 'ostree remote gpg-import' when producing cloud-images/ISO
by Micah Abbott 26 Apr '18

26 Apr '18

miabbott reported a new issue against the project: `atomic-wg` that you are following: `` A common problem that users hit when a new major release lands is having to manually configure a new remote or modify an existing remote to use the new major release GPG key. This is exacerbated now that we have a unified repo for all of our refs. A solution pointed out in the [upstream ostree issue](https://github.com/ostreedev/ostree/issues/773#issuecomment-38077335… is to use the `ostree remote gpg-import` functionality to make the recent keys available to the remote. Would it be possible to change how we produce the cloud-images/AMIs/ISOs so that the pre-configured remote uses this method to make all the recent keys available? ``` # ostree remote add fedora-atomic https://dl.fedoraproject.org/atomic/repo/ # cat /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-{27,28,29}-primary |ostree remote gpg-import --stdin fedora-atomic ``` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/461

3 5

[atomic-wg] Issue #460: Running container using podman gives Network unreachable on F28 Atomic Host
by Sinny Kumari 26 Apr '18

26 Apr '18

sinnykumari reported a new issue against the project: `atomic-wg` that you are following: `` In latest Fedora 28 Atomic Host RC 1.1, we have both podman and docker pre-installed. I was playing around with podman on Fedora 28 Atomic Host and tried to launch a container by running command ``` $ sudo podman run -t fedora bash [root@becd4a294478 /]# ``` Container launched successfully and got shell prompt. But, looks like network is unreachable. ``` # curl example.com no response. # dnf update Error: Failed to synchronize cache for repo updates. ``` To workaround, I launched container with option --net=host and then network was fine. ``` $ sudo podman run -t --net=host fedora bash ``` Note: network inside container launched by docker were fine `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/460

2 1

Re: Fedora-Atomic 27-20180407.0 compose check report
by Adam Williamson 26 Apr '18

26 Apr '18

On Sat, 2018-04-07 at 09:00 -0700, Adam Williamson wrote: > On Sat, 2018-04-07 at 10:32 -0400, Dusty Mabe wrote: > > > > On 04/07/2018 03:54 AM, Fedora compose checker wrote: > > > No missing expected images. > > > > > > Passed openQA tests: 2/2 (x86_64) > > > > > > > Can we get these emails to go to atomic(a)lists.fedoraproject.org? > > They're actually supposed to, and they're also only supposed to go out > when a test fails. I'm not sure whey they're acting like the > Rawhide/Branched mails at the moment, I had a brief look at it the > other day but couldn't see anything wrong. I'll have another look at it > next week. OK, it wasn't quite 'next week', but :P I figured out why this was broken, finally. The 'special' configuration for the two-week Atomic reports (mail them to a different set of addresses, and only mail on failure) relied on the fedfind 'milestone' for these composes being 'Atomic', but I changed that back in https://pagure.io/fedora-qa/fedfind/c/8c979e22cba0138b0bdc8414c86048a4a17f1… and https://pagure.io/fedora-qa/fedfind/c/26c556019bd9c4e4b9fd8cc05164bf18630c1… , all for terribly good reasons of course. I've now tweaked check- compose so you can override the configuration by the release's "dist" (which is what Pungi/productmd refer to as the 'shortname' - it's the first component of the compose ID, so 'Fedora', or 'Fedora-Atomic', or 'Fedora-Docker', etc.) instead of its "milestone", and tweaked the configuration of the check-compose deployment in Fedora infra to match. So if I got all that right, this should now work again. I also updated the list of addresses the mails will be sent to; it was previously Mike McGrath plus atomic@ , but I don't think Mike's the right person any more, so I changed it to Dusty, Colin and atomic@. So Dusty, Colin and the list should get the reports *only if* either of the tests failed. When both tests pass, no report will be sent out. Thanks folks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) April 2018