Comment 5 for bug 1829559

I just want to make sure we validate 2.5 does have the same exact issue
before the backport please.

On Thu, May 23, 2019 at 3:20 PM Achilleas Anagnostopoulos <
<email address hidden>> wrote:

> The actual code in the manual provider hasn't really changed since 2.4
> (that is as far as I searched).
>
> Unless something has radically changed in the state code between 2.5 and
> 2.6 backporting the fix will most likely fix it for 2.5 as well.
>
> I will backport and merge first thing in the morning.
>
> /A
>
> On Thu, 23 May 2019, 8:00 pm Richard Harding <<email address hidden>
> wrote:
>
> > There was an issue around manual and 2.5 as well. Can you please confirm
> > if 2.5 has the same issue and if so backport this and include it against
> > the 2.5 tree?
> >
> > Thanks
> >
> > --
> > You received this bug notification because you are a bug assignee.
> > https://bugs.launchpad.net/bugs/1829559
> >
> > Title:
> > cannot deploy with manual provider - 2.6.2, s390x
> >
> > Status in juju:
> > Fix Committed
> > Status in Ubuntu on IBM z Systems:
> > Fix Committed
> >
> > Bug description:
> > juju 2.6.2 on an amd64 instance as the controller, with s390x manual
> > machines
> >
> > I have provisioned 5 s390x machines, which are successfully added to
> > the model:
> >
> > Model Controller Cloud/Region Version SLA
> > Timestamp
> > s390x-mosci-s390x s390x-mosci-s390x manual 2.6.2
> > unsupported 15:52:46Z
> >
> > Machine State DNS Inst id Series AZ Message
> > 5 started 10.13.3.10 manual:10.13.3.10 bionic Manually
> > provisioned machine
> > 6 started 10.13.3.11 manual:10.13.3.11 bionic Manually
> > provisioned machine
> > 7 started 10.13.3.12 manual:10.13.3.12 bionic Manually
> > provisioned machine
> > 8 started 10.13.3.13 manual:10.13.3.13 bionic Manually
> > provisioned machine
> > 9 started 10.13.3.14 manual:10.13.3.14 bionic Manually
> > provisioned machine
> >
> > Note re unit numbering, the exact same issues were present with 0-4.
> >
> > I am unable to deploy a bundle with --map-machines=existing, e.g.:
> >
> > $ juju deploy bundle.yaml --map-machines=existing
> > ...
> > Resolving charm: cs:~openstack-charmers-next/swift-storage
> > Executing changes:
> > - upload charm cs:~openstack-charmers-next/cinder-374 for series bionic
> > - deploy application cinder on bionic using
> > cs:~openstack-charmers-next/cinder-374
> > ERROR cannot deploy bundle: cannot deploy application "cinder": cannot
> > add application "cinder": use "juju add-machine ssh:[user@]<host>" to
> > provision machines
> >
> > debug log: https://pastebin.canonical.com/p/xmydKcJJcs/
> > bundle url:
> >
> https://raw.githubusercontent.com/ubuntu-openstack/zopenstack/master/bundles/lpar/bionic-stein-stable.yaml
> >
> >
> > I am able to manually deploy a principal charm using --to:
> >
> > $ juju deploy cs:~openstack-charmers-next/cinder-374 --to lxd:5
> > Located charm "cs:~openstack-charmers-next/cinder-374".
> > Deploying charm "cs:~openstack-charmers-next/cinder-374".
> > $ juju status
> > Model Controller Cloud/Region Version SLA
> > Timestamp
> > s390x-mosci-s390x s390x-mosci-s390x manual 2.6.2
> > unsupported 15:57:30Z
> >
> > App Version Status Scale Charm Store Rev OS Notes
> > cinder waiting 0/1 cinder jujucharms 374 ubuntu
> >
> > Unit Workload Agent Machine Public address Ports Message
> > cinder/2 waiting allocating 5/lxd/0 waiting
> > for machine
> >
> > Machine State DNS Inst id Series AZ Message
> > 5 started 10.13.3.10 manual:10.13.3.10 bionic Manually
> > provisioned machine
> > 5/lxd/0 pending pending bionic
> >
> >
> > So I can use this method to deploy charms manually, until I get to a
> > subordinate charm:
> >
> > $ juju deploy neutron-openvswitch
> > Located charm "cs:neutron-openvswitch-259".
> > Deploying charm "cs:neutron-openvswitch-259".
> > ERROR cannot add application "neutron-openvswitch": use "juju
> > add-machine ssh:[user@]<host>" to provision machines
> > $ juju deploy neutron-openvswitch --num-units=0
> > ERROR --num-units must be a positive integer
> > $ juju deploy neutron-openvswitch --to 0
> > Located charm "cs:neutron-openvswitch-259".
> > Deploying charm "cs:neutron-openvswitch-259".
> > ERROR cannot use --num-units or --to with subordinate application
> >
> > debug log:
> >
> > https://pastebin.canonical.com/p/vZ8PScRWVr/
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/juju/+bug/1829559/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to juju.
> https://bugs.launchpad.net/bugs/1829559
>
> Title:
> cannot deploy with manual provider - 2.6.2, s390x
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1829559/+subscriptions
>