Comment 1 for bug 1961448
Revision history for this message
| Rodrigo Barbieri (rodrigo-barbieri2010) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
quick update, I repeated my tests now doing relation-set of the ingress-address and egress-subnets properties as well, logs still showed "None" being read from the relation, I further insisted on "juju resolved --no-retry" and saw the properties now being read successfully. A juju config command flipping debug value later broke it again, but it healed itself afterwards.
So right now it seems the most consistent workaround is to apply the properties manually through relation-set and insist on "juju resolved --no-retry" until it finally works. Still, a bugfix is needed to force the network-get to be invoked and update the properties.