Update patch set 1

Patch Set 1: Workflow-1

(1 comment)

Patch-set: 1
Reviewer: Gerrit User 20870 <20870@4a232e18-c5a9-48ee-94c0-e04e7cca6543>
Label: Workflow=-1, bdf0337a404a4914dc8e0d895fc08fee0676fd97
Attention: {"person_ident":"Gerrit User 20870 \u003c20870@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"REMOVE","reason":"\u003cGERRIT_ACCOUNT_20870\u003e replied on the change"}
This commit is contained in:
Gerrit User 20870 2023-11-08 19:30:17 +00:00 committed by Gerrit Code Review
parent 224c4524c2
commit d302553f20
1 changed files with 17 additions and 0 deletions

View File

@ -50,6 +50,23 @@
"message": "charm-recheck",
"revId": "d1bfa2f87812dd2a1511b735aae9d3c4e2061300",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": false,
"key": {
"uuid": "81a84be3_d66c6aa3",
"filename": "/PATCHSET_LEVEL",
"patchSetId": 1
},
"lineNbr": 0,
"author": {
"id": 20870
},
"writtenOn": "2023-11-08T19:30:17Z",
"side": 1,
"message": "The reason the test 100 failed is due to the cinder-api service being down as haproxy hadn\u0027t yet brought it back up. i.e. test 100 was trying to access the server, but the configuration from the previous step hadn\u0027t actually \u0027completed\u0027 as the service was not back up. We\u0027ll need to modify the test to wait longer, or retry the api call, to make it more stable.\n\nFrom the test:\n\n2023-11-03 15:54:35.259457 | focal-medium | 2023-11-03 15:54:35 [INFO] test_100_volume_create_extend_delete (zaza.openstack.charm_tests.cinder_backup.tests.CinderBackupTest)\n2023-11-03 15:54:35.260146 | focal-medium | 2023-11-03 15:54:35 [INFO] Test creating, extending a volume.\n2023-11-03 15:54:35.260215 | focal-medium | 2023-11-03 15:54:35 [INFO] ...\n2023-11-03 15:54:36.075459 | focal-medium | 2023-11-03 15:54:36 [INFO] ERROR\n\nFrom the cinder systemd log:\n\nNov 03 15:54:17 juju-4aac85-zaza-ea7cc25d288b-11 systemd[1]: Reloading The Apache HTTP Server...\nNov 03 15:54:18 juju-4aac85-zaza-ea7cc25d288b-11 systemd[1]: Reloaded The Apache HTTP Server.\nNov 03 15:54:29 juju-4aac85-zaza-ea7cc25d288b-11 haproxy[42609]: [WARNING] (42609) : Server cinder_api_172.16.0.64/cinder-0 is DOWN, reason: Layer7 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.\nNov 03 15:54:29 juju-4aac85-zaza-ea7cc25d288b-11 haproxy[42609]: [ALERT] (42609) : backend \u0027cinder_api_172.16.0.64\u0027 has no server available!\nNov 03 15:54:29 juju-4aac85-zaza-ea7cc25d288b-11 haproxy[42609]: Server cinder_api_172.16.0.64/cinder-0 is DOWN, reason: Layer7 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.\nNov 03 15:54:29 juju-4aac85-zaza-ea7cc25d288b-11 haproxy[42609]: Server cinder_api_172.16.0.64/cinder-0 is DOWN, reason: Layer7 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.\nNov 03 15:54:29 juju-4aac85-zaza-ea7cc25d288b-11 haproxy[42609]: backend cinder_api_172.16.0.64 has no server available!\nNov 03 15:54:29 juju-4aac85-zaza-ea7cc25d288b-11 haproxy[42609]: backend cinder_api_172.16.0.64 has no server available!\nNov 03 15:54:36 juju-4aac85-zaza-ea7cc25d288b-11 haproxy[42609]: 172.16.0.104:60880 [03/Nov/2023:15:54:36.065] tcp-in_cinder_api cinder_api_172.16.0.64/\u003cNOSRV\u003e -1/-1/0 0 SC 1/1/0/0/0 0/0\nNov 03 15:54:37 juju-4aac85-zaza-ea7cc25d288b-11 haproxy[42609]: [WARNING] (42609) : Server cinder_api_172.16.0.64/cinder-0 is UP, reason: Layer7 check passed, code: 200, check duration: 13ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.\nNov 03 15:54:37 juju-4aac85-zaza-ea7cc25d288b-11 haproxy[42609]: Server cinder_api_172.16.0.64/cinder-0 is UP, reason: Layer7 check passed, code: 200, check duration: 13ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.\nNov 03 15:54:37 juju-4aac85-zaza-ea7cc25d288b-11 haproxy[42609]: Server cinder_api_172.16.0.64/cinder-0 is UP, reason: Layer7 check passed, code: 200, check duration: 13ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.\n\ne.g. the apache server was restarted, haproxy detected it \u0027down\u0027 and shut the port, then it eventually detected the server as back, but by then the test 100 had given up.",
"revId": "d1bfa2f87812dd2a1511b735aae9d3c4e2061300",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
}
]
}