This bug is believed to be fixed in curtin in version 18.2. If this is
still a problem for you, please make a comment and set the state back to
New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
** Changed in: maas
Milestone: 2.5.0rc1 => 2.5.0beta4
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1735950
@Scott,
So it seems that curtin is always writing apt_preserve_sources_list:
True. To test this, I'm ensuring that MAAS never sends
apt_preserve_source_list (and this is reflected in the PR attached to
this branch).
With those changes, the resulting curtin config is:
** Changed in: maas
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas/2.3
Status: Triaged => Won't Fix
** Changed in: maas
Milestone: 2.5.x => 2.5.0rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Marking invalid for cloud-init as cloud-init's Traceback and error is
'desired' as it informs the cloud-init user of invalid cloud-config
provided to cloud-init.
** Changed in: cloud-init
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
Thanks for the clarification.
** Changed in: maas
Status: Incomplete => Triaged
** Changed in: maas
Importance: Undecided => Critical
** Also affects: maas/2.3
Importance: Undecided
Status: New
** Changed in: maas/2.3
Status: New => Triaged
** Changed in: maas/2.3
Setting this to Incomplete for MAAS, since it's not clear from if bad
input data from MAAS is causing this traceback in cloud-init, or if the
bug is only in cloud-init.
@jamesbeedy, can you tell us about how you have configured/customized
your apt sources in MAAS?
** Also affects: cloud-init
7 matches
Mail list logo
