Sure thing:
$ sudo systemctl status ssh
[sudo] password for andrewta:
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset:
enabled)
Active: failed (Result: start-limit) since Wed 2016-02-24 14:44:04 CST; 20s
ago
Process:
After boot starting ssh has never fails to start and correctly runs.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1549473
Title:
ssh will not start at boot: systemctl status ssh
Public bug reported:
Using apt I have reinstalled and purged both ssh and openssh-server.
apt-get remove --purge ssh openssh-server
reinstalled
updated
and on boot the ctl status is failed 255
After much forum research and attempts to default solutions, the final word was
that reinstall
I think this fix should be back ported to trusty so that we can
eventually install MAAS in a LXD environment.
--
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/1518440
Title:
tgt fails
** Changed in: juju-core (Ubuntu)
Status: Confirmed => New
--
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/1545913
Title:
[FFe] juju-core 2.0
To manage notifications about
Excluding all compression options was not an acceptable solution for me.
What has worked since I initially found this problem back in August was
to install rsync from the utopic repository where the bug was fixed.
That same version (3.1.1-3) is still available in vivid and wily
unchanged as far
Looks like I was premature in my last reply.
ami-bfb5ead5 just came up. I'll have to double check this bug report with one
of our customers.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
OK it looks like the bug was fixed for the hvm:ebs-ssd (General Purpose
SSD) AMI builds and not hvm:ebs (standard/magnetic EBS).
For example, in ubuntu-wily-15.10-amd64-server-20160105.1 for us-east-1:
* ami-bfb5ead5 ( hvm:ebs ) - FAILS
* ami-15b7e87f ( hvm:ebs-ssd ) - WORKS
for enhanced
Do we have any updates for fixing these AMIs for instance types that
have enhanced networking enabled?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1510345
Title:
[SRU] Cloud
Public bug reported:
Downgrade haproxy 1.6 to 1.5.15 reports that it failed on reboot of
machine. But in fact, it worked.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: haproxy 1.5.15-1ppa1~wily
ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
Uname: Linux
Another work around is to disable "performance_schema" This was not
enabled by default in the 5.5 packages AFAIK. Disabling it allows MySql
5.6 to install/start on a 512mb server for me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
*** This bug is a duplicate of bug 1311387 ***
https://bugs.launchpad.net/bugs/1311387
** This bug has been marked a duplicate of bug 1311387
postinst fails when installing on a low memory system
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Interestingly, using 5.6.27-0ubuntu0.14.04.1 on 14.04 on a 512mb server
consistently fails to install while 5.6.27-0ubuntu1 with 15.10 doesn't.
I don't see any obvious configuration difference scanning the diff
though.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
In january the trove install packages were changed to use systemd in this
commit:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/openstack-trove/wily/revision/21
This caused all services to startup using the same configuration file.
trove16464 1 0 Nov13
The init.d script was a broken symlink to nut-client, so I just copied
the systemd unit from an earlier package, and it works fine now.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Public bug reported:
The systemd unit for the upsmon has disapperared from nut-client package
since Ubuntu trusty:
http://packages.ubuntu.com/trusty/amd64/nut-client/filelist
(2.7.1-1ubuntu1)
vs
http://packages.ubuntu.com/vivid/amd64/nut-client/filelist
(2.7.1-1ubuntu4)
** Affects: nut
Hi Colin, I believe you now have access to the necessary hardware, but
please let me know if this is still an issue. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214
Great! Many thanks...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214
Title:
HP ProLiant m400 Server crashes with unhandled level 3 translation
fault
To manage
Sorry, I changed the status of this bug by accident.
But should it still be 'incomplete'?
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
** Changed in: qemu (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1494602
Title:
qemu-system-x86 nested virtualisation is broken on AMD
Hello, here is the extra information you have asked for.
Instance 37aa aka kvm id 677 is my currently running test instance, but I have
given you
the full ps output you have asked for. 18429 is the PID for this instance.
instance-37aa
12396aff-3f84-4ceb-9791-d20cf656fb35
Public bug reported:
I am reporting this bug against qemu-system-x86=1:2.2+dfsg-5expubuntu9.3~cloud0
in the Ubuntu cloud archive.
# lsb_release -rd
Description:Ubuntu 14.04.3
I just found this report myself. I've been experiencing the problem for
a while but had to rule out other causes. This is a pretty serious bug
in an LTS release.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
This is no longer happening on stock kernels.
** Changed in: lxc (Ubuntu)
Status: New = Invalid
--
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/1446658
Title:
lxc-test-apparmor
** Also affects: irqbalance (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214
Title:
HP ProLiant m400 Server crashes
Following Ming's identification of an irqbalance patch that fixes this
issue, I'm marking the Affected status on linux (Ubuntu) as being
invalid.
** Changed in: linux (Ubuntu Trusty)
Status: New = Invalid
** Changed in: linux (Ubuntu Utopic)
Status: New = Invalid
** Changed in:
One more thing that I think might be important. /repo was a symlink
itself to a mounted VMWare Fusion OS X host shared folder.
/repo - /mnt/hgfs/andrew/projects/PROJNAME
and I am now wondering if that shared folder disconnected during the
upgrade, thus the php.ini links were severed. I apologize
BTW, I can’t login. I use a password manager so I know the password and
username are correct. After clicking login I get a page that says “Bad
Request”. That seems like an error in the backend rather than an
authentication error. Because of this, I can’t change the status of the
report.
Andrew
keep them. On the second one it
displayed that error.
I can’t be 100% sure but I believe the system is fully operational and
upgraded properly. Thankfully for my sake, this was a test VM
specifically created to try out the upgrade from 14.04 = 14.10.
Andrew
On Jun 23, 2015, at 7:06 AM, Robie Basak
** Attachment added: apt.log
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1467552/+attachment/4418603/+files/apt.log
** Description changed:
- Since .I am only allowed to upload a single file, but the upgrade asked
- me to send two files: apt.log and main.log, I am pasting apt.log at
Public bug reported:
OUTPUT at command prompt just before error. It was working on php5 and I just
told it to keep my php.ini file. After saying keep my php.ini, the below was
outputted.
ucfr: Attempt from package libapache2-mod-php5 to take
/repo/config/etc/php.ini away from package
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.launchpad.net/bugs/1446658/+attachment/4380593/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1446658/+attachment/4380592/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: lxc.default.txt
https://bugs.launchpad.net/bugs/1446658/+attachment/4380595/+files/lxc.default.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: lxc-net.default.txt
https://bugs.launchpad.net/bugs/1446658/+attachment/4380594/+files/lxc-net.default.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Public bug reported:
Running lxc-test-apparmor fails on aarch64 (arm64) systems.
The following files which are listed in files_to_deny[] in
src/tests/aa.c:
/sys/kernel/uevent_helper
/proc/sys/kernel/sysrq
are not denied, but should be.
Perhaps I should be changing the apparmor profile
I was bitten by this too. In my case, it's because I installed postfix
within a chroot that I was using schroot to enter, but postfix wasn't
installed in the real root. Each time I'd enter the chroot, /etc/group
would be copied from the real root into the chroot, losing the
'postdrop' group
This appears to be fixed, at least in 1:6.6p1-2ubuntu2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1236299
Title:
ssh-agent env variables not set when not using Bourne shell
To
I'm not clear on what the issue with mailman is but if removing the
LimitUIDRange option from your Apache config solves it then it's
probably expected behaviour when calling a setuid root executable
(Exim?).
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Systemd support is currently under development, primarily to support
CentOS: http://reviews.vapour.ws/r/671/
--
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/1409639
Title:
juju
(I should have added: but will support Ubuntu, with a couple of minor
adjustments)
--
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/1409639
Title:
juju needs to support systemd for
I'm using netatalk as well, and this bug was causing
/run/samba/gencache_notrans.tdb to grow to several hundred MB until /run
was out of space. According to tdbtool the database itself was basically
empty, but it was still taking up disk even after a repack. Disabling
the module with
Mongodb ARM64 support explanation from Michael Hudson-Doyle.
1) MongoDB uses JS for two things:
i) The 'mongo' shell that people use for interactive use and admin
tasks etc. This is perhaps not used so much in production, but
it's something that most people use when first
** Tags added: hs-arm64-maas-juju
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1377308
Title:
booting cloud image without initramfs broken
To manage notifications about this
I'm pretty sure this is fixed in 1.21-alpha1. Can someone with an ARM
machine please test it?
--
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/1316579
Title:
--upload-tools doesn't
Many thanks to Michael, Raghu and Robie for helping to clarify. Marking
this bug as invalid...
** Changed in: mongodb (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
Michael, many thanks for your comment.
Could you confirm that we should be using juju-mongodb
(https://launchpad.net/ubuntu/+source/juju-mongodb) on ARM64 for the time
being? ISTR that juju-mongodb has omitted the libv8 engine, and associated
functionality.
Thanks again, Andy.
--
You received
Thanks Robie, so for ARM64 platforms we should be using MongoDb, but just
avoiding the shell and any scripting functions (in order to avoid invoking
libv8). Is that correct?
Thanks again, Andy.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Tags added: hs-moonshot
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1377308
Title:
booting cloud image without initramfs broken
To manage notifications about this bug go
** Tags removed: hs-moonshot
** Tags added: hs-moonshot-maas-juju
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1377308
Title:
booting cloud image without initramfs broken
To
** Changed in: mailman (Ubuntu)
Status: Confirmed = Invalid
--
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/1349433
Title:
AppArmor breaks seccomp @ Apache mpm-itk
To manage
@danieru: what network interfaces show up? is the primary network
interface called something other than eth0? If so, you'd need to set
the network-bridge attribute in environments.yaml.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
Trying to do in-place upgrade from 12.04.5 to 14.04.1 with some apache2,
ruby, puppet and foreman packages installed. Looks like the problem
packages were apache2 and apache2-mpm-worker.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: apache2 2.4.7-1ubuntu4.1
** Attachment added: /var/log/dist-upgrade/main.log
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1359227/+attachment/4182505/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
*** This bug is a duplicate of bug 1287222 ***
https://bugs.launchpad.net/bugs/1287222
The bug filed against the Cisco ssh client is CSCuo76464 - its fix
resolves the issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh
Note that the 'Operation not permitted' error in the original
demonstration is desired behaviour- when this does /not/ happen the
seccomp filter is not working as intended. It's not clear to me what
problem you're see'ing but it /could/ be an affect of the seccomp filter
in mpm-itk (governed by
** No longer affects: juju-core/1.20
--
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
Sorry, I was thinking that lp:1337091 was released already. We will look
at getting it into 1.20.2.
If you set the kernel parameter via MAAS [0] prior to first boot, then I
would concur that it's probably not going to help. If, however, you
modified GRUB after it came up and rebooted, I think
** Also affects: juju-core/1.20
Importance: Undecided
Status: New
** Changed in: juju-core/1.20
Milestone: None = 1.20.2
** Changed in: juju-core/1.20
Importance: Undecided = High
** Changed in: juju-core/1.20
Status: New = Triaged
--
You received this bug notification
Rick,
Sorry for the frustration. It is certainly not unreasonable to expect
14.04 to be working.
br0 is only brought up on first boot, so rebooting would not have
triggered that part of cloud-config again.
I believe we are looking at back-porting Juju 1.20.2 (the next stable
release) into
Public bug reported:
The recent security update to php5 broke common configurations for
php5-fpm.
From IRC:
asomething mdeslaur, did you see jdub's comment in LP: #1307027?
ubottu Launchpad bug 1307027 in php5 (Ubuntu) php5-fpm: Possible privilege
escalation due to insecure default
** Changed in: juju-core
Status: In Progress = Fix Committed
** Changed in: juju-core
Milestone: next-stable = 1.19.4
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Changed in: juju-core
Status: Triaged = In Progress
** Changed in: juju-core
Assignee: (unassigned) = Andrew Wilkins (axwalk)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https
So, my nodes don't have eth0, but p1p1, if that makes any difference.
This is most likely the key; the MAAS provider code assumes it's dealing
with eth0. Thanks for the information.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
script, remove lintian-overrides
[ Andrew Starr-Bochicchio ]
* Cherry-pick patches from Ubuntu and upstream for Django
1.5 and 1.6 compatability:
- 04-json-compat-django1.5.patch: Use json instead of simplejson for
Django 1.5. (LP: #1184219)
- 05-compat-django1.5
Mmm, not sure how this got tagged for lxc package and I don't know how
to fix that. :-/
** Package changed: lxc (Ubuntu) = ubuntu
--
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/1328683
Public bug reported:
This is a fresh install of 14.04 LTS Server on VMware ESXi 5.1 or 5.5, I
get the same symptom on both servers.
I installed with OpenSSH and LAMP packages. After the install, the server
reboots and comes up OK. I login, immediately type sudo reboot now and it
begins
I've filed the bug CSCuo76464 to get this fixed on the cisco side.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1287222
Title:
openssh-client 6.5 regression bug with certain
I am having a similar problem on Ubuntu-14.04. However, at one point, I
was able to connect to my vpn with 14.04.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/997927
Title:
NM
Public bug reported:
Please sync python-django 1.6.5-1 (main) from Debian sid (main)
Explanation of the Ubuntu delta and why it can be dropped:
All Ubuntu patches are backports from upstream. This release contains
them all.
Changelog entries since current utopic version 1.6.1-2ubuntu0.3:
Just chiming in, the patch worked for me as well on Ubuntu 12.04.4 with
Logwatch 7.4.0 and Dovecot 2.0.19. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logwatch in Ubuntu.
https://bugs.launchpad.net/bugs/1058760
Title:
** Changed in: juju-core
Assignee: (unassigned) = Andrew Wilkins (axwalk)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https
** Branch linked: lp:~axwalk/juju-core/lp1260171-stopinstances-ids
--
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/1316272
Title:
juju destroy-environment =256 nodes fails
To
Sadly I do not have a 256+ node MAAS to test with. I'm going to mark
this as Fix Committed; please let me know if you still have issues.
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team,
We already do POST when stopping instances. The problem is likely that
we first have to map instance IDs to instances so we can stop them (this
is dumb and needs to change; see lp:1260171).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Public bug reported:
I can not connect from a freshly installed 14.04 box to a Cisco
CSR1000V. 12.04 connects with no issues.
Debugging this, the symptoms are identical to this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1026430
see the logs below (hostnames, addresses, and
** Changed in: juju-core
Status: In Progress = Fix Committed
--
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/1313785
Title:
Can't SSH with juju ssh command to EC2 instance.
To
** Changed in: juju-core
Status: Triaged = In Progress
** Changed in: juju-core
Assignee: (unassigned) = Andrew Wilkins (axwalk)
--
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
Thanks, I hadn't noticed the version difference. I can also reproduce
the issue with a 1.18.2 server.
--
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/1313785
Title:
Can't SSH with juju
** Branch linked: lp:~axwalk/juju-core/lp1313785-ssh-useproxy
--
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/1313785
Title:
Can't SSH with juju ssh command to EC2 instance.
To manage
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: qemu-kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1316720
Title:
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: apt-cache show qemu-kvm
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1316812/+attachment/4106762/+files/apt-cache%20show%20qemu-kvm
--
You received this bug notification because
** Description changed:
Iso 172, 180, 183
Ubuntu fails to deploy because qemu-kvm fails to install because its
init service wont start.
init fails due to
- cat /etc/init/qemu-kvm.conf
+ cat /etc/init/qemu-kvm.conf
...
pre-start script
- # Silently exit if the package
** Description changed:
Iso 172, 180, 183
- Ubuntu fails to deploy because qemu-kvm fails to install because its
- init service wont start.
+ Ubuntu (guest) 12.04.04 qemu-kvm fails to install because upstart wont
+ pass.
+
+ root@node-2:~# apt-get install -f
+ Reading package lists... Done
** Changed in: fuel
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1316812
Title:
ubuntu qemu-kvm package attempts to start a service and fails
I am not able to reproduce this.
juju ssh will now ssh to machine 0's public address directly, and then
proxy through that to machine 0's internal address. This is to support
environments where machines do not have unique public addresses (i.e.
with load balancing).
Can you please ssh to the
On Mon, Apr 28, 2014 at 4:57 AM, James Page james.p...@ubuntu.com wrote:
How much memory does you installation have? The default innodb buffer
pool size increased in 5.6 and I'm wondering if this is the issue you
are hitting?
That sounds like it might be it. This is on a 512MB VPS. I'll try to
A CLI command is an interesting stopgap, but on a heavily utilized
OpenStack installation with automated tools operating against OpenStack,
this has a high manual maintenance cost. Surely there is some better
default that lies in the middle ground between keeping tokens for ever
and ever and
That seems reasonable. I would suggest adding that as a step to the
OpenStack setup documentation. No one has infinite database space,
eventually all used OpenStack installations will suffer unless this is
done. Regardless of what component (or person) has to complete the task,
they'll need to be
** Also affects: heat (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to heat in Ubuntu.
https://bugs.launchpad.net/bugs/1296912
Title:
python-qpid-python package does not exist
To
** No longer affects: neutron
** Summary changed:
- python-qpid-python package does not exist
+ python-qpid-python package does not exist in precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to heat in Ubuntu.
** Changed in: juju-core
Assignee: Roger Peppe (rogpeppe) = Andrew Wilkins (axwalk)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https
** Changed in: juju-core
Status: Triaged = In Progress
** Changed in: juju-core
Assignee: (unassigned) = Andrew Wilkins (axwalk)
** Changed in: juju-core
Milestone: 1.18.0 = 1.17.6
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Branch linked: lp:~axwalk/juju-core/lp1271144-maas-bridge-utils
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Branch linked: lp:~axwalk/juju-core/lp1271144-maas-bridge-utils
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
This only affects 1.17.2 and 1.17.3 interaction, so we can just close
it.
There was a change introduced in 1.17.2 to add an image-stream config
attribute, which was previously specific to the Azure provider. The
config default (omit) was invalid, though, causing the bug lp:1277636.
We fixed this
** Bug watch added: Samba Bugzilla #8449
https://bugzilla.samba.org/show_bug.cgi?id=8449
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=8449
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server
Great! Many thanks Chuck :-)
--
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/1264815
Title:
nova-compute can't be setting up during install on trusty
To manage notifications about
Does this patch need to be cherrypicked from the upstream project into
the Ubuntu archive?
--
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/1265443
Title:
nona on trusty: valueError
The workaround that's been identified is to download and install python-
webob_1.2.3.
--
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/1264815
Title:
nova-compute can't be setting up
1 - 100 of 411 matches
Mail list logo
