Hmm...I realize this is not a problem. I posted it in AskUbuntu and have
not heard anything. As this bug seemed very similar to what I was
experiencing, I was wondering if one of the persons who solved or know
how to solve could write a quick comment on how to do so...
IP forwardingDNS
Hmm...I realize this is not a problem. I posted it in AskUbuntu and have
not heard anything. As this bug seemed very similar to what I was
experiencing, I was wondering if one of the persons who solved or know
how to solve could write a quick comment on how to do so...
IP forwardingDNS
I am having same problems but with Ubuntu 14.04 LTS -
I have a Ubuntu MASS Server running on one node.
It has two NICs. One NIC (eth1) is connected to our organization's network. The
other NIC (eth0) is private network - to manage all the nodes in the cloud. I
am running DHCP server on eth0.
This is not a MAAS problem, you need to set up IP forwarding in your
maas server.
--
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/1237364
Title:
Commissioning with a Saucy image sets
I am having same problems but with Ubuntu 14.04 LTS -
I have a Ubuntu MASS Server running on one node.
It has two NICs. One NIC (eth1) is connected to our organization's network. The
other NIC (eth0) is private network - to manage all the nodes in the cloud. I
am running DHCP server on eth0.
This is not a MAAS problem, you need to set up IP forwarding in your
maas server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237364
Title:
Commissioning with a Saucy image sets node status to
I have a similar error, when I comission a node, I get this error:
Error output
failed [2/5] ( 00-maas-01-lshw 00-maas-02-virtuality)
I'm using Ubuntu Server 12.04.3 and Precise image for the nodes.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
@Paul: the problem you're having is that your nodes can't access the
outside world. They are thus unable to fetch the packages needed for
commissioning (see http://paste.ubuntu.com/7195406/).
Unless you changed the http_proxy config option (on the settings page —
or you can configure it using
I have a similar error, when I comission a node, I get this error:
Error output
failed [2/5] ( 00-maas-01-lshw 00-maas-02-virtuality)
I'm using Ubuntu Server 12.04.3 and Precise image for the nodes.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
@Paul: the problem you're having is that your nodes can't access the
outside world. They are thus unable to fetch the packages needed for
commissioning (see http://paste.ubuntu.com/7195406/).
Unless you changed the http_proxy config option (on the settings page —
or you can configure it using
Btw, I just found (and fixed) bug 1278895. It means that the list of
the failed scripts in the failed [3/5] … message is actually wrong:
it's the list of the scripts that didn't fail (!).
Here is the list of all the scripts that maas has:
00-maas-01-lshw
00-maas-02-virtuality
Another note: to debug commissioning problems, the quickest way is to
have a look at the output of the scripts that failed. You can't do that
with the UI right now but it's all available if you use the API/CLI:
The following CLI command :
$ maas-cli maas commissioning-results list
will spit out
Paul,
Would it be possible for you to collect console output?
On the other hand, what you could try is to obtain the output of the
scripts themselves from the database. These are in base64. Use
thefollowing command:
maas-cli username commissioning-results list
The results yields json output
Awesome, thank you Andres and Raphaël!!
Please see attachment.
Note to myself:
1. Login to the API by using the following steps:
https://maas.ubuntu.com/docs/maascli.html
2. Then run command: maas-cli maas commissioning-results list
commissioing-results.json
Best regards,
** Attachment
Another note: to debug commissioning problems, the quickest way is to
have a look at the output of the scripts that failed. You can't do that
with the UI right now but it's all available if you use the API/CLI:
The following CLI command :
$ maas-cli maas commissioning-results list
will spit out
Btw, I just found (and fixed) bug 1278895. It means that the list of
the failed scripts in the failed [3/5] … message is actually wrong:
it's the list of the scripts that didn't fail (!).
Here is the list of all the scripts that maas has:
00-maas-01-lshw
00-maas-02-virtuality
Paul,
Would it be possible for you to collect console output?
On the other hand, what you could try is to obtain the output of the
scripts themselves from the database. These are in base64. Use
thefollowing command:
maas-cli username commissioning-results list
The results yields json output
Awesome, thank you Andres and Raphaël!!
Please see attachment.
Note to myself:
1. Login to the API by using the following steps:
https://maas.ubuntu.com/docs/maascli.html
2. Then run command: maas-cli maas commissioning-results list
commissioing-results.json
Best regards,
** Attachment
Ran into similar same Error output and the node was connected to internet:
failed [2/5] ( 00-maas-01-lshw 00-maas-02-virtuality)
Some information on my configuration: The DHCP server is on a different
box and able to provide the correct ip, route, netmask, and gateway to
node.
Used the
Sorry, left out the important stuff:
Host MAAS version: 1.4+bzr1693+dfsg-0ubuntu2.2
Host OS version: ubuntu server 13.10
Host Kernel: 3.11.0-12-generic #19-Ubuntu
Node OS version: 12.04
Node Kernel version: 3.2.0-54-generic #82
Thanks again!
--
You received this bug notification because you
Paul,
Can you also please attach the output of /var/log/cloud-init.log and/or
cloud-init-output.log from the epehemeral image?
On Feb 7, 2014 7:25 PM, Paul pach...@cisco.com wrote:
Sorry, left out the important stuff:
Host MAAS version: 1.4+bzr1693+dfsg-0ubuntu2.2
Host OS version: ubuntu
Hi Andrew,
I could only find cloud-init.log under /var/log.
Please see attachment.
Thank you!
** Attachment added: cloud-int log file
https://bugs.launchpad.net/maas/+bug/1237364/+attachment/3973386/+files/cloud-init.log
--
You received this bug notification because you are a member of
Ran into similar same Error output and the node was connected to internet:
failed [2/5] ( 00-maas-01-lshw 00-maas-02-virtuality)
Some information on my configuration: The DHCP server is on a different
box and able to provide the correct ip, route, netmask, and gateway to
node.
Used the
Sorry, left out the important stuff:
Host MAAS version: 1.4+bzr1693+dfsg-0ubuntu2.2
Host OS version: ubuntu server 13.10
Host Kernel: 3.11.0-12-generic #19-Ubuntu
Node OS version: 12.04
Node Kernel version: 3.2.0-54-generic #82
Thanks again!
--
You received this bug notification because you
Paul,
Can you also please attach the output of /var/log/cloud-init.log and/or
cloud-init-output.log from the epehemeral image?
On Feb 7, 2014 7:25 PM, Paul pach...@cisco.com wrote:
Sorry, left out the important stuff:
Host MAAS version: 1.4+bzr1693+dfsg-0ubuntu2.2
Host OS version: ubuntu
Hi Andrew,
I could only find cloud-init.log under /var/log.
Please see attachment.
Thank you!
** Attachment added: cloud-int log file
https://bugs.launchpad.net/maas/+bug/1237364/+attachment/3973386/+files/cloud-init.log
--
You received this bug notification because you are a member of
We ran into this issue on 14.04.
maas version: 1.4+bzr1820+dfsg-0ubuntu1
deploy 12.04.3 images
Error output
failed [2/5] ( 00-maas-01-lshw 00-maas-02-virtuality)
list xmlns:lldp=lldp xmlns:lshw=lshw
lshw:node id=b7t6c claimed=true class=system handle=DMI:0001
lshw:descriptionDesktop
The reason for the error is because node couldn't get to the Internet.
Issue fixed by configuring the proxy to the MAAS server.
--
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/1237364
We ran into this issue on 14.04.
maas version: 1.4+bzr1820+dfsg-0ubuntu1
deploy 12.04.3 images
Error output
failed [2/5] ( 00-maas-01-lshw 00-maas-02-virtuality)
list xmlns:lldp=lldp xmlns:lshw=lshw
lshw:node id=b7t6c claimed=true class=system handle=DMI:0001
lshw:descriptionDesktop
The reason for the error is because node couldn't get to the Internet.
Issue fixed by configuring the proxy to the MAAS server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237364
Title:
** 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/1237364
Title:
Commissioning with a Saucy image sets node status to
** Changed in: maas
Status: Fix Committed = 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/1237364
Title:
Commissioning with a Saucy image sets node status to Failed tests
To
** Changed in: maas
Milestone: None = 13.10
** Changed in: maas
Status: Fix Released = 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/1237364
Title:
** Changed in: maas
Milestone: None = 13.10
** Changed in: maas
Status: Fix Released = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237364
Title:
Commissioning with a
** 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/1237364
Title:
Commissioning with a Saucy image sets node status to
** Changed in: maas
Status: Fix Committed = 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/1237364
Title:
Commissioning with a Saucy image sets node status to Failed tests
To
** Changed in: maas
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/1237364
Title:
Commissioning with a Saucy image sets node status to
** Branch linked: lp:ubuntu/saucy-proposed/maas
--
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/1237364
Title:
Commissioning with a Saucy image sets node status to Failed tests
To
This bug was fixed in the package maas - 1.4+bzr1693+dfsg-0ubuntu1
---
maas (1.4+bzr1693+dfsg-0ubuntu1) saucy; urgency=low
* New Upstream Release (LP: #1218526)
- This new upstream release contains fixes and improvements of the
features approved by the FFe above.
-
** Changed in: maas
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237364
Title:
Commissioning with a Saucy image sets node status to Failed tests
To
** Branch linked: lp:ubuntu/saucy-proposed/maas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237364
Title:
Commissioning with a Saucy image sets node status to Failed tests
To manage
This bug was fixed in the package maas - 1.4+bzr1693+dfsg-0ubuntu1
---
maas (1.4+bzr1693+dfsg-0ubuntu1) saucy; urgency=low
* New Upstream Release (LP: #1218526)
- This new upstream release contains fixes and improvements of the
features approved by the FFe above.
-
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Status: New = Confirmed
** Changed in: maas (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Status: New = Confirmed
** Changed in: maas (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
44 matches
Mail list logo
