[HELP-57] FIWARE.Request.Lab.Spain.MD-VPN issues at FI-LAB 10.0.3.45/21 - JIRA

Details

Type: extRequest
Status: Closed
Priority: Major
Resolution: Done
Fix Version/s: Sprint 4.1.1
Component/s: FIWARE-LAB-HELP
Labels:
None

HD-Node:
Spain

Description

Hi,
I created a testing VM in the FI-LAB region. The VM got assigned a private
IPv4 address of 10.0.3.45, and I also added a floating IP 130.206.83.11. I
can access the public IPv4 just fine, but it seems that the private,
XIFI-federated IPv4 range is having some troubles.

Here's how a tracepath looks from one of our nodes at CESNET:

[root@potemkin02 ~]# tracepath 10.0.3.45

1: 10.0.96.132 (10.0.96.132) 0.138ms pmtu
9100

1: no reply

2: 62.40.124.41 (62.40.124.41) 1.049ms

3: 62.40.124.41 (62.40.124.41) 0.983ms pmtu
1488

3: no reply

4: ae2.mx1.fra.de.geant.net (62.40.98.53) 34.677ms asymm
17

5: ae1.mx1.ams.nl.geant.net (62.40.98.129) 34.591ms asymm
16

6: ae2.mx1.lon.uk.geant.net (62.40.98.80) 34.565ms asymm
15

7: ae7.mx1.dub.ie.geant.net (62.40.98.92) 34.530ms asymm
14

8: ae1.mx2.dub.ie.geant.net (62.40.98.91) 34.546ms asymm
13

9: 62.40.102.15 (62.40.102.15) 34.323ms asymm
11

10: 10.0.0.1 (10.0.0.1) 34.403ms

11: no reply

12: no reply

13: no reply

14: no reply

15: no reply

16: no reply

17: no reply

18: no reply

19: no reply

20: no reply

21: no reply

22: no reply

23: no reply

24: no reply

25: no reply

26: no reply

27: no reply

In contrast, this is how a testing tracepath looks from the VM I launched:

[root@test-el6-1 ~]# traceroute 10.0.96.1
traceroute to 10.0.96.1 (10.0.96.1), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 20.300 ms 20.272 ms 20.243 ms
2 130.206.82.1 (130.206.82.1) 29.885 ms 29.851 ms 29.832 ms
3 130.206.82.1 (130.206.82.1) 2936.241 ms !H 2936.227 ms !H 2936.205
ms !H

Could you please confirm that this is expected to work? Unfortunately, the
information about the allocation and utilization of the XIFI-wide federated
IPv4 space is rather scarce in varioud public deliverables. It's well
possible that this use case is not supposed to work at all. Could you
please clarify that?

With kind regards,
Jan

–
Trojitá, a fast Qt IMAP e-mail client – http://trojita.flaska.net/
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help

Activity

Ascending order - Click to sort in descending order

FIWARE-LAB-HELP created issue - 24/Sep/14 2:33 PM

Hide

Permalink

FIWARE-LAB-HELP added a comment - 24/Sep/14 2:33 PM

Hi,

It seems that somewhere in the european Backbone (62.40.102.15) didn't
find FI-LAB's 10.0.0.1

Best regards,
José Ignacio.

El 19/05/14 12:03, Jan Kundrát escribió:
> Hi,
> I created a testing VM in the FI-LAB region. The VM got assigned a
> private IPv4 address of 10.0.3.45, and I also added a floating IP
> 130.206.83.11. I can access the public IPv4 just fine, but it seems
> that the private, XIFI-federated IPv4 range is having some troubles.
>
> Here's how a tracepath looks from one of our nodes at CESNET:
>
> [root@potemkin02 ~]# tracepath 10.0.3.45 1:
> 10.0.96.132 (10.0.96.132) 0.138ms pmtu
> 9100 1: no reply
> 2: 62.40.124.41 (62.40.124.41) 1.049ms
> 3: 62.40.124.41
> (62.40.124.41) 0.983ms pmtu 1488
> 3: no reply 4:
> ae2.mx1.fra.de.geant.net (62.40.98.53) 34.677ms asymm
> 17 5: ae1.mx1.ams.nl.geant.net
> (62.40.98.129) 34.591ms asymm 16
> 6: ae2.mx1.lon.uk.geant.net
> (62.40.98.80) 34.565ms asymm 15
> 7: ae7.mx1.dub.ie.geant.net
> (62.40.98.92) 34.530ms asymm 14
> 8: ae1.mx2.dub.ie.geant.net
> (62.40.98.91) 34.546ms asymm 13
> 9: 62.40.102.15
> (62.40.102.15) 34.323ms asymm 11
> 10: 10.0.0.1
> (10.0.0.1) 34.403ms
> 11: no reply 12:
> no reply 13: no reply
> 14: no reply 15:
> no reply 16: no reply
> 17: no reply 18:
> no reply 19: no reply
> 20: no reply 21:
> no reply 22: no reply
> 23: no reply 24:
> no reply 25: no reply
> 26: no reply 27:
> no reply
>
> In contrast, this is how a testing tracepath looks from the VM I
> launched:
>
> [root@test-el6-1 ~]# traceroute 10.0.96.1
> traceroute to 10.0.96.1 (10.0.96.1), 30 hops max, 60 byte packets
> 1 10.0.0.1 (10.0.0.1) 20.300 ms 20.272 ms 20.243 ms
> 2 130.206.82.1 (130.206.82.1) 29.885 ms 29.851 ms 29.832 ms
> 3 130.206.82.1 (130.206.82.1) 2936.241 ms !H 2936.227 ms !H
> 2936.205 ms !H
>
> Could you please confirm that this is expected to work? Unfortunately,
> the information about the allocation and utilization of the XIFI-wide
> federated IPv4 space is rather scarce in varioud public deliverables.
> It's well possible that this use case is not supposed to work at all.
> Could you please clarify that?
>
> With kind regards,
> Jan
>

________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help

Show

FIWARE-LAB-HELP added a comment - 24/Sep/14 2:33 PM Hi, It seems that somewhere in the european Backbone (62.40.102.15) didn't find FI-LAB's 10.0.0.1 Best regards, José Ignacio. El 19/05/14 12:03, Jan Kundrát escribió: > Hi, > I created a testing VM in the FI-LAB region. The VM got assigned a > private IPv4 address of 10.0.3.45, and I also added a floating IP > 130.206.83.11. I can access the public IPv4 just fine, but it seems > that the private, XIFI-federated IPv4 range is having some troubles. > > Here's how a tracepath looks from one of our nodes at CESNET: > > [root@potemkin02 ~] # tracepath 10.0.3.45 1: > 10.0.96.132 (10.0.96.132) 0.138ms pmtu > 9100 1: no reply > 2: 62.40.124.41 (62.40.124.41) 1.049ms > 3: 62.40.124.41 > (62.40.124.41) 0.983ms pmtu 1488 > 3: no reply 4: > ae2.mx1.fra.de.geant.net (62.40.98.53) 34.677ms asymm > 17 5: ae1.mx1.ams.nl.geant.net > (62.40.98.129) 34.591ms asymm 16 > 6: ae2.mx1.lon.uk.geant.net > (62.40.98.80) 34.565ms asymm 15 > 7: ae7.mx1.dub.ie.geant.net > (62.40.98.92) 34.530ms asymm 14 > 8: ae1.mx2.dub.ie.geant.net > (62.40.98.91) 34.546ms asymm 13 > 9: 62.40.102.15 > (62.40.102.15) 34.323ms asymm 11 > 10: 10.0.0.1 > (10.0.0.1) 34.403ms > 11: no reply 12: > no reply 13: no reply > 14: no reply 15: > no reply 16: no reply > 17: no reply 18: > no reply 19: no reply > 20: no reply 21: > no reply 22: no reply > 23: no reply 24: > no reply 25: no reply > 26: no reply 27: > no reply > > In contrast, this is how a testing tracepath looks from the VM I > launched: > > [root@test-el6-1 ~] # traceroute 10.0.96.1 > traceroute to 10.0.96.1 (10.0.96.1), 30 hops max, 60 byte packets > 1 10.0.0.1 (10.0.0.1) 20.300 ms 20.272 ms 20.243 ms > 2 130.206.82.1 (130.206.82.1) 29.885 ms 29.851 ms 29.832 ms > 3 130.206.82.1 (130.206.82.1) 2936.241 ms !H 2936.227 ms !H > 2936.205 ms !H > > Could you please confirm that this is expected to work? Unfortunately, > the information about the allocation and utilization of the XIFI-wide > federated IPv4 space is rather scarce in varioud public deliverables. > It's well possible that this use case is not supposed to work at all. > Could you please clarify that? > > With kind regards, > Jan > ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help

Hide

Permalink

FIWARE-LAB-HELP added a comment - 24/Sep/14 2:33 PM

On Monday, 19 May 2014 12:32:37 CEST, José Ignacio Carretero Guarde wrote:
> It seems that somewhere in the european Backbone (62.40.102.15) didn't
> find FI-LAB's 10.0.0.1

I don't think that the problem is in the GEANT's infrastructure because the
CESNET node can reach 10.0.0.1 just fine:

[root@potemkin02 ~]# tracepath 10.0.0.1
1: 10.0.96.132 (10.0.96.132) 0.102ms pmtu
9100
1: no reply
2: 62.40.124.41 (62.40.124.41) 1.117ms
3: 62.40.124.41 (62.40.124.41) 0.951ms pmtu
1488
3: no reply
4: ae2.mx1.fra.de.geant.net (62.40.98.53) 34.688ms asymm
17
5: ae1.mx1.ams.nl.geant.net (62.40.98.129) 35.294ms asymm
16
6: ae2.mx1.lon.uk.geant.net (62.40.98.80) 34.594ms asymm
15
7: ae7.mx1.dub.ie.geant.net (62.40.98.92) 35.314ms asymm
14
8: ae1.mx2.dub.ie.geant.net (62.40.98.91) 34.577ms asymm
13
9: 62.40.102.15 (62.40.102.15) 34.417ms asymm
11
10: 10.0.0.1 (10.0.0.1) 34.288ms reached
Resume: pmtu 1488 hops 10 back 246

In fact, 10.0.0.1 is visible within the trace towards 10.0.3.45 – see hop
#10:

[root@potemkin02 ~]# tracepath 10.0.3.45
1: 10.0.96.132 (10.0.96.132) 0.142ms pmtu
9100
1: no reply
2: 62.40.124.41 (62.40.124.41) 1.060ms
3: 62.40.124.41 (62.40.124.41) 1.006ms pmtu
1488
3: no reply
4: ae2.mx1.fra.de.geant.net (62.40.98.53) 34.700ms asymm
17
5: ae1.mx1.ams.nl.geant.net (62.40.98.129) 34.593ms asymm
16
6: ae2.mx1.lon.uk.geant.net (62.40.98.80) 34.572ms asymm
15
7: ae7.mx1.dub.ie.geant.net (62.40.98.92) 34.771ms asymm
14
8: ae1.mx2.dub.ie.geant.net (62.40.98.91) 34.544ms asymm
13
9: 62.40.102.15 (62.40.102.15) 34.359ms asymm
11
10: 10.0.0.1 (10.0.0.1) 34.424ms
11: no reply

Despite that, I cannot ping 10.0.3.45 from 10.0.96.132. I can ping
10.0.0.1, though.

With kind regards,
Jan

Show

FIWARE-LAB-HELP added a comment - 24/Sep/14 2:33 PM On Monday, 19 May 2014 12:32:37 CEST, José Ignacio Carretero Guarde wrote: > It seems that somewhere in the european Backbone (62.40.102.15) didn't > find FI-LAB's 10.0.0.1 I don't think that the problem is in the GEANT's infrastructure because the CESNET node can reach 10.0.0.1 just fine: [root@potemkin02 ~] # tracepath 10.0.0.1 1: 10.0.96.132 (10.0.96.132) 0.102ms pmtu 9100 1: no reply 2: 62.40.124.41 (62.40.124.41) 1.117ms 3: 62.40.124.41 (62.40.124.41) 0.951ms pmtu 1488 3: no reply 4: ae2.mx1.fra.de.geant.net (62.40.98.53) 34.688ms asymm 17 5: ae1.mx1.ams.nl.geant.net (62.40.98.129) 35.294ms asymm 16 6: ae2.mx1.lon.uk.geant.net (62.40.98.80) 34.594ms asymm 15 7: ae7.mx1.dub.ie.geant.net (62.40.98.92) 35.314ms asymm 14 8: ae1.mx2.dub.ie.geant.net (62.40.98.91) 34.577ms asymm 13 9: 62.40.102.15 (62.40.102.15) 34.417ms asymm 11 10: 10.0.0.1 (10.0.0.1) 34.288ms reached Resume: pmtu 1488 hops 10 back 246 In fact, 10.0.0.1 is visible within the trace towards 10.0.3.45 – see hop #10: [root@potemkin02 ~] # tracepath 10.0.3.45 1: 10.0.96.132 (10.0.96.132) 0.142ms pmtu 9100 1: no reply 2: 62.40.124.41 (62.40.124.41) 1.060ms 3: 62.40.124.41 (62.40.124.41) 1.006ms pmtu 1488 3: no reply 4: ae2.mx1.fra.de.geant.net (62.40.98.53) 34.700ms asymm 17 5: ae1.mx1.ams.nl.geant.net (62.40.98.129) 34.593ms asymm 16 6: ae2.mx1.lon.uk.geant.net (62.40.98.80) 34.572ms asymm 15 7: ae7.mx1.dub.ie.geant.net (62.40.98.92) 34.771ms asymm 14 8: ae1.mx2.dub.ie.geant.net (62.40.98.91) 34.544ms asymm 13 9: 62.40.102.15 (62.40.102.15) 34.359ms asymm 11 10: 10.0.0.1 (10.0.0.1) 34.424ms 11: no reply Despite that, I cannot ping 10.0.3.45 from 10.0.96.132. I can ping 10.0.0.1, though. With kind regards, Jan – Trojitá, a fast Qt IMAP e-mail client – http://trojita.flaska.net/ _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help

Hide

Permalink

FIWARE-LAB-HELP added a comment - 24/Sep/14 2:33 PM

I don't think that "ping" is a reliable tool in this case, anyway. —
Yes, I can admit you can ping a 10.0.0.1 from your IP, but FI-LAB's
10.0.0.1 doesn't respond to ping from 10.0.0.0/8 – In fact, it drops
those packages.

BR,
José Ignacio.

El 19/05/14 12:39, Jan Kundrát escribió:
> On Monday, 19 May 2014 12:32:37 CEST, José Ignacio Carretero Guarde
> wrote:
>> It seems that somewhere in the european Backbone (62.40.102.15) didn't
>> find FI-LAB's 10.0.0.1
>
> I don't think that the problem is in the GEANT's infrastructure
> because the CESNET node can reach 10.0.0.1 just fine:
>
> [root@potemkin02 ~]# tracepath 10.0.0.1
> 1: 10.0.96.132 (10.0.96.132) 0.102ms
> pmtu 9100
> 1: no reply
> 2: 62.40.124.41 (62.40.124.41) 1.117ms 3:
> 62.40.124.41 (62.40.124.41) 0.951ms pmtu 1488
> 3: no reply
> 4: ae2.mx1.fra.de.geant.net (62.40.98.53) 34.688ms
> asymm 17 5: ae1.mx1.ams.nl.geant.net (62.40.98.129) 35.294ms asymm 16
> 6: ae2.mx1.lon.uk.geant.net (62.40.98.80) 34.594ms
> asymm 15 7: ae7.mx1.dub.ie.geant.net (62.40.98.92)
> 35.314ms asymm 14 8: ae1.mx2.dub.ie.geant.net (62.40.98.91) 34.577ms
> asymm 13 9: 62.40.102.15 (62.40.102.15)
> 34.417ms asymm 11 10: 10.0.0.1
> (10.0.0.1) 34.288ms reached
> Resume: pmtu 1488 hops 10 back 246
>
> In fact, 10.0.0.1 is visible within the trace towards 10.0.3.45 – see
> hop #10:
>
> [root@potemkin02 ~]# tracepath 10.0.3.45
> 1: 10.0.96.132 (10.0.96.132) 0.142ms
> pmtu 9100
> 1: no reply
> 2: 62.40.124.41 (62.40.124.41) 1.060ms 3:
> 62.40.124.41 (62.40.124.41) 1.006ms pmtu 1488
> 3: no reply
> 4: ae2.mx1.fra.de.geant.net (62.40.98.53) 34.700ms
> asymm 17 5: ae1.mx1.ams.nl.geant.net (62.40.98.129) 34.593ms asymm 16
> 6: ae2.mx1.lon.uk.geant.net (62.40.98.80) 34.572ms
> asymm 15 7: ae7.mx1.dub.ie.geant.net (62.40.98.92)
> 34.771ms asymm 14 8: ae1.mx2.dub.ie.geant.net (62.40.98.91) 34.544ms
> asymm 13 9: 62.40.102.15 (62.40.102.15)
> 34.359ms asymm 11 10: 10.0.0.1
> (10.0.0.1) 34.424ms 11: no reply
>
> Despite that, I cannot ping 10.0.3.45 from 10.0.96.132. I can ping
> 10.0.0.1, though.
>
> With kind regards,
> Jan
>

________________________________

Show

FIWARE-LAB-HELP added a comment - 24/Sep/14 2:33 PM I don't think that "ping" is a reliable tool in this case, anyway. — Yes, I can admit you can ping a 10.0.0.1 from your IP, but FI-LAB's 10.0.0.1 doesn't respond to ping from 10.0.0.0/8 – In fact, it drops those packages. BR, José Ignacio. El 19/05/14 12:39, Jan Kundrát escribió: > On Monday, 19 May 2014 12:32:37 CEST, José Ignacio Carretero Guarde > wrote: >> It seems that somewhere in the european Backbone (62.40.102.15) didn't >> find FI-LAB's 10.0.0.1 > > I don't think that the problem is in the GEANT's infrastructure > because the CESNET node can reach 10.0.0.1 just fine: > > [root@potemkin02 ~] # tracepath 10.0.0.1 > 1: 10.0.96.132 (10.0.96.132) 0.102ms > pmtu 9100 > 1: no reply > 2: 62.40.124.41 (62.40.124.41) 1.117ms 3: > 62.40.124.41 (62.40.124.41) 0.951ms pmtu 1488 > 3: no reply > 4: ae2.mx1.fra.de.geant.net (62.40.98.53) 34.688ms > asymm 17 5: ae1.mx1.ams.nl.geant.net (62.40.98.129) 35.294ms asymm 16 > 6: ae2.mx1.lon.uk.geant.net (62.40.98.80) 34.594ms > asymm 15 7: ae7.mx1.dub.ie.geant.net (62.40.98.92) > 35.314ms asymm 14 8: ae1.mx2.dub.ie.geant.net (62.40.98.91) 34.577ms > asymm 13 9: 62.40.102.15 (62.40.102.15) > 34.417ms asymm 11 10: 10.0.0.1 > (10.0.0.1) 34.288ms reached > Resume: pmtu 1488 hops 10 back 246 > > In fact, 10.0.0.1 is visible within the trace towards 10.0.3.45 – see > hop #10: > > [root@potemkin02 ~] # tracepath 10.0.3.45 > 1: 10.0.96.132 (10.0.96.132) 0.142ms > pmtu 9100 > 1: no reply > 2: 62.40.124.41 (62.40.124.41) 1.060ms 3: > 62.40.124.41 (62.40.124.41) 1.006ms pmtu 1488 > 3: no reply > 4: ae2.mx1.fra.de.geant.net (62.40.98.53) 34.700ms > asymm 17 5: ae1.mx1.ams.nl.geant.net (62.40.98.129) 34.593ms asymm 16 > 6: ae2.mx1.lon.uk.geant.net (62.40.98.80) 34.572ms > asymm 15 7: ae7.mx1.dub.ie.geant.net (62.40.98.92) > 34.771ms asymm 14 8: ae1.mx2.dub.ie.geant.net (62.40.98.91) 34.544ms > asymm 13 9: 62.40.102.15 (62.40.102.15) > 34.359ms asymm 11 10: 10.0.0.1 > (10.0.0.1) 34.424ms 11: no reply > > Despite that, I cannot ping 10.0.3.45 from 10.0.96.132. I can ping > 10.0.0.1, though. > > With kind regards, > Jan > ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help

Manuel Escriche made changes - 30/Sep/14 6:39 PM

Field	Original Value	New Value
Assignee	Manuel Escriche [Administrator] [ mev ]	José Ignacio Carretero Guarde [ jicg ]

Manuel Escriche made changes - 03/Oct/14 8:52 AM

Resolution		Done [ 10000 ]
Status	To Do [ 10001 ]	Done [ 10000 ]

Manuel Escriche made changes - 22/Oct/14 3:32 PM

Component/s

FIWARE-LAB-HELP [ 10279 ]

Manuel Escriche made changes - 22/Oct/14 4:01 PM

Workflow	Basic Workflow [ 12415 ]	FW eRequest Workflow [ 16158 ]
Issue Type	Question [ 10004 ]	eRequest [ 10101 ]
FI-WARE Environment	FI-LAB [ 10100 ]
Resolution	Done [ 10000 ]

Manuel Escriche made changes - 22/Oct/14 4:53 PM

Resolution

Done [ 10000 ]

Manuel Escriche made changes - 22/Oct/14 10:14 PM

Workflow

FW eRequest Workflow [ 16158 ]

eRequest Workflow-2 [ 16732 ]

Manuel Escriche made changes - 22/Oct/14 10:29 PM

Status

Done [ 10000 ]

In Progress [ 3 ]

Manuel Escriche made changes - 22/Oct/14 10:31 PM

Status

In Progress [ 3 ]

Done [ 10000 ]

Manuel Escriche made changes - 22/Oct/14 10:33 PM

Workflow

eRequest Workflow-2 [ 16732 ]

FW eRequest Workflow [ 17111 ]

Manuel Escriche made changes - 02/Nov/14 4:43 PM

Fix Version/s

Sprint 4.1.1 [ 10737 ]

Manuel Escriche made changes - 02/Nov/14 4:49 PM

Reporter

FIWARE-LAB-HELP [ fiware-lab-help ]

FW External User [ fw.external.urser ]

Manuel Escriche made changes - 12/Jan/16 9:10 AM

Workflow	FW eRequest Workflow [ 17111 ]	FW extRequest Workflow-II [ 41159 ]
Status	Done [ 10000 ]	Closed [ 6 ]
Issue Type	eRequest [ 10101 ]	extRequest [ 10104 ]

Manuel Escriche made changes - 12/Apr/16 3:52 PM

HD-Node

Spain [ 10846 ]

Backlog Manager made changes - 12/Apr/16 3:54 PM

Summary

[Fiware-lab-help] MD-VPN issues at FI-LAB 10.0.3.45/21

FIWARE.Request.Lab.Spain.MD-VPN issues at FI-LAB 10.0.3.45/21

Transition

Time In Source Status

Execution Times

Last Executer

Last Execution Date

To Do

Done

8d 18h 19m

Manuel Escriche

03/Oct/14 8:52 AM

Done

In Progress

19d 13h 37m

Manuel Escriche

22/Oct/14 10:29 PM

In Progress

Done

1m 30s

Manuel Escriche

22/Oct/14 10:31 PM

Done

Closed

446d 11h 39m

Manuel Escriche

12/Jan/16 9:10 AM

People

Assignee:

José Ignacio Carretero Guarde

Reporter:

FW External User

Votes:

0 Vote for this issue

Watchers:

0 Start watching this issue

Dates

Created:

24/Sep/14 2:33 PM

Updated:

12/Apr/16 3:54 PM

Resolved:

22/Oct/14 10:31 PM

Agile

View on Board