)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"8231b32797101c9636a470516262355bdd9a8688","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"5bf8dbef_85e0e261","updated":"2026-07-22 15:47:14.000000000","message":"Minimally, this needs a release note, but I think it would help reviewers to have more context as for the question of why. For example, we know this default has been amazingly solid for operators which have addressed *all* of the fun and weird firmware settings in their server fleets where they were not consistent. But outside of that there is pain, especially if you have a conductor set to say, Sidney and the hardware clock on physical servers is in Kiribati/Cook Islands/French Polynesia/Hawaiian islands (This has literally happened and people have sought out help) from upstream.\n\nSo, if you can answer the question of \"why? and how does this help solve the issue?\", I think reviewers will be more amenable to landing something like this.","commit_id":"e7c33a97390fdc466713209f5aca08681be4ffba"}],"ironic_python_agent/config.py":[{"author":{"_account_id":22348,"name":"Zuul","username":"zuul","tags":["SERVICE_USER"]},"tag":"autogenerated:zuul:check","change_message_id":"feed3ab02af67c12b69e3f351873c32e5e26e7a5","unresolved":false,"context_lines":[{"line_number":89,"context_line":""},{"line_number":90,"context_line":"    cfg.IntOpt(\u0027auto_tls_allowed_clock_skew\u0027,"},{"line_number":91,"context_line":"               default\u003dint(APARAMS.get("},{"line_number":92,"context_line":"                    \u0027ipa-auto-tls-allowed-clock-skew\u0027, 3600)),"},{"line_number":93,"context_line":"               min\u003d0,"},{"line_number":94,"context_line":"               help\u003d\u0027Clock skew (in seconds) allowed in the generated TLS \u0027"},{"line_number":95,"context_line":"                    \u0027certificate.\u0027),"}],"source_content_type":"text/x-python","patch_set":1,"id":"9694d58a_130761e0","line":92,"updated":"2026-07-17 21:42:37.000000000","message":"pep8: E126 continuation line over-indented for hanging indent","commit_id":"40d73077f36aa1746601220f0e9267cb384c88f4"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"8231b32797101c9636a470516262355bdd9a8688","unresolved":true,"context_lines":[{"line_number":88,"context_line":"                     \u0027automatic agent TLS.\u0027),"},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"    cfg.IntOpt(\u0027auto_tls_allowed_clock_skew\u0027,"},{"line_number":91,"context_line":"               default\u003dint(APARAMS.get(\u0027ipa-auto-tls-allowed-clock-skew\u0027,"},{"line_number":92,"context_line":"                                       3600)),"},{"line_number":93,"context_line":"               min\u003d0,"},{"line_number":94,"context_line":"               help\u003d\u0027Clock skew (in seconds) allowed in the generated TLS \u0027"}],"source_content_type":"text/x-python","patch_set":2,"id":"38080855_cf4542e4","line":91,"updated":"2026-07-22 15:47:14.000000000","message":"So I *think* the base challenge is adding a parameter might be viewed as problematic, but I\u0027ve openly just wanted to re-model the clock skew to be more of an open range specifically because I\u0027ve had some issues where folks are deploying in weird time zones (Well, weird to folks in North America) and their hardware is set to one time zone, but their conductor is set to an entirely different time zone far outside of a one hour range, which honestly kind of becomes breaking in short order.\n\nMaybe some additional rationale to help the idea grow for code reviewers, or at least better understand why you want to put it on the kernel command line.","commit_id":"e7c33a97390fdc466713209f5aca08681be4ffba"}]}