*** This bug is a duplicate of bug 1435283 ***
https://bugs.launchpad.net/bugs/1435283
** This bug has been marked a duplicate of bug 1435283
juju occasionally switches a units public-address if an additional interface
is added post-deployment
--
You received this bug notification becaus
** Changed in: juju-core
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307445
Title:
openstack: instances with multiple nics on the same network don't have
determini
Michael, please see comments in bug 1435283 which iiuc is the same issue
(so essentially a duplicate). Comment #11 explains one possible solution
to the problem. Essentially what we want is for Juju to pick a
port/interface on unit start and remember it (e.g. by uuid) so that if
extra ports/interfa
** Changed in: juju-core
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307445
Title:
openstack: instances with multiple nics on the same network don't have
de
I'm sorry, but from the wording of the report it isn't clear to me
(genuine apologies) what behaviour you *want* (i.e. what the problem is
beyond "This can result in some odd behaviour"?
Is it just that you want a deterministic choice rather than apparently
"random", or is there one that should be
** Changed in: juju-core
Milestone: None => 1.25.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307445
Title:
openstack: instances with multiple nics on the same network don't have
determini
** Changed in: juju-core
Importance: Low => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307445
Title:
openstack: instances with multiple nics on the same network don't have
deterministi
** Tags added: network
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307445
Title:
openstack: instances with multiple nics on the same network don't have
deterministic private-addresses
To manag
** Changed in: juju-core
Status: New => Triaged
** Tags added: addressability openstack-provider
** Changed in: juju-core
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Changed in: juju-core (Ubuntu)
Importance: Undecided => Low
** Changed in: juju-core (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307445
Title:
openst
This might be due to the order they are returned in in the Nova or
Neutron API's I guess.
In the above example the configured eth0's are on 10.5.0.15 and
10.5.0.27
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
environment: jamespage
machines:
"11":
agent-state: started
agent-version: 1.18.1
dns-name: 10.5.0.26
instance-id: 24271ee3-b31d-4b7c-85ff-d027c03bd976
instance-state: ACTIVE
series: trusty
hardware: arch=amd64 cpu-cores=1 mem=2048M root-disk=10240M
"22":
agent-s
| 24271ee3-b31d-4b7c-85ff-d027c03bd976 | juju-jamespage-machine-11 | ACTIVE | -
| Running | james-page_admin_net=10.5.0.26, 10.5.0.15|
| 7ecdd56a-0531-41c1-b997-c5ebd8864d69 | juju-jamespage-machine-22 | ACTIVE | -
| Running | james-page_admin_net=10.5.0.27,
13 matches
Mail list logo