[Bug 1737428] Re: VRF support to solve routing problems associated with multi-homing
BUMP! +1000 for this feature. We need vrf support in MAAS to be able to use it with in bgp/vrf stack. @dmitriis thank you for the thorough write up and detailed explanation of the problem/solution here! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737428 Title: VRF support to solve routing problems associated with multi-homing To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures
I can verify the fix works in my environment using whats in xenial- proposed http://paste.ubuntu.com/26178059/ Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737640 Title: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures
thinking this is the same bug/duplicate I'm hitting here https://bugs.launchpad.net/juju/+bug/1736022 I'm deploying a few nodes to test the fix in proposed now -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737640 Title: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649397] Re: maas-dhcpd.service won't start
@andreserl, still confused as to why I can't add DHCP to a flat network space, without applying @obecker's fix from #10? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649397 Title: maas-dhcpd.service won't start To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1649397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649397] Re: maas-dhcpd.service won't start
@andreserl, I think the problem may be partially due to the fact that we are trying to configure dhcp on a flat address space, not a vlan. Per your comments above, you only mention vlan, not flat networks, should this matter to any affect? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649397 Title: maas-dhcpd.service won't start To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1649397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649397] Re: maas-dhcpd.service won't start
@andreserl yea, I can't get dhcp to light up for the life of me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649397 Title: maas-dhcpd.service won't start To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1649397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649397] Re: maas-dhcpd.service won't start
DHCP will not start, e.g. no green light on the controller on initial install of MAAS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649397 Title: maas-dhcpd.service won't start To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1649397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602192] Re: when starting many LXD containers, they start failing to boot with "Too many open files"
@stgrabber, what's the status on this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602192 Title: when starting many LXD containers, they start failing to boot with "Too many open files" To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1602192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598354] [NEW] Need pgtune in xenial archives
Public bug reported: Pgtune for xenial coalition ** Affects: pgtune (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598354 Title: Need pgtune in xenial archives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pgtune/+bug/1598354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595052] [NEW] Feature request - `charm detach`, `charm remove`
Public bug reported: To my understanding, only additive ops are supported ... though I'm not quite sure why. Do you mind adding the capability to also remove resources and charms? ** Affects: charm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1595052 Title: Feature request - `charm detach`, `charm remove` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm/+bug/1595052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521618] Re: wrong subnet in DHCP answer when multiple networks are present
Has a fix for this been implemented? This still seems to exist in MAAS-2.0 beta6+bzr5017 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521618 Title: wrong subnet in DHCP answer when multiple networks are present To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1521618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1488594] Re: Nodes cannot boot after a storage disk replacement
I really appreciate the input everyone. I guess I was a little overwhelmed dealing with a few different issues at once I didn't mean to place the blame on MAAS. That being said, node disk replacement under the direction of MAAS is still a rugged process for me. I understand that pxelinux/bios may be the root cause of my issue ... I guess I feel like MAAS had more to do with this due to MAAS not being able to recognize new disk after replacement w/o recommissioning. I feel like despite the boot issue, I would still need to recommission and down the node for MAAS to take inventory of the new disk after a replacement. Is this being looked into for 1.9? Thanks again, James On Mon, Jan 25, 2016 at 6:41 AM, Gavin Panellawrote: > Even when a node has been deployed, the node still attempts to PXE boot > from MAAS each time it's rebooted. MAAS knows it should boot locally and > gives the following configuration to PXELINUX: > > DEFAULT local > > LABEL local > LOCALBOOT 0 > > It appears that this does not do the right thing for your hardware. Put > another way, it does not do the same thing as your machine's BIOS does > when the network is unavailable. > > I suspect this is a bug in PXELINUX and/or your hardare. There may be > something that MAAS can do to help, but I don't think it's the cause, so > I'll target this bug at PXELINUX and mark it Invalid in MAAS for now. > > > ** Also affects: syslinux (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: maas >Status: Confirmed => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1488594 > > Title: > Nodes cannot boot after a storage disk replacement > > Status in MAAS: > Invalid > Status in syslinux package in Ubuntu: > New > > Bug description: > I'm experiencing this issue when I replace any osd disk on any ceph > storage node and then reboot it. Immediatly after the node pxe boots, > the node will hang at a "booting local disk" message and fails to > timeout or boot. A work-around I've found to get a node to boot after > a storage disk replacement is to momentarilly disable maas from > managing the network after the power on of a node who's disk has been > replaced; following that, after the node pxe boot times out and it > results to booting from local disk into the os, I re-enable maas > management on that network so the node gets an ip and continues the > boot process and eventually successfully boots. > > It would be nice to get some feedback on what is going on here, and > also a best practice for what/how to proceed in the case when you need > to swap storage disks. > > Thanks! > > maas.log <-- http://paste.ubuntu.com/12193844/ > > clusterd.log <-- http://paste.ubuntu.com/12193842/ > > maas - 1.8.0+bzr4001-0ubuntu2~trusty1 > trusty - 14.04.3 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/maas/+bug/1488594/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488594 Title: Nodes cannot boot after a storage disk replacement To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1488594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488594] Re: Nodes cannot boot after a storage disk replacement
I really appreciate the input everyone. I guess I was a little overwhelmed dealing with a few different issues at once I didn't mean to place the blame on MAAS. That being said, node disk replacement under the direction of MAAS is still a rugged process for me. I understand that pxelinux/bios may be the root cause of my issue ... I guess I feel like MAAS had more to do with this due to MAAS not being able to recognize new disk after replacement w/o recommissioning. I feel like despite the boot issue, I would still need to recommission and down the node for MAAS to take inventory of the new disk after a replacement. Is this being looked into for 1.9? Thanks again, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488594 Title: Nodes cannot boot after a storage disk replacement To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1488594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528034] [NEW] Error installing wily as a vmware fusion vm or virtualbox vm on osx 10.11.1
Public bug reported: No such luck provisioning a vmware fusion or virtualbox wily vm on osx 10.11.1 errors out when trying to make disk partitions during install. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubiquity 2.21.37 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.365 Date: Sat Dec 19 16:35:40 2015 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.37 ubuntu wily ** Description changed: - No such luck provisioning a vmware fusion wily vm.errors out when - trying to make disk partitions. + No such luck provisioning a vmware fusion or virtualbox wily vm on osx + 10.11.1 errors out when trying to make disk partitions during + install. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubiquity 2.21.37 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.365 Date: Sat Dec 19 16:35:40 2015 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - Error installing wily as a vmware fusion vm on osx 10.11.1 + Error installing wily as a vmware fusion vm or virtualbox vm on osx 10.11.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528034 Title: Error installing wily as a vmware fusion vm or virtualbox vm on osx 10.11.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1528034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs