You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "dave johnson (JIRA)" <ji...@apache.org> on 2011/07/13 16:37:00 UTC

[jira] [Created] (DTACLOUD-56) fails to get IP addr of RHEVM vm

fails to get IP addr of RHEVM vm
--------------------------------

                 Key: DTACLOUD-56
                 URL: https://issues.apache.org/jira/browse/DTACLOUD-56
             Project: DeltaCloud
          Issue Type: Bug
         Environment: Aeolus-conductor configured for rhevm provider

[root@hp-dl2x170g6-01 ~]# rpm -qa | egrep 'aeolus|deltacloud' | sort
aeolus-all-0.3.0-0.el6.20110711131044git5bc7abf.noarch
aeolus-conductor-0.3.0-0.el6.20110711131044git5bc7abf.noarch
aeolus-conductor-daemons-0.3.0-0.el6.20110711131044git5bc7abf.noarch
aeolus-conductor-doc-0.3.0-0.el6.20110711131044git5bc7abf.noarch
aeolus-configure-2.0.1-0.el6.20110708134115gitab1e6dc.noarch
condor-deltacloud-gahp-7.6.0-5dcloud.el6.x86_64
deltacloud-core-0.3.9999-1308927004.el6.noarch
libdeltacloud-0.9-1.el6.x86_64
rubygem-aeolus-cli-0.0.1-1.el6.20110711131044git5bc7abf.noarch
rubygem-deltacloud-client-0.3.1-1.el6.noarch
[root@hp-dl2x170g6-01 ~]# 
            Reporter: dave johnson
            Assignee: David Lutterkort


1.  Deploy a vm to rhevm provider through conductor deployables
2.  See vm start in rhevm UI
3.  Refresh conductor instance page to see IP address but get MAC address instead
4.  Access deltacloud api through browser and see the same thing, MAC is given for public address 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (DTACLOUD-56) fails to get IP addr of RHEVM vm

Posted by "dave johnson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DTACLOUD-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065328#comment-13065328 ] 

dave johnson commented on DTACLOUD-56:
--------------------------------------

Spoke to someone in the #rhev-dev irc channel and confirmed that there is no
rhev tools for linux in v2.2.

rhev-tools for linux will become available in rhev v3.0 which is scheduled for
external beta aug 2011 and full GA in December.


> fails to get IP addr of RHEVM vm
> --------------------------------
>
>                 Key: DTACLOUD-56
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-56
>             Project: DeltaCloud
>          Issue Type: Bug
>         Environment: Aeolus-conductor configured for rhevm provider
> [root@hp-dl2x170g6-01 ~]# rpm -qa | egrep 'aeolus|deltacloud' | sort
> aeolus-all-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-daemons-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-doc-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-configure-2.0.1-0.el6.20110708134115gitab1e6dc.noarch
> condor-deltacloud-gahp-7.6.0-5dcloud.el6.x86_64
> deltacloud-core-0.3.9999-1308927004.el6.noarch
> libdeltacloud-0.9-1.el6.x86_64
> rubygem-aeolus-cli-0.0.1-1.el6.20110711131044git5bc7abf.noarch
> rubygem-deltacloud-client-0.3.1-1.el6.noarch
> [root@hp-dl2x170g6-01 ~]# 
>            Reporter: dave johnson
>            Assignee: David Lutterkort
>         Attachments: actual.png
>
>
> 1.  Deploy a vm to rhevm provider through conductor deployables
> 2.  See vm start in rhevm UI
> 3.  Refresh conductor instance page to see IP address but get MAC address instead
> 4.  Access deltacloud api through browser and see the same thing, MAC is given for public address 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (DTACLOUD-56) fails to get IP addr of RHEVM vm

Posted by "dave johnson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DTACLOUD-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

dave johnson closed DTACLOUD-56.
--------------------------------

    Resolution: Won't Fix

Limitation of RHEV v2.2

> fails to get IP addr of RHEVM vm
> --------------------------------
>
>                 Key: DTACLOUD-56
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-56
>             Project: DeltaCloud
>          Issue Type: Bug
>         Environment: Aeolus-conductor configured for rhevm provider
> [root@hp-dl2x170g6-01 ~]# rpm -qa | egrep 'aeolus|deltacloud' | sort
> aeolus-all-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-daemons-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-doc-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-configure-2.0.1-0.el6.20110708134115gitab1e6dc.noarch
> condor-deltacloud-gahp-7.6.0-5dcloud.el6.x86_64
> deltacloud-core-0.3.9999-1308927004.el6.noarch
> libdeltacloud-0.9-1.el6.x86_64
> rubygem-aeolus-cli-0.0.1-1.el6.20110711131044git5bc7abf.noarch
> rubygem-deltacloud-client-0.3.1-1.el6.noarch
> [root@hp-dl2x170g6-01 ~]# 
>            Reporter: dave johnson
>            Assignee: David Lutterkort
>         Attachments: actual.png
>
>
> 1.  Deploy a vm to rhevm provider through conductor deployables
> 2.  See vm start in rhevm UI
> 3.  Refresh conductor instance page to see IP address but get MAC address instead
> 4.  Access deltacloud api through browser and see the same thing, MAC is given for public address 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (DTACLOUD-56) fails to get IP addr of RHEVM vm

Posted by "Michal Fojtik (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DTACLOUD-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064665#comment-13064665 ] 

Michal Fojtik commented on DTACLOUD-56:
---------------------------------------

Hi Dave,

This happen because you don't have guest tools installed on the VM. In RHEV-M in order to get an IP back you need to have them installed otherwise Deltacloud API is able to just fetch an MAC address of the guest.

 - michal

> fails to get IP addr of RHEVM vm
> --------------------------------
>
>                 Key: DTACLOUD-56
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-56
>             Project: DeltaCloud
>          Issue Type: Bug
>         Environment: Aeolus-conductor configured for rhevm provider
> [root@hp-dl2x170g6-01 ~]# rpm -qa | egrep 'aeolus|deltacloud' | sort
> aeolus-all-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-daemons-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-doc-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-configure-2.0.1-0.el6.20110708134115gitab1e6dc.noarch
> condor-deltacloud-gahp-7.6.0-5dcloud.el6.x86_64
> deltacloud-core-0.3.9999-1308927004.el6.noarch
> libdeltacloud-0.9-1.el6.x86_64
> rubygem-aeolus-cli-0.0.1-1.el6.20110711131044git5bc7abf.noarch
> rubygem-deltacloud-client-0.3.1-1.el6.noarch
> [root@hp-dl2x170g6-01 ~]# 
>            Reporter: dave johnson
>            Assignee: David Lutterkort
>         Attachments: actual.png
>
>
> 1.  Deploy a vm to rhevm provider through conductor deployables
> 2.  See vm start in rhevm UI
> 3.  Refresh conductor instance page to see IP address but get MAC address instead
> 4.  Access deltacloud api through browser and see the same thing, MAC is given for public address 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (DTACLOUD-56) fails to get IP addr of RHEVM vm

Posted by "dave johnson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DTACLOUD-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

dave johnson updated DTACLOUD-56:
---------------------------------

    Attachment: actual.png

shows ifconfig of vm and deltacloud-core/api/instances/uuid page

> fails to get IP addr of RHEVM vm
> --------------------------------
>
>                 Key: DTACLOUD-56
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-56
>             Project: DeltaCloud
>          Issue Type: Bug
>         Environment: Aeolus-conductor configured for rhevm provider
> [root@hp-dl2x170g6-01 ~]# rpm -qa | egrep 'aeolus|deltacloud' | sort
> aeolus-all-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-daemons-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-doc-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-configure-2.0.1-0.el6.20110708134115gitab1e6dc.noarch
> condor-deltacloud-gahp-7.6.0-5dcloud.el6.x86_64
> deltacloud-core-0.3.9999-1308927004.el6.noarch
> libdeltacloud-0.9-1.el6.x86_64
> rubygem-aeolus-cli-0.0.1-1.el6.20110711131044git5bc7abf.noarch
> rubygem-deltacloud-client-0.3.1-1.el6.noarch
> [root@hp-dl2x170g6-01 ~]# 
>            Reporter: dave johnson
>            Assignee: David Lutterkort
>         Attachments: actual.png
>
>
> 1.  Deploy a vm to rhevm provider through conductor deployables
> 2.  See vm start in rhevm UI
> 3.  Refresh conductor instance page to see IP address but get MAC address instead
> 4.  Access deltacloud api through browser and see the same thing, MAC is given for public address 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (DTACLOUD-56) fails to get IP addr of RHEVM vm

Posted by "dave johnson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DTACLOUD-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064867#comment-13064867 ] 

dave johnson commented on DTACLOUD-56:
--------------------------------------

Found the tools, will install and give some feedback tomorrow

> fails to get IP addr of RHEVM vm
> --------------------------------
>
>                 Key: DTACLOUD-56
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-56
>             Project: DeltaCloud
>          Issue Type: Bug
>         Environment: Aeolus-conductor configured for rhevm provider
> [root@hp-dl2x170g6-01 ~]# rpm -qa | egrep 'aeolus|deltacloud' | sort
> aeolus-all-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-daemons-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-doc-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-configure-2.0.1-0.el6.20110708134115gitab1e6dc.noarch
> condor-deltacloud-gahp-7.6.0-5dcloud.el6.x86_64
> deltacloud-core-0.3.9999-1308927004.el6.noarch
> libdeltacloud-0.9-1.el6.x86_64
> rubygem-aeolus-cli-0.0.1-1.el6.20110711131044git5bc7abf.noarch
> rubygem-deltacloud-client-0.3.1-1.el6.noarch
> [root@hp-dl2x170g6-01 ~]# 
>            Reporter: dave johnson
>            Assignee: David Lutterkort
>         Attachments: actual.png
>
>
> 1.  Deploy a vm to rhevm provider through conductor deployables
> 2.  See vm start in rhevm UI
> 3.  Refresh conductor instance page to see IP address but get MAC address instead
> 4.  Access deltacloud api through browser and see the same thing, MAC is given for public address 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira