yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #91387
[Bug 2008257] [NEW] OVN agent heartbeat timestamp format changed unexpectedly
Public bug reported:
Following an upgrade from Wallaby to Yoga of a Neutron OVN deployment, I
discovered that openstack-exporter would fail to return metrics for
Neutron agent states with the following error:
time="2023-02-23T10:49:33Z" level=error msg="Failed to collect metric
for exporter: neutron, error: failed to collect metric: agent_state,
error: parsing time \"2023-02-23 10:48:55.729000+00:00\": extra text:
\"+00:00\"" source="exporter.go:123"
I tracked it down to the following change which has also been backported
to stable/branches (so a recent Wallaby would also be affected):
https://review.opendev.org/c/openstack/neutron/+/844179
With this change, heartbeat timestamp includes timezone when previously
it didn't, causing clients such as the gophercloud library (which
openstack-exporter uses) to fail parsing of the response.
** 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/2008257
Title:
OVN agent heartbeat timestamp format changed unexpectedly
Status in neutron:
New
Bug description:
Following an upgrade from Wallaby to Yoga of a Neutron OVN deployment,
I discovered that openstack-exporter would fail to return metrics for
Neutron agent states with the following error:
time="2023-02-23T10:49:33Z" level=error msg="Failed to collect metric
for exporter: neutron, error: failed to collect metric: agent_state,
error: parsing time \"2023-02-23 10:48:55.729000+00:00\": extra text:
\"+00:00\"" source="exporter.go:123"
I tracked it down to the following change which has also been
backported to stable/branches (so a recent Wallaby would also be
affected): https://review.opendev.org/c/openstack/neutron/+/844179
With this change, heartbeat timestamp includes timezone when
previously it didn't, causing clients such as the gophercloud library
(which openstack-exporter uses) to fail parsing of the response.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2008257/+subscriptions
Follow ups