[Yahoo-eng-team] [Bug 1977629] [NEW] [ovn]agent's heartbeat time is error
Public bug reported:
when we show an agent, we can check agent's alive and heartbeat time. but now
agent's alive is False,
it's last_heart_at close to the current time, and each show will refresh the
last_heart_at.
The code[1] shows that the heartbeat time returns the current time, we
should return to the real update time
[1]
https://opendev.org/openstack/neutron/src/commit/d253b9fd08b969ebab09a5624df127a4bf1bfb1f/neutron/plugins/ml2/drivers/ovn/agent/neutron_agent.py#L85
stack@openstack:~$ openstack network agent show
d02fc630-4ac8-466f-9795-38e8177cfc55
+---+--+
| Field | Value
|
+---+--+
| admin_state_up| UP
|
| agent_type| OVN Controller Gateway agent
|
| alive | XXX
|
| availability_zone |
|
| binary| ovn-controller
|
| configuration | {'chassis_name': 'd02fc630-4ac8-466f-9795-38e8177cfc55',
'bridge-mappings': 'public:br-ex'}
|
| created_at| None
|
| description |
|
| ha_state | None
|
| host | openstack
|
| id| d02fc630-4ac8-466f-9795-38e8177cfc55
|
| last_heartbeat_at | 2022-06-04 01:59:27.926511
|
| location | Munch({'cloud': '', 'region_name': 'RegionOne', 'zone':
'', 'project': Munch({'id': '40e85036922248828c47cededb23036b', 'name':
'admin', 'domain_id': 'default', 'domain_name': None})}) |
| name | None
|
| resources_synced | None
|
| started_at| None
|
| topic | n/a
|
+---+--+
[Yahoo-eng-team] [Bug 1977524] Re: Wrong redirect after deleting zone from Zone Overview pane
** Also affects: horizon Importance: Undecided Status: New -- 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/1977524 Title: Wrong redirect after deleting zone from Zone Overview pane Status in Designate: New Status in OpenStack Dashboard (Horizon): New Bug description: When deleting zone from Zones -> specific zone -> Overview pane i am getting page not exist error. After successful notification that zone is being removed website redirects to /dashboard/dashboard/project/dnszones which has duplicate dashboard path. When deleting from zones list view everything works fine. Tested on Ussuri environment, but code seems to be unchanged in newer releases. I've tried to apply bugfixes for reloading zones/flating-ip panes but with no effect for this case To manage notifications about this bug go to: https://bugs.launchpad.net/designate/+bug/1977524/+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 1977490] Re: Tripleo Wallaby issue in template yaml generation
** Project changed: neutron => tripleo -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1977490 Title: Tripleo Wallaby issue in template yaml generation Status in tripleo: New Bug description: - High level description I am trying to install Tripleo Wallaby for which I have successfully installed the Undercloud Machine. For deploying the overcloud I have followed the below document https://docs.openstack.org/project-deploy-guide/tripleo- docs/latest/features/custom_networks.html#custom-networks Issue While running the Baremetal Provisioning Command: openstack overcloud node provision --stack overcloud --network- config --output overcloud-baremetal-deployed.yaml overcloud-baremetal- deploy.yaml Connectivity to the overcloud gets lost after sometime when ansible tries to apply the network config (with wrong syntax) and Overcloud nodes become unavailable. -- Sample Yaml overcloud-baremetal-deploy.yaml - name: Controller count: 3 defaults: networks: - network: ctlplane vif: true - network: external subnet: external_subnet - network: internal_api subnet: internal_api_subnet - network: j3mgmt subnet: j3mgmt_subnet - network: oc_provisioning subnet: oc_provisioning_subnet network_config: template: /usr/share/ansible/roles/tripleo_network_config/templates/bonds_vlans/bonds_vlans.j2 default_route_network: - external instances: - hostname: overcloud-controller-0 name: node-a #provisioned: false - hostname: overcloud-controller-1 name: node-b #provisioned: false - hostname: overcloud-controller-2 name: node-c #provisioned: false - name: Compute count: 1 defaults: networks: - network: ctlplane vif: true - network: internal_api subnet: internal_api_subnet - network: j3mgmt subnet: j3mgmt_subnet network_config: template: /usr/share/ansible/roles/tripleo_network_config/templates/bonds_vlans/bonds_vlans.j2 instances: - hostname: overcloud-novacompute-0 name: node-d #provisioned: false -- Expected output config.yaml should be generated correctly To manage notifications about this bug go to: https://bugs.launchpad.net/tripleo/+bug/1977490/+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 1977490] [NEW] Tripleo Wallaby issue in template yaml generation
Public bug reported: - High level description I am trying to install Tripleo Wallaby for which I have successfully installed the Undercloud Machine. For deploying the overcloud I have followed the below document https://docs.openstack.org/project-deploy-guide/tripleo- docs/latest/features/custom_networks.html#custom-networks Issue While running the Baremetal Provisioning Command: openstack overcloud node provision --stack overcloud --network-config --output overcloud-baremetal-deployed.yaml overcloud-baremetal- deploy.yaml Connectivity to the overcloud gets lost after sometime when ansible tries to apply the network config (with wrong syntax) and Overcloud nodes become unavailable. -- Sample Yaml overcloud-baremetal-deploy.yaml - name: Controller count: 3 defaults: networks: - network: ctlplane vif: true - network: external subnet: external_subnet - network: internal_api subnet: internal_api_subnet - network: j3mgmt subnet: j3mgmt_subnet - network: oc_provisioning subnet: oc_provisioning_subnet network_config: template: /usr/share/ansible/roles/tripleo_network_config/templates/bonds_vlans/bonds_vlans.j2 default_route_network: - external instances: - hostname: overcloud-controller-0 name: node-a #provisioned: false - hostname: overcloud-controller-1 name: node-b #provisioned: false - hostname: overcloud-controller-2 name: node-c #provisioned: false - name: Compute count: 1 defaults: networks: - network: ctlplane vif: true - network: internal_api subnet: internal_api_subnet - network: j3mgmt subnet: j3mgmt_subnet network_config: template: /usr/share/ansible/roles/tripleo_network_config/templates/bonds_vlans/bonds_vlans.j2 instances: - hostname: overcloud-novacompute-0 name: node-d #provisioned: false -- Expected output config.yaml should be generated correctly ** 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/1977490 Title: Tripleo Wallaby issue in template yaml generation Status in neutron: New Bug description: - High level description I am trying to install Tripleo Wallaby for which I have successfully installed the Undercloud Machine. For deploying the overcloud I have followed the below document https://docs.openstack.org/project-deploy-guide/tripleo- docs/latest/features/custom_networks.html#custom-networks Issue While running the Baremetal Provisioning Command: openstack overcloud node provision --stack overcloud --network- config --output overcloud-baremetal-deployed.yaml overcloud-baremetal- deploy.yaml Connectivity to the overcloud gets lost after sometime when ansible tries to apply the network config (with wrong syntax) and Overcloud nodes become unavailable. -- Sample Yaml overcloud-baremetal-deploy.yaml - name: Controller count: 3 defaults: networks: - network: ctlplane vif: true - network: external subnet: external_subnet - network: internal_api subnet: internal_api_subnet - network: j3mgmt subnet: j3mgmt_subnet - network: oc_provisioning subnet: oc_provisioning_subnet network_config: template: /usr/share/ansible/roles/tripleo_network_config/templates/bonds_vlans/bonds_vlans.j2 default_route_network: - external instances: - hostname: overcloud-controller-0 name: node-a #provisioned: false - hostname: overcloud-controller-1 name: node-b #provisioned: false - hostname: overcloud-controller-2 name: node-c #provisioned: false - name: Compute count: 1 defaults: networks: - network: ctlplane vif: true - network: internal_api subnet: internal_api_subnet - network: j3mgmt subnet: j3mgmt_subnet network_config: template: /usr/share/ansible/roles/tripleo_network_config/templates/bonds_vlans/bonds_vlans.j2 instances: - hostname: overcloud-novacompute-0 name: node-d #provisioned: false -- Expected output config.yaml should be generated correctly To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1977490/+subscriptions
