[Bug 1246990] Re: [qemu-x86-64-linux-user 1.6.1] qemu: uncaught target signal 11 (Segmentation fault) - core dumped
and, `strace ./rjsuuplicant -n eth0 -u USER -p PASS -d 1 -s internet` is attached as strace_native.log ** Attachment added: strace_native.log https://bugs.launchpad.net/qemu/+bug/1246990/+attachment/3897370/+files/strace_native.log ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1246990 Title: [qemu-x86-64-linux-user 1.6.1] qemu: uncaught target signal 11 (Segmentation fault) - core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1246990/+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 1247013] [NEW] mod_python APLOG_NOERRNO unable to log on Apache 2.4
Public bug reported: When an error occurs from mod_python on Saucy (which uses Apache 2.4) there is nothing logged. I have tracked this issue down to the value of APLOG_NOERRNO being incorrect. This value is defined to be (APLOG_LEVELMASK + 1); on Apache 2.2, APLOG_LEVELMASK was 7, but on Apache 2.4 it is 15. The value in mod_python's Python code (which sadly can't use the C definition in a direct manner) is hardcoded as 8, but for Apache 2.4 it needs to be updated to 16. This variable is defined in lib/python/mod_python/apache.py, and should be an easy fix. (FWIW, I have not experienced other issues so far with the mod_python 3.3.1 patches for Apache 2.4.) (Also, I will note that the 3.4 and now 3.5 of mod_python from upstream no longer even have this variable: it still exists for backwards-compatibility with old code, but it is defined as 0.) ** Affects: libapache2-mod-python (Ubuntu) Importance: Undecided Status: New ** Patch added: patch to fix this issue against 3.3.1 https://bugs.launchpad.net/bugs/1247013/+attachment/3897448/+files/aplog_noerrno.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libapache2-mod-python in Ubuntu. https://bugs.launchpad.net/bugs/1247013 Title: mod_python APLOG_NOERRNO unable to log on Apache 2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-python/+bug/1247013/+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 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
This is still affecting users of the 1.4+bzr1693+dfsg-0ubuntu2 pacakge in Saucy. Steps to reproduce: - Install maas using the saucy server install CD. - Edit /etc/maas/import_pxe_files - set ARCHES to i.e. ARCHES=amd64/generic - Configure the rest of MaaS, click the import boot images in the UI - PXE boot a machine What happens: The machine PXE boots, gets assigned an IP address by MaaS. The node gets stuck on Trying to load: pxelinux.cfg/default and finally reboots after a timeout triggers. This results in an eternal reboot loop. What should be happening: The machine PXE boots, gets assigned an IP address, and successfully downloads a bootable image from tftp, resuming normal operations. -- 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/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+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 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
Further information: Relevant stacktrace: https://pastebin.canonical.com/99705/ -- 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/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+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 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
@tribaal: I think what you're seeing here is bug 1181334 (note the fact that the error you see mentions i386). Can you try changing /etc/maas/import_pxe_files to set ARCHES to i386/generic amd64/generic, re-run the import script and try again? -- 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/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+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 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
Sorry, I used a private pastebin, here's the public equivalent: http://pastebin.ubuntu.com/6340916/ @rvb: Yeah that looks like what I'm seeing indeed. I'll give it a try and report back! -- 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/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+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 1247013] Re: mod_python APLOG_NOERRNO unable to log on Apache 2.4
The attachment patch to fix this issue against 3.3.1 seems to be a patch. If it isn't, please remove the patch flag from the attachment, remove the patch tag, and if you are a member of the ~ubuntu- reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libapache2-mod-python in Ubuntu. https://bugs.launchpad.net/bugs/1247013 Title: mod_python APLOG_NOERRNO unable to log on Apache 2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-python/+bug/1247013/+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 1246229] Re: Error: Puppet::Parser::AST::Resource failed with error TypeError: no implicit conversion from nil to integer at ...
I'v copied your testcase with copy and paste to /etc/puppet/manifests/test.pp and run: # puppet apply /etc/puppet/manifests/test.pp Could not retrieve zpool_version: undefined method `captures' for nil:NilClass Warning: Could not retrieve fact fqdn Error: Puppet::Parser::AST::Resource failed with error TypeError: no implicit conversion from nil to integer at /etc/puppet/manifests/test.pp:5 on node pcdanisch Error: Puppet::Parser::AST::Resource failed with error TypeError: no implicit conversion from nil to integer at /etc/puppet/manifests/test.pp:5 on node pcdanisch Since this is a ruby error message, I've checked which ruby version puppet runs: /usr/bin/ruby - /etc/alternatives/ruby - /usr/bin/ruby1.9.1 Same with another machine that has been installed as 13.04 and upgraded to 13.10. I don't have a freshly installed machine here right now, I have to get at home to do so. regards -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1246229 Title: Error: Puppet::Parser::AST::Resource failed with error TypeError: no implicit conversion from nil to integer at ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1246229/+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 1246229] Re: Error: Puppet::Parser::AST::Resource failed with error TypeError: no implicit conversion from nil to integer at ...
And, btw., ruby-hiera was installed on the first, but not on the second machine. Both behave identically. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1246229 Title: Error: Puppet::Parser::AST::Resource failed with error TypeError: no implicit conversion from nil to integer at ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1246229/+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 1247107] [NEW] Runaway irqbalance consuming CPU and Memory
Public bug reported: Looks like a runaway irqbalance process is consuming massive amount of Memory and CPU. This is running on a calxeda arm server used as a build server. Was unable to find any mention of irqbalance in /var/logs. Hopefully apport recorded the right data. PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 861 root 20 0 1896m 1.5g 372 S 40.5 39.1 1447:25 irqbalance $ apt-cache policy irqbalance irqbalance: Installed: 1.0.5-2 Candidate: 1.0.5-2 Version table: *** 1.0.5-2 0 500 http://ports.ubuntu.com/ubuntu-ports/ raring/main armhf Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: irqbalance 1.0.5-2 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic armv7l ApportVersion: 2.9.2-0ubuntu8.5 Architecture: armhf Date: Fri Nov 1 06:33:51 2013 MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: irqbalance UpgradeStatus: Upgraded to raring on 2013-07-24 (99 days ago) ** Affects: irqbalance (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf raring -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1247107 Title: Runaway irqbalance consuming CPU and Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1247107/+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 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
@rvb: Yes, adding back the i386 architecture made the boot up work. I'll subscribe to bug 1181334 instead! Thanks for your help. -- 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/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+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 1181334] Re: i386 required to install amd64
Can confirm, it would save us (the landscape team, but also other users I wager) a lot of time and disk space if we could only download amd64 images and use that successfully. -- 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/1181334 Title: i386 required to install amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1181334/+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 1181334] Re: i386 required to install amd64
** Tags added: landscape -- 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/1181334 Title: i386 required to install amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1181334/+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 1159818] Re: Allow architecture armhf with template ubuntu-cloud when running on ARM
This was fixed by smoser and pushed to trunk. Here is a diff if you're interested: https://pastebin.canonical.com/99718/ -- 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/1159818 Title: Allow architecture armhf with template ubuntu-cloud when running on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1159818/+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 1247148] [NEW] rndc addzone isn't working. fix available
Public bug reported:
OS: Ubuntu 12.04,
Bind package:
ii bind91:9.8.1.dfsg.P1-4ubuntu0.7
Internet Domain Name Server
Bind folder:
drwxr-s--- 3 bind bind 4096 Nov 1 20:46 /etc/bind
* Steps to reproduce the issue
rndc -s localhost addzone 'zzz.com { type master; file
/etc/bind/master/zzz.com; };'
rndc: 'addzone' failed: permission denied
* Steps to fix
Edit /etc/init.d/bind9 , add -d /etc/bind to start-stop-daemon in start)
section
* Explanation
Named tries to store *.nzf (zones created by rndc zoneadd) in a directory from
where it started. By default it is not /etc/bind
** Affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1247148
Title:
rndc addzone isn't working. fix available
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1247148/+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 1242913] Re: /dev/pts being created with mode=600 by Lxc
Ah, my bad, Stephane. I tested Ubuntu 13.10 saucy. ** Tags added: verification-done-saucy -- 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/1242913 Title: /dev/pts being created with mode=600 by Lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242913/+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 1242913] Re: /dev/pts being created with mode=600 by Lxc
ubuntu@ip-10-164-72-103:~$ cat /etc/issue Ubuntu 13.04 \n \l ubuntu@ip-10-164-72-103:~$ dpkg -l | grep lxc ii liblxc00.9.0-0ubuntu3.7 amd64Linux Containers userspace tools (library) ii lxc0.9.0-0ubuntu3.7 amd64Linux Containers userspace tools ii lxc-docker 0.6.5 amd64lxc-docker is a Linux container runtime ii lxc-docker-0.6.5 0.6.5 amd64lxc-docker is a Linux container runtime ii lxc-templates 0.9.0-0ubuntu3.7 all Linux Containers userspace tools (development) ii python3-lxc0.9.0-0ubuntu3.7 amd64Linux Containers userspace tools (Python 3.x bindings) ubuntu@ip-10-164-72-103:~$ fgrep pts /proc/mounts devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 ubuntu@ip-10-164-72-103:~$ sudo docker run -i -t ubuntu /bin/bash root@853de93e944c:/# fgrep pts /proc/mounts devpts /dev/tty1 devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=666 0 0 devpts /dev/ptmx devpts rw,relatime,gid=5,mode=620,ptmxmode=666 0 0 ** Tags added: verification-done-raring -- 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/1242913 Title: /dev/pts being created with mode=600 by Lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242913/+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 1242913] Re: /dev/pts being created with mode=600 by Lxc
ubuntu@ip-10-185-176-79:~$ cat /etc/issue Ubuntu 12.10 \n \l ubuntu@ip-10-185-176-79:~$ dpkg -l | grep lxc ii liblxc00.8.0~rc1-4ubuntu39.12.10.5 amd64Linux Containers userspace tools (library) ii lxc0.8.0~rc1-4ubuntu39.12.10.5 amd64Linux Containers userspace tools ii lxc-docker 0.6.5 amd64lxc-docker is a Linux container runtime ii lxc-docker-0.6.5 0.6.5 amd64lxc-docker is a Linux container runtime ubuntu@ip-10-185-176-79:~$ fgrep pts /proc/mounts devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 ubuntu@ip-10-185-176-79:~$ sudo docker run -i -t ubuntu /bin/bash root@e2c33ddbd910:/# fgrep pts /proc/mounts devpts /dev/tty1 devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=666 0 0 devpts /dev/ptmx devpts rw,relatime,gid=5,mode=620,ptmxmode=666 0 0 ** Tags added: verification-done-quantal -- 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/1242913 Title: /dev/pts being created with mode=600 by Lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242913/+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 1242913] Re: /dev/pts being created with mode=600 by Lxc
Strike Comment #19. Precise is good too. ** Tags added: verification-done-precise ** Tags removed: verification-needed -- 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/1242913 Title: /dev/pts being created with mode=600 by Lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242913/+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 1242913] Re: /dev/pts being created with mode=600 by Lxc
Hang on, wrong paste there for precise... -- 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/1242913 Title: /dev/pts being created with mode=600 by Lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242913/+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 1242913] Re: /dev/pts being created with mode=600 by Lxc
ubuntu@ip-10-166-49-90:~$ cat /etc/issue Ubuntu 12.04.3 LTS \n \l ubuntu@ip-10-166-49-90:~$ dpkg -l | grep lxc ii lxc 0.7.5-3ubuntu69 Linux containers userspace tools ii lxc-docker 0.6.5 lxc-docker is a Linux container runtime ii lxc-docker-0.6.5 0.6.5 lxc-docker is a Linux container runtime ubuntu@ip-10-166-49-90:~$ fgrep pts /proc/mounts devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 ubuntu@ip-10-166-49-90:~$ sudo docker run -i -t ubuntu /bin/bash root@b244742650f6:/# fgrep pts /proc/mounts devpts /dev/tty1 devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=666 0 0 devpts /dev/ptmx devpts rw,relatime,gid=5,mode=620,ptmxmode=666 0 0 -- 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/1242913 Title: /dev/pts being created with mode=600 by Lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242913/+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 1243476] Re: Apache 2.4 transition broke the web interface
A temporary workaround is to create a symbolic link in the /etc/apache2 /conf-enabled directory to the existing configuration file in /etc/apache2/conf.d directory: sudo ln -s /etc/apache2/conf.d/backuppc.conf /etc/apache2/conf- enabled/backuppc.conf restarting the apache2 webserver should re-enable web access to backuppc -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to backuppc in Ubuntu. https://bugs.launchpad.net/bugs/1243476 Title: Apache 2.4 transition broke the web interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1243476/+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 216847] Re: sshd will not start at boot if ListenAddress is set, because network interface is not yet up
same problem with package openssh-server of Ubuntu 13.10 (Saucy) error messages in /var/log/auth.log after boot process: Nov 1 17:31:46 pc sshd[1209]: error: Bind to port xxx on yyy.yyy.y.y failed: Cannot assign requested address. Nov 1 17:31:46 pc sshd[1209]: fatal: Cannot bind any address. reason: /etc/ssh/sshd_config uses ListenAddress option solution: in /etc/init/ssh.conf change line start on runlevel [2345] to start on runlevel [2345] and net-device-up IFACE!=lo message in /var/log/auth.log after boot process now: Nov 1 17:39:20 pc sshd[1518]: Server listening on yyy.yyy.y.y port xxx. What needs to be done, so that the solution will get into the package? Could anybody help? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/216847 Title: sshd will not start at boot if ListenAddress is set, because network interface is not yet up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/216847/+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 1247229] [NEW] causes procps configure to fail
Public bug reported: error: Invalid argument setting key net.ipv4.tcp_mem found in /etc/sysctl.d/30-iscsitarget.conf ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: iscsitarget (not installed) ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33 Uname: Linux 3.2.0-34-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Fri Nov 1 18:31:17 2013 InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) MarkForUpload: True SourcePackage: iscsitarget UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iscsitarget (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1247229 Title: causes procps configure to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1247229/+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 1243476] Re: Apache 2.4 transition broke the web interface
Workaround did not work for me on a freshly installed system. Getting the following error on restart of apache2: * Restarting web server apache2 ...fail! * The apache2 configtest failed. Output of config test was: apache2: Syntax error on line 216 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/conf-enabled/backuppc.conf: No such file or directory Action 'configtest' failed. The Apache error log may have more information. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to backuppc in Ubuntu. https://bugs.launchpad.net/bugs/1243476 Title: Apache 2.4 transition broke the web interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1243476/+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 1243476] Re: Apache 2.4 transition broke the web interface
Instead this workaround worked (like MDill described in the original Bug Description): ln -s /etc/backuppc/apache.conf /etc/apache2/conf-enabled/backuppc.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to backuppc in Ubuntu. https://bugs.launchpad.net/bugs/1243476 Title: Apache 2.4 transition broke the web interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1243476/+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 1243017] Re: upstart commands break inside byobu-tmux after a session restart
** Changed in: byobu (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1243017 Title: upstart commands break inside byobu-tmux after a session restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1243017/+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 1244509] Re: .screenrc bindings overrides .byobu/keybindings
Committed revision 2230. ** Changed in: byobu (Ubuntu) Status: New = In Progress ** Changed in: byobu (Ubuntu) Importance: Undecided = Low ** Changed in: byobu (Ubuntu) Assignee: (unassigned) = Dustin Kirkland (kirkland) ** Changed in: byobu (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1244509 Title: .screenrc bindings overrides .byobu/keybindings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1244509/+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 1243017] Re: upstart commands break inside byobu-tmux after a session restart
Committed revision 2231. ** Changed in: byobu (Ubuntu) Status: New = In Progress ** Changed in: byobu (Ubuntu) Assignee: (unassigned) = Dustin Kirkland (kirkland) ** Changed in: byobu (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1243017 Title: upstart commands break inside byobu-tmux after a session restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1243017/+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 1243017] Re: upstart commands break inside byobu-tmux after a session restart
** Branch linked: lp:byobu -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1243017 Title: upstart commands break inside byobu-tmux after a session restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1243017/+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 1244509] Re: .screenrc bindings overrides .byobu/keybindings
** Branch linked: lp:byobu -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1244509 Title: .screenrc bindings overrides .byobu/keybindings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1244509/+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 1237071] Re: Incompatible with virtualenv
Committed revision 2232. ** Changed in: byobu (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1237071 Title: Incompatible with virtualenv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1237071/+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 1231490] Re: [SRU] cloud-init should handle formating the azure disks
** Branch linked: lp:ubuntu/precise-proposed/cloud-init -- 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/1231490 Title: [SRU] cloud-init should handle formating the azure disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1231490/+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 1237071] Re: Incompatible with virtualenv
** Branch linked: lp:byobu -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1237071 Title: Incompatible with virtualenv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1237071/+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 1245486] Re: package python-vm-builder 0.12.4+bzr488-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Any news on this? Why is it marked as invalid? ** Changed in: vm-builder (Ubuntu) Status: Invalid = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1245486 Title: package python-vm-builder 0.12.4+bzr488-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1245486/+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 1244509] Re: .screenrc bindings overrides .byobu/keybindings
This bug was fixed in the package byobu - 5.62-0ubuntu1 --- byobu (5.62-0ubuntu1) trusty; urgency=low * usr/share/byobu/keybindings/f-keys.tmux: - as it turns out, showing the current window name when renaming is really annoying * usr/bin/byobu-janitor, usr/lib/byobu/menu, usr/share/byobu/profiles/screenrc: LP: #1244509 - customizations of screen configuration should go in $BYOBU_CONFIG_DIR/.screenrc, which will be sourced last; rather than ~/.screenrc (which should be reserved for screen-without-byobu) * usr/bin/byobu-reconnect-sockets, usr/bin/byobu-select-session: - LP: #1243017 - add a few environment variables to restore, including upstart to ensure upstart commands resume working in a session restart * README, usr/bin/byobu-config, usr/bin/byobu-select-session, usr/lib/byobu/include/ec2instancespricing.py: - LP: #996559, LP: #988471, LP: #1237071 - Okay, this is the last time I'm going back and forth on this; for real ;-) - In our 3 python scripts, we are going to use #!/usr/bin/python + The vast majority of Byobu users are getting it from their distro, and the package itself appropriately depends on python - Advanced users, developers, and others who want to run a different python in their environment will need to sed update three scripts - I've left a hint in the README to that effect -- Dustin Kirkland kirkl...@ubuntu.com Fri, 18 Oct 2013 16:29:56 -0500 ** Changed in: byobu (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1244509 Title: .screenrc bindings overrides .byobu/keybindings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1244509/+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 1243017] Re: upstart commands break inside byobu-tmux after a session restart
This bug was fixed in the package byobu - 5.62-0ubuntu1 --- byobu (5.62-0ubuntu1) trusty; urgency=low * usr/share/byobu/keybindings/f-keys.tmux: - as it turns out, showing the current window name when renaming is really annoying * usr/bin/byobu-janitor, usr/lib/byobu/menu, usr/share/byobu/profiles/screenrc: LP: #1244509 - customizations of screen configuration should go in $BYOBU_CONFIG_DIR/.screenrc, which will be sourced last; rather than ~/.screenrc (which should be reserved for screen-without-byobu) * usr/bin/byobu-reconnect-sockets, usr/bin/byobu-select-session: - LP: #1243017 - add a few environment variables to restore, including upstart to ensure upstart commands resume working in a session restart * README, usr/bin/byobu-config, usr/bin/byobu-select-session, usr/lib/byobu/include/ec2instancespricing.py: - LP: #996559, LP: #988471, LP: #1237071 - Okay, this is the last time I'm going back and forth on this; for real ;-) - In our 3 python scripts, we are going to use #!/usr/bin/python + The vast majority of Byobu users are getting it from their distro, and the package itself appropriately depends on python - Advanced users, developers, and others who want to run a different python in their environment will need to sed update three scripts - I've left a hint in the README to that effect -- Dustin Kirkland kirkl...@ubuntu.com Fri, 18 Oct 2013 16:29:56 -0500 ** Changed in: byobu (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1243017 Title: upstart commands break inside byobu-tmux after a session restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1243017/+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 1237071] Re: Incompatible with virtualenv
This bug was fixed in the package byobu - 5.62-0ubuntu1 --- byobu (5.62-0ubuntu1) trusty; urgency=low * usr/share/byobu/keybindings/f-keys.tmux: - as it turns out, showing the current window name when renaming is really annoying * usr/bin/byobu-janitor, usr/lib/byobu/menu, usr/share/byobu/profiles/screenrc: LP: #1244509 - customizations of screen configuration should go in $BYOBU_CONFIG_DIR/.screenrc, which will be sourced last; rather than ~/.screenrc (which should be reserved for screen-without-byobu) * usr/bin/byobu-reconnect-sockets, usr/bin/byobu-select-session: - LP: #1243017 - add a few environment variables to restore, including upstart to ensure upstart commands resume working in a session restart * README, usr/bin/byobu-config, usr/bin/byobu-select-session, usr/lib/byobu/include/ec2instancespricing.py: - LP: #996559, LP: #988471, LP: #1237071 - Okay, this is the last time I'm going back and forth on this; for real ;-) - In our 3 python scripts, we are going to use #!/usr/bin/python + The vast majority of Byobu users are getting it from their distro, and the package itself appropriately depends on python - Advanced users, developers, and others who want to run a different python in their environment will need to sed update three scripts - I've left a hint in the README to that effect -- Dustin Kirkland kirkl...@ubuntu.com Fri, 18 Oct 2013 16:29:56 -0500 ** Changed in: byobu (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1237071 Title: Incompatible with virtualenv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1237071/+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 1241785] Re: should allow nesting without changing TERM
This bug was fixed in the package byobu - 5.62-0ubuntu1 --- byobu (5.62-0ubuntu1) trusty; urgency=low * usr/share/byobu/keybindings/f-keys.tmux: - as it turns out, showing the current window name when renaming is really annoying * usr/bin/byobu-janitor, usr/lib/byobu/menu, usr/share/byobu/profiles/screenrc: LP: #1244509 - customizations of screen configuration should go in $BYOBU_CONFIG_DIR/.screenrc, which will be sourced last; rather than ~/.screenrc (which should be reserved for screen-without-byobu) * usr/bin/byobu-reconnect-sockets, usr/bin/byobu-select-session: - LP: #1243017 - add a few environment variables to restore, including upstart to ensure upstart commands resume working in a session restart * README, usr/bin/byobu-config, usr/bin/byobu-select-session, usr/lib/byobu/include/ec2instancespricing.py: - LP: #996559, LP: #988471, LP: #1237071 - Okay, this is the last time I'm going back and forth on this; for real ;-) - In our 3 python scripts, we are going to use #!/usr/bin/python + The vast majority of Byobu users are getting it from their distro, and the package itself appropriately depends on python - Advanced users, developers, and others who want to run a different python in their environment will need to sed update three scripts - I've left a hint in the README to that effect -- Dustin Kirkland kirkl...@ubuntu.com Fri, 18 Oct 2013 16:29:56 -0500 ** Changed in: byobu (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1241785 Title: should allow nesting without changing TERM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1241785/+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 1247262] [NEW] [SRU] datasource for smartos uses util.is_true instead of futil.is_true
You have been subscribed to a public bug:
[Impact]: The cloud-init version Precise uses the wrong is_true test
from util instead of futil for the SmartOS datasource. If a user sends
over a user-script or user-data, the instance will be unaccessable due
to a stack trace. This means that user-data or user-scripts are fatal to
the instance as the user will be unable to access system using SmartOS
as the virtualization platform.
[Test Case]:
1. Create a simple user-data script
2. Boot up 12.04 in SmartOS
3. Update the instance meta-data with user-script
4. delete /var/lib/cloud
5. Run cloud-init start and cloud-init-cfg all
6. Check /var/log/cloud-init.log for errors
7. Confirm that simple user-data script ran
8. The user-data script should be found in /var/lib/cloud/instance/user-data.txt
[REGRESSION] None. This change is fixes broken functionality and is a
two line change. This has been tested on SmartOS and confirmed to fix
the problem.
datasource for smartos uses util.is_true instead of futil.is_true, this
causes a stack trace on SmartOS
2013-11-01 18:21:39,683 - cloud-init[INFO]: cloud-init start-local running:
Fri, 01 Nov 2013 18:21:39 +. up 7.28 seconds
2013-11-01 18:21:39,874 - __init__.py[DEBUG]: searching for data source in []
2013-11-01 18:21:39,874 - __init__.py[DEBUG]: Did not find data source.
searched classes: []
2013-11-01 18:21:43,765 - cloud-init[INFO]: cloud-init start running: Fri, 01
Nov 2013 18:21:43 +. up 11.19 seconds
2013-11-01 18:21:43,861 - __init__.py[DEBUG]: searching for data source in
['DataSourceSmartOS']
2013-11-01 18:21:43,861 - DataSourceSmartOS.py[DEBUG]: Getting hostname from
dmidecode
2013-11-01 18:21:43,864 - DataSourceSmartOS.py[DEBUG]: Determining hypervisor
product name via dmidecode
2013-11-01 18:21:45,485 - __init__.py[WARNING]: get_data of DataSourceSmartOS
raised 'module' object has no attribute 'is_true'
2013-11-01 18:21:45,500 - util.py[DEBUG]: Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/cloudinit/__init__.py, line 215, in
get_data_source
if s.get_data():
File /usr/lib/python2.7/dist-packages/cloudinit/DataSourceSmartOS.py, line
144, in get_data
md[ci_noun] = self.query(smartos_noun, strip=strip)
File /usr/lib/python2.7/dist-packages/cloudinit/DataSourceSmartOS.py, line
178, in query
b64=b64)
File /usr/lib/python2.7/dist-packages/cloudinit/DataSourceSmartOS.py, line
240, in query_data
b64 = util.is_true(b64)
AttributeError: 'module' object has no attribute 'is_true'
2013-11-01 18:21:45,500 - __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceSmartOS'] {noformat}
{noformat}
** Affects: cloud-init (Ubuntu)
Importance: High
Assignee: Ben Howard (utlemming)
Status: In Progress
--
[SRU] datasource for smartos uses util.is_true instead of futil.is_true
https://bugs.launchpad.net/bugs/1247262
You received this bug notification because you are a member of Ubuntu Server
Team, which is subscribed to cloud-init in Ubuntu.
--
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 1247262] Re: [SRU] datasource for smartos uses util.is_true instead of futil.is_true
** Package changed: ubuntu = cloud-init (Ubuntu) -- 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/1247262 Title: [SRU] datasource for smartos uses util.is_true instead of futil.is_true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1247262/+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 1247262] Re: [SRU] datasource for smartos uses util.is_true instead of futil.is_true
** Also affects: cloud-init (Ubuntu Precise) Importance: Undecided Status: New -- 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/1247262 Title: [SRU] datasource for smartos uses util.is_true instead of futil.is_true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1247262/+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 1247262] Re: [SRU] datasource for smartos uses util.is_true instead of futil.is_true
** Description changed:
[Impact]: The cloud-init version Precise uses the wrong is_true test
from util instead of futil for the SmartOS datasource. If a user sends
over a user-script or user-data, the instance will be unaccessable due
to a stack trace. This means that user-data or user-scripts are fatal to
the instance as the user will be unable to access system using SmartOS
as the virtualization platform.
+
+ This only affects 12.04. futil is a backport of utilities in future
+ version. util.is_true is valid for 12.10 and later. As result, there is
+ no fix needed for quantal and later.
[Test Case]:
1. Create a simple user-data script
2. Boot up 12.04 in SmartOS
3. Update the instance meta-data with user-script
4. delete /var/lib/cloud
5. Run cloud-init start and cloud-init-cfg all
6. Check /var/log/cloud-init.log for errors
7. Confirm that simple user-data script ran
8. The user-data script should be found in
/var/lib/cloud/instance/user-data.txt
[REGRESSION] None. This change is fixes broken functionality and is a
two line change. This has been tested on SmartOS and confirmed to fix
the problem.
datasource for smartos uses util.is_true instead of futil.is_true, this
causes a stack trace on SmartOS
2013-11-01 18:21:39,683 - cloud-init[INFO]: cloud-init start-local running:
Fri, 01 Nov 2013 18:21:39 +. up 7.28 seconds
2013-11-01 18:21:39,874 - __init__.py[DEBUG]: searching for data source in []
2013-11-01 18:21:39,874 - __init__.py[DEBUG]: Did not find data source.
searched classes: []
2013-11-01 18:21:43,765 - cloud-init[INFO]: cloud-init start running: Fri, 01
Nov 2013 18:21:43 +. up 11.19 seconds
2013-11-01 18:21:43,861 - __init__.py[DEBUG]: searching for data source in
['DataSourceSmartOS']
2013-11-01 18:21:43,861 - DataSourceSmartOS.py[DEBUG]: Getting hostname from
dmidecode
2013-11-01 18:21:43,864 - DataSourceSmartOS.py[DEBUG]: Determining hypervisor
product name via dmidecode
2013-11-01 18:21:45,485 - __init__.py[WARNING]: get_data of DataSourceSmartOS
raised 'module' object has no attribute 'is_true'
2013-11-01 18:21:45,500 - util.py[DEBUG]: Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/cloudinit/__init__.py, line 215, in
get_data_source
if s.get_data():
File /usr/lib/python2.7/dist-packages/cloudinit/DataSourceSmartOS.py,
line 144, in get_data
md[ci_noun] = self.query(smartos_noun, strip=strip)
File /usr/lib/python2.7/dist-packages/cloudinit/DataSourceSmartOS.py,
line 178, in query
b64=b64)
File /usr/lib/python2.7/dist-packages/cloudinit/DataSourceSmartOS.py,
line 240, in query_data
b64 = util.is_true(b64)
AttributeError: 'module' object has no attribute 'is_true'
2013-11-01 18:21:45,500 - __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceSmartOS'] {noformat}
{noformat}
--
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/1247262
Title:
[SRU] datasource for smartos uses util.is_true instead of
futil.is_true
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1247262/+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 1247262] Re: [SRU] datasource for smartos uses util.is_true instead of futil.is_true
Hello Ben, or anyone else affected, Accepted cloud-init into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cloud- init/0.6.3-0ubuntu1.9 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Precise) Status: New = Fix Committed ** Tags added: verification-needed ** Changed in: cloud-init (Ubuntu Precise) Importance: Undecided = High -- 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/1247262 Title: [SRU] datasource for smartos uses util.is_true instead of futil.is_true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1247262/+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
