Comment 6 for bug 1923315
Revision history for this message
| Stamatis Katsaounis (skatsaounis) wrote | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
2eb648a
demo site
(Get the code!)
I am reopening this old bug since I was able to reproduce it. The problem is that param osystem is completely ignored plus distro param should be distro_series. While the later is a wrong call towards the latest MAAS API as OP found out, the former is a MAAS bug as it should not presenting it as a valid param to users.
Regarding the successful second try, that happened because distro_series was set to a release version which was already present for esxi. But what would happen if for example centos/7.0 was also present? The current implementation of MAAS code might match centos and as a surprise to the user, since osystem is ignored, the machine could be deployed with CentOS.