Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Marking the OVA as "Managed By" causes warnings when interacting with it via VC #1184

Open
zjs opened this issue Nov 30, 2017 · 7 comments
Open
Labels
component/ova The build process for the OVA itself kind/defect Behavior that is inconsistent with what's intended product/ova Related to the OVA packaging of vSphere Integrated Containers severity/4-minor Low usability or functional impact. Often has an easy workaround.

Comments

@zjs
Copy link
Member

zjs commented Nov 30, 2017

Because the OVA is marked as being "Managed By" the H5 client, warnings are shown when interacting with it via both the H5 Client and the Flex client:

image

image

image

image

You should not modify the virtual machine directly. Use the management console of the solution to make changes.

These messages are misleading because users should modify the virtual machine directly because there isn't a management console for the fake "solution" we've marked them as being managed by.

@zjs zjs added product/ova Related to the OVA packaging of vSphere Integrated Containers kind/defect Behavior that is inconsistent with what's intended team/lifecycle labels Nov 30, 2017
@zjs
Copy link
Member Author

zjs commented Nov 30, 2017

@stuclem: I think we should have some sort of release note for this instructing customers to ignore these warnings on the OVA.

@zjs zjs added the impact/doc/note Requires creation of or changes to an official release note label Nov 30, 2017
@stuclem
Copy link
Contributor

stuclem commented Nov 30, 2017

OK, thanks @zjs. Is this issue ever likely to be fixed, or is it a permanent feature?

@zjs
Copy link
Member Author

zjs commented Nov 30, 2017

I think that's still TBD. I'd like to fix this, but am not sure how hard it will be (and therefore unsure how likely we are to get to it in the future).

@stuclem
Copy link
Contributor

stuclem commented Dec 1, 2017

OK, will leave as a release note for the time being.

@stuclem
Copy link
Contributor

stuclem commented Jan 9, 2018

Attempted release note:

  • vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
    If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.

    Workaround: Ignore the warnings and click Yes to proceed with the operation.

@zjs is this OK?

@stuclem
Copy link
Contributor

stuclem commented Jan 11, 2018

Thanks @zjs. Removing kind/note.

@stuclem stuclem removed the impact/doc/note Requires creation of or changes to an official release note label Jan 11, 2018
@zjs zjs removed the kind/quality label Jul 30, 2018
@zjs zjs added severity/4-minor Low usability or functional impact. Often has an easy workaround. component/ova The build process for the OVA itself and removed priority/p3 labels Jan 28, 2019
@hickeng
Copy link
Member

hickeng commented Jan 28, 2019

There was a reason the OVA was marked as managed by - I don't recall precisely what that was. It may have been to allow the UI plugin to discover the OVA due to not having access to the tag API.
Noted here because simply removing the managedBy reference may not be viable as an isolated piece of work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/ova The build process for the OVA itself kind/defect Behavior that is inconsistent with what's intended product/ova Related to the OVA packaging of vSphere Integrated Containers severity/4-minor Low usability or functional impact. Often has an easy workaround.
Projects
None yet
Development

No branches or pull requests

5 participants