Versions Compared

Old Version 51

changes.mady.by.user Samir Raval

Saved on

compared with

New Version Current

changes.mady.by.user Jelon Anderson (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Repair Jira Macros

...

FolderTest Files

Pool

BadConnect.yaml – FAIL – DAOS issue -

Jira Legacy
serverHPDD Community JiraSystem JIRA
serverId8bba2dd1f325724b-4333f7c9-300634db-bfcdbd1c-f35d4ebbd2ad69d12ec98a69
keyDAOS-1691

BadCreate.yaml – FAIL – DAOS issue-

Jira Legacy
serverHPDD Community JiraSystem JIRA
serverId8bba2dd1f325724b-4333f7c9-300634db-bfcdbd1c-f35d4ebbd2ad69d12ec98a69
keyDAOS-1705

BadEvict.yaml – FAIL - TEST issue -

Jira Legacy
serverHPDD Community JiraSystem JIRA
serverId8bba2dd1f325724b-4333f7c9-300634db-bfcdbd1c-f35d4ebbd2ad69d12ec98a69
keyDAOS-1709
- This looks like Test defect. After investigation this can be assigned to Dev, if it's DAOS side issue.

BadExclude.yaml - FAIL - TEST issue -

Jira Legacy
serverHPDD Community JiraSystem JIRA
serverId8bba2dd1f325724b-4333f7c9-300634db-bfcdbd1c-f35d4ebbd2ad69d12ec98a69
keyDAOS-1711

BadQuery.yaml - PASS

ConnectTest.yaml – FAIL - Test issue -

Jira Legacy
serverHPDD Community JiraSystem JIRA
serverId8bba2dd1f325724b-4333f7c9-300634db-bfcdbd1c-f35d4ebbd2ad69d12ec98a69
keyDAOS-1718
- Tried with socket with NVMe and it's working fine.

DestroyRebuild.yaml – Need 6 Serves - FAIL - This will not work until we get pool destroy fix

Jira Legacy
serverSystem JIRA
serverIdf325724b-f7c9-34db-bd1c-69d12ec98a69
keyDAOS-1811
There is existing defect open for same test
Jira Legacy
serverSystem JIRA
serverIdf325724b-f7c9-34db-bd1c-69d12ec98a69
keyDAOS-989

DestroyTests.yaml - Need 6 Servers - FAIL - This will not work until we get pool destroy fix

Jira Legacy
serverSystem JIRA
serverIdf325724b-f7c9-34db-bd1c-69d12ec98a69
keyDAOS-1811
Jira Legacy
serverSystem JIRA
serverIdf325724b-f7c9-34db-bd1c-69d12ec98a69
keyDAOS-1691

EvictTest.yaml - PASS

GlobalHandle.yaml - PASS

InfoTests.yaml - FAIL - DAOS issue -

Jira Legacy
serverHPDD Community JiraSystem JIRA
serverId8bba2dd1f325724b-4333f7c9-300634db-bfcdbd1c-f35d4ebbd2ad69d12ec98a69
keyDAOS-1722

MultipleCreatesTest.yaml - PASS

MultiServerCreateDeleteTest.yaml - PASS

Permission.yaml - FAIL - DAOS issue -

Jira Legacy
serverHPDD Community JiraSystem JIRA
serverId8bba2dd1f325724b-4333f7c9-300634db-bfcdbd1c-f35d4ebbd2ad69d12ec98a69
keyDAOS-1722

PoolSvc.yaml – FAIL - TEST issue -

Jira Legacy
serverHPDD Community JiraSystem JIRA
serverId8bba2dd1f325724b-4333f7c9-300634db-bfcdbd1c-f35d4ebbd2ad69d12ec98a69
keyDAOS-1242

RebuildNoCap.yaml – Need 6 Servers - FAIL - TEST issue -

Jira Legacy
serverSystem JIRA
serverIdf325724b-f7c9-34db-bd1c-69d12ec98a69
keyDAOS-1846
, Now the Pool should be too full to start a rebuild and it should return rebuild failure error as per test. Confirm with Scott on expected behavior of tests.

RebuildTests.yaml – Need 6 Servers - DAOS issue - FAIL -

Jira Legacy
serverSystem JIRA
serverIdf325724b-f7c9-34db-bd1c-69d12ec98a69
keyDAOS-1828

RebuildWithIO.yaml – PASS - Need 6 Servers

SimpleCreateDeleteTest.yaml - PASS

Object

ArrayObjTest.yaml - PASS

CreateManyDkeys.yaml - PASS

ObjFetchBadParam.yaml - PASS

ObjUpdateBadParam.yaml - PASS

PunchTest.yaml - PASS

Container

Open.yaml - PASS - It's required some minor modification in Tear down code to work with NVMe, disconnecting the pool before destroying it works fine in SCM but not in NVME

Jira Legacy
serverHPDD Community JiraSystem JIRA
serverId8bba2dd1f325724b-4333f7c9-300634db-bfcdbd1c-f35d4ebbd2ad69d12ec98a69
keyDAOS-1691
. Eventually test case will need update.

OpenClose.yaml - Need 4 Servers - FAIL - Test Issue -

Jira Legacy
serverHPDD Community JiraSystem JIRA
serverId8bba2dd1f325724b-4333f7c9-300634db-bfcdbd1c-f35d4ebbd2ad69d12ec98a69
keyDAOS-1799

ContainerAsync.yaml – Need 4 servers - PASS - DAOS issue -

Jira Legacy
serverSystem JIRA
serverIdf325724b-f7c9-34db-bd1c-69d12ec98a69
keyDAOS-1811
- Defect Verified.

GlobalHandle.yaml - PASS

Attribute.yaml - PASS

BasicEpochTest.yaml - PASS

Delete.yaml – FAIL -test Issue -

Jira Legacy
serverHPDD Community JiraSystem JIRA
serverId8bba2dd1f325724b-4333f7c9-300634db-bfcdbd1c-f35d4ebbd2ad69d12ec98a69
keyDAOS-1789
- Make sure to use 1G pool size for NVMe. Add pool.disconnect() if this test required to be ran with NVMe

FullPoolContainerCreate.yaml - FAIL - Test Issue -

Jira Legacy
serverHPDD Community JiraSystem JIRA
serverId8bba2dd1f325724b-4333f7c9-300634db-bfcdbd1c-f35d4ebbd2ad69d12ec98a69
keyDAOS-1768
- This test will not work with NVMe as minimum size of pool on NVMe is 1G where in test it's 16MB


SimpleCreateDeleteTest.yaml – Need 6 Servers - PASS - Pool Destroy issue observer for which

Jira Legacy
serverSystem JIRA
serverIdf325724b-f7c9-34db-bd1c-69d12ec98a69
keyDAOS-1811
- Verified Defect.

io

IorSingleServer.yaml - FAIL PASS - DAOS issue -

Jira Legacy
serverHPDD Community JiraSystem JIRA
serverId8bba2dd1f325724b-4333f7c9-300634db-bfcdbd1c-f35d4ebbd2ad69d12ec98a69
keyDAOS-1791
- Need to update the TC if it fails again but it's working OK. Increase the pool size or put some delay in between IOR as per defect

repoRepoTest.yaml - Not Executed - It's not DAOS function test
serverServerLaunch.yaml - Not Executed - It's only server start which works in TestSetup() part of most of the test cases
unittestUnittest.yaml - Not Executed - It's Unit tests so not needed to run against NVMe

Current Automation tests with NVMe:

Option 1: 

  1. We can identified the *.yaml file to be ran with NVMe
  2. Update the NVMe config parameter in yaml file.
  3. Update the tags to run on *.yaml NVMe hardware.

Option 2:

...