Cannot establish CMR - macaroon auth fails
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Committed
|
Critical
|
Ian Booth | ||
Bug Description
Since the release of Juju version 3.1, I have encountered a critical problem where I am unable to establish cross-model relations.
Steps to Reproduce:
- Install and configure Juju version 3.1 on a supported environment.
- Create multiple models within Juju.
- Attempt to establish a cross-model relation between any two models.
- Observe the error or unexpected behavior preventing the successful establishment of the cross-model relation.
Short steps to reproduce:
```
cd tests
./main.sh -v -p lxd cmr run_offer_consume
```
Detail steps:
```
juju add-model model-offer
echo "Deploy consumed workload and create the offer"
juju deploy juju-qa-
juju offer dummy-source:sink dummy-offer
echo "Check list-offer output"
juju list-offers --format=json | jq -r 'has("dummy-
echo "Deploy workload in consume model"
juju add-model "model-consume"
juju switch "model-consume"
juju deploy juju-qa-dummy-sink
echo "Relate workload in consume model with offer"
juju consume "admin/
juju relate dummy-sink dummy-offer
echo "Provide config for offered workload and change the status of consumed offer"
# Change the dummy-source config for "token" and check that the change
# is represented in the consuming model's dummy-sink unit.
juju switch "model-offer"
juju config dummy-source token=yeah-boi
juju switch "model-consume"
juju status
# wait for the offer goes to an error state
```
It should be possible to establish cross-model relations by specifying the appropriate relation endpoints.
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju: | |
| status: | New → Incomplete |
| Jack Shaw (jack-shaw) wrote | #2 |
| Jack Shaw (jack-shaw) wrote | #3 |
| Max Asnaashari (masnax) wrote | #4 |
| Changed in juju: | |
| status: | Incomplete → Confirmed |
| Ian Booth (wallyworld) wrote | #5 |
| summary: |
- Cannot establish CMR staring from 3.1 + Cannot establish CMR - macaroon auth fails |
| Changed in juju: | |
| importance: | Undecided → Critical |
| status: | Confirmed → Triaged |
| status: | Triaged → In Progress |
| assignee: | nobody → Ian Booth (wallyworld) |
| Ian Booth (wallyworld) wrote | #6 |
| Changed in juju: | |
| milestone: | none → 3.1.3 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| milestone: | 3.1.3 → none |
Juju 3.1.2 works fine for me running a test on aws using the dummy sink and source charms.
Just because the consume model shows a saas error, that is not necessarily a cmr issue - all that indicates is that the offered application has gone into error and that is reported in the consumer model.
You need to investigate the underlying reason why the offered app has gone into error, or if not, what the logs etc show.