NPK not recognizing my spot instance increases.
Just as the title says, NPK is not recognizing that I've increased my spot instance quota. I've recently gotten it moved up to 64 for all G and VT Spot Instances but NPK still thinks my quota is 16 which results in four instances available at any given time. I should be able to see 16 available instances now but when I re-installed NPK and update and hopefully have my instance reflect the new instance availability count, it was still displaying only four instances.
Also, the instructions for spot increases are outdated. Please advise.
Hi there, I've also just got my increased spot instances, but NPK does not update the new Quota. I've searched within the configs and docs on how to retrigger an update of quota, but haven't found anything so far.
Did a reinstall work with the new quota applied properly?
For anyone in the Future encountering this issue: run the oneliner again -> npm run update -> if the quota does not refresh on the first try, repeat again, as I had to do it multiple times
This isn't correct. Running the one-liner once is sufficient. If the change isn't showing in your browser, use Shift+F5 to refresh without cache.
I'll plan to add a cachebuster to the JS so this isn't so confusing.
On Wed, Oct 16, 2024 at 9:37 AM Tobias Rauch @.***> wrote:
For anyone in the Future encountering this issue: run the oneliner again -> npm run update -> if the quota does not refresh on the first try, repeat again, as I had to do it multiple times
— Reply to this email directly, view it on GitHub https://github.com/c6fc/npk/issues/100#issuecomment-2417199889, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABDAN6SQ2OVHSXUTRZCZG3Z32B2FAVCNFSM6AAAAABQBIT2CWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJXGE4TSOBYHE . You are receiving this because you are subscribed to this thread.Message ID: @.***>
-- Brad Woodward AWS PSA+SCS, OSCP, OSCE, MCITP, MCSA, CISSP-ISSAP, CRISC, CPSA, CRT
@.*** @bradwoodward_io
Sounds perfect 😃