Hello,
on providing new image for CI check gates that has been created with virt-customize not Diskimage Builder [1][2], it raises issues on some test jobs, that are currently tested on [3].
By discovering what changes needs to be done for virt-customize image, later that image can be replaced by "pure" Centos 9 stream image (only Zuul SSH authorized key will be injected) with pre-tasks, that can apply all the current changes. It means, that the image customization would be simple and helps to control more the system.
Currently errors:
- for job: periodic-tripleo-ci-centos-9-ovb-3ctlr_1comp_1supp-featureset064-master
```
2022-10-03 14:32:03.574994 | primary | TASK [Set eth2 public IP address] **********************************************
2022-10-03 14:32:03.575162 | primary | Monday 03 October 2022 14:32:03 +0000 (0:00:00.049) 0:04:11.661 ********
2022-10-03 14:32:11.064281 | primary | fatal: [supplemental]: FAILED! => {"changed": false, "cmd": "ip a add dev eth2 10.0.0.250/24;\nip l set eth2 up;\nip link set dev eth2 mtu 1450;\nping 10.0.0.1 -c 4 -q;\n", "delta": "0:00:06.150737", "end": "2022-10-03 10:32:10.823018", "msg": "non-zero return code", "rc": 1, "start": "2022-10-03 10:32:04.672281", "stderr": "", "stderr_lines": [], "stdout": "PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.\n\n--- 10.0.0.1 ping statistics ---\n4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3062ms\npipe 3", "stdout_lines": ["PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.", "", "--- 10.0.0.1 ping statistics ---", "4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3062ms", "pipe 3"]}
```
- for job: periodic-tripleo-ci-centos-9-ovb-3ctlr_1comp-featureset001-master
```
2022-10-03 15:11:07.317795 | primary | TASK [did the deployment pass or fail?] ****************************************
2022-10-03 15:11:07.317869 | primary | Monday 03 October 2022 15:11:07 +0000 (0:00:00.050) 1:07:02.872 ********
2022-10-03 15:11:07.344113 | primary | fatal: [undercloud -> localhost]: FAILED! => {
2022-10-03 15:11:07.344176 | primary | "failed_when_result": true,
2022-10-03 15:11:07.344188 | primary | "overcloud_deploy_result": "failed"
2022-10-03 15:11:07.344198 | primary | }
```
Other jobs seems to have similar issue.
More information and logs are available in test job patch set [3].
Hello,
on providing new image for CI check gates that has been created with virt-customize not Diskimage Builder [1][2], it raises issues on some test jobs, that are currently tested on [3].
By discovering what changes needs to be done for virt-customize image, later that image can be replaced by "pure" Centos 9 stream image (only Zuul SSH authorized key will be injected) with pre-tasks, that can apply all the current changes. It means, that the image customization would be simple and helps to control more the system.
Currently errors:
- for job: periodic- tripleo- ci-centos- 9-ovb-3ctlr_ 1comp_1supp- featureset064- master ******* ******* ******* ******* ******* **** tripleo- ci-centos- 9-ovb-3ctlr_ 1comp-featurese t001-master ******* ******* ******* ******* ***** when_result" : true, deploy_ result" : "failed"
```
2022-10-03 14:32:03.574994 | primary | TASK [Set eth2 public IP address] *******
2022-10-03 14:32:03.575162 | primary | Monday 03 October 2022 14:32:03 +0000 (0:00:00.049) 0:04:11.661 ********
2022-10-03 14:32:11.064281 | primary | fatal: [supplemental]: FAILED! => {"changed": false, "cmd": "ip a add dev eth2 10.0.0.250/24;\nip l set eth2 up;\nip link set dev eth2 mtu 1450;\nping 10.0.0.1 -c 4 -q;\n", "delta": "0:00:06.150737", "end": "2022-10-03 10:32:10.823018", "msg": "non-zero return code", "rc": 1, "start": "2022-10-03 10:32:04.672281", "stderr": "", "stderr_lines": [], "stdout": "PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.\n\n--- 10.0.0.1 ping statistics ---\n4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3062ms\npipe 3", "stdout_lines": ["PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.", "", "--- 10.0.0.1 ping statistics ---", "4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3062ms", "pipe 3"]}
```
- for job: periodic-
```
2022-10-03 15:11:07.317795 | primary | TASK [did the deployment pass or fail?] *******
2022-10-03 15:11:07.317869 | primary | Monday 03 October 2022 15:11:07 +0000 (0:00:00.050) 1:07:02.872 ********
2022-10-03 15:11:07.344113 | primary | fatal: [undercloud -> localhost]: FAILED! => {
2022-10-03 15:11:07.344176 | primary | "failed_
2022-10-03 15:11:07.344188 | primary | "overcloud_
2022-10-03 15:11:07.344198 | primary | }
```
Other jobs seems to have similar issue.
More information and logs are available in test job patch set [3].
Thanks for help,
Dan
[1] https:/ /softwarefactor y-project. io/r/c/ config/ +/26030 /softwarefactor y-project. io/r/c/ config/ +/26166 /review. rdoproject. org/r/c/ testproject/ +/44982
[2] https:/
[3] https:/