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.

Sign up for GitHub

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

Jump to bottom

Upgrade script doesn't support appliance fqdn #1731

Open
ghost opened this issue May 9, 2018 · 3 comments
Open

Upgrade script doesn't support appliance fqdn #1731

ghost opened this issue May 9, 2018 · 3 comments
Assignees
@luwang-vmware
Labels
area/pub/vsphere Published documentation for vSphere administrators component/upgrade The automated upgrade script impact/doc/user Requires changes to official user documentation product/ova Related to the OVA packaging of vSphere Integrated Containers resolution/will-not-fix This issue is valid, but will not be fixed severity/2-serious High usability or functional impact. Often has no workaround. source/customer Reported by a customer, directly or via an intermediary

Comments

@ghost
Copy link

ghost commented May 9, 2018 •
edited by ghost
Loading

Bug Report Basic Information

When following the ./upgrade.sh script, it asks you to enter the FQDN or IP of the old VIC Appliance and it does not work if you enter the FQDN, only the IP.

https://github.com/vmware/vic-product/blob/master/installer/build/scripts/upgrade/upgrade.sh#L300
https://vmware.github.io/vic-product/assets/files/html/1.4/vic_vsphere_admin/upgrade_appliance.html

We should:

  • Add a release note to indicate fqdn is not supported.
  • Remove the fqdn option in the future, or actually support it.
@ghost ghost added impact/doc/note Requires creation of or changes to an official release note product/ova Related to the OVA packaging of vSphere Integrated Containers source/customer Reported by a customer, directly or via an intermediary team/lifecycle labels May 9, 2018
@stuclem stuclem added area/pub Published documentation for end-users priority/p0 area/pub/vsphere Published documentation for vSphere administrators and removed impact/doc/note Requires creation of or changes to an official release note priority/p2 labels May 14, 2018
@stuclem stuclem self-assigned this May 14, 2018
@stuclem stuclem mentioned this issue May 15, 2018
Merged
@stuclem
Copy link
Contributor

stuclem commented May 15, 2018

Doc update is in #1747.

Removing the kind/user-doc flag and unassigning myself, as this is the issue for the development work, rather than the doc work.

@stuclem stuclem removed their assignment May 15, 2018
@stuclem stuclem added impact/doc/note Requires creation of or changes to an official release note priority/p2 and removed area/pub Published documentation for end-users priority/p0 labels May 15, 2018
@stuclem
Copy link
Contributor

stuclem commented May 15, 2018 •
edited
Loading

Added the following to the Release Notes:

  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

@stuclem stuclem removed the impact/doc/note Requires creation of or changes to an official release note label May 15, 2018
@zjs zjs added severity/2-serious High usability or functional impact. Often has no workaround. component/upgrade The automated upgrade script and removed priority/p2 labels Jan 29, 2019
@stuclem stuclem added the impact/doc/user Requires changes to official user documentation label Apr 3, 2019
@stuclem stuclem mentioned this issue Apr 3, 2019
Closed
@renmaosheng renmaosheng added the resolution/will-not-fix This issue is valid, but will not be fixed label May 28, 2019
@renmaosheng
Copy link
Contributor

Stuart, we don't plan to fix this. @stuclem

@stuclem stuclem mentioned this issue May 28, 2019
Merged
@stuclem stuclem mentioned this issue May 28, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@luwang-vmware luwang-vmware

Labels
area/pub/vsphere Published documentation for vSphere administrators component/upgrade The automated upgrade script impact/doc/user Requires changes to official user documentation product/ova Related to the OVA packaging of vSphere Integrated Containers resolution/will-not-fix This issue is valid, but will not be fixed severity/2-serious High usability or functional impact. Often has no workaround. source/customer Reported by a customer, directly or via an intermediary
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@zjs @renmaosheng @stuclem @luwang-vmware