Bug #2480
"Wrong type NilClass. Not allowed!" when deploying VMs in Sunstone
| Status: | Closed | Start date: | 11/20/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Daniel Molina | % Done: | 0% | |
| Category: | Sunstone | |||
| Target version: | Release 4.4 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.4 |
Description
Hello,
Upgraded from version 4.2 to 4.4 and having trouble deploying VMs in this new version. If I submit a VM for deployment, it will stay in a 'Pending' state. If I manually deploy, I receive a 'Wrong type NilClass. Not allowed!' error message.
No other log entries occur at this time.
I tried removing and recreating the database from scratch in case there was an issue with existing data but the same result.
Again, this was an upgrade from 4.2. Occurs on VMs on both Ceph and FS datastores (so I'm assuming it is for all). Have not tried a fresh install (as our systems would follow the upgrade path).
Related issues
Associated revisions
bug #2480: Use default values for enforce and ds_id if nil
bug #2480: Use default values for enforce and ds_id if nil
(cherry picked from commit 95fa5c34d3ac04ea1b16791b0ceb9cc81ef640b3)
History
#1
Updated by Daniel Molina over 7 years ago
Hi Bill,
There is a problem when specifying the ds_id from Sunstone. I have fixed it in this commit:
http://dev.opennebula.org/issues/2478#change-6728
But I think the problem you are experiencing is just a cache problem, you will face the previous bug after solving this. Could you try clearing the browser cache or using an incognito window?
#2
Updated by Bill Campbell over 7 years ago
I think you are correct! Your genius trumps my genius. ;-)
I ran into another sunstone issue, I'll file another report.
Thanks
#3
Updated by Daniel Molina over 7 years ago
- Category set to Sunstone
- Status changed from Pending to Closed
- Assignee set to Daniel Molina
- Target version set to Release 4.4
- Resolution set to fixed