)]}'
{"tempest/scenario/test_network_basic_ops.py":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"b4da70a1f3e04cd29fd96c5c2c152b9596fd14ce","unresolved":false,"context_lines":[{"line_number":582,"context_line":"        # renewal should be immediate."},{"line_number":583,"context_line":"        # Timeouts are suggested by salvatore-orlando in"},{"line_number":584,"context_line":"        # https://bugs.launchpad.net/neutron/+bug/1412325/comments/3"},{"line_number":585,"context_line":"        renew_delay \u003d CONF.network.build_interval"},{"line_number":586,"context_line":"        renew_timeout \u003d CONF.network.build_timeout"},{"line_number":587,"context_line":""},{"line_number":588,"context_line":"        self._setup_network_and_servers(dns_nameservers\u003d[initial_dns_server])"}],"source_content_type":"text/x-python","patch_set":1,"id":"9fdfeff1_f480c4c1","side":"PARENT","line":585,"range":{"start_line":585,"start_character":22,"end_line":585,"end_character":49},"updated":"2019-01-28 14:39:01.000000000","message":"This defaults to 1 but since it\u0027s a config option someone could be setting it higher if they need to for whatever reason in their deployment. So we might want to make renew_delay a multiple of build_interval rather than just hard-code it to 3, but that\u0027s just an idea. I\u0027m not sure how much it would really matter since this renew_delay variable is just for this specific test.","commit_id":"ceb882169a369c2a00c5b8d95e98fe5bf49c2d9e"},{"author":{"_account_id":15554,"name":"Bence Romsics","email":"bence.romsics@gmail.com","username":"ebenrom","status":"inactive contributor"},"change_message_id":"da16a174135fa9fd733f03c37c463de069d67a60","unresolved":false,"context_lines":[{"line_number":582,"context_line":"        # renewal should be immediate."},{"line_number":583,"context_line":"        # Timeouts are suggested by salvatore-orlando in"},{"line_number":584,"context_line":"        # https://bugs.launchpad.net/neutron/+bug/1412325/comments/3"},{"line_number":585,"context_line":"        renew_delay \u003d CONF.network.build_interval"},{"line_number":586,"context_line":"        renew_timeout \u003d CONF.network.build_timeout"},{"line_number":587,"context_line":""},{"line_number":588,"context_line":"        self._setup_network_and_servers(dns_nameservers\u003d[initial_dns_server])"}],"source_content_type":"text/x-python","patch_set":1,"id":"9fdfeff1_f780c6c1","side":"PARENT","line":585,"range":{"start_line":585,"start_character":22,"end_line":585,"end_character":49},"in_reply_to":"9fdfeff1_f480c4c1","updated":"2019-01-28 15:17:36.000000000","message":"Multiplying the original config value sounds like a good idea.\n\nHowever I will only upload that after I have seen the first test result from tempest-slow. Because the reproduction I wrote about in the commit message in not and end-to-end reproduction. Based on what I could prove with my local, partial reproduction I\u0027m quite sure we\u0027re triggering the double-sigint deconfig of the address. But when it comes to how this test runs in the gate I don\u0027t know if the dhcp response is just slow or missing. If it just slow this change has a good chance to fix it. If it is missing this change will do nothing.\n\nSo I\u0027m waiting for the outcome of tempest-slow.","commit_id":"ceb882169a369c2a00c5b8d95e98fe5bf49c2d9e"}]}