[Bug 1267913] Re: juju relation-list doesn't report full units list when unit is down
I'm closing this WONTFIX and have opened lp:1312173 to track readiness- reporting. ** Changed in: juju-core Status: Triaged = Won't Fix ** Changed in: juju-core Milestone: 1.20.0 = None ** Changed in: juju-core (Ubuntu) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1267913 Title: juju relation-list doesn't report full units list when unit is down To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1267913/+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 1267913] Re: juju relation-list doesn't report full units list when unit is down
To be clear: none of this is unexpected (apart from the distinct agent- state issue noted by jamespage that looks like lp:1205451). Juju communicates state changes to units as a series of single-change deltas, effectively; when a new unit comes up in a relation with several others, it will first see 0, then 1, then 2, then... related units 00 and so, really, this bug reduces to when I tell juju there's an error, it acts like there's an error, and that's a straight-up WONTFIX in juju-core. BUT if you *didn't* return an error in that situation, and you really were in a temporarily failed active/active configuration, you'd also have problems, because you can't reasonably configure and start that unit without splitting the service's brain. We can mitigate this situation in a number of ways: * we could restore the pyjuju behaviour, and just not inform you of units that are not really present. This won't work, because you'll just configure in standalone mode, and thus split-brain your intended active/active deployment. * we could expose some independent mechanism by which a unit could report whether it's actually working or not; this would allow you to leave rabbit unconfigured and exit the hook without error, having made sure to set the not actually working flag. This'd (1) give users a way to observe this condition from outside, and (2) allow the unit to recover once more units came online (by having set the not working flag, rather than setting a unit error state). * we could add new hooks: let's strawman name-relation-idle, which would fire whenever one of the named relation's hook queues emptied. This would let you defer *all* relation setup work until the whole picture was available to you -- at the cost of maybe waiting a long time before it actually ran -- or at least to let you avoid putting the unit in an error state before you're really sure it's in one (because you always know you'll have at least one more hook in which to correct yourself. Both the second and third options have some glimmers of value to them, but even together I'm not sure they're a complete solution. I'd like to hear your thoughts. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1267913 Title: juju relation-list doesn't report full units list when unit is down To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1267913/+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 1208430] Re: mongodb runs as root user
Nate, I think this is *very* closely related to what you're working on right now -- would you roll this into your pipeline please? ** Changed in: juju-core Assignee: (unassigned) = Nate Finch (natefinch) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1208430 Title: mongodb runs as root user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1208430/+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 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
** Changed in: juju-core Milestone: None = 1.17.1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1248283 Title: Juju deploy of Charm in MAAS fails because dbus fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1248283/+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 1229275] Re: juju destroy-environment also destroys nodes that are not controlled by juju
Looks like we never added anything to tag the machines with their environment. Implementation note: *please* tag with environment UUID, not environment name (names are not globally unique, and environments will be referencing one another one day: treating the name as anything other than an alias is counterproductive). ** Changed in: maas (Ubuntu) Status: New = Triaged ** Changed in: maas (Ubuntu) Importance: Undecided = Critical -- 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/1229275 Title: juju destroy-environment also destroys nodes that are not controlled by juju To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1229275/+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 1183129] Re: 'juju status' difficult to read and provides unneccessary information
** Changed in: juju-core Status: New = Triaged ** Changed in: juju-core Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1183129 Title: 'juju status' difficult to read and provides unneccessary information To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1183129/+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 1183109] Re: 'juju destroy-environment' missing from 'juju help'
It's missing from the basic commands list, but is listed in `juju help commands` (referenced in the default help) and described in `juju help destroy-environment`. What's the rationale for adding destroy-environment specifically to the most-important-commands list? If we add everything, it becomes a somewhat unhelpful firehose -- not quite as bad as bzr would be, but still not very pleasant -- and it seems to us that the bzr model is actually helpful and worth following. ** Changed in: juju-core Status: New = Opinion -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1183109 Title: 'juju destroy-environment' missing from 'juju help' To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1183109/+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 1200878] Re: Upgrade breaks existing pyjuju deployment
Closing in juju-core: lp:1220260 should cover what can be done to resolve it. ** Changed in: juju-core (Ubuntu) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1200878 Title: Upgrade breaks existing pyjuju deployment To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1200878/+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 1200878] Re: Upgrade breaks existing pyjuju deployment
** Changed in: juju-core Status: New = Triaged ** Changed in: juju-core Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1200878 Title: Upgrade breaks existing pyjuju deployment To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1200878/+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 1182898] Re: Please support `juju --version`
** Changed in: juju-core Status: New = Triaged ** Changed in: juju-core Importance: Undecided = Medium ** Tags added: bitesize -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1182898 Title: Please support `juju --version` To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1182898/+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 1182902] Re: juju help does not expose 'version' option
** Changed in: juju-core Status: New = Triaged ** Changed in: juju-core Importance: Undecided = Medium ** Tags added: bitesize -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1182902 Title: juju help does not expose 'version' option To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1182902/+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 1182901] Re: juju help does not expose version number
** Tags added: bitesize -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1182901 Title: juju help does not expose version number To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1182901/+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 1182901] Re: juju help does not expose version number
** Changed in: juju-core Status: New = Triaged ** Changed in: juju-core Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1182901 Title: juju help does not expose version number To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1182901/+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 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think...
** Changed in: juju-core 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/1069570 Title: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think... To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1069570/+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 1078213] Re: juju-machine-agent.log/logs are not logrotated
We clearly should rotate logs, but the urgency has gone down since we made some changes to what we log in the course of initial juju-core scale testing. ** Changed in: juju-core Status: New = Triaged ** Changed in: juju-core Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078213 Title: juju-machine-agent.log/logs are not logrotated To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1078213/+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 955576] Re: 'local:' services not started on reboot
Just a note: the local storage-server and machine-agent are now upstartified; the missing pieces are zookeeper and the lxc containers, neither of which should be tricky to fix. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/955576 Title: 'local:' services not started on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/955576/+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
