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

default_groupadmin not working on FSunstone (FireEdge) #6896

Open
3 tasks
Franco-Sparrow opened this issue Feb 5, 2025 · 2 comments
Open
3 tasks

default_groupadmin not working on FSunstone (FireEdge) #6896

Franco-Sparrow opened this issue Feb 5, 2025 · 2 comments

Comments

@Franco-Sparrow
Copy link

Franco-Sparrow commented Feb 5, 2025

Description

Default view for groupadmins cant load this view for them on FSunstone. Is not able to load default_groupadmin. RSunstone can successfully load this view for default admins.

To Reproduce

1-Create a user and group and make this user admin of its own group (Default behavior when create users from OpenNebula Tenants for WHMCS).
2-Login into the cloud and the default view will not be the groupadmin view.

roles/install_opennebula/files/fsunstone-views.yaml

# This file describes which Sunstone views are available according to the
# primary group a user belongs to

# Specify the filename for a custom logo to be used in the UI.
# Acceptable formats include: .jpg, .jpeg, .png.
# Ensure the filename adheres to the pattern: [a-zA-Z0-9-_]+.(jpg|jpeg|png)
# Example:
#
# logo: custom_logo.png

#logo: images/opennebula-5.0.png
groups:
    oneadmin:
        - admin
        - group_admin
        - advanced
        - simple
default:
    - advanced
    - simple
default_groupadmin:
    - group_admin
    - advanced
    - simple
labels_groups:
    default:

# Name and description of each view.
#
# More views could be added creating a new object under views attribute.
# Example:
#   customview:
#     name: Name of the custom view
#     description: Description of the custom view

views:
  admin:
    name: groups.view.admin.name
    description: groups.view.admin.description
  group_admin:
    name: groups.view.group_admin.name
    description: groups.view.group_admin.description
  advanced:
    name: groups.view.advanced.name
    description: groups.view.advanced.description
  simple:
    name: groups.view.simple.name
    description: groups.view.simple.description

Expected behavior

Login int the cloud with a group admin user, and default view should be the configured view for group admin.

Details

  • Affected Component: [FSunstone]
  • Hypervisor: [KVM]
  • Version: [6.10.2]

Additional context

Image

Image

Progress Status

  • Code committed
  • Testing - QA
  • Documentation (Release notes - resolved issues, compatibility, known issues)
@Franco-Sparrow
Copy link
Author

Hi Mr. @vichansson

You may validate this FireEdge issue as well. I can confirm it from my end.

Cheers

@Franco-Sparrow
Copy link
Author

Franco-Sparrow commented Feb 6, 2025

Hi @dcarracedo

This was not an issue, just a missconfiguration from my end.

SOLUTION

Create file with the Sunstone views for the given group:

source /tmp/vars
cat << EOF > /var/tmp/group_${GROUP_NAME}_views.txt
FIREEDGE=[
  DEFAULT_VIEW = "advanced",
  VIEWS        = "advanced,simple",
  GROUP_ADMIN_DEFAULT_VIEW = "group_admin",
  GROUP_ADMIN_VIEWS        = "group_admin,advanced,simple"]
SUNSTONE=[
  DEFAULT_VIEW = "advanced",
  VIEWS        = "advanced,simple",
  GROUP_ADMIN_DEFAULT_VIEW = "group_admin",
  GROUP_ADMIN_VIEWS        = "group_admin,advanced,simple"]
OPENNEBULA=[
  DEFAULT_IMAGE_PERSISTENT="NO",
  DEFAULT_IMAGE_PERSISTENT_NEW="NO" ]
EOF
Update the group with previous configuration:

Update group:

source /tmp/vars
onegroup update ${GROUP_NAME} -a /var/tmp/group_${GROUP_NAME}_views.txt

FOR THE FUTURE

Make available this configuration by default from fireedge (set a custom template for SUNSTONE and FIREEDGE views) for new created groups. If you dont want to use default opennebula views, because you may have your owns views with different names, you should be able to set this config by default using your custom views and names. Right now each new group needs to be updated with the new template.

Should I create a feture request for this?

PS: You may close the issue.

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

2 participants