[Bug 2029116] [NEW] Apps in co-located container does not have all interfaces required by spaces

[Bartosz Woronicz]

Public bug reported:

Tested on juju-2.9.44 and juju-3.2.0
installed:          2.9.44                       (23558) 98MB classic
installed:          3.2.0                        (23190) 80MB -

If we have two applications sharing the same container like historically
designate-bind and memcached
we encounter the issue that if the application first created has less spaces
than the one that will rely upon juju will silently create the unit without complaining

I think that should be checked at least at the bundle validation level

  designate-bind:
    num_units: 3
    to:
    - memcached/0
    - memcached/1
    - memcached/2

Example configuration

  memcached:
    bindings:
      ? ''
      : oam-space
      cache: internal-space
    charm: memcached
    num_units: 2
    options:
      allow-ufw-ip6-softfail: true
    series: jammy
    ...

  designate-bind:
    bindings:
      ? ''
      : oam-space
      certificates: internal-space
      dns-backend: internal-space
      dns-frontend: provided-dns-access-space
    channel: yoga/stable
    charm: designate-bind
    num_units: 2
    options:
      disable-dnssec-validation: true
      forwarders: '"10.169.135.1;10.169.135.2;10.169.135.3"

        '
      recursion: true
      use-internal-endpoints: true
    series: jammy

    ...

** Affects: juju (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  Tested on juju-2.9.44 and juju-3.2.0
  installed:          2.9.44                       (23558) 98MB classic
  installed:          3.2.0                        (23190) 80MB -
  
  If we have two applications sharing the same container like historically
- designate-bind and memcached 
+ designate-bind and memcached
  we encounter the issue that if the application first created has less spaces
  than the one that will rely upon juju will silently create the unit without complaining
  
  I think that should be checked at least at the bundle validation level
  
-   designate-bind:
-     num_units: 3
-     to:
-     - memcached/0
-     - memcached/1
-     - memcached/2
+   designate-bind:
+     num_units: 3
+     to:
+     - memcached/0
+     - memcached/1
+     - memcached/2
  
  Example configuration
  
-   memcached:
+   memcached:
+     bindings:
+       ? ''
+       : oam-space
+       cache: internal-space
+     charm: memcached
+     num_units: 2
+     options:
+       allow-ufw-ip6-softfail: true
+     series: jammy
+     ...
+ 
+   designate-bind:
      bindings:
        ? ''
        : oam-space
-       cache: internal-space
-     charm: memcached
+       certificates: internal-space
+       dns-backend: internal-space
+       dns-frontend: provided-dns-access-space
+     channel: yoga/stable
+     charm: designate-bind
      num_units: 2
      options:
-       allow-ufw-ip6-softfail: true
+       disable-dnssec-validation: true
+       forwarders: '"10.169.135.1;10.169.135.2;10.169.135.3"
+ 
+         '
+       recursion: true
+       use-internal-endpoints: true
      series: jammy
-     ...
  
-   designate:
-     bindings:
-       ? ''
-       : oam-space
-       admin: external-space
-       amqp: internal-space
-       certificates: internal-space
-       coordinator-memcached: internal-space
-       dns-backend: internal-space
-       identity-service: internal-space
-       internal: internal-space
-       public: external-space
-       shared-db: internal-space
-     channel: yoga/stable
-     charm: designate
-     num_units: 3
-     ...
+     ...

** Package changed: software-properties (Ubuntu) => juju (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/2029116

Title:
  Apps in co-located container does not have all interfaces required by
  spaces

Status in juju package in Ubuntu:
  New

Bug description:
  Tested on juju-2.9.44 and juju-3.2.0
  installed:          2.9.44                       (23558) 98MB classic
  installed:          3.2.0                        (23190) 80MB -

  If we have two applications sharing the same container like historically
  designate-bind and memcached
  we encounter the issue that if the application first created has less spaces
  than the one that will rely upon juju will silently create the unit without complaining

  I think that should be checked at least at the bundle validation level

    designate-bind:
      num_units: 3
      to:
      - memcached/0
      - memcached/1
      - memcached/2

  Example configuration

    memcached:
      bindings:
        ? ''
        : oam-space
        cache: internal-space
      charm: memcached
      num_units: 2
      options:
        allow-ufw-ip6-softfail: true
      series: jammy
      ...

    designate-bind:
      bindings:
        ? ''
        : oam-space
        certificates: internal-space
        dns-backend: internal-space
        dns-frontend: provided-dns-access-space
      channel: yoga/stable
      charm: designate-bind
      num_units: 2
      options:
        disable-dnssec-validation: true
        forwarders: '"10.169.135.1;10.169.135.2;10.169.135.3"

          '
        recursion: true
        use-internal-endpoints: true
      series: jammy

      ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju/+bug/2029116/+subscriptions