-
Notifications
You must be signed in to change notification settings - Fork 18
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
Block charm on inappropriate architecture (warn users about ARM revision deployed to AMD hardware) #463
Comments
Hi @cbartz , as I can see the revision 240 was an ARM build. Did you deploy it to ARM hardware? As your juju CLI is AMD For AMD architecture you should use revision 239 . However I recommend to let juju choose proper revision for your architecture (by using channel without specifying revision). If you still need ARM build, please consider to use 14/candidate revisions (they are going to be stable soon). Resolved? |
@marceloneppel IMHO, we should improve our charm to make sure extected architecture matching to the running hardware and block the charm otherwise, I think such issues will be popular (due to revision pinning in many places). I will keep this open for @lucasgameiroborges to pickup. ACK? |
@taurus-forever Looking at the shell history, it seems I explicitly specified revision 240 (not sure why to be honest, probably to make sure I get the latest rev) and it is on amd. Sorry about that! The experience on charmhub is not good regarding different revs per architecture, it is not even mentioning arm there! |
I find it easiest to filter with |
@cbartz there is an upcoming improvements on CharmHub WEB, so it will be easier to navigate between architectures. Meanwhile, yes, the command recommended above is the safest way to go here. We will keep it open to check architecture in the charm and produce reasonable blocking message on the user mistake. TODO: #463 (comment) Thank you for reporting anyway! |
FYI, related juju feature request to improve UX: https://bugs.launchpad.net/juju/+bug/2073962 |
Actually, there might be a problem in the latest release of this feature, we are investigating the issue now, reopening for clarity! |
Steps to reproduce
juju deploy postgresql-k8s --trust --channel 14/edge --revision=240
Expected behavior
Unit goes into active status.
Actual behavior
Unit goes into error status.
Versions
Operating system: Ubuntu 22.04.4 LTS
Juju CLI: 3.1.8-genericlinux-amd64
Juju agent: 3.1.8
Charm revision: 240
microk8s: MicroK8s v1.29.2 revision 6529
Log output
Juju debug log:
Additional context
The text was updated successfully, but these errors were encountered: