1324799 - can't set priority to 0 for new rules

Status: RESOLVED FIXED

(Release Engineering Graveyard :: Applications: Balrog (backend), defect, P3)

Description

[[e-mail] (:bhearsum)]

Pretty much the same bug as we had for background rate in bug 1282841, but for the priority field.

Tomislav fixed that already, and volunteered to look at this, too.

Comment 1

[Tomislav Jurin]

Hi Ben just wanted to let you know that I didn't have time because of personal reasons to look at this. I am starting today so expect it soon. Best luck.

Comment 2

[Tomislav Jurin]

Hi bhearsum, do you maybe have idea why do I get this error when trying to open rules:

API Proxying to `/api/rules` failed with: `Error: connect EHOSTUNREACH`


I can normally open home page, but can't view any rules. Doing the same things I did on last bug so I am bit confused why is this happening.

Comment 3

[[e-mail] (:bhearsum)]

(In reply to Tomislav Jurin from comment #2)
> Hi bhearsum, do you maybe have idea why do I get this error when trying to
> open rules:
> 
> API Proxying to `/api/rules` failed with: `Error: connect EHOSTUNREACH`
> 
> 
> I can normally open home page, but can't view any rules. Doing the same
> things I did on last bug so I am bit confused why is this happening.

It could be that one of your containers failed to start, but it's hard to say anything definitive without seeing the full output from docker-compose.

Comment 4

[Tomislav Jurin]

The whole log seems to be too big for mozilla pastebin. I think error could be along these lines:

https://pastebin.mozilla.org/8958253

Comment 5

[Tomislav Jurin]

Hi bhearsum, unfortunately magic didn't work,I still ahve the same problem with rules.

this is the log from docker-compose up
https://gist.github.com/gilleycro/784c696214159131fc2e312d483d7a21

I am just leaving it here so I don't forget it tomorrow,will catch you on IRC.

Thanks

Comment 6

[Tomislav Jurin]

I have tried to set this up on multiple laptops without luck, always the same error. Sorry bhearsum I don't think I will be able to fix this one. 

If anyone is interested in working on this feel free to take it.

Sorry once again.

Comment 7

[[e-mail] (:bhearsum)]

(In reply to Tomislav Jurin from comment #6)
> I have tried to set this up on multiple laptops without luck, always the
> same error. Sorry bhearsum I don't think I will be able to fix this one. 
> 
> If anyone is interested in working on this feel free to take it.
> 
> Sorry once again.

Sorry to hear that, but no worries. Thanks for your efforts anyways.

Comment 8

[A.S.]

I'll have a look at it.

Comment 9

[A.S.]

This change has already been deployed . Should I change the status of this bug ?

Comment 10

[[e-mail] (:bhearsum)]

(In reply to Ashish Sareen from comment #9)
> This change has already been deployed . Should I change the status of this
> bug ?

Yes, please! I'm not sure how this was overlooked.