The issue seems to be that the screen-n-dhcp.txt file is not created and the Jenkins plugin code that uploads all the log files to logs.openstack.org fails.
Most possible cause of this issue might be that the plugin code started doing strict checking for file existence since earlier too there used to be no screen-n-dhcp.txt generated but it was not a problem. For instance, check the following logs from a merged patch
If you look, screen-n-dhcp.txt is empty file. But this seemed to be not an issue then.
Therefore the conclusion that something changed in the Jenkins plugin code which is causing the gate failure.
As a workaround, following approaches were tried:
- enabling n-dhcp service via settings file in the Solum devstack plugin. The idea here was that if we enable n-dhcp, may be it will generate the corresponding log file. But this did not work.
- Create a dummy screen-n-dhcp file with some dummy content in the post_test_hook. This seem to work as seen in the following patch: https://review.openstack.org/#/c/298342/5
The issue seems to be that the screen-n-dhcp.txt file is not created and the Jenkins plugin code that uploads all the log files to logs.openstack.org fails.
Most possible cause of this issue might be that the plugin code started doing strict checking for file existence since earlier too there used to be no screen-n-dhcp.txt generated but it was not a problem. For instance, check the following logs from a merged patch
http:// logs.openstack. org/40/ 293640/ 6/check/ gate-solum- devstack- dsvm/dd0b1f5/ logs/
(merged) https:/ /review. openstack. org/#/c/ 293640/
If you look, screen-n-dhcp.txt is empty file. But this seemed to be not an issue then.
Therefore the conclusion that something changed in the Jenkins plugin code which is causing the gate failure.
As a workaround, following approaches were tried: /review. openstack. org/#/c/ 298342/ 5
- enabling n-dhcp service via settings file in the Solum devstack plugin. The idea here was that if we enable n-dhcp, may be it will generate the corresponding log file. But this did not work.
- Create a dummy screen-n-dhcp file with some dummy content in the post_test_hook. This seem to work as seen in the following patch: https:/