Open mdavis-xyz opened 5 years ago
Thanks for filing this issue @mlda065!
I am not able to reproduce this so I suspect that this may be an issue in how the GUI is processing valid relationships. Are the two charms in question public? Or can you maybe provide two sample charms with the same relation metadata?
git clone https://github.com/Juniper/contrail-charms -b R5
cd contrail-charms
juju deploy bundle.yaml
contrail-analytics:contrail-analyticsdb - contrail-analyticsdb:contrail-analyticsdb
juju add-relation contrail-analytics contrail-analyticsdb
series: bionic
variables:
openstack-origin: &openstack-origin distro
openstack-region: &openstack-region RegionOne
oam-space: &oam-space oam-space
admin-space: &admin-space oam-space
public-space: &public-space oam-space
internal-space: &internal-space internal-space
overlay-space: &overlay-space internal-space
ceph-public-space: &ceph-public-space ceph-access-space
ceph-cluster-space: &ceph-cluster-space ceph-replica-space
oam-space-constr: &oam-space-constr spaces=oam-space
ceph-access-constr: &ceph-access-constr spaces=ceph-access-space
osd-devices: &osd-devices /dev/sdb
aodh-vip: &aodh-vip "10.246.64.80"
ceilometer-vip: &ceilometer-vip "10.246.64.81"
cinder-vip: &cinder-vip "10.246.64.82"
dashboard-vip: &dashboard-vip "10.246.64.83"
designate-vip: &designate-vip "10.246.64.84"
glance-vip: &glance-vip "10.246.64.85"
gnocchi-vip: &gnocchi-vip "10.246.64.86"
heat-vip: &heat-vip "10.246.64.87"
keystone-vip: &keystone-vip "10.246.64.88"
mysql-vip: &mysql-vip "10.246.64.89"
neutron-api-vip: &neutron-api-vip "10.246.64.90"
nova-cc-vip: &nova-cc-vip "10.246.64.91"
rados-gateway-vip: &rados-gateway-vip "10.246.64.92"
contrail-keepalived: &contrail-keepalived-vip "10.246.64.93"
worker-multiplier: &worker-multiplier 0.25
docker-registry: &docker-registry "hub.juniper.net/contrail-nightly"
docker-user: &docker-user wrongUser
docker-password: &docker-password wrongPassword
image-tag: &image-tag "5.1.0-0.573-queens"
docker-registry-insecure: &docker-registry-insecure false
machines:
"1":
constraints: tags=spare
series: bionic
services:
ubuntu:
charm: cs:ubuntu
num_units: 1
bindings:
to: [ "1" ]
ntp:
charm: cs:ntp
num_units: 0
options:
source: ntp.ubuntu.com
contrail-openstack:
charm: ./contrail-openstack
series: bionic
num_units: 0
options:
docker-registry: *docker-registry
docker-user: *docker-user
docker-password: *docker-password
image-tag: *image-tag
docker-registry-insecure: *docker-registry-insecure
contrail-agent:
charm: ./contrail-agent
num_units: 0
series: bionic
options:
log-level: "SYS_DEBUG"
docker-registry: *docker-registry
docker-user: *docker-user
docker-password: *docker-password
image-tag: *image-tag
docker-registry-insecure: *docker-registry-insecure
vhost-gateway: "10.58.1.1"
physical-interface: "nfp_p0"
contrail-agent-dpdk:
charm: ./contrail-agent
num_units: 0
series: bionic
options:
log-level: "SYS_DEBUG"
docker-registry: *docker-registry
docker-user: *docker-user
docker-password: *docker-password
image-tag: *image-tag
docker-registry-insecure: *docker-registry-insecure
dpdk: true
dpdk-main-mempool-size: "65536"
dpdk-pmd-txd-size: "2048"
dpdk-pmd-rxd-size: "2048"
dpdk-driver: ""
dpdk-coremask: "1-4"
vhost-gateway: "10.58.1.1"
physical-interface: "nfp_p0"
contrail-analytics:
charm: ./contrail-analytics
num_units: 1
series: bionic
bindings:
options:
log-level: "SYS_DEBUG"
docker-registry: *docker-registry
docker-user: *docker-user
docker-password: *docker-password
image-tag: *image-tag
docker-registry-insecure: *docker-registry-insecure
control-network: "10.58.1.1/24"
to: [ "1" ]
contrail-analyticsdb:
charm: ./contrail-analyticsdb
num_units: 1
series: bionic
bindings:
options:
log-level: "SYS_DEBUG"
cassandra-minimum-diskgb: "4"
cassandra-jvm-extra-opts: "-Xms8g -Xmx8g"
docker-registry: *docker-registry
docker-user: *docker-user
docker-password: *docker-password
image-tag: *image-tag
docker-registry-insecure: *docker-registry-insecure
control-network: "10.58.1.1/24"
to: [ "1" ]
contrail-controller:
charm: ./contrail-controller
series: bionic
num_units: 1
bindings:
options:
log-level: "SYS_DEBUG"
cassandra-minimum-diskgb: "4"
cassandra-jvm-extra-opts: "-Xms8g -Xmx8g"
docker-registry: *docker-registry
docker-user: *docker-user
docker-password: *docker-password
image-tag: *image-tag
docker-registry-insecure: *docker-registry-insecure
control-network: "10.58.1.1/24"
auth-mode: no-auth
to: [ "1" ]
contrail-keystone-auth:
charm: ./contrail-keystone-auth
series: bionic
num_units: 1
bindings:
to: [ "lxd:1" ]
relations:
- [ "ubuntu", "ntp" ]
- [ "contrail-controller", "contrail-keystone-auth" ]
- [ "contrail-analytics", "contrail-analyticsdb" ]
- [ "contrail-controller", "contrail-analytics" ]
- [ "contrail-controller", "contrail-analyticsdb" ]
- [ "contrail-openstack", "contrail-controller" ]
- [ "contrail-agent", "contrail-controller"]
@hatched Is this still relevant?
We'll need to follow-up on this response and see if we can reproduce.
Steps to reproduce
Alternatively, click on the new relation button in the graph itself, and drag the end of that line over another circle,
Expected Behavior
The list of all possible relations should appear.
When dragging the end of that line for a new relation, applications which can have a relation with that application should be selectable.
I am able to create a relationship between this particular application and another using the command line. So a valid relationship possibility definitely exists.
Actual behavior
When dragging the end of that line for a new relation, all circles are greyed out. Releasing the mouse button over another circle does not result in a relationship creation.