[jira] [Commented] (CLOUDSTACK-9040) Tomcat 7 & 8 don't work with the install scripts on Ubuntu
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993325#comment-14993325 ] ASF GitHub Bot commented on CLOUDSTACK-9040: Github user ustcweizhou commented on the pull request: https://github.com/apache/cloudstack/pull/1040#issuecomment-154340784 @borisroman Thanks! good to know it. Could you give more details how to make it work on tomcat7, so that we can discuss and look for a solution to make CS working on both of tomcat6 and tomcat 7 if possible? > Tomcat 7 & 8 don't work with the install scripts on Ubuntu > -- > > Key: CLOUDSTACK-9040 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9040 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.6.0 >Reporter: Boris Schrijver >Assignee: Boris Schrijver >Priority: Critical > Fix For: 4.6.0 > > > Tomcat 7 & 8 don't work with the install scripts currently present on Ubuntu. > For now, we will just use Tomcat 6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9039) Log folder path Ubuntu
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993328#comment-14993328
]
ASF GitHub Bot commented on CLOUDSTACK-9039:
Github user ustcweizhou commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1039#discussion_r44112930
--- Diff: python/lib/cloudutils/serviceConfigServer.py ---
@@ -107,7 +107,8 @@ def checkHostName():
bash("chown cloud.cloud /var/run/cloudstack-management.pid")
#distro like sl 6.1 needs this folder, or tomcat6 failed to start
checkHostName()
-bash("mkdir /var/log/cloudstack-management/")
+bash("mkdir /var/log/cloudstack/")
+bash("mkdir /var/log/cloudstack/management/")
--- End diff --
I agree with @milamberspace .
btw, what about the /var/log/cloudstack/usage for usage server?
> Log folder path Ubuntu
> --
>
> Key: CLOUDSTACK-9039
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9039
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
>Affects Versions: 4.6.0
>Reporter: Boris Schrijver
>Assignee: Boris Schrijver
>Priority: Minor
>
> Log folder path is incorrect during setup.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9039) Log folder path Ubuntu
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993338#comment-14993338 ] ASF GitHub Bot commented on CLOUDSTACK-9039: Github user borisroman commented on the pull request: https://github.com/apache/cloudstack/pull/1039#issuecomment-154343137 @ustcweizhou This is only for the management server! The usage server will create it's own paths when installed. @milamberspace I'll push that change, thanks! > Log folder path Ubuntu > -- > > Key: CLOUDSTACK-9039 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9039 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.6.0 >Reporter: Boris Schrijver >Assignee: Boris Schrijver >Priority: Minor > > Log folder path is incorrect during setup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9041) Modifying template creation from snapshot function in common.py
Priti Sarap created CLOUDSTACK-9041: --- Summary: Modifying template creation from snapshot function in common.py Key: CLOUDSTACK-9041 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9041 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Reporter: Priti Sarap In create_from_snapshot function of Template class there is no parameter to accept if the template is public hence default it is creating private templates Hence adding this parameter. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9041) Modifying template creation from snapshot function in base.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priti Sarap updated CLOUDSTACK-9041: Summary: Modifying template creation from snapshot function in base.py (was: Modifying template creation from snapshot function in common.py) > Modifying template creation from snapshot function in base.py > - > > Key: CLOUDSTACK-9041 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9041 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Reporter: Priti Sarap > > In create_from_snapshot function of Template class there is no parameter to > accept if the template is public hence default it is creating private > templates > Hence adding this parameter. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9039) Log folder path Ubuntu
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993386#comment-14993386
]
ASF GitHub Bot commented on CLOUDSTACK-9039:
Github user ustcweizhou commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1039#discussion_r44116130
--- Diff: python/lib/cloudutils/serviceConfigServer.py ---
@@ -107,7 +107,8 @@ def checkHostName():
bash("chown cloud.cloud /var/run/cloudstack-management.pid")
#distro like sl 6.1 needs this folder, or tomcat6 failed to start
checkHostName()
-bash("mkdir /var/log/cloudstack-management/")
+bash("mkdir -p /var/log/cloudstack/")
+bash("mkdir -p /var/log/cloudstack/management/")
--- End diff --
you could remove line 110
> Log folder path Ubuntu
> --
>
> Key: CLOUDSTACK-9039
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9039
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
>Affects Versions: 4.6.0
>Reporter: Boris Schrijver
>Assignee: Boris Schrijver
>Priority: Minor
>
> Log folder path is incorrect during setup.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9039) Log folder path Ubuntu
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993396#comment-14993396 ] ASF GitHub Bot commented on CLOUDSTACK-9039: Github user ustcweizhou commented on the pull request: https://github.com/apache/cloudstack/pull/1039#issuecomment-154350435 @borisroman LGTM if remove line 110. > Log folder path Ubuntu > -- > > Key: CLOUDSTACK-9039 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9039 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.6.0 >Reporter: Boris Schrijver >Assignee: Boris Schrijver >Priority: Minor > > Log folder path is incorrect during setup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9041) Modifying template creation from snapshot function in base.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993408#comment-14993408 ] ASF GitHub Bot commented on CLOUDSTACK-9041: GitHub user pritisarap12 opened a pull request: https://github.com/apache/cloudstack/pull/1041 CLOUDSTACK-9041: Modifying template creation from snapshot function In create_from_snapshot function of Template class there is no parameter to accept if the template is public hence default it is creating private templates Hence adding this parameter. You can merge this pull request into a Git repository by running: $ git pull https://github.com/pritisarap12/cloudstack CLOUDSTACK-9041-Modifying-template-creation-from-snapshot-function-in-base.py Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1041.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1041 commit bbe0fc4be9527d51820b067a602886003991db4d Author: Priti Sarap Date: 2015-11-06T09:06:32Z CLOUDSTACK-9041: Modifying template creation from snapshot function in base.py > Modifying template creation from snapshot function in base.py > - > > Key: CLOUDSTACK-9041 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9041 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Reporter: Priti Sarap > > In create_from_snapshot function of Template class there is no parameter to > accept if the template is public hence default it is creating private > templates > Hence adding this parameter. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8832) Update Nuage VSP plugin to work with Nuage VSP release 3.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993434#comment-14993434 ] ASF GitHub Bot commented on CLOUDSTACK-8832: Github user ustcweizhou commented on the pull request: https://github.com/apache/cloudstack/pull/801#issuecomment-154363971 @mlsorensen I agree with that third-parties can ship their own packages based on official release. It is more flexible for them. They can release new packages with new feature/improvement and bug fix, no need to wait for official cloudstack release. I also understand their concern that the code difference between their branch and master branch will become more and more bigger if they cannot merge most of their codes to main branch. It will be difficult to upgrade to new cloudstack versio. The upgrade means a lot of work, especially if there is framework refactoring. I believe many companies have their cloudstack branch with new features and customized UI , and they face the issue when they want new features and upgrade to new version. > Update Nuage VSP plugin to work with Nuage VSP release 3.2 > -- > > Key: CLOUDSTACK-8832 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8832 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.6.0 >Reporter: Nick Livens >Assignee: Nick Livens > Attachments: nuageVspMarvinLogs.tar.gz > > > Nuage VSP 3.2 is being released, we want to bring the plugin up to date for > this release -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
René Moser created CLOUDSTACK-9042: -- Summary: VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs Key: CLOUDSTACK-9042 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Virtual Router Affects Versions: 4.5.2, 4.6.0 Reporter: René Moser Fix For: 4.5.3, 4.6.0 VR advanced networking. We experienced an issue when a few VMs were started at a time, some of them and always the same ones did not receive a IP from DHCP. After a debuging, we identified the problem in this sed command in ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh the VM which was not in /etc/dhcphosts.txt was named: songlog-1 When another VM was started named "log-1" the "songlog-1" entry was removed unexpectedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993535#comment-14993535 ] ASF GitHub Bot commented on CLOUDSTACK-9042: GitHub user resmo opened a pull request: https://github.com/apache/cloudstack/pull/1042 CLOUDSTACK-9042: VR: DHCP: fix missing DHCP host enties in /etc/dhcpentries.txt we had: 02:00:1e:07:01:53,set:10_102_92_5,10.102.92.5,songlog-1,infinite 02:00:0b:a2:00:3d,set:10_102_92_234,10.102.92.234,log-1,infinite This sed matched unexpectetly "songlog-1" as well when "log-1" was processed, resulting missing dhcp entry for songlog-1. You can merge this pull request into a Git repository by running: $ git pull https://github.com/resmo/cloudstack CLOUDSTACK-9042 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1042.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1042 commit baba68286faa89d83bfee7a7592f6392ff65e25d Author: Rene Moser Date: 2015-11-06T11:25:10Z CLOUDSTACK-9042: VR: DHCP: fix missing DHCP host enties in /etc/dhcpentries.txt we had: 02:00:1e:07:01:53,set:10_102_92_5,10.102.92.5,songlog-1,infinite 02:00:0b:a2:00:3d,set:10_102_92_234,10.102.92.234,log-1,infinite This sed matched unexpectetly "songlog-1" as well when "log-1" was processed, resulting missing dhcp entry for songlog-1. > VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs > --- > > Key: CLOUDSTACK-9042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.5.2, 4.6.0 >Reporter: René Moser > Fix For: 4.5.3, 4.6.0 > > > VR advanced networking. > We experienced an issue when a few VMs were started at a time, some of them > and always the same ones did not receive a IP from DHCP. > After a debuging, we identified the problem in this sed command in > ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh > the VM which was not in /etc/dhcphosts.txt was named: > songlog-1 > When another VM was started named "log-1" the "songlog-1" entry was removed > unexpectedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] René Moser reassigned CLOUDSTACK-9042: -- Assignee: René Moser > VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs > --- > > Key: CLOUDSTACK-9042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.5.2, 4.6.0 >Reporter: René Moser >Assignee: René Moser > Fix For: 4.5.3, 4.6.0 > > > VR advanced networking. > We experienced an issue when a few VMs were started at a time, some of them > and always the same ones did not receive a IP from DHCP. > After a debuging, we identified the problem in this sed command in > ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh > the VM which was not in /etc/dhcphosts.txt was named: > songlog-1 > When another VM was started named "log-1" the "songlog-1" entry was removed > unexpectedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] René Moser updated CLOUDSTACK-9042: --- Fix Version/s: (was: 4.4.4) 4.4.5 > VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs > --- > > Key: CLOUDSTACK-9042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.4.4, 4.5.2, 4.6.0 >Reporter: René Moser >Assignee: René Moser > Fix For: 4.4.5, 4.5.3, 4.6.0 > > > VR advanced networking. > We experienced an issue when a few VMs were started at a time, some of them > and always the same ones did not receive a IP from DHCP. > After a debuging, we identified the problem in this sed command in > ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh > the VM which was not in /etc/dhcphosts.txt was named: > songlog-1 > When another VM was started named "log-1" the "songlog-1" entry was removed > unexpectedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] René Moser updated CLOUDSTACK-9042: --- Fix Version/s: 4.4.4 > VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs > --- > > Key: CLOUDSTACK-9042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.4.4, 4.5.2, 4.6.0 >Reporter: René Moser >Assignee: René Moser > Fix For: 4.4.5, 4.5.3, 4.6.0 > > > VR advanced networking. > We experienced an issue when a few VMs were started at a time, some of them > and always the same ones did not receive a IP from DHCP. > After a debuging, we identified the problem in this sed command in > ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh > the VM which was not in /etc/dhcphosts.txt was named: > songlog-1 > When another VM was started named "log-1" the "songlog-1" entry was removed > unexpectedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] René Moser updated CLOUDSTACK-9042: --- Affects Version/s: 4.4.4 > VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs > --- > > Key: CLOUDSTACK-9042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.4.4, 4.5.2, 4.6.0 >Reporter: René Moser >Assignee: René Moser > Fix For: 4.4.5, 4.5.3, 4.6.0 > > > VR advanced networking. > We experienced an issue when a few VMs were started at a time, some of them > and always the same ones did not receive a IP from DHCP. > After a debuging, we identified the problem in this sed command in > ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh > the VM which was not in /etc/dhcphosts.txt was named: > songlog-1 > When another VM was started named "log-1" the "songlog-1" entry was removed > unexpectedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remi Bergsma updated CLOUDSTACK-9042: - Priority: Critical (was: Major) > VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs > --- > > Key: CLOUDSTACK-9042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.4.4, 4.5.2, 4.6.0 >Reporter: René Moser >Assignee: René Moser >Priority: Critical > Fix For: 4.4.5, 4.5.3, 4.6.0 > > > VR advanced networking. > We experienced an issue when a few VMs were started at a time, some of them > and always the same ones did not receive a IP from DHCP. > After a debuging, we identified the problem in this sed command in > ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh > the VM which was not in /etc/dhcphosts.txt was named: > songlog-1 > When another VM was started named "log-1" the "songlog-1" entry was removed > unexpectedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993576#comment-14993576 ] Remi Bergsma commented on CLOUDSTACK-9042: -- Intruduced here: https://github.com/apache/cloudstack/commit/63298d9b742811919717ffd6303c8a2e9d37a3dd > VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs > --- > > Key: CLOUDSTACK-9042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.4.4, 4.5.2, 4.6.0 >Reporter: René Moser >Assignee: René Moser >Priority: Critical > Fix For: 4.4.5, 4.5.3, 4.6.0 > > > VR advanced networking. > We experienced an issue when a few VMs were started at a time, some of them > and always the same ones did not receive a IP from DHCP. > After a debuging, we identified the problem in this sed command in > ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh > the VM which was not in /etc/dhcphosts.txt was named: > songlog-1 > When another VM was started named "log-1" the "songlog-1" entry was removed > unexpectedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993576#comment-14993576 ] Remi Bergsma edited comment on CLOUDSTACK-9042 at 11/6/15 12:22 PM: Introduced here: https://github.com/apache/cloudstack/commit/63298d9b742811919717ffd6303c8a2e9d37a3dd was (Author: remibergsma): Intruduced here: https://github.com/apache/cloudstack/commit/63298d9b742811919717ffd6303c8a2e9d37a3dd > VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs > --- > > Key: CLOUDSTACK-9042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.4.4, 4.5.2, 4.6.0 >Reporter: René Moser >Assignee: René Moser >Priority: Critical > Fix For: 4.4.5, 4.5.3, 4.6.0 > > > VR advanced networking. > We experienced an issue when a few VMs were started at a time, some of them > and always the same ones did not receive a IP from DHCP. > After a debuging, we identified the problem in this sed command in > ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh > the VM which was not in /etc/dhcphosts.txt was named: > songlog-1 > When another VM was started named "log-1" the "songlog-1" entry was removed > unexpectedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993590#comment-14993590 ] ASF GitHub Bot commented on CLOUDSTACK-9042: Github user ustcweizhou commented on the pull request: https://github.com/apache/cloudstack/pull/1042#issuecomment-154398072 LGTM btw, can you check other part except hostname in the file and fix them too? > VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs > --- > > Key: CLOUDSTACK-9042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.4.4, 4.5.2, 4.6.0 >Reporter: René Moser >Assignee: René Moser >Priority: Critical > Fix For: 4.4.5, 4.5.3, 4.6.0 > > > VR advanced networking. > We experienced an issue when a few VMs were started at a time, some of them > and always the same ones did not receive a IP from DHCP. > After a debuging, we identified the problem in this sed command in > ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh > the VM which was not in /etc/dhcphosts.txt was named: > songlog-1 > When another VM was started named "log-1" the "songlog-1" entry was removed > unexpectedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9039) Log folder path Ubuntu
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993594#comment-14993594
]
ASF GitHub Bot commented on CLOUDSTACK-9039:
Github user wido commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1039#discussion_r44132316
--- Diff: python/lib/cloudutils/serviceConfigServer.py ---
@@ -107,7 +107,8 @@ def checkHostName():
bash("chown cloud.cloud /var/run/cloudstack-management.pid")
#distro like sl 6.1 needs this folder, or tomcat6 failed to start
checkHostName()
-bash("mkdir /var/log/cloudstack-management/")
+bash("mkdir -p /var/log/cloudstack/")
+bash("mkdir -p /var/log/cloudstack/management/")
--- End diff --
Both lines can be removed. The packaging already creates them.
> Log folder path Ubuntu
> --
>
> Key: CLOUDSTACK-9039
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9039
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
>Affects Versions: 4.6.0
>Reporter: Boris Schrijver
>Assignee: Boris Schrijver
>Priority: Minor
>
> Log folder path is incorrect during setup.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8832) Update Nuage VSP plugin to work with Nuage VSP release 3.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993602#comment-14993602 ] ASF GitHub Bot commented on CLOUDSTACK-8832: Github user remibergsma commented on the pull request: https://github.com/apache/cloudstack/pull/801#issuecomment-154401989 Great! This one is on my list to be merged once 4.6.0 is out and we start building 4.7.0. > Update Nuage VSP plugin to work with Nuage VSP release 3.2 > -- > > Key: CLOUDSTACK-8832 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8832 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.6.0 >Reporter: Nick Livens >Assignee: Nick Livens > Attachments: nuageVspMarvinLogs.tar.gz > > > Nuage VSP 3.2 is being released, we want to bring the plugin up to date for > this release -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8715) Add support for qemu-guest-agent to libvirt provider
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993621#comment-14993621 ] ASF GitHub Bot commented on CLOUDSTACK-8715: Github user wido commented on the pull request: https://github.com/apache/cloudstack/pull/1027#issuecomment-154403884 @ustcweizhou I looked at the code more closely and it looks good. However, I would still vote for having the Agent port always enabled. This saves a lot of code and a lot of testing as well. I would also remove the Python code and write a Java Util which directly talks to the local Unix socket. So, we always enable a Guest Agent port and when we want to talk to the Instance we send a ping. If it responds, it responds. If not, we assume there is no Agent in there. > Add support for qemu-guest-agent to libvirt provider > > > Key: CLOUDSTACK-8715 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8715 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Reporter: Sten Spans >Assignee: Wido den Hollander > Labels: kvm, libvirt, qemu, systemvm > Fix For: Future > > > The qemu guest agent is a newer part of qemu/kvm/libvirt which exposes quite > a lot of useful functionality, which can only be provided by having an agent > on the VM. This includes things like freezing/thawing filesystems (for > backups), reading files on the guest, listing interfaces / ip addresses, etc. > This feature has been requested by users, but is currently not implemented. > http://users.cloudstack.apache.narkive.com/3TTmy3zj/enabling-qemu-guest-agent > The first change needed is to add the following to the XML generated for KVM > virtual machines,: > > > > > This provides the communication channel between libvirt and the agent on the > host. All in all a pretty simple change to LibvirtComputingResource.java / > LibvirtVMDef.java > Secondly the qemu-guest-agent package needs to be added to the systemvm > template. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993627#comment-14993627 ] ASF GitHub Bot commented on CLOUDSTACK-9042: Github user remibergsma commented on the pull request: https://github.com/apache/cloudstack/pull/1042#issuecomment-154404851 FYI: Started tests on this branch. > VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs > --- > > Key: CLOUDSTACK-9042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.4.4, 4.5.2, 4.6.0 >Reporter: René Moser >Assignee: René Moser >Priority: Critical > Fix For: 4.4.5, 4.5.3, 4.6.0 > > > VR advanced networking. > We experienced an issue when a few VMs were started at a time, some of them > and always the same ones did not receive a IP from DHCP. > After a debuging, we identified the problem in this sed command in > ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh > the VM which was not in /etc/dhcphosts.txt was named: > songlog-1 > When another VM was started named "log-1" the "songlog-1" entry was removed > unexpectedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9040) Tomcat 7 & 8 don't work with the install scripts on Ubuntu
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993632#comment-14993632 ] ASF GitHub Bot commented on CLOUDSTACK-9040: Github user remibergsma commented on the pull request: https://github.com/apache/cloudstack/pull/1040#issuecomment-154405274 Can someone please post some results of a successful install after this change? > Tomcat 7 & 8 don't work with the install scripts on Ubuntu > -- > > Key: CLOUDSTACK-9040 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9040 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.6.0 >Reporter: Boris Schrijver >Assignee: Boris Schrijver >Priority: Critical > Fix For: 4.6.0 > > > Tomcat 7 & 8 don't work with the install scripts currently present on Ubuntu. > For now, we will just use Tomcat 6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9039) Log folder path Ubuntu
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993637#comment-14993637 ] ASF GitHub Bot commented on CLOUDSTACK-9039: Github user remibergsma commented on the pull request: https://github.com/apache/cloudstack/pull/1039#issuecomment-154405523 FYI: Started tests on this branch. > Log folder path Ubuntu > -- > > Key: CLOUDSTACK-9039 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9039 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.6.0 >Reporter: Boris Schrijver >Assignee: Boris Schrijver >Priority: Minor > > Log folder path is incorrect during setup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8715) Add support for qemu-guest-agent to libvirt provider
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993641#comment-14993641 ] ASF GitHub Bot commented on CLOUDSTACK-8715: Github user ustcweizhou commented on the pull request: https://github.com/apache/cloudstack/pull/1027#issuecomment-154405884 @wido thanks for your review. good to hear that. There are 5 commits by me in this PR. You can cherry-pick the commits you need to your branch and continue your work :) The function checkGuestAgentSync in the commit is used to verify if the guest agent works. > Add support for qemu-guest-agent to libvirt provider > > > Key: CLOUDSTACK-8715 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8715 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Reporter: Sten Spans >Assignee: Wido den Hollander > Labels: kvm, libvirt, qemu, systemvm > Fix For: Future > > > The qemu guest agent is a newer part of qemu/kvm/libvirt which exposes quite > a lot of useful functionality, which can only be provided by having an agent > on the VM. This includes things like freezing/thawing filesystems (for > backups), reading files on the guest, listing interfaces / ip addresses, etc. > This feature has been requested by users, but is currently not implemented. > http://users.cloudstack.apache.narkive.com/3TTmy3zj/enabling-qemu-guest-agent > The first change needed is to add the following to the XML generated for KVM > virtual machines,: > > > > > This provides the communication channel between libvirt and the agent on the > host. All in all a pretty simple change to LibvirtComputingResource.java / > LibvirtVMDef.java > Secondly the qemu-guest-agent package needs to be added to the systemvm > template. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9039) Log folder path Ubuntu
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993662#comment-14993662 ] ASF GitHub Bot commented on CLOUDSTACK-9039: Github user borisroman commented on the pull request: https://github.com/apache/cloudstack/pull/1039#issuecomment-154409103 @remibergsma @ustcweizhou As @wido pointed out, they are already created through the packager. https://github.com/apache/cloudstack/blob/master/debian/rules#L61 https://github.com/apache/cloudstack/blob/master/debian/cloudstack-management.install#L43 > Log folder path Ubuntu > -- > > Key: CLOUDSTACK-9039 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9039 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.6.0 >Reporter: Boris Schrijver >Assignee: Boris Schrijver >Priority: Minor > > Log folder path is incorrect during setup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9039) Log folder path Ubuntu
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993674#comment-14993674 ] ASF GitHub Bot commented on CLOUDSTACK-9039: Github user borisroman commented on the pull request: https://github.com/apache/cloudstack/pull/1039#issuecomment-154411673 @wido @ustcweizhou Could you review again please? > Log folder path Ubuntu > -- > > Key: CLOUDSTACK-9039 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9039 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.6.0 >Reporter: Boris Schrijver >Assignee: Boris Schrijver >Priority: Minor > > Log folder path is incorrect during setup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993691#comment-14993691 ] ASF GitHub Bot commented on CLOUDSTACK-9042: Github user resmo commented on the pull request: https://github.com/apache/cloudstack/pull/1042#issuecomment-154414891 @ustcweizhou seeing some more potential problems. > VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs > --- > > Key: CLOUDSTACK-9042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.4.4, 4.5.2, 4.6.0 >Reporter: René Moser >Assignee: René Moser >Priority: Critical > Fix For: 4.4.5, 4.5.3, 4.6.0 > > > VR advanced networking. > We experienced an issue when a few VMs were started at a time, some of them > and always the same ones did not receive a IP from DHCP. > After a debuging, we identified the problem in this sed command in > ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh > the VM which was not in /etc/dhcphosts.txt was named: > songlog-1 > When another VM was started named "log-1" the "songlog-1" entry was removed > unexpectedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9025) Unable to deploy VM instance from template if template spin from linked clone snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remi Bergsma updated CLOUDSTACK-9025: - Fix Version/s: (was: 4.6.0) > Unable to deploy VM instance from template if template spin from linked clone > snapshot > -- > > Key: CLOUDSTACK-9025 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9025 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: XenServer >Affects Versions: 4.5.2 > Environment: XenServer 6.5 >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar >Priority: Critical > > As default, CloudStack create linked clone snapshot for VM instance . When we > take a snapshot for the VM, and create a template based on such snapshot, > CloudStack only download incremental VHD as template file, as a result, the > VM instance fail to deploy as it is incomplete. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9043) Localization de_DE and zh_CN don't works: Uncaught SyntaxError: Unexpected token ILLEGAL
Milamber created CLOUDSTACK-9043: Summary: Localization de_DE and zh_CN don't works: Uncaught SyntaxError: Unexpected token ILLEGAL Key: CLOUDSTACK-9043 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9043 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.6.0 Reporter: Milamber Assignee: Milamber Fix For: 4.6.0 Found 2 bugs in German and Chinese localization (characters illegals in javascript) Some strings don't localized, only thes keys displays (all strings after the illegal char) (Error message in Chrome: Uncaught SyntaxError: Unexpected token ILLEGAL) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-8427) Some messages are hard-coded in javascript after Volume upload branch merge(0b835592)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milamber closed CLOUDSTACK-8427. Resolution: Fixed > Some messages are hard-coded in javascript after Volume upload branch > merge(0b835592) > - > > Key: CLOUDSTACK-8427 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8427 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Ramamurti Subramanian >Assignee: Milamber > Fix For: 4.6.0 > > > Some messages are hard-coded in javascript after Volume upload branch > merge(0b835592) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8427) Some messages are hard-coded in javascript after Volume upload branch merge(0b835592)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milamber updated CLOUDSTACK-8427: - Fix Version/s: (was: Future) 4.6.0 > Some messages are hard-coded in javascript after Volume upload branch > merge(0b835592) > - > > Key: CLOUDSTACK-8427 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8427 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Ramamurti Subramanian >Assignee: Milamber > Fix For: 4.6.0 > > > Some messages are hard-coded in javascript after Volume upload branch > merge(0b835592) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993752#comment-14993752 ] ASF GitHub Bot commented on CLOUDSTACK-9042: Github user resmo commented on the pull request: https://github.com/apache/cloudstack/pull/1042#issuecomment-154426348 @remibergsma @ustcweizhou updated and rebased the patch with some more fixes... > VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs > --- > > Key: CLOUDSTACK-9042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.4.4, 4.5.2, 4.6.0 >Reporter: René Moser >Assignee: René Moser >Priority: Critical > Fix For: 4.4.5, 4.5.3, 4.6.0 > > > VR advanced networking. > We experienced an issue when a few VMs were started at a time, some of them > and always the same ones did not receive a IP from DHCP. > After a debuging, we identified the problem in this sed command in > ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh > the VM which was not in /etc/dhcphosts.txt was named: > songlog-1 > When another VM was started named "log-1" the "songlog-1" entry was removed > unexpectedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993773#comment-14993773 ] ASF GitHub Bot commented on CLOUDSTACK-9042: Github user remibergsma commented on the pull request: https://github.com/apache/cloudstack/pull/1042#issuecomment-154430267 @resmo @ustcweizhou This script is not used in 4.6 I'd say. There is a python class called CsDhcp.py that handles this. > VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs > --- > > Key: CLOUDSTACK-9042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.4.4, 4.5.2, 4.6.0 >Reporter: René Moser >Assignee: René Moser >Priority: Critical > Fix For: 4.4.5, 4.5.3, 4.6.0 > > > VR advanced networking. > We experienced an issue when a few VMs were started at a time, some of them > and always the same ones did not receive a IP from DHCP. > After a debuging, we identified the problem in this sed command in > ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh > the VM which was not in /etc/dhcphosts.txt was named: > songlog-1 > When another VM was started named "log-1" the "songlog-1" entry was removed > unexpectedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993801#comment-14993801 ] ASF GitHub Bot commented on CLOUDSTACK-9042: Github user resmo commented on the pull request: https://github.com/apache/cloudstack/pull/1042#issuecomment-154436021 @remibergsma okay, never mind for false alarm then. > VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs > --- > > Key: CLOUDSTACK-9042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.4.4, 4.5.2, 4.6.0 >Reporter: René Moser >Assignee: René Moser >Priority: Critical > Fix For: 4.4.5, 4.5.3, 4.6.0 > > > VR advanced networking. > We experienced an issue when a few VMs were started at a time, some of them > and always the same ones did not receive a IP from DHCP. > After a debuging, we identified the problem in this sed command in > ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh > the VM which was not in /etc/dhcphosts.txt was named: > songlog-1 > When another VM was started named "log-1" the "songlog-1" entry was removed > unexpectedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9042) VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993851#comment-14993851 ] ASF GitHub Bot commented on CLOUDSTACK-9042: Github user remibergsma commented on the pull request: https://github.com/apache/cloudstack/pull/1042#issuecomment-154446597 @resmo That's all fine, glad you took the time to submit this. You may want to send the same PR against 4.5, as it is definitely relevant there. And, maybe you can repeat the test you did against 4.6, so we know if it works fine in 4.6. It uses other code, but there could still be an issue. > VR: Missing dhcp entries in /etc/dhpchosts.txt after starting a few VMs > --- > > Key: CLOUDSTACK-9042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9042 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.4.4, 4.5.2, 4.6.0 >Reporter: René Moser >Assignee: René Moser >Priority: Critical > Fix For: 4.4.5, 4.5.3, 4.6.0 > > > VR advanced networking. > We experienced an issue when a few VMs were started at a time, some of them > and always the same ones did not receive a IP from DHCP. > After a debuging, we identified the problem in this sed command in > ./systemvm/patches/debian/config/opt/cloud/bin/edithosts.sh > the VM which was not in /etc/dhcphosts.txt was named: > songlog-1 > When another VM was started named "log-1" the "songlog-1" entry was removed > unexpectedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9043) Localization de_DE and zh_CN don't works: Uncaught SyntaxError: Unexpected token ILLEGAL
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993884#comment-14993884 ] ASF GitHub Bot commented on CLOUDSTACK-9043: GitHub user milamberspace opened a pull request: https://github.com/apache/cloudstack/pull/1043 CLOUDSTACK-9043 Remove \n (new line) in German and Chinese translation The new line isn't in the original strings and are invalid character in the javascript files/ui Tested with success on Chrome You can merge this pull request into a Git repository by running: $ git pull https://github.com/milamberspace/cloudstack CLOUDSTACK-9043-Unexpected-token-ILLEGAL_de_DE-zh_CN Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1043.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1043 commit 813cbc0c571eab465fe8d380df920ada4f62141c Author: Milamber Date: 2015-11-06T15:37:23Z Remove \n (new line) in German and Chinese translation The new line isn't in the original strings and are invalid character in the javascript files/ui > Localization de_DE and zh_CN don't works: Uncaught SyntaxError: Unexpected > token ILLEGAL > > > Key: CLOUDSTACK-9043 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9043 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.6.0 >Reporter: Milamber >Assignee: Milamber > Labels: ui > Fix For: 4.6.0 > > > Found 2 bugs in German and Chinese localization (characters illegals in > javascript) > Some strings don't localized, only thes keys displays (all strings after the > illegal char) > (Error message in Chrome: Uncaught SyntaxError: Unexpected token ILLEGAL) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-5822) ssh keypairs are removed after rebooting vm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994059#comment-14994059 ] ASF GitHub Bot commented on CLOUDSTACK-5822: GitHub user ustcweizhou opened a pull request: https://github.com/apache/cloudstack/pull/1044 CLOUDSTACK-5822: keep user-added sshkeys in authorized_keys For now, if we add the ssh key inside the vm (not on cloudstack UI), the sshkey will be removed if we reset the sshkey on cloudstack UI. After this commit, the sshkey (added by cloudstack) will end with cloudst...@apache.org. We will only control the sshkeys with cloudst...@apache.org. This will be used for multiple sshkey support for vm in the future. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ustcweizhou/cloudstack keep-sshkey Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1044.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1044 commit 64ef4fa958878ceedfc8009804898f439cdeaf0f Author: Wei Zhou Date: 2015-11-06T13:28:14Z CLOUDSTACK-5822: keep user-added sshkeys in authorized_keys > ssh keypairs are removed after rebooting vm > --- > > Key: CLOUDSTACK-5822 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5822 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Wei Zhou >Assignee: Wei Zhou > > For a ssh keypair-enabled vm, the keys in /root/.ssh/authorized_keys will be > reset after rebooting the vm. Only the keypair specified in cloudstack will > be added. We should keep the keypairs added by users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
