You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have some test specifications that require IPv6-only but checking the box in the PWA Test specification doesn't seem to be persistent. We can successfully update after checking the box, but coming back to the test specification shows "IPv4 only" selected?!
One specific example is from our PWA instance running on psconfig.opensciencegrid.org. The test is called "WLCG-OSG IPv6 IP6_FLOW_ID 6hr Bandwidth". When we check this test spec it shows the "IPv4 only" box is checked. We can instead select "IPv6 only" and update, which seems to work. If we go to another test spec and then come back it again shows "IPv4 only" is checked.
This test spec is used on the config "USATLAS IPv6 Bandwidth". If we examine the JSON sent for one of the nodes in that mesh, we see:
We have some test specifications that require IPv6-only but checking the box in the PWA Test specification doesn't seem to be persistent. We can successfully update after checking the box, but coming back to the test specification shows "IPv4 only" selected?!
One specific example is from our PWA instance running on psconfig.opensciencegrid.org. The test is called "WLCG-OSG IPv6 IP6_FLOW_ID 6hr Bandwidth". When we check this test spec it shows the "IPv4 only" box is checked. We can instead select "IPv6 only" and update, which seems to work. If we go to another test spec and then come back it again shows "IPv4 only" is checked.
This test spec is used on the config "USATLAS IPv6 Bandwidth". If we examine the JSON sent for one of the nodes in that mesh, we see:
USATLAS IPv6 Bandwidth: {
type: "throughput",
spec: {
duration: "PT25S",
source: "{% address[0] %}",
dest: "{% address[1] %}",
flow-label: 65540,
omit: "PT5S",
ip-version: 6,
schema: 1
}
},
So, the ip-version IS correct, even though PWA continues to show "IPv4 only" being checked.
The text was updated successfully, but these errors were encountered: