cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daan Hoogland (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-4969) Cannot change Host OS preference from xyz -> None
Date Sun, 01 Feb 2015 09:54:34 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daan Hoogland closed CLOUDSTACK-4969.
-------------------------------------
    Resolution: Fixed

submitted: f194adb2ded586516f98e045bb318ca1af0730e5

> Cannot change Host OS preference from xyz -> None
> -------------------------------------------------
>
>                 Key: CLOUDSTACK-4969
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4969
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API, UI
>    Affects Versions: 4.2.0
>            Reporter: Marty Sweet
>
> Using the API (or Web Interface) users are unable to change Hosts OS Preference away
from an OS to None.
> Reproduce:
> 1) Infrastructure > Hosts (View All) > Click Host > Edit
> 2) Change OS Preference to Ubuntu
> 3) Save
> 4) Refresh > go back into menu, it is Ubuntu
> 5) Edit > Change OS Preference to None
> 6) Save
> 7) Refresh > go back into menu, it is Ubuntu
> Changing from an OS -> None does not save.
> This functionality doesn't work when manipulating the API commands either.
> The following requests are sent from the WebUI:
> Changing to Ubuntu:
> client/api?command=updateHost
> &id=864e1675-92e3-45cd-a184-54d65e61d3da
> &hosttags=
> &osCategoryId=47c65292-32f7-4000-8786-1eb722072cb4
> &response=json
> Request sent changing to None:
> client/api?command=updateHost
> &id=864e1675-92e3-45cd-a184--4d65e61d3da
> &hosttags=
> &response=json
> It appears that osCategoryId should contain the UUID for the `guest_os_category`, when
this is set to 11 (as set for 'None' in my DB), it does not work either. The JSON response
from the API simply returns the old value with no errors.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message