@niedbalski FYI, tempest results from wily-liberty-proposed and trusty-
liberty staging are consistent with wily-liberty (distro) and trusty-
liberty (uca updates). ie. No new failures. Now that it has been
promoted to trusty-liberty-proposed, we will need to re-test there.
There is typically
FYI, following additional regression tests, today we promoted qemu 2.2
+dfsg-5expubuntu9.7~cloud2 from kilo-proposed to kilo-updates in the
Ubuntu Cloud Archive.
** Changed in: cloud-archive/kilo
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
FYI, following additional regression tests, today we promoted neutron
2014.1.5-0ubuntu4~cloud0 from proposed to icehouse-updates in the Ubuntu
Cloud Archive.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
n)
Status: New => In Progress
** Changed in: neutron-openvswitch (Juju Charms Collection)
Milestone: None => 16.01
** Changed in: neutron-openvswitch (Juju Charms Collection)
Assignee: (unassigned) => Ryan Beisner (1chb1n)
--
You received this bug notification because you
)
Importance: Undecided
Status: New
** Changed in: neutron-openvswitch (Ubuntu)
Assignee: (unassigned) => Ryan Beisner (1chb1n)
** Changed in: heat (Ubuntu)
Assignee: (unassigned) => Ryan Beisner (1chb1n)
** Changed in: glance (Ubuntu)
Assignee: (unassigned) => Rya
With Vivid, openhpid fails to install and start @ 2.14.1-1.3ubuntu2.
This is blocking hacluster from installing on Vivid.
I believe this is due to this directive in the /etc/openhpi/openhpi.conf file:
###
## OpenHPI will not be useful unless it is configured for your system. Once
## you have
Checked again with 2.14.1-1.3ubuntu2.1 from vivid-proposed. While I've
not done any functional testing against openhpid itself, apt and dpkg
now exit cleanly, whereas they did not @ ubuntu2.
ubuntu@juju-beis1-machine-3:/etc/apt/preferences.d$ apt-cache policy openhpid
** 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 the bug report.
https://bugs.launchpad.net/bugs/1488453
Title:
Package postinst always fail on first install when
Here is a non-OpenStack generic reproducer to re-confirm.
Generic reproducer bundle:
http://paste.ubuntu.com/13576737/
PASS: MAAS 1.9b2 + Juju 1.25.0
lxc units get unique IPs: http://paste.ubuntu.com/13576758/
FAIL: MAAS 1.9b2 + Juju 1.25.1
lxc units all have the same IP:
** Description changed:
- With the proposed Juju 1.25.1, lxc units all possess the same IP address:
+ With MAAS 1.9b2 + proposed Juju 1.25.1, lxc units all possess the same IP
address:
http://paste.ubuntu.com/13499208/.
- With stable Juju 1.25.0, lxc units get unique IP addresses as
@andreserl
b2
About to upgrade to latest RC in our lab.
--
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/1519527
Title:
juju 1.25.1: lxc units all have the same IP address -
@andreserl
RC2
Please disregard my mentions of B2. Indeed I am using RC2.
** Description changed:
- With MAAS 1.9b2 + proposed Juju 1.25.1, lxc units all possess the same IP
address:
+ With MAAS 1.9rc2 + proposed Juju 1.25.1, lxc units all possess the same IP
address:
Given that with Juju 1.25.0 + MAAS 1.9b2, the container IPs were sane
and unique, I think Juju should still track and block on this bug as a
regression with shared interest in releasing a functional MAAS 1.9.x +
JUJU 1.25.x combo.
Whether that means waiting for MAAS to be fix-released on a new
** Tags added: openstack uosci
--
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/1488453
Title:
Package postinst always fail on first install when using systemd
To manage notifications
@racb yep, that was my original take on this, but somehow I convinced
myself otherwise apparently. Either way, hacluster won't install on
V/W. ;-)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
# Wily
ubuntu@1ea-wily214622:~$ sudo apt-get install corosync pacemaker python-netaddr
ipmitool
...
Setting up libesmtp6 (1.0.6-4) ...
Setting up libheartbeat2 (1:3.0.5+hg12629-1.2) ...
Setting up liblrmd1 (1.1.12-0ubuntu2) ...
Setting up libpe-status4 (1.1.12-0ubuntu2) ...
Setting up libpengine4
#Vivid
ubuntu@1ea-vivid214622:~$ sudo apt-get install corosync pacemaker
python-netaddr ipmitool
...
Setting up libpe-rules2 (1.1.12-0ubuntu2) ...
Setting up libcib4 (1.1.12-0ubuntu2) ...
Setting up libstonithd2 (1.1.12-0ubuntu2) ...
Setting up libcrmcluster4 (1.1.12-0ubuntu2) ...
Setting up
This doesn't appear to be purely a charm issue. When I apt-get install
heat-api on a fresh trusty instance, I do not have an
/etc/heat/templates/ dir.
Suspect this is a packaging issue, as the package source does contain the awol
items:
Public bug reported:
Starting with nova-cloud-controller/next rev179 (which was a c-h sync),
functional tests for Trusty-Juno began to fail. New instances are in an
ERROR state. Messages are timing out.
NOTE: Trusty-Icehouse and Precise-Icehouse tests are passing as of
n-c-c/next rev181.
#
Blueprint changed by Ryan Beisner:
Work items changed:
Work items for ubuntu-15.06:
[1chb1n] Add V/W charm-helper pieces for amulet testing (bug 1461535): DONE
[1chb1n] Add basic heat charm amulet tests (in conjunction with V/W
enablement): DONE
[1chb1n] Add basic ceilometer-agent charm
Blueprint changed by Ryan Beisner:
Work items changed:
Work items for ubuntu-15.06:
[1chb1n] Add V/W charm-helper pieces for amulet testing (bug 1461535): DONE
[1chb1n] Add basic heat charm amulet tests (in conjunction with V/W
enablement): DONE
[1chb1n] Add basic ceilometer-agent charm
Blueprint changed by Ryan Beisner:
Work items changed:
Work items for ubuntu-15.06:
[1chb1n] Add V/W charm-helper pieces for amulet testing (bug 1461535): DONE
[1chb1n] Add basic heat charm amulet tests (in conjunction with V/W
enablement): DONE
[1chb1n] Add basic ceilometer-agent charm
Blueprint changed by Ryan Beisner:
Work items changed:
Work items for ubuntu-15.06:
- [1chb1n] Add V/W charm-helper pieces for amulet testing (bug 1461535): TODO
- [1chb1n] Add basic heat charm amulet tests (in conjunction with V/W
enablement): TODO
- [1chb1n] Add basic ceilometer-agent charm
Blueprint changed by Ryan Beisner:
Work items changed:
Work items for ubuntu-15.06:
[1chb1n] Add V/W charm-helper pieces for amulet testing (bug 1461535): TODO
[1chb1n] Add basic heat charm amulet tests (in conjunction with V/W
enablement): TODO
[1chb1n] Add basic ceilometer-agent charm
Blueprint changed by Ryan Beisner:
Work items changed:
Work items for ubuntu-15.06:
[1chb1n] Add V/W charm-helper pieces for amulet testing (bug 1461535): TODO
[1chb1n] Add basic heat charm amulet tests (in conjunction with V/W
enablement): TODO
[1chb1n] Add basic ceilometer-agent charm
Blueprint changed by Ryan Beisner:
Definition Status: New = Drafting
--
OpenStack QA for 15.10
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-w-openstack-qa
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https
Blueprint changed by Ryan Beisner:
Work items changed:
Work items for ubuntu-15.07:
[1chb1n] Add basic heat charm amulet tests: TODO
[1chb1n] Add basic percona-cluster charm amulet tests: TODO
[1chb1n] Add basic ceilometer-agent charm amulet tests: TODO
[1chb1n] Add basic cinder-ceph
Blueprint changed by Ryan Beisner:
Work items changed:
+ Work items for ubuntu-15.06:
+ [1chb1n] Add V/W charm-helper pieces for amulet testing (bug 1461535): TODO
+ [1chb1n] Add basic heat charm amulet tests (in conjunction with V/W
enablement): TODO
+ [1chb1n] Add basic ceilometer-agent charm
Blueprint changed by Ryan Beisner:
Whiteboard changed:
[USER STORIES]
- Charlie wants to use the OpenStack charms to run CI in a multi-node scalable
environment against every upstream commit to master. Charlie needs to set up
CI in house to deploy from source and run tempest or other tests
Blueprint changed by Ryan Beisner:
Work items changed:
Work items for ubuntu-15.07:
+ [1chb1n] Add basic heat charm amulet tests: TODO
+ [1chb1n] Add basic percona-cluster charm amulet tests: TODO
+ [1chb1n] Add basic ceilometer-agent charm amulet tests: TODO
+ [1chb1n] Add basic cinder-ceph
I also hit this issue with Trusty-Kilo heat deployments.
Installing python-testscenarios and python-testresources on the heat
unit resolved as a workaround, but is probably not the right/permanent
fix.
** Project changed: cloud-archive = heat (Juju Charms Collection)
** Also affects: heat
** Changed in: cinder (Juju Charms Collection)
Assignee: (unassigned) = Ryan Beisner (1chb1n)
--
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/1440948
Title:
qemu-img: symbol
** Tags added: openstack uosci
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1443542
Title:
curtin race on vivid when /dev/sda1 doesn't exist
To manage notifications about this
ubuntu@juju-osci-sv07-machine-1:~$ tail /etc/apt/sources.list.d/*
== /etc/apt/sources.list.d/cloud-archive.list ==
deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/icehouse
main
== /etc/apt/sources.list.d/cloud_config_sources.list ==
deb
** Branch linked: lp:~1chb1n/charms/trusty/cinder/backport-vol-from-img-
lp1440948
** Branch linked: lp:~1chb1n/charms/trusty/cinder/amulet-fix-vol-from-
img-lp1440948
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in
** Description changed:
- On Precise:
+ On Trusty:
$ qemu-img --help
qemu-img: symbol lookup error: qemu-img: undefined symbol: rbd_aio_discard
$ qemu-img
qemu-img: symbol lookup error: qemu-img: undefined symbol: rbd_aio_discard
$ dpkg-query --show qemu-utils
qemu-utils
** Branch unlinked: lp:~1chb1n/charms/trusty/cinder/volume-from-image
--
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/1440948
Title:
qemu-img: symbol lookup error: qemu-img:
Even with qemu-img installed, the test fails. This appears to be due to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680307
Please see this demonstration of the busted qemu-img on Precise:
http://paste.ubuntu.com/10764770/
** Bug watch added: Debian Bug tracker #680307
FYI, a potentially-related precise rbd libvirt issue:
https://bugs.launchpad.net/charms/+source/nova-compute/+bug/1427660
--
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/1440948
It looks like we still have package issues @ 2015.1~b2-0ubuntu5~cloud0.
trusty-kilo-proposed:
ubuntu@juju-machine-0-lxc-7:/var/log/juju$ dpkg-query --show openstack-dash*
openstack-dashboard 1:2015.1~b2-0ubuntu5~cloud0
openstack-dashboard-ubuntu-theme1:2015.1~b2-0ubuntu5~cloud0
FWIW, I just ran into this on ppc64el trusty-kilo-proposed testing. But
-- it looks like I have but to wait.
** Tags added: openstack uosci
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
** Branch linked: lp:~jjo/charms/trusty/rabbitmq-server/use-
rabbitmqctl-q-for-list-cmds
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1416854
Title:
Fail to install
** Changed in: keystone (Ubuntu)
Status: New = Invalid
** Changed in: keystone (Juju Charms Collection)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
FWIW - We saw this too in our automated OpenStack charm testing (UOSCI).
Our work around is to overwrite known_hosts with our base known_hosts
file on every build, on every jenkins slave. A bit of a hack, but it
does the trick.
--
You received this bug notification because you are a member of
See prior bug https://bugs.launchpad.net/charms/+source/rabbitmq-
server/+bug/1417205
** Tags added: openstack uosci
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1416854
** Tags added: openstack uosci
--
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/1418187
Title:
_get_host_numa_topology assumes numa cell has memory
To manage notifications about this
** Branch linked: lp:~1chb1n/charms/trusty/keystone/kilo-support
** Branch linked: lp:~openstack-charmers/charms/trusty/keystone/next
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
FYI juju deployment used amd64 images; my manual test inadvertently
used the i386 image. I re-confirmed manual apt pkg install with an
amd64 vivid image.
Adding system user `rabbitmq' (UID 111) ...
Adding new user `rabbitmq' (UID 111) with group `rabbitmq' ...
Not creating home directory
Public bug reported:
For Trusty-Kilo OpenStack deployments, the config-changed hook fails.
Keystone.log shows:
ERROR No module named backends.sql
See attached for traceback.
** Affects: keystone (Ubuntu)
Importance: Undecided
Status: New
** Affects: keystone (Juju Charms
** Tags added: openstack uosci
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1410155
Title:
Missing /etc/rabbitmq
To manage notifications about this bug go to:
** Tags added: openstack uosci
--
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/1408972
Title:
openvswitch: failed to flow_del (No such file or directory)
To manage
** Tags added: openstack uosci
--
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/1336555
Title:
ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size()
To manage notifications
Update, fyi:
Nova booted 110 instances. 16 had no net.
Deleted the instances.
Nova booted 110 more instances. 17 had no net.
Deleted the instances.
Consistent with the ~15% no net we saw last time around.
v
Deleted neutron nets and subnets, then re-added them.
^
Nova booted 110 instances. All
After revisiting the unit logs from successful runs and failed runs,
this appears to be behind the fail (wants a reboot):
Reading state information... Done
2015-01-06 19:56:06 INFO mon-relation-changed Creating new GPT entries.
2015-01-06 19:56:06 INFO mon-relation-changed Warning: The kernel is
Please disregard my ceph comment on this bug. Wrong tab.
--
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/1352570
Title:
ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size()
And disregard GPT comment. Same story. Geez. I'm going EOD!
--
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/1352570
Title:
ovs-vswitchd crashed with SIGSEGV in
Oh, fyi, it is all 3 ceph units:
ceph:
charm: local:utopic/ceph-105
exposed: false
relations:
mon:
- ceph
units:
ceph/0:
agent-state: error
agent-state-info: 'hook failed: mon-relation-changed'
agent-version: 1.20.14
machine: 2
So from a user symptom / impact standpoint, when new instances are nova
booted, they are able to send DHCP DISCOVER packet through the
corresponding bridge, but return DHCP OFFER traffic never reaches the
new instance.
In all cases that I have seen, the neutron net, subnet, and port
statuses all
We're seeing ovs crashes on a private deployment. They seem to surface
only after being up for some time (1mo) and after creating/deleting a
lot of instances over that time period (20K), but all with a sane
system resource load.
$ apt-cache policy openvswitch-common
openvswitch-common:
** Tags added: openstack uosci
--
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/1352570
Title:
ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size()
To manage notifications
For the life of me, I couldn't get ubuntu-bug or apport to automagically
add the .crash and stack trace to this bug. Here it is, though, via
attachment. ~9mb
** Attachment added: _usr_sbin_ovs-vswitchd.0.crash
Public bug reported:
keystone icehouse package needs dependency for python-six 1.5.2-1, which
is in the cloud archive
2014-12-16 04:05:17 INFO install Setting up keystone
(1:2014.1.3-0ubuntu2~cloud0) ...
2014-12-16 04:05:17 INFO install Traceback (most recent call last):
2014-12-16 04:05:17
ubuntu@juju-beis1-machine-8:~$ dpkg -l | egrep 'keystone|six'
iF keystone 1:2014.1.3-0ubuntu2~cloud0
OpenStack identity service - Daemons
ii python-keystone 1:2014.1.3-0ubuntu2~cloud0
OpenStack identity service - Python library
ii
When installing keystone in a fresh enviro using the cloud archive, it
installs cleanly. But if an older version of python-six is already
installed, such as may be provided earlier by another package's
dependency, the older 1.1.0-2 six version remains.
--
You received this bug notification
issue affects precise OpenStack charm deployments
--
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/1403114
Title:
[SRU] icehouse package needs python-six 1.5.2-1 dependency
To
** Tags added: openstack
--
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/1382632
Title:
Insecure key file permissions
To manage notifications about this bug go to:
Blueprint changed by Ryan Beisner:
Work items changed:
Work items for ubuntu-14.05:
[gnuoy] charm-helpers unit testing: DONE
Work items for ubuntu-14.06:
[mikemc] Simplestreams image sync charm: DONE
[niedbalski] swift-storage block device persistence through reboots: DONE
[gnuoy
Today's commits on n-api and ncc triggered deploy tests. P, T + U all
deploy cleanly with -next branches:
ceilometer: 52
ceilometer-agent: 41
ceph: 82
cinder: 45
glance: 62
keystone: 79
mongodb: 52
mysql: 126
neutron-api: 45
neutron-gateway: 67
neutron-openvswitch: 32
nova-cloud-controller:
Also just so you know, unit test on n-api is failing:
Starting tests...
...F..F
==
FAIL: test_register_configs
(unit_tests.test_neutron_api_utils.TestNeutronAPIUtils)
Using these revs from -next, Trusty and Utopic deploy cleanly:
neutron-api: 44
nova-cloud-controller: 103
** Attachment added: unit-nova-cloud-controller-0.log.trusty
And Precise deploy fails with same as jjo reports:
hook failed: shared-db-relation-changed
** Attachment added: unit-nova-cloud-controller-0.log.precise
FYI/FWIW, there was err in my deploy test logic from gnuoy's MP. I deploy
tested it against Juno, which passed.
Once it merged, our CI deploy tests which run -next against P, T U, started
to fail. Naturally, it'd be *much* better to detect that at the MP level.
Adjusting logic.
--
You
Nova sec operations are now OK after deploying with ncc and neutron-api.
http://paste.ubuntu.com/8459292/
FYI, the deployer bundle used:
http://paste.ubuntu.com/8459289/
lint checks pass for:
https://code.launchpad.net/~gnuoy/charms/trusty/nova-cloud-controller/next-fix-1372893
** Tags removed: osci
** Tags added: uosci
--
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/1372893
Title:
Neutron has an empty database after deploying juno on utopic
To manage
fyi, same bundle deploys ok with 104+41, and nova-secgroup cmds succeed.
## revnos deployed:
ceilometer: 52
ceilometer-agent: 41
ceph: 82
cinder: 45
glance: 62
keystone: 79
mongodb: 52
mysql: 126
neutron-api: 41
neutron-gateway: 65
neutron-openvswitch: 31
nova-cloud-controller: 104
nova-compute:
** Also affects: neutron-api (Juju Charms Collection)
Importance: Undecided
Status: New
** Also affects: nova-cloud-controler (Juju Charms Collection)
Importance: Undecided
Status: New
** No longer affects: neutron-api (Ubuntu)
--
You received this bug notification because
+1, we had a filled disk in on one box due to this.
--
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/1355877
Title:
celery log files are not rotated
To manage notifications about this
Is this a dup of 1302192?
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1302192
--
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/1313550
Title:
ping does not work as a
FYI may also want to see comment 5 from previous/related bug 1302192;
attributes were OK in cloudimage at that point.
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1302192/comments/5
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Thank you for the info. Can you also collect and post more info about
the host using these commands?
dpkg -l | egrep 'qemu|kvm|libvirt'
lsb_release -a
free -m
uname -a
virsh capabilities
qemu-system-x86_64 -machine help
--
You received this bug notification because you are a member of
Add'l input from my environment:
I recently upgraded one of my two local hosts from Precise to Trusty,
containing a dozen or so guests, including Ubuntu Precise, Trusty,
CentOS, and a Windows guest. I had to adjust the machine types in the
XML definitions after the upgrade. Other than that,
Public bug reported:
An existing site is no longer online following a Precise to Trusty
upgrade when the site is in the default DocumentRoot. This is because
DocumentRoot on Trusty is now /var/www/html whereas it was /var/www for
Precise.
There is a simple work-around for simple deployments:
@Doug I saw the same in a 12.04 to 14.04 upgrade, also had to edit the
machine type. Other than that one edit, all of my VMs worked after the
Trusty upgrade. Take note that this triggers Windows VMs to have to re-
activate due to the changed 'hardware.'
But I think this bug is more about a live
Thank you for filing this bug.
For further clarification: are you connecting to a vncserver service
running within the guest VM? Or are you connecting to the qemu VNC head
on the server which hosts the virtual machines? Also, on which host and
environment are you seeing the 'low graphics
Curiosity fueled a couple of tests on this. In checking 2 common
scenarios, at least one use case confirms.
Aside from this confirmation, a bigger-picture question could be: in
principle, how is 53 being open and interactive by default any different
than 80, 22, or 137-139 being open and
Yep, I'm with ya Robie.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1306646
Title:
dnsmasq provides recursive answers to the Internet by default
To manage notifications about
FYI - related bug regarding missing dependencies in a no-network
scenario: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1172566
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Issue confirmed on Trusty daily ISO.
** Tags added: trusty
--
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/1172566
Title:
MAAS Server ISO install fails when network is disconnected
More detail, see also attached tarball:
Apr 14 17:26:05 in-target: dpkg: error processing package
maas-region-controller-min (--configure):
Apr 14 17:26:05 in-target: subprocess installed post-installation script
returned error exit status 255
Apr 14 17:26:05 in-target: dpkg: dependency
Thanks, Scott. Further confirmation:
In previous no-network MAAS tests, the environment had no default
gateway set.
So, the missing dependency claim is debunked. This is not a dependency,
nor an ISO issue. Dependencies are indeed met on the Trusty ISO.
I confirmed this by successful
Take note: the missing dependency claim is debunked. Dependencies are
indeed met on the Trusty ISO. I confirmed this by successful
installation of MAAS from ISO on a machine with a fully configured ip
interface, but with no internet access. There is however, a separate
MAAS installation
I think you're right, and I think that is indeed the place to do it.
I've seen other people, on similar topics, debate 'the line.' This very
discussion will be valuable in this change because it shows that we are
assessing that aspect. Thanks again for filing this.
--
You received this bug
Confirmed fix in a new install using Trusty iso 2014-apr-11 ... MAAS
front end is functional on first boot.
--
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/1298559
Title:
Internal
Fix confirmed on Trusty server ISO 2014-APR-10. MAAS front end is
functional after installation via 'Create a new MAAS on this server'
method.
Thanks, Andres!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Dave - i'll re-test today with no internet. But the good news is, using
20140410 iso, you can now get a working MAAS front end.
James - will do on 20140411, again with no-internet.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas
Installing MAAS controller from ISO with no internet connection fails
due to dependencies of the maas, maas-dns and maas-region-controller
packages. pkg-sel bails out with 100.
If we do expect users to be able to deploy a MAAS controller on an
island with no internet connection, then this is
Re-confirmed fix in a new install using Trusty iso 2014-apr-10. MAAS
front end is functional on first boot.
--
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/1298559
Title:
Internal
Confirmed 'internal server error' issue exists with Trusty 2014-APR-09
daily ISO, when using the 'Create a new MAAS on this server' method.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Issue exists in Trusty server ISO 2014-APR-09.
Workaround confirmed, but I've not explored other potential effects of removing
this package:
sudo apt-get remove libpam-smbpass
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Confirmed to resolve the MAAS upgrade crash on an existing Trusty MAAS
environment.
Beware however, after rev 2230 was confirmed in the repo, I was still
stuck in a loop with apt/dpkg trying to install rev 2227. I couldn't
complete an apt-get update (it halted, advising that dpkg --configure -a
1 - 100 of 105 matches
Mail list logo
