Nightly 05/07/18 VC 6.0 5-25-OPS-User-Grant: failed to validate ops credentials: This operation is not supported on object

[AngieCris]

Nightly 05/07/18, VC 6.0
5-25-OPS-User-Grant
Test case: granted ops-user perms work after upgrade

vic-machine install failed:

May  8 2018 04:09:06.094Z ERROR op=14780.1: --------------------
May  8 2018 04:09:06.094Z ERROR op=14780.1: Failed to validate operations credentials: ServerFaultCode: The operation is not supported on the object.
May  8 2018 04:09:06.094Z DEBUG [ END ] op=14780.1 [vic/lib/install/validate.(*Validator).ListIssues:273] [308.982µs] 
May  8 2018 04:09:06.094Z DEBUG [ END ] op=14780.1 [vic/lib/install/validate.(*Validator).Validate:299] [2.088876028s] 
May  8 2018 04:09:06.094Z ERROR op=14780.1: Create cannot continue: configuration validation failed
May  8 2018 04:09:06.128Z ERROR op=14780.1: --------------------
May  8 2018 04:09:06.128Z ERROR op=14780.1: vic-machine-linux create failed: validation of configuration failed

link to download complete logs: https://storage.cloud.google.com/vic-ci-logs/vic_nightly_logs_2018-05-07-20-32-56.zip?authuser=1
vic-machine log:
vic-machine.log

Cc: @jzt

[AngieCris]

Nightly 05/06/18, VC 6.0

same error, vic-machine install failed ops creds validation

link: https://storage.cloud.google.com/vic-ci-logs/vic_nightly_logs_2018-05-06-20-32-56.zip?authuser=1
vic-machine log: vic-machine.log

[AngieCris]

nightly 05/05/18, VC 6.0

same failure
link: https://storage.cloud.google.com/vic-ci-logs/vic_nightly_logs_2018-05-05-20-32-56.zip?authuser=1

[jzt]

The ops user perms don't work in 1.31, so a test to ensure that they "still" work after upgrading from 1.3.1 seems invalid to me. This test has been failing as far back as I can find logs in GCP (Feb 1 2018) with the same message. While I don't know exactly what's causing it (yet), it's clear that the grant perms operation does not and likely has never functioned in 1.3.1. This PR was assumed to fix the original issue, but it appears that the bug that was fixed in 1.3.1 only stopped the VCH deploy from failing when --grant-ops-perms was supplied. It did not fix what we see here, which is a permission error for the object on which the permissions are to be applied. Seeing as we can't retroactively go back and fix 1.3.1, I'm not sure if we should simply remove this test altogether, or comment it out until our next release, when we can continue testing that ops user perms still work after performing an upgrade from 1.4.0 -> 1.4.1/1.5.0.

[jzt]

Disabling this test until our next release. Captured in #7983.