BOunce your nodes. I was stuck on this for almost a week. Your servers
aren't responding to the Wake On LAN or whatever remotemethod you
are trying to use to wake up the servers.
After you setup your MAAS controller, you power-on your servers. If
DHCP/DNS is setup right, they PXE boot and load a
BOunce your nodes. I was stuck on this for almost a week. Your servers
aren't responding to the Wake On LAN or whatever remotemethod you
are trying to use to wake up the servers.
After you setup your MAAS controller, you power-on your servers. If
DHCP/DNS is setup right, they PXE boot and load a
I am having this same issue. I set up a box as a maas server and could
not get any of the vm nodes on Virtual box to finish commissoning so i
set up another box on a junker comp and started from scratch. Out of
three tests on VB they all subscribed and after acceptance finished the
enrollment
I am having this same issue. I set up a box as a maas server and could
not get any of the vm nodes on Virtual box to finish commissoning so i
set up another box on a junker comp and started from scratch. Out of
three tests on VB they all subscribed and after acceptance finished the
enrollment
I am running into the same issue. My MAAS and nodes are in a virtual
environment for testing. Attached is a screenshot of my VM after PXE
booting which shows the same init: cloud-init-nonet main process (###)
killed by TERM signal error that Andrew mentioned.
** Attachment added:
I am running into the same issue. My MAAS and nodes are in a virtual
environment for testing. Attached is a screenshot of my VM after PXE
booting which shows the same init: cloud-init-nonet main process (###)
killed by TERM signal error that Andrew mentioned.
** Attachment added:
#5
I too met this just one node. expecting solution ~
--
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/992075
Title:
Commissioning status persists with cloud-init 0.6.3-0ubuntu1
To
Hi,
I have only one node in state Commissionning.
I am getting the following error :
The provisioning service encountered a problem with the Cobbler server,
fault code 99: dns-name duplicated: cloud-jpd-5 If the error message is
not clear, you may need to check the Cobbler logs in
#5
I too met this just one node. expecting solution ~
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992075
Title:
Commissioning status persists with cloud-init 0.6.3-0ubuntu1
To manage
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
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
I too am seeing this bug and am interested in seeing a resolution. It
should be noted I am using virtual adapters with and I am running this
in a test environment with virtual machines, yet I am seeing the same
symptoms. Do we have any updates on a possible fix?
--
You received this bug
I too am seeing this bug and am interested in seeing a resolution. It
should be noted I am using virtual adapters with and I am running this
in a test environment with virtual machines, yet I am seeing the same
symptoms. Do we have any updates on a possible fix?
--
You received this bug
I am also using cloud-init 0.6.3-0ubuntu1.
At first I did see the bug at
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/981845 and as per my
comment there, did have the network cables inadvertantly switched, no
PXE boot. Switching the cables and re-booting the node had no effect on
the
I am also using cloud-init 0.6.3-0ubuntu1.
At first I did see the bug at
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/981845 and as per my
comment there, did have the network cables inadvertantly switched, no
PXE boot. Switching the cables and re-booting the node had no effect on
the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New = Confirmed
--
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/992075
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992075
Title:
** Description changed:
Hi guys,
I've been through this issue
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/981845
I followed the instruction of the comment #2 but the new version of
cloud-init didn't solve my issue.
I'm running 12.04 final release and up to date. (apt-get
** Description changed:
Hi guys,
I've been through this issue
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/981845
I followed the instruction of the comment #2 but the new version of
cloud-init didn't solve my issue.
I'm running 12.04 final release and up to date. (apt-get
19 matches
Mail list logo
