Steps to reproduce:
1) install squid3 (wily)
2) systemd is able to start/stop squid3
3) break the config (add a syntax error that prevents squid3 from starting)
4) neither manual nor systemd startup of squid3 work (expected)
5) fix the config
6) manual startup works again (expected), systemctl sta
I just upgraded from 14.04 all the way to 15.10.
2015-10-28 10:17:17 upgrade maas-common:all 1.7.6+bzr3376-0ubuntu2~14.04.1
1.7.6+bzr3376-0ubuntu2~15.04.1
2015-10-28 10:54:59 upgrade maas-common:all 1.7.6+bzr3376-0ubuntu2~15.04.1
1.8.3+bzr4053-0ubuntu1
MAAS wouldn't start up, with this in syslo
Sagar, please use ifconfig and its manpage. I did nothing magic, just
manual interface configuration instead of DHCP.
It is really just about giving the interface an IP/subnet, and
eventually a default gateway with "route add" ...
--
You received this bug notification because you are a member of
Public bug reported:
I have a MAAS running in a VM, LAN is bridged.
I created another VM using virt-manager, with CPU 1, RAM 1G, disk 8G and
PXE booted it from MAAS.
I have configured the power type as libvirt and added necessary
credentials to MAAS so it can remote control libvirtd via ssh.
En
Public bug reported:
I have a MAAS server that uses a box running dnsmasq as a DNS forwarder.
With MAAS enabling dnssec by default, I get errors like these and DNS
resolution from the MAAS provisioned machines doesn't work beyond what
MAAS manages.
Aug 21 01:29:17 maas-region-hkg named[1147]: er
Public bug reported:
I have a VM host running Ubuntu 14.04.2 LTS, and several VMs running
15.04.
On the host, I found these:
Aug 13 07:47:04 hkgdcsrv01 kernel: [1804566.706973] kvm [21590]: vcpu1
unhandled rdmsr: 0x606
Aug 13 07:47:05 hkgdcsrv01 kernel: [1804567.776637] kvm [21590]: vcpu0
unha
Public bug reported:
What I did:
* Set up a box as VM host for manually provisioned VMs (using ssh and
virt-manager)
* Created a new VM using the 15.04 server ISO (amd64)
* Select "multiple host install using MAAS"
* made this VM a standalone MAAS
After installation finishes the VM reboots, and
Can we expect a fix for this anytime soon?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1442112
Title:
booting ppc64el with hwe-u kernel hangs in initrd
To manage n
Public bug reported:
Hardware HP DL380Gen9, 128GB RAM, 2 CPUs
Windows guest causing lots of I/O pressure caused qemu to crash.
$ lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04
ii qemu-system-x86 2.0.0+dfsg-2ubuntu1.10
amd64
Result of running your foocheck script:
$ ./foocheck
found: eth0
br-int: /sys/class/net/br-int 6a:8f:8a:ce:3a:49
br-tun: /sys/class/net/br-tun 6e:8b:75:17:c9:43
eth0: /sys/class/net/eth0 6c:ae:8b:6a:d8:08
eth1: /sys/class/net/eth1 6c:ae:8b:6a:d8:09
eth2: /sys/class/net/eth2 6c:ae:8b:6a:d8:0a
eth3
This happened again today.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/924105
Title:
integer out of range errors for fact_values
To manage notifications about this bug go to:
htt
*** This bug is a duplicate of bug 1329383 ***
https://bugs.launchpad.net/bugs/1329383
** This bug has been marked a duplicate of bug 1329383
celery from 12.04+cloudarchive is incompatible with python-amqp from
cloud-tools-next
--
You received this bug notification because you are a memb
Public bug reported:
Our environment requires stable IP addresses for LXC containers deployed
to MAAS managed physical machines via juju.
We are smooshing OpenStack infrastructure components (glance, cinder,
rabbitmq-server, swift-proxy, ...) to 3 units each on 3 physical hosts
for HA.
HA enable
We also see this behaviour on LXC containers deployed to MAASified
machines where MAAS does *not* manage DHCP/DNS.
We are trying to smoosh OpenStack infra into LXC units on MAASified
machines for HA.
It is most visible with rabbitmq-server, which bails out on NXdomain for
the unit.
It's also rep
Done: https://bugs.launchpad.net/ubuntu/+source/libiscsi/+bug/1271653
--
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/1271573
Title:
please add iSCSI support back to qemu packages
To m
Public bug reported:
Symptom:
qemu-system-x86_64 -drive
file=iscsi://192.168.4.21:3260/iqn.2000-01.com.synology:nas-scl.ltsp-root/2,if=none,id=drive-virtio-disk0,format=raw
qemu-system-x86_64: -drive
file=iscsi://192.168.4.21:3260/iqn.2000-01.com.synology:nas-scl.ltsp-root/2,if=none,id=drive-vi
Public bug reported:
I try to get help from charm-tools:
alex@thinkpad:~$ charm help
/usr/share/charm-tools/scripts/help: 11: /usr/share/charm-tools/scripts/help:
/usr/share/charm-tools/scripts/: Permission denied
Using latest daily of raring.
ii charm-tools
The problem still exists in the latest juju version from ppa. Any
updates?
ii juju0.6.0.1+bzr618-0juju all
next generation service orchestration system
ii lxc 0.8.0~rc1-4ubuntu39. amd64
Linux Containers use
Public bug reported:
What I try to do:
I set up a local lxc environment on my laptop. Here's my
environments.yaml:
default: lxc
juju-origin: ppa
environments:
lxc:
type: local
control-bucket: juju-
admin-secret:
data-dir: /srv/lxctmp
default-series: precise
I purged juju
19 matches
Mail list logo
