Home · About · Download · Documentation · Getting Help · Google+

Custom Query (57 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1 - 3 of 57)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#13 fixed "No nodes found" reported when attempting to do provision node. gmk ajdecon

Reported by ajdecon, 7 years ago.

Description

Initial installation of warewulf-{common,vnfs,provision}. Added two nodes with names rutc0028 and rutc0030, and nodes were successfully added. However, when I attempt a "provision node" command Warewulf reports "No nodes found".

[root@wwtest warewulf]# wwsh Warewulf> node print #### rutc0028 #################################################################

rutc0028: ID = 2 rutc0028: NAME = rutc0028 rutc0028: NETDEVS = netdev(NAME=eth0,IPADDR=10.20.2.1,HWADDR=00:15:C5:EF:7B:01) rutc0028: TYPE = node rutc0028: HWADDR = 00:15:C5:EF:7B:01

#### rutc0030 #################################################################

rutc0030: ID = 5 rutc0030: NAME = rutc0030 rutc0030: NETDEVS = netdev(NAME=eth0,IPADDR=10.20.2.3,HWADDR=00:15:C5:EF:80:A0) rutc0030: TYPE = node rutc0030: HWADDR = 00:15:C5:EF:80:A0

Warewulf> provision node rutc0028 --bootstrap=2.6.18-238.el5 --vnfs rhel-5.vnfs No nodes found

Followed instructions in the Quickstart document exactly until this problem. Cannot identify the nodes by hwaddr, name, etc in the "provision node" command.

#17 fixed Cannot change the vnfs setting for a node gmk ajdecon

Reported by ajdecon, 7 years ago.

Description

Summary: cannot use node set command to change the vnfs for an existing node.

Warewulf rev 428 running on CentOS 5.6. Created a vnfs and provisioned three compute nodes as shown in the quickstart guide using wwnodescan, no problems.

Then I carried out the exact same process: use mkchroot-rh.sh to create a new chroot (and modified it by placing an ssh authorized_keys file in place), created the vnfs capsule and imported it into warewulf. Then I used the following command to change the VNFS:

node set node000 -s vnfs=centos-5.6.vnfs

Typing "node print" showed that the vnfs name had changed to centos-5.6.vnfs, but the VNFSID was the same (=1). Rebooting showed that the original vnfs was still being provisioned. Deleting the original vnfs resulted in the node getting stuck in a loop in which it continually retried provisioning.

Following this I deleted the node and re-added it using wwnodescan, whereupon it provisioned normally with the correct vnfs. But I have not yet successfully changed the vnfs in an existing node.

#20 fixed Error when attempting to export vnfs. gmk ajdecon

Reported by ajdecon, 7 years ago.

Description

Currently running warewulf rev 428. Attempted to export a vnfs using "vnfs export --name=centos-new.vnfs /tmp/centos-again.vnfs", and several different variations thereof. In all cases, received the following error:

Can't call method "get" on an undefined value at /usr/lib/perl5/vendor_perl/5.8.8/Warewulf/Module/Cli/Vnfs.pm line 262, <FIN> line 2.

That line in Vnfs.pm is

my $dirname = dirname($opt_export);

This line is in the last "else" clause of an if statement which tests against $opt_export. I threw a print statement in above just before the whole if statement and tried again with several statements, and $opt_export was empty. Not quite sure where $opt_export is supposed to be coming from here.

1 2 3 4 5 6 7 8 9 10 11
Note: See TracQuery for help on using queries.