Thank you for taking the time to report this bug.
MAAS in precise (-updates) no longer uses cobbler, for this reason I'm
marking this bug as won't fix. If you feel this bug is still present,
please re-open the bug.
** Changed in: maas (Ubuntu)
Status: Confirmed => Fix Released
** Changed
** Also affects: maas (Ubuntu Precise)
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/989355
Title:
Unable to create Node: timed out
To manage notificatio
This is fixed in trunk with the removal of Cobbler
** Changed in: maas
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989355
Title:
Unable to create Node: time
To find some way to get MAAS to wait longer, I I initially looked in
"/usr/share/pyshared/cobbler/modules/sync_post_restart_services.py" and
found code that looks like it uses subprocess_sp() from
"/usr/share/pyshared/cobbler/utils.py" to run "service dnsmasq restart".
Perhaps the code for restarti
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.
Thanks Julian for giving us some insight into the cause of this issue!
If you have some insight into the command sequence MAAS is running then
I hope you can help identify a workaround to enable adding nodes or
create a mini-Howto manually remove a partially added node (from
Cobbler, dnsmasq, etc m
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989355
Title:
Unable to create Node: timed out
To manag
Julian, I see the same delay in the cobbler log, however it is 27
seconds in my case. There is nothing else running on the system and I
have already run maas-import-isos. I am running this in a VM at the
moment to experiment before I do a real hardware install. The VM has
access to 8 cores and the
Julian, this is a fresh install maas-servers only. I reinstalled the
server and I succesfully added the first node, but when tried the next
one, again the time out error. I do this *after* the maas-import-isos.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
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.
-
Same problem here. I still cannot add my first node.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989355
Title:
Unable to create Node: timed out
To manage notifications about this bug go to:
https
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 => Triag
Same behaviour occurs when I tried to re-adding the node.
How can I speed things up? The dnsmasq is working well by doing dhcp and
resolving names.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989355
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 pserv/
15 matches
Mail list logo
