sureshanaparti closed issue #8967: IP address conflicts held by public IPs of
virtual routers
URL: https://github.com/apache/cloudstack/issues/8967
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
sureshanaparti commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2197940877
Thanks @vdombrovski @hsato03. Fixed in #9234.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
hsato03 commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2163679437
@bragonznx @vdombrovski
We also discovered that the public IP can be duplicated when different VRs
have the same control IP. Could you check the database to see if there
hsato03 commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2163616158
Hello @bragonznx @vdombrovski
We reproduced the issue using the script you provided in this discussion and
also discovered that this situation also happens when creating a
weizhouapache commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2147175349
> @hsato03 are you working on this? I see you assigned but also an open PR
by @weizhouapache : #9059
@DaanHoogland
The issue I fixed in #9059 is not exactly the
DaanHoogland commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2147156671
@hsato03 are you working on this? I see you assigned but also an open PR by
@weizhouapache : #9059
--
This is an automated message from the Apache Git Service.
To respond
weizhouapache commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2110150962
thanks @vdombrovski
same as suspected, I think your issue is different as what I faced in my
testing (should be fixed by #9059).
--
This is an automated message from
vdombrovski commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2107149571
Hello @weizhouapache, sorry for the late reply.
I ran the script again to fetch your logs, I can confirm that:
1. These logs do sometimes appear when running the
weizhouapache commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2098790623
> @hsato03 and I were able to reproduce the situation and we are now
analyzing the workflows to fix it. We hope to open a PR shortly to share our
findings and tests
GutoVeronezi commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2098766181
Hello @bragonznx,
Thank you and @vdombrovski for reporting the situation and providing solid
and concrete information for us to reproduce the issue; and I am sorry
bragonznx commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2098464206
"Nobody is obligated to care about your issue. However, in open source,
there are individuals who are genuinely interested in helping you resolve it.
It's important to show
DaanHoogland commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2097583377
> What do you want to proof ?
@bragonznx , if you really want to provide "proof", it would need to be a
fix. This is open source and Wei is trying to figure it out ,
weizhouapache commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2096301615
> What do you want to proof ? **Because we have both got the issue of this
IP conflicts issue.** I can't spend my time digging in Exception/error, I have
too much of them.
bragonznx commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2096202224
What do you want to proof ?
**Because we have both got the issue of this IP conflicts issue.**
I can't spend my time digging in Exception/error, I have too much of them.
weizhouapache commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2096191093
> It's on management server where @vdombrovski did all the tests, so it
should be here
@bragonznx
it would be good to upload the management server logs.
if
bragonznx commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2096166693
It's on management server where @vdombrovski did all the tests, so it should
be here
--
This is an automated message from the Apache Git Service.
To respond to the
weizhouapache commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2096122002
>
> root@mgt-01:~# zegrep 'Failed to release.*Unable to revoke'
/var/log/cloudstack/management/management-server.log.*
>
> root@mgt-01:~#
>
@bragonznx
bragonznx commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2096057909
root@mgt-01:~# zegrep 'Failed to release.*Unable to revoke'
/var/log/cloudstack/management/management-server.log.*
root@mgt-01:~#
--
This is an automated message from
DaanHoogland commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2095950993
> zegrep 'Failed to release | Unable to revoke '
/var/log/cloudstack/management/management-server.log.*
is the pipe symbol within the single quotes a problem in this
weizhouapache commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2095851530
> root@mgt-01:~# zegrep 'Failed to release | Unable to revoke '
/var/log/cloudstack/management/management-server.log.*
>
> root@mgt-01:~#
>
> no matter the
bragonznx commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2095771744
root@mgt-01:~# zegrep 'Failed to release | Unable to revoke '
/var/log/cloudstack/management/management-server.log.*
root@mgt-01:~#
no matter the kind of grep you
weizhouapache commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2095753230
> zgrep 'Failed to release | Unable to revoke '
/var/log/cloudstack/management/management-server.log.*
@bragonznx
can you use `zegrep` instead ?
```
bragonznx commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2095742854
root@mgt-01:~# zgrep 'Failed to release | Unable to revoke '
/var/log/cloudstack/management/management-server.log.*
root@mgt-01:~# egrep 'Failed to release | Unable to revoke
weizhouapache commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2092742040
@vdombrovski @bragonznx
after some hours, I am able to reproduce the issue twice
it looks like the issue is caused by concurrent actions
- disassociate IP
bragonznx commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2090468604
We haven't any java development capability : we only have Python developer
in our company.
But I'm open to any proposal to fix this very annoying issue.
--
This is an
bragonznx commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2090438875
@rohityadavcloud do you have any fix of this in the changelog from 4.18 or
4.19 ?
Because if it's not the case, I don't see the point you mentioned at all
We will
vdombrovski commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2090422500
@weizhouapache because it's a timing issue, you need to make sure that both
scripts run with a delay, otherwise you are getting a favorable case where both
operations target
weizhouapache commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2090350202
> @DaanHoogland here is how I successfully reproduced the issue on our QA
platform:
>
> ```
> 56 bytes from 1e:00:4d:00:00:c1 (XX.YY.17.30): index=959 time=275.810
rohityadavcloud commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2089949459
@vdombrovski @bragonznx have you tried to reproduce this issue against
CloudStack 4.18.2.0 or 4.19.0.1 ?
Anyone is welcome to propose a fix.
--
This is an automated
rohityadavcloud commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2089946691
cc @weizhouapache @sureshanaparti to triage
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
bragonznx commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2089917165
Hello
Do we have any news on this ?
I believe it's too important breaking production, to wait for a sponsor to
cover this patch
Best regards
--
This is
vdombrovski commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2079829634
@DaanHoogland yes correct, released after I wrote my comment, which means we
will surely plan our tests now.
As for proof inside the DB, I've ran more tests, and I can
DaanHoogland commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2077094467
> We are currently waiting for the 4.18.2.0 to be released as our next
upgrade candidate.
it has been released ;)
As for how to prevent it, I have no ready
vdombrovski commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2076886241
@DaanHoogland as I said, this doesn't seem to be a priority at the current
time, even though it might be one of the main pillars of the project. I'm not
judging here, I'm
DaanHoogland commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2076518899
Don't be putting the project down like that, concurrency is one of the main
pillars of the project. We have not always been too good at it (as a project),
admitted. Manpower
bragonznx commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2075401415
Hi
We need that to be fix, how can we help ?
Best
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
vdombrovski commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2075380164
@DaanHoogland here is how I successfully reproduced the issue on our QA
platform:
```
56 bytes from 1e:00:4d:00:00:c1 (XX.YY.17.30): index=959 time=275.810 usec
weizhouapache commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2075229433
did a quick test, everything looks good
this may need intensive testing to reproduce the issue
--
This is an automated message from the Apache Git Service.
To respond
DaanHoogland commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2075009281
oh, that,
```
2024-04-23 13:11:27,089 WARNING Unable to find and process databag for
file: ip_associations.json.a81b47b8-2a91-42a2-a529-1de42849049c, for json
vdombrovski commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2074922796
@DaanHoogland not sure if this helps, in /var/log/cloud.log I'm getting the
same log repeated for all IPs:
```
2024-04-04 04:43:29,474 INFO Add: rule=-I
DaanHoogland commented on issue #8967:
URL: https://github.com/apache/cloudstack/issues/8967#issuecomment-2074616301
thanks @vdombrovski , this will (obviously) be hard to reproduce in a lab
environment. the true/false flag of the databag should ensure that IPs are
removed, so it not being
vdombrovski opened a new issue, #8967:
URL: https://github.com/apache/cloudstack/issues/8967
# ISSUE TYPE
* Bug Report
# COMPONENT NAME
~~~
VR
~~~
# CLOUDSTACK VERSION
~~~
4.17.2
~~~
Note: I believe this impacts
42 matches
Mail list logo
