Hide Forgot
Description of problem: ----------------------- systemctl status shows a broken link for Docs : <snip> [root@gqas006 /]# systemctl status pacemaker ● pacemaker.service - Pacemaker High Availability Cluster Manager Loaded: loaded (/usr/lib/systemd/system/pacemaker.service; disabled; vendor preset: disabled) Active: active (running) since Fri 2018-03-02 01:08:00 EST; 1min 7s ago Docs: man:pacemakerd http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Explained/index.html Main PID: 3873 (pacemakerd) CGroup: /system.slice/pacemaker.service ├─3873 /usr/sbin/pacemakerd -f ├─3874 /usr/libexec/pacemaker/cib ├─3875 /usr/libexec/pacemaker/stonithd ├─3876 /usr/libexec/pacemaker/lrmd ├─3877 /usr/libexec/pacemaker/attrd ├─3878 /usr/libexec/pacemaker/pengine └─3879 /usr/libexec/pacemaker/crmd </snip> http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Explained/index.html - This does not work Version-Release number of selected component (if applicable): -------------------------------------------------------------- pacemaker-1.1.18-11.el7.x86_64 How reproducible: ----------------- 100%
Created attachment 1402898 [details] Screenshot
Thanks for catching this! The upstream site moved some files around recently. The correct URL is now: https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Explained/index.html
Fixed by upstream commit e947893
As of pacemaker-1.1.18-13.el7, the pacemaker_remote unit file is also fixed.
before: ======= > [root@virt-261 ~]# rpm -q pacemaker pacemaker-remote > pacemaker-1.1.18-11.el7.x86_64 > pacemaker-remote-1.1.18-11.el7.x86_64 > [root@virt-261 ~]# systemctl status pacemaker > ● pacemaker.service - Pacemaker High Availability Cluster Manager > Loaded: loaded (/usr/lib/systemd/system/pacemaker.service; disabled; vendor preset: disabled) > Active: inactive (dead) > Docs: man:pacemakerd > http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Explained/index.html > [root@virt-261 ~]# curl -sI http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Explained/index.html | head -n 1 > HTTP/1.1 301 Moved Permanently > [root@virt-261 ~]# systemctl status pacemaker_remote > ● pacemaker_remote.service - Pacemaker Remote Service > Loaded: loaded (/usr/lib/systemd/system/pacemaker_remote.service; disabled; vendor preset: disabled) > Active: inactive (dead) > Docs: man:pacemaker_remoted > http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Remote/index.html > [root@virt-261 ~]# curl -sI http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Remote/index.html | head -n 1 > HTTP/1.1 301 Moved Permanently Both documentation URLs get redirected to a generic "not found" page. after: ====== > [root@virt-153 ~]# rpm -q pacemaker pacemaker-remote > pacemaker-1.1.19-3.el7.x86_64 > pacemaker-remote-1.1.19-3.el7.x86_64 > [root@virt-153 ~]# systemctl status pacemaker > ● pacemaker.service - Pacemaker High Availability Cluster Manager > Loaded: loaded (/usr/lib/systemd/system/pacemaker.service; disabled; vendor preset: disabled) > Active: inactive (dead) > Docs: man:pacemakerd > https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Explained/index.html > [root@virt-153 ~]# curl -sI https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Explained/index.html | head -n 1 > HTTP/1.1 200 OK > [root@virt-153 ~]# systemctl status pacemaker_remote > ● pacemaker_remote.service - Pacemaker Remote Service > Loaded: loaded (/usr/lib/systemd/system/pacemaker_remote.service; disabled; vendor preset: disabled) > Active: inactive (dead) > Docs: man:pacemaker-remoted > https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Remote/index.html > [root@virt-153 ~]# curl -sI https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Remote/index.html | head -n 1 > HTTP/1.1 200 OK Both pacemaker and pacemaker_remote systemd unit files contain a working documentation URL. Marking verified in 1.1.19-3.el7.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3055