Bug 1478081

Summary:	/etc/ppp/ipv6-down does not run ipv6-down.local
Product:	[Fedora] Fedora	Reporter:	Antonin <antonin.vecera>
Component:	ppp	Assignee:	Michal Sekletar <msekleta>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	27	CC:	jskarvad, jsynacek, msekleta, thozza
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-30 18:49:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Antonin 2017-08-03 14:29:19 UTC

Description of problem:
ppp daemon on exit run /etc/ppp/ipv6-down script. This script should call local script "/etc/ppp/ipv6-down.local".
But this execution depends on existence of file "/etc/sysconfig/network-scripts/ifcfg-ppp0". If this file does not exist then "ipv6-down.local" is not started.

I found that it helps to change the shell (first line) in file "ipv6-down" from /bin/sh to /bin/bash. (#!/bin/bash)
The twins file /etc/ppp/ipv6-up in current package already has interpreter set to /bin/bash.

Version-Release number of selected component (if applicable):
ppp-2.4.7-11.fc26.x86_64

How reproducible:


Steps to Reproduce:
1. don't use (remove) /etc/sysconfig/network-scripts/ifcfg-ppp0
2. create /etc/ppp/ipv6-down.local
3. pppd call provider
4. killall pppd

Actual results:
"/etc/ppp/ipv6-down" exits early and does not run local script "/etc/ppp/ipv6-down.local".

Expected results:
call ipv6-down.local


Additional info:

My ppp config file /etc/ppp/peers/provider:

plugin rp-pppoe.so
eno1
user USER
password PASSWORD
noauth
noipdefault
defaultroute
ipparam ppp0
lcp-echo-interval 20
lcp-echo-failure 3
maxfail 720
persist
unit 0
+ipv6

Comment 1 Ben Cotton 2018-11-27 17:46:19 UTC

This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2018-11-30 18:49:22 UTC

Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.