Troubleshooting
Last updated
Was this helpful?
Last updated
Was this helpful?
For Catalog-specific issues, see .
Package.set_dir()
on the package root (".") overrides package-level metadata. If you do not provideset_dir(".", foo, meta=baz)
with a value formeta=
,set_dir
will set package-level metadata toNone
.
A common pattern is to Package.browse()
to get the most recent
version of a package, and then Package.push()
updates.
You can preserve package-level metadata when calling set_dir(".", ...)
as follows:
Users can either be invited directly or are just-in-time provisioned (JIP) when they sign in via SSO and receive the "default role."
If an admin (or any user) is created by JIP, or created through CloudFormation with an SSO Provider set to anything other than Disabled, then setting the password for that user has no effect and password login will never succeed for that user. Said another way, users created through SSO can only log in through SSO.
You must disable SSO and enable PasswordAuth
if you wish to log in as an
admin using a password (as opposed to SSO).
The following are common causes of failed logins. In most cases we recommend that you check the browser's network panel for details.
Changing the admin password is only possible with PasswordAuth=Enabled
in
CloudFormation and is subject to the following limitations for security reasons:
Has no effect if SSO is in use, or was in use when the admin was first created.
Has no effect on pre-existing admin username/password pairs.
You can click "reset password" on the login page.
To change the admin email (e.g. you have accidentally broken your admin user) try the following:
Change the value of the AdminEmail
CloudFormation parameter to a net new
email.
Apply the change as a stack Update.
Once the update is successful, the new admin can log in, set roles, and nominate other admins as needed.
Quilt stack outputs:
Initiate drift detection:
After drift detection is complete:
Quilt stack events:
To expedite the resolution of any errors encountered while using Quilt, please capture the following logs and share them with Quilt support:
Find the name of your Quilt stack:
Capture Quilt log events for the last 30 minutes as follows:
Determine which principal you're using as follows:
Inspect problematic objects with the following commands:
Sometimes you may wish to find an ID or other information from a logical resource in a Quilt stack. The following example is for security groups. Modify the commands as needed for other resource types.
The event source mapping is a Lambda resource that reads from SQS.
If for some reason the event source mapping is disabled, it can be enabled as follows.
.
SSO connector misconfigured. See for details.
SSL errors are often caused by misspelled names, or incomplete Subject
Alternate Names. The ACM certificate for CertificateArnELB
must cover all
three Quilt either via a suitable *
or
explicit Subject Alternate Names.
On rare occasions, Quilt stack deployment updates might fail. This can happen for several reasons. To expedite resolution of stack deployment issues, it's helpful to have the following data and output from the following commands when contacting.