[all] Request to fix the warning to reduce the log size
Hello Everyone,
As you might have noticed the discussion in infra channel, log size are increasing a lot and one of the main reasons is warnings (especially repeatedly warnings). Few of them are from oslo policy on new policy and DeprecdatedRule. However, those are not the only warnings, there are lot from other lib also.
Before we start facing more issues in logging system and indexing, we would request all the project team to start looking at the logs and fix the warnings as much as possible.
I started fixing few of the oslo policy warning on DeprecatedRule in applicable projects and once all patches are merged, we can convert them to error from oslo side to avoid any future warnings-
https://review.opendev.org/q/topic:%22fix-oslo-policy-warnings%22+(status:op...)
[1] https://meetings.opendev.org/meetings/tc/2021/tc.2021-07-08-15.00.log.html#l...
-gmann
On Wed, Jul 14, 2021, at 1:47 PM, Ghanshyam Mann wrote:
Hello Everyone,
As you might have noticed the discussion in infra channel, log size are increasing a lot and one of the main reasons is warnings (especially repeatedly warnings). Few of them are from oslo policy on new policy and DeprecdatedRule. However, those are not the only warnings, there are lot from other lib also.
Before we start facing more issues in logging system and indexing, we would request all the project team to start looking at the logs and fix the warnings as much as possible.
I think it is important to note that it isn't just the CI system's log indexing that is affected by this. Operators in the real world are likely getting flooded by the warnings and those don't help them fix the code. It can also make it more difficult to determine the underlying causes of real issues if you have to sift through many warnings.
All that to say this is an improvement not just to the CI tooling but also likely to real deployments .
I started fixing few of the oslo policy warning on DeprecatedRule in applicable projects and once all patches are merged, we can convert them to error from oslo side to avoid any future warnings-
https://review.opendev.org/q/topic:%22fix-oslo-policy-warnings%22+(status:op...)
[1] https://meetings.opendev.org/meetings/tc/2021/tc.2021-07-08-15.00.log.html#l...
-gmann
On Wed, 2021-07-14 at 14:15 -0700, Clark Boylan wrote:
On Wed, Jul 14, 2021, at 1:47 PM, Ghanshyam Mann wrote:
Hello Everyone,
As you might have noticed the discussion in infra channel, log size are increasing a lot and one of the main reasons is warnings (especially repeatedly warnings). Few of them are from oslo policy on new policy and DeprecdatedRule. However, those are not the only warnings, there are lot from other lib also.
Before we start facing more issues in logging system and indexing, we would request all the project team to start looking at the logs and fix the warnings as much as possible.
I think it is important to note that it isn't just the CI system's log indexing that is affected by this. Operators in the real world are likely getting flooded by the warnings and those don't help them fix the code. It can also make it more difficult to determine the underlying causes of real issues if you have to sift through many warnings.
All that to say this is an improvement not just to the CI tooling but also likely to real deployments .
+1 i was going to say this would only affect real deployemnt after xena is released but actully looking at stable wallaby i guess 3.7.0 was included for wallaby https://github.com/openstack/requirements/blob/stable/wallaby/upper-constrai... so yes this is affecting all wallaby installs
victoria and older should not be impacted https://github.com/openstack/requirements/blob/stable/victoria/upper-constra...
so yes this is imporant not just for ci but for really installs.
I started fixing few of the oslo policy warning on DeprecatedRule in applicable projects and once all patches are merged, we can convert them to error from oslo side to avoid any future warnings-
https://review.opendev.org/q/topic:%22fix-oslo-policy-warnings%22+(status:op...)
[1] https://meetings.opendev.org/meetings/tc/2021/tc.2021-07-08-15.00.log.html#l...
-gmann
---- On Wed, 14 Jul 2021 16:23:43 -0500 Sean Mooney smooney@redhat.com wrote ----
On Wed, 2021-07-14 at 14:15 -0700, Clark Boylan wrote:
On Wed, Jul 14, 2021, at 1:47 PM, Ghanshyam Mann wrote:
Hello Everyone,
As you might have noticed the discussion in infra channel, log size are increasing a lot and one of the main reasons is warnings (especially repeatedly warnings). Few of them are from oslo policy on new policy and DeprecdatedRule. However, those are not the only warnings, there are lot from other lib also.
Before we start facing more issues in logging system and indexing, we would request all the project team to start looking at the logs and fix the warnings as much as possible.
I think it is important to note that it isn't just the CI system's log indexing that is affected by this. Operators in the real world are likely getting flooded by the warnings and those don't help them fix the code. It can also make it more difficult to determine the underlying causes of real issues if you have to sift through many warnings.
All that to say this is an improvement not just to the CI tooling but also likely to real deployments .
+1 i was going to say this would only affect real deployemnt after xena is released but actully looking at stable wallaby i guess 3.7.0 was included for wallaby https://github.com/openstack/requirements/blob/stable/wallaby/upper-constrai... so yes this is affecting all wallaby installs
Well, as DeprecatedRule warning fix need requirement bump so we will not be able to backport that even u-c is 3.7.0. But yes for Xena onwards it will be helpful for operator.
I have not checked all other warnings but many should be backport-able.
-gmann
victoria and older should not be impacted https://github.com/openstack/requirements/blob/stable/victoria/upper-constra...
so yes this is imporant not just for ci but for really installs.
I started fixing few of the oslo policy warning on DeprecatedRule in applicable projects and once all patches are merged, we can convert them to error from oslo side to avoid any future warnings-
https://review.opendev.org/q/topic:%22fix-oslo-policy-warnings%22+(status:op...)
[1] https://meetings.opendev.org/meetings/tc/2021/tc.2021-07-08-15.00.log.html#l...
-gmann
On Wed, Jul 14, 2021 at 15:47, Ghanshyam Mann gmann@ghanshyammann.com wrote:
Hello Everyone,
As you might have noticed the discussion in infra channel, log size are increasing a lot and one of the main reasons is warnings (especially repeatedly warnings). Few of them are from oslo policy on new policy and DeprecdatedRule. However, those are not the only warnings, there are lot from other lib also.
Before we start facing more issues in logging system and indexing, we would request all the project team to start looking at the logs and fix the warnings as much as possible.
The sqlAlchemy 1.4 version bump introduced a lot of repeated warning. It is fixed in oslo.db 10.0.0 but to be able to bump the global requirements[1] to that version first we need to fix Keystone[2].
Cheers, gibi
[1]https://review.opendev.org/c/openstack/requirements/+/799054 [2]https://review.opendev.org/q/topic:%22oslo.db-10.0.0%22+(status:open%20OR%20...)
I started fixing few of the oslo policy warning on DeprecatedRule in applicable projects and once all patches are merged, we can convert them to error from oslo side to avoid any future warnings-
https://review.opendev.org/q/topic:%22fix-oslo-policy-warnings%22+(status:op...)
[1] https://meetings.opendev.org/meetings/tc/2021/tc.2021-07-08-15.00.log.html#l...
-gmann
participants (4)
-
Balazs Gibizer
-
Clark Boylan
-
Ghanshyam Mann
-
Sean Mooney