Re: [node-devel] RC for oVirt Node 3.0.0 is now available
- Original Message - > From: "Mike Burns" > To: "node-devel" , annou...@ovirt.org > Sent: Friday, May 17, 2013 7:12:48 PM > Subject: [node-devel] RC for oVirt Node 3.0.0 is now available > > What can I test? > You can focus on hardware support, package integration, the > installation (all paths) and the TUI. Hi! 1. ovirt-node-upgrade should be moved to /usr/sbin as it is a tool to be executed by admin, and it is not working properly. ssh host ovirt-node-upgrade --iso=- --reboot=10 < iso 2. when I try to enable ssh and save, I get the following on black text screen: An error appeared in the UI: Press ENTER to logout... or enter 's' to drop to shell 3. I don't understand the difference of gray and non gray fields... I can access both... 4. Registration of HTTP does not work for some reason... do not think it is a new problem. 5. Registration using HTTPS produces a dialog with the following content: @ENGINENAME@ Fingerprint TBD ... 6. Saving does not configure vdsm-reg.conf nor starting it. --- Douglas, Can you please work with ovirt-node team so that we have a working solution? Thanks, Alon ___ node-devel mailing list node-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/node-devel
Re: [node-devel] RC for oVirt Node 3.0.0 is now available
On 05/20/2013 04:48 AM, Alon Bar-Lev wrote: - Original Message - From: "Mike Burns" To: "node-devel" , annou...@ovirt.org Sent: Friday, May 17, 2013 7:12:48 PM Subject: [node-devel] RC for oVirt Node 3.0.0 is now available What can I test? You can focus on hardware support, package integration, the installation (all paths) and the TUI. Hi! Thanks for the testing Alon! 1. ovirt-node-upgrade should be moved to /usr/sbin as it is a tool to be executed by admin, and it is not working properly. ssh host ovirt-node-upgrade --iso=- --reboot=10 < iso Joey, can you post a patch to move it into /usr/sbin? 2. when I try to enable ssh and save, I get the following on black text screen: An error appeared in the UI: Press ENTER to logout... or enter 's' to drop to shell Ryan, can you look into this? 3. I don't understand the difference of gray and non gray fields... I can access both... Do you have examples? Fabian, can you investigate? 4. Registration of HTTP does not work for some reason... do not think it is a new problem. 5. Registration using HTTPS produces a dialog with the following content: @ENGINENAME@ Fingerprint TBD ... 6. Saving does not configure vdsm-reg.conf nor starting it. These 3 -- yes, there are a number of things broken on the page. I filed a bug over the weekend: https://bugzilla.redhat.com/show_bug.cgi?id=964320 --- Douglas, Can you please work with ovirt-node team so that we have a working solution? Thanks, Alon Thanks, Mike ___ node-devel mailing list node-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/node-devel
Re: [node-devel] RC for oVirt Node 3.0.0 is now available
On 05/20/2013 11:07 AM, Douglas Schilling Landgraf wrote: On 05/20/2013 08:03 AM, Mike Burns wrote: On 05/20/2013 04:48 AM, Alon Bar-Lev wrote: - Original Message - From: "Mike Burns" To: "node-devel" , annou...@ovirt.org Sent: Friday, May 17, 2013 7:12:48 PM Subject: [node-devel] RC for oVirt Node 3.0.0 is now available What can I test? You can focus on hardware support, package integration, the installation (all paths) and the TUI. Hi! Thanks for the testing Alon! 1. ovirt-node-upgrade should be moved to /usr/sbin as it is a tool to be executed by admin, and it is not working properly. ssh host ovirt-node-upgrade --iso=- --reboot=10 < iso Joey, can you post a patch to move it into /usr/sbin? 2. when I try to enable ssh and save, I get the following on black text screen: An error appeared in the UI: Press ENTER to logout... or enter 's' to drop to shell Ryan, can you look into this? 3. I don't understand the difference of gray and non gray fields... I can access both... Do you have examples? Fabian, can you investigate? 4. Registration of HTTP does not work for some reason... do not think it is a new problem. 5. Registration using HTTPS produces a dialog with the following content: @ENGINENAME@ Fingerprint TBD ... 6. Saving does not configure vdsm-reg.conf nor starting it. These 3 -- yes, there are a number of things broken on the page. I filed a bug over the weekend: https://bugzilla.redhat.com/show_bug.cgi?id=964320 Mike/Alon Should I start from this point? This is were I left it over the weekend. Mike ___ node-devel mailing list node-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/node-devel
Re: [node-devel] RC for oVirt Node 3.0.0 is now available
On 05/20/2013 08:03 AM, Mike Burns wrote: On 05/20/2013 04:48 AM, Alon Bar-Lev wrote: - Original Message - From: "Mike Burns" To: "node-devel" , annou...@ovirt.org Sent: Friday, May 17, 2013 7:12:48 PM Subject: [node-devel] RC for oVirt Node 3.0.0 is now available What can I test? You can focus on hardware support, package integration, the installation (all paths) and the TUI. Hi! Thanks for the testing Alon! 1. ovirt-node-upgrade should be moved to /usr/sbin as it is a tool to be executed by admin, and it is not working properly. ssh host ovirt-node-upgrade --iso=- --reboot=10 < iso Joey, can you post a patch to move it into /usr/sbin? 2. when I try to enable ssh and save, I get the following on black text screen: An error appeared in the UI: Press ENTER to logout... or enter 's' to drop to shell Ryan, can you look into this? 3. I don't understand the difference of gray and non gray fields... I can access both... Do you have examples? Fabian, can you investigate? 4. Registration of HTTP does not work for some reason... do not think it is a new problem. 5. Registration using HTTPS produces a dialog with the following content: @ENGINENAME@ Fingerprint TBD ... 6. Saving does not configure vdsm-reg.conf nor starting it. These 3 -- yes, there are a number of things broken on the page. I filed a bug over the weekend: https://bugzilla.redhat.com/show_bug.cgi?id=964320 Mike/Alon Should I start from this point? -- Cheers Douglas ___ node-devel mailing list node-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/node-devel
Re: [node-devel] RC for oVirt Node 3.0.0 is now available
Am Montag, den 20.05.2013, 08:03 -0400 schrieb Mike Burns: > On 05/20/2013 04:48 AM, Alon Bar-Lev wrote: > > > > > > - Original Message - > >> From: "Mike Burns" > >> To: "node-devel" , annou...@ovirt.org > >> Sent: Friday, May 17, 2013 7:12:48 PM > >> Subject: [node-devel] RC for oVirt Node 3.0.0 is now available > >> > >> What can I test? > >> You can focus on hardware support, package integration, the > >> installation (all paths) and the TUI. > > > > Hi! > > Thanks for the testing Alon! Yes! Thanks for testing. > > 3. I don't understand the difference of gray and non gray fields... I can > > access both... > > Do you have examples? > > Fabian, can you investigate? Sure. Alon, one example I could find were "options", e.g. on the NIC details page (where you set the bootprotocol of a nic etc) the options were also gray (instead of black, to signal that you can change them). It is intended - and it widely is this way - that gray fields can not be edited/changed. Have you got another example of a field which is gray and can be edited/changed? Thanks! fabian ___ node-devel mailing list node-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/node-devel
Re: [node-devel] RC for oVirt Node 3.0.0 is now available
Am Dienstag, den 21.05.2013, 12:34 +0200 schrieb Fabian Deutsch: > Am Montag, den 20.05.2013, 08:03 -0400 schrieb Mike Burns: > > On 05/20/2013 04:48 AM, Alon Bar-Lev wrote: > > > > > > > > > - Original Message - > > >> From: "Mike Burns" > > >> To: "node-devel" , annou...@ovirt.org > > >> Sent: Friday, May 17, 2013 7:12:48 PM > > >> Subject: [node-devel] RC for oVirt Node 3.0.0 is now available > > >> > > >> What can I test? > > >> You can focus on hardware support, package integration, the > > >> installation (all paths) and the TUI. > > > > > > Hi! > > > > Thanks for the testing Alon! > > Yes! Thanks for testing. > > > > > > 3. I don't understand the difference of gray and non gray fields... I can > > > access both... > > > > Do you have examples? > > > > Fabian, can you investigate? > > Sure. > Alon, > one example I could find were "options", e.g. on the NIC details page > (where you set the bootprotocol of a nic etc) the options were also gray > (instead of black, to signal that you can change them). > It is intended - and it widely is this way - that gray fields can not be > edited/changed. > Have you got another example of a field which is gray and can be > edited/changed? Checkboxes had the same problem. fabian > Thanks! > fabian > > > ___ > node-devel mailing list > node-devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel ___ node-devel mailing list node-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/node-devel
