Problem that Bamboo Hook Call appends 0:0:0:0:0:0:0:1 to any IP

[Andre Sturm]

I want to configure Bamboo to build a plan when it is triggered by a hook, configured in Stash. Bamboo and Stash are installed on the same server and I trigger the correct plan using http://bamboo.XXX.de/api/rest/updateAndBuild.action?buildKey=XXX-XXX.

But even if i use curl to call the url on the same host, I always get the message:

Build request for Dummy - Dummy Plan; originated from X.X.X.X,0:0:0:0:0:0:0:1 which is not an allowed address (one of[, X.X.X.X]). 

X.X.X.X is in both cases the same IP. The IPv4 IP of my Bamboo and Stash Server.

I tried to enter my v4 Adress in the Trigger IP field in the Bamboo Hooks Panel for my home IP, my work IP and the server itself but the result is always the same -> ,0:0:0:0:0:0:0:1 is added to the IP Address.

Unfortunately I cannot even enter X.X.X.X,0:0:0:0:0:0:0:1 in the Trigger IP field since it is not accepted due to the fact that I can enter a list of comma separated IPs and X.X.X.X and 0:0:0:0:0:0:0:1 are handled as separated IPs so that the last one is not valid.

How can I solve the problem? I use bamboo version 5.8.1 build 5866 

Thank you for your answer.

[rrudnicki]

Hi, 

I agree with Jeff that disabling ipv6 isn't the ideal, but is a workaround. 

Just add the following lines on the /etc/sysctl.conf to disable the ipv6 and restart the Linux.

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
net.ipv6.conf.eth0.disable_ipv6 = 1

Regards, 

Renato Rudnicki

[Andre Sturm]

Hello Rafael,

this is a pity because it is very important for me since there is no workaround or do you have any idea?

I will upvote the issue and really hope that this is fixed very soon since we really need this for all toolchains. If someone has further ideas how to solve the problem I look forward.

Thank you very much for your fast help.

Stefan

[Jeff Thomas]

While not ideal, I've worked around this issue recently by disabling IPv6 on the Bamboo server.

[rsperafico]

Hello Stefan,

Thank you for the information provided.

We've investigated this issue further and we suspect you might be experiencing this bug:

• Bamboo repository IP field does not allow to enter IPv6 addresses

If you also agree, I would suggest adding any comments to the issue above as well as voting on the issue to create it's popularity and likelihood of being fixed in a future release.

Please see the document below for more information on Atlassian's bug fixing policy.

If you find this answer useful, I would kindly ask you to accept it so the same will be visible to others who might be facing the same issue you have inquired.

Thank you for your understanding.

—

Kind regards,
Rafael P. Sperafico
Atlassian Support

[Andre Sturm]

Hi Rafael,

thank you for your answer.

I added 127.0.0.1,85.214.x.x to the trigger ip addresses field and used 

curl http://bamboo.xxx.de/api/rest/updateAndBuild.action?buildKey=JMD-JMDP to trigger my build.

The resulting message is:

<errors>

        <error>Build request for plan &quot;JMB Dummy - JMB Dummy Plan&quot; originated from 85.214.x.x,0:0:0:0:0:0:0:1 which is not an allowed address (one of[, 85.214.x.x, 127.0.0.1]).</error>

Unfortunately the problem seems not to be solved. I think there is probably a problem with the script when it comes to ipv6 addresses. But it makes no sense why it is not enough to check the v4 address.

Do you have any further ideas?

Best wishes

Stefan

[rsperafico]

Hello Stefan,

Thank you for your question.

Could you please add the following in the "Trigger IP addresses" field under "Plan configuration >> Triggers" tab:

# [internal-ip-address], i.e.: 192.168.0.11
127.0.0.1,[internal-ip-address]
 
# as a result, you would have:
127.0.0.1,192.168.0.11

After that, please attempt on running the same cURL command and/or trigger a hook.

If you find this answer useful, I would kindly ask you to accept it so the same will be visible to others who might be facing the same issue you have inquired.

Thank you for your understanding.

—

Kind regards,
Rafael P. Sperafico
Atlassian Support