Anyone who is affected, please can you paste all the information
requested in #15. Please also say which versions of every package you
are using.
Robie - it could be a bug that's fixed in the code awaiting SRU. We are
not testing older packages in the lab.
** Changed in: maas
Status:
** Changed in: maas
Status: New = Triaged
** Changed in: maas
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/1103195
Title:
MAAS WebUI
This looks like it's BIOS-dependent then, which explains why some of us
weren't able to recreate it.
** Changed in: maas
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Marking the maas task invalid as it's fixed in packaging.
** Changed in: maas (Ubuntu)
Status: Confirmed = In Progress
** Changed in: maas
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
The commit message on the revno (from 2012-10-03) that added
manage_etc_hosts says:
--
specify 'preserve_sources_list' to cloud-init in install preseed
This moves the cloud-init/local-cloud-config out of the preseed
explicitly
and instead renders it in
I can remove it, but I don't know enough about cloud-init to know what,
if anything, it will break. So if someone can confirm it's ok I'll do
it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
In that case, this bug is not a MAAS bug, it's a packaging bug.
** Changed in: maas
Status: New = Invalid
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
I think we just need to move the patch I did for the Django package
right into the maas package (with file path changes etc etc)
--
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/1130232
Hey Andres,
Upstream doesn't have packaging really. The packaging branch that's
there belongs to Ubuntu, it just happens to be owned by Maas
maintainers.
Cheers
Andres Rodriguez andres...@ubuntu-pe.org wrote:
Hi Julian,
This bug does not belong to the packaging nor MAAS *in* Ubuntu, because
On Wednesday 20 Feb 2013 19:54:21 Raphaël Badin wrote:
On 02/20/2013 08:32 PM, Andres Rodriguez wrote:
Oh btw... we need to make sure that this doesn't provide any regression
or upgrade failures from those who have been using MAAS from ppa:maas-
maintainers/stable.
Good point, that's
Public bug reported:
If LC_ALL is not set (which seems to be the default on a few server
installations I've done now), mid way through installing, you get this
backtrace and then the installation just hangs. You can ctrl-c out of
it but the package is left half configured.
Traceback (most
Your LC_ALL must be set then.
--
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/1134036
Title:
Package install hangs if LC_ALL is not set
To manage notifications about this bug go to:
The links aren't that useful because it's showing the post-facto state.
If you could deliberately unset LC_ALL and then install the packages
from scratch it would be closer to my own experience.
If it ends up installing ok for you, then there's some deep voodoo at
work here! It's very repeatable
On 01/03/13 09:47, Dave Walker wrote:
We have seen this previously on a bunch of packages, where the locale
isn't configured. We particularly saw this on cloud images, which
wouldn't have an understanding of the required locale until first
login ( it might not be installed.)
Personally, i
On 01/03/13 19:12, Raphaël Badin wrote:
The links aren't that useful because it's showing the post-facto state. If
you could deliberately unset LC_ALL and then install the
packages from scratch it would be closer to my own experience.
That's what I did and it seems fine (easy to recreate
Maas returns a 409 CONFLICT when there's no node available. This is
purely a Juju problem.
** Changed in: maas
Status: New = Invalid
** Changed in: maas (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: maas
Status: New = Triaged
--
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/1154803
Title:
Constraints prevents the allocation of nodes if they are equal to the
** Changed in: maas
Status: New = Triaged
** Changed in: maas
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-tx-tftp in Ubuntu.
https://bugs.launchpad.net/bugs/116
Title:
HP
** Also affects: maas/1.2
Importance: Undecided
Status: New
** Changed in: maas/1.2
Status: New = Fix Committed
** Changed in: maas/1.2
Importance: Undecided = Critical
** Changed in: maas/1.2
Milestone: None = 12.10-stabilization
** No longer affects: maas/1.2
--
You
Please note that when this upgrade runs, it will render some existing
installations unusable until they configure the cluster controller.
Previously, MAAS depended on external configuration of DHCP etc via
Cobbler or manually. Now that Cobbler has gone, it must be configured
in MAAS where it was
I am largely unfamiliar with the Ubuntu SRU process so I'm contributing
where I can here, please excuse my lack of understanding. I am upstream
in this case so I'll write from that point of view.
The existing 12.04 package is already *broken* which is the whole reason
for this SRU. It was
Yep - some of the templates support it (POWER_TEMPLATES_DIR) but not
all. We need to extend the configuration of location to the others.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Please don't ping pong the bug status
I didn't touch the bug status.
It's my understanding from reading the bug, that if users that have already
manually configured things once and have a working system install the new
package, things will stop working until they do additional manual
** Changed in: maas
Status: New = Triaged
** Changed in: maas
Importance: Undecided = High
--
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/1172336
Title:
MAAS server
On 16/05/13 01:57, Robie Basak wrote:
Personally, i feel the bug is the locale not being configured properly
on te platform.. but I appreciate the packaging should handle this
with more grace.
If LC_* isn't set, then AIUI locale C is implied; this should not need
any further configuration
Looking at the code path, it's either doing commissioning or xinstall.
In this case, it should be using the architecture defined on the node
itself. Are you sure it's set as amd64?
The only time i386 is required is when the client PXE implementation
doesn't supply an arch and we fall back to
Are you sure this is not bug 1171418 ?
Juju acquires and starts very quickly and there's never been a problem
with it.
** Changed in: maas
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
*** This bug is a duplicate of bug 1064212 ***
https://bugs.launchpad.net/bugs/1064212
** This bug has been marked a duplicate of bug 1064212
If a machine is booted manually when in status declared, TFTP server
tracebacks
--
You received this bug notification because you are a member of
On Monday 20 May 2013 12:58:13 you wrote:
node in this case was most definitely known to maas and set to
amd64/generic.
It might be something that broke recently then :(
I've been installing amd64 on my own nodes without downloading i386 images.
I'll try to re-create.
--
You received this
Urgh this is nasty.
We have plans to completely re-write the importer script in Python in
the near future. That would be an ideal time to address any of these
problems, so if you can firm up a plan and document it here, we'll
implement it.
Please don't write any more shell, or changes to shell.
** Changed in: maas
Status: New = In Progress
** Changed in: maas
Assignee: (unassigned) = Andres Rodriguez (andreserl)
** Changed in: maas
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: maas
Status: New = Triaged
** Changed in: maas
Importance: Undecided = High
--
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/1182980
Title:
global parameters
** Changed in: maas
Status: Fix Committed = Fix Released
--
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/1154142
Title:
When a file is requested via the API, the returned JSON
** Changed in: maas
Status: Fix Committed = Fix Released
--
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/1131418
Title:
Nodes don't go to ready, after commissioning they get a
I suspect this is caused by task messages getting generated before a
celeryd listener is connected/registered. I saw it once myself (but
only once).
** Changed in: maas
Status: New = Triaged
** Changed in: maas
Importance: High = Critical
--
You received this bug notification
** 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/1171696
** Changed in: maas
Status: Fix Committed = Fix Released
--
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/1182978
Title:
MAAS will fail to set the correct user if a previous
I am closing the maas task because a completely updated version of maas
is about to be SRUed which will be likely to make this go away.
** Changed in: maas
Status: Incomplete = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: maas
Status: Incomplete = Triaged
** Changed in: maas
Importance: Undecided = Low
** Tags added: feature security
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Changed in: maas
Status: Fix Committed = Fix Released
--
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/1171418
Title:
MAAS fails to power up machines when trying to install
No, I never saw this sort of message at all. I concur with falling
back to a C locale though, because as it stands package installation of
Postgres just *hangs*.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Changed in: maas
Status: Triaged = In Progress
** Changed in: maas
Assignee: (unassigned) = Julian Edwards (julian-edwards)
--
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
** Changed in: maas/1.2
Milestone: 12.10-stabilization = None
** Changed in: maas
Status: Triaged = Fix Released
** Changed in: maas/1.2
Assignee: Andres Rodriguez (andreserl) = Julian Edwards (julian-edwards)
** Changed in: maas/1.2
Status: Triaged = In Progress
--
You
** Branch linked: lp:~julian-edwards/maas/1.2-ipmi-backport
** Changed in: maas/1.2
Status: In Progress = Fix Committed
--
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/1064527
** Changed in: maas
Status: Fix Committed = Fix Released
--
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/1182980
Title:
global parameters do not apply to enlistment
To manage
** Tags added: api cli
** Changed in: maas
Status: New = Triaged
** Changed in: maas
Importance: Undecided = High
** Tags added: trivial
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
It's clear that PG has a packaging bug, it should not hang the postinst
script because of an invalid locale. That bug ought to be triaged and
this can be a dupe of it.
@Robie
Yes I see a /etc/profile.d/Z99-cloud-locale-test.sh but not the skip file. I
can recreate this trivially with new
** Changed in: maas
Status: Triaged = Fix Released
** Also affects: maas/1.3
Importance: Undecided
Status: New
** Changed in: maas/1.3
Status: New = Triaged
** Changed in: maas/1.3
Importance: Undecided = Critical
--
You received this bug notification because you
** Changed in: maas/1.3
Status: Triaged = In Progress
** Changed in: maas/1.3
Assignee: (unassigned) = Julian Edwards (julian-edwards)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https
** Changed in: maas/1.3
Status: In Progress = Fix Committed
--
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
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1081701
Title:
The metadata address mentioned in the preseed is
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1086162
Title:
IPMI based power management default to IPMI 1.5 based
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1070774
Title:
The hostname of a node can still be changed once the
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1081692
Title:
The value of 'next-server' in the dhcp config is
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1066929
Title:
duplicate entry added to named.conf.local on each
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/975454
Title:
complete documentation and man pages
To manage
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1068843
Title:
[SRU] maas-cluster-controller doesn't have images for
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1069734
Title:
Filestorage is unique to each appserver instance
To
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/994887
Title:
Nodes listing does not support sorting
To manage
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1059645
Title:
URI in API description wrong when accessing machine
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1066775
Title:
Main page slow to load with many nodes
To manage
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1070775
Title:
The zone name (attached to a cluster controller) can
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1070765
Title:
DNS forward zone ends up with nonsensical entries
To
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1070522
Title:
maas-cli nodes new incomplete documentation
To
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1064224
Title:
IPMI detection ends up with power_address of 0.0.0.0
** Changed in: maas
Milestone: None = 13.10
--
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/1185160
Title:
no way to see what user has a node allocated
To manage notifications
** Tags added: trivial
** Changed in: maas
Milestone: None = 13.10
--
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/1172336
Title:
MAAS server reference to AvahiBoot wiki page that
I re-created this. It's as simple as renaming
/var/lib/maas/ephemeral/precise/ephemeral/i386/ to something else and
then trying to enlist a node. The TFTP server then tracebacks as above.
** Changed in: maas
Status: Incomplete = Triaged
** Changed in: maas
Importance: Undecided =
What this means is that the node's BIOS itself is not supplying an
architecture on the TFTP request for a pxeconfig. MAAS needs to know
what architecture it is so it can serve the right config, and if it's
not supplied it defaults, not unreasonably, to i386.
Since there's a workaround (you could
Andres, in that case does this need a MAAS bug task?
** Changed in: maas
Status: New = 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/1185261
Title:
MaaS nodes
Bryan, have you tried following the step-by-step instructions at
maas.ubuntu.com at all?
--
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/975472
Title:
add high level design document(s)
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1171418
Title:
MAAS fails to power up machines when trying to
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1131418
Title:
Nodes don't go to ready, after commissioning they get
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1154142
Title:
When a file is requested via the API, the returned
** Changed in: maas/1.2
Status: Fix Committed = Fix Released
--
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/1130232
Title:
Implement GenericIpAddressField in MAAS rather than
Sonali, that is a standard message the first time you connect to a new
host with ssh.
--
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/1015207
Title:
juju setup fails, ERROR Invalid SSH
** 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 cobbler in Ubuntu.
https://bugs.launchpad.net/bugs/979899
Packging bug - re-assigning.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Status: New = Confirmed
** Changed in: maas
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
** Changed in: maas
Status: New = Triaged
** Changed in: maas
Importance: Undecided = High
--
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/975472
Title:
add high level
This is a packaging issue - Apache handles all SSL not maas.
** 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/975462
Title:
add ability
** Changed in: maas
Status: New = Triaged
** Changed in: maas
Importance: Undecided = High
** Changed in: maas
Milestone: None = 12.04
** Changed in: maas
Milestone: 12.04 = 12.04.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
You're right, I had forgotten about those.
** Changed in: maas
Status: Invalid = Triaged
** Changed in: maas
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
The problem is that cobbler took 10 seconds to restart dnsmasq:
Thu Apr 26 21:41:10 2012 - INFO | running: service dnsmasq restart
Thu Apr 26 21:41:20 2012 - INFO | received on stdout: * Restarting DNS
forwarder and DHCP server dnsmasq
But the MAAS server has a 7 second timeout waiting for
I'm stumped as to why it takes so long, I've never seen that before.
I'll get someone else to take a look at this.
** Changed in: maas (Ubuntu)
Status: Incomplete = Confirmed
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Status: New =
Mark, do you see the same delay in the cobbler log when it's restarting
dnsmasq?
Everyone: is anything else running on your machine that would slow it
all down? maas-import-isos?
On the bright side, we are going to re-architect this to make it
asynchronous so the web app doesn't need to wait.
So cobbler is doing something weird, I will have to punt to someone who
knows it better than I.
--
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/989355
Title:
Unable to create Node:
Invalidating trunk task since I think this is just a packaging problem.
Feel free to re-open it if discovered otherwise.
** 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.
** Changed in: maas
Status: New = Triaged
** Changed in: maas
Importance: Undecided = High
** Tags added: ui
--
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/994781
Title:
I thought of something you can try - if you change the cobbler settings
to not manage dhcp and set your external dhcp up manually, it might
work. Please let me know.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
I'm sorry this is troublesome for you. I don't think we ever tested it
with having cobbler manage DHCP or dnsmasq, we just expected people to
set next-server on the existing DHCP.
For timeouts, there's a setting called PSERV_TIMEOUT which is currently
set to 7, try changing that and let me know.
Packaging bug, so re-targeting.
** 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.
*** This bug is a duplicate of bug 972829 ***
https://bugs.launchpad.net/bugs/972829
** This bug has been marked a duplicate of bug 972829
maas-server setting requires port even when using http default
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
It has /usr/sbin/maas instead of /usr/bin/maas
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
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) = Launchpad Red Squad (redsquad)
** Changed in: maas
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug assignee.
https://bugs.launchpad.net/bugs/975473
Title:
On Saturday 09 Jun 2012 04:31:51 you wrote:
Is the functionality of the shell documented anywhere? This would be
VERY useful to know. Given the gui doesn't always work the way it
should, I could see this as really good and important information.
It's not documented, it's intended as a
init: cloud-init-nonet main process (###) killed by TERM signal
is expected. Please see bug 1015223
Please also read all the FAQs and let me know if any of the suggestions help
(there are things mentioned that are not in the bug here).
https://answers.launchpad.net/maas/+faqs
--
You received
Bootstrapping is not instant, you need to wait for the master node to
install before status works.
** Changed in: maas
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
Please see the first two questions on
https://answers.launchpad.net/maas/+faqs
--
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/1015207
Title:
juju setup fails, ERROR Invalid SSH key -
That looks like a connection refused to zookeeper, nothing to do with
maas. I suspect your zk node hasn't come up properly, which might be
related to bug 992075
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
The ZK node is the first one to be booted by Juju when you run juju
bootstrap. Juju installs ZK on it.
Since ZK is not there, you have a problem at that stage. Since you
managed to log in, can you examine the cloud-init logs please? If
there's nothing sensitive in there perhaps attach to the
1 - 100 of 625 matches
Mail list logo
