<div dir="ltr">Anyway to workaround this? Maybe downgrade hiera?</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 3, 2016 at 5:55 PM, Ronelle Landy <span dir="ltr"><<a href="mailto:rlandy@redhat.com" target="_blank">rlandy@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I am not sure exactly where you installed from, and when you did your installation, but any chance, you've hit: <a href="https://bugs.launchpad.net/tripleo/+bug/1584892" rel="noreferrer" target="_blank">https://bugs.launchpad.net/tripleo/+bug/1584892</a>?<br>
There is a link bugzilla record.<br>
<span class="im HOEnZb"><br>
----- Original Message -----<br>
> From: "Pedro Sousa" <<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>><br>
> To: "Ronelle Landy" <<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>><br>
> Cc: "Christopher Brown" <<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a>>, "Ignacio Bravo" <<a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a>>, "rdo-list"<br>
> <<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>><br>
</span><div class="HOEnZb"><div class="h5">> Sent: Friday, June 3, 2016 12:26:58 PM<br>
> Subject: Re: [rdo-list] Baremetal Tripleo stable version?<br>
><br>
> Thanks Ronelle,<br>
><br>
> do you think this kind of errors can be related with network settings?<br>
><br>
> "Could not retrieve fact='rabbitmq_nodename', resolution='<anonymous>':<br>
> undefined method `[]' for nil:NilClass Could not retrieve<br>
> fact='rabbitmq_nodename', resolution='<anonymous>': undefined method `[]'<br>
> for nil:NilClass"<br>
><br>
> On Fri, Jun 3, 2016 at 4:56 PM, Ronelle Landy <<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>> wrote:<br>
><br>
> > Hi Pedro,<br>
> ><br>
> > You could use the docs you referred to.<br>
> > Alternatively, if you want to use a vm for the undercloud and baremetal<br>
> > machines for the overcloud, it is possible to use Tripleo Qucikstart with a<br>
> > few modifications.<br>
> > <a href="https://bugs.launchpad.net/tripleo-quickstart/+bug/1571028" rel="noreferrer" target="_blank">https://bugs.launchpad.net/tripleo-quickstart/+bug/1571028</a>.<br>
> ><br>
> > ----- Original Message -----<br>
> > > From: "Pedro Sousa" <<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>><br>
> > > To: "Ronelle Landy" <<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>><br>
> > > Cc: "Christopher Brown" <<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a>>, "Ignacio Bravo" <<br>
> > <a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a>>, "rdo-list"<br>
> > > <<a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>><br>
> > > Sent: Friday, June 3, 2016 11:48:38 AM<br>
> > > Subject: Re: [rdo-list] Baremetal Tripleo stable version?<br>
> > ><br>
> > > Hi Ronelle,<br>
> > ><br>
> > > maybe I understand it wrong but I thought that Tripleo Quickstart was for<br>
> > > deploying virtual environments?<br>
> > ><br>
> > > And for baremetal we should use<br>
> > ><br>
> > <a href="http://docs.openstack.org/developer/tripleo-docs/installation/installation.html" rel="noreferrer" target="_blank">http://docs.openstack.org/developer/tripleo-docs/installation/installation.html</a><br>
> > > ?<br>
> > ><br>
> > > Thanks<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > On Fri, Jun 3, 2016 at 4:43 PM, Ronelle Landy <<a href="mailto:rlandy@redhat.com">rlandy@redhat.com</a>> wrote:<br>
> > ><br>
> > > > Hello,<br>
> > > ><br>
> > > > We have had success deploying RDO (Mitaka) on baremetal systems - using<br>
> > > > Tripleo Quickstart with both single-nic-vlans and bond-with-vlans<br>
> > network<br>
> > > > isolation configurations.<br>
> > > ><br>
> > > > Baremetal can have some complicated networking issues but, from<br>
> > previous<br>
> > > > experiences, if a single-controller deployment worked but a HA<br>
> > deployment<br>
> > > > did not, I would check:<br>
> > > > - does the HA deployment command include: -e<br>
> > > ><br>
> > /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml<br>
> > > > - are there possible MTU issues?<br>
> > > ><br>
> > > ><br>
> > > > ----- Original Message -----<br>
> > > > > From: "Christopher Brown" <<a href="mailto:cbrown2@ocf.co.uk">cbrown2@ocf.co.uk</a>><br>
> > > > > To: <a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>, <a href="mailto:ibravo@ltgfederal.com">ibravo@ltgfederal.com</a><br>
> > > > > Cc: <a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a><br>
> > > > > Sent: Friday, June 3, 2016 10:29:39 AM<br>
> > > > > Subject: Re: [rdo-list] Baremetal Tripleo stable version?<br>
> > > > ><br>
> > > > > Hello Ignacio,<br>
> > > > ><br>
> > > > > Thanks for your response and good to know it isn't just me!<br>
> > > > ><br>
> > > > > I would be more than happy to provide developers with access to our<br>
> > > > > bare metal environments. I'll also file some bugzilla reports to see<br>
> > if<br>
> > > > > this generates any interest.<br>
> > > > ><br>
> > > > > Please do let me know if you make any progress - I am trying to<br>
> > deploy<br>
> > > > > HA with network isolation, multiple nics and vlans.<br>
> > > > ><br>
> > > > > The RDO web page states:<br>
> > > > ><br>
> > > > > "If you want to create a production-ready cloud, you'll want to use<br>
> > the<br>
> > > > > TripleO quickstart guide."<br>
> > > > ><br>
> > > > > which is a contradiction in terms really.<br>
> > > > ><br>
> > > > > Cheers<br>
> > > > ><br>
> > > > > On Fri, 2016-06-03 at 14:30 +0100, Ignacio Bravo wrote:<br>
> > > > > > Pedro / Christopher,<br>
> > > > > ><br>
> > > > > > Just wanted to share with you that I also had plenty of issues<br>
> > > > > > deploying on bare metal HA servers, and have paused the deployment<br>
> > > > > > using TripleO until better winds start to flow here. I was able to<br>
> > > > > > deploy the QuickStart, but on bare metal the history was different.<br>
> > > > > > Couldn't even deploy a two server configuration.<br>
> > > > > ><br>
> > > > > > I was thinking that it would be good to have the developers have<br>
> > > > > > access to one of our environments and go through a full install<br>
> > with<br>
> > > > > > us to better see where things fail. We can do this handholding<br>
> > > > > > deployment once every week/month based on developers time<br>
> > > > > > availability. That way we can get a working install, and we can<br>
> > > > > > troubleshoot real life environment problems.<br>
> > > > > ><br>
> > > > > ><br>
> > > > > > IB<br>
> > > > > ><br>
> > > > > > On Jun 3, 2016, at 6:15 AM, Pedro Sousa <<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>> wrote:<br>
> > > > > ><br>
> > > > > > > Yes. I've used this, but I'll try again as there's seems to be<br>
> > new<br>
> > > > > > > updates.<br>
> > > > > > ><br>
> > > > > > ><br>
> > > > > > ><br>
> > > > > > > Stable Branch Skip all repos mentioned above, other than epel-<br>
> > > > > > > release which is still required.<br>
> > > > > > > Enable latest RDO Stable Delorean repository for all packages<br>
> > > > > > > sudo curl -o /etc/yum.repos.d/delorean-liberty.repo<br>
> > <a href="https://trunk.r" rel="noreferrer" target="_blank">https://trunk.r</a><br>
> > > > > > > <a href="http://doproject.org/centos7-liberty/current/delorean.repo" rel="noreferrer" target="_blank">doproject.org/centos7-liberty/current/delorean.repo</a><br>
> > > > > > > Enable the Delorean Deps repository<br>
> > > > > > > sudo curl -o /etc/yum.repos.d/delorean-deps-liberty.repo<br>
> > <a href="http://tru" rel="noreferrer" target="_blank">http://tru</a><br>
> > > > > > > <a href="http://nk.rdoproject.org/centos7-liberty/delorean-deps.repo" rel="noreferrer" target="_blank">nk.rdoproject.org/centos7-liberty/delorean-deps.repo</a><br>
> > > > > > ><br>
> > > > > > > On Fri, Jun 3, 2016 at 11:10 AM, Christopher Brown <<br>
> > <a href="mailto:cbrown2@ocf.co">cbrown2@ocf.co</a>.<br>
> > > > > > > uk> wrote:<br>
> > > > > > > > No, Liberty deployed ok for us.<br>
> > > > > > > ><br>
> > > > > > > > It suggests to me a package mismatch. Have you completely<br>
> > rebuilt<br>
> > > > > > > > the<br>
> > > > > > > > undercloud and then the images using Liberty?<br>
> > > > > > > ><br>
> > > > > > > > On Fri, 2016-06-03 at 11:04 +0100, Pedro Sousa wrote:<br>
> > > > > > > > > AttributeError: 'module' object has no attribute 'PortOpt'<br>
> > > > > > > > --<br>
> > > > > > > > Regards,<br>
> > > > > > > ><br>
> > > > > > > > Christopher Brown<br>
> > > > > > > > OpenStack Engineer<br>
> > > > > > > > OCF plc<br>
> > > > > > > ><br>
> > > > > > > > Tel: <a href="tel:%2B44%20%280%29114%20257%202200" value="+441142572200">+44 (0)114 257 2200</a><br>
> > > > > > > > Web: <a href="http://www.ocf.co.uk" rel="noreferrer" target="_blank">www.ocf.co.uk</a><br>
> > > > > > > > Blog: <a href="http://blog.ocf.co.uk" rel="noreferrer" target="_blank">blog.ocf.co.uk</a><br>
> > > > > > > > Twitter: @ocfplc<br>
> > > > > > > ><br>
> > > > > > > > Please note, any emails relating to an OCF Support request must<br>
> > > > > > > > always<br>
> > > > > > > > be sent to <a href="mailto:support@ocf.co.uk">support@ocf.co.uk</a> for a ticket number to be<br>
> > generated<br>
> > > > > > > > or<br>
> > > > > > > > existing support ticket to be updated. Should this not be done<br>
> > > > > > > > then OCF<br>
> > > > > > > ><br>
> > > > > > > > cannot be held responsible for requests not dealt with in a<br>
> > > > > > > > timely<br>
> > > > > > > > manner.<br>
> > > > > > > ><br>
> > > > > > > > OCF plc is a company registered in England and Wales.<br>
> > Registered<br>
> > > > > > > > number<br>
> > > > > > > ><br>
> > > > > > > > 4132533, VAT number GB 780 6803 14. Registered office address:<br>
> > > > > > > > OCF plc,<br>
> > > > > > > ><br>
> > > > > > > > 5 Rotunda Business Centre, Thorncliffe Park, Chapeltown,<br>
> > > > > > > > Sheffield S35<br>
> > > > > > > > 2PG.<br>
> > > > > > > ><br>
> > > > > > > > If you have received this message in error, please notify us<br>
> > > > > > > > immediately and remove it from your system.<br>
> > > > > > > ><br>
> > > > > ><br>
> > > > > > _______________________________________________<br>
> > > > > > rdo-list mailing list<br>
> > > > > > <a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a><br>
> > > > > > <a href="https://www.redhat.com/mailman/listinfo/rdo-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
> > > > > ><br>
> > > > > > To unsubscribe: <a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a><br>
> > > > > --<br>
> > > > > Regards,<br>
> > > > ><br>
> > > > > Christopher Brown<br>
> > > > > OpenStack Engineer<br>
> > > > > OCF plc<br>
> > > > ><br>
> > > > > Tel: <a href="tel:%2B44%20%280%29114%20257%202200" value="+441142572200">+44 (0)114 257 2200</a><br>
> > > > > Web: <a href="http://www.ocf.co.uk" rel="noreferrer" target="_blank">www.ocf.co.uk</a><br>
> > > > > Blog: <a href="http://blog.ocf.co.uk" rel="noreferrer" target="_blank">blog.ocf.co.uk</a><br>
> > > > > Twitter: @ocfplc<br>
> > > > ><br>
> > > > > Please note, any emails relating to an OCF Support request must<br>
> > always<br>
> > > > > be sent to <a href="mailto:support@ocf.co.uk">support@ocf.co.uk</a> for a ticket number to be generated or<br>
> > > > > existing support ticket to be updated. Should this not be done then<br>
> > OCF<br>
> > > > ><br>
> > > > > cannot be held responsible for requests not dealt with in a timely<br>
> > > > > manner.<br>
> > > > ><br>
> > > > > OCF plc is a company registered in England and Wales. Registered<br>
> > number<br>
> > > > ><br>
> > > > > 4132533, VAT number GB 780 6803 14. Registered office address: OCF<br>
> > plc,<br>
> > > > ><br>
> > > > > 5 Rotunda Business Centre, Thorncliffe Park, Chapeltown, Sheffield<br>
> > S35<br>
> > > > > 2PG.<br>
> > > > ><br>
> > > > > If you have received this message in error, please notify us<br>
> > > > > immediately and remove it from your system.<br>
> > > > ><br>
> > > > > _______________________________________________<br>
> > > > > rdo-list mailing list<br>
> > > > > <a href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a><br>
> > > > > <a href="https://www.redhat.com/mailman/listinfo/rdo-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
> > > > ><br>
> > > > > To unsubscribe: <a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a><br>
> > > > ><br>
> > > ><br>
> > ><br>
> ><br>
><br>
</div></div></blockquote></div><br></div>