Open czomo opened 11 months ago
Thanks for the report @czomo. We're aware of the problem and will fix asap.
@chrisdoherty4 Any update from your side? It's not working on v1-27-142 neither of any 1.28-*.
Is that fixed? We are hitting same behavior with 1.28.7.
Can you confirm the OS you are using @joeto0 ? Is it Bottlerocket?
Also, @czomo can you confirm the OS you are using as well? Its Ubuntu right?
yes, bottlerocket.
On Wed, Apr 24, 2024 at 6:38 PM Mitali Paygude @.***> wrote:
Can you confirm the OS you are using @joeto0 https://github.com/joeto0 ? Is it Bottlerocket?
Also, @czomo https://github.com/czomo can you confirm the OS you are using as well? Its Ubuntu right?
— Reply to this email directly, view it on GitHub https://github.com/aws/eks-anywhere-packages/issues/1024#issuecomment-2075963870, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC4HXO5BOEOOISNGQTGLBETY7AX6PAVCNFSM6AAAAAA64K3QD2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZVHE3DGOBXGA . You are receiving this because you were mentioned.Message ID: @.***>
Also, @czomo can you confirm the OS you are using as well? Its Ubuntu right?
yes, Ubuntu we find out that in our case faulty was the host Path, as for now we stopped using packages in favour of predefined daemonset '''
What happened: Any version of package bundle above v1-27-128 are not usable because of multiple issues. Should we keep those faulty packages in registry? Is there any end2end test that could detect that in future?
log_1
log_2
What you expected to happen: eks-anywhere-packages shouldn't be published with such breaking changes How to reproduce it (as minimally and precisely as possible):
000000000000.dkr.ecr.eu-west-2.amazonaws.com
registryAnything else we need to know?: We also checked latest v1-28 with k8s 1.28 and it also experience issues the same as v1-27-137
Environment: k8s 1.27, tinker provisioner with bare bone nodes, ubuntu 22.04 ami