Re: [EXTERNAL] Re: [VOTE] Release Apache Traffic Control 3.0.0-RC4

2019-02-08 Thread Gray, Jonathan
Changing my vote again to -1. My anymap testing failure appears to be a result of a real issue rather than human/configuration error. TLDR; assigning servers to ANY_MAP DS breaks TR zone file generation. https://github.com/apache/trafficcontrol/issues/3315 Jonathan G On 2/8/19, 12:11 AM, "Gra

Re: [EXTERNAL] Re: [VOTE] Release Apache Traffic Control 3.0.0-RC4

2019-02-07 Thread Gray, Jonathan
+1 Known Issues I had to adapt for: 3181 - SSL certificates not self-signed but lacking SKI & AKI extensions can lead to fatal loss of all Traffic Routers in associated CDN 2828 - Self-signed certificate generation via TP or the associated API endpoint doesn't work I verified: Using the RC4 tar

Re: [VOTE] Release Apache Traffic Control 3.0.0-RC4

2019-02-06 Thread Dan Kirkwood
+1 Verified the following: - sha checksum correct - gpg signature correct - RELEASE-3.0.0-RC4 tag signed correctly - BUILD_NUMBER file indicates the correct commit count and hash - all components build with `./pkg -v` - saw same problem with `weasel`, but it's pointing out files in `.m2` dir (from

Re: [EXTERNAL] [VOTE] Release Apache Traffic Control 3.0.0-RC4

2019-02-06 Thread Gray, Jonathan
The issue cited was where I found it because I had automation that had weakly typed payloads as was permissible via perl. Once I upgraded to a version that had been converted to Go, the automation broke. I can fairly easily fix it in my code, but API are contracts and I object to retroactively

Re: [EXTERNAL] [VOTE] Release Apache Traffic Control 3.0.0-RC4

2019-02-06 Thread Dave Neuman
Do you have an example of an endpoint that is in the 3.0 release that will not work now because of this bug? I think we should take a look at what is effected and make our decision from there. A release is not guaranteed to have no known issues, but we do need to decide if we can live with the k

Re: [EXTERNAL] [VOTE] Release Apache Traffic Control 3.0.0-RC4

2019-02-06 Thread Gray, Jonathan
I'm -1 on the release because of issue https://github.com/apache/trafficcontrol/issues/3304 . The conversion to go from perl has inconsistent strong/weak typing implementation inside the json payloads. The Traffic Portal is the primary client that's been checked and converted to strong typing

Re: [VOTE] Release Apache Traffic Control 3.0.0-RC4

2019-02-05 Thread Dave Neuman
+1 I verified the following: Sha512, GPG signature (had an warning but that is ok) Built all components using pkg on a fresh Centos7.5 VM. It looked like there might be issues with weasel, but I am not going to -1 because of that because it's not critical to running Traffic Control. Thanks, Dave

[VOTE] Release Apache Traffic Control 3.0.0-RC4

2019-02-01 Thread Gelinas, Derek
Hello All, I've prepared a release for v3.0.0-RC4 The vote is open for at least 72 hours and passes if a majority of at least 3 +1 PPMC votes are cast. [ ] +1 Approve the release [ ] -1 Do not release this package because ... Changes since 2.2 https://github.com/apache/trafficcontrol/compare/2.2.x