[Bug 1080912] Re: qemu-kvm must depend on udev
Hello Jared, or anyone else affected, Accepted qemu-kvm into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qemu-kvm/1.0+noroms- 0ubuntu14.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: qemu-kvm (Ubuntu Precise) Status: In Progress = Fix Committed ** Tags added: verification-needed ** Changed in: qemu-kvm (Ubuntu Quantal) Status: In Progress = Fix Committed -- 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/1080912 Title: qemu-kvm must depend on udev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1080912/+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 1080912] Please test proposed package
Hello Jared, or anyone else affected, Accepted qemu-kvm into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qemu-kvm/1.2.0 +noroms-0ubuntu2.12.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1080912 Title: qemu-kvm must depend on udev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1080912/+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 1078530] Please test proposed package
Hello Robert, or anyone else affected, Accepted qemu-kvm into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qemu-kvm/1.0+noroms- 0ubuntu14.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: qemu-kvm (Ubuntu Quantal) Status: In Progress = Fix Committed -- 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/1078530 Title: upstart job fails to start under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1078530/+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 1078530] Please test proposed package
Hello Robert, or anyone else affected, Accepted qemu-kvm into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qemu-kvm/1.2.0 +noroms-0ubuntu2.12.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1078530 Title: upstart job fails to start under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1078530/+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 1077838] Please test proposed package
Hello Robert, or anyone else affected, Accepted qemu-kvm into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qemu-kvm/1.0+noroms- 0ubuntu14.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: qemu-kvm (Ubuntu Quantal) Status: In Progress = Fix Committed -- 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/1077838 Title: qemu-nbd -r -c taints device for subsequent usage, even after -d To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1077838/+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 1077838] Please test proposed package
Hello Robert, or anyone else affected, Accepted qemu-kvm into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qemu-kvm/1.2.0 +noroms-0ubuntu2.12.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1077838 Title: qemu-nbd -r -c taints device for subsequent usage, even after -d To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1077838/+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 1057024] Re: kvm kernel module always loaded, without setting /dev/kvm permissions
Hello Parameswaran, or anyone else affected, Accepted qemu-kvm into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qemu-kvm/1.0+noroms- 0ubuntu14.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-done ** Tags added: verification-needed ** Changed in: qemu-kvm (Ubuntu Quantal) Status: In Progress = Fix Committed -- 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/1057024 Title: kvm kernel module always loaded, without setting /dev/kvm permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1057024/+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 1057024] Please test proposed package
Hello Parameswaran, or anyone else affected, Accepted qemu-kvm into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qemu-kvm/1.2.0 +noroms-0ubuntu2.12.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1057024 Title: kvm kernel module always loaded, without setting /dev/kvm permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1057024/+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 156085] Re: Could not open /proc/bus/usb/devices
** Changed in: usbview (Debian) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/156085 Title: Could not open /proc/bus/usb/devices To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/156085/+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 1081836] Re: nova-compute (folsom) fails to start, compute_driver is None
** Also affects: nova Importance: Undecided Status: New ** Also affects: nova/folsom Importance: Undecided Status: New ** Changed in: nova Status: New = Invalid ** Changed in: nova/folsom Milestone: None = 2012.2.1 ** Changed in: nova/folsom Importance: Undecided = High -- 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/1081836 Title: nova-compute (folsom) fails to start, compute_driver is None To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1081836/+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 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting
the current default installation wherein network-manager starts an instance of dnsmasq to act as a DHCP, DNS and TFTP server. NetworkManager starts an instance of dnsmasq to act only as a non- caching DNS nameserver forwarder. This instance listens only on the loopback interface 127.0.1.1. If your client is DHCPing with a dnsmasq instance on an Ubuntu server then that dnsmasq instance is most probably a standalone instance, configured by means of files included in the dnsmasq package (not to be confused with the dnsmasq-base package which contains little more than the dnsmasq binary and which both the dnsmasq package and the network-manager package depend on) and started by an initscript, not by NetworkManager. In reading further into your text my understanding is hampered by the fact that I am not entirely sure which machine you are referring to at different points in your text. The problem is that the LTSP client, after successfully getting DHCP assignments, fails to download the pxelinux boot image. It reports PXE-E32: TFTP open timeout. To be more specific on the DHCP assignments, it identifies my hardware router as the DHCP server and the default gateway. It identifies the LTSP server as proxy and boot server. Is your LTSP server running Ubuntu and standalone dnsmasq? Then shouldn't the client use your LTSP server as the DHCP server? So dnsmasq is not binding to my server IP during boot. If I remove /etc/dnsmasq.d/network-manager (which issues the sole dnsmasq directive to bind all the interfaces instead of listening on 0.0.0.0) and restart the server it allows the client to boot normally. I think I know what is happening. The network-manager package causes (by means of the /etc/dnsmasq.d/network-manager file) the standalone dnsmasq to start in bind-interfaces mode. In that mode dnsmasq doesn't listen on the wildcard IP address; it only listens on the addresses assigned to interfaces that are up when it (dnsmasq) starts. At boot, dnsmasq starts before the external interface is configured via DHCP, so dnsmasq doesn't listen on the external interface. If dnsmasq is restarted after the external interface is configured then dnsmasq listens on that interface too. If you remove /etc/dnsmasq.d/network-manager then standalone dnsmasq listens on the wildcard address when it starts and all is well except that now standalone dnsmasq conflicts with the NetworkManager-controlled dnsmasq instance. To fix this you have to disable the latter. Edit /etc/NetworkManager/NetworkManager.conf and comment out the line dns=dnsmasq: put a '#' at the beginning of the line. In the future we hope that standalone dnsmasq running in bind-interfaces mode will be enhanced such that it listens on interfaces that are brought up after it (dnsmasq) starts. The author of dnsmasq, Simon Kelley, has already implemented this enhancement experimentally. Once that work is done it will be possible to run dnsmasq in bind-interfaces mode without causing the problem that you ran into. -- 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/959037 Title: NM-controlled dnsmasq prevents other DNS servers from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+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 1081952] [NEW] squid 3.1.19 external_acl_type fail
Public bug reported:
System: ubuntu 12.04.1
Squid: 3.1.19-1ubuntu3.12.04.1 (apt-get install)
In squid.conf:
...
external_acl_type testcom_ip ttl=0 children=5 ipv4 %SRC php
/php/squid_eacl/test_ip.php
acl testcom_ipacl external testcom_ip
http_access allow testcom testcom_ipacl
http_access deny all
...
In the /php/squid_eacl/test_ip.php, I let it return OK everytime:
?php
$time=null;
$output=null;
while ($i = fopen('php://stdin', 'r')) {
$ii = fgets($i);
$s = trim($ii);
fclose($i);
if ($s == NULL) {
if ($time == time()) {
break;
} else {
$time = time();
continue;
}
}
$o = fopen('php://stdout', 'w');
#fwrite($o,OK user=test\n);
fwrite($o,OK\n);
fclose($o);
}
?
Client use the Squid server as proxy and will get Access Deny many
time. It seems squid will miss the external_acl_type acl ( http_access
allow testcom testcom_ipacl) of config.conf in sometime.
** Affects: squid3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1081952
Title:
squid 3.1.19 external_acl_type fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1081952/+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 1053364] Re: Add SIGPIPE handler to subprocess execution in rootwrap and utils.execute
** Changed in: cinder Status: Fix Committed = Fix Released ** Changed in: cinder Milestone: None = grizzly-1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to quantum in Ubuntu. https://bugs.launchpad.net/bugs/1053364 Title: Add SIGPIPE handler to subprocess execution in rootwrap and utils.execute To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1053364/+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 541886] Re: clamd: can't initialize the internal logger
So apparmor is not correctly configured then? What apparmor config change is needed? By settings into complain mode, presumably after a reboot, apparmor will log errors again? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/541886 Title: clamd: can't initialize the internal logger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/541886/+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 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Changed in: cinder Status: Fix Committed = Fix Released -- 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/1065702 Title: After folsom upgrade, instances can no longer access existing volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065702/+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
[Blueprint servercloud-r-ceph] Ceph Activities for Raring
Blueprint changed by James Page: Work items changed: Work items: - Backport argonaut to precise-folsom cloud archive: INPROGRESS + Backport argonaut to precise-folsom cloud archive: DONE Upgrade packaging to bobtail release: TODO MIR for additional dependencies for upstart integration: TODO Enable upstart configurations in packaging: TODO Test upgrade paths from 12.10 with upstart and init scripts: TODO - Upstream support for XFS in ceph-disk-*: TODO + Upstream support for XFS in ceph-disk-*: DONE Review upstream patches for mod_fastcgi: TODO Review/test ceph RADOS with mod_fcgid: TODO Write dep8 tests for ceph and get automated: TODO Write UTAH tests for ceph and get automated: TODO Identify use-cases for ceph performance scenarios: TODO Upload bobtail to the grizzly cloud archive: TODO Multi-node ceph testing in the lab: TODO Ceph testing in the Openstack CI Lab: INPROGRESS Enable rbd storage pool support in libvirt: DONE -- Ceph Activities for Raring https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-ceph -- 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 1075948] Re: Cinder installation depends on installing Git
** Branch linked: lp:~openstack-ubuntu-testing/cinder/grizzly -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1075948 Title: Cinder installation depends on installing Git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1075948/+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 1081836] Re: nova-compute (folsom) fails to start, compute_driver is None
** Changed in: nova (Ubuntu) Importance: Undecided = High ** Changed in: nova (Ubuntu) Status: New = Confirmed -- 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/1081836 Title: nova-compute (folsom) fails to start, compute_driver is None To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1081836/+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 1081701] Re: The metadata address mentioned in the preseed is wrong.
Raphaël and I discussed two options:
1. Render the preseed in the cluster.
2. Send the cluster address to the region during start-up so that it
can render the preseed with the correct address.
We decided that #1 better divides responsibilities, but that we would
go for option #2 for two reasons: it's a lot less work, and it doesn't
preclude doing #1 at a later date and may be useful to that effort.
I made some notes about what it would take to do #1, included below,
which may be worth tracking as a blueprint (Julian, what is the best
way to propose work like this?).
.. -*- mode: rst -*-
Things needed from the region to render a preseed:
==
- From ``maasserver.compose_preseed``:
- Metadata URL: ``absolute_reverse('metadata')``
- Token: ``NodeKey.objects.get_token_for_node(node)``
- Node status: ``node.status`` (only if commissioning or not)
- From ``maasserver.preseed``:
- Node status: ``node.status`` (only if commissioning or not)
- Enum ``PRESEED_TYPE``.
⇒ Move to ``provisioningserver``?
- Setting ``PRESEED_TEMPLATE_LOCATIONS``.
⇒ Move to ``provisioningserver``.
- Config:
- ``commissioning_distro_series``
- ``main_archive``
- ``ports_archive``
- ``http_proxy``
⇒ Can be obtained via API.
- Server host: ``get_maas_facing_server_host`` (used for?)
⇒ Already known on cluster?
- Server URL: ``absolute_reverse('nodes_handler')`` (used for?)
⇒ Already known on cluster?
- Enlistment URL: ``absolute_reverse('enlist')``
- Disable netboot URL::
absolute_reverse(
'metadata-node-by-id',
args=['latest', node.system_id])
- Enlistment preseed URL::
absolute_reverse(
'metadata-enlist-preseed', args=[version],
query={'op': 'get_enlist_preseed'})
⇒ Becomes responsibility of ``provisioningserver``.
- Regular preseed URL::
absolute_reverse(
'metadata-node-by-id', args=[version, node.system_id],
query={'op': 'get_preseed'})
⇒ Becomes responsibility of ``provisioningserver``.
- From ``contrib/preseeds_v2/generic``:
- Node architecture: ``node.architecture``
Which boils down to:
Code moves (see below_) and a view that returns:
- Metadata URL: ``absolute_reverse('metadata')``
- Token: ``NodeKey.objects.get_token_for_node(node)``
- Node status: ``node.status`` (only if commissioning or not)
- Node architecture: ``node.architecture``
- Enlistment URL: ``absolute_reverse('enlist')``
- Disable netboot URL::
absolute_reverse(
'metadata-node-by-id', args=['latest', node.system_id])
- *Optional:* return config items (e.g. ``ports_archive``)
.. _below: `Adding rendering server to the provisioning server:`_
Adding rendering server to the provisioning server:
===
- Resurrect HTTP server in ``provisioningserver.plugin``.
- Move code, as detailed earlier_, to ``provisioningserver``, and
perform some moderate refactoring.
- Add handler to the ``provisioningserver`` HTTP server to query the
view_ detailed above, perhaps query the API for config, and call the
render code.
.. _earlier: `Things needed from the region to render a preseed:`_
.. _view: `Which boils down to:`_
Notes:
==
- The ``pxeconfig`` view calculates the preseed URLs. This calculation
no longer needs to happen, and its responsibility passes to the
provisioning server.
--
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/1081701
Title:
The metadata address mentioned in the preseed is wrong.
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1081701/+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 1081836] Re: nova-compute (folsom) fails to start, compute_driver is None
Reviewed: https://review.openstack.org/16711 Committed: http://github.com/openstack/nova/commit/7e8a1662577bc86e873f9f957e74076ac89eb80b Submitter: Jenkins Branch:stable/folsom commit 7e8a1662577bc86e873f9f957e74076ac89eb80b Author: Adam Gandelman adam.gandel...@canonical.com Date: Wed Nov 21 16:13:29 2012 -0800 Reinstate default FLAGS.compute_driver for folsom A previous cherry-picked commit moved the compute_driver flag from the compute manager to the global flags file, but did not take the flags default value along. This breaks existing Folsom installations that still use connection_type. Note, this is only proposed to stable/folsom to fix a regression. Not applicable to master as connection_type is gone in Grizzly. Fixes bug 1081836. Change-Id: I135d6adc215c40fb9f46f382dbe22fb38b413ff8 ** Changed in: nova/folsom Status: New = Fix Committed -- 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/1081836 Title: nova-compute (folsom) fails to start, compute_driver is None To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1081836/+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 1075948] Re: Cinder installation depends on installing Git
** Branch linked: lp:~openstack-ubuntu-testing/cinder/precise-grizzly -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1075948 Title: Cinder installation depends on installing Git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1075948/+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 1081836] Re: nova-compute (folsom) fails to start, compute_driver is None
Thanks for find this nasty issue This is the commit which introduced the regression: https://review.openstack.org/16432 It's a backport of this: https://review.openstack.org/14991 However, the latter fix was only required to fix an issue with this fix on master: https://review.openstack.org/14068 This is now being backported too: https://review.openstack.org/#/c/16713/ Which means the original backport causing this regression will still be needed and we just need to fix it. ** Changed in: nova/folsom Importance: High = Critical ** Changed in: nova/folsom Assignee: (unassigned) = Mark McLoughlin (markmc) -- 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/1081836 Title: nova-compute (folsom) fails to start, compute_driver is None To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1081836/+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 1081836] Fix proposed to nova (stable/folsom)
Fix proposed to branch: stable/folsom Review: https://review.openstack.org/16773 -- 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/1081836 Title: nova-compute (folsom) fails to start, compute_driver is None To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1081836/+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 1081836] Re: nova-compute (folsom) fails to start, compute_driver is None
Wow, some sort of weird overlap. ** Changed in: nova/folsom Assignee: Mark McLoughlin (markmc) = Adam Gandelman (gandelman-a) -- 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/1081836 Title: nova-compute (folsom) fails to start, compute_driver is None To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1081836/+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 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Branch linked: lp:~openstack-ubuntu-testing/cinder/precise-folsom -- 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/1065702 Title: After folsom upgrade, instances can no longer access existing volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065702/+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
[Blueprint servercloud-r-lxc] LXC work for R
Blueprint changed by Stéphane Graber:
Work items changed:
Work items:
[serge-hallyn] Send user namespace delta to kernel-team ASAP: DONE
[serge-hallyn] Post syslog namespace design wiki page: DONE
[serge-hallyn] Send syslog namespace prototype to lkml: DONE
[serge-hallyn] Send syslog namespace description to kernel-team ASAP: BLOCKED
[daniel-lezcano] Improved monitor notification support: TODO
[stgraber] Fix lxc-ls (re-write using api): DONE
[serge-hallyn] lxc-create or template option to specify userns mapping: TODO
[serge-hallyn] push user namespace lxc delta upstream: TODO
[serge-hallyn] add config options for loglevel and output file: TODO
[serge-hallyn] drop lxccontainer.log default logging in api: BLOCKED
[serge-hallyn] lxc-create - set a default log level and log file in
/var/log/lxc/$container: TODO
[serge-hallyn] lxc.autodev: push lxc patch upstream: INPROGRESS
[serge-hallyn] lxc.autodev: push lxc patch into package: TODO
[serge-hallyn] lxc.autodev: push mountall patch into package: TODO
[serge-hallyn] list broken functionality in ubuntu container in user
namespace: TODO
[serge-hallyn] improve ubuntu container experience in user namespace: TODO
[serge-hallyn] add config option for RLIMIT_NPROC in userns container: TODO
[stgraber] add (not container) to upstart jobs which just fail: TODO
- [stgraber] write tool to pass devices into container: INPROGRESS
+ [stgraber] write tool to pass devices into container: DONE
[stgraber] create a separate package for templates: DONE
[stgraber] have lxc-create record the name of template used in container
config file for debugging: TODO
[stgraber] support templates outside of $templatedir (pushed to git): DONE
[stgraber] investigate what's needed to support containers outside of
/var/lib/lxc: TODO
[serge-hallyn] test apparmor profile stacking; implement any lxc changes
needed to support it: BLOCKED
[stgraber] rebase staging branch on upstream master: DONE
[serge-hallyn] test attach support in userns kernrel; shout if anything
missing: TODO
[daniel-lezcano] investigate/use http://lxc.sourceforge.net/download/procfs
to filter /proc/{cpuinfo,meminfo,etc}: TODO
[stgraber] investigate: does dnsmasq save mac-ip across host reboots? (it
does): DONE
[stgraber] Port arkose to python3 (and make it pep8 clean): TODO
[stgraber] Port arkose to python3-lxc: TODO
[stgraber] Port auto-dist-upgrader to python3-lxc: TODO
[stgraber] Tweak the tests to ensure auto-dist-upgrader on LXC gives the same
results as on kvm: TODO
[stgraber] Check what it'd take to make lxc work fine when
creating/starting/stopping containers in parallel: TODO
[stgraber] Add code to detect and install langpacks in containers (at least
-base-en): TODO
[stgraber] Get LXC into main: TODO
--
LXC work for R
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-lxc
--
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 1081701] Re: The metadata address mentioned in the preseed is wrong.
Ok cheers - I have captured this on https://blueprints.launchpad.net/maas/+spec/cluster-renders-preseed -- 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/1081701 Title: The metadata address mentioned in the preseed is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1081701/+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 1081701] Re: The metadata address mentioned in the preseed is wrong.
see also bug 1081701 -- 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/1081701 Title: The metadata address mentioned in the preseed is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1081701/+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 1081701] Re: The metadata address mentioned in the preseed is wrong.
grar, I meant see also bug 1081696 -- 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/1081701 Title: The metadata address mentioned in the preseed is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1081701/+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
