build: pack/deploy charm on resolute#109
Open
jansdhillon wants to merge 26 commits intocanonical:mainfrom
Open
build: pack/deploy charm on resolute#109jansdhillon wants to merge 26 commits intocanonical:mainfrom
resolute#109jansdhillon wants to merge 26 commits intocanonical:mainfrom
Conversation
resoluteresolute
Contributor
|
Build and deploy worked as expected. I don't think we want to merge all of these changes, though. Can you clean it up so the PR has just the changes we need? The other details are probably good fodder for our internal docs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note that build CI will fail because the
ccccache doesn't have the resolute build yetRefresh charmcraft to the latest version (4.1+):
Pack
charmcraft clean && charmcraft pack --platform ubuntu@26.04:amd64Deploy
Run shortly after deploying to ensure the model pulls from
ubuntu-daily:After the model settles check the services are up:
juju ssh landscape-server/0 -- "sudo lsctl status"...
Testing auth
To test OIDC, ask Spencer to invite you to the dev Okta if you haven't already.
Then, get the IP address of
landscape-server/0, and set it like so in/etc/hosts:replacing that with the real IP. Note that we have to use
landscape-server-jammy.combecause the login redirect URIs for Okta need to be specific URLs.Also, the charm guards against having OIDC and OpenID set in the charm config for some reason, that's why the bundle uses
additional_service_config.Log in with OIDC at
https://landscape-server-jammy.com/.Truncating the account DB and retrying with OpenID (Ubuntu One)
Truncate the databases by first getting the
operatorsecret:Use it to truncate the main and account databases so we can recreate the first account with OpenID:
Then, go back to
https://landscape-server-jammy.com/and instead log in with Ubuntu One.Running integration tests