Pacemaker on Wily vs. Xenial

[Mark Haney]

Actually, I never tested it on 14.04.  I was testing it on 15.10, which is
where the service.d and uidgid.d directories *are* created.  Those are
definitely not created in the 16.04 install.  The example files I'm not
worried about, to be honest.  I will see about testing manually creating
those directories and seeing if pacemaker will start.  (I honestly don't
think it will, but I've slept since then.)

It's just strange that those two directories would be missing since I can't
find anything in the changelogs between 1.1.12 and 1.1.14 to explain why
they would be.



On Wed, Apr 27, 2016 at 4:30 AM, Tom H <tomh0665 at gmail.com> wrote:

> On Mon, Apr 25, 2016 at 4:41 PM, Mark Haney <mark.haney at vifprogram.com>
> wrote:
> >
> > I've noticed something odd about the Pacemaker installation between Wily
> and
> > Xenial.  This has been something I've seen since late February, but I'm
> not
> > certain it's a bug/problem.
> >
> > Originally I started testing a floating IP failover setup with Pacemaker
> on
> > 15.10 and found that the 'crm' commands failed to work due to some sort
> of
> > version mismatch. So, I upgraded them to 16.04 beta to be able to setup
> the
> > resources and test.  It wasn't until I built a 16.04 Beta VM from scratch
> > that I noticed the difference.  For example, in 15.10, this is the
> contents
> > of the /etc/corosync/ directory:
> >
> > root at marcellus:~# lxc exec wily -- /bin/bash
> > root at wily:~# ls /etc/corosync/
> > corosync.conf  corosync.conf.example  corosync.conf.example.udpu
> service.d
> > uidgid.d
> >
> > But, in 16.04 the directory is all but empty:
> >
> > root at xenial-2:~# ls /etc/corosync/
> > corosync.conf
> >
> > Now, this isn't a dealbreaker as far as I can tell, except for one thing,
> > the documentation requires me to setup the pcmk file inside
> > /etc/corosync/service.d/ with the pacemaker version information.  If it's
> > not there, I can't get pacemaker to start.
> >
> > The only way I've been able to get this to work is to install 15.10,
> install
> > pacemaker, upgrade to 16.04 and all is well.
> >
> > I'm no pacemaker expert (which is why I'm testing it), but it seems like
> the
> > 16.04 base install package is broken.  Is there something I'm
> overlooking?
> > I've not seen docs specific to 16.04's pacemaker version so I've had to
> rely
> > on the 15.10 docs out there.  But the versions aren't that different
> > (1.1.12/Wily, 1.1.14/Xenial), so I can't imagine there's been a massive
> > change between the two.
>
> The example files have been moved to "/usr/share/doc/corosync/examples/".
>
> I've looked at corosync's "./debian/" directory for 14.04 and there's
> nothing in rules, preinst, or postinst (or install) about
> "/etc/corosync/service.d/".
>
> I've gripped through 14.04's "Contents-amd64.gz" for
> "corosync/service" and there's no sign of "/etc/corosync/service.d/".
>
> Did you create it manually on 14.04? Does another program create it
> without including it in its "owned" files/directories"?
>
> Does corosync run if you create it manually? (Hopefully!)
>
> Maybe it's worth filing a bug report asking for this directory to be
> created at install.
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>



-- 

Mark Haney ::: Senior Systems Engineer
*VIF* *International Education*
P.O. Box 3566 ::: Chapel Hill, N.C. 27515 ::: USA
919-265-5006 office

Global learning for all.
www.viflearn.com
Find VIF on Facebook <http://facebook.com/VIFInternationalEducation> |
Twitter <https://twitter.com/vifglobaled> | LinkedIn
<http://www.linkedin.com/company/vif-international-education>

Recognized as a ‘Best for the World’
<http://bestfortheworld.bcorporation.net/> B Corp!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20160427/7fe0d99c/attachment.html>