fix: CVE-2021-3997 in image build

[andyzhangx]

What type of PR is this?
/kind bug

What this PR does / why we need it:
fix: CVE-2021-3997 in image build, fixed following image CVE:

https://github.com/kubernetes-csi/csi-driver-iscsi/runs/4810456604?check_suite_focus=true

test/iscsi-csi:latest (ubuntu 20.04)
====================================
Total: 2 (UNKNOWN: 0, LOW: 0, MEDIUM: 2, HIGH: 0, CRITICAL: 0)

+-------------+------------------+----------+-------------------+-------------------+--------------------------------------+
|   LIBRARY   | VULNERABILITY ID | SEVERITY | INSTALLED VERSION |   FIXED VERSION   |                TITLE                 |
+-------------+------------------+----------+-------------------+-------------------+--------------------------------------+
| libsystemd0 | CVE-2021-3997    | MEDIUM   | 245.4-4ubuntu3.14 | 245.4-4ubuntu3.15 | systemd: Uncontrolled recursion in   |
|             |                  |          |                   |                   | systemd-tmpfiles when removing files |
|             |                  |          |                   |                   | -->avd.aquasec.com/nvd/cve-2021-3997 |
+-------------+                  +          +                   +                   +                                      +
| libudev1    |                  |          |                   |                   |                                      |
|             |                  |          |                   |                   |                                      |
|             |                  |          |                   |                   |                                      |
+-------------+------------------+----------+-------------------+-------------------+--------------------------------------+

iscsiplugin (gobinary)
======================
Total: 0 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0)

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

fix: CVE-2021-3997 in image build

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andyzhangx]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[andyzhangx]

@humblec I realized we don't have an e2e test for this repo, is it possible to set up a containerized iscsi server and then add e2e tests, I could help set up the test pipeline if there is a solution.

[humblec]

@humblec I realized we don't have an e2e test for this repo, is it possible to set up a containerized iscsi server and then add e2e tests, I could help set up the test pipeline if there is a solution.

Yeah, have to experiment e2e. We will cut a alpha release and between alpha to GA we will bring up the e2e . . wdyt?

[humblec]

/lgtm

[andyzhangx]

@humblec I realized we don't have an e2e test for this repo, is it possible to set up a containerized iscsi server and then add e2e tests, I could help set up the test pipeline if there is a solution.

Yeah, have to experiment e2e. We will cut a alpha release and between alpha to GA we will bring up the e2e . . wdyt?

@humblec lgtm, with an e2e test pipeline, I would be more confident when I make code change.

[humblec]

@humblec I realized we don't have an e2e test for this repo, is it possible to set up a containerized iscsi server and then add e2e tests, I could help set up the test pipeline if there is a solution.

Yeah, have to experiment e2e. We will cut a alpha release and between alpha to GA we will bring up the e2e . . wdyt?

@humblec lgtm, with an e2e test pipeline, I would be more confident when I make code change.

Agreed. !