Description of problem:
I'm testing F29-beta5 amd64 silverblue image under qemu.
I get errors in the logs from rpm-ostree.
$ journalctl -b --no-hostname -p err --no-pager
Sep 21 15:53:46 rpm-ostree: Txn AutomaticUpdateTrigger on /org/projectatomic/rpmostree1/fedora_workstation failed:  Couldn't connect to server
Sep 21 15:54:14 rpm-ostree: Txn AutomaticUpdateTrigger on /org/projectatomic/rpmostree1/fedora_workstation failed:  Couldn't connect to server
Those errors are non-actionable without information *what* server is being contacted. The network works in general, I can ping hosts.
Version-Release number of selected component (if applicable):
Steps to reproduce:
$ install and boot F29 beta
$ journalctl -b -p err
errors reported in log
can you cat /etc/ostree/remotes.d/*.conf ? That should let you know what server was attempted to be contacted.
If you want the server printed out in the logs then maybe open an RFE at github.com/projectatomic/rpm-ostree
I opened https://github.com/ostreedev/ostree/issues/1731.
[fedora@localhost ~]$ ls /etc/ostree/remotes.d/
[fedora@localhost ~]$ cat /etc/ostree/remotes.d/fedora-workstation.conf
It seems I have some network issue with the fedora servers:
$ ping kojipkgs.fedoraproject.org
PING kojipkgs.fedoraproject.org (126.96.36.199) 56(84) bytes of data.
64 bytes from proxy01.fedoraproject.org (188.8.131.52): icmp_seq=1 ttl=47 time=194 ms
64 bytes from proxy01.fedoraproject.org (184.108.40.206): icmp_seq=2 ttl=47 time=203 ms
$ curl https://kojipkgs.fedoraproject.org/atomic/repo/
OK, so I'll close this as UPSTREAM, for the RFE, and close this here since the actual error seems to be a network issue.