Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Updated documentation #2

Merged
merged 2 commits into from
Nov 26, 2020
Merged

Updated documentation #2

merged 2 commits into from
Nov 26, 2020

Conversation

nam-jaehyun
Copy link
Collaborator

Updated documentation

@nam-jaehyun nam-jaehyun merged commit 4c0910a into kubearmor:master Nov 26, 2020
haytok added a commit to haytok/KubeArmor that referenced this pull request Jun 12, 2023
The following errors occur when executing KubeArmor/KubeArmor/build/test_kubearmor.sh
or go test in the directory KubeArmor/KubeArmor/monitor.

  > go test
  # github.com/kubearmor/KubeArmor/KubeArmor/monitor
  ./systemMonitor.go:343:4: (*github.com/kubearmor/KubeArmor/KubeArmor/feeder.Feeder).Warnf format %+v reads arg kubearmor#2, but call has 1 arg
  ./systemMonitor.go:347:4: (*github.com/kubearmor/KubeArmor/KubeArmor/feeder.Feeder).Warnf format %+v reads arg kubearmor#2, but call has 1 arg
  ./systemMonitor.go:351:4: (*github.com/kubearmor/KubeArmor/KubeArmor/feeder.Feeder).Warnf format %+v reads arg kubearmor#2, but call has 1 arg
  ./systemMonitor.go:355:4: (*github.com/kubearmor/KubeArmor/KubeArmor/feeder.Feeder).Warnf format %+v reads arg kubearmor#2, but call has 1 arg
  FAIL  github.com/kubearmor/KubeArmor/KubeArmor/monitor [build failed]

This commit corrects the process in KubeArmor/monitor/systemMonitor.go
so that the test can be executed normally.

When running the test, the error occurs when calling mon.Logger.Warnf()
, which is called in the UpdateNsKeyMap(). This error occurs due to
missing arguments.

The current implementation does not properly output the message. Also, the
test cannot be executed.

Therefore, we will modify it so that this error is not output when
mon.Logger.Warnf() is called.

Also, when the test was run again with this modification, an error occurred
in DestroyBPFMaps() due to a nil check failure of mon.BpfNsVisibilityMap.

Therefore, the logic to check for nil in DestroyBPFMaps() is also corrected.

Signed-off-by: Hayato Kiwata <simplelpmis6@gmail.com>
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants