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

Package Acquisition steps taking 10x longer in 2024.4 #9149

Open
evolutionise opened this issue Nov 29, 2024 · 4 comments
Open

Package Acquisition steps taking 10x longer in 2024.4 #9149

evolutionise opened this issue Nov 29, 2024 · 4 comments
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving

Comments

@evolutionise
Copy link

Severity

Sev 3

Version

2024.4.6945

Latest Version

None

What happened?

Two customers have reported that package acquisition steps are taking up to 10x longer to run on 2024.4.6945 in self-hosted Octopus Deploy installations.

Reproduction

Have not been able to reproduce locally in dev

Error and Stacktrace

No response

More Information

No response

Workaround

To revert to the previous package acquisition step behaviour, set the environment variable

OCTOPUS__FeatureToggles__UseNewAcquirePackagesStepControllerFeatureToggle="false"
@evolutionise evolutionise added the kind/bug This issue represents a verified problem we are committed to solving label Nov 29, 2024
@evolutionise evolutionise self-assigned this Nov 29, 2024
@donnybell
Copy link

Another affected customer [Internal Link]

@octoreleasebot
Copy link

Release Note: Flipped default value of UseNewAcquirePackagesStepControllerFeatureToggle to stop package acquisition steps taking significantly longer

@Octobob
Copy link
Member

Octobob commented Dec 4, 2024

🎉 The fix for this issue has been released in:

Release stream Release
2024.4 2024.4.6962
2025.1 2025.1.2772

@evolutionise evolutionise reopened this Dec 4, 2024
@evolutionise
Copy link
Author

Not closing it as we've shipped a mitigation, not a fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

4 participants