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

I have Sunstone errors when I disable support endpoint #3268

Closed
7 tasks
baby-gnu opened this issue Apr 24, 2019 · 1 comment
Closed
7 tasks

I have Sunstone errors when I disable support endpoint #3268

baby-gnu opened this issue Apr 24, 2019 · 1 comment

Comments

@baby-gnu
Copy link
Contributor

Description

If I disable the support endpoint in sunstone-server.conf, I have error messages on the web interface:

  • Action Support.check not defined
  • Action Support.checkversion not defined

To Reproduce

  1. Disable support endpoint sed -i -e 's,\(- support\),# \1,' /etc/one/sunstone-server.conf
  2. Restart Sunstone
  3. Connect to the sunstone as cloud view user

Expected behavior

When I disable the support endpoint in the server configuration I should not have any errors in the cloud view.

Maybe related: note that disabling the support-tab in the admin/users views do not hide the Not officially supported link in the menu.

Details

  • Affected Component: Sunstone
  • Hypervisor: KVM
  • Version: 5.8.1

Additional context

It looks like the API call are made regardless of the configuration of the view

Progress Status

  • Branch created
  • Code committed to development branch
  • Testing - QA
  • Documentation
  • Release notes - resolved issues, compatibility, known issues
  • Code committed to upstream release/hotfix branches
  • Documentation committed to upstream release/hotfix branches
@tinova tinova added this to the Release 5.10 milestone Oct 17, 2019
@tinova tinova modified the milestones: Release 5.10, Release 5.10.1 Oct 29, 2019
jloboescalona2 pushed a commit to jloboescalona2/one that referenced this issue Nov 4, 2019
Signed-off-by: Jorge Lobo <jlobo@opennebula.systems>
jloboescalona2 pushed a commit to jloboescalona2/docs that referenced this issue Nov 4, 2019
Signed-off-by: Jorge Lobo <jlobo@opennebula.systems>
jloboescalona2 pushed a commit to jloboescalona2/one that referenced this issue Nov 4, 2019
Signed-off-by: Jorge Lobo <jlobo@opennebula.systems>
@jloboescalona2
Copy link
Contributor

@tinova, PRs to approve
-ONE: #3907
-Docs: OpenNebula/docs#825

tinova pushed a commit that referenced this issue Nov 4, 2019
Signed-off-by: Jorge Lobo <jlobo@opennebula.systems>
tinova pushed a commit to OpenNebula/docs that referenced this issue Nov 4, 2019
Signed-off-by: Jorge Lobo <jlobo@opennebula.systems>
@tinova tinova closed this as completed Nov 4, 2019
@tinova tinova modified the milestones: Release 5.10.1, Release 5.10 Nov 4, 2019
jloboescalona2 pushed a commit to jloboescalona2/one that referenced this issue Nov 7, 2019
Signed-off-by: Jorge Lobo <jlobo@opennebula.systems>
tinova pushed a commit that referenced this issue Nov 7, 2019
Signed-off-by: Jorge Lobo <jlobo@opennebula.systems>
rsmontero pushed a commit that referenced this issue Oct 29, 2024
- If the API response returns only 1 object, it won't be array wrapped,
  causing issues when formatting the response to a dataset. Now
  transformApiResponseToDataset always casts the response to an array.

Signed-off-by: Victor Hansson <vhansson@opennebula.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants