| 2016-06-18 15:29:18 |
Larry Michel |
bug |
|
|
added bug |
| 2016-06-18 15:29:18 |
Larry Michel |
attachment added |
|
log.bmcdup.tar.gz https://bugs.launchpad.net/bugs/1593991/+attachment/4686199/+files/log.bmcdup.tar.gz |
|
| 2016-06-18 15:32:09 |
Larry Michel |
description |
I am enlisting servers on maas through the CLI and I ended up with one power controller controlling 37 nodes. I wonder whether this had to do with me executing these commands as a script, because not all of them ended up on the same power controller. I saw another 2 servers that shared their power controller which was separe. If I deleted one these servers and added it again through the CLI, it came up fine with its own power controller. I am guessing I can work around this by putting a sleep (1 or 2 seconds) between each commands.
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=2c:59:e5:9a:d3:f4 hostname=reading domain=oilstaging power_type=ipmi
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=d8:9d:67:6f:56:28 hostname=gulon domain=oilstaging power_type=ipmi
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=2c:59:e5:41:a8:6c hostname=tucker domain=oilstaging power_type=ipmi
There's nothing wrong during the create. However, when I try to update the power parameters, I see this warning message in the UI:
This power controller manages 37 other nodes. Changing power parameters will affect these nodes.
Then I see that they all have same values. If update the power parameters for one, it updates for every nodes:
For example:
maas root machine update 4y3hed power_parameters_power_driver=LAN_2_0 power_parameters_power_address=192.168.224.44 power_parameters_power_pass=really? power_parameters_power_user=admin
"4y3han": {
"power_address": "192.168.224.44",
"power_pass": "really?",
"power_user": "admin",
"power_driver": "LAN_2_0",
"mac_address": ""
},
"4y3hed": {
"power_address": "192.168.224.44",
"power_pass": "really?",
"power_user": "admin",
"power_driver": "LAN_2_0",
"mac_address": ""
},
If I delete the server and add through the UI.
ubuntu@maas2-integration:~$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-====================================-============-=================================================
ii maas 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server common files
ii maas-dhcp 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS DHCP server
ii maas-dns 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS DNS server
ii maas-proxy 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS Caching Proxy
ii maas-rack-controller 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Rack Controller for MAAS
ii maas-region-api 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Region controller API service for MAAS
ii maas-region-controller 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server provisioning libraries (Python 3)
ubuntu@maas2-integration:~$ |
I am enlisting servers on maas through the CLI and I ended up with one power controller controlling 37 nodes. I wonder whether this had to do with me executing these commands as a script, because not all of them ended up on the same power controller. I saw another 2 servers that shared their power controller which was separate from the one controlling the 37 nodes.
I deleted one these servers and added it again through the CLI; it came up fine with its own power controller. I am guessing I can work around this by putting a sleep (1 or 2 seconds) between each commands?
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=2c:59:e5:9a:d3:f4 hostname=reading domain=oilstaging power_type=ipmi
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=d8:9d:67:6f:56:28 hostname=gulon domain=oilstaging power_type=ipmi
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=2c:59:e5:41:a8:6c hostname=tucker domain=oilstaging power_type=ipmi
There are no error during the machines create. However, when I try to update the power parameters on the UI, I see this warning message:
This power controller manages 37 other nodes. Changing power parameters will affect these nodes.
Then I see that they all have same values. If update the power parameters for one, it updates for every nodes:
For example:
maas root machine update 4y3hed power_parameters_power_driver=LAN_2_0 power_parameters_power_address=192.168.224.44 power_parameters_power_pass=really? power_parameters_power_user=admin
"4y3han": {
"power_address": "192.168.224.44",
"power_pass": "really?",
"power_user": "admin",
"power_driver": "LAN_2_0",
"mac_address": ""
},
"4y3hed": {
"power_address": "192.168.224.44",
"power_pass": "really?",
"power_user": "admin",
"power_driver": "LAN_2_0",
"mac_address": ""
},
The same thing happens when updating from the CLI.
If I delete the server and add through the UI.
ubuntu@maas2-integration:~$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-====================================-============-=================================================
ii maas 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server common files
ii maas-dhcp 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS DHCP server
ii maas-dns 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS DNS server
ii maas-proxy 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS Caching Proxy
ii maas-rack-controller 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Rack Controller for MAAS
ii maas-region-api 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Region controller API service for MAAS
ii maas-region-controller 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server provisioning libraries (Python 3)
ubuntu@maas2-integration:~$ |
|
| 2016-06-29 13:08:58 |
Andres Rodriguez |
summary |
2.0 beta7: nodes enlisted manually through CLI added with a single power controller controlling all the nodes for power type IPMI |
[2.0b7] nodes enlisted manually through CLI added with a single power controller controlling all the nodes for power type IPMI |
|
| 2016-07-08 16:53:36 |
Larry Michel |
attachment added |
|
screenshots.tar.gz https://bugs.launchpad.net/maas/+bug/1593991/+attachment/4697516/+files/screenshots.tar.gz |
|
| 2016-07-08 16:53:47 |
Jason Hobbs |
summary |
[2.0b7] nodes enlisted manually through CLI added with a single power controller controlling all the nodes for power type IPMI |
[2.0rc1] nodes enlisted manually through CLI added with a single power controller controlling all the nodes for power type IPMI |
|
| 2016-07-08 16:54:27 |
Jason Hobbs |
description |
I am enlisting servers on maas through the CLI and I ended up with one power controller controlling 37 nodes. I wonder whether this had to do with me executing these commands as a script, because not all of them ended up on the same power controller. I saw another 2 servers that shared their power controller which was separate from the one controlling the 37 nodes.
I deleted one these servers and added it again through the CLI; it came up fine with its own power controller. I am guessing I can work around this by putting a sleep (1 or 2 seconds) between each commands?
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=2c:59:e5:9a:d3:f4 hostname=reading domain=oilstaging power_type=ipmi
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=d8:9d:67:6f:56:28 hostname=gulon domain=oilstaging power_type=ipmi
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=2c:59:e5:41:a8:6c hostname=tucker domain=oilstaging power_type=ipmi
There are no error during the machines create. However, when I try to update the power parameters on the UI, I see this warning message:
This power controller manages 37 other nodes. Changing power parameters will affect these nodes.
Then I see that they all have same values. If update the power parameters for one, it updates for every nodes:
For example:
maas root machine update 4y3hed power_parameters_power_driver=LAN_2_0 power_parameters_power_address=192.168.224.44 power_parameters_power_pass=really? power_parameters_power_user=admin
"4y3han": {
"power_address": "192.168.224.44",
"power_pass": "really?",
"power_user": "admin",
"power_driver": "LAN_2_0",
"mac_address": ""
},
"4y3hed": {
"power_address": "192.168.224.44",
"power_pass": "really?",
"power_user": "admin",
"power_driver": "LAN_2_0",
"mac_address": ""
},
The same thing happens when updating from the CLI.
If I delete the server and add through the UI.
ubuntu@maas2-integration:~$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-====================================-============-=================================================
ii maas 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server common files
ii maas-dhcp 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS DHCP server
ii maas-dns 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS DNS server
ii maas-proxy 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS Caching Proxy
ii maas-rack-controller 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Rack Controller for MAAS
ii maas-region-api 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Region controller API service for MAAS
ii maas-region-controller 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server provisioning libraries (Python 3)
ubuntu@maas2-integration:~$ |
I am enlisting servers on maas through the CLI and I ended up with one power controller controlling 37 nodes. I wonder whether this had to do with me executing these commands as a script, because not all of them ended up on the same power controller. I saw another 2 servers that shared their power controller which was separate from the one controlling the 37 nodes.
I deleted one these servers and added it again through the CLI; it came up fine with its own power controller. I am guessing I can work around this by putting a sleep (1 or 2 seconds) between each commands?
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=2c:59:e5:9a:d3:f4 hostname=reading domain=oilstaging power_type=ipmi
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=d8:9d:67:6f:56:28 hostname=gulon domain=oilstaging power_type=ipmi
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=2c:59:e5:41:a8:6c hostname=tucker domain=oilstaging power_type=ipmi
There are no error during the machines create. However, when I try to update the power parameters on the UI, I see this warning message:
This power controller manages 37 other nodes. Changing power parameters will affect these nodes.
Then I see that they all have same values. If update the power parameters for one, it updates for every nodes:
For example:
maas root machine update 4y3hed power_parameters_power_driver=LAN_2_0 power_parameters_power_address=192.168.224.44 power_parameters_power_pass=really? power_parameters_power_user=admin
"4y3han": {
"power_address": "192.168.224.44",
"power_pass": "really?",
"power_user": "admin",
"power_driver": "LAN_2_0",
"mac_address": ""
},
"4y3hed": {
"power_address": "192.168.224.44",
"power_pass": "really?",
"power_user": "admin",
"power_driver": "LAN_2_0",
"mac_address": ""
},
The same thing happens when updating from the CLI.
If I delete the server and add through the UI.
ubuntu@maas2-production:~$ dpkg -l | grep maas
ii maas 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all MAAS client and command-line interface
ii maas-common 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all MAAS server common files
ii maas-dhcp 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all MAAS DHCP server
ii maas-dns 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all MAAS DNS server
ii maas-proxy 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all MAAS Caching Proxy
ii maas-rack-controller 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all Rack Controller for MAAS
ii maas-region-api 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all Region controller API service for MAAS
ii maas-region-controller 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all Region Controller for MAAS
ii python3-django-maas 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all MAAS server provisioning libraries (Python 3) |
|
| 2016-07-08 17:45:30 |
Jason Hobbs |
summary |
[2.0rc1] nodes enlisted manually through CLI added with a single power controller controlling all the nodes for power type IPMI |
[2.0rc1] nodes enlisted manually as IPMI all have the same BMC |
|
| 2016-07-08 18:23:21 |
Larry Michel |
attachment added |
|
Screenshot from 2016-07-08 13-21-35.png https://bugs.launchpad.net/maas/+bug/1593991/+attachment/4697559/+files/Screenshot%20from%202016-07-08%2013-21-35.png |
|
| 2016-07-08 19:02:37 |
Andres Rodriguez |
description |
I am enlisting servers on maas through the CLI and I ended up with one power controller controlling 37 nodes. I wonder whether this had to do with me executing these commands as a script, because not all of them ended up on the same power controller. I saw another 2 servers that shared their power controller which was separate from the one controlling the 37 nodes.
I deleted one these servers and added it again through the CLI; it came up fine with its own power controller. I am guessing I can work around this by putting a sleep (1 or 2 seconds) between each commands?
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=2c:59:e5:9a:d3:f4 hostname=reading domain=oilstaging power_type=ipmi
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=d8:9d:67:6f:56:28 hostname=gulon domain=oilstaging power_type=ipmi
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=2c:59:e5:41:a8:6c hostname=tucker domain=oilstaging power_type=ipmi
There are no error during the machines create. However, when I try to update the power parameters on the UI, I see this warning message:
This power controller manages 37 other nodes. Changing power parameters will affect these nodes.
Then I see that they all have same values. If update the power parameters for one, it updates for every nodes:
For example:
maas root machine update 4y3hed power_parameters_power_driver=LAN_2_0 power_parameters_power_address=192.168.224.44 power_parameters_power_pass=really? power_parameters_power_user=admin
"4y3han": {
"power_address": "192.168.224.44",
"power_pass": "really?",
"power_user": "admin",
"power_driver": "LAN_2_0",
"mac_address": ""
},
"4y3hed": {
"power_address": "192.168.224.44",
"power_pass": "really?",
"power_user": "admin",
"power_driver": "LAN_2_0",
"mac_address": ""
},
The same thing happens when updating from the CLI.
If I delete the server and add through the UI.
ubuntu@maas2-production:~$ dpkg -l | grep maas
ii maas 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all MAAS client and command-line interface
ii maas-common 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all MAAS server common files
ii maas-dhcp 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all MAAS DHCP server
ii maas-dns 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all MAAS DNS server
ii maas-proxy 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all MAAS Caching Proxy
ii maas-rack-controller 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all Rack Controller for MAAS
ii maas-region-api 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all Region controller API service for MAAS
ii maas-region-controller 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all Region Controller for MAAS
ii python3-django-maas 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.0.0~rc1+bzr5143-0ubuntu1~xenial1 all MAAS server provisioning libraries (Python 3) |
There's a combination of issues:
1. MAAS allows you to add a machine only specifying power_type, e.g. "ipmi". (The only reason when this should be allowed is when power_type=manual). There's also a error that should be addressed in https://bugs.launchpad.net/maas/+bug/1600328
2. When you add multiple machines only specifying power_type (no power_parameters_<param>, it causes all machines to think they have the same BMC. (See bellow explanation).
How to solve
=============
1. When adding a machine with power_type=manual, and no power_parameters_XYZ it should succeed.
2. When adding a machine with power_type={ipmi,etc}, and no power_parameters_XYZ, it should fail and should show an error that no power parameters have been provided.
======================================================================
I am enlisting servers on maas through the CLI and I ended up with one power controller controlling 37 nodes. I wonder whether this had to do with me executing these commands as a script, because not all of them ended up on the same power controller. I saw another 2 servers that shared their power controller which was separate from the one controlling the 37 nodes.
I deleted one these servers and added it again through the CLI; it came up fine with its own power controller. I am guessing I can work around this by putting a sleep (1 or 2 seconds) between each commands?
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=2c:59:e5:9a:d3:f4 hostname=reading domain=oilstaging power_type=ipmi
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=d8:9d:67:6f:56:28 hostname=gulon domain=oilstaging power_type=ipmi
maas root machines create architecture=amd64 subarchitecture=generic min_hwe_kernel=hwe-t mac_addresses=2c:59:e5:41:a8:6c hostname=tucker domain=oilstaging power_type=ipmi
There are no error during the machines create. However, when I try to update the power parameters on the UI, I see this warning message:
This power controller manages 37 other nodes. Changing power parameters will affect these nodes.
Then I see that they all have same values. If update the power parameters for one, it updates for every nodes:
For example:
maas root machine update 4y3hed power_parameters_power_driver=LAN_2_0 power_parameters_power_address=192.168.224.44 power_parameters_power_pass=really? power_parameters_power_user=admin
"4y3han": {
"power_address": "192.168.224.44",
"power_pass": "really?",
"power_user": "admin",
"power_driver": "LAN_2_0",
"mac_address": ""
},
"4y3hed": {
"power_address": "192.168.224.44",
"power_pass": "really?",
"power_user": "admin",
"power_driver": "LAN_2_0",
"mac_address": ""
},
The same thing happens when updating from the CLI.
If I delete the server and add through the UI.
ubuntu@maas2-integration:~$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-====================================-============-=================================================
ii maas 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server common files
ii maas-dhcp 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS DHCP server
ii maas-dns 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS DNS server
ii maas-proxy 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS Caching Proxy
ii maas-rack-controller 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Rack Controller for MAAS
ii maas-region-api 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Region controller API service for MAAS
ii maas-region-controller 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server provisioning libraries (Python 3)
ubuntu@maas2-integration:~$ |
|
| 2016-07-08 19:03:09 |
Andres Rodriguez |
summary |
[2.0rc1] nodes enlisted manually as IPMI all have the same BMC |
[2.0b7, API/CLI] allow's you to add machines with power_type and no power_parameters |
|
| 2016-07-11 07:02:21 |
Jeffrey C Jones |
maas: importance |
Undecided |
Medium |
|
| 2016-07-11 07:02:25 |
Jeffrey C Jones |
maas: status |
New |
In Progress |
|
| 2016-07-11 07:02:29 |
Jeffrey C Jones |
maas: assignee |
|
Jeffrey C Jones (trapnine) |
|
| 2016-07-11 07:03:31 |
Jeffrey C Jones |
summary |
[2.0b7, API/CLI] allow's you to add machines with power_type and no power_parameters |
[2.0b7, API/CLI] allows you to add machines with power_type but no power_parameters |
|
| 2016-07-11 07:03:49 |
Jeffrey C Jones |
summary |
[2.0b7, API/CLI] allows you to add machines with power_type but no power_parameters |
[2.0b7, API/CLI] allows you to add machines with power_type and no power_parameters |
|
| 2016-08-23 14:57:46 |
Andres Rodriguez |
maas: importance |
Medium |
Critical |
|
| 2016-08-23 14:57:58 |
Andres Rodriguez |
nominated for series |
|
maas/2.0 |
|
| 2016-08-23 14:57:58 |
Andres Rodriguez |
bug task added |
|
maas/2.0 |
|
| 2016-08-23 14:57:58 |
Andres Rodriguez |
nominated for series |
|
maas/trunk |
|
| 2016-08-23 14:57:58 |
Andres Rodriguez |
bug task added |
|
maas/trunk |
|
| 2016-08-23 14:58:06 |
Andres Rodriguez |
maas/2.0: milestone |
|
2.0.1 |
|
| 2016-08-23 14:58:07 |
Andres Rodriguez |
maas/trunk: milestone |
|
2.1.0 |
|
| 2016-08-23 14:58:09 |
Andres Rodriguez |
maas/2.0: importance |
Undecided |
Critical |
|
| 2016-08-23 14:58:12 |
Andres Rodriguez |
maas/2.0: status |
New |
Triaged |
|
| 2016-08-26 06:43:26 |
Jeffrey C Jones |
maas/trunk: status |
In Progress |
Triaged |
|
| 2016-10-04 19:27:33 |
Newell Jensen |
maas/trunk: assignee |
Jeffrey C Jones (trapnine) |
Newell Jensen (newell-jensen) |
|
| 2016-10-04 19:27:37 |
Newell Jensen |
maas/2.0: assignee |
|
Newell Jensen (newell-jensen) |
|
| 2016-10-04 19:42:33 |
Newell Jensen |
maas/2.0: assignee |
Newell Jensen (newell-jensen) |
|
|
| 2016-10-04 19:42:35 |
Newell Jensen |
maas/trunk: assignee |
Newell Jensen (newell-jensen) |
|
|
| 2016-10-13 17:08:00 |
Andres Rodriguez |
maas: milestone |
2.1.0 |
2.1.1 |
|
| 2016-10-20 08:42:34 |
Launchpad Janitor |
branch linked |
|
lp:~ltrager/maas/lp1593991 |
|
| 2016-10-20 20:39:37 |
Blake Rouse |
maas/2.0: status |
Triaged |
In Progress |
|
| 2016-10-20 20:39:42 |
Blake Rouse |
maas/2.0: assignee |
|
Lee Trager (ltrager) |
|
| 2016-10-20 20:39:46 |
Blake Rouse |
maas/trunk: status |
Triaged |
In Progress |
|
| 2016-10-20 20:39:48 |
Blake Rouse |
maas/2.0: status |
In Progress |
Triaged |
|
| 2016-10-20 20:39:50 |
Blake Rouse |
maas/2.0: assignee |
Lee Trager (ltrager) |
|
|
| 2016-10-20 20:39:56 |
Blake Rouse |
maas/trunk: assignee |
|
Lee Trager (ltrager) |
|
| 2016-10-21 01:20:06 |
MAAS Lander |
maas/trunk: status |
In Progress |
Fix Committed |
|
| 2016-10-24 18:42:17 |
Launchpad Janitor |
branch linked |
|
lp:~ltrager/maas/lp1593991_2.0 |
|
| 2016-10-24 21:52:57 |
MAAS Lander |
maas/2.0: status |
Triaged |
Fix Committed |
|
| 2016-10-25 19:10:19 |
Lee Trager |
maas/2.0: assignee |
|
Lee Trager (ltrager) |
|
| 2016-12-08 08:49:57 |
Lee Trager |
maas/2.0: status |
Fix Committed |
Fix Released |
|
| 2016-12-08 08:50:02 |
Lee Trager |
maas/trunk: status |
Fix Committed |
Fix Released |
|
| 2018-08-30 13:47:20 |
Marco Mariani |
bug |
|
|
added subscriber Marco Mariani |
