Re: Where is network configuration "hidden" on Ubuntu 16.04?
On 08/10/18 10:57, Little Girl wrote: Where else can I look for the remnnts of the "5" configuration which are being applied at boot and preventing parts of the file-based configuration from working? I even decompressed a copy of initrd.img... and found nothing. [...] If nothing else, hopefully this message will draw attention to your original message and maybe someone with a more appropriate solution will join in. I find this alias useful to search or query various config settings... alias q='find -type f -print0 | xargs -0 grep ' then "cd /etc" (most often) and ie; "q 12.34.56.78" the IP being set from the previous 5 machine on the 2 machine. Change the IP for any unique info related to the other machine and you may locate the remnants of old config files. /var/lib/ is another place to look. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Ubuntu server "Live CD"?
On 07/09/18 07:26, Leroy Tennison wrote: I have a situation where I need to quickly bring up an Ubuntu 16.04 server environment on physical hardware without doing an install (I'm "borrowing" hardware set aside for other use). [...] Is there a better way I can mimic "Live CD" behavior with better functionality? You question was already answered by David but FWIW when I've been in a situation like this I install the current ISO installer onto another USB stick and boot that to do any hardware forensics or diagnostics. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Deprecation notice for mail-stack-delivery (dovecot) - planned to be dropped in 18.10
On 5/12/18 2:13 AM, Serge E. Hallyn wrote: I installed by hand, but am very interested in upping the number of people using self-hosted email, so interested in helping with that. FWIW, and please excuse this off-topic message and self-promotion, but I've been developing a very light weight mail/web/dns server with a PHP frontend that could be considered BETA quality, ie; mostly usable. It is probably quite relevant because it is 100% developed and based on Ubuntu 18.04 and significantly more sophisticated than the current mail-stack-delivery package -> https://github.com/netserva -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Xenial on USB stick install can't detect itself
On 07/04/16 12:54, Seth Arnold wrote: The usb stick with the server iso is fine and the usb keyboard/mouse works okay on this hardware, it's the destination installation on yet another usb stick that is the problem. When I boot onto the installed OS the initrd does not detect the partition UUID and drops me to the initramfs prompt and the Ah, I see. It feels unlikely to be your issue, but you may wish to fiddle with the switch in your bios that controls between legacy bios, uefi, and a combination of the two.. my first install attempt didn't work because I used the "both" setting in my bios. I get the same results on 2 laptops so I don't think it's a BIOS issue and thanks to your suggestion I have tried some BIOS boot variations but it's super annoying to have to waste time doing this when 15.10 works fine. Last night I tried again by loading a daily ISO on the same kind of brand new USB stick as the destination and put both into the HP microserver and did the install on that device. This time the partition was found and it booted okay BUT now the ethernet interface is missing (tg3.ko) so even though I now have USB keyboard access I still can't upgrade the packages. Maybe this is just my bad luck trying beta/dailys that just happen to still have bugs in the installer that just happen to affect my current needs. I have been running xenial on my main work laptop for 4 months now and a few weeks ago I was even so bold as to upgrade my main DELL online server from wily to xenial and that seems to be working fine. I think I had good reason to feel confident enough to start installing late term xenial iso's a few weeks before the final release. However, yesterday I ordered a new DELL server and the techs were good enough to install the last xenial beta2 and the SSD drives had a hdparm test of 118 Mb/s which is slower than the 200 Mb/s on my other server with a SATA drive! That tech is now in a world of pain because reinstalling the beta iso has lost usb keyboard access to the DELL chasis (he is onsite rather than using DRAC). These are my problems because I am using a pre-release, I understand that, but as I mentioned I had (false) confidence after using xenial on a couple of key computers and on DOZENs of VPSs in the last 2 months (on older centos kernels) that "it's time" to go all in and start installing to more serious hardware. Frankly, my confidence in ubuntu server is shattered and I'm not sure these fundamental installation issues will be fixed in the next ~2 weeks. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Xenial on USB stick install can't detect itself
On 07/04/16 04:55, Seth Arnold wrote: Which image did you start from? Unfortunately I'm not 100% sure now. It might have been a beta2 or a daily from a week ago. I did a recent hardware install using ubuntu-16.04-beta2-server-amd64.iso (0f948fea5a587a62a873d2c001948a6ffbda20b67b05a468006caf9dfd41bcd7) and was able to see both the USB installer stick as well as the usb keyboard I used to drive the installation. The usb stick with the server iso is fine and the usb keyboard/mouse works okay on this hardware, it's the destination installation on yet another usb stick that is the problem. When I boot onto the installed OS the initrd does not detect the partition UUID and drops me to the initramfs prompt and the usb keyboard also does not work so I can't really investigate what's missing but it sure seems like some essential usb initrd or kernel modules are missing on the installed to usb stick. Like I say, I've done this many dozens of times before without an issue so if something like this is happening for an LTS release then that is a concern. I boot the ext4-based OS (and swap) usb stick from an internal usb slot in a HP microserver so that I don't have to partition the 4 btrfs raid-1 drives. Perhaps xenial server has not been well tested on small-iron servers. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Xenial on USB stick install can't detect itself
I just installed a recent daily xenial 64bit server onto a USB stick that is to go into the internal USB slot of a HP microserver. It used to work fine with wily and even a manually upgraded wily -> xenial up till a month ago. This is the 2nd USB stick I've tried and booting up just gets to the initramfs prompt after 30 seconds of... Begin: Running /scripts/local-block ... done. then it says can't find the UUID of the partition I just booted from. On that HP microserver I have no USB keyboard access so I can't investigate it any further but when I boot the same USB stick on my laptop I get the same result and sure enough there is no typical /dev/sdb* devices and blkid does not show the device I just booted from! It's like the install did not add any USB drivers or modules to the initrd image orkernel. Is this expected behavior with xenial server installs and if so how can I work around this and force USB modules to be installed to initrd? -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Bug 1564832] [NEW] Apparmor profile for NTPd needs to allow read/write access to /dev/ppsX
Public bug reported: Am trying to get NTP to work with the kernel PPS subsystem, for high- accuracy GPS-based clocks. On startup of NTPd I see this: Apr 1 11:18:58 doorway kernel: [ 300.387443] audit: type=1400 audit(1459505938.042:9): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/dev/pps0" pid=1668 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Adding this to the usr.sbin.ntpd apparmor profile eliminated the error: /dev/pps[0-9]* rw, I'm not sure why ntpd needs *write* access to ppsN though, perhaps that can be improved. ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1564832 Title: Apparmor profile for NTPd needs to allow read/write access to /dev/ppsX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1564832/+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
Re: [Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
Sorry about this. I do believe it's addressed by our move to Mongo 3.2, but I haven't tested that as the branch hasn't quite landed. It is targeted to Juju 2.0 and Ubuntu 16.04 though. Mark -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+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
Re: Calling for Server Guide reviewers/contributors - - XENIAL
I'll offer to help out. Mark On Thursday, March 17, 2016, Doug Smythies <dsmyth...@telus.net> wrote: > On 2106.02.04 07:40 Peter Matulis wrote: > > > We need people to review current instructions provided in the > > Ubuntu Server Guide and suggest improvements. > > Please visit the following link and help out where you can. > > > > > https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/UbuntuServerGuide > > > > The subjects we need the most help with this cycle are the following, in > order of priority: > > > > Zentyal > > Ceph > > systemd > > Chat Applications overview > > IRC Server > > Jabber Instant Messaging Server > > > > Samba - Introduction > > Samba - File Server > > Samba - Print Server > > Samba - Securing File and Print Server > > Samba - As a Domain Controller > > Samba - Active Directory Integration > > OpenVPN > > Samba and LDAP > > Exim4 > > Mailman > > Mail Filtering > > > > DNS troubleshooting > > AppArmor > > Certificates > > eCryptfs > > Monitoring overview > > Nagios > > Munin > > Ruby on Rails > > phpMyAdmin > > > > Instead of helping on a per-topic basis you can also offer fixes to > existing bugs: > > > > https://bugs.launchpad.net/serverguide > > > > We're also looking for help in maintaining the guide in terms > > of validating reviews (merge proposals). > > We need help with the Serverguide. > In particular, we need help from subject matter experts. > While the documentation string freeze deadline has just past, > the Serverguide is not bound by that deadline because it is not > a released package, so there is still time to contribute. > > To summarize where are at the moment: NOWHERE!!! Nothing has > been contributed for revised for the 16.04 LTS cycle. > > ... Doug > > > > -- > ubuntu-doc mailing list > ubuntu-...@lists.ubuntu.com <javascript:;> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-doc > -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Bug 1445616] Re: crmsh in vivid/wily/xenial is not compatible with pacemaker
I'd love a Wily fix as well. This is preventing me from moving forward on a project to load balance my web servers. -- 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/1445616 Title: crmsh in vivid/wily/xenial is not compatible with pacemaker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1445616/+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
Re: [Bug 1512980] Re: Please enable PPS in the Ubuntu build of ntpd
Thanks Robie, excited to take it for a spin :) -- 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/1512980 Title: Please enable PPS in the Ubuntu build of ntpd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1512980/+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
Re: [Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
Paul, I believe the plan is to move to MongoDB 3.2 with Juju 2.0, which solves the issue. I am not sure when we will have an upgrade mechanism from 1.x to 2.x but we intend to do that in due course. Mark -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+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 1512980] Re: Please enable PPS in the Ubuntu build of ntpd
Thanks kick-d :) -- 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/1512980 Title: Please enable PPS in the Ubuntu build of ntpd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1512980/+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 1494141] Re: HAProxy 1.5 init script does not terminate processes
I don't understand the current status of this bug. I think what I'm reading is that this was fixed for trusty-backports inside of the work done to close #1481737, but I'm not certain. Is there anyone that could confirm that? Thank you -- 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/1494141 Title: HAProxy 1.5 init script does not terminate processes To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1494141/+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 1460164] Re: upgrade of openvswitch-switch can sometimes break neutron-plugin-openvswitch-agent
Is the fix here to ensure that restarts of one are automatically sequenced with restarts of the other service? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1460164 Title: upgrade of openvswitch-switch can sometimes break neutron-plugin- openvswitch-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1460164/+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 1273462] Re: Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists
In Bug #1521771, I spent some time tracking down different behavior between the mysql-5.5 "init" and "upstart" scripts. They differ on how many seconds are waited between the SIGTERM and SIGKILL signals are sent. Different values can mean the difference between a slower clean shutdown and a shutdown interrupted by a SIGKILL signal. In the case of that of that package, redirecting the "init.d" calls to the upstart script will have a positive impact in my opinion-- giving more time for MySQL to shutdown cleanly. So the proposed patch will be functionally helpful. I do suggest that for any package that's affected by this, the "init.d" script should be cleaned out, so only the code remains that redirects people to the upstart script. There is nothing about this line of code in an "init.d" script which indicates that that all the code below it is about to ignored: . /lib/lsb/init-functions Nor does the proposed patch emit any output that confirms that redirect is happened. The result is that someone could pull their hair out wondering why the "init.d" script is not behaving as expected. Realize that there are packages like "ec2-consistent-snapshot" which exist only in a PPA and make a hardcoded call to "/etc/init.d/mysql". It does that in hopes of working on non-Debian-based systems as well. (The package is also several years old, from an era when init.d scripts were more common). I'm not sure what small projects are supposed to when they want to issue a command like "stop mysql" in a way that might work across SysV init scripts, upstart and systemd. -- 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/1273462 Title: Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1273462/+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
Re: [Bug 1521771] Re: init.d.mysql shutdown timeout value does not match init/mysql.conf value
Thanks for the reply. For the mysql-5.6 package, I recommend clearly out the "init.d" script except for the redirect to the "upstart" script. This will avoid the false impression that the code in in the "init.d" script is still active. Mark -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1521771 Title: Shutdown timeout values are inconsistent between init.d, upstart and systemd init scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1521771/+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 1521771] [NEW] init.d.mysql shutdown timeout value does not match init/mysql.conf value
Public bug reported: In `/etc/init/mysql.conf`, the configuration is set to wait 5 minutes after a SIGTERM is issued before a SIGKILL is issued. The value was intentionally set that high because sometimes the default of 5 seconds wasn't long enough [1]. 1. https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.1/+bug/620441 The code used for this in the upstart script is: kill timeout 300 However the parallel change was not made to /etc/init.d/mysql It has the same logic, but waits only 10 seconds, like this: ``` killall -15 mysqld server_down= for i in 1 2 3 4 5 6 7 8 9 10; do sleep 1 if mysqld_status check_dead nowarn; then server_down=1; break; fi done if test -z "$server_down"; then killall -9 mysqld; fi ``` I would consider submitting a patch to change the timeout from 10 seconds to 300 in this script, but I can't believe spelling out the numbers from 1 to 300 is the best way to do that, as the current code counts to 10 like this. I know that using upstart and the "service" command are the preferred way to manage MySQL, but as long as the init.d script continues to be shipped it should parallel the upstart script when possible. This change matters to projects like ec2-consistent-shutdown, which tries to shutdown MySQL cleanly across a number of linux variations. It currently does that with a hardcoded reference to /etc/init.d/mysql, which apparenty works, while I don't think the upstart syntax would be as portable. [2] 2. https://github.com/alestic/ec2-consistent-snapshot/pull/68 ** Affects: mysql-5.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1521771 Title: init.d.mysql shutdown timeout value does not match init/mysql.conf value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1521771/+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
Re: [Bug 1512980] Re: Please enable PPS in the Ubuntu build of ntpd
Thank you Christian! Let's go with 4.2.8 for all the obvious reasons, get it done in Ubuntu and offer up the patch to Debian. Mark -- 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/1512980 Title: Please enable PPS in the Ubuntu build of ntpd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1512980/+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 1512980] [NEW] Please enable PPS in the Ubuntu build of ntpd
Public bug reported: NTPD includes a reference clock driver called "pps" which uses a modern kernel mechanism for pulse-per-second devices for very accurate timekeeping. PPS is particularly useful for anybody building a stratum 0 GPS-disciplined time server. Please could we enable the PPS driver in Ubuntu's build of NTP? http://doc.ntp.org/4.2.6/drivers/driver22.html Thanks, Mark ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1512980 Title: Please enable PPS in the Ubuntu build of ntpd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1512980/+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
Re: [Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
I believe the fix here is in the work to rev to mongo 3.0 or 3.2 in 16.04. Mark -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+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 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting
The proposed update works for us. When is it likely to be released as we don't want to do this on our production servers? -- 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/1504781 Title: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504781/+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 1236439] Re: switch to use hostnames like nova breaks upgrades of l3-agent
** Changed in: neutron Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1236439 Title: switch to use hostnames like nova breaks upgrades of l3-agent To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1236439/+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 1505164] [NEW] python3.4 3.4.3 prevents installation of libapache2-mod-wsgi-py3
Public bug reported: Steps to reproduce (using a docker container): $ docker pull ubuntu:trusty $ docker run --rm -it ubuntu:trusty /bin/bash # lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 # apt-get update # apt-get install python3.4 python3.4 is already the newest version. # python3 --version Python 3.4.3 # dpkg -l python3.4 ii python3.4 3.4.3-1ubuntu1~14.0 # apt-get install apache2 ... # apt-get install libapache2-mod-wsgi-py3 The following packages have unmet dependencies: libapache2-mod-wsgi-py3 : Depends: libpython3.4 (>= 3.4~b1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ** Affects: mod-wsgi (Ubuntu) Importance: Undecided Status: New ** Affects: python3.4 (Ubuntu) Importance: Undecided Status: New ** Description changed: Steps to reproduce (using a docker container): $ docker pull ubuntu:trusty - $ docker run --rm -it ubuntu:trust /bin/bash + $ docker run --rm -it ubuntu:trusty /bin/bash # lsb_release -rd Description: Ubuntu 14.04.3 LTS Release: 14.04 # apt-get update # apt-get install python3.4 python3.4 is already the newest version. # python3 --version Python 3.4.3 # dpkg -l python3.4 ii python3.4 3.4.3-1ubuntu1~14.0 # apt-get install apache2 ... # apt-get install libapache2-mod-wsgi-py3 The following packages have unmet dependencies: - libapache2-mod-wsgi-py3 : Depends: libpython3.4 (>= 3.4~b1) but it is not going to be installed + libapache2-mod-wsgi-py3 : Depends: libpython3.4 (>= 3.4~b1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ** Also affects: mod-wsgi (Ubuntu) Importance: Undecided Status: New ** Summary changed: - 3.4.3 prevents installation of libapache2-mod-wsgi-py3 + python3.4 3.4.3 prevents installation of libapache2-mod-wsgi-py3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mod-wsgi in Ubuntu. https://bugs.launchpad.net/bugs/1505164 Title: python3.4 3.4.3 prevents installation of libapache2-mod-wsgi-py3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mod-wsgi/+bug/1505164/+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 1505164] Re: Ubuntu Docker images include packages deleted from trusty-updates
Thank you @racb for taking the time to look into this and reassign it correctly - apols for my clumsy assignment. Dan @daniel-thewatkins - thanks dude. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mod-wsgi in Ubuntu. https://bugs.launchpad.net/bugs/1505164 Title: Ubuntu Docker images include packages deleted from trusty-updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1505164/+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 1497393] [NEW] openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.5: openvswitch kernel module failed to build
Public bug reported: This appears at every update ProblemType: Package DistroRelease: Ubuntu 12.04 Package: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.5 ProcVersionSignature: Ubuntu 3.13.0-63.104~precise1-generic 3.13.11-ckt25 Uname: Linux 3.13.0-63-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.9 Architecture: i386 DKMSKernelVersion: 3.13.0-64-generic Date: Fri Sep 18 18:32:21 2015 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MarkForUpload: True PackageArchitecture: all PackageVersion: 1.4.6-0ubuntu1.12.04.5 SourcePackage: openvswitch Title: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.5: openvswitch kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1497393 Title: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.5: openvswitch kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1497393/+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 1448254] Re: openvswitch systemd unit file ordering wrong
Sorry, lost track of the bug as it fell into 100 papercuts... if it helps I solved my ordering problem by modifying the /lib/systemd/sysytem/openvswitch-nonetwork.service as follows [Unit] Description=Open vSwitch Internal Unit PartOf=openvswitch-switch.service # Without this all sorts of looping dependencies occur doh! DefaultDependencies=no #precedants pulled from isup@ service requirements After=apparmor.service local-fs.target systemd-tmpfiles-setup.service #subsequent to this service we need the network to start Wants=network-pre.target openvswitch-switch.service Before=network-pre.target openvswitch-switch.service [Service] Type=oneshot RemainAfterExit=yes EnvironmentFile=-/etc/default/openvswitch-switch ExecStart=/usr/share/openvswitch/scripts/ovs-ctl start \ --system-id=random $OPTIONS ExecStop=/usr/share/openvswitch/scripts/ovs-ctl stop This pulled up the services and allowed my configuration to work openvswitch-nonetwork.service ● ├─openvswitch-switch.service ● └─network-pre.target ● ├─ifup@br-eth2.service ● ├─ifup@br-ex.service ● ├─ifup@eth0.service ● ├─ifup@ovs-system.service ● ├─networking.service ● └─network.target ● ├─mysql.service ● ├─openvswitch-switch.service ● ├─rabbitmq-server.service ● ├─rc-local.service ● ├─ssh.service ● └─network-online.target ● ├─apache2.service ● ├─dns-clean.service ● └─kerneloops.service (the dots are green :) ) There is lots of noise on the net about chickens and eggs, so I do not know if it solves some other case The thing that took me so long to solve it (besides unfamiliarity of systemd) was the AUTOMATIC inclusion of dependencies, who on earth dreamt that up? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1448254 Title: openvswitch systemd unit file ordering wrong To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+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 1480513] [NEW] nginx-common should not depend on python
Public bug reported: None of the dependencies for nginx-common (lsb-base and init-system- helpers) require python support so the nginx-common package should not force the python package to be installed. The current python dependency should be moved to Suggests or added to the other nginx-* packages that may need python support. The nginx-light package does not need python but because of the dependency in nginx-common it forces python to be installed. ** Affects: nginx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1480513 Title: nginx-common should not depend on python To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1480513/+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 1480513] Re: nginx-common should not depend on python
Thank you for considering this request and marking it appropriately. Please kindly suggest to the Debian folks that this future ngx-conf utility should be in a separate package to isolate the need for python. I only noticed this because I routinely remove anything to do with python from my VPS and lxc containers to keep them as light as possible and I was puzzled why installing nginx(-light) tried to reinstall python-2.7. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1480513 Title: nginx-common should not depend on python To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1480513/+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 1448254] Re: openvswitch systemd unit file ordering wrong
I have a the same problem. In systemd, there are two files openvswitch-nonetwork.service openvswitch-switch.service which are supposed to fix this problem I am testing OpenStack with VXLAN and require sudo ovs-vsctl add-br br-eth2 sudo ovs-vsctl set port br-eth2 tag=2001 sudo ovs-vsctl add-port br-eth2 vxlan1 sudo ovs-vsctl set interface vxlan1 type=vxlan options:remote_ip=192.168.102.205 sudo ovs-vsctl add-port br-eth2 vxlan2 sudo ovs-vsctl set interface vxlan2 type=vxlan options:remote_ip=192.168.102.234 sudo ovs-vsctl add-br br-ex sudo ovs-vsctl add-port br-ex eth0 then bring up the network from /etc/network/interfaces with auto lo iface lo inet loopback auto eth0 iface eth0 inet manual up ifconfig $IFACE 0.0.0.0 up up ip link set $IFACE promisc on down ip link set $IFACE promisc off down ifconfig $IFACE down auto br-ex iface br-ex inet static address 192.168.102.206 netmask 255.255.255.0 gateway 192.168.102.36 dns-nameservers 192.168.102.10 192.168.102.50 up ip link set $IFACE promisc on down ip link set $IFACE promisc off auto br-eth2 iface br-eth2 inet static address 10.1.0.11 netmask 255.255.255.0 up ip link set $IFACE promisc on down ip link set $IFACE promisc off mtu 1446 from sudo systemctl list-unit-files i get openvswitch-nonetwork.service static openvswitch-switch.service enabled so I assume they are running -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1448254 Title: openvswitch systemd unit file ordering wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1448254/+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 1349949] Re: Juju's mongodb does not need to log every command in syslog
Can we put that fragment in the jujud blob, so it's installed when Juju is installed? 99-jujud.conf might be a better name for it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+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 1450563] Re: python-nova is missing gettextutils.py breaking nova-compute-flex
What release is this? juno, kilo, liberty?I ran a couple of tests with Kilo and the ubuntu cloud archive and don't seem to hit this issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1450563 Title: python-nova is missing gettextutils.py breaking nova-compute-flex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1450563/+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
Re: ubuntu-server Digest, Vol 113, Issue 6
It's the hypervisor, most likely. I've got one too. I have to unplug the front power switch, as it keeps power cycling randomly otherwize. mark. On 28 May 2015 at 13:00, ubuntu-server-requ...@lists.ubuntu.com wrote: Send ubuntu-server mailing list submissions to ubuntu-server@lists.ubuntu.com To subscribe or unsubscribe via the World Wide Web, visit https://lists.ubuntu.com/mailman/listinfo/ubuntu-server or, via email, send a message with subject or body 'help' to ubuntu-server-requ...@lists.ubuntu.com You can reach the person managing the list at ubuntu-server-ow...@lists.ubuntu.com When replying, please edit your Subject line so it is more specific than Re: Contents of ubuntu-server digest... Today's Topics: 1. IBM Server/EFI Boot: What could have happened? (Jorge Andres Brugger) -- Message: 1 Date: Wed, 27 May 2015 09:36:54 -0300 From: Jorge Andres Brugger jbrug...@dasu.com.ar To: ubuntu-server@lists.ubuntu.com Subject: IBM Server/EFI Boot: What could have happened? Message-ID: mk4dn5$3mr$1...@ger.gmane.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed I have an IBM System x server with Ubuntu Server 14.04, standard settings (UEFI BIOS defaults, LSI RAID controller, two mirrored disks). LSI config said RAID is optimal. Yesterday I rebooted it and refuses to boot because missing operating system. After fighting for a while with the problem I managed to explicitly configure the boot using /ubuntu/grubx64.efi and the server is alive again. This was not configured this way before. In the past I?ve rebooted the server many times without any issue. What could have happened? How I can do to return to the previous setting? (i.e. standard and non forced EFI boot config) Thank you very much! -- Jorge Andr?s Brugger Departamento de Inform?tica DASU - Obra Social del Personal de la Universidad Nacional de la Patagonia Comodoro Rivadavia, Chubut, Argentina Tel?fono (0297) 446- int. 103 Correo electr?nico: jbrug...@dasu.com.ar Website: www.dasu.com.ar Quien hace, puede equivocarse. Quien nada hace, ya est? equivocado. (Daniel Kon) -- -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam End of ubuntu-server Digest, Vol 113, Issue 6 * -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: ubuntu-server Digest, Vol 113, Issue 7
.. and another thing.. That ubuntu desktop is horrible. It's just like that as there is nothing to beat the old start menu system. It's like that just for the sake of it. Long live KDE (it's in the app store) mark On 29 May 2015 at 13:00, ubuntu-server-requ...@lists.ubuntu.com wrote: Send ubuntu-server mailing list submissions to ubuntu-server@lists.ubuntu.com To subscribe or unsubscribe via the World Wide Web, visit https://lists.ubuntu.com/mailman/listinfo/ubuntu-server or, via email, send a message with subject or body 'help' to ubuntu-server-requ...@lists.ubuntu.com You can reach the person managing the list at ubuntu-server-ow...@lists.ubuntu.com When replying, please edit your Subject line so it is more specific than Re: Contents of ubuntu-server digest... Today's Topics: 1. Re: ubuntu-server Digest, Vol 113, Issue 6 (Mark Carter) -- Message: 1 Date: Fri, 29 May 2015 12:29:33 +0100 From: Mark Carter marcasci...@gmail.com To: ubuntu-server@lists.ubuntu.com Subject: Re: ubuntu-server Digest, Vol 113, Issue 6 Message-ID: caor23r9xranshe1zvp+qug+evmy1q6dlrahemughghwkd3y...@mail.gmail.com Content-Type: text/plain; charset=utf-8 It's the hypervisor, most likely. I've got one too. I have to unplug the front power switch, as it keeps power cycling randomly otherwize. mark. On 28 May 2015 at 13:00, ubuntu-server-requ...@lists.ubuntu.com wrote: Send ubuntu-server mailing list submissions to ubuntu-server@lists.ubuntu.com To subscribe or unsubscribe via the World Wide Web, visit https://lists.ubuntu.com/mailman/listinfo/ubuntu-server or, via email, send a message with subject or body 'help' to ubuntu-server-requ...@lists.ubuntu.com You can reach the person managing the list at ubuntu-server-ow...@lists.ubuntu.com When replying, please edit your Subject line so it is more specific than Re: Contents of ubuntu-server digest... Today's Topics: 1. IBM Server/EFI Boot: What could have happened? (Jorge Andres Brugger) -- Message: 1 Date: Wed, 27 May 2015 09:36:54 -0300 From: Jorge Andres Brugger jbrug...@dasu.com.ar To: ubuntu-server@lists.ubuntu.com Subject: IBM Server/EFI Boot: What could have happened? Message-ID: mk4dn5$3mr$1...@ger.gmane.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed I have an IBM System x server with Ubuntu Server 14.04, standard settings (UEFI BIOS defaults, LSI RAID controller, two mirrored disks). LSI config said RAID is optimal. Yesterday I rebooted it and refuses to boot because missing operating system. After fighting for a while with the problem I managed to explicitly configure the boot using /ubuntu/grubx64.efi and the server is alive again. This was not configured this way before. In the past I?ve rebooted the server many times without any issue. What could have happened? How I can do to return to the previous setting? (i.e. standard and non forced EFI boot config) Thank you very much! -- Jorge Andr?s Brugger Departamento de Inform?tica DASU - Obra Social del Personal de la Universidad Nacional de la Patagonia Comodoro Rivadavia, Chubut, Argentina Tel?fono (0297) 446- int. 103 Correo electr?nico: jbrug...@dasu.com.ar Website: www.dasu.com.ar Quien hace, puede equivocarse. Quien nada hace, ya est? equivocado. (Daniel Kon) -- -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam End of ubuntu-server Digest, Vol 113, Issue 6 * -- next part -- An HTML attachment was scrubbed... URL: https://lists.ubuntu.com/archives/ubuntu-server/attachments/20150529/ccb59ca8/attachment-0001.html -- -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam End of ubuntu-server Digest, Vol 113, Issue 7 * -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Bug 1226855] Re: Cannot use open-iscsi inside LXC container
This is a blocking issue for users of iscsi-based storage HW on Openstack; is there any way of re-prioritizing this issue? -- 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 1439280] Re: Libvirt CPU affinity error
Matt, Tony, that's for the clarification. I'm still a bit confused as to when the cloud archive used by trusty (http://ubuntu- cloud.archive.canonical.com/ubuntu/dists/trusty-updates/) would be updated to point to this new libvirt cloud level. (sorry for being a newbie on this). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1439280 Title: Libvirt CPU affinity error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1439280/+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 1439280] Re: Libvirt CPU affinity error
When will this get fixed for Trusty? that's where it was originally reported. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1439280 Title: Libvirt CPU affinity error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1439280/+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 1439280] Re: Libvirt CPU affinity error
Using the patch above (that basically hacks out qemu specifically), nova boot work fine. Same qemu environment as I noted in my 4-23 post. Can we get this patch out for formal review by nova folks? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1439280 Title: Libvirt CPU affinity error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1439280/+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 1450881] Re: qemu-system-sparc MUTEX_HELD assert and libC lock errors
Yes, this is a known issue which I can reproduce using a Solaris installation. I still have a few outstanding bugs on my list to do before I can start looking into this one, but I will keep this bug up to date as/when I can start work on it - apologies for not being able to be more specific than this at the moment. -- 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/1450881 Title: qemu-system-sparc MUTEX_HELD assert and libC lock errors To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1450881/+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 1439280] Re: Libvirt CPU affinity error
I also see this is still an issue with http://ubuntu- cloud.archive.canonical.com/ubuntu trusty-updates/kilo main VERSION=14.04.1 LTS, Trusty Tahr # virsh version Compiled against library: libvirt 1.2.12 Using library: libvirt 1.2.12 Using API: QEMU 1.2.12 Running hypervisor: QEMU 2.2.0 nova-compute 1:2015.1~rc1-0ubuntu1~cloud0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1439280 Title: Libvirt CPU affinity error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1439280/+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 1355813] Re: Interface MTU management across MAAS/juju
Do we need to take into account any overhead being added by the protocol stack along the way? For example, if the underlying MAAS machine can be told to use 9000 byte MTUs and jumbo frames, then each layer up could adopt that, but might need to chop off some of that for protocol / tunnel / encapsulation overhead. I've seen cases where your internal interface needs to have, say 20 byte smaller MTUs than the host. Perhaps THAT's the bit that we should focus on specifying. So MAAS gets told just jumbo frames here and then everything else focuses on understanding and allowing for overhead, but maximising MTU subject to that overhead. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1355813 Title: Interface MTU management across MAAS/juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+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 1439280] Re: Libvirt CPU affinity error
Any ideas on how one could workaround this? How to disable affinity in nova, libvirt, or qemu config's? Some easy place in the code to hack? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1439280 Title: Libvirt CPU affinity error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1439280/+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 1434257] [NEW] MAAS should set dnssec-validation to no in /etc/bind/named.conf.options
Public bug reported: Several enterprise customers have had problems bootstrapping juju, getting errors like: Download failed. wait 15s\nAttempt 5 to download tools from https://streams.canonic al.com/juju/tools/releases/juju-1.21.3-trusty- amd64.tgz...\ncurl: (6) Could not resolve host: streams.canonica l.com\ntools from https://streams.canonical.com/juju/tools/releases/juju-1.21.3-trusty- amd64.tgz downloaded: H TTP 000; time 9.519s; size 0 bytes; speed 0.000 bytes/s sha256sum: /var/lib/juju/tools/1.21.3-trusty-amd64/too ls.tar.gz: No such file or directory\nERROR failed to bootstrap environment: subprocess encountered error code 1\n', 'status': 1}' [DEBUG ?? 03-19 13:21:00] ?? cloudinstall.utils ?? (utils.py, global_exchandler, 62)] Traceback (most recent call last): File /usr/share/openstack/cloudinstall/utils.py, line 77, in run super().run() File /usr/lib/python3.4/threading.py, line 868, in run self._target(*self._args, **self._kwargs) File /usr/share/openstack/cloudinstall/machinewait.py, line 127, in do_continue self.installer.do_install() File /usr/share/openstack/cloudinstall/multi_install.py, line 144, in do_install raise Exception(Problem with juju bootstrap.) Exception: Problem with juju bootstrap. solution turned out to be editing /etc/bind/named.conf.options and changing the line dnssec-validation auto; to dnssec-validation no; ** 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/1434257 Title: MAAS should set dnssec-validation to no in /etc/bind/named.conf.options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1434257/+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 1257186] Re: memory leakage messages (no talloc stackframe)
Confirmed in Ubuntu 14.04.02 LTS after recent upgrade from Ubuntu 12.04 LTS. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1257186 Title: memory leakage messages (no talloc stackframe) To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1257186/+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 1331214] Re: MAAS (amttool) cannot control AMT version 8
Verified on several VPro machines in the Dell lab, with different AMT firmware levels. ## PowerEdge T20 FW 9.0.21-build 1462works ## Laptop: E6400 FW 4.2.60-build 1060works ## Laptop: E6520 FW 7.1.4-build 1068works ## Laptop: E6430 FW 8.0.1-build 1399works ## Laptop: M4700FW 8.1.40-build 1416works -- 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/1331214 Title: MAAS (amttool) cannot control AMT version 8 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1331214/+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 1408369] Re: No apache2.4 config
This affects the Debian/Ubuntu mailman package. It does not affect the GNU Mailman project. ** Project changed: mailman = mailman (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mailman in Ubuntu. https://bugs.launchpad.net/bugs/1408369 Title: No apache2.4 config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1408369/+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 1278529] Re: Using S3, BackendException: No connection to backend
** Also affects: python-boto (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-boto in Ubuntu. https://bugs.launchpad.net/bugs/1278529 Title: Using S3, BackendException: No connection to backend To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1278529/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
I simply issued sudo reboot and this happened. So I assume then that I have a different issue from the original reporter? Should I open a separate bug and stop polluting this one? In the meantime I'll pull the requested config files. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
/etc/network/interfaces # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet manual auto juju-br0 iface juju-br0 inet dhcp bridge_ports eth0 /etc/network/interfaces.d is empty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
Same as comment #44 I'm running hardware MAAS and I get this on every deployment. If I let cloud-init error out I can get logged in and juju- br0 is up by that point but it doesn't come up until after cloud-init tries to do it's stuff. This makes the nodes I deploy unusable. I'm going to see if I can come up with a fix and I'll post here if I do. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
@dimitern Thanks for the swift reply. I'll do this now, for your information I'm currently running juju 1.21-beta3-trusty-amd64 from the juju-proposed ppa. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
Also I've found that if I edit /etc/init/networking.conf and change the starts on line to:- starts on stopped cloud-init-local Then everything works fine although I realise that this is a very poor solution. Best I could manage with my limited upstart knowledge. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
@dimitern Quite right, it is the devel branch I'm using. I was trying to find a new version which might already have a fix. I'm not very up on building software based on go. I'm getting the following when I try to run go install -v launchpad.net/juju-core/... go build launchpad.net/juju-core/... # launchpad.net/juju-core/testing/filetesting testing/filetesting/filetesting.go:194: cannot use checkers.Satisfies (type check.Checker) as type gocheck.Checker in function argument: check.Checker does not implement gocheck.Checker (wrong type for Info method) have Info() *check.CheckerInfo want Info() *gocheck.CheckerInfo # launchpad.net/juju-core/worker/uniter/charm worker/uniter/charm/bundles.go:52: cannot use err (type *error) as type error in function argument: *error is pointer to interface, not interface # launchpad.net/juju-core/utils/ssh utils/ssh/ssh_gocrypto.go:84: undefined: ssh.ClientConn make: *** [build] Error 2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
Here is the bootstrap log created when I run juju bootstrap --to db2.ed1.mavennetwork.co.uk --debug ~/maas-bootstrap.log ** Attachment added: maas-bootstrap.log https://bugs.launchpad.net/juju-core/+bug/1271144/+attachment/4282230/+files/maas-bootstrap.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
And these are the juju and cloud logs from the node which was bootstrapped. This node is working fine right now but once it is rebooted I will get the cloud-init problem. I'll reboot it now and then post the logs after the problematic boot. ** Attachment added: logs.zip https://bugs.launchpad.net/juju-core/+bug/1271144/+attachment/4282231/+files/logs.zip -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
And lastly the logs from the node after it is rebooted. On this boot it takes a very long time to come up as cloud-init waits for the network bridge to come up and then eventually errors out. ** Attachment added: logs2.zip https://bugs.launchpad.net/juju-core/+bug/1271144/+attachment/4282232/+files/logs2.zip -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1349941] Re: qemu-ppc segfault on simple hello world
So later on I had the ability to setup some more servers running with QEMU and found these packages were causing the same issues: lib32asan0 lib32atomic1 lib32gcc-4.8-dev lib32gcc1 lib32gcc1 lib32gomp1 lib32itm1 lib32quadmath0 libc6-x32 libx32atomic1 libx32gomp1 libx32itm1 libx32quadmath0 gcc-4.8-multilib libx32gcc-4.8-dev libx32gcc1 After removing those things started working again. -- 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/1349941 Title: qemu-ppc segfault on simple hello world To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1349941/+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 1399283] [NEW] openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.4: openvswitch kernel module failed to build
Public bug reported: don't know! happened during update ProblemType: Package DistroRelease: Ubuntu 12.04 Package: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.4 ProcVersionSignature: Ubuntu 3.13.0-40.69~precise1-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic i686 ApportVersion: 2.0.1-0ubuntu17.8 Architecture: i386 DKMSKernelVersion: 3.13.0-41-generic Date: Thu Dec 4 17:20:08 2014 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release i386 (20130213) MarkForUpload: True PackageArchitecture: all PackageVersion: 1.4.6-0ubuntu1.12.04.4 SourcePackage: openvswitch Title: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.4: openvswitch kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1399283 Title: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.4: openvswitch kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1399283/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
I'm seeing the same error on my hardware MAAS cluster with the latest maas stable and juju stable . Failing bridge on the bootstrap node is called juju-br0. I will post more info on Monday. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1321885] Re: IPMI detection and automatic setting fail in ubuntu 14.04 maas
Verified that the fix works on Dell PowerEdge R805 . maas 1.7.0+bzr3299-0ubuntu1~trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1321885 Title: IPMI detection and automatic setting fail in ubuntu 14.04 maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1321885/+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
Re: [Bug 1300507] Re: Rabbit password is reset on every upgrade which forces lockstep cluster restarts
We'll SRU 1.7 once it's super-solid! Mark -- 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/1300507 Title: Rabbit password is reset on every upgrade which forces lockstep cluster restarts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1300507/+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 1279000] Re: db migrate script to set charset=utf8 for all tables
** Changed in: openstack-chef Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to glance in Ubuntu. https://bugs.launchpad.net/bugs/1279000 Title: db migrate script to set charset=utf8 for all tables To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1279000/+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 1349941] Re: qemu-ppc segfault on simple hello world
I was having this same issue with qemu-ppc both the 2.0 version and a handbuilt 2.1.0 version running on 14.04. By installing these packages the error disappeared: acl libaio1 libasound2 libasound2-data libasyncns0 libbrlapi0.6 libcaca0 libflac8 libogg0 libpulse0 librados2 librbd1 libsdl1.2debian libseccomp2 libsndfile1 libspice-server1 libvorbis0a libvorbisenc2 libxen-4.4 libxenstore3.0 libyajl2 sharutils I'm not sure which one of the libvorbis/flac/ogg/asound packages fixed it, but they were key for the segfault to go away. I noticed based on the post from jrr that packages qemu-system-common, qemu-keymaps, qemu-system-ppc, qemu-user-static pulled in those other packages as deps and tried just installing the packages along with qemu- user. Just wan'ted to add that to this post. -- 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/1349941 Title: qemu-ppc segfault on simple hello world To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1349941/+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 1362052] [NEW] Provide Juju details on Horizon
Public bug reported: Please can we restore the ability to view a Juju stanza for a user of Ubuntu OpenStack? It should take the form: environment-name: type: openstack auth-url: http://192.168.9.97:5000/v2.0 region: region auth-mode: userpass use-floating-ip: true network: default-network-for-project tenant-name: project-name username: username password: Your Password Here authorized-keys: your ssh public key i.e. pre-fill network, tenant, and username, and invite the user to provide password. This should be provided on the Horizon Overview page (and is specific to the combination of tenant and user) until we have the Juju GUI integrated to Horizon. ** Affects: horizon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1362052 Title: Provide Juju details on Horizon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1362052/+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 1362053] [NEW] Provide Juju details on Horizon
Public bug reported: Please can we restore the ability to view a Juju stanza for a user of Ubuntu OpenStack? It should take the form: environment-name: type: openstack auth-url: http://192.168.9.97:5000/v2.0 region: region auth-mode: userpass use-floating-ip: true network: default-network-for-project tenant-name: project-name username: username password: Your Password Here authorized-keys: your ssh public key i.e. pre-fill network, tenant, and username, and invite the user to provide password. This should be provided on the Horizon Overview page (and is specific to the combination of tenant and user) until we have the Juju GUI integrated to Horizon. ** Affects: horizon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1362053 Title: Provide Juju details on Horizon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1362053/+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
Re: [Bug 1318366] Re: jujud on state server panic misses transaction in queue
Is there a way to run Go processes under a debugger and generate very high-resolution debugging output? I'm seeing this every second or third attempt to build a cloud. It might be that debugging overhead makes the problem vanish (yay Heisenberg) but it might give us a useful picture. Alternatively, I can provide ssh access to an environment which demonstrates the crash-and-restart behaviour. Mark -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1318366 Title: jujud on state server panic misses transaction in queue To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1318366/+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 1318366] Re: jujud on state server panic misses transaction in queue
Thanks Gustavo, this is 50% of the issues I see on cloud builds so am excited to get a build of the tools with this fix applied. Curtis, think we can spin a build through CI asap that would show up in the testing tools bucket on S3? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1318366 Title: jujud on state server panic misses transaction in queue To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1318366/+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 1318366] Re: jujud on state server panic misses transaction in queue
Yes, I saw the same restarting of Mongo, looks like every 10-15 seconds. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1318366 Title: jujud on state server panic misses transaction in queue To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1318366/+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 1318366] Re: jujud on state server panic misses transaction in queue
Attached is a dump of the Juju database in this case. ** Attachment added: dump.tgz https://bugs.launchpad.net/juju-core/+bug/1318366/+attachment/4164924/+files/dump.tgz -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1318366 Title: jujud on state server panic misses transaction in queue To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1318366/+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 1318366] Re: jujud on state server panic misses transaction in queue
After some experiments in compression options, here are all the Juju logs you could ever want :) http://people.canonical.com/~mark/juju-server-crash-logs.tar.xz 68M compressed, about 1.9G uncompressed. That's /var/log/juju/ from machine 0. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1318366 Title: jujud on state server panic misses transaction in queue To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1318366/+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 1318366] Re: jujud on state server panic misses transaction in queue
Here is a snippet of syslog showing two cycles of Mongo starts and restarts. This is happening constantly! Gustavo and I are wondering whether the numactl advice might be relevant. ** Attachment added: syslog.mongorestarts.log https://bugs.launchpad.net/juju-core/+bug/1318366/+attachment/4165278/+files/syslog.mongorestarts.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1318366 Title: jujud on state server panic misses transaction in queue To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1318366/+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 1318366] Re: jujud on state server panic misses transaction in queue
Digging in further, it appears that jujud is writing to /etc/init/juju- db.conf (the Upstart job for its database) every few seconds. I'll file a separate bug about this because it plausibly is the root cause of the mongo restarts we're seeing. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1318366 Title: jujud on state server panic misses transaction in queue To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1318366/+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 1318366] Re: jujud on state server panic misses transaction in queue
I've got this in a live environment from the cloud-installer too. How do I know where to point mongodump? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1318366 Title: jujud on state server panic misses transaction in queue To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1318366/+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 1078213] Re: logs are not logrotated
** Changed in: juju-core Importance: Medium = High ** Changed in: juju-core Milestone: None = 1.21-alpha1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078213 Title: logs are not logrotated To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1078213/+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 833994] Re: debian-installer does not support https when using with preseed files
Verified. Thanks! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler-enlist in Ubuntu. https://bugs.launchpad.net/bugs/833994 Title: debian-installer does not support https when using with preseed files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cobbler-enlist/+bug/833994/+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 1334958] Re: package haproxy 1.4.24-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
I have resolved this for this install; this box had an actual user account called `haproxy`. I renamed this account to something else and attempted the update again. It was successful that time. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1334958 Title: package haproxy 1.4.24-2 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/haproxy/+bug/1334958/+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 1334958] Re: package haproxy 1.4.24-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
# this config needs haproxy-1.1.28 or haproxy-1.2.1 global log 127.0.0.1 local0 log 127.0.0.1 local1 notice #log loghostlocal0 info maxconn 4096 #chroot /usr/share/haproxy user haproxy group haproxy daemon #debug #quiet stats socket /etc/haproxy/haproxysock level admin defaults log global modehttp option httplog option dontlognull retries 3 option redispatch maxconn 2000 contimeout 5000 clitimeout 5 srvtimeout 5 listen stats :1936 mode http stats enable stats hide-version stats realm Haproxy\ Statistics stats uri / stats auth redacted:redacted frontend myFlo-HTTP bind 192.0.2.55:80 default_backend myFlo-Servers-RR acl scheduler url_sub -i schedule #ACL for scheduler requests use_backend myFlo-Servers-SRC if scheduler frontend myFloLite-HTTP bind 192.168.100.8:80 default_backend myFloLite-Servers backend myFloLite-Servers mode http balance roundrobin option httpchk HEAD / server liteweb1:80 192.168.100.9 check port 80 inter 2000 server liteweb2:80 192.168.100.10 check port 80 inter 2000 backend myFlo-Servers-RR mode http balance roundrobin option httpchk HEAD /health_check.html HTTP/1.1\r\nHost:\ haproxy.test server myfloweb1:80 192.168.100.5 check port 80 inter 2000 server myfloweb2:80 192.168.100.14 check port 80 inter 2000 backend myFlo-Servers-SRC mode http balance source option httpchk HEAD /health_check.html HTTP/1.1\r\nHost:\ haproxy.test server myfloweb1:80 192.168.100.5 check port 80 inter 2000 server myfloweb2:80 192.168.100.14 check port 80 inter 2000 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1334958 Title: package haproxy 1.4.24-2 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/haproxy/+bug/1334958/+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 1334958] [NEW] package haproxy 1.4.24-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: Doing release upgrade from 12.04 to 14.04. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: haproxy 1.4.24-2 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Uname: Linux 3.2.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Fri Jun 27 15:36:08 2014 DuplicateSignature: package:haproxy:1.4.24-2:ErrorMessage: subprocess installed post-installation script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-10-02 (633 days ago) InstallationMedia: Ubuntu-Server 11.10 Oneiric Ocelot - Release amd64 (20111011) SourcePackage: haproxy Title: package haproxy 1.4.24-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2014-06-27 (0 days ago) modified.conffile..etc.default.haproxy: # Set ENABLED to 1 if you want the init script to start haproxy. ENABLED=1 # Add extra flags here. #EXTRAOPTS=-de -m 16 mtime.conffile..etc.default.haproxy: 2012-10-02T12:34:46.10 mtime.conffile..etc.haproxy.haproxy.cfg: 2014-06-27T14:46:05.313880 ** Affects: haproxy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty ** Attachment removed: modified.conffile..etc.haproxy.haproxy.cfg.txt https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1334958/+attachment/4140329/+files/modified.conffile..etc.haproxy.haproxy.cfg.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1334958 Title: package haproxy 1.4.24-2 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/haproxy/+bug/1334958/+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 1334958] Re: package haproxy 1.4.24-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
** Attachment added: modified.conffile..etc.haproxy.haproxy.cfg.txt https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1334958/+attachment/4140330/+files/modified.conffile..etc.haproxy.haproxy.cfg.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1334958 Title: package haproxy 1.4.24-2 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/haproxy/+bug/1334958/+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 1331276] [NEW] Starting lxc container from libvirt disconnects host network
Public bug reported: Starting an lxc container, defined via the XML below, results in the host's eth0 getting disconnected. I see DHCP messages beng generated and notice this process: root 5640 0.0 0.0 10232 2416 ?Ss 13:05 0:00 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0 is created - in addition to the usual network manager one. When I try to stop the container from virsh I get permission denied killing process 5640 (if I kill it myself, then I can stop the container). Starting and stopping the container via lxc-start|stop does not produceany unusual symptoms. === container definition === (root) $ cat lxc1.xml domain type='lxc' namelxc1/name memory327680/memory os typeexe/type init/sbin/init/init /os vcpu1/vcpu clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/lib/libvirt/libvirt_lxc/emulator filesystem type='mount' source dir='/var/lib/lxc/lxc1/rootfs'/ target dir='/'/ /filesystem interface type='network' source network='default'/ /interface console type='pty'/ /devices /domain ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libvirt-bin 1.2.2-0ubuntu13.1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Wed Jun 18 13:43:01 2014 InstallationDate: Installed on 2014-03-17 (92 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140314) ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.libvirtd.conf: [modified] modified.conffile..etc.libvirt.qemu.conf: [modified] modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified] mtime.conffile..etc.libvirt.libvirtd.conf: 2014-04-30T14:46:35.465205 mtime.conffile..etc.libvirt.qemu.conf: 2014-04-30T14:36:31.125221 mtime.conffile..etc.libvirt.qemu.networks.default.xml: 2014-06-18T12:59:02.877673 ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1331276 Title: Starting lxc container from libvirt disconnects host network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1331276/+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 1315188] Re: No init.d script included in icehouse ubuntu packaging
** Tags added: 14.04 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1315188 Title: No init.d script included in icehouse ubuntu packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1315188/+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 644825] Re: screen unpredictably crashes
*** This bug is a duplicate of bug 375625 *** https://bugs.launchpad.net/bugs/375625 screen not freezing up nor turning zombie, but i got the error described above. it happens reliably. i just manufactured Ubuntu 14.04. when exiting using ^A^D it does exactly what this bug describes. my screen is then lost completely (no longer exists), then i get logged out. the commands i'm running are: byobu-screen -d -m -L -a -t amp703 -S amp703 -T xterm-color byobu-screen -d -r amp703 i then type ^A^D it hangs for about 10 seconds. it then returns this: Error: Cannot find master process to attach to! my PS1 appears as would normally happen after a command completes, but then i am logged out immediately through no action of my own complete with the word logout as if the ^D part was interpreted by my shell. sure enough, if i just type ^A by itself within byobu, after 10s it drops to my shell with the master process error above. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to screen in Ubuntu. https://bugs.launchpad.net/bugs/644825 Title: screen unpredictably crashes To manage notifications about this bug go to: https://bugs.launchpad.net/byobu/+bug/644825/+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 644825] Re: screen unpredictably crashes
*** This bug is a duplicate of bug 375625 *** https://bugs.launchpad.net/bugs/375625 also, if i use screen directly, e.g. replace byobu-screen with just screen, it works as expected. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to screen in Ubuntu. https://bugs.launchpad.net/bugs/644825 Title: screen unpredictably crashes To manage notifications about this bug go to: https://bugs.launchpad.net/byobu/+bug/644825/+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 1304613] Re: nodes can't get out to the internet beyond the maas server by default
To add to this, as I also am experiencing this problem: My maas has 2 nics and 2 networks: Outbound eth1: talks to the world (or in thsi case my partner OEM's lab network Private eth0: talks only to maas-create nodes. Call it 10.0.0.0/24 . I've set up maas as DHCP DNS manager for eth0. I have *not* NATed eth0 as the Partner OEM does not like private NATs on its lab network. My /etc/resolv.conf, /etc/maas/dhcp.conf and /etc/dhcp/dhclient.conf are saying the right things. When I create node1 (using fastpath install) I can ping other things on the 10.0.0.0/24 network (by name or address) but cannot ping google.com (even though the name resolves correctly). If I turn on NAT this works. This makes post-node-startup installation and configuration very problematic. -- 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/1304613 Title: nodes can't get out to the internet beyond the maas server by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1304613/+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 1304613] Re: nodes can't get out to the internet beyond the maas server by default
Actually, my last comment encompasses a different problem (that of isolation), so ignore it. But do count this as a vote to some kind of NAT on/off tooling in MAAS. -- 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/1304613 Title: nodes can't get out to the internet beyond the maas server by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1304613/+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
Re: [Bug 1305839] Re: FFe: Support for Third Party Driver Installation
To Robbie's point - yes, it makes no sense to make the install break mysteriously when we can get it to work, any more so on a server or a phone. It does make sense to flag in the UI when we have used drivers outside of the normal Ubuntu kernel set. We're not installing proprietary applications, I don't see a significant moral issue. Mark -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1305839] Re: FFe: Support for Third Party Driver Installation
The key difference in my mind is recoverability. In the server case, the install is by nature largely automated, and often will fail altogether if you don't for example have the ability to configure your hard drives. Perhaps an analogy for the desktop would be to ask the question - what if a popular, common device that was required for system installation in a large percentage of cases required a non-free driver to be on the disk and used by default. We would certainly opt to make that device installable; consider our approach on phones, where we accept binary blobs and invest a lot to deliver a free userspace. I don't think we're crossing a significant new line here. There are many pieces of no-charge proprietary software we COULD be installing to make the product better, but we don't, given our values. In this case, I see no moral high ground in crippling the install unless someone answered an ideological question. We often forget how hard it is for new users to come up to speed - we know all the permutations and combinations and tradeoffs, most users do not. Consider also how comfortable we are enabling people to run Ubuntu on proprietary clouds - where they will never see the code beneath the code, as it were. Having said all this, I didn't clarify earlier that this mechanism should only be used for hardware which has no free driver. We should always silently select the free driver if such a driver exists, and if people want to go hunting for a proprietary one, ensure they can find them in a standard, supportable, upgradeable fashion, but not use it by default. -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1305839] Re: FFe: Support for Third Party Driver Installation
Thanks all for the comments and discussion. Responding to some key points: * building confidence in code changes both for this FFE and subsequent SRUs is important, the archive and RM teams have a mandate to seek comfort on that front before ack'ing an upload under either circumstances * in other words - thank you for calling out the late change :) * I have asked and the MAAS team have assured that all SRU changes will come with appropriate test suites * I would expect to see a test suite for this change and would expect that test suite to have been run on the appropriate hardware. Separately, we'll arrange to have MAAS CI and testing integrated to the OIL lab, which has a rapidly growing range of hardware. * installing the necessary drivers is the norm in the linux environment; warning the user about the consequences of this is the norm in the Ubuntu environment. * I'd ask that we accept this FFE once tests are in place, or if needed, with a commitment to tests as a zero-day SRU * I'd ask that the MAAS team commit to flagging the installation of such drivers in the MAAS node UI, possibly also with a flag on the node listing * all of this assumes the existence of a setting which enables a system administrator to tell MAAS not to do this by default on any given machine without explicit approval As general guidance, this is an area that will evolve fast in the coming months and years, so I've asked the MAAS team to keep developing on 14.04 LTS as their primary platform, introducing no dependencies that are not in 14.04, so we can SRU. If we need to move to universe to make that more comfortable for the release team, let's do that. We got stuck in 12.04 with old versions of key tools that should have been moved - stuck because of bad thinking on the deps front, and perceived dogma on the RM front. We can do better this time by requiring rigorous CI and testing on SRUs, and being sensible about deps. That goes for maas, juju and related tools, all of which need to be current and useful in the coming two years. -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1305839] Re: FFe: Support for Third Party Driver Installation
Also, thank you Adam for pointing out that we need to do the same sort of ubiquity- and jockey-like calling out of the issues associated with binary blobs on servers that we do on the PC. I'll get the MAAS folks to make that very clear on the node page as a way of socialising the benefits of open drivers. -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1302741] Re: dpkg-reconfigure maas-region-controller fails
I have not seen any reportable breakage; admittedly I have not fully stressed maas nor used all of its functions. -- 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/1302741 Title: dpkg-reconfigure maas-region-controller fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1302741/+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
Re: [Bug 1287147] Re: [FFe] juju-core 1.18
We decided that we should land everything but HA and VLAN work this week in a stable release to minimize the risk that either of those changes could have on overall stability in the release. However, HA and VLAN work is underway, and much of it has already landed, and the first HA support is expected to land in a development release in the next several days. On Mon, Apr 7, 2014 at 12:44 PM, Dave Walker davewal...@ubuntu.com wrote: There seems to be some confusion or change in plans. The original description states 1.18 consists of: 1) HA of Juju state nodes 2) Full support for ppc64el and arm64 But the revised timeline says Without HA. Is HA no longer a release target? Other than supporting ppc64el and arm64, are there any other featureful changes? Thanks. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1287147 Title: [FFe] juju-core 1.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1287147/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1287147 Title: [FFe] juju-core 1.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1287147/+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 1208430] Re: mongodb runs as root user
** Changed in: juju-core Importance: High = Critical -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1208430 Title: mongodb runs as root user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1208430/+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 1208430] Re: mongodb runs as root user
Reducing the security implications of running MongoDB is an important thing for us to do. It's not quite critical, because nobody is asking for it directly now, and the risk is still somewhat limited. But there is a risk, and I think the general policy of treating even security -- even relatively lower risk stuff -- as important is a good habit of mind for us. We are going to be at the center of a lot of important developments. On the other hand once you can control the MongoDB server, your opportunities for privilege escalation on hosts in that environment are probably greater in other directions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1208430 Title: mongodb runs as root user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1208430/+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 1284718] Re: interface-attach to external network a) works and b) results in undeletable instances
** No longer affects: neutron -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1284718 Title: interface-attach to external network a) works and b) results in undeletable instances To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1284718/+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 1300026] Re: Enlistment/commissioning boot no longer works
ignore last comment. A fresh import works.until you reboot. Even if you changed nothing else in the configuration of the server or maas, enlistment will no longer work until you do another maas-import-pxe-files at which time things will work again. ** Tags added: blocks-hwcert-server ** Changed in: maas Status: Invalid = Confirmed -- 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/1300026 Title: Enlistment/commissioning boot no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1300026/+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 1246236] Re: pxe boot from maas fails due to time out
I'm seeing this error in the Garage MAAS today. As it happens, also have two interfaces on the network on that machine. Will try reducing to one and reboot. -- 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/1246236 Title: pxe boot from maas fails due to time out To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1246236/+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 1300026] Re: Enlistment/commissioning boot no longer works
A fresh import works.until you reboot. Even if you changed nothing else in the configuration of the server or maas, enlistment will no longer work until you reboot. -- 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/1300026 Title: Enlistment/commissioning boot no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1300026/+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 1246236] Re: pxe boot from maas fails due to time out
Was not able to reproduce after a reboot. -- 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/1246236 Title: pxe boot from maas fails due to time out To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1246236/+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 1208430] Re: mongodb runs as root user
** Changed in: juju-core Milestone: None = 1.18.0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1208430 Title: mongodb runs as root user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1208430/+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 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang
@jamie However, I don't feel the download size is itself a blocker. We can perform uploads for everything at first, figure out how to be smarter/more selective later and along the way work with upstream on dynamic linking if that makes sense. I think that is particularly true in *this* case where we are talking just about Juju Core. Of course as a standard policy, for a future where there may be many go applications in the distro, I think we really do want either golang-go or gcc-go with dynamic linking to be moved into a supportable state. And I also agree that we should not confuse the current case (1 app) with the future. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+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
