RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
I have seen following issues with flannel on rhel7:

1. When flannel is uninstalled, the dir /usr/libexec/flannel is not cleaned up.

2. Env var used for the flags etcd-endpoints and etcd-prefix are not canonical:

The correct ones are:
etcd-endpoints:  FLANNELD_ETCD_ENDPOINTS
etcd-prefix: FLANNELD_ETCD_PREFIX

The flannel rpm uses:
etcd-endpoints: FLANNEL_ETCD
etcd-prefix: FLANNEL_ETCD_KEY

Version-Release number of selected component (if applicable):
0.5.3-9.el7

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

As this is RFE, let's make the flannel more shiny not before 7.3.

So I don't think systemd variable expansion handles that syntax...

I think we'd have to make a helper script which runs bash to handle this...

I'd rather we just doc'd it, but if we have to fix it, I think it needs to be a helper script called by ExecStart which actually launches flannel a Jan suggested...

Test with flannel-0.5.5-2 and the uninstall and conf files are all as expect.

Details:
1. use ls to check flannel after uninstall:
# ls /usr/libexec/flannel
ls: cannot access /usr/libexec/flannel: No such file or directory

2. flannel conf file content:

# Flanneld configuration options  

# etcd url location.  Point this to the server where etcd runs
FLANNEL_ETCD_ENDPOINTS="https://127.0.0.1:2379"

# etcd config key.  This is the configuration key that flannel queries
# For address range assignment
FLANNEL_ETCD_PREFIX="/atomic.io/network"
....

So set this to verified.