[openstack-dev] [TripleO] CI status update for this week
Joe Gordon
joe.gordon0 at gmail.com
Fri Jun 20 21:24:39 UTC 2014
On Fri, Jun 20, 2014 at 2:15 PM, Charles Crouch <ccrouch at redhat.com> wrote:
>
>
> ----- Original Message -----
> >
> >
> >
> > On Jun 20, 2014 1:52 PM, "Charles Crouch" < ccrouch at redhat.com > wrote:
> > >
> > >
> > >
> > > ----- Original Message -----
> > > > Not a great week for TripleO CI. We had 3 different failures related
> to:
> > > >
> > > > Nova [1]: we were using a deprecated config option
> > > > Heat [2]: missing heat data obtained from the Heat CFN API
> > > > Neutron [3]: a broken GRE overlay network setup
> > >
> > > The last two are bugs, but is there anything tripleo can do about
> avoiding
> > > the first one in the future?:
> > > e.g. reviewing a list of deprecated options and seeing when they will
> be
> > > removed.
> > ++
> > >
> > > do the integrated projects have a protocol for when an option is
> deprecated
> > > and at what point it can be removed?
> > > e.g. if I make something deprecated in icehouse I can remove it in
> juno,
> > > but if I
> > > make something deprecated at the start of juno I can't remove it at
> the end
> > > of juno?
> >
> > That is exactly what we do, deprecate for one release. This was the
> removal
> > of deprecated icehouse options patch.
>
> Ok great, and just to be clear I didn't mean to imply Nova did anything
> wrong here.
> I'm looking for what tripleo can do to make sure it keeps up.
>
> Is there any easy way to see what options have been deprecated in a
> release for
> the integrated projects?
> I guess a list would only need to be pulled together once at the end of
> each release.
>
Yup, if you look at the config file you can generate it will tell you what
has been deprecated.
>
>
> > >
> > > >
> > > > The TripleO check jobs look to be running stable again today so if
> your
> > > > patch had failures from earlier this week then recheck away (perhaps
> > > > referencing one of these bugs if appropriate). The queue is fairly
> empty
> > > > right now...
> > > >
> > > > Thanks for all the help in tracking these down and getting things
> fixed.
> > > >
> > > > [1] https://bugs.launchpad.net/tripleo/+bug/1292105
> > >
> > > I think [1] was meant to be
> > > https://bugs.launchpad.net/tripleo/+bug/1330735
> > >
> > > > [2] https://bugs.launchpad.net/heat/+bug/1331720
> > > > [3] https://bugs.launchpad.net/tripleo/+bug/1292105
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > OpenStack-dev mailing list
> > > > OpenStack-dev at lists.openstack.org
> > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > > >
> > >
> > > _______________________________________________
> > > OpenStack-dev mailing list
> > > OpenStack-dev at lists.openstack.org
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140620/1fad9476/attachment.html>
More information about the OpenStack-dev
mailing list