Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Infrastructure nodes should not count as scan job nodes #5081

Open
gscho opened this issue May 18, 2021 · 0 comments
Open

Infrastructure nodes should not count as scan job nodes #5081

gscho opened this issue May 18, 2021 · 0 comments
Labels

Comments

@gscho
Copy link

gscho commented May 18, 2021

Describe the bug

When you configure a node to report chef client run data to Automate, it creates a new node object which is shown in the Infrastructure -> Client Runs section. It also will show up as an added node in the Compliance -> Scan Jobs -> Nodes Added section but it will not show in the actual list of "added" nodes. This is confusing for users.

To Reproduce

Steps to reproduce the behavior:
(Easiest to see from a fresh automate install)

  • Bootstrap a new node and see it report its run data to chef automate
  • Total nodes will be shown as 1
  • Head over to Compliance -> Scan Jobs -> Nodes Added tab
  • All nodes will show 1
  • The list of added nodes will be empty.

Expected behavior

The list of "all nodes" should show all added nodes and not all nodes.

Versions (please complete the following information):

  • Automate Build Number: 20210504084406

Aha! Link: https://chef.aha.io/epics/SH-E-522

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants