** 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
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
** 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.
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
** 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
** 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.
** 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
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/
-
** 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
*** 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
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
(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
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
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
://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
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
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
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
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
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:
** 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
** 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
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
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
** 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
25 matches
Mail list logo
