Pulkit Tandon

Related bugs


1 → 75 of 116 results First • Previous • • Last
Critical
Fix Committed
#1682080 [Service connections]: Control and agent connection goes unstable on editing entry in agent.conf
Juniper Openstack 282
Critical
Fix Committed
#1682080 [Service connections]: Control and agent connection goes unstable on editing entry in agent.conf
Juniper Openstack trunk 282
Critical
Fix Committed
#1699983 [vDNS: VM do not get default DNS IP if IPAM dns method is not set
Juniper Openstack 12
Critical
Fix Committed
#1699983 [vDNS: VM do not get default DNS IP if IPAM dns method is not set
Juniper Openstack trunk 12
Critical
Fix Committed
#1699983 [vDNS: VM do not get default DNS IP if IPAM dns method is not set
Juniper Openstack r3.2 12
Critical
Fix Committed
#1699983 [vDNS: VM do not get default DNS IP if IPAM dns method is not set
Juniper Openstack r3.2.3.x 12
Critical
Fix Committed
#1699983 [vDNS: VM do not get default DNS IP if IPAM dns method is not set
Juniper Openstack r3.1 12
Critical
Fix Committed
#1699983 [vDNS: VM do not get default DNS IP if IPAM dns method is not set
Juniper Openstack r3.0 12
Critical
Fix Committed
#1712327 [SM]: Not able to add contrail networking image for Centos71 package
Juniper Openstack 8
Critical
Fix Committed
#1712327 [SM]: Not able to add contrail networking image for Centos71 package
Juniper Openstack r4.0 8
Critical
Fix Committed
#1712327 [SM]: Not able to add contrail networking image for Centos71 package
Juniper Openstack trunk 8
Critical
Fix Committed
#1712479 [SM]: Add image failed for centos networking
Juniper Openstack 6
Critical
Fix Committed
#1712479 [SM]: Add image failed for centos networking
Juniper Openstack r4.0 6
Critical
Fix Committed
#1712479 [SM]: Add image failed for centos networking
Juniper Openstack trunk 6
Critical
Fix Committed
#1682080 [Service connections]: Control and agent connection goes unstable on editing entry in agent.conf
Juniper Openstack r3.1 282
Critical
Fix Committed
#1682080 [Service connections]: Control and agent connection goes unstable on editing entry in agent.conf
Juniper Openstack r3.2 282
Critical
Fix Committed
#1682080 [Service connections]: Control and agent connection goes unstable on editing entry in agent.conf
Juniper Openstack r2.21.x 282
Critical
In Progress
#1752657 [k8s-R5.0-Single-Yaml-Prov]: k8s provisioning using single yaml failed
Juniper Openstack 14
Critical
In Progress
#1752657 [k8s-R5.0-Single-Yaml-Prov]: k8s provisioning using single yaml failed
Juniper Openstack trunk 14
Critical
Fix Committed
#1760217 Provision fails for Contrail 5.0 (contrail-ansible-deployer) for orch: K8s
Juniper Openstack 18
Critical
Fix Committed
#1760217 Provision fails for Contrail 5.0 (contrail-ansible-deployer) for orch: K8s
Juniper Openstack trunk 18
Critical
Fix Committed
#1760217 Provision fails for Contrail 5.0 (contrail-ansible-deployer) for orch: K8s
Juniper Openstack r5.0 18
Critical
Fix Committed
#1752657 [k8s-R5.0-Single-Yaml-Prov]: k8s provisioning using single yaml failed
Juniper Openstack r5.0 14
Critical
Fix Committed
#1764506 [k8s-R5.0]: Agent crash observed on k8s sanity run
Juniper Openstack 6
Critical
Fix Committed
#1764506 [k8s-R5.0]: Agent crash observed on k8s sanity run
Juniper Openstack trunk 6
High
Fix Committed
#1540777 [Discovery_R3.0_Ubuntu_2704] : Subscribe request do not subscribe to multiple publishers if multiple rules are present having different publishers and same subscribers
Juniper Openstack 6
High
New
#1543108 [Discovery_R3.0_Ubuntu_2711]: XMPP server is not doing load balancing and Auto load balancing is also not working for xmpp-server
Juniper Openstack 6
High
Fix Committed
#1548638 [Discovery-Rel3.0-Centos-1]: All clients re-subscribe to a different publisher when a rule is added which was supposed to affect only 1 subscriber (No Auto load balance)
Juniper Openstack 6
High
Fix Committed
#1548771 [Discovery-Rel3.0-Centos-1]: Applying rule on DNS-server affects the rule entry already applied to XMPP server and vice versa. (Tested for client type : vrouter-agent)
Juniper Openstack 6
High
New
#1543108 [Discovery_R3.0_Ubuntu_2711]: XMPP server is not doing load balancing and Auto load balancing is also not working for xmpp-server
Juniper Openstack r3.0 6
High
Fix Committed
#1540777 [Discovery_R3.0_Ubuntu_2704] : Subscribe request do not subscribe to multiple publishers if multiple rules are present having different publishers and same subscribers
Juniper Openstack trunk 6
High
Fix Committed
#1548771 [Discovery-Rel3.0-Centos-1]: Applying rule on DNS-server affects the rule entry already applied to XMPP server and vice versa. (Tested for client type : vrouter-agent)
Juniper Openstack trunk 6
High
Fix Committed
#1548638 [Discovery-Rel3.0-Centos-1]: All clients re-subscribe to a different publisher when a rule is added which was supposed to affect only 1 subscriber (No Auto load balance)
Juniper Openstack trunk 6
High
Fix Committed
#1583566 [vDNS]: Records lost on named restart if scaled configuration is present
Juniper Openstack 6
High
Fix Committed
#1583566 [vDNS]: Records lost on named restart if scaled configuration is present
Juniper Openstack r3.0 6
High
Fix Committed
#1583566 [vDNS]: Records lost on named restart if scaled configuration is present
Juniper Openstack trunk 6
High
New
#1543108 [Discovery_R3.0_Ubuntu_2711]: XMPP server is not doing load balancing and Auto load balancing is also not working for xmpp-server
Juniper Openstack trunk 6
High
Fix Committed
#1583566 [vDNS]: Records lost on named restart if scaled configuration is present
Juniper Openstack r2.20 6
High
Fix Committed
#1583566 [vDNS]: Records lost on named restart if scaled configuration is present
Juniper Openstack r2.22.x 6
High
Fix Committed
#1583566 [vDNS]: Records lost on named restart if scaled configuration is present
Juniper Openstack r2.21.x 6
High
New
#1597487 [vDNS]: Difference in memory utilization of named just after configurations and after restart
Juniper Openstack 6
High
Fix Committed
#1583566 [vDNS]: Records lost on named restart if scaled configuration is present
Juniper Openstack r3.0.2.x 6
High
New
#1543108 [Discovery_R3.0_Ubuntu_2711]: XMPP server is not doing load balancing and Auto load balancing is also not working for xmpp-server
Juniper Openstack r3.1 6
High
New
#1597487 [vDNS]: Difference in memory utilization of named just after configurations and after restart
Juniper Openstack trunk 6
High
New
#1606448 [qos]: Fabric based qos config not working
Juniper Openstack 8
High
New
#1606448 [qos]: Fabric based qos config not working
Juniper Openstack r3.1 8
High
Fix Committed
#1610232 [Discovery-R3.1]: Discovery server not accepting admin token in X-Auth-Token header of incoming request
Juniper Openstack r3.1 6
High
Fix Committed
#1712261 [SM] contrail-docs package not loaded while provisioning
Juniper Openstack 6
High
Fix Committed
#1712261 [SM] contrail-docs package not loaded while provisioning
Juniper Openstack trunk 6
High
Fix Committed
#1712261 [SM] contrail-docs package not loaded while provisioning
Juniper Openstack r4.0 6
High
Fix Committed
#1732406 [R4.1]: Analytics down on fresh provisioning due to zookeeper not coming up
Juniper Openstack 8
High
Fix Committed
#1732406 [R4.1]: Analytics down on fresh provisioning due to zookeeper not coming up
Juniper Openstack trunk 8
High
Fix Committed
#1732406 [R4.1]: Analytics down on fresh provisioning due to zookeeper not coming up
Juniper Openstack r4.1 8
High
New
#1732607 [K8s]: Agent down in new pod after initial agent pod is killed
Juniper Openstack r4.0 6
High
Fix Committed
#1732406 [R4.1]: Analytics down on fresh provisioning due to zookeeper not coming up
Juniper Openstack r4.0 8
High
New
#1732607 [K8s]: Agent down in new pod after initial agent pod is killed
Juniper Openstack r4.1 6
High
Fix Committed
#1735590 [Openshift/K8S] : When configuring SNAT router host losing connectivity
Juniper Openstack 12
High
Fix Committed
#1735590 [Openshift/K8S] : When configuring SNAT router host losing connectivity
Juniper Openstack r4.1 12
High
Fix Committed
#1735590 [Openshift/K8S] : When configuring SNAT router host losing connectivity
Juniper Openstack trunk 12
High
Fix Committed
#1735874 K8S: Analytics services fail when 3 node HA setup is brought up using single yaml
Juniper Openstack 6
High
Fix Committed
#1735874 K8S: Analytics services fail when 3 node HA setup is brought up using single yaml
Juniper Openstack trunk 6
High
Fix Committed
#1735874 K8S: Analytics services fail when 3 node HA setup is brought up using single yaml
Juniper Openstack r4.1 6
High
New
#1737488 [R4.1 - 59] Core observed during k8s sanity run (core.async_5)
Juniper Openstack r4.1 6
High
New
#1761137 [k8s]: k8s master HA not supported
Juniper Openstack 6
High
New
#1761137 [k8s]: k8s master HA not supported
Juniper Openstack trunk 6
High
New
#1761137 [k8s]: k8s master HA not supported
Juniper Openstack r5.0 6
High
Fix Committed
#1735590 [Openshift/K8S] : When configuring SNAT router host losing connectivity
Juniper Openstack r5.0 12
High
Fix Committed
#1765941 [k8s-R5.0]: Sync between Control and data plane required to handle situations where CNI miss the messages
Juniper Openstack 6
High
Fix Committed
#1765941 [k8s-R5.0]: Sync between Control and data plane required to handle situations where CNI miss the messages
Juniper Openstack r5.0 6
High
Fix Committed
#1765941 [k8s-R5.0]: Sync between Control and data plane required to handle situations where CNI miss the messages
Juniper Openstack trunk 6
High
Fix Committed
#1770316 [QOS-R5.0]: Not able to set qos queue scheduling
Juniper Openstack 6
High
Fix Committed
#1770316 [QOS-R5.0]: Not able to set qos queue scheduling
Juniper Openstack r5.0 6
High
Fix Committed
#1770316 [QOS-R5.0]: Not able to set qos queue scheduling
Juniper Openstack trunk 6
High
Fix Committed
#1773786 [R4.1-k8s] K8s sanity test case fix
Juniper Openstack r4.1 6
High
Fix Committed
#1781119 [k8s-5.0.1]: In multi cluster nested environment, Pod with same name and namespace name is not reachable
Juniper Openstack 6
1 → 75 of 116 results First • Previous • • Last