s we can automate the
>> >> instructions. For data modification, the developer who’s made the
>> >> changes, still needs to provide the instructions on the dev list.
>> >>
>> >> -Alena.
>> >>
>> >> From: Mike Tutkowski >
Prokharchyk
Subject: Re: [DB-CHANGE] Infrastructure tab fails to load with db exception
That is true. It was not my intent to address that problem, though. I was
simply commenting on the question of whether we should continue to use the
[DB-CHANGE] e-mail tag (I believe we should).
On Wed, Aug
> -Alena.
> >>
> >> From: Mike Tutkowski >> >
> >> Date: Wednesday, August 6, 2014 at 11:33 AM
> >> To: "dev@cloudstack.apache.org
> >> " <
> >> dev@cloudstack.apache.org
> >> >
> >> Cc: Alena Prokharchyk
tkowski >> >
>>> Date: Wednesday, August 6, 2014 at 11:33 AM
>>> To: "dev@cloudstack.apache.org
>>> " <
>>> dev@cloudstack.apache.org
>>> >
>>> Cc: Alena Prokharchyk >> >, Koushik
>>> Das >> >
>>
August 6, 2014 at 11:33 AM
>> To: "dev@cloudstack.apache.org
>> " <
>> dev@cloudstack.apache.org
>> >
>> Cc: Alena Prokharchyk > >, Koushik
>> Das > >
>> Subject: Re: [DB-CHANGE] Infrastructure tab fails to load with db
>> excep
made the changes, still needs to
>>>> provide the instructions on the dev list.
>>>>
>>>> -Alena.
>>>>
>>>> From: Mike Tutkowski >>> >
>>>> Date: Wednesday, August 6, 2014 at 11:33 AM
>>>> To: &
s on the dev list.
>>>
>>> -Alena.
>>>
>>> From: Mike Tutkowski >> >
>>> Date: Wednesday, August 6, 2014 at 11:33 AM
>>> To: "dev@cloudstack.apache.org
>>> " <
>>> dev@cloudstack.apache.org
>>> >
11:33 AM
>> To: "dev@cloudstack.apache.org
>> " <
>> dev@cloudstack.apache.org
>> >
>> Cc: Alena Prokharchyk > >, Koushik
>> Das > >
>> Subject: Re: [DB-CHANGE] Infrastructure tab fails to load with db
>> exception
>>
>>
ke Tutkowski >
> Date: Wednesday, August 6, 2014 at 11:33 AM
> To: "dev@cloudstack.apache.org
> " <
> dev@cloudstack.apache.org
> >
> Cc: Alena Prokharchyk >, Koushik
> Das >
> Subject: Re: [DB-CHANGE] Infrastructure tab fails to load with db
>
sues.apache.org/jira/browse/CLOUDSTACK-7273
>>>
>>>
>>>Thanks,
>>>-Nitin
>>>
>>>On 06/08/14 5:28 AM, "Koushik Das"
>>>> wrote:
>>>
>>>>Thanks Saksham. This fixed the initial issue. But I noticed a
rchyk
mailto:alena.prokharc...@citrix.com>>, Koushik
Das mailto:koushik....@citrix.com>>
Subject: Re: [DB-CHANGE] Infrastructure tab fails to load with db exception
What about the details for updating your DB?
If we just receive a general e-mail notification, then each dev will
indepen
gt;Thanks Saksham. This fixed the initial issue. But I noticed a new one,
> >>>after destroying the last VR if you select the infra view it again
> >>>results in exception. Not sure if anything else needs to be fixed.
> >>>
> >>>-Original Message
sults in exception. Not sure if anything else needs to be fixed.
>>>
>>>-----Original Message-
>>>From: Saksham Srivastava [mailto:saksham.srivast...@citrix.com]
>>>Sent: Wednesday, 6 August 2014 3:37 PM
>>>To: dev@cloudstack.apache.org
>>>Sub
ew one,
>>after destroying the last VR if you select the infra view it again
>>results in exception. Not sure if anything else needs to be fixed.
>>
>>-Original Message-
>>From: Saksham Srivastava [mailto:saksham.srivast...@citrix.com]
>>Sent: Wednesday, 6
>From: Saksham Srivastava [mailto:saksham.srivast...@citrix.com]
>Sent: Wednesday, 6 August 2014 3:37 PM
>To: dev@cloudstack.apache.org
>Subject: [DB-CHANGE] Infrastructure tab fails to load with db exception
>
>I remember we used to follow the practice of informing others in
Thanks for sending this out! These can be really helpful.
On Wed, Aug 6, 2014 at 4:06 AM, Saksham Srivastava <
saksham.srivast...@citrix.com> wrote:
> I remember we used to follow the practice of informing others in case db
> changes are committed, but we do not do it anymore.
> In case you are
]
Sent: Wednesday, 6 August 2014 3:37 PM
To: dev@cloudstack.apache.org
Subject: [DB-CHANGE] Infrastructure tab fails to load with db exception
I remember we used to follow the practice of informing others in case db
changes are committed, but we do not do it anymore.
In case you are on dev setup
I remember we used to follow the practice of informing others in case db
changes are committed, but we do not do it anymore.
In case you are on dev setup on master branch post the following commit :
commit b9d834e83854009483f6d061f9996e5ffaa9b883
Author: Nitin Mehta
Date: Tue Aug 5 17:29:34 201
18 matches
Mail list logo