/srv/irclogs.ubuntu.com/2018/06/11/#cloud-init.txt

=== cpaelzer_ is now known as cpaelzer
cpaelzersmoser: blackboxsw: yeah we had no extra chrony love pre Bionic04:51
cpaelzerand getting them to work in container was due to that >=Bionic as well04:52
cpaelzerbut reading the backlog you found all that04:52
cpaelzeranything left open with it?04:52
=== shardy is now known as shardy_lunch
=== ivve_ is now known as ivve
=== shardy_lunch is now known as shardy
=== caribou_ is now known as caribo
=== caribo is now known as caribou
=== r-daneel_ is now known as r-daneel
=== r-daneel_ is now known as r-daneel
mgerdtsblackboxsw the notes say that the last bi-weekly meeting was 13 days ago.  The topic says the next meeting is in 7 days.  Are we rounding up due to a holiday a couple weeks back?15:47
rharpermgerdts: likely, a few folks on the team are out today, so we figured we'd need a bit more time to have additional work land before the next meeting16:05
mgerdtsIs smoser one of those that's out?16:06
dpb1mgerdts: yes16:19
dpb1mgerdts: and blackboxsw :)16:19
dpb1holiday season unfortunately16:19
mgerdtsAre they out all week?16:19
dpb1scotts back on wednesday, blackboxsw later today16:20
mgerdtsok, thanks16:20
ffledglingHello, running into some trouble w/ configuring dns for an image that uses cloud-init. Cloud init doesn't seem to pick up changes from either network-config nor from user-data's resolv module17:15
ffledglingIs this functionality broken? (Using a nocloud provider with a fedora 28 image, cloud-init v17.1)17:15
rharperffledgling: do you have a paste of your cloud-config/user-data and the cloud-init.log available ?17:19
ffledglingrharper: I can give you the former, where can I find the cloud-init.log?17:20
rharper /var/log/cloud-init.log17:20
ffledglingrharper: log - https://paste.fedoraproject.org/paste/ez66J-WWe6NeZkh5mTASUg17:21
ffledglingrharper: configs - https://paste.fedoraproject.org/paste/6y2H38~zsLG0PyZ4JMPkOw17:26
rharperffledgling:  it looks like the cc_resolve_conf module is not enabled by default,  in /etc/cloud/cloud.cfg , under cloud_config_modules: list, upstream doesn't have a  - resolve_conf  in the list;  I suspect that's why the user-data module isn't called17:26
ffledglingrharper: I see, but then it's not picked up from network-config either17:27
rharperwhere is your network-config stored?17:27
rharperwhat datasource are you using, generally one cannot provide network-config via user-data ; it has to be part of the data-source (or in the cloud config on disk)17:27
ffledglingit's all in an iso mounted into the VM; source is nocloud17:28
rharperthings like NoCloud can use it, or ConfgDrive17:28
rharperah, perfect, lemme look at the log then17:28
ffledglingThe other stuff in the config like ip, gateway are picked up fwiw, so it's just the DNS that's causing trouble17:28
ffledglingThis seemed to encapsulate the symptoms - https://bugzilla.redhat.com/show_bug.cgi?id=1473890 ; but I'm not sure if it's still a problem upstream17:29
ubot5bugzilla.redhat.com bug 1473890 in cloud-init "cloud-init sysconfig renderer does not render DNS or GATEWAY" [High,Closed: eol]17:29
rharper /etc/sysconfig/network-scripts/ifcfg-eth17:29
rharperthat's fixed, you can try cloud-init from copr repos17:29
rharperhttps://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/17:30
rharperwhat's in your ifcfg-eth0 ?17:30
rharperdo you see any DNS_ settings there?17:30
ffledglinghttps://paste.fedoraproject.org/paste/rlRkQVQ0GJ8lesH4Qp3hNg17:30
mgerdtsThe "pick up changes" part of your question makes me suspect  https://bugs.launchpad.net/cloud-init/+bug/176580117:30
ubot5Ubuntu bug 1765801 in cloud-init "network should be optionally reconfigured on every boot" [Undecided,Confirmed]17:30
rharperthat's not related directly to you query on dns entries being rendered in sysconfig in a NoCloud scenario17:31
ffledglingnope, I don't even generate the resolv.conf myself, not touching anything network directly, everything goes through cloud-init17:31
ffledglingIt generates the file, but it's always empty17:31
ffledglingrharper: how do I try a newer version of cloud-init with an existing image? If that's possible at all?17:32
rharperyes17:33
rharperadd the repo to the image, if you can get into it, then upgrade cloud-init, and then you can  rm -rf /var/log/cloud-init* /var/lib/cloud/{instance*, data}  ; and reboot17:33
rharpertrunk renders your network-config like this in sysconfig: https://paste.ubuntu.com/p/g5k9j3XpqV/17:34
rharperthat should fix your dns issue17:34
ffledglinglet me try that17:34
rharperyou may find that 17.1 has this bug in it:  https://bugs.launchpad.net/cloud-init/+bug/171268017:35
ubot5Ubuntu bug 1712680 in maas-images "cloud-init re-generates network config every reboot overwriting manual admin changes on CentOS." [Undecided,New]17:35
rharperin which case, comment #11 is helpful ,for workarounds, https://bugs.launchpad.net/cloud-init/+bug/1712680/comments/1117:35
ffledglingHm, don't think that's my issue - since I'm destroying and recreating the image from scratch every time, so this is after first boot17:35
rharperoh sure, I mean, if you make a local change, you may still see this issue17:36
ffledglingah, good to know17:36
ffledglingrharper: so... I can confirm the newer version works18:14
rharpergreat!18:14
ffledglingNow the question is, how do I get this in the default image?18:14
rharperthat's a fedora question18:14
rharperthere are some folks from the project in here18:15
ffledglingwould you know who?18:15
rharperffledgling: larsks is with RH, may know a good connection18:16
larsksWhat do I know? I deny everything.18:16
rharperhehe18:16
rharperlarsks: where would ffledgling file a request to get the fedora cloud images with an updated cloud-init18:17
rharperhttps://fedoraproject.org/wiki/Cloud_SIG looks like a place to start18:18
larsksYou could file a bugzilla against Fedora...https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora18:18
rharpermailing list died off in 2015 though18:18
ffledglinglarsks: that, I was going to do, but there was already a bug for fedora 26 that seems to have died...18:19
ffledglingis that still the best way?18:19
larsksThere has been some talk recently about rebasing the Fedora package on the latest cloud-init release.  The primary package maintainer I think is just busy.18:19
larsksSomeone recently showed up volunteering to help with package maintenance, but I'm not sure where that stands right now.18:20
larsksI would say go ahead and open the bug, ping me with the url, and I am happy to prod some folks.18:20
ffledglinglarsks: okay, thank you!18:22
ffledglingIf the package update is not a major process then I can probably volunteer to get this one out as well, but I suspect that might not be how it works18:22
ffledglinglarsks: https://bugzilla.redhat.com/show_bug.cgi?id=158997218:46
ubot5bugzilla.redhat.com bug 1589972 in cloud-init "cloud-init + nocloud ignores DNS configuration" [Unspecified,New]18:46
ffledglingLet me know if there's more detail needed there18:46
larsksffledgling: thanks, looks good.18:48
blackboxswmgerdts: afternoon/evening. yeah I had a little break this morning. I tried sending out an email to cloud-init@lists.launchpad.net to notify folks about the shift. (and changed the IRC topic to reflect that as you saw).19:53
blackboxswrharper: I'm taking over https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/347727 to get some unit tests over it (and to also fix the issues with unicde in custom-scripts too)19:54
rharperblackboxsw: ok20:02
blackboxswrharper: btw, https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/347559 should be all done per review comments20:03
rharperk, reviewing20:03
blackboxswavoided warnings unless device-level != subnet-level mtu value20:04
blackboxswand added unit test coverage of that20:04
rharperci says no20:04
rharperis that glitch or needs fix to land before it says yes ?20:04
blackboxswbah, pycodestyle. pushing fix now:wq20:10
blackboxswand apparently saving that message in irc too20:10
blackboxswrharper: pushed. I had left a debug maxDiff = None in there that isn't required.20:10
blackboxswlooks like smoser's branch covers the string conversion of all mime types. ok, so we don't need separate changes for x-shellscript or cloud-boothook20:33
blackboxswok just unit test coverage exhibiting the uncode problem20:34
rharpernice20:34
blackboxswunicode rather20:34
blackboxswcpaelzer: way late on the response back to you. but nope, artful//chrony is not a supported thing. so nothing to worry about it. I just need to fix cloud-init's CI to avoid trying to test chrony deployment on artufl20:38
blackboxswcpaelzer: way late on the response back to you. but nope, artful//chrony is not a supported thing. so nothing to worry about it. I just need to fix cloud-init's CI to avoid trying to test chrony deployment on artful20:38
blackboxswwell on artful inside containers only20:41

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!