[Yahoo-eng-team] [Bug 1837882] Re: while creating external network subnet range through Horizon UI helper message says give subnet range as comma separated but accept hyphen("-")
** Project changed: horizon-cisco-ui => horizon
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1837882
Title:
while creating external network subnet range through Horizon UI helper
message says give subnet range as comma separated but accept
hyphen("-")
Status in OpenStack Dashboard (Horizon):
New
Bug description:
Description: When user is trying to create an external network with
subnet range using hyphen "-" delimiter (20.x.x.10-20.x.x.100) even
when the helper message says clearly notify user the
"(start_ip_range,end_ip_range) as comma separated delimeter" is
going through successfully without error message. please see the Ui
attachment for more info.
Also after giving Hyphen range in the external subnet. External
network window leads to an unexpected error saying "Specify additional
attributes for the subnet" without giving any proper error message.
Pre - condition :
create a tenant router r1 router with gateway external network .
Step1 ->Create external network using admin user from Horizon.
Step2 ->on the create network window . name -> external
project->admin
provider network type->external
leave the physical network blank(but
make sure user has tier 0 gateway set)
Step3-> click next-> subnet name -> subnet1
network address-> Try to give external network range as
that of the gateway ip.
Gateway IP-> Give the gateway IP of the subnet
Step4-> under subnet details. Uncheck the "Enable Dhcp".
allocation pool-> give subnet range as
(20.x.x.10-20.x.x.100)
Step5-> Once user click "next" window comes back to step2 and further
clicking next leads to message "Specify additional attributes for the
subnet"
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1837882/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1833374] [NEW] Default behavior is not consistent while creating FWaaS-v2 group through Horizon Dashboard and through CLI command.
Public bug reported: Description: Creating Firewall Group through openstack CLI command set the admin state to true please find the below command, but through Horizon Dashboard Admin state is set to "False" by default. [root@vioshim-l42jp6xt7m-vioshim-84bb866c4d-lw6wj /]# openstack firewall group create --name F9 +---+--+ | Field | Value| +---+--+ | Description | | | Egress Policy ID | None | | ID| b16bbdd5-ba11-475a-b74a-acf27b3667ac | | Ingress Policy ID | None | | Name | F9 | | Ports | [] | | Project | 52e5cd63615243cd9439952c5214d0f7 | | Shared| False| | State | UP | | Status| INACTIVE | | project_id| 52e5cd63615243cd9439952c5214d0f7 | +---+--+ Expected: Dafault behavior should be consistent whether the Firewall group created using Horizon or through the neutron cLi command. ** Affects: neutron-fwaas-dashboard Importance: Undecided Status: New ** Project changed: neutron => neutron-fwaas-dashboard ** Description changed: - Description: Creating Firewall Group through openstack CLI command - please find the below command, but through Horizon Dashboard Admin - state is set to "False" by default - + Description: Creating Firewall Group through openstack CLI command set + the admin state to true please find the below command, but through + Horizon Dashboard Admin state is set to "False" by default. [root@vioshim-l42jp6xt7m-vioshim-84bb866c4d-lw6wj /]# openstack firewall group create --name F9 +---+--+ | Field | Value| +---+--+ | Description | | | Egress Policy ID | None | | ID| b16bbdd5-ba11-475a-b74a-acf27b3667ac | | Ingress Policy ID | None | | Name | F9 | | Ports | [] | | Project | 52e5cd63615243cd9439952c5214d0f7 | | Shared| False| | State | UP | | Status| INACTIVE | | project_id| 52e5cd63615243cd9439952c5214d0f7 | +---+--+ - - Expected: Dafault behavior should be consistent whether the Firewall group created using Horizon or through the neutron cLi command. + Expected: Dafault behavior should be consistent whether the Firewall + group created using Horizon or through the neutron cLi command. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1833374 Title: Default behavior is not consistent while creating FWaaS-v2 group through Horizon Dashboard and through CLI command. Status in Neutron FWaaS dashboard: New Bug description: Description: Creating Firewall Group through openstack CLI command set the admin state to true please find the below command, but through Horizon Dashboard Admin state is set to "False" by default. [root@vioshim-l42jp6xt7m-vioshim-84bb866c4d-lw6wj /]# openstack firewall group create --name F9 +---+--+ | Field | Value| +---+--+ | Description | | | Egress Policy ID | None | | ID| b16bbdd5-ba11-475a-b74a-acf27b3667ac | | Ingress Policy ID | None | | Name | F9 | | Ports | [] | | Project | 52e5cd63615243cd9439952c5214d0f7 | | Shared| False| | State | UP | | Status| INACTIVE | | project_id| 52e5cd63615243cd9439952c5214d0f7 | +---+--+ Expected: Dafault behavior should be consistent whether the Firewall group created using Horizon or through the neutron cLi
[Yahoo-eng-team] [Bug 1831613] [NEW] Deletion of Lbaas-listener is successfull even when it is part of Lbaas pool
Public bug reported: Description ->Deletion of loadbalancer listener is successfull even when it is attached to Lbaas pool. After deletion of listener when user creates a new listener neutron Cli command do not support addition of new listener in existing lbaas pool. User impact of deletion-> loadbalancer stops working if user able to delete listener accidentally Step to reproduce the scenario-> neutron lbaas-loadbalancer-create --name lb-15 public-subnet neutron lbaas-listener-create --name listener-15-1 --loadbalancer lb-15 --protocol HTTP --protocol-port 80 --connection-limit 1 neutron lbaas-pool-create --name pool-15 --lb-algorithm ROUND_ROBIN --listener listener-15-1 --protocol HTTP neutron lbaas-healthmonitor-create --name health-15 --delay 5 --max-retries 4 --timeout 3 --type PING --pool pool-15 neutron lbaas-listener-delete create a listener again and try to add to existing pool no cli support this operation as well as no Horizon support for the same Expected output-> Two approach to look for. 1. If deletion of listener is possible then addition of listener should also be allowed. 2. Another option is if listener is mandatory field for pool creation then like other field lbaaS listener deletion should throw an error. version of openstack -> stable stein linux ubuntu -> 18.04 Reason why it is needed:(while creation of listener is mandatory for a pool then deletion also should not be allowed without deleting pool). root@vmware:~/vio6.0# neutron lbaas-pool-create --name lb-pool2 --lb-algorithm ROUND_ROBIN --protocol HTTP --insecure neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. /usr/local/lib/python2.7/dist-packages/urllib3/connectionpool.py:857: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings InsecureRequestWarning) /usr/local/lib/python2.7/dist-packages/urllib3/connectionpool.py:857: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings InsecureRequestWarning) At least one of --listener or --loadbalancer must be specified. ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1831613 Title: Deletion of Lbaas-listener is successfull even when it is part of Lbaas pool Status in neutron: New Bug description: Description ->Deletion of loadbalancer listener is successfull even when it is attached to Lbaas pool. After deletion of listener when user creates a new listener neutron Cli command do not support addition of new listener in existing lbaas pool. User impact of deletion-> loadbalancer stops working if user able to delete listener accidentally Step to reproduce the scenario-> neutron lbaas-loadbalancer-create --name lb-15 public-subnet neutron lbaas-listener-create --name listener-15-1 --loadbalancer lb-15 --protocol HTTP --protocol-port 80 --connection-limit 1 neutron lbaas-pool-create --name pool-15 --lb-algorithm ROUND_ROBIN --listener listener-15-1 --protocol HTTP neutron lbaas-healthmonitor-create --name health-15 --delay 5 --max-retries 4 --timeout 3 --type PING --pool pool-15 neutron lbaas-listener-delete create a listener again and try to add to existing pool no cli support this operation as well as no Horizon support for the same Expected output-> Two approach to look for. 1. If deletion of listener is possible then addition of listener should also be allowed. 2. Another option is if listener is mandatory field for pool creation then like other field lbaaS listener deletion should throw an error. version of openstack -> stable stein linux ubuntu -> 18.04 Reason why it is needed:(while creation of listener is mandatory for a pool then deletion also should not be allowed without deleting pool). root@vmware:~/vio6.0# neutron lbaas-pool-create --name lb-pool2 --lb-algorithm ROUND_ROBIN --protocol HTTP --insecure neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. /usr/local/lib/python2.7/dist-packages/urllib3/connectionpool.py:857: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings InsecureRequestWarning) /usr/local/lib/python2.7/dist-packages/urllib3/connectionpool.py:857: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
[Yahoo-eng-team] [Bug 1318550] [NEW] vpnaas:Aether-Vpn_agent is not able to handle two ipsec-site connection creation request simultaneously.
Public bug reported: neutron net-create ext-net1 --router:external=True neutron subnet-create --allocation-pool start=192.142.0.60,end=192.142.0.100 --gateway 192.142.0.1 ext-net1 192.142.0.0/16 --enable_dhcp=False step 1= neutron net-create net1 neutron subnet-create net1 10.10.1.0/24 --name sub1 neutron router-create r1 neutron router-interface-add r1 sub1 neutron router-gateway-set r1 ext-net1 neutron net-create net2 neutron subnet-create net2 10.10.2.0/24 --name sub2 neutron router-create r2 neutron router-interface-add r2 sub2 neutron router-gateway-set r2 ext-net1 neutron vpn-ikepolicy-create ikepolicy1 neutron vpn-ipsecpolicy-create ipsecpolicy1 neutron vpn-service-create --name myvpn1 --description My vpn service r1 sub1 neutron ipsec-site-connection-create --name vpnconnection1 --vpnservice-id myvpn1 --ikepolicy-id ikepolicy1 --ipsecpolicy-id ipsecpolicy1 --peer-address 192.142.0.61 --peer-id 192.142.0.61 --peer-cidr 10.10.2.0/24 --psk secret neutron vpn-ikepolicy-create ikepolicy2 neutron vpn-ipsecpolicy-create ipsecpolicy2 neutron vpn-service-create --name myvpn2 --description My vpn service r2 sub2 neutron ipsec-site-connection-create --name vpnconnection2 --vpnservice- id myvpn2 --ikepolicy-id ikepolicy2 --ipsecpolicy-id ipsecpolicy2 --peer-address 192.142.0.60 --peer-id 192.142.0.60 --peer-cidr 10.10.1.0/24 --psk secret create one more network on site1 net3 with subnet 5.5.5.0/24 sub3 create a network on site2 net4 with subnet 8.8.8.0/24 sub4 create a service objects myvpn3 with r1 and sub3 create a service objects myvpn4 with r2 and sub4 create a ipsecsite connection neutron ipsec-site-connection-create --name vpnconnection3 --vpnservice-id myvpn3 --ikepolicy-id ikepolicy1 --ipsecpolicy-id ipsecpolicy1 --peer-address 192.142.0.61 --peer-id 192.142.0.61 --peer- cidr 5.5.5.0/24 --psk secret neutron ipsec-site-connection-create --name vpnconnection4 --vpnservice-id myvpn2 --ikepolicy-id ikepolicy2 --ipsecpolicy-id ipsecpolicy2 --peer-address 192.142.0.60 --peer-id 192.142.0.60 --peer-cidr 8.8.8.0/24 --psk secret ipsecsite connection with vpnconnection3 and vpnconnection4 always goes into pending create state. basically i am trying to bind two vpn service objects with one routerid ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1318550 Title: vpnaas:Aether-Vpn_agent is not able to handle two ipsec-site connection creation request simultaneously. Status in OpenStack Neutron (virtual network service): New Bug description: neutron net-create ext-net1 --router:external=True neutron subnet-create --allocation-pool start=192.142.0.60,end=192.142.0.100 --gateway 192.142.0.1 ext-net1 192.142.0.0/16 --enable_dhcp=False step 1= neutron net-create net1 neutron subnet-create net1 10.10.1.0/24 --name sub1 neutron router-create r1 neutron router-interface-add r1 sub1 neutron router-gateway-set r1 ext-net1 neutron net-create net2 neutron subnet-create net2 10.10.2.0/24 --name sub2 neutron router-create r2 neutron router-interface-add r2 sub2 neutron router-gateway-set r2 ext-net1 neutron vpn-ikepolicy-create ikepolicy1 neutron vpn-ipsecpolicy-create ipsecpolicy1 neutron vpn-service-create --name myvpn1 --description My vpn service r1 sub1 neutron ipsec-site-connection-create --name vpnconnection1 --vpnservice-id myvpn1 --ikepolicy-id ikepolicy1 --ipsecpolicy-id ipsecpolicy1 --peer-address 192.142.0.61 --peer-id 192.142.0.61 --peer-cidr 10.10.2.0/24 --psk secret neutron vpn-ikepolicy-create ikepolicy2 neutron vpn-ipsecpolicy-create ipsecpolicy2 neutron vpn-service-create --name myvpn2 --description My vpn service r2 sub2 neutron ipsec-site-connection-create --name vpnconnection2 --vpnservice-id myvpn2 --ikepolicy-id ikepolicy2 --ipsecpolicy-id ipsecpolicy2 --peer-address 192.142.0.60 --peer-id 192.142.0.60 --peer-cidr 10.10.1.0/24 --psk secret create one more network on site1 net3 with subnet 5.5.5.0/24 sub3 create a network on site2 net4 with subnet 8.8.8.0/24 sub4 create a service objects myvpn3 with r1 and sub3 create a service objects myvpn4 with r2 and sub4 create a ipsecsite connection neutron ipsec-site-connection-create --name vpnconnection3 --vpnservice-id myvpn3 --ikepolicy-id ikepolicy1 --ipsecpolicy-id ipsecpolicy1 --peer-address 192.142.0.61 --peer-id 192.142.0.61 --peer-cidr 5.5.5.0/24 --psk secret neutron ipsec-site-connection-create --name vpnconnection4 --vpnservice-id myvpn2 --ikepolicy-id ikepolicy2 --ipsecpolicy-id ipsecpolicy2 --peer-address 192.142.0.60 --peer-id 192.142.0.60 --peer-cidr 8.8.8.0/24 --psk secret ipsecsite connection with vpnconnection3 and vpnconnection4 always goes into pending create state. basically i am trying to
[Yahoo-eng-team] [Bug 1318600] [NEW] VPNasS- Vpn service object cannot be updated with multiple subnets
Public bug reported: neutron net-create ext-net1 --router:external=True neutron subnet-create --allocation-pool start=192.142.0.60,end=192.142.0.100 --gateway 192.142.0.1 ext-net1 192.142.0.0/16 --enable_dhcp=False neutron net-create net1 neutron subnet-create net1 10.10.1.0/24 --name sub1 neutron router-create r1 neutron router-interface-add r1 sub1 neutron router-gateway-set r1 ext-net1 neutron net-create net2 neutron subnet-create net2 10.10.2.0/24 --name sub2 neutron router-create r2 neutron router-interface-add r2 sub2 neutron router-gateway-set r2 ext-net1 neutron vpn-ikepolicy-create ikepolicy1 neutron vpn-ipsecpolicy-create ipsecpolicy1 neutron vpn-service-create --name myvpn1 --description My vpn service r1 sub1 neutron vpn-ikepolicy-create ikepolicy2 neutron vpn-ipsecpolicy-create ipsecpolicy2 neutron vpn-service-create --name myvpn2 --description My vpn service r2 sub2 neutron ipsec-site-connection-create --name vpnconnection1 --vpnservice- id myvpn1 --ikepolicy-id ikepolicy1 --ipsecpolicy-id ipsecpolicy1 --peer-address 192.142.0.61 --peer-id 192.142.0.61 --peer-cidr 10.10.2.0/24 --psk secret neutron ipsec-site-connection-create --name vpnconnection2 --vpnservice-id myvpn2 --ikepolicy-id ikepolicy2 --ipsecpolicy-id ipsecpolicy2 --peer-address 192.142.0.60 --peer-id 192.142.0.60 --peer-cidr 10.10.1.0/24 --psk secret create a subnet in the network net1 and net2 respectively. neutron vpn-service-update myvpn1 new-subnet-id 1 neutron vpn-service-update myvpn2 new-subnet-id 2 ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1318600 Title: VPNasS- Vpn service object cannot be updated with multiple subnets Status in OpenStack Neutron (virtual network service): New Bug description: neutron net-create ext-net1 --router:external=True neutron subnet-create --allocation-pool start=192.142.0.60,end=192.142.0.100 --gateway 192.142.0.1 ext-net1 192.142.0.0/16 --enable_dhcp=False neutron net-create net1 neutron subnet-create net1 10.10.1.0/24 --name sub1 neutron router-create r1 neutron router-interface-add r1 sub1 neutron router-gateway-set r1 ext-net1 neutron net-create net2 neutron subnet-create net2 10.10.2.0/24 --name sub2 neutron router-create r2 neutron router-interface-add r2 sub2 neutron router-gateway-set r2 ext-net1 neutron vpn-ikepolicy-create ikepolicy1 neutron vpn-ipsecpolicy-create ipsecpolicy1 neutron vpn-service-create --name myvpn1 --description My vpn service r1 sub1 neutron vpn-ikepolicy-create ikepolicy2 neutron vpn-ipsecpolicy-create ipsecpolicy2 neutron vpn-service-create --name myvpn2 --description My vpn service r2 sub2 neutron ipsec-site-connection-create --name vpnconnection1 --vpnservice-id myvpn1 --ikepolicy-id ikepolicy1 --ipsecpolicy-id ipsecpolicy1 --peer-address 192.142.0.61 --peer-id 192.142.0.61 --peer-cidr 10.10.2.0/24 --psk secret neutron ipsec-site-connection-create --name vpnconnection2 --vpnservice-id myvpn2 --ikepolicy-id ikepolicy2 --ipsecpolicy-id ipsecpolicy2 --peer-address 192.142.0.60 --peer-id 192.142.0.60 --peer-cidr 10.10.1.0/24 --psk secret create a subnet in the network net1 and net2 respectively. neutron vpn-service-update myvpn1 new-subnet-id 1 neutron vpn-service-update myvpn2 new-subnet-id 2 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1318600/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
