Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
MIME-Version: 1.0
In-Reply-To: <DB5PR07MB168512032EAABD8F496FEBECE9920@DB5PR07MB1685.eurprd07.prod.outlook.com>
References: <CAC2panoj8w=3-wUvznpnF4bqtjYBwQgueHr1b2O3h5vZAnrQgw@mail.gmail.com>
 <CANLSSBV7nSZF4H36thtxO6HZSitJVjttFjD3TQoCWzMeMi6OnQ@mail.gmail.com> <DB5PR07MB168512032EAABD8F496FEBECE9920@DB5PR07MB1685.eurprd07.prod.outlook.com>
From: Will Stevens <williamstevens@gmail.com>
Date: Thu, 22 Dec 2016 08:44:46 -0500
Message-ID: <CAC2panoSQ4nSAVqGnaO+Wgb-_FB_udVwJ=dZwBcp__TiN+X2cg@mail.gmail.com>
Subject: Re: Error on Master
To: Rohit Yadav <rohit.yadav@shapeblue.com>
Cc: dev@cloudstack.apache.org
Content-Type: multipart/alternative; boundary=001a1140d7bc0f510205443f790b
archived-at: Thu, 22 Dec 2016 13:44:59 -0000

--001a1140d7bc0f510205443f790b
Content-Type: text/plain; charset=UTF-8

No problem. I think it is because I have been upgrading this env from
master to master periodically and the schema changes were only recently
added in the upgrade sql. We should be good. Thanks for checking. I got my
env working with the details in this thread, so hopefully it will help
others if they have a similar nontraditional upgrade of master to master.

Thanks for the hard work rohit and happy holidays. :)

On Dec 22, 2016 1:55 AM, "Rohit Yadav" <rohit.yadav@shapeblue.com> wrote:

> Will,
>
>
> I tried to run some upgrade tests and could not reproduce your issue.
>
> If this happens again, let me know.
>
>
> Regards.
> ------------------------------
> *From:* Rohit Yadav <bhaisaab@apache.org>
> *Sent:* 22 December 2016 12:03:41
> *To:* Will Stevens
> *Cc:* dev@cloudstack.apache.org
> *Subject:* Re: Error on Master
>
> Hi Will,
>
> I tried a fresh installation of latest master and I was able to deploy
> database. I'll run upgrade tests soon to verify if there are any issues.
>
> Regards.
>
> On Thu, Dec 22, 2016 at 12:41 AM, Will Stevens <williamstevens@gmail.com>
> wrote:
>
> > Has anyone seen this.
> >
> > I upgraded a system which was running master to a later version of master
> > and I get the following when I start the service after upgrading.
> >
> > 2016-12-21 18:55:13,388 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
> > (main:null) (logid:) Exception encountered during context initialization
> -
> > cancelling refresh attempt: org.springframework.context.
> ApplicationContextException:
> > Failed to start bean 'cloudStackLifeCycle'; nested exception is
> > com.cloud.utils.exception.CloudRuntimeException: DB Exception on:
> > com.mysql.jdbc.JDBC4PreparedStatement@69cd2214: SELECT
> > network_offerings.id, network_offerings.name,
> > network_offerings.unique_name, network_offerings.display_text,
> > network_offerings.nw_rate, network_offerings.mc_rate,
> > network_offerings.traffic_type, network_offerings.specify_vlan,
> > network_offerings.system_only, network_offerings.service_offering_id,
> > network_offerings.tags, network_offerings.default, network_offerings.
> availability,
> > network_offerings.state, network_offerings.removed,
> > network_offerings.created, network_offerings.guest_type,
> > network_offerings.dedicated_lb_service, network_offerings.shared_
> source_nat_service,
> > network_offerings.specify_ip_ranges, network_offerings.sort_key,
> > network_offerings.uuid, network_offerings.redundant_router_service,
> > network_offerings.conserve_mode, network_offerings.elastic_ip_service,
> > network_offerings.eip_associate_public_ip, network_offerings.elastic_lb_
> service,
> > network_offerings.inline, network_offerings.is_persistent,
> > network_offerings.egress_default_policy, network_offerings.concurrent_
> connections,
> > network_offerings.keep_alive_enabled, network_offerings.supports_
> streched_l2,
> > network_offerings.supports_public_access, network_offerings.internal_lb,
> > network_offerings.public_lb FROM network_offerings WHERE
> > network_offerings.unique_name = _binary'System-Public-Network'  AND
> > network_offerings.removed IS NULL  ORDER BY RAND() LIMIT 1
> >
> >
> > I tried running the SQL directly to see what I get and I get the
> following:
> >
> > mysql> SELECT network_offerings.id, network_offerings.name,
> > network_offerings.unique_name, network_offerings.display_text,
> > network_offerings.nw_rate, network_offerings.mc_rate,
> > network_offerings.traffic_type, network_offerings.specify_vlan,
> > network_offerings.system_only, network_offerings.service_offering_id,
> > network_offerings.tags, network_offerings.default, network_offerings.
> availability,
> > network_offerings.state, network_offerings.removed,
> > network_offerings.created, network_offerings.guest_type,
> > network_offerings.dedicated_lb_service, network_offerings.shared_
> source_nat_service,
> > network_offerings.specify_ip_ranges, network_offerings.sort_key,
> > network_offerings.uuid, network_offerings.redundant_router_service,
> > network_offerings.conserve_mode, network_offerings.elastic_ip_service,
> > network_offerings.eip_associate_public_ip, network_offerings.elastic_lb_
> service,
> > network_offerings.inline, network_offerings.is_persistent,
> > network_offerings.egress_default_policy, network_offerings.concurrent_
> connections,
> > network_offerings.keep_alive_enabled, network_offerings.supports_
> streched_l2,
> > network_offerings.supports_public_access, network_offerings.internal_lb,
> > network_offerings.public_lb FROM network_offerings WHERE
> > network_offerings.unique_name = _binary'System-Public-Network'  AND
> > network_offerings.removed IS NULL  ORDER BY RAND() LIMIT 1;
> >
> > ERROR 1054 (42S22): Unknown column 'network_offerings.supports_
> public_access'
> > in 'field list'
> >
> > Did I miss a step or something in my upgrade from master to the latest
> > master?  I have done this upgrade a few times in the past without issues,
> > but maybe something has changed?
> >
>
> rohit.yadav@shapeblue.com
> www.shapeblue.com
> @shapeblue
>
>
>
>

--001a1140d7bc0f510205443f790b--