[atomic-wg] Issue #468: systemd-journald has no logs on fresh DigitalOcean
droplets
by Dalton Hubble
dghubble reported a new issue against the project: `atomic-wg` that you are following:
``
systemd-journald is missing logs on fresh droplets. journalctl shows nothing for any unit.
```
$ journalctl
No journal files were found.
-- No entries --
```
That's not right. There should at least be some system logs there. Check any unit and find no entries.
It seems like restarting `systemd-journald` or rebooting works around the issue, so its present only on fresh droplets. Originally observed on DigitalOcean's `20180424.4` image and doing a rolling upgrade to `28.20180425.0` addressed the issue - but that probably only worked because of the reboot. Since fresh `28.20180425.0` droplets now also have the systemd-journald issue.
```
● ostree://fedora-atomic:fedora/28/x86_64/atomic-host
Version: 28.20180425.0 (2018-04-25 19:14:57)
Commit: 94a9d06eef34aa6774c056356d3d2e024e57a0013b6f8048dbae392a84a137ca
GPGSignature: Valid signature by 128CF232A9371991C8A65695E08E7E629DB62FB1
```
https://twitter.com/dghubble/status/993277668828168192
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/468
5 years, 10 months
Fedora Atomic APAC WG Meeting Minutes 2018-05-29
by Sinny Kumari
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting-1/2018-05-29/fedora_atom...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting-1/2018-05-29/fedora_atom...
Log:
https://meetbot.fedoraproject.org/fedora-meeting-1/2018-05-29/fedora_atom...
========================================
#fedora-meeting-1: fedora_atomic_apac_wg
========================================
Meeting started by ksinny at 05:00:36 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2018-05-29/fedora_atom...
.
Meeting summary
---------------
* Roll Call (ksinny, 05:00:51)
* Action items from last meeting (ksinny, 05:04:06)
* atomic working group talks/sessions for flock 2018 (ksinny, 05:06:05)
* LINK: https://pagure.io/atomic-wg/issue/502 (ksinny, 05:06:14)
* CFP submission is a bit different this time, we need to create an
issue for submission at https://pagure.io/flock/issues (ksinny,
05:08:35)
* Flock website has ben updated with CFP details -
https://flocktofedora.org/ (ksinny, 05:11:46)
* Open Floor (ksinny, 05:12:18)
* LINK: https://communityblog.fedoraproject.org/ (sayan, 05:15:01)
* ACTION: sayan to write a blog at Fedora communityblog about
atomic-wg apac meeting (ksinny, 05:17:36)
* A new Atomic TwoWeek RC from 20180528 is available for tetsing -
https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-M...
(ksinny, 05:19:18)
* ACTION: sayan will chair next atomic-wg-apac meeting (ksinny,
05:21:22)
* We are planning to have a atomic booth at Devconf.in and snarwade
will be helping us with it (ksinny, 05:30:12)
* ACTION: ksinny to create a atomic-wg ticket to discuss progress
around having atomic booth at Devconf.in (ksinny, 05:30:30)
Meeting ended at 05:32:47 UTC.
Action Items
------------
* sayan to write a blog at Fedora communityblog about atomic-wg apac
meeting
* sayan will chair next atomic-wg-apac meeting
* ksinny to create a atomic-wg ticket to discuss progress around having
atomic booth at Devconf.in
Action Items, by person
-----------------------
* ksinny
* ksinny to create a atomic-wg ticket to discuss progress around
having atomic booth at Devconf.in
* sayan
* sayan to write a blog at Fedora communityblog about atomic-wg apac
meeting
* sayan will chair next atomic-wg-apac meeting
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* ksinny (56)
* snarwade_ (25)
* sayan (23)
* zodbot (11)
* kushal (3)
* snarwade (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
5 years, 10 months
2wk atomic release candidate: 20180528
by Sinny Kumari
Hi all,
We have new Release Candidate available for testing which contains
updated kernel with fixes for CVE-2018-3639.
We will attempt to release the 20180528 images tomorrow.
These images contain the following ostree version/commits
from the Fedora-28-updates-20180527.0 updates run:
Version: 28.20180527.0
Commit(x86_64):
291ea90da29bc5abe757b5a50813b3de1396b08412939a89b3b671aba9856093
Commit(aarch64):
f3f1b43c6bb1fa705d36f4e2b470e1dc510af421b3d122457f21f1664b37182e
Commit(ppc64le):
372a253acef6db9acced3d1cb09090473567d10a2a9e5d488f487e7df441c696
The Atomic Host VM images are in the directory:
x86_64:
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-20180...
aarch64:
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-20180...
ppc64le:
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-20180...
The Atomic Host ISO images are in the directory:
x86_64:
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-20180...
aarch64:
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-20180...
ppc64le:
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-20180...
The AMIs are here:
Fedora-AtomicHost-28-20180528.0.x86_64 ap-northeast-1 ami-8049b0ff hvm
standard
Fedora-AtomicHost-28-20180528.0.x86_64 ap-northeast-2 ami-05a9026b hvm
standard
Fedora-AtomicHost-28-20180528.0.x86_64 ap-south-1 ami-13fbd47c hvm
standard
Fedora-AtomicHost-28-20180528.0.x86_64 ap-southeast-1 ami-b51728c9 hvm
standard
Fedora-AtomicHost-28-20180528.0.x86_64 ap-southeast-2 ami-20419242 hvm
standard
Fedora-AtomicHost-28-20180528.0.x86_64 ca-central-1 ami-43df5c27 hvm
standard
Fedora-AtomicHost-28-20180528.0.x86_64 eu-central-1 ami-ebaf8500 hvm
standard
Fedora-AtomicHost-28-20180528.0.x86_64 eu-west-1 ami-1738036e hvm
standard
Fedora-AtomicHost-28-20180528.0.x86_64 eu-west-2 ami-bc20ccdb hvm
standard
Fedora-AtomicHost-28-20180528.0.x86_64 sa-east-1 ami-4da6f821 hvm
standard
Fedora-AtomicHost-28-20180528.0.x86_64 us-east-1 ami-223f535d hvm
standard
Fedora-AtomicHost-28-20180528.0.x86_64 us-west-1 ami-36f8e356 hvm
standard
Fedora-AtomicHost-28-20180528.0.x86_64 us-west-2 ami-7d136805 hvm
standard
Fedora-AtomicHost-28-20180528.0.x86_64 ap-northeast-1 ami-724ab30d hvm
gp2
Fedora-AtomicHost-28-20180528.0.x86_64 ap-northeast-2 ami-72a8031c hvm
gp2
Fedora-AtomicHost-28-20180528.0.x86_64 ap-south-1 ami-02f9d66d hvm
gp2
Fedora-AtomicHost-28-20180528.0.x86_64 ap-southeast-1 ami-f3152a8f hvm
gp2
Fedora-AtomicHost-28-20180528.0.x86_64 ap-southeast-2 ami-11469573 hvm
gp2
Fedora-AtomicHost-28-20180528.0.x86_64 ca-central-1 ami-47df5c23 hvm
gp2
Fedora-AtomicHost-28-20180528.0.x86_64 eu-central-1 ami-c5af852e hvm
gp2
Fedora-AtomicHost-28-20180528.0.x86_64 eu-west-1 ami-2a3f0453 hvm
gp2
Fedora-AtomicHost-28-20180528.0.x86_64 eu-west-2 ami-633cd004 hvm
gp2
Fedora-AtomicHost-28-20180528.0.x86_64 sa-east-1 ami-0aa9f766 hvm
gp2
Fedora-AtomicHost-28-20180528.0.x86_64 us-east-1 ami-ec0c6093 hvm
gp2
Fedora-AtomicHost-28-20180528.0.x86_64 us-west-1 ami-8b9d86eb hvm
gp2
Fedora-AtomicHost-28-20180528.0.x86_64 us-west-2 ami-28106b50 hvm
gp2
An example of the diff between this and the previous released version (for
x86_64) is:
ostree diff commit old:
a29367c58417c28e2bd8306c1f438b934df79eba13706e078fe8564d9e0eb32b
ostree diff commit new:
291ea90da29bc5abe757b5a50813b3de1396b08412939a89b3b671aba9856093
Upgraded:
NetworkManager 1:1.10.6-3.fc28 -> 1:1.10.8-1.fc28
NetworkManager-libnm 1:1.10.6-3.fc28 -> 1:1.10.8-1.fc28
NetworkManager-team 1:1.10.6-3.fc28 -> 1:1.10.8-1.fc28
bubblewrap 0.2.0-3.fc28 -> 0.2.1-1.fc28
cockpit-bridge 167-1.fc28 -> 168-1.fc28
cockpit-docker 167-1.fc28 -> 168-1.fc28
cockpit-networkmanager 167-1.fc28 -> 168-1.fc28
cockpit-ostree 167-1.fc28 -> 168-1.fc28
cockpit-system 167-1.fc28 -> 168-1.fc28
container-selinux 2:2.55-1.fc28 -> 2:2.61-1.git9b55129.fc28
container-storage-setup 0.8.0-3.git1d27ecf.fc28 ->
0.10.0-1.gitdf0dcd5.fc28
crypto-policies 20180425-1.git6ad4018.fc28 -> 20180425-5.git6ad4018.fc28
curl 7.59.0-2.fc28 -> 7.59.0-3.fc28
cyrus-sasl-lib 2.1.27-0.1rc7.fc28 -> 2.1.27-0.2rc7.fc28
fedora-gpg-keys 28-2 -> 28-3
fedora-repos 28-2 -> 28-3
file 5.33-2.fc28 -> 5.33-5.fc28
file-libs 5.33-2.fc28 -> 5.33-5.fc28
glib-networking 2.56.0-1.fc28 -> 2.56.1-1.fc28
glib2 2.56.1-1.fc28 -> 2.56.1-2.fc28
glibc 2.27-8.fc28 -> 2.27-15.fc28
glibc-all-langpacks 2.27-8.fc28 -> 2.27-15.fc28
glibc-common 2.27-8.fc28 -> 2.27-15.fc28
initscripts 9.79-3.fc28 -> 9.80-1.fc28
kernel 4.16.8-300.fc28 -> 4.16.11-300.fc28
kernel-core 4.16.8-300.fc28 -> 4.16.11-300.fc28
kernel-modules 4.16.8-300.fc28 -> 4.16.11-300.fc28
libcurl 7.59.0-2.fc28 -> 7.59.0-3.fc28
libidn2 2.0.4-7.fc28 -> 2.0.5-1.fc28
libnfsidmap 1:2.3.1-8.rc1.fc28 -> 1:2.3.1-9.rc1.fc28
libpsl 0.20.2-1.fc28 -> 0.20.2-2.fc28
libsss_idmap 1.16.1-4.fc28 -> 1.16.1-8.fc28
libsss_nss_idmap 1.16.1-4.fc28 -> 1.16.1-8.fc28
libsss_sudo 1.16.1-4.fc28 -> 1.16.1-8.fc28
libxcrypt 4.0.0-5.fc28 -> 4.0.1-1.fc28
microcode_ctl 2:2.1-22.fc28 -> 2:2.1-23.fc28
nfs-utils 1:2.3.1-8.rc1.fc28 -> 1:2.3.1-9.rc1.fc28
pam 1.3.0-10.fc28 -> 1.3.1-1.fc28
podman 0.5.1-1.gitd0fbfdc.fc28 -> 0.5.3-2.gitdc3f9df.fc28
procps-ng 3.3.12-1.fc28 -> 3.3.12-2.fc28
publicsuffix-list-dafsa 20180419-1.fc28 -> 20180514-1.fc28
python2 2.7.15-1.fc28 -> 2.7.15-2.fc28
python2-libs 2.7.15-1.fc28 -> 2.7.15-2.fc28
python2-setuptools 39.0.1-1.fc28 -> 39.2.0-1.fc28
python3-rpm 4.14.1-7.fc28 -> 4.14.1-9.fc28
python3-setuptools 39.0.1-1.fc28 -> 39.2.0-1.fc28
python3-sssdconfig 1.16.1-4.fc28 -> 1.16.1-8.fc28
rpm 4.14.1-7.fc28 -> 4.14.1-9.fc28
rpm-build-libs 4.14.1-7.fc28 -> 4.14.1-9.fc28
rpm-libs 4.14.1-7.fc28 -> 4.14.1-9.fc28
rpm-ostree 2018.4-1.fc28 -> 2018.5-1.fc28
rpm-ostree-libs 2018.4-1.fc28 -> 2018.5-1.fc28
rpm-plugin-selinux 4.14.1-7.fc28 -> 4.14.1-9.fc28
selinux-policy 3.14.1-24.fc28 -> 3.14.1-29.fc28
selinux-policy-targeted 3.14.1-24.fc28 -> 3.14.1-29.fc28
sssd-client 1.16.1-4.fc28 -> 1.16.1-8.fc28
tzdata 2018d-1.fc28 -> 2018e-1.fc28
userspace-rcu 0.10.1-2.fc28 -> 0.10.1-3.fc28
vim-minimal 2:8.0.1806-1.fc28 -> 2:8.1.020-1.fc28
Added:
rpm-sign-libs-4.14.1-9.fc28.x86_64
Happy testing!
5 years, 10 months
[atomic-wg] Issue #418: Design Meetings over Video
by Steve Milner
smilner reported a new issue against the project: `atomic-wg` that you are following:
``
An idea that @dustymabe had was to start having design meetings via video (like Hangouts/BJN/etc..) to help speed up design discussions. We traditionally either had these discussions over long issue threads or IRC conversations. Would it be worth having a time/location that we could get community members together to discuss deeper design items together in public?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/418
5 years, 10 months
[atomic-wg] Issue #466: Layered containers from candidate registry should be
used
by Honza Horak
hhorak reported a new issue against the project: `atomic-wg` that you are following:
``
Let me describe my frustration from building layered containers in Fedora.
We've been maintaining CentOS and RHEL based images for various interesting stuff like databases (PostgreSQL, MariaDB) or dynamic languages (Python, NodeJS) at http://github.com/sclorg/ and we'd love to see the same set of containers in Fedora as well.
The challenge I see is that we have 2 or 3 layers on top of the base image, e.g.: Fedora 28 -> s2i-core -> s2i-base -> python, which is probably somewhat special, comparing to simple container images that just depend on the base image. The problem is that when we want to build either s2i-base or python, we only can take image from the release registry (registry.fedoraproject.org, mentioned in the guidelines and enforced in the tooling), so if the release would work as expected every two weeks, we can build s2i-core, in 2 weeks we can build s2i-base, and in another two weeks we can have up2date python container that uses some features from s2i-core that we built 4 weeks back.. That is not what we want to see.
And then, there is the release itself, that is still somewhat indeterministic, and we don't see when the built image will be available.
Anyway, when thinking about how to fix this process issue, it looks like everything would be better if layered images from the *candidate* registry would be used when building a new container. It might be done simply by rewriting `FROM` (`s/registry.fedoraproject.org/candidate-registry.fedoraproject.org/`) as such rewrites are done anyway in OSBS... If someone would really like to use the image from released registry, they can use concrete release tag..
What do you think?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/466
5 years, 10 months
[atomic-wg] Issue #375: Article for F27: The new Atomic Workstation
by Josh Berkus
jberkus reported a new issue against the project: `atomic-wg` that you are following:
``
Since we're now offering regular updates for Atomic Workstation, it's time for a detailed blog post about installing it and running it. Maybe even a series.
Ideal would be a summary article in Fedora Magazine, and a detailed series over time on the Atomic blog.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/375
5 years, 10 months