EasyRSA Charm

invalid constraint value: arch=amd64 valid values are: [arm64 armhf]

Bug #1981116 reported by Takuya Shibuta on 2022-07-09

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	EasyRSA Charm	Incomplete	Medium	Unassigned	EasyRSA Charm 1.29

Bug Description

I'm not sure if this is a matter to be reported here but let me take a shot.
I got the following error messgae when executed following command

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ubuntu@ubuntu:~$ juju deploy charmed-kubernetes
Located bundle "charmed-kubernetes" in charm-hub, revision 1020
Located charm "easyrsa" in charm-hub, channel stable
Located charm "etcd" in charm-hub, channel stable
Located charm "kubeapi-load-balancer" in charm-hub, channel stable
Located charm "kubernetes-control-plane" in charm-hub, channel stable
Located charm "kubernetes-worker" in charm-hub, channel stable
Executing changes:
- upload charm easyrsa from charm-hub for series focal from channel stable with arch
itecture=amd64
- deploy application easyrsa from charm-hub on focal with stable
ERROR cannot deploy bundle: cannot deploy application "easyrsa": cannot add applicat
ion "easyrsa": invalid constraint value: arch=amd64
valid values are: [arm64 armhf]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
steps to reproduce:

https://ubuntu.com/kubernetes/install

Environment:
Raspberry Pi 4 Model B (8GB)
Linux ubuntu 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aar
ch64 aarch64 aarch64 GNU/Linux

I'm not sure if this is intended or not.
But I thought I report it, in case this was unintended.
I hope this gets resolved.
I'd be happy if there is a work around for this.

Thanks in advance.

See original description

Takuya Shibuta (japbhangra) on 2022-07-09

description:

updated

Takuya Shibuta (japbhangra) on 2022-07-09

summary:

- cannot add applicat ion "easyrsa": invalid constraint value: arch=amd64
+ invalid constraint value: arch=amd64 valid values are: [arm64 armhf]

Chris Johnston (cjohnston) on 2022-11-07

Changed in charm-easyrsa:
status:	New → Confirmed

Kevin W Monroe (kwmonroe) on 2023-04-06

Changed in charm-easyrsa:
milestone:	none → 1.27+ck1
importance:	Undecided → Medium

Revision history for this message

Kevin W Monroe (kwmonroe) wrote on 2023-05-26:

We're addressing this in the ops re-write, planned for ck8s 1.28.

Changed in charm-easyrsa:
milestone:	1.27+ck1 → 1.28

Revision history for this message

Adam Dyess (addyess) wrote on 2023-08-07:

@japbhangra

I know it's been far too long before looking at this -- i apologize sincerely for that.

I wanted to try to address this issue and saw that your bundle deployment ran into an issue deploying `easyrsa` from a ras-pi juju client which of course is arm64. I frequently test against arm64 instances on AWS and don't run into trouble with the deployment -- but I feel like there's a constraint somewhere in the bundle you've deployed which is defaulting the easyrsa unit to have an arch=amd64

I'm making this assessment based on `invalid constraint value: arch=amd64`

I've looked at the current stable charmed-kubernetes bundle and the only constraints on workers is:

`constraints: cores=2 mem=8G root-disk=16G`

the architecture of the juju client (ie -- the terminal you launch the juju deploy from) shouldn't necessarily influence the architecture of the target cloud. I think what's happening is that juju doesn't know it needs to constrain the architecture of your cloud to arm64 machines (if that's what is intended) [1]

When I need to deploy charmed-kubernetes to arm64 only, here's the overlay I deploy with -- effectively forcing juju's hand on deploying the a different architecture rather than letting it have to pick based on the type of cloud you're asking juju to deploy to.

--------------------------------
# arm64-overlay.yaml
applications:
  easyrsa:
    constraints: "arch=arm64 cores=2 mem=8G root-disk=16G"
  etcd:
    constraints: "arch=arm64 cores=2 mem=8G root-disk=16G"
  kubeapi-load-balancer:
    constraints: "arch=arm64 cores=1 mem=4G root-disk=16G"
  kubernetes-control-plane:
    constraints: "arch=arm64 cores=2 mem=8G root-disk=16G"
  kubernetes-worker:
    constraints: "arch=arm64 cores=2 mem=8G root-disk=16G"
machines:
  "0":
    constraints: "arch=arm64"
  "1":
    constraints: "arch=arm64"
  "2":
    constraints: "arch=arm64"
  "3":
    constraints: "arch=arm64"
  "4":
    constraints: "arch=arm64"
  "5":
    constraints: "arch=arm64"
  "6":
    constraints: "arch=arm64"
  "7":
    constraints: "arch=arm64"
  "8":
    constraints: "arch=arm64"
  "9":
    constraints: "arch=arm64"
------------------------------

[1] https://juju.is/docs/juju/constraint

@japbhangra

I know it's been far too long before looking at this -- i apologize sincerely for that.

I wanted to try to address this issue and saw that your bundle deployment ran into an issue deploying `easyrsa` from a ras-pi juju client which of course is arm64.  I frequently test against arm64 instances on AWS and don't run into trouble with the deployment -- but I feel like there's a constraint somewhere in the bundle you've deployed which is defaulting the easyrsa unit to have an arch=amd64

I'm making this assessment based on `invalid constraint value: arch=amd64`

I've looked at the current stable charmed-kubernetes bundle and the only constraints on workers is:

`constraints: cores=2 mem=8G root-disk=16G`

[1] https://juju.is/docs/juju/constraint

Changed in charm-easyrsa:
status:	Confirmed → Incomplete

Adam Dyess (addyess) on 2023-08-18

Changed in charm-easyrsa:
milestone:	1.28 → 1.28+ck1

Adam Dyess (addyess) on 2023-09-20

Changed in charm-easyrsa:
milestone:	1.28+ck1 → 1.29

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.