I have walked through the 3 test cases on 3 different instances in
an OpenStack installation with yakkety images.
There was a difference in behavior from what was listed in the description
for item 'b'. That is by design, and I just didn't realize it when writing
the test case.
On xenial, where ds-identify is set to 'report' mode, you will see the
warning. But on yakkety, where ds-identify is enabled, the system does
not warn as it goes on and uses the Ec2 metadata service. So instead
you see a warning that this system is using the Ec2 metadata service
and it should not be.
I have walked through the 3 test cases on 3 different instances in
an OpenStack installation with yakkety images.
There was a difference in behavior from what was listed in the description
for item 'b'. That is by design, and I just didn't realize it when writing
the test case.
On xenial, where ds-identify is set to 'report' mode, you will see the
warning. But on yakkety, where ds-identify is enabled, the system does
not warn as it goes on and uses the Ec2 metadata service. So instead
you see a warning that this system is using the Ec2 metadata service
and it should not be.