** No longer affects: maas
--
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/1499869
Title:
maas wily deployment to HP Proliant m400 arm64 server cartridge fails
Status in cloud-init:
Hi Michael,
The question is, why are you sending cloud-init configuration with
network config when MAAS already sends one?
Have you considered the possibility that since you are sending duplicate
information, cloud-init may be failing altogether? That said, 50-curtin-
networking.cfg is the config
** Changed in: maas
Milestone: 2.5.x => 2.6.0
** No longer affects: maas/2.4
--
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/1607345
Title:
Collect all logs needed to debug curtin
** Changed in: maas
Status: Incomplete => Invalid
--
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/1819994
Title:
An error occurs when MAAS Deploy 18.04 on ThinkSystem SR590
Sta
MAAS sends this snippet:
network:
bonds:
bond0:
interfaces:
- eth6
- eth7
macaddress: 00:11:0a:66:2e:24
mtu: 9000
parameters:
down-delay: 0
gratuitous-arp: 1
mii-monitor-interval: 100
mode: active-backup
transmit-has
** 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/1827238
Title:
Machines fail to deploy because cloud-init needs to acce
Public bug reported:
When deploying Bionic, /etc/resolv.conf is not configured correctly,
which leads to no DNS resolution. In the output below, you will see that
netplan config is correctly to the 10.90.90.1 nameserver, but in
resolv.conf that's a local address.
Resolv.conf should really be conf
** Changed in: maas
Importance: Undecided => Low
** Changed in: maas
Status: Invalid => Triaged
--
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/1750884
Title:
[2.4, bionic]
** Changed in: maas
Importance: High => Medium
** Changed in: maas
Status: Won't Fix => Triaged
** Changed in: maas
Importance: Medium => Low
** Changed in: maas
Milestone: None => 2.4.x
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
We believe that this is not longer an issue in the latest releases of
MAAS. If you believe this is still an issue, please re-open this bug
report and target it accordingly.
** Changed in: maas
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Y
Dear user,
This is an automated message.
We believe this bug report is no longer an issue in the latest version
of MAAS. For such reason, we are making this issue as Won't Fix. If you
believe this issue is still present in the latest version of MAAS,
please re-open this bug report.
** Changed in
This is definitely not a MAAS bug, as the config sent is exactly as the
one send for Ubuntu.
** Also affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https
** Changed in: maas
Status: Incomplete => Invalid
--
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/1759616
Title:
[2.x] CentOS networking adds weird route
Status in cloud-init:
** 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/1758919
Title:
Static routes are not per-interface, which breaks some d
** Changed in: cloud-init
Status: New => Invalid
--
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/1742971
Title:
[b1] pod created vm fails commissioning after getting 404 from
** Changed in: maas/2.3
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/1758919
Title:
Static routes are not per-interface, which breaks so
I'm marking this as incomplete for 2.3 provided that the latest logs
show the failure on 2.3.1. Since 2.3.2 is already released, I'd like to
see if 2.3.2 has improved this.
2018-04-08 10:20:28 provisioningserver.rpc.clusterservice: [info] Rack
controller 'fcffxf' registered (via swoobat:pid=25312)
** 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/1742971
Title:
[b1] pod created vm fails commissioning after getting 40
Public bug reported:
Cloud-init rsyslog has the major version of cloud-init:
May 11 17:40:51 maas-enlisting-node cloud-init[550]: Cloud-init v. 18.2
running 'init-local' at Fri, 11 May 2018 17:40:47 +. Up 15.63
seconds.
However, it would be nice if it places the whole version, so that we ca
** Also affects: maas/2.4
Importance: Undecided
Status: New
** Changed in: maas/2.4
Milestone: None => 2.4.x
** Changed in: maas/2.4
Status: New => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to clou
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.laun
** Changed in: maas
Status: Incomplete => Invalid
--
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/1774666
Title:
Bond interfaces stuck at 1500 MTU on Bionic
Status in cloud-ini
** Also affects: cloud-init
Importance: Undecided
Status: New
** Tags added: wishlist
--
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/1775430
Title:
[enhancement] Make gw op
I'm re-opening this task for MAAS, as a user has been able to reproduce
this issue in a different context. While there's a work-around on
comment #22, the situation is that even when the same network
configuration sent for xenial and bionic deployments is the same, the
configuration differs, due to
Public bug reported:
When deploying bionic, cloud-init doesn't set the mac address for the
bond or bridge interface, which causes issues when there's expectations
between MAC/IP mappings.
For example, in Bionic:
curtin config sent (/etc/cloud/cloud.cfg.d/50-curtin-networking.cfg):
http://paste.
** 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/1771885
Title:
bionic: static maas missing search domain in systemd-res
** 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
@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:
http://paste.ubuntu.com/p/s8
** 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
Title:
** Changed in: maas/2.3
Status: New => Won't Fix
--
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/1742971
Title:
[b1] pod created vm fails commissioning after getting 404 from
Hi Jeff,
Could you please provide:
1. curtin config (maas machine get-curtin-config )
2. curtin version
3. Power settings of this machine (maas machine power-parameters
). I'm interested in the power_boot_type.
Thanks!
** Changed in: cloud-init
Status: New => Invalid
** Also affects:
Thanks for the quick response. So from the information provided above I
can conclude that:
1. MAAS is *not* telling the machine to boot EFI.
2. The storage config reflects one for legacy systems (non-EFI).
This would either be an issue with curtin (although its quite strange it
does what it does
** Changed in: maas
Status: New => Invalid
--
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/1806504
Title:
userdata runcmd overwrites runcmd under cloud.cfg.d
Status in cloud-in
I believe that his is no longer an issue. I'm going to mark this bug as
Invalid. Please re-open if you believe the issue still exists or file a
new one.
** Changed in: maas
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team
** 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/1732522
Title:
[2.3] Ephemeral boot environment does not renew DHCP lea
@Lee
Adding a task to maas-images to ensure we are using the latest cloud-
init which contains this fix.
** Changed in: maas
Status: Incomplete => Invalid
** Also affects: maas-images
Importance: Undecided
Status: New
** Changed in: maas-images
Assignee: (unassigned) => Le
** Changed in: maas
Status: New => 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/1621615
Title:
network not configured when ipv6 netbooted into cloud-init
Status
** Also affects: maas/2.1
Importance: Undecided
Status: New
** Also affects: maas/trunk
Importance: Critical
Status: Triaged
** Changed in: maas/trunk
Milestone: 2.0.0 => next
** Changed in: maas/trunk
Milestone: next => 2.2.0
** Changed in: maas/2.1
Milestone: N
I believe we discussed it last week. If for whatever reason cloud-init
fails to post events because MAAS may not accept them or similar, cloud-
init shouldn't be failing and posting a failed event.
** Changed in: maas
Status: New => Won't Fix
** Also affects: cloud-init
Importance: Und
** Changed in: maas/2.1
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/1582323
Title:
Commissioning fails when competing cloud metadata re
** Summary changed:
- [2.1] Fail to add PPA behind maas-proxy
+ cloud-init does not take into consideration proxies when adding PPA's.
** Summary changed:
- cloud-init does not take into consideration proxies when adding PPA's.
+ cloud-init does not take into consideration proxy when adding PPA'
Public bug reported:
After update [1] of cloud-init in Ubuntu (which landed in xenial-updates
on 2017-06-27), it is causing NTP reload failures.
https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
0ubuntu1~16.04.1
In MAAS scenarios, this is causing the machine to fail to deploy.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu)
Importance: Undecided => Critical
--
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Milestone: None => 2.3.0
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Yahoo!
We discussed this internally and decided that MAAS is doing the right
thing here. Although unlikely, you may want to prevent enabling SSH at
all, but MAAS will still ensure the machine is marked deployed even if
the user prevents ssh from being run (and configures user login on a
curtin script).
*
** No longer affects: maas
--
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/1701417
Title:
cloud-init fails to configure bonding on CentOS 7
Status in cloud-init:
Fix Committed
Bug
Public bug reported:
ubuntu@withkvm:/var/log$ cat cloud-init.log | grep landscape
2017-08-15 17:17:28,660 - stages.py[DEBUG]: Running module landscape () with
frequency once-per-instance
2017-08-15 17:17:28,660 - handlers.py[DEBUG]: start:
modules-final/config-landscape: running config-landscape
Public bug reported:
Ubuntu (starting from Xenial), uses timesyncd by default as a NTP
client.
When configuring NTP, instead of configuring Ubuntu's default client, it
installs and configures 'ntp' daemon. In Ubuntu Core, however, it
configures 'timesyncd' (obviously) because Ubuntu Core doesn't
Public bug reported:
Using MAAS 2.2.2 and newest CentOS image that uses cloud-init cloud-
init-0.7.9+224.g681baff-1.el7.centos.noarch, network configuration is
being create even when configuration already exists.
MAAS deployed an image that configures network interface via custom
curthooks on the
Public bug reported:
Using MAAS 2.2.2 and newest CentOS image that uses cloud-init cloud-
init-0.7.9+224.g681baff-1.el7.centos.noarch, network configuration re-
created after reboot.
The configuration created was:
[centos@withkvm ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Created by c
Public bug reported:
When using curtin's network passthrough, it writes config in
/etc/network/interfaces.d/50-cloud-init.cfg instead of
/etc/network/interfaces.
This is likely to break juju provided that (i believe) it parses /e/n/i
to do their bridge configuration.
** Affects: cloud-init
** Changed in: maas
Status: Incomplete => Invalid
** Changed in: maas
Milestone: 2.3.0 => None
--
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/1686485
Title:
cc_ntp fails t
Public bug reported:
MAAS supports adding additional repositories but it does not support
disabling components or sources:
Components are [main, universe, multiverse, restricted]
deb source packages = deb-src
** Affects: cloud-init
Importance: Undecided
Status: New
** Affects: maa
Hi Jason,
This seems like a curtin or cloud-init issue, or even an Ubuntu issue
itself. Based on your logs, it seems e/n/i was configured but networking
doesn't come up, and that sounds due to having
/etc/network/interfaces.d/*.cfg. I'm gonna mark this invalid for MAAS
and open curtin/cloud-init t
** 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/1582323
Title:
Commissioning fails when competing cloud metadata reside
** 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/1664384
Title:
[2.1] Support configuring components and disabling deb-s
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Milestone: None => 2.2.0rc3
** Changed in: maas
Importance: Undecided => Wishlist
** Changed in: maas
Status: New => Triaged
--
You received this bug notification because you are a member of Yah
** 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/1683542
Title:
After configuing Ubuntu Core system still displays subiq
MAAS stores install.log.
MAAS doesn't store cloud unit logs because cloud-Init doesn't send them.
However, you have rsyslog a that are what cloud-I it logs, although, I think it
may not be logging correctly (/var/log/Maas/Rsyslog/)
** Changed in: maas
Importance: Undecided => Wishlist
** Cha
** 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/1478103
Title:
need support for configuring syslog
Status in cloud-ini
** Changed in: maas
Status: Incomplete => Invalid
--
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/1577960
Title:
[2.0b4] After commissioning, subnet lists 'observed' IP address
Public bug reported:
Trying to use the new configuration format of APT configuration while
still providing the OLD format, causes cloud-init fails to configure
APT.
cloud-init should be ignoring the old format if the new format is
provided to ensure backwards compat.
This is a problem for MAAS p
I'm reopening this bug and this has not really been fixed:
ubuntu@node01:~$ dpkg -l | grep cloud-init
ii cloud-init 0.7.7-22-g763f403-0ubuntu1all
Init scripts for cloud instances
Config MAAS sends cloud-init: http://pastebin.ubuntu.com/23111940/
/etc/apt
Seeting back to fix-released, as now we need to send
preserve_sources_list: false
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ya
Public bug reported:
Sending a custom APT config to cloud-init fails to:
1. add keys
2. configure sources
3. configura additional repository.
The same config is being sent to curtin, and curtin doesn't seem to fail
(curtin install log http://paste.ubuntu.com/23112826/ just in case).
config sent
** Changed in: maas
Milestone: next => 2.1.0
** Changed in: maas
Importance: Critical => Wishlist
** Changed in: maas
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https
Public bug reported:
cloud-init tries to install NTP package before it actually configures
/etc/apt/sources.list.
In a closed MAAS environment where MAAS is limited to access to
us.archive.ubuntu.com , cloud-init is trying to access to
archive.ubuntu.com.
In commissioning, however, cloud-init is
MAAS now provides NTP and keeps the MAAS servers as well as the machines
in sync. As such, we are closing this one.
Thanks.
** Changed in: maas
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscrib
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
htt
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Milestone: None => 1.9.0
** Changed in: maas
Importance: Undecided => Wishlist
** Changed in: maas
Status: New => Confirmed
--
You received this bug notification because you are a member of Yaho
Public bug reported:
Cloud-init status messages that are send to MAAS provide a SUCCESS/FAIL
results for the different modules that cloud-init runs. As such, if a
module failed, MAAS captures that FAIL message and acts upon on it; for
example, it marks a machine Failed Deployment.
That being said
I Sint ser whats the relation between a cloud image and MAAS. It seems
you are running a cloud image on top of open stack and that's something
that MAAS doesn't do.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: maas
Status: New => Invalid
--
You r
** 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/1303925
Title:
commissioning fails silently if a node can't reach the r
Hi Sean,
Again, this is not a problem in MAAS. So why would cloud-init report the
time is in the future. What happens if you just don't try to ensure the
clocks are the same? The error in deployment above is telling me that
the clocks are not synced.
Cloud-init only fixes the clock-skew so there
74 matches
Mail list logo
