[atomic-wg] Issue #447: coordinate Project Atomic-related talks for
devconf.in
by Dusty Mabe
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
4 years, 10 months
[atomic-wg] Issue #455: Building of containers does not work
by Honza Horak
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
4 years, 10 months
[atomic-wg] Issue #449: Fedora 28 Atomic Test Day
by Sinny Kumari
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 years, 11 months
[atomic-wg] Issue #460: Running container using podman gives Network
unreachable on F28 Atomic Host
by Sinny Kumari
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
4 years, 11 months
Re: Fedora-Atomic 27-20180407.0 compose check report
by Adam Williamson
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/8c979e22cba0138b0bdc8414c86048a4a17...
and
https://pagure.io/fedora-qa/fedfind/c/26c556019bd9c4e4b9fd8cc05164bf18630...
, 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
4 years, 11 months