Welcome, Guest
Username: Password: Remember me
Archived CloudStack Forums for reference purposes please direct all future inquiries to the Apache CloudStack mailing lists.

incubator.apache.org/cloudstack/mailing-lists.html
  • Page:
  • 1

TOPIC: No templates, except in templates

No templates, except in templates 9 months 2 weeks ago #12742

  • Parviainen
  • Parviainen's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 2
  • Karma: 0
Hi,
I've been at this for a few hours, so let's try here.

I can't create an instance, as there are no templates to choose from. In Templates, the standard template is shown (I can also see it if I manually mount the secondary NFS) but when creating an instance, can find nothing.

I also cannot add ISO files, they don't seem to download (I added 0.0.0.0/0 to secstorage.allowed.internal.sites, so should be no problem). They show up, but they never end up to downloaded state. (There should be some kind of error notifications here, and explanations on why, eg. network timeout, host outside allowed network etc.)

I found I should check if the SSVM is up, but could find no explanation on what that is, or how to do it. I surmised the acronym could mean Secondary Storage Virtual Machine, and found that I should run this
select * from host where type="SecondaryStorageVM";
and got an empty result set. (I assumed I should run this in management server, under database Cloud)

There is something classified as type=SecondaryStorage however, those seem to be my secondary storage NFS shares, both giving status:alert.

Weird thing is, I deleted one of them previously as I had typoed the path.

I suspect, for some reason, the SSVM is not running(?). How to restart it? What else can I do to provide debugging information?
The administrator has disabled public write access.

Re: No templates, except in templates 9 months 1 week ago #12760

  • Parviainen
  • Parviainen's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 2
  • Karma: 0
After much fiddling, I solved it.

For future reference, here's what I did.

Firstly, for some reason no IP address spaces were allocated by default, so I went to infrastructure -> zones -> my-zone-name -> physical network -> my physical network name-> storage -> ip allocations and added a few IPs there.

Secondly, I disabled the zone, pod and put host on maintenance mode, and brought everything up again.

I was now able to create a VM, but currently cannot access it through the console.

It seems under certain circumstances, the first start wizard will get everything cocked up, particularly if during the process the page is refreshed after a certain point, not all settings will be saved.
The administrator has disabled public write access.
  • Page:
  • 1
Time to create page: 0.321 seconds
About BuildaCloud.org Resources Site Info

Build a Cloud.org is a resource for those users who want to build cloud computing software with both open source and proprietary software.