[01:11] <mup> Bug #1481992 opened: Upgrade of grub-pc during install fails <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1481992>
[04:18] <mup> Bug #1397952 changed: DNS breaks for multihomed host <canonical-bootstack> <canonical-is> <MAAS:Expired> <https://launchpad.net/bugs/1397952>
[13:12] <jogarret6204> Hi folks. i'm having trouble getting maas 1.8 to work with 1404.  does this combination work, or should I back down to something in 1.7?
[13:13] <jogarret6204> can't provision VMs.  can't bootstrap juju
[13:13] <jogarret6204> https://bugs.launchpad.net/maas/+bug/1481970
[13:37] <roaksoax> jogarret6204: is maas-dhcpd running?
[13:37] <roaksoax> jogarret6204: can you test sudo add-apt-repository ppa:maas-maintainers/experimental
[13:37] <roaksoax> jogarret6204: and then sudo apt-get update && sudo apt-get dist-upgrade -> to upgrade MAAS
[13:37] <jogarret6204> trying now
[13:38] <roaksoax> jogarret6204: this is weirD:
[13:38] <roaksoax>  provisioningserver.service_monitor.UnknownServiceError: 'maas-dhcpd' is unknown to upstart.
[13:38] <roaksoax> if it is maas on trusty, i wonder why that would be unknown to upstart
[13:39] <jogarret6204> saw soemthing in release notes about transitioning to systemd...  was wondering if I was caught in transition phase
[13:39] <jogarret6204> ..by using 1.8 on trusty..
[13:40] <roaksoax> jogarret6204: can you show me your sudoers ?
[13:40] <roaksoax> jogarret6204: /etc/sudoers.d/99-maas-sudoers
[13:40] <roaksoax>  ?
[13:41] <jogarret6204> maas ALL= NOPASSWD: /usr/sbin/service maas-dhcpd start
[13:41] <jogarret6204> its about 20 lines - where should I post it?
[13:42] <roaksoax> jogarret6204: pastebin ?
[13:42] <roaksoax> jogarret6204: http://paste.ubuntu.com/12013755/
[13:42] <roaksoax> jogarret6204: does it look like that?
[13:43] <jogarret6204> yes - identical...  interesting that all three of these show up in logs asn not recognized by upstart
[13:44] <jogarret6204> Aug  6 09:42:54 maas maas.service_monitor: [ERROR] While monitoring service 'tgt' an error was encountered: 'tgt' is unknown to upstart.
[13:44] <roaksoax> jogarret6204: are you running on trusty with systemd?
[13:45] <roaksoax> jogarret6204: by installing 1.8.1 no fix either?
[13:45] <jogarret6204> idk how can I tell?  I'm a network guy.  just learning linux
[13:45] <roaksoax> jogarret6204: sudo service maas-dhcpd status ?
[13:45] <roaksoax> ls /var/lib/systemd ?
[13:45] <roaksoax> blake_r_: https://bugs.launchpad.net/maas/+bug/1481970
[13:45] <jogarret6204> oh - I know that service is running, yes
[13:46] <jogarret6204> now sure how to tell if I am running systemd
[13:47] <roaksoax> jogarret6204: ls /var/lib/systemd ?
[13:48] <jogarret6204> think I am running it
[13:48] <jogarret6204> http://pastebin.com/m6SRBwAu
[13:48] <roaksoax> jogarret6204: nope you are not
[13:49] <jogarret6204> no?  what is the indicator?
[13:49] <roaksoax> jogarret6204: /lib/systemd/systemd
[13:54] <blake_r_> jogarret6204: does /etc/init/maas-dhcpd.conf exist?
[13:56] <jogarret6204> will check - restarting now.  assume it is because I provisioned 10 bare-metal machinse yesterday.. oever with the failures today, mahine gets IP, then gives it back before failing
[13:57] <jogarret6204> yes.  exists.  interesting that you ask, because I rebuilt this entire machine yesterday because maas-dhcp process was not starting, /maas/dhcpd.copnf fiel was not getting created was in the logs
[13:57] <jogarret6204> but on this rebuild the maas-dhcp is starting ok
[14:01] <jogarret6204> same fail as the bug with version 1.8
[14:01] <jogarret6204> UnhandledCommand: ('UNHANDLED', 'Unknown Error [maas:pid=973:cmd=RemoveHostMaps:ask=18]')
[14:01] <jogarret6204> maas-dhcpd.conf file does exist
[14:02] <blake_r_> jogarret6204: can you do "sudo service maas-dhcpd status"
[14:02] <blake_r_> jogarret6204: and provide the output
[14:03] <jogarret6204> maas-dhcpd start/running, process 1656
[14:04] <mup> Bug #1432666 changed: [FFe] New upstream release 1.8.0 <upgrade-software-version> <maas (Ubuntu):Fix Released> <https://launchpad.net/bugs/1432666>
[14:07] <blake_r_> jogarret6204: wierd
[14:07] <jogarret6204> added the new clusterd trace tothe bug, but line numbers were the same
[14:07] <blake_r_> jogarret6204: ah check your sudoers
[14:07] <blake_r_> jogarret6204: /etc/sudoers.d/maas
[14:07] <blake_r_> jogarret6204: what is the content of that?
[14:10] <jogarret6204> is is same as roaksoax had posted earlier
[14:10] <jogarret6204> http://paste.ubuntu.com/12013755/
[14:10] <jogarret6204> one thing my be dofferent on my system
[14:10] <jogarret6204> I have libvirt and using kvm on this machine to make my VM for juju to use for deployment
[14:11] <jogarret6204> so I added a maas user myself, wiht a password.
[14:11] <jogarret6204> would that conflict at all here?  since I see this maas user being used a lot
[14:11] <jogarret6204> was adding my maas user to libvirt for power control of the VM
[14:43] <jogarret6204> @blake_r_ - any other ideas?  or should I back down into 1.7? I need to get this environment up today. I do appreciate the help from both you and roalksoax
[14:43] <blake_r_> jogarret6204: is the maas user part of the maas group?
[14:46] <jogarret6204> i was alloweed to add it so I assume not.
[14:46] <jogarret6204> retrying a provision after adding  - no dice.,  same exceptions and fail
[14:48] <blake_r_> jogarret6204: you will need to restart the system
[14:49] <jogarret6204> k - restarting
[15:01] <jogarret6204> failed again.  also GUI for nodes hangs with "connecting" status.  restarting one more time
[15:01] <jogarret6204> other gui screens avaialable at the time..  just the MAAS/#/nodes hangs at "connecting"
[15:05] <jogarret6204> sorry - browser issue.  works fin in chrime.  IE is "connecting"
[15:14] <blake_r_> jogarret6204: IE does not support websockets
[15:14] <blake_r_> jogarret6204: so that didn't work?
[15:14] <jogarret6204> nope.  just tried again
[15:14] <blake_r_> jogarret6204: you have something not configured correctly since you created the maas user manually
[15:15] <blake_r_> jogarret6204: the maas user needs to be able to use sudo for those commands
[15:15] <blake_r_> jogarret6204: try this "sudo -u maas -H server maas-dhcpd status"
[15:15] <blake_r_> jogarret6204: if that fails then your maas user is incorrect
[15:18] <jogarret6204> that works
[15:18] <jogarret6204> but I do see issues in syslog
[15:19] <jogarret6204> maas sudo: pam_unix(sudo:auth): auth could not identify password for [maas]
[15:21] <blake_r_> jogarret6204: maas should require no password to execute that command
[15:21] <blake_r_> jogarret6204: something is incorrect with your maas user and sudoers
[15:31] <jogarret6204> I think you got it!  changed visudo from:  maas ALL=(ALL)  ALL  to maas ALL=(ALL) NOPASSWD: ALL
[15:32] <jogarret6204> juju is bootstrapping
[15:32] <blake_r_> jogarret6204: awesome!
[15:32] <blake_r_> jogarret6204: glad you figured it out
[15:32] <blake_r_> jogarret6204: let me know if you have any more questions or run into any more issues
[15:32] <jogarret6204> yep.  all me.  :-)  - Your helpis much appreciated!
[15:33] <jogarret6204> roaksoax thanks to you as well.
[15:33] <roaksoax> jogarret6204: was this a clean systme?
[15:33] <roaksoax> or what changed that?
[15:33] <blake_r_> roaksoax: no he created the maas user manually
[15:34] <blake_r_> roaksoax: it was part of the maas user group, and he made changes manually
[15:34] <roaksoax> blake_r_: gotcha!
[15:34] <jogarret6204> it was a clean build, then updated.  Added libvirt, added maas user when adding libvirt for power control
[15:35] <jogarret6204> some internal notes I had using maas as the virsh user...
[15:38] <mup> Bug #1481970 changed: 'maas-dhcpd' is unknown to upstart. <MAAS:Invalid> <https://launchpad.net/bugs/1481970>
[21:09] <mup> Bug #1455770 changed: 100 GB disk shows as 1 in GUI <apport-collected> <sts> <tests> <third-party-packages> <trusty> <MAAS:Fix Released> <MAAS 1.7:Won't Fix> <https://launchpad.net/bugs/1455770>
[21:30] <mup> Bug #1482385 opened: boot-sources disappear after import <cisco> <landscape> <MAAS:New> <https://launchpad.net/bugs/1482385>
[21:33] <mup> Bug #1482385 changed: boot-sources disappear after import <cisco> <landscape> <MAAS:New> <https://launchpad.net/bugs/1482385>
[21:39] <mup> Bug #1482385 opened: boot-sources disappear after import <cisco> <landscape> <MAAS:New> <https://launchpad.net/bugs/1482385>
[22:33] <mup> Bug #1482405 opened: Unhandled failure dispatching AMPQ command <oil> <MAAS:New> <https://launchpad.net/bugs/1482405>
[22:36] <mup> Bug #1482405 changed: Unhandled failure dispatching AMPQ command <oil> <MAAS:New> <https://launchpad.net/bugs/1482405>
[22:39] <mup> Bug #1482405 opened: Unhandled failure dispatching AMPQ command <oil> <MAAS:New> <https://launchpad.net/bugs/1482405>