I guess you are referring to the bug
https://issues.apache.org/jira/browse/CLOUDSTACK-4716


On 12/11/13 3:57 PM, "Marcus Sorensen" <shadow...@gmail.com> wrote:

>I'm wondering if someone can quickly help me figure out an issue with
>4.1 to 4.2 upgrade. I seem to be missing a bunch of types on existing
>accounts for my resource_count table. In particular, I'm missing rows
>for pre-4.2 accounts for resource types:
>
>cpu
>memory
>primary_storage
>secondary_storage
>
>Does anyone know what's supposed to upgrade existing accounts with
>these? I'm getting SQL syntax errors because resource lookups return
>no results.
>
>
>new account:
>
>| 646684 |       NULL |     17806 | user_vm           |           0 |
>| 646687 |       NULL |     17806 | public_ip         |           0 |
>| 646690 |       NULL |     17806 | volume            |           0 |
>| 646693 |       NULL |     17806 | snapshot          |           0 |
>| 646696 |       NULL |     17806 | template          |           0 |
>| 646699 |       NULL |     17806 | project           |           0 |
>| 646702 |       NULL |     17806 | network           |           0 |
>| 646705 |       NULL |     17806 | vpc               |           0 |
>| 646708 |       NULL |     17806 | cpu               |           0 |
>| 646711 |       NULL |     17806 | memory            |           0 |
>| 646714 |       NULL |     17806 | primary_storage   |           0 |
>| 646717 |       NULL |     17806 | secondary_storage |           0 |
>
>old account:
>
>| 639760 |       NULL |     17653 | user_vm           |           1 |
>| 639763 |       NULL |     17653 | public_ip         |           0 |
>| 639766 |       NULL |     17653 | volume            |           1 |
>| 639769 |       NULL |     17653 | snapshot          |           0 |
>| 639772 |       NULL |     17653 | template          |           0 |
>| 639775 |       NULL |     17653 | project           |           0 |
>| 639778 |       NULL |     17653 | network           |           1 |
>| 639781 |       NULL |     17653 | vpc               |           1 |

Reply via email to