Have something to say?
Impersonate user when using IDP
When we go to impersonate a user from the client area it provides the URL however attempting to use it takes us to the sign-in page. The sign in page only offers the option to redirect to the IDP therefore doesn’t work as the impersonation is done by Osie and our IDP isn’t aware.
Moving a project keeps existing permissions
Moving a project from one organisation to another does not look to update the user permissions. I’d expect when a project moved to another organisation that it would: Update user permissions to match those at the organisation level Update the billing profile to start billing from that point forward to the billing profile linked to the organisation
AZ settings relying on volumev3 endpoint
OSIE Version 26.6.1, Openstack 2026.1 service provider availability zone configuration only picks up cinder when volumev3 endpoints are recreated. Under customer portal it shows no volumes in the menu or when creating a new server with the new endpoint again only recreating volumev3 fixes it.
Trove create DB missing network
When creating a DB with trove in OSIE as a customer, it shows no dropdown or selection for which network the service should be on, where does that get configured?
Kubernetes PVC claims not adhering to AZ choice
(This could very well be my problem and not an issue with OSIE) I created a kubernetes cluster with magnum and its up and good. When I create an application on it with persistant volume claims, it tries to use my FSD1 availability zone. Within the OSIE Admin portal, I do NOT have Availability zones set for cinderv3 or anything at all. Is osie not adhering to that AZ setting when setting up the clusters with Magnum, or is this an openstack problem? I am not sure if this is something that needs to be corrected when creating the cluster so it knows the AZ (‘nova’) to put its volumes, or if I just need to work with customers to have them specify the az as nova manually for every application with a PVC that they deploy.
Magnum/Kubernetes node status incorrect
I’m provisioning a cluster right now and the cluster status is UNHEALTHY because the worker nodes are still provisioning. Within OSIE it shows those nodes as green, but they are not From the Kubernetes status, it shows 0 workers available, but you can’t tell that in OSIE. I’m not sure how much is available to you with just the magnum API calls..not sure if this deeper info is exposed to you.. but it would be great to have this be more factual, and show these systems red, so its obvious why the thing is UNHEALTHY
Account Settings
The account section cannot be managed; clicking on the username—“Account”—in the upper-right corner only takes you to the organizations and projects, but not to an account page. There needs to be a way to manage your account (e.g., reset password and MFA).
Unimport Project
Please consider to enable unimport project function of existing project without cloud resources deleteion. Thank you.
API create user endpoint with invalid date
Users created with the admin_api/v1/users POST endpoint have an invalid create date. curl -X POST 'https://osie.domain.com/admin_api/v1/users' \ -H 'Authorization: Bearer eyJhb...Ig' \ -H 'Content-Type: application/json' \ -H 'Accept: application/json' \ -d '{ "email": "ficticious@abc.com", "sub": "ficticious@abc.com" }' Also, feature request for first_name and last_name to be available at user creation. The endpoint doesn’t support those fields currently but GET does
Can not delete billing profile
A user requested to be removed entirely from our system. I was able to delete the Organization and User, but have to use a backend MongoDB tool to be able to delete the Billing Profile. Is there a better process for this, or can you make the billing profile be deleteable somehow in the UI?
Load Balancer SSL Upload Issue
SSL certificate/key upload form not show when create a new load balancer.
Enable and disable network ports
Apologies if this already exists, but it doesn’t seem possible for a user to disable/enable a network port (administratively shut/no shut) from within OSIE. Would it be possible to add this functionality? Thanks!
Billing profiles on multiple organisations
Setting a billing profile to multiple organisations results in errors such as As discussed this isn’t a valid configuration so it would be useful to only show billing profiles not associated with another organisation when selecting the billing profile to apply to an organisation.
Charge description on single item entries
When we have a pricing plan item with a custom charge description, it doesn’t seem to show when there is only 1 charge that applies to that type e.g. a single charge on resource type ‘instance’ doesn’t show the charge description; however multiple charges on an ‘instance’ resource allows dropdown which shows the custom charge description.
Cleaning up after trial users who left
The process to clean up after a trial user who creates a bunch of resources sucks! I have to go through manually and delete things.. when deleting them in openstack, Osie says "not found" and doesnt clean up its own record. Cant just schedule for deletion, even though the resources are disabled.
Volume attachment from Volume shows no servers
Steps to reproduce: Create a new volume from the Volumes tab Go into the new volume and choose ‘attach to instance’ No instances are shown: However attaching the volume from the server end shows the new volume and allows attachment.
Restore Cinder Volume Snapshots to a New Disk
Firstly, apologies if this functionality already exists and we have misunderstood the current workflow. If so, please feel free to point us in the right direction. Our current understanding is that OSIE does not provide a straightforward way to take an existing Cinder volume snapshot and restore/convert it into a new Cinder volume/disk? At present, the recovery workflow appears to require us to create/deploy a VM using the snapshot/image, rather than simply converting the snapshot back into a usable disk? If so, for our customers and Service Operations teams, this makes what should be a relatively simple disk rollback or recovery operation unnecessarily complicated. Ideally, the workflow would be: Create a snapshot of the required Cinder-backed VM disk. If a rollback is later required, select the snapshot and choose something such as Create Disk from Snapshot. OSIE creates a new Cinder volume from that snapshot. Shut down the affected VM. Detach the existing disk from the VM. Attach the newly created disk from the snapshot. Power the VM back on. We have not currently been able to test whether the underlying OpenStack behaviour differs depending on the Cinder backend. We suspect this workflow may behave differently with Ceph-backed Cinder storage, compared with our current storage platform? Potential Future Enhancement A further enhancement could be to automate the full rollback workflow within OSIE. For example, a Revert Disk to Snapshot action could: Prompt the user to select the disk and snapshot. Shut down the VM safely. Create a new Cinder volume from the selected snapshot. Detach the current disk. Attach the replacement disk in the same position/device mapping. Power the VM back on. With appropriate confirmation and warning prompts, this could turn a multi-step recovery process into a much simpler and safer operation for both customers and Service Operations. The primary request, however, is simply to expose a straightforward snapshot → new Cinder volume → disk swap workflow within OSIE.
Feature Request: Improve Organisation and Project Navigation
Background As we continue adding more organisations and projects into OSIE, the organisation/project selection page shown after login is becoming increasingly difficult to navigate. This is likely to be particularly noticeable for administrative/service-provider users who have access to multiple customer organisations and a large number of projects. A customer user who only has access to one organisation or a small number of projects may not experience the same issue. Currently, all accessible organisations and projects are displayed together using tiles. As the number of projects grows, this results in an increasingly long page and significant scrolling to locate a particular customer or project. Requested Improvements It would be useful to provide several navigation/view options so users can choose the layout that works best for them, rather than enforcing a single view for everyone. Suggested improvements: Alphabetically sort organisations and projects. Currently, the ordering appears to be based on the order in which access was granted. Alphabetical ordering would provide a predictable and consistent way of locating organisations and projects. Add selectable Tile / List views. Retain the existing tile view, but allow users to switch to a more compact list view. Ideally, the user's preferred view could be remembered. Add an Organisation → Project view option. Allow users to choose a hierarchical view where the initial screen lists organisations only, with the associated projects displayed after selecting an organisation. This could also behave intelligently where appropriate: Users with multiple organisations could initially see the organisation list. Users with only one organisation could optionally be taken directly to its projects. Users with only one project could potentially be taken directly into that project. This should ideally be an alternative view rather than replacing the existing tile layout, as different types of users will have different requirements. Add search/filter functionality. There is currently no obvious search capability, which becomes increasingly noticeable as the environment grows. Search/filtering would be particularly useful for: Organisations Projects Virtual Machines / Instances Volumes Network Ports Networks For example, an administrator should be able to type part of a customer or project name on the initial page and immediately filter the displayed results. The same functionality would be useful within a project when locating a specific VM, volume, port or network.
Shared File System
Unable to fetch “Share Type“ options. In Horizon/Skyline dashboard is working fine. os image: ubuntu 24.04 lts openstack 2026.1 kolla ansible