Zach Shepherd
Zach Shepherd
@wjun: Ah, I see. The sorting algorithm suffers from the same issue as some of our other code that looks at version numbers: it assumes a build with a higher...
It looks like the linked mock-ups are related to VIC Upgrade, not VCH upgrade. I think we'll need a different set of mockups in order to properly decompose this Epic.
This should not be fixed for 1.3.0. @stuclem: We should ensure that this is documented in an appropriate fashion. We should make it clear to users that they should generally...
In my case, I discovered that the root cause of my error was having an old, powered off OVA as a part of my vSphere inventory following upgrade. It seems...
This should not be fixed for 1.3.0. @stuclem: We should ensure that this is documented in an appropriate fashion. We should make it clear to users that they should generally...
The field appears to be marked as required, so I don't think clearing the value is an option. This seems to be higher priority than it's currently labeled, but perhaps...
We should **not** fix this for 1.3.0. @stuclem: We should have a release not that explains this to users and refers them to the "quoting" instructions in our documentation so...
Not strictly a pre-req. but if we fix this, we should definitely fix vmware/vic#6792 in the same release.
Marking P1 as this seems to be the best way to ensure links are updated to point to 1.4 documentation.
> We should not mark the status as "green tick" until we've confirmed the VCH is up and functional. It looks like we currently base this on the status of...