[Bug 1315501] Re: cloud-init does not use interfaces.d in trusty
@smoser, hi any outlook on the fix for this? Thanks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1315501 Title: cloud-init does not use interfaces.d in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1315501/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1303934] Re: no error message to console when cloud-config-url fails to load
Upon further investigation, this is going to seem odd but I had two disks per VM (for Autopilot) of differing types (for testing) and the Deployed root disk was set to sdb, whereas sda was used for the initial Deploingt target (new/different bug?)(note: I renamed the nodes vs. above to avoid confusion for me but these are the same nodes as above): Deploying: overlayroot on / type overlayfs (rw,lowerdir=/media/root-ro/,upperdir=/media/root-rw/overlay) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/cgroup type tmpfs (rw) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755) /dev/sdc on /media/root-ro type ext4 (ro) tmpfs-root on /media/root-rw type tmpfs (rw,relatime) none on /sys/fs/pstore type pstore (rw) systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd) /dev/sda1 on /tmp/tmpHpNIFU/target type ext4 (rw) /dev on /tmp/tmpHpNIFU/target/dev type none (rw,bind) /proc on /tmp/tmpHpNIFU/target/proc type none (rw,bind) /sys on /tmp/tmpHpNIFU/target/sys type none (rw,bind) Deployed: /dev/sdb1 on / type ext4 (rw) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/cgroup type tmpfs (rw) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755) none on /sys/fs/pstore type pstore (rw) overflow on /tmp type tmpfs (rw,size=1048576,mode=1777) systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd) So I'm unsure if the renaming fixed it and/or the disk reconfiguration (two identical SATA emulations) but now it works. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1303934 Title: no error message to console when cloud-config-url fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1303934/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1303934] Re: no error message to console when cloud-config-url fails to load
I think I just hit this problem with MAAS 1.7.2 with a trusty virtual
setup on my laptop, I'll hopefully keep this for a few days to test a
Chef bug so let me know if you need any more information:
ubuntu@maas-node-1:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.2 LTS
Release:14.04
Codename: trusty
ubuntu@maas-node-1:~$ dpkg -l | grep cloud-init
ii cloud-init 0.7.5-0ubuntu1.5 all
Init scripts for cloud instances
ii cloud-initramfs-dyn-netconf 0.25ubuntu1 all
write a network interface file in /run for BOOTIF
ubuntu@maas-node-1:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic
root=UUID=ebef096d-3483-4027-abf4-d0621f6f7144 ro
ubuntu@maas-node-1:~$ tail -20 /var/log/cloud-init.log
2015-05-31 17:19:17,681 - url_helper.py[DEBUG]: Please wait 5 seconds while we
wait to try again
2015-05-31 17:19:22,685 - url_helper.py[DEBUG]: [0/1] open
'http://192.168.101.2/MAAS/metadata//2012-03-01/meta-data/instance-id' with
{'url': 'http://192.168.101.2/MAAS/metadata//2012-03-01/meta-data/instance-id',
'headers': {'Authorization': 'OAuth realm="", oauth_nonce="26709034",
oauth_timestamp="1433092762", oauth_consumer_key="uU9KHB7kPK24yZcFrx",
oauth_signature_method="PLAINTEXT", oauth_version="1.0",
oauth_token="gwF4Eh6beNEqXcg3f6",
oauth_signature="%262bj652WEP7dp3NHKxsHZVRaFmhCeUv79"'}, 'allow_redirects':
True, 'method': 'GET', 'timeout': 4.0} configuration
2015-05-31 17:19:25,685 - url_helper.py[DEBUG]: Calling
'http://192.168.101.2/MAAS/metadata//2012-03-01/meta-data/instance-id' failed
[118/120s]: request error [HTTPConnectionPool(host='192.168.101.2', port=80):
Max retries exceeded with url: /MAAS/metadata//2012-03-01/meta-data/instance-id
(Caused by : [Errno 113] No route to host)]
2015-05-31 17:19:25,685 - url_helper.py[DEBUG]: Please wait 5 seconds while we
wait to try again
2015-05-31 17:19:30,690 - DataSourceMAAS.py[CRITICAL]: Giving up on md from
['http://192.168.101.2/MAAS/metadata//2012-03-01/meta-data/instance-id'] after
123 seconds
2015-05-31 17:19:30,697 - util.py[WARNING]: No instance datasource found!
Likely bad things to come!
2015-05-31 17:19:30,697 - util.py[DEBUG]: No instance datasource found! Likely
bad things to come!
Traceback (most recent call last):
File "/usr/bin/cloud-init", line 242, in main_init
init.fetch()
File "/usr/lib/python2.7/dist-packages/cloudinit/stages.py", line 308, in
fetch
return self._get_data_source()
File "/usr/lib/python2.7/dist-packages/cloudinit/stages.py", line 236, in
_get_data_source
pkg_list)
File "/usr/lib/python2.7/dist-packages/cloudinit/sources/__init__.py", line
260, in find_source
raise DataSourceNotFoundException(msg)
DataSourceNotFoundException: Did not find any data source, searched classes:
(DataSourceMAAS)
2015-05-31 17:19:30,702 - util.py[DEBUG]: Reading from /proc/uptime
(quiet=False)
2015-05-31 17:19:30,703 - util.py[DEBUG]: Read 14 bytes from /proc/uptime
2015-05-31 17:19:30,703 - util.py[DEBUG]: cloud-init mode 'init' took 124.041
seconds (124.04)
ubuntu@maas-node-1:/var/lib/cloud/data$ cat previous-datasource
DataSourceMAAS: DataSourceMAAS [http://192.168.101.2/MAAS/metadata/]
^^^ Interesting bit, I'm switching between two MAASes (testing 1.8 which
is [powered off] at 192.168.101.2)
root@maas-node-1:/var/lib/cloud/instances/node-bec4d2f6-0652-11e5-b1c1-525400cad0ca#
cat datasource
DataSourceMAAS: DataSourceMAAS [http://192.168.101.2/MAAS/metadata/]
root@maas-node-1:/var/lib/cloud/instances/node-bec4d2f6-0652-11e5-b1c1-525400cad
**
ubuntu@maas17:~$ dpkg -l | grep 'maas '
ii maas1.7.5+bzr3369-0ubuntu1~trusty1 all
MAAS server all-in-one metapackage
ubuntu@maas17:~$ ifconfig eth0 | head -2
eth0 Link encap:Ethernet HWaddr 52:54:00:XX:YY:ZZ
inet addr:192.168.101.3 Bcast:192.168.101.255 Mask:255.255.255.0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1303934
Title:
no error message to console when cloud-config-url fails to load
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1303934/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1226855] Re: Cannot use open-iscsi inside LXC container
@Serge, Hi, had a customer ping me about this bug, any updates? Here's his explanation: You may recall our conversation around iSCSI connectivity for binding block volume with host in OpenStack. The host is Linux container and block volume is on EMC VMAX. The I/O path is over iSCSI. The environment is Ubuntu 14.04 LTS x64. Our observation and KB found from internet is also given. - Regular attach volume works fine (iSCSI login occurs between compute node and array target). In this context, Compute node is a physical host - When creating bootable volume, controller node needs to perform iSCSI login for instance to copy. We are seeing issues with this. In this case, Compute node is an LXC container. - Same isciadm commands that fail within the container, run fine when running outside the container (on physical controller host) Looks like, There’s a iSCSI kernel bug with mounting a target within a container The issue is with multiple namespaces it appears. KBs found: https://github.com/lxc/lxc/issues/177 https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1226855 https://groups.google.com/forum/#!topic/open-iscsi/GhKfxIix4ds Do we know whether this is fixed? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1226855 Title: Cannot use open-iscsi inside LXC container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226855/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 728018] Re: 10.04 LTS: Failure to start instance due to network address failure
** Changed in: eucalyptus (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/728018 Title: 10.04 LTS: Failure to start instance due to network address failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/728018/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271188] Re: maas-import-ephermerals provides no feedback on progress
Although amd64/trusty is the current priority, downloading based on the current MaaS default series or allowing to specify the priority arch/series as an option would be ideal. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1271188 Title: maas-import-ephermerals provides no feedback on progress To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1271188/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1081660] Re: If maas-enlist fails to reach a DNS server, the node will be named "; ; connection timed out; no servers could be reached"
This occurred on just one of thirty nodes, raring maas (1.3+bzr1461 +dfsg-0ubuntu2.2) with precise commissioning on armhf, for me. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas-enlist in Ubuntu. https://bugs.launchpad.net/bugs/1081660 Title: If maas-enlist fails to reach a DNS server, the node will be named ";; connection timed out; no servers could be reached" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas-enlist/+bug/1081660/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1206715] Re: maas-import-pxe-files raring installer-armhf highbank ERROR 404: Not Found.
*** This bug is a duplicate of bug 1166994 *** https://bugs.launchpad.net/bugs/1166994 ** This bug has been marked a duplicate of bug 1166994 need to use generic kernel for highbank on ARM -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1206715 Title: maas-import-pxe-files raring installer-armhf highbank ERROR 404: Not Found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1206715/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1206715] [NEW] maas-import-pxe-files raring installer-armhf highbank ERROR 404: Not Found.
Public bug reported: 1.4.5 (1.3+bzr1461+dfsg-0ubuntu2.1) Ubuntu 13.04 Linux c01 3.8.0-26-generic #38-Ubuntu SMP Mon Jun 17 21:48:11 UTC 2013 armv7l armv7l armv7l GNU/Linux ubuntu@c01:~$ sudo maas-import-pxe-files Downloading to temporary location /tmp/tmp.yjQSYTXTy2. /tmp/tmp.yjQSYTXTy2 ~ 2013-07-30 17:39:11 URL:http://archive.ubuntu.com/ubuntu//dists/precise/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64//linux [4965840/4965840] -> "linux" [1] ... ... http://ports.ubuntu.com/ubuntu-ports//dists/raring/main/installer-armhf/current/images/highbank/netboot//vmlinuz: 2013-07-30 17:44:57 ERROR 404: Not Found. Highbank no longer exists in raring, generic does but does not get pulled in for armhf: http://ports.ubuntu.com/ubuntu-ports/dists/raring/main/installer- armhf/current/images/generic/netboot/ ** Affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1206715 Title: maas-import-pxe-files raring installer-armhf highbank ERROR 404: Not Found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1206715/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1206681] [NEW] login page cluster controllers missing boot image warning message link pulls IP vs. URL
Public bug reported: 1.4.5 (1.3+bzr1461+dfsg-0ubuntu2.1) Ubuntu 13.04 Linux c01 3.8.0-26-generic #38-Ubuntu SMP Mon Jun 17 21:48:11 UTC 2013 armv7l armv7l armv7l GNU/Linux Login page message, "Some cluster controllers are missing boot images. Either the import task has not been initiated (for each cluster, the task must be initiated by hand the first time), or the import task failed." contains a link: "initiated by hand" is a link: http://10.229.32.2/MAAS/settings/#accepted-clusters But the page URL is http://localhost:/MAAS/accounts/login/?next=%2FMAAS%2F (proxied). All other links are correct that I can tell (ie. http://localhost:/MAAS/settings/ ) I believe the "initiated by hand" link should be: http://localhost:/MAAS/settings/#accepted-clusters vs. http://10.229.32.2/MAAS/settings/#accepted-clusters ** Affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1206681 Title: login page cluster controllers missing boot image warning message link pulls IP vs. URL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1206681/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
