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

4.1.0 Walkthrough #484

Open
nwmac opened this issue Sep 16, 2020 · 0 comments
Open

4.1.0 Walkthrough #484

nwmac opened this issue Sep 16, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@nwmac
Copy link
Member

nwmac commented Sep 16, 2020

API Keys pointer to + button is missing
Think this is because downstream we hide the arrow in the endpoint page

^^ Did you fix this? I could not reproduce

Helm chart history table does not update on chart upgrade

  • Could refresh on visit? Convert to normal list with refresh button?

Backup Endpoints password should have confirm field
password field should have a confirm password field as well

Cannot run two stratos instances in the same kube cluster
DB of second fails to come up.

Data dir is: /var/lib/mysql/
Data directory already exists...

Home Page CF App Favourite Card Clips Text
See 'g'
image

Erronious uaa secrets entry in metrics chart
Not sure this value is needed given that this is part of cloud foundry section now

secrets:
  UAA_ADMIN_CLIENT_SECRET: null

This is for backwards compatibility with old SCF values - can go at some point

Cannot see upgrade option after installing console
Install rc6 via cli from http://opensource.suse.com/stratos, open console and registered same helm repo and minikube rc6 installed to, go to rc6 in workloads and no upgrade option is provided

--> #512

Workloads are not automatically refreshed after installing chart
install a chart, go to workloads and need to manually refresh to see chart

Incorrect upgrade options given for metrics via helm hub

-> See: #514

YAML Editor fails to load for Stratos chart
The schema form works fine, but switching to yaml editor fails (errors in console, editor doesn't load)


Fixed

Should not show API keys link if no persistent storage
No db? No API keys. Pertinent to when stratos deployed via CF push

Helm Install does not work - click on the install button, nothing happens - console log shows:

main-es2015.8940b024db541d403f01.js:1 ERROR Error: Uncaught (in promise): ReferenceError: Cannot access 'eo' before initialization
ReferenceError: Cannot access 'eo' before initialization
    at Module.WorkloadsModule (10-es2015.b17adc2a83b53d1de3a5.js:1)

^^ Actually, workloads module is broken - can't click on the workloads side nav item

Error seen in logs:

│ WARN[Wed Sep 16 13:56:07 UTC 2020] Error saving Chart cassandra, Version 5.6.4 to the database: Unable to save Helm Chart Version: Error 1406: Data too long for column 'description' at row 1 

Looks like we need to truncate the text data

Cannot view charts with just helm hub registered #493
Cannot read property 'id' of null. Response from jetstream for sratos monocular charts is {"data":null,"meta":{"totalPages":1}}

Duped charts between helm hub and repos default to helm hub break charts list filtering by source

  • Register helm hub and helm bitnami repo (bitnami endpoint must be called bitnami to match repo name used in helm hub charts). Try to filter the charts view to bitnami and nothing is shown.
  • This is due to the unique key for helm hub charts (repo name / chart name) matching helm repo charts (endpoint name / chart name). When persisting the charts the former overwrites the later

CF Event Table: Details JSON text is too large See cloudfoundry#4601
This is in a mat-dialog-content, which has correct font size when in a dialog but not in a list

CF Instances Last Operation is bunched up See cloudfoundry#4606

  • Should have detail about last operation on new line
    image
@nwmac nwmac added the bug Something isn't working label Sep 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant