Have something to say?
Security Group is not displayed on the Port after saving
Security Group changes appear to be accepted without errors, but the assigned Security Group is not visible after saving. This prevents us from confirming whether the intended security policies are applied to the Port.
sign-up link shows up when sign-up is disabled
sign-up disabled on all realms but still get the link to sing up. Trying to sign up will fail saying signup is disabled for this realm.
Selecting project removes realm selection
In client area when I have any realm selected and open user or org realm still stays selected in the dropdown menu but when clicking on project realm resets to βAll realms"
Renaming projects via OSIE portal
Our customer renamed a project via osie portal but the change was not reflected in openstack/keystone. So the project name now differs in osie portal and openstack/keystone.
WHMCS Payment Integration Issue
We have an issue regarding WHMCS payment gateway integration. The invoice was paid, but unable to add funds. For context, the invoice id isΒ 348925 WHMCS = paid OSIE = error Gateway Message = An error occurred while adding the funds Thank you
RabbitMQ - migrate transient_nonexcl_queues to durable queues or exclusive transient queues
Rabbit 4.3+ dropped support for transient_nonexcl_queues, which is the type of queues OSIE is trying to create (the feature has been deprecated since 2021 - https://www.rabbitmq.com/release-information/deprecated-features-list, but up until 4.3 RabbitMQ only threw warnings into log, now it rejects them). This can be worked around by setting deprecated_features.permit.transient_nonexcl_queues = true in RabbitMQ cluster configuration, however itβs not a permanent fix since the the feature will be removed in future RabbitMQ versions. Documentation at https://www.rabbitmq.com/docs/queues#durability recommends switching to different type of queues: Transient (non-durable) non-exclusive classic queues are deprecated and cannot be declared by default starting with RabbitMQ 4.3.0. Please use one of the following: - durable queues - non-durable exclusive queues - durable queues with a queue TTL (a reasonably close equivalent to non-exclusive transient queues) To explicitly allow transient non-exclusive queues, add the following line to rabbitmq.conf: Enables deprecated non-durable (transient) non-exclusive queues (disabled by default as of RabbitMQ 4.3.0, will be removed in a later version) deprecated_features.permit.transient_nonexcl_queues = true Do you plan on implementing this in the future in order to not run into problems when upgrading to newer RabbitMQ version in the future? Thank you.
Storware Integration β Policies are not scoped to Projects or Organizations
Currently, Storware policies in OSIE are not sufficiently separated by project or organization. Users can see policies that are not related to their own project or organization. This creates an issue in multi-tenant environments, as policies from other tenants or organizational scopes may be visible even though they are not relevant to the user. Expected Behavior: A user should only be able to see policies associated with their Project or Organization. When creating a new policy, it should be possible to define its scope: Project-wide β only available and visible within the selected project. Organization-wide β available and visible across the corresponding organization. The selected scope should determine which users can see and use the policy.
Server Activity list on server Overview page grows without limit
On the server Overview page in the user dashboard, the βServer Activityβ panel lists every action since the server was created (create, start, stop, reboot, reset state, pause, unpause, shelve, unshelve, migrate, extend volume, change password and so on). There is no limit or pagination, so the page keeps getting longer as activity builds up. On a server about 3 months old the panel already runs to around 40 entries and stretches the Overview page far below the other sections. Servers that are rebooted or restarted often will become hard to use.
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!