[
https://issues.apache.org/jira/browse/DTACLOUD-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577660#comment-13577660
]
Ronelle Landy commented on DTACLOUD-472:
----------------------------------------
Testing fix with haml 3.1.7 ...
>> curl -X GET --user "un:pw" "localhost:3001/api/instances?format=xml"
<?xml version='1.0' encoding='utf-8' ?>
<instances>
<instance href='http://localhost:3001/api/instances/inst1' id='inst1'>
<name>MockUserInstance</name>
<owner_id>mockuser</owner_id>
<image href='http://localhost:3001/api/images/img3' id='img3'></image>
<realm href='http://localhost:3001/api/realms/us' id='us'></realm>
<state>RUNNING</state>
<hardware_profile
href='http://localhost:3001/api/hardware_profiles/m1-small' id='m1-small'>
</hardware_profile>
<actions>
<link href='http://localhost:3001/api/instances/inst1/reboot'
method='post' rel='reboot' />
<link href='http://localhost:3001/api/instances/inst1/stop' method='post'
rel='stop' />
<link href='http://localhost:3001/api/instances/inst1/run;id=inst1'
method='post' rel='run' />
<link href='http://localhost:3001/api/images;instance_id=inst1'
method='post' rel='create_image' />
</actions>
<public_addresses><address
type='hostname'>img1.inst1.public.com</address></public_addresses>
<private_addresses><address
type='hostname'>img1.inst1.private.com</address></private_addresses>
<storage_volumes></storage_volumes>
<authentication type='key'>
</authentication>
</instance>
<instance href='http://localhost:3001/api/instances/inst0' id='inst0'>
<name>Mock Instance With Profile Change</name>
<owner_id>mockuser</owner_id>
<image href='http://localhost:3001/api/images/img1' id='img1'></image>
<realm href='http://localhost:3001/api/realms/us' id='us'></realm>
<state>RUNNING</state>
<hardware_profile
href='http://localhost:3001/api/hardware_profiles/m1-large' id='m1-large'>
<property kind='fixed' name='memory' unit='MB' value='12288'></property>
</hardware_profile>
<actions>
<link href='http://localhost:3001/api/instances/inst0/reboot'
method='post' rel='reboot' />
<link href='http://localhost:3001/api/instances/inst0/stop' method='post'
rel='stop' />
<link href='http://localhost:3001/api/instances/inst0/run;id=inst0'
method='post' rel='run' />
<link href='http://localhost:3001/api/images;instance_id=inst0'
method='post' rel='create_image' />
</actions>
<public_addresses><address
type='hostname'>img1.inst0.public.com</address></public_addresses>
<private_addresses><address
type='hostname'>img1.inst0.private.com</address></private_addresses>
<storage_volumes></storage_volumes>
<authentication type='key'>
</authentication>
</instance>
</instances>
[root@cloud-qe-3 ~]# gem query |grep haml
haml (3.1.7)
Testing HAML 4.0 ...
[root@cloud-qe-3 ~]# gem query |grep haml
haml (4.0.0)
[root@cloud-qe-3 ~]# curl -X GET --user "un:pw"
"localhost:3001/api/instances?format=xml"
<?xml version='1.0' encoding='utf-8' ?>
<instances>
<instance href='http://localhost:3001/api/instances/inst1' id='inst1'>
<name>MockUserInstance</name>
<owner_id>mockuser</owner_id>
<image href='http://localhost:3001/api/images/img3' id='img3'></image>
<realm href='http://localhost:3001/api/realms/us' id='us'></realm>
<state>RUNNING</state>
<hardware_profile
href='http://localhost:3001/api/hardware_profiles/m1-small' id='m1-small'>
</hardware_profile>
<actions>
<link href='http://localhost:3001/api/instances/inst1/reboot'
method='post' rel='reboot' />
<link href='http://localhost:3001/api/instances/inst1/stop' method='post'
rel='stop' />
<link href='http://localhost:3001/api/instances/inst1/run;id=inst1'
method='post' rel='run' />
<link href='http://localhost:3001/api/images;instance_id=inst1'
method='post' rel='create_image' />
</actions>
<public_addresses><address
type='hostname'>img1.inst1.public.com</address></public_addresses>
<private_addresses><address
type='hostname'>img1.inst1.private.com</address></private_addresses>
<storage_volumes></storage_volumes>
<authentication type='key'>
</authentication>
</instance>
<instance href='http://localhost:3001/api/instances/inst0' id='inst0'>
<name>Mock Instance With Profile Change</name>
<owner_id>mockuser</owner_id>
<image href='http://localhost:3001/api/images/img1' id='img1'></image>
<realm href='http://localhost:3001/api/realms/us' id='us'></realm>
<state>RUNNING</state>
<hardware_profile
href='http://localhost:3001/api/hardware_profiles/m1-large' id='m1-large'>
<property kind='fixed' name='memory' unit='MB' value='12288'></property>
</hardware_profile>
<actions>
<link href='http://localhost:3001/api/instances/inst0/reboot'
method='post' rel='reboot' />
<link href='http://localhost:3001/api/instances/inst0/stop' method='post'
rel='stop' />
<link href='http://localhost:3001/api/instances/inst0/run;id=inst0'
method='post' rel='run' />
<link href='http://localhost:3001/api/images;instance_id=inst0'
method='post' rel='create_image' />
</actions>
<public_addresses><address
type='hostname'>img1.inst0.public.com</address></public_addresses>
<private_addresses><address
type='hostname'>img1.inst0.private.com</address></private_addresses>
<storage_volumes></storage_volumes>
<authentication type='key'>
</authentication>
</instance>
</instances>
> HAML 4.0 break the XML views
> ----------------------------
>
> Key: DTACLOUD-472
> URL: https://issues.apache.org/jira/browse/DTACLOUD-472
> Project: DeltaCloud
> Issue Type: Bug
> Reporter: Michal Fojtik
> Assignee: Michal Fojtik
> Priority: Blocker
>
> Hi,
> HAML has recently received an update and unfortunately it breaks our XML
> views:
> with haml-3.7.1:
> <?xml version='1.0' encoding='utf-8' ?>
> <instance href='http://localhost:3001/api/instances/inst0' id='inst0'>
> <name>Mock Instance With Profile Change</name>
> <owner_id>mockuser</owner_id>
> <image href='http://localhost:3001/api/images/img1' id='img1'></image>
> <realm href='http://localhost:3001/api/realms/us' id='us'></realm>
> <state>RUNNING</state>
> <hardware_profile
> href='http://localhost:3001/api/hardware_profiles/m1-large' id='m1-large'>
> <property kind='fixed' name='memory' unit='MB' value='12288'></property>
> </hardware_profile>
> <actions>
> <link href='http://localhost:3001/api/instances/inst0/reboot'
> method='post' rel='reboot' />
> <link href='http://localhost:3001/api/instances/inst0/stop' method='post'
> rel='stop' />
> <link href='http://localhost:3001/api/instances/inst0/run;id=inst0'
> method='post' rel='run' />
> <link href='http://localhost:3001/api/images;instance_id=inst0'
> method='post' rel='create_image' />
> </actions>
> <public_addresses><address
> type='hostname'>img1.inst0.public.com</address></public_addresses>
> <private_addresses><address
> type='hostname'>img1.inst0.private.com</address></private_addresses>
> <storage_volumes></storage_volumes>
> <authentication type='key'>
> </authentication>
> </instance>
> now with haml-4.0.0:
> <instance href='http://localhost:3001/api/instances/inst0' id='inst0'>
> <name>Mock Instance With Profile Change</name>
> <owner_id>mockuser</owner_id>
> <image href='http://localhost:3001/api/images/img1' id='img1'></image>
> <realm href='http://localhost:3001/api/realms/us' id='us'></realm>
> <state>RUNNING</state>
> <hardware_profile
> href='http://localhost:3001/api/hardware_profiles/m1-large' id='m1-large'>
> <property kind='fixed' name='memory' unit='MB' value='12288'></property>
> </hardware_profile>
> <actions>
> <link href='http://localhost:3001/api/instances/inst0/reboot'
> method='post' rel='reboot'>
> <link href='http://localhost:3001/api/instances/inst0/stop' method='post'
> rel='stop'>
> <link href='http://localhost:3001/api/instances/inst0/run;id=inst0'
> method='post' rel='run'>
> <link href='http://localhost:3001/api/images;instance_id=inst0'
> method='post' rel='create_image'>
> </actions>
> <public_addresses><address
> type='hostname'>img1.inst0.public.com</address></public_addresses>
> <private_addresses><address
> type='hostname'>img1.inst0.private.com</address></private_addresses>
> <storage_volumes></storage_volumes>
> <authentication type='key'>
> </authentication>
> </instance>
> Note the missing '/' in <links>
> There might be other views affected. I'm marking this bug as a 'blocker'
> because it could potentially hit all our users after they install DC.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
