-
Notifications
You must be signed in to change notification settings - Fork 3
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
SPIKE: Investigate why production-deployment workflow fails #1778
Comments
|
re-deployment failed. |
Update: there are multiple keys associated with the tanf-key service instance, which can be confirmed via for the purposes of testing, I updated the credentials in HHS circleci with test-deploy credentials to confirm that the @andrew-jameson can we discuss the appropriate path forward? There are at least a couple of items worth revisiting:
|
Yes, happy to discuss when you're available. While the user/pass tasks were noted in #1764 I don't believe I was looped in on all that was done there. I'm also a little curious on why #1766 does not fully address the issues here given that it was functioning prior to recent deployments. |
5/17 UpdateNotes below include prod deployment-related details that helped me to confirm that apps deploy to the correct routes and login buttons redirect to authentication services (Neither service is currently working. login.gov will be replaced with xms and we are still troubleshooting AMS in #1627)
|
Deleted CDN service, telling it to forward cookie and other auth headers made no difference. Once this operation is complete, will run this:
|
since we're tracking prod-related issues in this ticket, including a link to the most recent update: #726 (comment) |
Sent follow-up to cloud.gov support ticket #4217 detailing CDN/domain service changes. Next step will be to try circumventing DNS alias records using just cloud.gov provided |
Circumventing DNS aliases allowed successful login.gov authentication. No cookie magic needed. Still working with cloud.gov so we can use the official ACF domains. @ADPennington has reached out to AMS for us to set up a session with them to try AMS using these provided domains. |
testing login.gov flow 2 ways:
|
production-deployment workflow is functioning since this update. there's still some cleanup of environment variables to ensure this continues to work properly but this will be tracked in #897. Closing this ticket @stevenino |
Description:
On 5/10, we attempted the production-deployment workflow from
hhs:master
, and it failed at thelogin to cloud.gov and set application targets
step (see below)This ticket tracks troubleshooting.
The text was updated successfully, but these errors were encountered: