[Bug 1368497] Re: AMT Power control doesn't handle some passwords
** Changed in: maas Status: New = Triaged ** Changed in: maas Importance: Undecided = Medium -- 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/1368497 Title: AMT Power control doesn't handle some passwords To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1368497/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1373261] Re: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address
On 5 November 2014 11:23, Jeroen T. Vermeulen 1373...@bugs.launchpad.net wrote: Note how the first part of the netloc, up to the first colon, is replaced with the new address — but the rest of the netloc is still there. Ah, now ISWYM. Sorry, I'd missed that the *existing* MAAS URL in pserv.yaml was an IPv6 address. Thanks for clarification. -- 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/1373261 Title: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1373261/+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 1373261] Re: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address
** Changed in: maas Status: Triaged = In Progress ** Changed in: maas (Ubuntu) Assignee: Gavin Panella (allenap) = (unassigned) -- 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/1373261 Title: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1373261/+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 1373261] Re: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address
I can't reproduce this locally; it seems to work fine with properly formatted — and even improperly formatted — IPv6 addresses. We really need to see the problem you're seeing Jeroen. ** Changed in: maas Status: In Progress = Incomplete -- 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/1373261 Title: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1373261/+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 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
** Branch linked: lp:~gmb/maas/restrict-dynamic-range-to- slash-16-bug-1382190 -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+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 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
** Changed in: maas Status: In Progress = Fix Committed ** Branch linked: lp:~gmb/maas/generate-dns-for-dynamic-pool-bug-1382190 -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+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 1373261] Re: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address
** Changed in: maas Assignee: (unassigned) = Graham Binns (gmb) -- 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/1373261 Title: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1373261/+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 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
Using $GENERATE statements, I get the following results: /16 dynamic range: 10.0.0.1 - 10.0.255.255 - Reverse Zone: http://paste.ubuntu.com/8721352/ - Forward Zone: http://paste.ubuntu.com/8721358/ /24 dynamic range: 10.0.0.1 - 10.0.0.255 - Reverse zone: http://paste.ubuntu.com/8721363/ - Forward zone: http://paste.ubuntu.com/8721366/ /25 dynamic range: 10.0.0.128 - 10.0.0.255 - Reverse zone: http://paste.ubuntu.com/8721391/ - Forward zone: http://paste.ubuntu.com/8721403/ Weird dynamic range: 10.0.0.1 - 10.0.1.33: - Reverse zone: http://paste.ubuntu.com/8721501/ - Forward zone: http://paste.ubuntu.com/8721503/ Note that there's what looks like a weird inefficiency in the /24 (1-255) and others. That's because I'm using netaddr.IPRange() internally to create an IP range to work from, and then converting that into a set of IPNetworks to ensure we get full coverage of weird corner-case networks (and so that I don't have to do all the maths myself). Thing is, .1-.255, although we identify it as a /24 by sight, isn't actually a /24; it's only 254 addresses, so IPRange breaks it down into individual CIDRs rather than just covering it with a /24. It's a weirdness we can live with, I think. For a /16/ we still see only 260-odd $GENERATES as opposed to 65,000 which I'd call an improvement :). -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+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 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
** Changed in: maas Status: Triaged = In Progress -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+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 1274947] Re: juju lxc instances deployed via MAAS don't have resolvable hostnames
*** This bug is a duplicate of bug 1382190 *** https://bugs.launchpad.net/bugs/1382190 ** This bug has been marked a duplicate of bug 1382190 LXCs assigned IPs by MAAS DHCP lack DNS PTR entries -- 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/1274947 Title: juju lxc instances deployed via MAAS don't have resolvable hostnames To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1274947/+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 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
Ah, so, the light of day: $GENERATE is only useful for networks with an address range /24 — i.e. up to 255 addresses. After that it breaks down, because: $GENERATE 1-254 $.$.0.10.in-addr.arpa. IN PTR no-name-yet-$.$.maas. Only generates 255 addresses; it's not recursive. You just get 10.10.0.10.in-addr.arpa. 300 IN PTR no-name-yet-10-10.maas. 100.100.0.10.in-addr.arpa.300 IN PTR no-name-yet-100-100.maas. 101.101.0.10.in-addr.arpa.300 IN PTR no-name-yet-101-101.maas. 102.102.0.10.in-addr.arpa.300 IN PTR no-name-yet-102-102.maas. 103.103.0.10.in-addr.arpa.300 IN PTR no-name-yet-103-103.maas. 104.104.0.10.in-addr.arpa.300 IN PTR no-name-yet-104-104.maas. 105.105.0.10.in-addr.arpa.300 IN PTR no-name-yet-105-105.maas. Etc. Which means that for a /16 we'd need 256 $GENERATEs; for a /8, 65536 of them. That's… suboptimal. Options: 1. We could say We'll generate PTR records for /24 dynamic ranges only. Advantages: Pretty easy to do Disadvantages: We're forcing users into a particular configuration. 2. We limit the dynamic range to /16 for IPv4 (similar to before when we enforced a /16 network). Advantages: 256 lines isn't the *worst*, performance wise, so we could probably get away with it. Disadvantages: We still have to write those 256 lines on every deployment. 3. We add the PTR record when we parse the DHCP lease Advantages: No bloat; pretty much as we already do now for static IPs. Disadvantages: Noticeable lag between the node acquiring a lease and getting a PTR. None of these options is lovely. -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+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 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
(I'd say that option 3 is the most tasteful, as long as we can solve the lag problem). -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
On 23 October 2014 11:04, Julian Edwards 1382...@bugs.launchpad.net wrote: I don't think #3 is that bad actually; remember that's how we used to do it before static IP days so it's tried and tested (although admittedly the DNS was in place by the time commissioning ended). Yeah, #3 doesn't work for the use case of LXC containers that come up relatively quickly, aren't going through commissioning, and just want to Get Stuff Done. -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+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 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
Andres and I have discussed this further, and he pointed out that the LXCs can take a *long* time to start. That would be sufficient time for us to parse the leases file and update the DNS with a PTR for the new node (option #3). I've tested this out locally. The LXC container took ~30minutes to start from `juju deploy mysql --to lxc:0`, and it acquired an IP address ~5 minutes before the juju agent showed as started. It was another 5 minutes until the mysql unit showed as started. This is more than enough time for us to create DNS entries for the container, with a hostname either based on its IP address (e.g. maas- dynamic-1.maas) or based on the client-hostname field in the lease (e.g. juju-machine-0-lxc-0-dynamic.maas). The second is more meaningful, but it's also more code. Andres and I agreed that this was a better solution than #2 above. -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+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 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
We've agreed that as a fix for the problem — since it's going to potentially break a lot of charms on customer deployments — we're going to put PTR records back in for dynamic-pool IP addresses. I'm going to investigate using the bind GENERATE directive to make this simpler [1]. [1] http://www.thedumbterminal.co.uk/?action=showArticlearticleId=116 ** Changed in: maas Status: Incomplete = Triaged ** Changed in: maas Assignee: Julian Edwards (julian-edwards) = Graham Binns (gmb) -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+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 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
I started out by poking the $GENERATE directive into my reverse zone file manually: ; Zone file modified: 2014-10-21 18:24:59.654931. ; Note that the modification time of this file doesn't reflect ; the actual modification time. MAAS controls the modification time ; of this file to be able to force the zone to be reloaded by BIND. $TTL300 @ INSOA maas. nobody.example.com. ( 000260 ; serial 600 ; Refresh 1800 ; Retry 604800 ; Expire 300 ; TTL ) IN NS maas. $GENERATE 1-100 $.0.0.10.in-addr.arpa. IN PTR no-name-yet-$.maas. 129.0.0.10.in-addr.arpa. IN PTR devoted-minute.maas. 128.0.0.10.in-addr.arpa. IN PTR dismayed-clown.maas. This works perfectly: graham@dodger:~⟫ dig +noall +answer -x 10.0.0.128 @10.0.0.1 128.0.0.10.in-addr.arpa. 300IN PTR dismayed-clown.maas. graham@dodger:~⟫ dig +noall +answer -x 10.0.0.129 @10.0.0.1 129.0.0.10.in-addr.arpa. 300IN PTR devoted-minute.maas. graham@dodger:~⟫ dig +noall +answer -x 10.0.0.100 @10.0.0.1 100.0.0.10.in-addr.arpa. 300IN PTR no-name-yet-100.maas. So, now all we need to do is have the DNSReverseZoneConfig add this for the dynamic range (I say all we need to do; obviously that's 1 task, but I'll divide it up in the morning). -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+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 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
I think this will work for IPv6 too, but as Kiko pointed out on IRC so will wildcards — the main reason I'd like to stick with $GENERATE for both is that it's one less bit of code to write ;) -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
On 22 October 2014 23:19, Gavin Panella gavin.pane...@canonical.com wrote: On 22 October 2014 22:03, Graham Binns graham.bi...@canonical.com wrote: This works perfectly: Awesome, that's great. Sort of brain-dump follows: How does this work for networks that don't line up with IPv4 octets? For example, for a dynamic range that covers 192.168.0.0/23, would we need to write the following? $GENERATE 1-254 $.0.168.192.in-addr.arpa. IN PTR no-name-yet-$.maas. $GENERATE 1-254 $.1.168.192.in-addr.arpa. IN PTR no-name-yet-$.maas. A /16 would need 256 lines. If I'm reading [1] right (and I may not be; it's late), we could do something like this: $GENERATE 1-254 $.$.0.10.in-addr.arpa. IN PTR no-name-yet-$.$.maas. But a quick check of that on my local MAAS suggests it doesn't work. I'll dig further tomorrow. Is this expanded macro-like within BIND, or is it compiled into a rule? It may make a difference to performance. AFAICT, it's expanded rather than compiled into a rule. I assume we'll do this only for IPv4? If it's compiled to a rule, we /could/ do it for IPv6 too, but that may be a slope down which we don't want to slip. Ultimately we want to steer people towards reserving IP addresses via MAAS's API. True. That said, if we fix this for v6 too it means that some very nasty hacks in charms can be canned, and that's not a terrible thing for our users. If it's easy to do, I say we might as well be consistent. If v6 causes (as I suspect it will) considerable headaches here, then we'll stick with v4 and push for everyone to use APIs as they should be doing. Is this enough to satisfy RabbitMQ? Some services like to make sure that they can round-trip through DNS, i.e. that the PTR record resolves to a name that then resolves back to the starting address. I haven't checked that out yet, but it's a good point. We could always use $GENERATE to generate the forward zone too, though, if your first point doesn't make that entirely onerous. We could choose the prefix to encourage people to reserve addresses. For example, dynamic-$, anon-$, temporary-$, or do-not-use-$, in order of severity. Unfortunately this is bikeshed territory, so I'm going to put myself out of the running by voting for do-not-rely-on-this-you-get-to-keep-the-pieces-and-give-me-one-million-dollars-$. use-this-at-your-peril-$.maas. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
On 22 October 2014 23:56, Graham Binns graham.bi...@canonical.com wrote: $GENERATE 1-254 $.$.0.10.in-addr.arpa. IN PTR no-name-yet-$.$.maas. But a quick check of that on my local MAAS suggests it doesn't work. I'll dig further tomorrow. Nope, scratch that, it works fine. Well, named-checkzone generates a perfectly valid set of rules, but strangely the reverse lookup itself doesn't work. Definitely more poking to be done on the morrow. For a /23 (or some other such fun thing), yes, I think we'd have to write $GENERATE 1-254 $.0.168.192.in-addr.arpa. IN PTR no-name-yet-$.maas. $GENERATE 1-254 $.1.168.192.in-addr.arpa. IN PTR no-name-yet-$.maas. Again. More `dig`ing (geddit?) tomorrow. -- 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/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+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 1379144] Re: maas-proxy package won't install when upgrading from older version
maas-proxy installs *fine* from a PPA — but you have to install it manually; it's not installed by default on upgrade from 1.5, so we should add something to the release notes to explain that. ** Changed in: maas (Ubuntu) Status: Confirmed = Invalid ** Changed in: maas Status: Triaged = Invalid -- 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/1379144 Title: maas-proxy package won't install when upgrading from older version To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1379144/+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 1355680] Re: MAAS upgrade struggles with BIND
** Also affects: maas (Ubuntu) Importance: Undecided Status: New ** Changed in: maas Status: New = Invalid -- 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/1355680 Title: MAAS upgrade struggles with BIND To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1355680/+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 1310846] Re: amt template gives up way too easily
** Branch linked: lp:~gmb/maas/dustins-patch -- 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/1310846 Title: amt template gives up way too easily To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1310846/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1305839] Re: FFe: Support for Third Party Driver Installation
If you land code for this feature without tests then *please* file a bug (tagged tech-debt) and let us on the MAAS team know so that we can either write the tests or help you write the tests. If you don't file a bug, chances are it's going to get forgotten about. I've already filed bug 1307906 for adding tests for the web UI warning; it's not a big change and I'll take care of adding the tests today. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1246236] Re: pxe boot from maas fails due to time out
On 14 March 2014 14:43, Adam Collard adam.coll...@canonical.com wrote: So in my case, the problem was PEBKAC and networking. Specifically I had two interfaces on my MAAS server that were connected to the same network, both had equally weighted routes to the gateway. Only one of them was configured in MAAS for the cluster controller. It was (seemingly) by chance that the second NIC was the one that the other nodes were trying to TFTP off of. It'd be lovely if MAAS would report this kind of stuff... Hey, I can ping myself... That's not good... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1246236 Title: pxe boot from maas fails due to time out To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1246236/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 972254] Re: vmtoolsd crashed with SIGSEGV in SmcCloseConnection()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/972254 Title: vmtoolsd crashed with SIGSEGV in SmcCloseConnection() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/972254/+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
