Just a follow up to this:
I updated my codebase, rebuilt my cloud from scratch, and now it seems that
all of my disks/volumes (both root and data) show up on the Storage tab as
I spin up VMs and attach data disks to them.
On Sun, Jul 6, 2014 at 12:25 AM, Mike Tutkowski <
mike.tutkow...@solidfire
Interesting...one of my three ROOT disks shows up at the time being.
On Sun, Jul 6, 2014 at 12:17 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> I noticed tonight that the Storage tab no longer shows me ROOT
> volumes...just DATADISK ones.
>
> Possibly related to the issue that was
I noticed tonight that the Storage tab no longer shows me ROOT
volumes...just DATADISK ones.
Possibly related to the issue that was being discussed in this thread?
On Tue, Jul 1, 2014 at 6:18 PM, Mike Tutkowski wrote:
> Actually, this is a good opportunity to remind devs in general that if you
Actually, this is a good opportunity to remind devs in general that if you
make a change to a schema-upgrade file for a release and you are not on
master that you should take a peek at the schema-upgrade file on master to
see if it needs to be updated, as well.
In this case, it would have been OK
Thanks!
On Tue, Jul 1, 2014 at 4:26 PM, Yoshikazu Nojima wrote:
> Hi all,
> I pushed a commit to fix this issue.
> I confirmed listVolumes doesn't throw an error now in my environment.
>
> Commit 890e71cb5c2f80b09cd4db7947d94e325d7bd182 in cloudstack's branch
> refs/heads/master from Yoshikazu
Hi all,
I pushed a commit to fix this issue.
I confirmed listVolumes doesn't throw an error now in my environment.
Commit 890e71cb5c2f80b09cd4db7947d94e325d7bd182 in cloudstack's branch
refs/heads/master from Yoshikazu Nojima
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=890e71c ]
Somehow I didn't see that aliasing going on there.
On Tue, Jul 1, 2014 at 2:05 PM, Mike Tutkowski wrote:
> Ah, yes, good point.
>
>
> On Tue, Jul 1, 2014 at 2:02 PM, Yoshikazu Nojima wrote:
>
>> Hi Mike,
>> I suppose "iso" is an alias for "vm_template".
>> See the left join syntax you refered.
Ah, yes, good point.
On Tue, Jul 1, 2014 at 2:02 PM, Yoshikazu Nojima wrote:
> Hi Mike,
> I suppose "iso" is an alias for "vm_template".
> See the left join syntax you refered.
>
> >left join
> >`cloud`.`vm_template` iso ON iso.id = volumes.iso_id
>
>
> Regards,
> Noji
>
> 2
Hi Mike,
I suppose "iso" is an alias for "vm_template".
See the left join syntax you refered.
>left join
>`cloud`.`vm_template` iso ON iso.id = volumes.iso_id
Regards,
Noji
2014-07-01 12:19 GMT-06:00 Mike Tutkowski :
> This diff shows some of the problem:
>
> http://i.imgur.
This diff shows some of the problem:
http://i.imgur.com/PW7lqbs.png
Six fields have been removed from the volume_view and five of those six are
still in use.
It is not a simple matter of adding them back in, however, because the iso
table that used to be used is no longer present in 4.5.
That b
Upon further consideration, I forgot that we drop and re-create views in
the SQL - if need be - from release to release.
It looks like a new version of the volume_view went into 4.5 with
11f5bdd78de4121331b07995800f6e9e7c22f2c0, which is from Review Request
19446.
It appears volume_view is missin
Actually, in looking at "git blame", it appears this view has never had
those two columns.
I think the intent, however, is that those two columns exist in the view.
I'm adding them in my sandbox and testing this out now.
On Mon, Jun 30, 2014 at 10:11 PM, Mike Tutkowski <
mike.tutkow...@solidfir
I looked into this a bit more.
It appears that the "volume_view" no longer has the following two columns:
vm_template.name template_name
vm_template.display_text template_display_text
The problem is that the Java class, VolumeJoinVO, still has reference to
them (a variable for each one).
I woul
Thanks for the reply.
The weird part is that this is the second time I've recreated the DB and
seen this issue.
If I have time a bit later, I can see if the SQL in Git is wrong and update
it with what you provided.
Thanks!
On Mon, Jun 30, 2014 at 5:47 AM, Bharat Kumar
wrote:
> Hi Mike,
>
> I
Hi Mike,
I think the volume_view did not get created properly for some reason. I think
recreating the volume_view will fix the problem.
below commas should fix the issue.
DROP VIEW IF EXISTS `cloud`.`volume_view`;
CREATE VIEW `cloud`.`volume_view` AS
select
volumes.id,
volum
Hi,
If you click on the Storage tab in the GUI when you have one or more
volumes, you receive the following exception (is this something someone is
already working on?):
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException:
Unknown column 'volume_view.template_name' in 'field list
16 matches
Mail list logo
