in our current gating we have the following results:
 

• core healthchecks are FAIl due to 
  Basic DMAAP Bus Controller Health Check With Basic Auth | FAIL |
  503 != 200
   
• small healthchecks arre FAIL due to
  Basic DMAAP Bus Controller Health Check With Basic Auth | FAIL |
  503 != 200
  Basic AAF SMS Health Check                              | FAIL |
  No keyword with name 'dev-aaf' found.
   
  I can see that gating and integration daily (http://onapci.org/logs/windriver-rke-staging-daily/15/report.html#totals?critical) have both the error on this new Dmaap test. 
  A patch in progress on AAF should fix the issue on gating (it is OK on integration)
   
  the new Dmaap use case has been added 16 days ago by Piotr (https://github.com/onap/testsuite/blame/master/robot/testsuites/health-check.robot)
   
  as it is not working on both gating and daily integration, would it make sense to remove the "core" tag?
  For me core healthchecks correpond to critical healthchecks => if it is FAIL it means that the system is not usable at all.
  I assume here that it is not the case.
   
  If we remove the core tag and keep all the others (health, dev-dmaap), it will still be tested (in full healthcheck) but will not prevent the trigger of End to End tests.
   
  In fact today, the success of core healthchecks is mandatory to trigger the End to End use cases (and then be able to check that the cleaning operations is now OK)