cloud November 2016

cloud@lists.fedoraproject.org

23 participants
73 discussions

[atomic-wg] Issue #160 `Ship fedora-motd in F24 atomic image`
by Pagure 24 Nov '16

24 Nov '16

trishnag added a new comment to an issue you are following: `` We need to ship this for f25. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/160

1 0

[atomic-wg] Issue #154 `make Fedora Atomic download page clearer`
by Pagure 24 Nov '16

24 Nov '16

mattdm added a new comment to an issue you are following: `` I have two small ones. First, I think the freshness indicator is not visible enough in the top bar. Maybe that's just me. I guess, for one thing, it's easy to gloss over header-section text, but also, there's no indication that that's a dynamic value. What about changing "Produced N days ago" to "Produced N days ago, on YYYY-MM-DD" (or whatever internationalized date format the web team prefers)? Second, it currently says "1 days ago". I'd love that to be properly special-cased to "1 day ago", or even better, "yesterday". And "0 days ago" could be "today" or "fresh for you just today!" `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/154

1 0

[atomic-wg] Issue #154 `make Fedora Atomic download page clearer`
by Pagure 24 Nov '16

24 Nov '16

dustymabe added a new comment to an issue you are following: `` I would say update the wiki page, but whatever works. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/154

1 0

[atomic-wg] Issue #154 `make Fedora Atomic download page clearer`
by Pagure 24 Nov '16

24 Nov '16

mattdm added a new comment to an issue you are following: `` Should we update Josh's wiki page above or put proposals here? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/154

1 0

[atomic-wg] Issue #154 `make Fedora Atomic download page clearer`
by Pagure 24 Nov '16

24 Nov '16

dustymabe added a new comment to an issue you are following: `` @jberkus - now we can propose new changes to the F25 page. please schedule some time for interested parties to get together and go over your proposed changes. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/154

1 0

[atomic-wg] Issue #173 `Fedora Cloud Base Vagrant Boxes Don't Allow Vagrant User To su To Other Users`
by Pagure 24 Nov '16

24 Nov '16

The issue: `Fedora Cloud Base Vagrant Boxes Don't Allow Vagrant User To su To Other Users` of project: `atomic-wg` has been assigned to `dustymabe` by trishnag. https://pagure.io/atomic-wg/issue/173

1 0

[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
by Pagure 23 Nov '16

23 Nov '16

walters added a new comment to an issue you are following: `` Oh, sorry, I was reading the git log and missed that we already did back out the change: https://pagure.io/fedora-kickstarts/c/6f3661e3a5f2625b73ee8e998087285d7c6e7… Nevermind. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174

1 0

[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
by Pagure 23 Nov '16

23 Nov '16

dustymabe added a new comment to an issue you are following: `` > One should be able to configure static IPs via nmcli in bootcmd hooks in cloud-init, so I'd like to back out the change to enable network.service. hmm. I don't think we enabled network.service ``` -bash-4.3# systemctl status NetworkManager | cat ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2016-11-22 20:20:04 UTC; 19h ago Docs: man:NetworkManager(8) Main PID: 32401 (NetworkManager) Tasks: 4 (limit: 4915) Memory: 44.0M CPU: 1min 29.555s CGroup: /system.slice/NetworkManager.service ├─32401 /usr/sbin/NetworkManager --no-daemon └─32465 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-eth0.pid -lf /var/lib/NetworkManager/dhclient-5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03-eth0.lease -cf /var/lib/NetworkManager/dhclient-eth0.conf eth0 Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <info> [1479915956.6560] device (veth01b40c4): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <info> [1479915956.6563] policy: disabling autoconnect for connection 'Wired connection 6'. Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <warn> [1479915956.6564] device (veth01b40c4): Activation: failed for connection 'Wired connection 6' Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <info> [1479915956.6565] device (veth158a7ac): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <info> [1479915956.6567] policy: disabling autoconnect for connection 'Wired connection 5'. Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <warn> [1479915956.6568] device (veth158a7ac): Activation: failed for connection 'Wired connection 5' Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <info> [1479915956.6575] device (veth01b40c4): state change: failed -> disconnected (reason 'none') [120 30 0] Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <info> [1479915956.6584] device (veth158a7ac): state change: failed -> disconnected (reason 'none') [120 30 0] Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <info> [1479915956.6595] device (veth01b40c4): enslaved to non-master-type device ovs-system; ignoring Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <info> [1479915956.6597] device (veth158a7ac): enslaved to non-master-type device ovs-system; ignoring Warning: NetworkManager.service changed on disk. Run 'systemctl daemon-reload' to reload units. -bash-4.3# -bash-4.3# systemctl status network | cat Warning: network.service changed on disk. Run 'systemctl daemon-reload' to reload units. ● network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network; generated; vendor preset: disabled) Active: inactive (dead) Docs: man:systemd-sysv-generator(8) ``` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174

1 0

[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
by Pagure 23 Nov '16

23 Nov '16

jasonbrooks added a new comment to an issue you are following: `` We talked about enabling the network service, but we instead patched cloud-init to make NM work. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174

1 0

[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
by Pagure 23 Nov '16

23 Nov '16

kushal added a new comment to an issue you are following: `` Somehow I want to shout "networkd" "networkd" :) `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud November 2016