So this is an attempt to fix everything in Puppet modules: * https://github.com/puppetlabs/puppetlabs-stdlib/pull/577 * https://github.com/puppetlabs/puppetlabs-rabbitmq/pull/443
If we have the patches like this, there will be no need to patch TripleO. Please review the patches if needed, Thanks On Tue, Mar 15, 2016 at 1:57 PM, Emilien Macchi <[email protected]> wrote: > So from now, we pin [5] puppetlabs-rabbitmq to the commit before [3] > and I rebased Attila's patch to test CI again. > This pin is a workaround, in the meantime we are working on a fix in > puppetlabs-rabbitmq. > > [5] https://review.openstack.org/293074 > > I also reported the issue in TripleO Launchpad: > https://bugs.launchpad.net/tripleo/+bug/1557680 > > Also a quick note: > Puppet OpenStack CI did not detect this failure because we don't > deploy puppetlabs-rabbitmq from master but from the latest release > (tag). > > On Tue, Mar 15, 2016 at 1:17 PM, Emilien Macchi <[email protected]> wrote: >> TL;DR;This e-mail tracks down the work done to make RabbitMQ working >> on IPv6 deployments. >> It's currently broken and we might need to patch different Puppet >> modules to make it work. >> >> Long story: >> >> Attila Darazs is currently working on [1] to get IPv6 tested by >> TripleO CI but is stuck because a RabbitMQ issue in Puppet catalog >> [2], reported by Dan Sneddon. >> [1] https://review.openstack.org/#/c/289445 >> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1317693 >> >> [2] is caused by a patch in puppetlabs-rabbitmq [3], that change the >> way we validate RabbitMQ is working from testing localhost to testing >> the actual binding IP. >> [3] >> https://github.com/puppetlabs/puppetlabs-rabbitmq/commit/dac8de9d95c5771b7ef7596b73a59d4108138e3a >> >> The problem is that when testing the actual IPv6, it curls fails for >> some different reasons explained on [4] by Sofer. >> [4] https://review.openstack.org/#/c/292664/ >> >> So we need to investigate puppetlabs-rabbitmq and puppet-staging to >> see if whether or not we need to change something there. >> For now, I don't think we need to patch anything in TripleO Heat >> Templates, but we'll see after the investigation. >> >> I'm currently working on this task, but any help is welcome, >> -- >> Emilien Macchi > > > > -- > Emilien Macchi -- Emilien Macchi __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
