Description of problem:
Errors in configuration can cause the loading script to stop loading the rest.
This bug is a split of bug 1649877

Version-Release number of selected component (if applicable):
ipset-6.38-3.el7_6.x86_64
ipset-6.38-2.el7.x86_64

How reproducible:
always

Steps to Reproduce:
mkdir /etc/sysconfig/ipset.d/
cat > /etc/sysconfig/ipset.d/a.set <<EOF
create a hash:ip family inet hashsize 1024 maxelem 50
add a 10.20.30.40
EOF
cat > /etc/sysconfig/ipset.d/b.set  <<EOF
create b hash:ip family inet hashsize 1024 maxelem 50
invalid string
add b 10.20.30.41
EOF
cat > /etc/sysconfig/ipset.d/c.set  <<EOF
create c hash:ip family inet hashsize 1024 maxelem 50
add c 10.20.30.42
EOF

systemctl restart ipset
ipset list | egrep Name\|Number
Name: a
Number of entries: 0
Name: b
Number of entries: 0
Name: c
Number of entries: 0
# here there should have been always a 1 entry

echo 'invalid string' > /etc/sysconfig/ipset.d/b.set
systemctl restart ipset
ipset list | egrep Name\|Number
Name: a
Number of entries: 0
# no members and set 'c' is missing

rm /etc/sysconfig/ipset.d/b.set
mkdir /etc/sysconfig/ipset.d/00dir
systemctl restart ipset
ipset list | egrep Name\|Number
Name: a
Number of entries: 1
Name: c
Number of entries: 1

Expected results:
* set members are always present for created sets
* error in file similar to 'b.set' with 'invalid string' does not prevent rest of the sets to be loaded and populated correctly

Additional info: