Installation suse cloud 6-problem

Sounds about right, try to install that, too and see what’s coming next.

Check your network.json file in /etc/crowbar/, to me it sounds like this could be the reason why your connection is lost after running crowbar script. I don’t know if it helps, but here’s my output of my network.json:

{ "attributes": { "network": { "start_up_delay": 30, "enable_tx_offloading": false, "enable_rx_offloading": false, "teaming": { "mode": 4 }, "mode": "team", "interface_map": [ { "pattern": "X9DRT", "bus_order": [ "0000:00/0000:00:01.1/0000:02:00.0", "0000:00/0000:00:01.1/0000:02:00.1" ] } ], "conduit_map": [ { "pattern": "team/2/.*", "conduit_list": { "intf2": { "if_list": [ "+1g1", "+1g2" ] }, "intf1": { "if_list": [ "+1g1", "+1g2" ] }, "intf0": { "if_list": [ "+1g1", "+1g2" ] } } }, { "pattern": "team/1/.*", "conduit_list": { "intf2": { "if_list": [ "?1g1" ], "team_mode": 0 }, "intf1": { "if_list": [ "?1g1" ] }, "intf0": { "if_list": [ "?1g1" ] } } }, { "pattern": "team/.*/.*", "conduit_list": { "intf2": { "if_list": [ "1g1", "1g2" ] }, "intf1": { "if_list": [ "1g1", "1g2" ] }, "intf0": { "if_list": [ "1g1", "1g2" ] } } } ], "networks": { "nova_fixed": { "add_bridge": false, [...]

But I didn’t modify that file myself, it was a colleague who knows networking way better than me. I left out the part with the networks (fixed, floating, etc.), I believe you can use the defaults here.
For reference, my admin server is also a VM (xen), but they only have one interface (eth0):

[CODE]root@admin1:~ # ip link list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 00:16:3e:00:20:00 brd ff:ff:ff:ff:ff:ff

root@admin1:~ # ip address show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether 00:16:3e:00:20:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.124.129/24 brd 192.168.124.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::216:3eff:fe00:2000/64 scope link
valid_lft forever preferred_lft forever
[/CODE]

Hope this helps!

On 14/09/16 13:54, pracadyplomowa20 wrote:
[color=blue]

pracadyplomowa20;34296 Wrote:[color=green]

so i installed dnsmsql rerun installation internet connection is gone
again this is from
https://www.dropbox.com/s/cr8k3jq7si0c1hq/repo_setup.PNG?dl=0
before runnig crowbar script i have connection to internet after runing
this script connection is gone and i must reset interfaces to get
connection to internet .[/color]

now i got another i think missing pattern now is dhcp3
https://www.dropbox.com/s/nzndh2jnmuhxn1b/error4.PNG?dl=0.[/color]

Both of the above Dropbox links don’t show a graphic.

My SOC6 setup in a private network under VirtualBox on Linux does not
have access to the internet (or any other network for that matter - it’s
private with no NAT). I did not have to mess with the network.json file.

Given you’re having trouble installing packages where are you installing
from? Sounds like remote repos which obviously need a working network
connection. Perhaps try attaching ISOs as virtual DVD drives (I attach
both the SLES12 SP1 DVD1 and SOC6 DVD ISOs) which will allow the install
to find all the packages it needs.

HTH.

Simon
SUSE Knowledge Partner


If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

On 14/09/16 11:34, pracadyplomowa20 wrote:
[color=blue]

here are /etc/hosts :

https://www.dropbox.com/s/1kzq78xdt1yswga/etcHost.PNG?dl=0[/color]

I wonder whether having a short name of AdminNode which is different to
that in the fully qualified host name admin2.example.com causes
problems? The documentation has “192.168.124.10 admin.cloud.example.com
admin” which I also use with no problem but given your later replies I
think it’s ultimately a networking issue …

HTH.

Simon
SUSE Knowledge Partner


If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

On 14/09/16 15:08, Simon Flood wrote:
[color=blue]

My SOC6 setup in a private network under VirtualBox on Linux does not
have access to the internet (or any other network for that matter - it’s
private with no NAT). I did not have to mess with the network.json file.

Given you’re having trouble installing packages where are you installing
from? Sounds like remote repos which obviously need a working network
connection. Perhaps try attaching ISOs as virtual DVD drives (I attach
both the SLES12 SP1 DVD1 and SOC6 DVD ISOs) which will allow the install
to find all the packages it needs.[/color]

A thought - SOC6 expects the router IP address to be 192.168.124.1 but
you’re using NAT which if VirtualBox is anything like VMware desktop
products might reserve that for bridge interface with 192.168.124.2 as
router.

HTH.

Simon
SUSE Knowledge Partner


If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

[QUOTE=smflood;34302]On 14/09/16 11:34, pracadyplomowa20 wrote:
[color=blue]

here are /etc/hosts :

https://www.dropbox.com/s/1kzq78xdt1yswga/etcHost.PNG?dl=0[/color]

I wonder whether having a short name of AdminNode which is different to
that in the fully qualified host name admin2.example.com causes
problems? The documentation has “192.168.124.10 admin.cloud.example.com
admin” which I also use with no problem but given your later replies I
think it’s ultimately a networking issue …

HTH.

Simon
SUSE Knowledge Partner


If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------[/QUOTE]
Ok i manage install it , but the problem is . When i want launch another node vie pxe it work https://www.dropbox.com/s/budl5p6ou585mqx/node1.PNG?dl=0 but when i check dash board that node don’t show up. I add in Provisioner root_password_hash, but what about login?. I don’t know what worked previ i just put both cd into cd-room sles12 sp1 and cloud and remove gateway from routing and cloud has been installed.

On 15/09/16 09:04, pracadyplomowa20 wrote:
[color=blue]

Ok i manage install it , but the problem is . When i want launch
another node vie pxe it work
https://www.dropbox.com/s/budl5p6ou585mqx/node1.PNG?dl=0 but when i
check dash board that node don’t show up. I add in Provisioner
root_password_hash, but what about login?[/color]

If the new node PXE boots then check
/var/log/crowbar/sledgehammer/<MAC_address>..transcript (also
present on newly booted node which you should be able to SSH to from the
Admin Server) which should indicate why it’s not showing up in the
Dashboard.

My guess is time synchronisation not being set up on the Admin Server or
is out of sync.

HTH.

Simon
SUSE Knowledge Partner


If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

[QUOTE]My guess is time synchronisation not being set up on the Admin Server or
is out of sync.
[/QUOTE]

Without knowing the results yet, I assume smflood is right, I had the same issue at the beginning of my installations. Make sure that you have the ntp barclamp configured with a ntp server and this server is reachable for the new nodes.

Y it is ntp . but how configure it i do this https://www.dropbox.com/s/i90t0ng6qcjg124/ntp.PNG?dl=0

On 15/09/16 13:24, pracadyplomowa20 wrote:
[color=blue]

Y it is ntp . but how configure it i do this
https://www.dropbox.com/s/i90t0ng6qcjg124/ntp.PNG?dl=0[/color]

Which server/node is that ntp.conf file from?

You need to have time synchronisation set up and working on the Admin
Server before running install-suse-cloud as you can’t make changes to
the NTP configuration on the Admin Server afterwards (since Chef will
interfere).

If your nodes will have access to an external time source you might be
able to set the NTP Barclamp to point to that time source - it’s
currently likely to be pointing to a broken or unreachable one.

HTH.

Simon
SUSE Knowledge Partner


If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

[QUOTE=smflood;34322]On 15/09/16 13:24, pracadyplomowa20 wrote:
[color=blue]

Y it is ntp . but how configure it i do this
https://www.dropbox.com/s/i90t0ng6qcjg124/ntp.PNG?dl=0[/color]

Which server/node is that ntp.conf file from?

You need to have time synchronisation set up and working on the Admin
Server before running install-suse-cloud as you can’t make changes to
the NTP configuration on the Admin Server afterwards (since Chef will
interfere).

If your nodes will have access to an external time source you might be
able to set the NTP Barclamp to point to that time source - it’s
currently likely to be pointing to a broken or unreachable one.

HTH.

Simon
SUSE Knowledge Partner


If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------[/QUOTE]
its form my admin node , and i don’t have internet connection now since i run install-suse-cloud from website

On 15/09/16 14:24, pracadyplomowa20 wrote:
[color=blue]

its form my admin node , and i don’t have internet connection now since
i run install-suse-cloud from website[/color]

Hmm … I solved this by configuring NTP on my openSUSE host machine to
respond to NTP requests from 192.168.124.0/24. Not sure if/how you can
do this with Windows 10.

HTH.

Simon
SUSE Knowledge Partner


If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

[QUOTE ] If your nodes will have access to an external time source you might be
able to set the NTP Barclamp to point to that time source - it’s
currently likely to be pointing to a broken or unreachable one.
[/QUOTE]
What do you mean by that i don’t event know what login is set up on those nodes. What is default login on it?

hmm i installed ntp on windows but i don’t think it will works since what i understand after install suse cloud script network is isolated form outside im correct?

OK i done this i just make another vm with latest ubuntu connected him to natNetwork (adminnode) and set up ntp conf now i see nodes :slight_smile:

On 15/09/16 14:54, pracadyplomowa20 wrote:
[color=blue]

What do you mean by that i don’t event know what login is set up on
those nodes. What is default login on it?[/color]

In the Dashboard running on the Admin Server so http://192.168.124.10/
select Barclamps > Crowbar then edit NTP Management.

HTH.

Simon
SUSE Knowledge Partner


If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

now i have another problem yesterday i launch to establish controller node compute and everythink went fine . Today i log in and state of those nodes are power off when all vms are launched and works plus i cant set up another node https://www.dropbox.com/s/il7866jdtlrhc7q/noconnection.PNG?dl=0 . Now i power cycle on each vm but still nodes aren’t ready and i cant create another node.

im start to think its better i like to install this cloud on vmware vsphere

ok i fixed it i don’t know why tftp was disable .I just enable it vie yast2