Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Blocking Issues with No Workaround

Jira
serverONAP JIRA
columnskey,summary,created,updated,assignee,reporter,priority,status,labels
maximumIssues50
jqlQuerystatus != Closed AND (project = Test OR labels = Integration) AND issuetype = Bug AND affectedVersion = "frankfurt Release" AND priority = Highest ORDER BY priority DESC, updated DESC
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Integration High Priority Issues

Jira
serverONAP JIRA
columnskey,summary,created,updated,assignee,reporter,priority,status,labels
maximumIssues50
jqlQuerystatus != Closed AND status != Done AND (project = Test OR labels = Integration AND labels != healthcheck) AND issuetype = Bug AND fixVersion = "Frankfurt Release" AND priority = High ORDER BY key, priority DESC, updated DESC
serverId425b2b0a-557c-3c0c-b515-579789cceedb


HTTP/HTTPS security follow-up

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuerylabels in (integration) and labels in (security) AND labels in (HTTPS) AND fixVersion = "Frankfurt Release"
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Note security scans are tested on evey gating and on Master Daily (a dashboard to master daily has to be done and referenced) to view if the fixes have been integrated in OOM Master.

The results can be found in the file http_public_endpoints.log

A white list must be implemented to exclude some pods (robot, sniro, aaf)

Rooted pods security follow-up

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuerylabels in (integration) and labels in (security) AND labels in (root) AND fixVersion = "Frankfurt Release"
serverId425b2b0a-557c-3c0c-b515-579789cceedb

results can be found in gating and daily master in root_pods.log

For Frankfurt the focus must be done on our dockers

Upstream docker can be excluded.

Please note that the test check that the default user is not root. In some case the user exists but the main process is not launched as root (REQ-215 is fine even if it is usually simplifier to delete the root user..)